Date: Mon, 16 Oct 2000 11:04:08 +0300 From: Dennis Melentyev <dennis@mebius-kb.kiev.ua> To: freebsd-stable@FreeBSD.ORG Cc: Andy <deimos@lewman.com> Subject: Re: ata timeouts in 4.1-stable? Message-ID: <20001016110407.A5565@mebius-kb.kiev.ua> In-Reply-To: <Pine.BSF.4.21.0010132033480.460-100000@lowrider.lewman.org>; from deimos@lewman.com on Fri, Oct 13, 2000 at 08:48:44PM -0400 References: <Pine.BSF.4.21.0010132033480.460-100000@lowrider.lewman.org>
next in thread | previous in thread | raw e-mail | index | archive | help
IMHO problem may be within with your CD-DRIVE. I has such a problem with
SAMSUNG 24xCD until I haven't pull it out and throw away. It can work
normally ONLY as a single drive on the controller.
BTW it's "IMHO" ;)
On Fri, Oct 13, 2000 at 08:48:44PM -0400, Andy wrote:
> I'm using fbsd 4.1-stable, last cvsup and make world was
> 2000-09-24. Everything looked fine until I added another ide drive, as
> secondary slave, to the primary master. I did check the archives first,
> and what I found was that people have reported this problem with ATA-66
> controllers, not ATA-33. I now get log warnings such as:
>
> Oct 13 19:29:30 lowrider /kernel: ad2: WRITE command timeout - resetting
> Oct 13 19:29:30 lowrider /kernel: ata1: resetting devices .. done
> Oct 13 19:29:40 lowrider /kernel: ad2: WRITE command timeout - resetting
> Oct 13 19:29:50 lowrider /kernel: ata1: resetting devices .. done
> Oct 13 19:30:11 lowrider /kernel: ad2: WRITE command timeout - resetting
> Oct 13 19:30:11 lowrider /kernel: ata1: resetting devices .. done
> Oct 13 19:30:11 lowrider /kernel: ad2: WRITE command timeout - resetting
> Oct 13 19:30:11 lowrider /kernel: ata1: resetting devices .. done
> Oct 13 19:30:11 lowrider /kernel: ad2: WRITE command timeout - resetting
> Oct 13 19:30:11 lowrider /kernel: ata1-master: WARNING: WAIT_READY
> active=ATA_ACTIVE_ATA
> Oct 13 19:30:11 lowrider /kernel: ad2: trying fallback to PIO mode
> Oct 13 19:30:11 lowrider /kernel: ata1: resetting devices .. done
>
> My controller is:
>
> Oct 11 22:51:53 lowrider /kernel: atapci0: <Intel PIIX4 ATA33 controller>
> port 0xf000-0xf00f at device 7.1 on pci0
> Oct 11 22:51:53 lowrider /kernel: ata0: at 0x1f0 irq 14 on atapci0
> Oct 11 22:51:53 lowrider /kernel: ata1: at 0x170 irq 15 on atapci0
>
> and my disks are:
>
> Oct 11 22:51:54 lowrider /kernel: ad0: 5006MB <FUJITSU MPB3052ATU>
> [10850/15/63] at ata0-master using UDMA33
> Oct 11 22:51:54 lowrider /kernel: ad2: 4134MB <QUANTUM BIGFOOT_CY4320A>
> [8960/15/63] at ata1-master using WDMA2
> Oct 11 22:51:54 lowrider /kernel: acd0: CDROM <FX240S> at ata0-slave using
> PIO3
>
>
> The errors above occur during the dump of an fs, the creation of a large
> tarball, or nightly run jobs that involve ad2. The actual disk in ad2
> came out of a 3.5-stable system that ran without these errors. The disk
> appears to be fine, as I've put it back into the old system, and dumped
> the /usr fs to a tarball on it.
>
> These errors don't appear to be affecting the end result, as the tarballs,
> and dump files are still valid, but I'm wondering if these are cause for
> concern. Or if I should add this to a PR?
>
>
> --
>
> | Andy | e-mail | web |
> | | andy@lewman.com | www.lewman.com |
>
> ... If forced to travel on an airplane, try and get in the cabin with
> the Captain, so you can keep an eye on him and nudge him if he falls
> asleep or point out any mountains looming up ahead ...
> -- Mike Harding, "The Armchair Anarchist's Almanac"
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
--
Dennis Melentyev
C/C++ programmer @ Mebius-KB, Kiev, Ukraine
dennis@mebius-kb.kiev.ua
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?20001016110407.A5565>