Gertjan Oude Lohuis wrote:
> One of our fileservers went down pretty hard yesterday. We recently 
> upgraded the kernel to 2.6.24 because we suffered from the 
> lockd-lockup with our previous kernel (2.6.18).
> The server stopped responding completely to any requests (nfs, ssh, 
> ping) and every few seconds a stacktrace was dumped on the console. 
> The stacktraces hint at nfsd (Pid: 2716, comm: nfsd Not tainted 
> (2.6.24.2-fwsh-byte #2) and various nfs-functions in the trace). I 
> attached some of them to this message.

This morning the same server crashed again, with the same stacktrace (at 
least to my eyes :-)). I think we'll be downgrading to 2.6.23 as soon as 
possible. Is there anything I can do to get more debug information? Now 
or when it crashes? When the server crashes, I'm able to logging to it 
with the serial console, and reboot it with 'send break -> b'.

Regards,
Gertjan Oude Lohuis