Date: Tue, 26 May 1998 09:02:19 -0600 From: Nate Williams <nate@mt.sri.com> To: Mike Smith <mike@smith.net.au> Cc: Michael Robinson <robinson@public.bta.net.cn>, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver Message-ID: <199805261502.JAA05071@mt.sri.com> In-Reply-To: <199805261243.FAA00386@antipodes.cdrom.com> References: <199805261023.SAA11951@public.bta.net.cn> <199805261243.FAA00386@antipodes.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805261502.JAA05071>