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: Tuesday, February 5, 2008 - 3:56 pm

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

Currently it is DDB which let it fail in witness after memory corruption.
But I'm more interested in the panic originator; so, as far as it is
unusable, can you please remove DDB option and try to get the panic
again? it should not give you the failing assertion without DDB.

Thanks,
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, (Tue Feb 5, 3:56 pm)
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)