From nobody  Sun May  3 22:33:51 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA24338;
          Sun, 3 May 1998 22:33:51 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199805040533.WAA24338@hub.freebsd.org>
Date: Sun, 3 May 1998 22:33:51 -0700 (PDT)
From: morris@barvennon.com
To: freebsd-gnats-submit@freebsd.org
Subject: system will not soft reboot
X-Send-Pr-Version: www-1.0

>Number:         6506
>Category:       kern
>Synopsis:       system will not soft reboot
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May  3 22:40:00 PDT 1998
>Closed-Date:    Thu May 24 12:56:00 PDT 2001
>Last-Modified:  Thu May 24 12:57:36 PDT 2001
>Originator:     chris
>Release:        2.2.5
>Organization:
>Environment:
Dear someone at freebsd, 

I love the system, & have 2.2.2 up as server for barvennon.com .  I am upgrading (experimenting) on/to 2.2.5 on a second
computer, and there seems to be no way to get it (2nd pc) to do a shutdown or reboot.  When that computer is on dos 6.22
MEMMAKER can reboot, so it probably isn't an inherent hardware prob.  I have tried with or without booteasy, always the
same prob., it just stops before complete shutdown.  Below are vital statistics, if you want i can let you get at it online, to check
what is set up inside.. 

hardware - ibm "value point"  486dx-33   8MB RAM, 203mb HD 

software - freebsd 2.2.5 with dedicated disk 203MB (booteasy with a dos partition didn't work any better.) 

the messages... 

shutdown -r now 

shutdown NOW! 
shutdown: [PID171] 

***FINAL System shutdown message from root@zeta.barvennon.com*** 

System going down IMMEDIATELY 

May   4 15:43:39 zeta shutdown: reboot by root: 
May   4 15:43:39 zeta shutdown: reboot by root: 

System shutdown time has arrived 
May   4 15:43:41 zeta syslogd: exiting on signal 15 
May   4 15:43:41 zeta syslogd: exiting on signal 15 
May   4 15:43:41 zeta syslogd: exiting on signal 15 

Syncing discs... 8 8 6 done 
rebooting... 
keyboard reset did not work, attempting CPU shutdown 

and there is where it hangs. 

sometimes, it stops at an earlier point. 

have you got a fix?  maybe I have installed it wrong, but I have reinstalled it dozens of times on that hardware, no luck, always
the same prob.  I installed it on another computer, & this problem did not arise. 

I suspect the IBM hardware, is it different, in a way that you did not account for in BSD? 

I am happy to set up an account on barvennon.com from which you can log onto zeta as su & inspect. 

chris 
  
  
>Description:
see above
>How-To-Repeat:
ha ha

try an ibm valuepoint 486dx33 8mb
>Fix:
put it on a nother computer
>Release-Note:
>Audit-Trail:

From: Matthew Hunt <mph@pobox.com>
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 <mph@pobox.com> * Stay close to the Vorlon.
 http://mph124.rh.psu.edu/~mph/pgp.key for PGP public key 0x67203349.
State-Changed-From-To: open->closed 
State-Changed-By: kris 
State-Changed-When: Thu May 24 12:56:00 PDT 2001 
State-Changed-Why:  
Problem relates to a very old version of FreeBSD; please follow-up 
to this PR if it persists with FreeBSD 4.3 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6506 
>Unformatted:
