Re: kern/50375: layerfs (nullfs) locking problem leading to livelock

["J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>]

The following reply was made to PR kern/50375; it has been noted by GNATS.

From: "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Jeff Rizzo <riz%NetBSD.org@localhost>
Subject: Re: kern/50375: layerfs (nullfs) locking problem leading to livelock
Date: Wed, 28 Oct 2015 17:26:38 +0100

 > My understanding is that the next step would be to look at the =
 individual frames of the backtrace of that process to figure out what vp =
 is - I would appreciate suggestions for how to do this with the system =
 live, using either ddb or gdb against /dev/mem.  (Assume I don't know =
 what I'm doing, and give me very specific instructions :)
 
 So you have the tstile threads lwp address (either from crash or ddb or =
 ps).
 
 Running gdb with netbsd.gdb against /dev/mem
 
 	gdb netbsd.gdb
 	target kvm /dev/mem
 
 you should be able to get a backtrace with arguments with
 
 	kvm proc 0x96f831a0
 	bt
 
 These backtraces for all threads in tstile should help.
 
 --
 J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig (Germany)