Date: Tue, 6 May 2008 05:59:38 -0700 From: Jeremy Chadwick <koitsu@freebsd.org> To: Stephen Clark <sclark46@earthlink.net> Cc: freebsd-stable@freebsd.org Subject: Re: reboot after panic Message-ID: <20080506125938.GA8831@eos.sc1.parodius.com> In-Reply-To: <481B19C4.1040806@earthlink.net> References: <4819BB3A.6000407@earthlink.net> <B9638CACBA387E48927BB56B6A15550715CEDF@svr1.irtnog.org> <481A16E7.8040709@earthlink.net> <20080501210233.GA15528@lava.net> <481B19C4.1040806@earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 02, 2008 at 09:40:20AM -0400, Stephen Clark wrote: > Mine is a nvidia 6300 mb with a dual core amd processor. I am causing the panic > while trying to develope a DD for a EVDO usb modem - so it is not a great > problem - I was just surprised it wasn't rebooting. This is a 6.1 system. > > Yes it is sort of discouraging that it is hard to get answers when you > aren't running the latest and greatest kernel. In our case we have over 500 > units in > the field running a mix of 4.9 and 6.1 and it is not feasible to > continually upgrade them, especially since there is no documented way to > reliably upgrade > a remote installation. Does the system reboot OK if you issue the "reboot" command? If not, then the problem is likely with the reboot method being used (ACPI vs. non-ACPI) or ACPI tweakage prior to reboot, and not anything to do with panics. See the following two sysctls: hw.acpi.disable_on_reboot hw.acpi.handle_reboot -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080506125938.GA8831>