Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!solace!news.stealth.net!nntp04.primenet.com!nntp.primenet.com!news.mathworks.com!newsfeed.internetmci.com!tyger.inna.net!usenet From: "Jordan K. Hubbard" <jkh@FreeBSD.org> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: can ccd(4) crash a hard drive? Date: Thu, 22 Aug 1996 22:47:59 -0700 Organization: Walnut Creek CDROM Lines: 11 Message-ID: <321D460F.446B9B3D@FreeBSD.org> References: <4vi8b3$nmt@ocean.silcom.com> <321CEBE7.41C67EA6@telstra.net> <321D44C0.167EB0E7@FreeBSD.org> NNTP-Posting-Host: time.cdrom.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-CURRENT i386) Jordan K. Hubbard wrote: > but not actually caused by it. Sig 11's point to bad memory or cache, > not the disk I/O subsystem at all. Actually, just to follow-up to myself here, I should point out that there actaully *are* situations were a misbehaving disk controller can cause Sig 11's too (by DMA'ing in bad data for an executable that's being paged in), but that doesn't appear likely in this case. --- - Jordan Hubbard President, FreeBSD Project