lock order reversal on recent (06/30) CURRENT

Is the following a known problem? (occured while running python2.3 using kse) lock order reversal 1st 0xc03c3c40 smp rendezvous (smp rendezvous) @ /usr/src/sys/kern/subr_smp.c:3 13 2nd 0xc03c00c0 sched lock (sched lock) @ /usr/src/sys/i386/i386/sys_machdep.c:2 92 Stack backtrace: backtrace(c0343

python2.3 build with kse freezes CURRENT

For the last few weeks I have difficulties building python2.3 with threads enabled. Building using -lthr leaves python's thread related modules inoperable. Using -lkse builds ok, but in the python test suite test_signal.py hangs for ever. It seems that a SIGALRM is not caught. Until sometime l

curses header conflict (wchar_t,wint_t)

When trying to install python2.3 on either stable or current the python curses module doesn't build. I get the following compiler complaints: STABLE (line numbers in brackets are from CURRENT) /usr/include/ncurses.h:236(289): conflicting types for `wchar_t' /usr/include/stdlib.h:58(57): previous

smp-kernel panics while booting

I have 2 Xeon processors on a PDPEA (Rioworks) motherboard (http://www.rioworks.co.jp/products/pdpea.html). The generic kernel boots without problems (see output of dmesg below). When I use the SMP kernel I invariably (5.0 release, various CURRENTs, the latest cvsuped yesterday, various BIOS set