From owner-freebsd-hackers Sun Aug 27 10:59:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id E677937B422 for ; Sun, 27 Aug 2000 10:59:42 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id OAA07853; Sun, 27 Aug 2000 14:43:49 -0400 (EDT) From: "Clarence Brown" To: "'Alfred Perlstein'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 14:03:53 -0400 Message-ID: <003601c01051$2a05ea40$8c6896d1@granitepost.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20000827095200.A1209@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > Behalf Of Alfred Perlstein > * 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. > I booted the machine with power up, logged in as root, did "shutdown -h now", hit space to reboot. During the countdown I hit "space" then at the "ok" prompt? I typed "boot -v [ENTER]" More info DID scroll by before the hang, but I didn't see any difference in the output at the point of the hang. The last 3 lines were the same as without the "boot -v": npx0: on motherboard npx0: INT16 interface isa0: on motherboard I don't think the "npx0:" lines are related to the "isa0:" line. At this point the machine appears locked up. No disk or other observable activity. If I had to guess from my HW design experience I'd say there's an obscure register somewhere that the firmware initializes properly on a hardware boot, but that is missed by the software reset. This would seem to be fixable by simply isolating the register(s) and adding their initialization to the code somewhere. Looks like I might have to figure out how to setup my system for kernel debug... Any other ideas before I start reading the kernel debug web pages ... I don't really want to have to figure out how to install and use a new (to me) compiler/debugger combo, not to mention getting all the source etc... I've got the 4 CD subscription set, is the source and all that on there somewhere? Don't tell me I also get to figure out how to use CVS at the same time . I really need to quite playing with this computer and finish putting the new floor joists where the bathroom is supposed to be... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message