Date: Wed, 27 Dec 2006 23:50:43 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: "R. Tyler Ballance" <tyler@bleepsoft.com>, Brian Dean <brian@bsdhome.com> Subject: Re: Kernel hang on 6.x Message-ID: <200612272350.43680.jhb@freebsd.org> In-Reply-To: <552E24DE-C1D1-41B1-83D2-157F0A3E0449@bleepsoft.com> References: <20061214190510.GA26590@neutrino.bsdhome.com> <552E24DE-C1D1-41B1-83D2-157F0A3E0449@bleepsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 14 December 2006 16:06, R. Tyler Ballance wrote: > > On Dec 14, 2006, at 1:05 PM, Brian Dean wrote: > > > Hi, > > > > We're experiencing a kernel hang on a 6.x quad processor Sun amd64 > > based system. We are able to reproduce it fairly reliably, but the > > environment to do so is not easily replicatable so I cannot provide a > > simple test case. However, I have been able to build a debug kernel > > and when the system "hangs", I can break to the debugger prompt. But > > once there, I'm not sure what to do to isolate where the system is > > hung up. I have confirmed that the hang occurs in both SMP and > > uniprocessor mode. Here are some system details: > > > I think you'll need to ship this machine to my house for further > um....erm, diagnostics, yes, that's it ;) > > > On a more serious topic, can you paste the output from: > > > ddb> show pcpu > ddb>allpcpu > ddb>traceall > ddb>show alllocks > ddb>show lockedvnods > > Just curious as to whether those would show more info, because you're > right, that trace is about as informative as new printer paper :) The 'traceall' seemed to miss several threads actually (like pid 18). Can you get a 'ps'? Also, are you able to get a kernel dump when this happens? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612272350.43680.jhb>