Date: Tue, 07 Dec 2004 09:56:38 +0100 From: Jimmy Selgen <spamtrap1@devlix.dk> To: Garance A Drosihn <drosih@rpi.edu> Cc: Christopher Vance <christopher@nu.org> Subject: Re: ad0: FAILURE - WRITE_DMA Message-ID: <1102409798.5240.6.camel@localhost.localdomain> In-Reply-To: <p06200755bddafda88af3@[128.113.24.47]> References: <200410081937.15068.miha@ghuug.org> <200410291657.33606.miha@ghuug.org> <4182BD51.6070800@freebsdbrasil.com.br> <p06200755bddafda88af3@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2004-12-07 at 01:38 -0500, Garance A Drosihn wrote: > At 3:47 PM +1100 12/7/04, Christopher Vance wrote: > >I gave up with 5.3 on my SiI3512A with Seagate SATA disks because of > >this (mine was not only TIMEOUT, but also FAILURE) and related panics. I too have been getting TIMEOUT and FAILURE messages with 5.3. Hardware works perfect with 5.2.1, but somewhere around 5.3-BETA7 i started getting FAILURE messages on one of my disks when it returns from powersave/spin down. When trying to access the mounted device after a TIMEOUT i get "Bad file descriptor", and then on a following reboot i get a panic after i finishes syncing disks, like "vlere, negative ref count" or something. setting hw.ata.ata_dma = 0 didn't help. i just got READ_MUL TIMEOUT instead. I tried reinstalling 5.2.1 and it works like a dream there. I already sent my info to sos@, so i'm just sounding off to let you know you're not alone :) /Jimmy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1102409798.5240.6.camel>