From owner-freebsd-stable Tue May 26 08:04:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10041 for freebsd-stable-outgoing; Tue, 26 May 1998 08:04:06 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09880 for ; Tue, 26 May 1998 08:03:55 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA20466; Tue, 26 May 1998 09:02:27 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA05071; Tue, 26 May 1998 09:02:19 -0600 Date: Tue, 26 May 1998 09:02:19 -0600 Message-Id: <199805261502.JAA05071@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver In-Reply-To: <199805261243.FAA00386@antipodes.cdrom.com> References: <199805261023.SAA11951@public.bta.net.cn> <199805261243.FAA00386@antipodes.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk > > >> 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message