On 31-Jul-01 Vincent Poy wrote:
> On Tue, 31 Jul 2001, John Baldwin wrote:
>> > root@pele [9:29pm][/usr/temp] >>
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: lock order reversal
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @
>> > /usr/src/sys/vm/vm_glue.c:469
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: 1st 0xd92fea9c process lock @
>> > /usr/src/sys/vm/vm_glue.c:469
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock
>> > @ /usr/src/sys/kern/kern_lock.c:239
>> > Jul 28 21:29:40 pele /boot/kernel/kernel: 2nd 0xc118dfb0 lockmgr interlock
>> > @ /usr/src/sys/kern/kern_lock.c:239
>>
>> This is due to the way that lockmgr locks are implemented unfortunately, and
>> will be fixed when vm maps switch to sx locks instead of lockmgr locks.
>
> Interesting. Is there a workaround so it just reboots instead of
> freezing? Also, I noticed that you committed some changes to the kernel,
> is that supposed to help it any?
There is currently not a workaround. The changes committed fix other things,
but not this problem. I haven't actually seen this lock order cause a freeze
before to be honest.
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
