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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Attilio Rao <attilio@...>
Cc: Kostik Belousov <kostikbel@...>, <freebsd-current@...>
Date: Thursday, January 24, 2008 - 1:47 pm

On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote:

The first lines of the ktr output are attached.  I can try to extract
all 32768 lines if needed, but they all look almost the same.  I.e.,
the function name and the td pointer are the same while td_locks
bump is 1 or -1.

-- 
Yar

db> show ktr
430 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
429 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
428 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
427 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
426 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
425 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
424 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
423 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
422 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
421 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
420 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
419 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
418 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
417 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
416 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
415 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
414 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
413 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
412 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
411 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
410 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
409 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
408 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
407 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
406 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
405 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
404 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
403 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
402 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
401 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
400 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
399 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
398 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
397 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
396 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
395 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
394 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
393 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
392 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
391 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
390 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
389 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
388 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
387 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
386 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
385 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
384 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks
383 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
382 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
381 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks
...
_______________________________________________
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, Yar Tikhiy, (Thu Jan 24, 1:47 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)