From owner-freebsd-stable Tue May 26 14:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29603 for freebsd-stable-outgoing; Tue, 26 May 1998 14:54:32 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from apollo.ptway.com (apollo.ptway.com [199.176.148.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29490 for ; Tue, 26 May 1998 14:54:12 -0700 (PDT) (envelope-from haskin@ptway.com) Received: from brianjr (210R1.infinitecom.com [199.176.148.77] (may be forged)) by apollo.ptway.com (8.8.7/8.8.7) with SMTP id QAA13736; Tue, 26 May 1998 16:56:51 -0400 Message-ID: <003901bd88f0$d7250ca0$0b00000a@brianjr.haskin.org> From: "Brian Haskin" To: Cc: "Michael Robinson" Subject: Re: Bug in wd driver Date: Tue, 26 May 1998 17:54:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk -----Original Message----- From: Nate Williams To: Mike Smith Cc: Michael Robinson ; freebsd-stable@FreeBSD.ORG Date: Tuesday, May 26, 1998 12:09 PM Subject: Re: Bug in wd driver >> > >> I wrote a message related to this problem to freebsd-questions >> > >> yesterday, but upon further investigation, I have decided this is >> > >> a bug, not a feature. >> > > >> > >Actually, it's almost certainly a hardware fault. >> > >> > Actually, the bug is that the driver does not recover gracefully from a >> > recoverable hardware fault. It instead goes into an infinite loop, taking >> > significant pieces of the kernel with it. >> >> Actually, an interrupt timeout is not a "recoverable hardware fault". > >Sure it is. You're being silly now Mike, this is indeed a 'bug' in the >driver, but it's probably not one that's going to be fixed unless the >submitter fixes it himself. Fixing it is non-trivial but possible to >do. > >Having a bad spot on a disk shouldn't make the disk *totally* unusable, >as every other 'significant' OS can deal with fine. > >This is also why I was w/out a laptop for 5 months, since our driver >couldn't get past the bad sector on the boot partition when it went bad >and everytime fsck tried to read it it locked up the computer. :( > Nate, I think what Mike is saying is that at least in this case the bad spot doesn't seem to be the real problem. The problem appears to be that the disk firmware is crashing, which is certainly an unrecoverable error. Brian Haskin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message