From owner-freebsd-hackers Sun Aug 27 9:52: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D933537B42C for ; Sun, 27 Aug 2000 09:52:05 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7RGq0Z07318; Sun, 27 Aug 2000 09:52:00 -0700 (PDT) Date: Sun, 27 Aug 2000 09:52:00 -0700 From: Alfred Perlstein To: Blaz Zupan Cc: Clarence Brown , freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000827095200.A1209@fw.wintelcom.net> References: <003301c01041$5c3e9da0$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from blaz@amis.net on Sun, Aug 27, 2000 at 06:12:54PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Blaz Zupan [000827 09:13] wrote: > > Problem: If I do a "shutdown -h now" and then press > > any key to reboot, the system ALWAYS hangs after > > displaying the line.. > > > > isa0: on motherboard > > I think I've seen this on a customer's 486 (used as a wireless router) and if > I remember correctly it was caused by the ata driver. Unplugging the hard disk > fixed it (but obviously I couldn't install FreeBSD on such a machine :), it > was a Western Digital. Using the wd driver fixed it as well. Plugging in > another hard disk (a newer Western Digital) fixed it as well. I chose the > later route, as the old disk crashed a couple of days after using it with the > wd driver. Also, I had to use userconfig to remove all drivers for hardware I > didn't have. Guys, here's what you need to do; go to: http://www.freebsd.org/handbook/kerneldebug.html Basically you need to compile a kernel with: options DDB options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to then when it hangs at boot one might be able to to hit ctrl+alt+esc to get into the kernel debugger, then hit 't' (i think, it's been a while :) ) to get a traceback. Tell us what you see. Another simpler option is interrupting the boot countdown and typing 'boot -v' to get a more verbose boot then give us more information than just "isa0: on motherboard". :) Please let us know what you find out. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message