Date: Sun, 11 Jul 2004 22:59:47 -0400 From: Brian Fundakowski Feldman <green@FreeBSD.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: "panic: malloc(M_WAITOK) in interrupt context" while in DDB Message-ID: <20040712025947.GN1626@green.homeunix.org> In-Reply-To: <Pine.NEB.3.96L.1040711201316.19581V-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1040711201316.19581V-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 11, 2004 at 08:16:37PM -0400, Robert Watson wrote: > > Got the following rather drawn out stack trace while working with DDB on a > panic earlier this afternoon. I got a good three panics/traps: > > (1) Breaking to DDB using the serial console to evaluate a hang. (fine) > > (2) Calling panic from DDB to get a dump, which generated a trap because > it tried to sync(). (Remind me: why do we do that?) > > (3) Getting a panic because I called panic from that session of DDB > because KDB tried to perform an orderly shutdown, resulting in GEOM > panicking on trying to generate safe shutdown events by mallocing. > > It sounds like we should really turn off trying to sync() in panic(). It > sounds like we also should also have a better way of having module > shutdown take place from the debugger. I think I've been trying to get people to accept that it's a bad idea for years now. Any machine I touch just gets debug.sync_on_panic=0 in its /etc/sysctl.conf immediately. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040712025947.GN1626>