8.0 BETA1 LOR

Fernando Apesteguía fernando.apesteguia at gmail.com
Tue Jul 14 09:55:25 UTC 2009


2009/7/13 Glen Barber <glen.j.barber at gmail.com>:
> 2009/7/13 Glen Barber <glen.j.barber at gmail.com>:
>> Hi, Fernando
>>
>> 2009/7/13 Fernando Apesteguía <fernando.apesteguia at gmail.com>:
>>> Hi there,
>>>
>>> I downloaded FreeBSD 8.0 in order to help testing it. I have found
>>> several issues. This is the first one:
>>>
>>> Jul 13 18:37:43 beastie kernel: lock order reversal:
>>> Jul 13 18:37:43 beastie kernel: 1st 0xffffff0007d42ba8 ufs (ufs) @
>>> /usr/src/sys/kern/vfs_mount.c:1199
>>> Jul 13 18:37:43 beastie kernel: 2nd 0xffffff002e007270 devfs (devfs) @
>>> /usr/src/sys/fs/msdosfs/msdosfs_vfsops.c:944
>>> Jul 13 18:37:43 beastie kernel: KDB: stack backtrace:
>>> Jul 13 18:37:43 beastie kernel: db_trace_self_wrapper() at
>>> db_trace_self_wrapper+0x2a
>>> Jul 13 18:37:43 beastie kernel: _witness_debugger() at _witness_debugger+0x2e
>>> Jul 13 18:37:43 beastie kernel: witness_checkorder() at witness_checkorder+0x81e
>>> Jul 13 18:37:43 beastie kernel: __lockmgr_args() at __lockmgr_args+0xcf3
>>> Jul 13 18:37:43 beastie kernel: vop_stdlock() at vop_stdlock+0x39
>>> Jul 13 18:37:43 beastie kernel: VOP_LOCK1_APV() at VOP_LOCK1_APV+0x9b
>>> Jul 13 18:37:43 beastie kernel: _vn_lock() at _vn_lock+0x47
>>> Jul 13 18:37:43 beastie kernel: msdosfs_sync() at msdosfs_sync+0x227
>>> Jul 13 18:37:43 beastie kernel: dounmount() at dounmount+0x2ca
>>> Jul 13 18:37:43 beastie kernel: unmount() at unmount+0x28a
>>> Jul 13 18:37:43 beastie kernel: syscall() at syscall+0x1af
>>> Jul 13 18:37:43 beastie kernel: Xfast_syscall() at Xfast_syscall+0xd0
>>> Jul 13 18:37:43 beastie kernel: --- syscall (22, FreeBSD ELF64,
>>> unmount), rip = 0x8006a09ac, rsp = 0x7fffffffdc38, rbp = 0 ---
>>> Jul 13 18:37:44 beastie gnome-keyring-daemon[61245]: removing
>>> removable location: volume_size_4144496640
>>>
>>> I got this while trying to unmount a USB device. The unmounting seemed
>>> to be fine, all the files were in the device and no corruption
>>> occurred. I found a very similar problem (maybe the same) here[1]. Any
>>> clues about this?
>>>
>>>
>>> Thanks in advance.
>>>
>>> PS: Is this the proper list for asking these questions?
>>>
>>> [1] http://forums.freebsd.org/showthread.php?p=31490
>>
>> You can view reported lock order reversals here:
>>
>> http://sources.zabbadoz.net/freebsd/lor.html
>>
>> Questions about the -CURRENT branch should be asked on questions at .
>>
>
> This is why multitasking is not generally a good thing.  I meant current at .

OK, thanks. I will have a look at the list.

Cheers

>
> Sorry for the noise.
>
>
> --
> Glen Barber
>


More information about the freebsd-questions mailing list