From nobody@FreeBSD.ORG Tue May  4 06:41:46 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id E1CC5154C4; Tue,  4 May 1999 06:41:46 -0700 (PDT)
Message-Id: <19990504134146.E1CC5154C4@hub.freebsd.org>
Date: Tue,  4 May 1999 06:41:46 -0700 (PDT)
From: schreib_mir_du_spacken@gmx.de
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: Error while starting FreeBSD
X-Send-Pr-Version: www-1.0

>Number:         11488
>Category:       i386
>Synopsis:       Error while starting FreeBSD
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May  4 06:50:01 PDT 1999
>Closed-Date:    Tue May 16 14:38:29 PDT 2000
>Last-Modified:  Tue May 16 14:41:51 PDT 2000
>Originator:     Matthias Kretschmer
>Release:        Release 3.1
>Organization:
Private
>Environment:
FreeBSD myname.my.domain 3.1-RELEASE root@myname.my.domain:/usr/src/sys/compile/NOTEBOOK i386
>Description:
After running Win98 and just rebooting the computer (it is an Mitac 5036 Notebook with Tillamook 266MHz CPU and 64MB-Ram) the system crashes after initializing the npx0 driver/device. After switching the notebook off, freebsd boots and the it runs normally!
>How-To-Repeat:
Just running Windows 98 befor starting FreeBSD!
>Fix:
Switching the notebook off before running FreeBSD solves the problem.

>Release-Note:
>Audit-Trail:

From: Omachonu Ogali <oogali@intranova.net>
To: freebsd-gnats-submit@freebsd.org
Cc: schreib_mir_du_spacken@gmx.edu
Subject: Re: i386/11488: Error while starting FreeBSD
Date: Thu, 27 Apr 2000 02:41:22 -0400 (EDT)

 My conclusion is that the laptop is not resetting the coprocessor on each
 reboot causing it to be in an open state, so when FreeBSD attempts to
 initalize it, it fails resulting in a machine lockup.  Unless this was
 reported to the manafacturer, the only solution would be to power off and
 on before switching operating systems.
 
 -- 
 +-------------------------------------------------------------------------+
 | Omachonu Ogali                                     oogali@intranova.net |
 | Intranova Networking Group                 http://tribune.intranova.net |
 | PGP Key ID:                                                  0xBFE60839 |
 | PGP Fingerprint:       C8 51 14 FD 2A 87 53 D1  E3 AA 12 12 01 93 BD 34 |
 +-------------------------------------------------------------------------+
 
 
State-Changed-From-To: open->closed 
State-Changed-By: hoek 
State-Changed-When: Tue May 16 14:38:29 PDT 2000 
State-Changed-Why:  
I concur with Omachonu Ogali <oogali@intranova.net> analysis of the 
problem.  The laptop hardware must not be resetting itself properly 
and, if Omachonu is correct, nothing could be done even if FreeBSD 
knew exactly what wasn't being initialised correctly.  A full power 
cycle isn't too expensive a price to pay, and not a bad idea anyways. 
>Unformatted:
