From owner-freebsd-bugs Thu Apr 27 0:30: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id CF1D737BE07 for ; Thu, 27 Apr 2000 00:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id AAA47730; Thu, 27 Apr 2000 00:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 27 Apr 2000 00:30:02 -0700 (PDT) Message-Id: <200004270730.AAA47730@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Omachonu Ogali Subject: Re: i386/11488: Error while starting FreeBSD Reply-To: Omachonu Ogali Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/11488; it has been noted by GNATS. From: Omachonu Ogali 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 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message