Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Dec 2003 09:53:48 -0600
From:      Kirk Strauser <kirk@strauser.com>
To:        current@freebsd.org
Subject:   Re: ATA + DMA still giving repeatable freezes
Message-ID:  <3FE31F0C.80808@strauser.com>
Resent-Message-ID: <200312192313.hBJNDbeq056851@kanga.honeypot.net>
In-Reply-To: <87fzfqy732.fsf@strauser.com>
References:  <87fzfqy732.fsf@strauser.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFC07A31A8040F45438679067
Content-Type: multipart/mixed;
 boundary="------------010309040601050007070600"

This is a multi-part message in MIME format.
--------------010309040601050007070600
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Kirk Strauser wrote:

> I built world after cvsup'ing -CURRENT this morning and am still having the
> same ATA READ_DMA hangs that started in early October on my system.  I can
> repeat the hangs at will; the machine serves as an Amanda server, and
> launching a backup for itself plus 3 client machines is guaranteed to
> trigger it:
> 
>     ad0: TIMEOUT - READ_DMA retrying (2 retries left)
>     ata0: resetting devices ..
>     ad0: FAILURE - already active DMA on this device
>     ad0: setting up DMA failed

Am I the only person seeing this?  I filed a PR but haven't heard
anything yet.

Additional information:

This happens whether or not I disable ACPI.

I've used atacontrol to select suboptimal drive modes, but still get the
crashes at anything higher than BIOSPIO.  To be explicit, I still get
the READ_DMA errors when the mode is set to PIO4.

I'm at my wits' end and ready to revert to 4.x, although I realize that
I'll eventually have to bring this server back to a 5.x install unless I
want to hang on to 4.9 or 4.10 forever.
-- 
Kirk Strauser


--------------010309040601050007070600
Content-Type: application/pgp-signature;
 name="file:///tmp/nsmail.pgp"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="file:///tmp/nsmail.pgp"

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuMi4zIChH
TlUvTGludXgpCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggVGh1bmRlcmJpcmQgLSBodHRw
Oi8vZW5pZ21haWwubW96ZGV2Lm9yZwoKaUQ4REJRRS80eDZyNXNSZytZMENwdkVSQXRiSUFL
Q09neC9iVFJlYk9xMHk2cVB4cDZOaTlyZU9YUUNmWVJOWgpWVS9UMUVlak9oV1lVSk43U25x
aTJEND0KPTZ3Q3MKLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tCgo=
--------------010309040601050007070600--

--------------enigFC07A31A8040F45438679067
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/4x8M5sRg+Y0CpvERAv3VAJ9ngnIpGNYAfIFrIBovQjHWL2JVvQCfQAHY
Iyp+PlBQDciDnpBXReAS0fw=
=DH4r
-----END PGP SIGNATURE-----

--------------enigFC07A31A8040F45438679067--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FE31F0C.80808>