Date: Tue, 08 Mar 2005 17:34:34 -0500 From: David Scheidt <dmschei@attglobal.net> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Reproducible Panic with port iplog Message-ID: <422E287A.80805@attglobal.net> In-Reply-To: <20050308184005.GA30165@hub.freebsd.org> References: <2861.172.16.0.199.1109814152.squirrel@172.16.0.199> <20050303015438.GF15329@obiwan.tataz.chchile.org> <2910.172.16.0.199.1109816379.squirrel@172.16.0.199> <1646.172.16.0.199.1110049506.squirrel@172.16.0.199> <4420.172.16.0.199.1110301463.squirrel@172.16.0.199> <20050308100730.Q38988@carver.gumbysoft.com> <20050308184005.GA30165@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Tue, Mar 08, 2005 at 10:09:01AM -0800, Doug White wrote: > >>On Tue, 8 Mar 2005, Mike Jakubik wrote: >> >>>It does not seem to be for me. The system just stands there doing nothing >>>after the panic, when there is no debugger built in the kernel. >>> >>>P.S. I have also submitted a PR for this. >>>http://www.freebsd.org/cgi/query-pr.cgi?pr=78384 >> >>I don't know if I can get to this before the release, but I've put it on >>my tracking list. I need a way to provoke a panic, and the best way seems >>to be to program the syscons panic key. > > > I've seen DDB_UNATTENDED cause a hang-on-panic instead of a dump + > reboot on HEAD. I've also seen it not dumping core when it does > manage to reboot. I haven't tested this on RELENG_5. > > Both my ThinkPad and a desktop box I've got running RELENG_5 hang on panic. No reboot, no dump. Have to pull the battery from the ThinkPad to get it to reboot. dumpdev is set in rc.conf on both machines.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?422E287A.80805>