Re: panic: System call lstat returning with 1 locks held

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Pawel Jakub Dawidek <pjd@...>
Cc: <freebsd-current@...>
Date: Friday, January 18, 2008 - 3:12 am

On 1/17/08, Pawel Jakub Dawidek <pjd@freebsd.org> wrote:

I rebuilt the zfs module as suggested.

When I reboot, I am now seeing 4 different lock order reversals related to ZFS:

1. This lock order reversal occurs most often:

lock order reversal:
 1st 0xffffff0001b95838 dr->dt.di.dr_mtx (dr->dt.di.dr_mtx) @
/usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1866
 2nd 0xffffff00017531c0 db->db_mtx (db->db_mtx) @
/usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1888
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
witness_checkorder() at witness_checkorder+0x606
_sx_xlock() at _sx_xlock+0x52
dbuf_sync_list() at dbuf_sync_list+0x215
dbuf_sync_list() at dbuf_sync_list+0x194
dnode_sync() at dnode_sync+0x385
dmu_objset_sync() at dmu_objset_sync+0x116
dsl_pool_sync() at dsl_pool_sync+0x153
spa_sync() at spa_sync+0x39e
txg_sync_thread() at txg_sync_thread+0x17d
fork_exit() at fork_exit+0x12a
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffffffd72a3d30, rbp = 0 ---

2. This lock order reversal is similar to the one above:

lock order reversal:
 1st 0xffffff0001b00d38 dr->dt.di.dr_mtx (dr->dt.di.dr_mtx) @
/usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1866
 2nd 0xffffff0001a27760 db->db_mtx (db->db_mtx) @
/usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1837
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
witness_checkorder() at witness_checkorder+0x606
_sx_xlock() at _sx_xlock+0x52
dbuf_sync_list() at dbuf_sync_list+0xaf
dbuf_sync_list() at dbuf_sync_list+0x194
dnode_sync() at dnode_sync+0x385
dmu_objset_sync() at dmu_objset_sync+0x116
dsl_pool_sync() at dsl_pool_sync+0x72
spa_sync() at spa_sync+0x39e
txg_sync_thread() at txg_sync_thread+0x17d
fork_exit() at fork_exit+0x12a
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffffffd72a3d30, rbp = 0 ---

3. lock order reversal related to the write syscall

lock order reversal:
1st 0xffffff00269f6500 dn->dn_mtx
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
panic: System call lstat returning with 1 locks held, Scot Hetzel, (Tue Jan 15, 9:52 am)
Re: panic: System call lstat returning with 1 locks held, Kostik Belousov, (Tue Jan 15, 10:39 am)
Re: panic: System call lstat returning with 1 locks held, Pawel Jakub Dawidek, (Thu Jan 17, 7:40 am)
Re: panic: System call lstat returning with 1 locks held, Scot Hetzel, (Fri Jan 18, 3:12 am)
Re: panic: System call lstat returning with 1 locks held, Norikatsu Shigemura, (Fri Jan 18, 12:55 pm)
Re: panic: System call lstat returning with 1 locks held, Kris Kennaway, (Wed Jan 16, 5:55 am)
Re: panic: System call lstat returning with 1 locks held, John Baldwin, (Wed Jan 16, 11:11 am)