Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uwm.edu!spool.mu.edu!agate!reason.cdrom.com!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Strange Crash Date: 27 Aug 1995 16:20:38 GMT Organization: Walnut Creek CDROM Lines: 21 Message-ID: <41q60m$p3u@reason.cdrom.com> References: <DDywqs.Jo9@ritz.mordor.com> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 1.1N (X11; I; FreeBSD 2.2-CURRENT i386) To: ritz@ritz.mordor.com X-URL: news:DDywqs.Jo9@ritz.mordor.com ritz@ritz.mordor.com (Chris Mauritz) wrote: >Anyone seen this before? > >Aug 26 15:08:20 sauron /kernel: bt0: Try to abort >Aug 26 15:08:39 sauron /kernel: bt0: Try to abort >Aug 26 15:08:41 sauron /kernel: bt0: Abort Operation has timed out >Aug 26 15:08:42 sauron /kernel: biodone: buffer already done Yeah, I have.. I used to have a drive that would, very occasionally, just decide that it was having an attack of existential angst and needed to spin down for awhile. When this would happen, FreeBSD would notice its last operation go astray, try to abort it, time out on the abort (because the device was offline, not stuck) and then proceed to go to pieces over it. Bad error checking (or more simply a lack thereof) in the SCSI driver is the real culprit. It's better to have your hardware work, of course, but FreeBSD still shouldn't have kittens when it stops in recoverable ways.. Bug stompers in the SCSI code are always welcome! :) Jordan