Dave [EMAIL PROTECTED] writes:
My thinking: the threading in the kernel for 5.1 CURRENT hasn't all the
kinks out yet. Does anyone know what is going on?
Before rushing off to the FreeBSD people with it though, they 1) might
already be aware, and 2) maybe I don't understand the error
Hello!
I have it too, after compiling kernel with debug info and spinlock
witnessing. It does no harm, I guess...
I get THIS *every* time I exit X-windows:
lock order reversal
1st 0xc45f4b90 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:432
2nd 0xc082f110 system map (system map) @
On Sat, Jul 12, 2003 at 11:30:18PM +0200, Pawel Kraszewski wrote:
Hello!
I have it too, after compiling kernel with debug info and spinlock
witnessing. It does no harm, I guess...
Problems with -current should not be discussed on the questions@
mailing list. Check the current@ archives
I get THIS *every* time I exit X-windows:
lock order reversal
1st 0xc45f4b90 vm object (vm object) @ /usr/src/sys/vm/vm_object.c:432
2nd 0xc082f110 system map (system map) @ /usr/src/sys/vm/vm_kern.c:325
Stack backtrace:
backtrace(c057b35f,c082f110,c058cfb6,c058cfb6,c058ce51) at