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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Yar Tikhiy <yar@...>
Cc: Kostik Belousov <kostikbel@...>, Scot Hetzel <swhetzel@...>, <freebsd-current@...>, Doug Barton <dougb@...>
Date: Wednesday, February 6, 2008 - 10:52 am

2008/2/6, Yar Tikhiy <yar@comp.chem.msu.su>:

This is the new I wanted to know! :)
With better checks in lockmgr code, we would have caught more
informations about it.

Can you please now add DDB support and once it breaks in DDB do a
'show alllocks' and maybe other small investigations?
This should shade a light for us.

Attilio


-- 
Peace can only be achieved by understanding - A. Einstein
_______________________________________________
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, Attilio Rao, (Wed Feb 6, 10:52 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)