From owner-freebsd-hackers Sun Aug 27 11: 2: 6 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 561DE37B423 for ; Sun, 27 Aug 2000 11:01:58 -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 OAA07866; Sun, 27 Aug 2000 14:46:04 -0400 (EDT) From: "Clarence Brown" To: "'Blaz Zupan'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 14:06:08 -0400 Message-ID: <003701c01051$7a44d2a0$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: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. > This is after the install ... Don't know how I could unplug the hard disk, while it's booting from the same hard disk ... It IS a Western Digital Caviar AC22000 drive. I might be able to dig up an even older Seagate for a test install. I've never had to mess with the kernel before, generic always worked ... "userconfig"? I'll look it up. How do I make it use the WD driver? Will that affect the IDE CDROM? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message