Date: Fri, 13 Aug 2004 14:09:09 -0600 From: Scott Long <scottl@samsco.org> To: Lukas Ertl <le@freebsd.org> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: Deadlocks with recent SMP current Message-ID: <411D1FE5.3080809@samsco.org> In-Reply-To: <20040813215227.F730@korben.in.tern> References: <Pine.NEB.3.96L.1040813152348.73100I-100000@fledge.watson.org> <20040813215227.F730@korben.in.tern>
next in thread | previous in thread | raw e-mail | index | archive | help
Lukas Ertl wrote: > On Fri, 13 Aug 2004, Robert Watson wrote: > >> will eventually get a solid hang. I tried it on a new SMP box with an >> NMI >> button I received yesterday but was unable to get into the debugger. I'm >> in the process of de-obfuscating the NMI path to increase the chances of >> successfully getting into the debugger and then I'll try again to see >> what >> I can figure out. > > > I have an NMI-enabled SMP box too, and the only message I got when > sending an NMI to the deadlocked system was 'kernel trap 12 with > interrupts disabled', but nothing more. > > If you want me to test something, feel free to shout out. > > cheers, > le > The NMI handler(s) try to do far too much and often get caught up in mutexes. I've locally changed it to just call either kdb_backtrace() or kdb_enter() and then reboot. We might want to consider looking for a general solution for this in 5.3. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?411D1FE5.3080809>