Date: Thu, 14 Dec 2006 15:06:29 -0600 From: "R. Tyler Ballance" <tyler@bleepsoft.com> To: Brian Dean <brian@bsdhome.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x Message-ID: <552E24DE-C1D1-41B1-83D2-157F0A3E0449@bleepsoft.com> In-Reply-To: <20061214190510.GA26590@neutrino.bsdhome.com> References: <20061214190510.GA26590@neutrino.bsdhome.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :) Cheers R. Tyler Ballance: Lead Mac Developer at bleep. software contact: tyler@bleepsoft.com | jabber: tyler@jabber.geekisp.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?552E24DE-C1D1-41B1-83D2-157F0A3E0449>