From owner-freebsd-bugs Sun May 3 23:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28811 for freebsd-bugs-outgoing; Sun, 3 May 1998 23:12:25 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28805 for ; Sun, 3 May 1998 23:12:24 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id XAA26030; Sun, 3 May 1998 23:10:00 -0700 (PDT) Date: Sun, 3 May 1998 23:10:00 -0700 (PDT) Message-Id: <199805040610.XAA26030@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Matthew Hunt Subject: Re: kern/6506: system will not soft reboot Reply-To: Matthew Hunt Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/6506; it has been noted by GNATS. From: Matthew Hunt To: morris@barvennon.com, freebsd-gnats-submit@FreeBSD.ORG Cc: Subject: Re: kern/6506: system will not soft reboot Date: Mon, 4 May 1998 02:10:41 -0400 On Sun, May 03, 1998 at 10:33:51PM -0700, morris@barvennon.com wrote: > hardware - ibm "value point" 486dx-33 8MB RAM, 203mb HD [...] > Syncing discs... 8 8 6 done > rebooting... > keyboard reset did not work, attempting CPU shutdown This seems to be a fairly common problem with 486 motherboards. My old one did it, and the problem is reported here occasionally. Typically, these motherboards can be rebooted using Linux, if the kernel command-line option "reboot=bios" is supplied. A colleague tried to port the relevant kernel code to FreeBSD, but we were not able to get it to reboot my motherboard. I don't have that motherboard, so I cannot provide any more assistance in that regard. Perhaps this is enough of a clue for somebody who is so inclined to pursue it... -- Matthew Hunt * Stay close to the Vorlon. http://mph124.rh.psu.edu/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message