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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Scot Hetzel <swhetzel@...>
Cc: <freebsd-current@...>
Date: Tuesday, January 15, 2008 - 10:39 am

On Tue, Jan 15, 2008 at 07:52:12AM -0600, Scot Hetzel wrote:
I think this could be related to the recent vn_lock()/VOP_LOCK() KPI change=
s.
Please, add DEBUG_VFS_LOCKS to the kernel config, and do the
	show lockedvnods
from the ddb prompt when the panic occurs. The witness does not track
the lockmgr locks.

are
ons.
s.

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, 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)