Date: Wed, 13 Jan 1999 10:51:52 -0500 From: Lee Cremeans <lee@st-lcremean.tidalwave.net> To: "Joseph T. Lee" <nugundam@la.best.com>, Andrew Atrens <atrens@nortelnetworks.com>, freebsd-current@FreeBSD.ORG Subject: Re: potential ide_pci.c bugster Message-ID: <19990113105152.A5109@tidalwave.net> In-Reply-To: <19990113021908.A11598@la.best.com>; from Joseph T. Lee on Wed, Jan 13, 1999 at 02:19:08AM -0800 References: <19990112004945.A68879@tidalwave.net> <Pine.BSF.4.05.9901121615040.600-100000@hcarp00g.ca.nortel.com> <19990113021908.A11598@la.best.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa > wdc1: unit 0 (wd2): <QUANTUM MAVERICK 270A>, LBA, 32-bit, multi-block-8, sleep-hack > wd2: 258MB (528640 sectors), 524 cyls, 16 heads, 63 S/T, 512 B/S > > wd2: interrupt timeout (status 58<rdy,seekdone,drq> error 1<no_dam>) > wd2: wdtimeout() DMA status 4 > > -current as of 10th. Error pops up once in a while with or without > softupdates. I use it for /usr/src so nothing vital on it..yet. This drive is too old to support even multiword 2 DMA. If you're getting timeouts, and they seem to only happen when accessing certain files or areas, then your drive has some bad-but-not-totally-dead sectors on it, and the drive electronics are being slow about correcting the error. This is becoming a FAQ, I think... -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990113105152.A5109>