From owner-freebsd-questions Thu Apr 9 18:47:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24352 for freebsd-questions-outgoing; Thu, 9 Apr 1998 18:47:09 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from euthyphro.uchicago.edu (euthyphro.uchicago.edu [128.135.21.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24340 for ; Thu, 9 Apr 1998 18:46:57 -0700 (PDT) (envelope-from sfarrell@phaedrus.uchicago.edu) Received: from phaedrus.uchicago.edu (phaedrus [128.135.21.10]) by euthyphro.uchicago.edu (8.8.6/8.8.4) with ESMTP id UAA22795; Thu, 9 Apr 1998 20:46:52 -0500 (CDT) Received: (from sfarrell@localhost) by phaedrus.uchicago.edu (8.8.8/8.8.5) id UAA22101; Thu, 9 Apr 1998 20:46:51 -0500 (CDT) To: jwlo@ms11.hinet.net Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Please help me!! References: <352D2A8E.6FE308B7@ms11.hinet.net> From: sfarrell+lists@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 09 Apr 1998 20:46:50 -0500 In-Reply-To: Doug Lo's message of "Fri, 10 Apr 1998 04:07:42 +0800" Message-ID: <87af9usb1w.fsf@phaedrus.uchicago.edu> Lines: 30 X-Mailer: Gnus v5.6.3/XEmacs 20.3 - "Vatican City" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Lo writes: > Yesterday I used boot floopy to install FreeBSD 2.2.6-RELEASE. > First time I boot, it got a messange "Intel Pentium F00F detected, > installing workaround", > after I got this message, it still works fine for me. > Then I edit my kernel, reboot, it got messages: > > Intel Pentium F00F detected, installing wrokaround. > pid 5 (sh), uid 0 : exited on singal 8 > Apr 10 04:04:33 init:/bin/sh on /etc/rc terminated abnormally, going to > single user mode. > Enter full pathname of shell or RETURN for /bin/sh: > > So I used 'single user mode(-s)' to reboot, still the same. > Would anyone like to teach me how to solve this issue? Well, you should be able to get back up and running by typing kernel.old or kernel.GENERIC at the boot prompt. then, you evidentally changed something in the kernel config that caused a problem... start again with the GENERNIC config file and make a new kernel. I suppose you could either use trial-and-error to figure out what that was, or else post any items you think might be likely to have been problematic. I don't know off-hand what might cause /bin/sh to break! -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message