Date: Wed, 16 Aug 2006 10:51:37 -0500 From: Vlad <marchenko@gmail.com> To: "James Seward" <jamesoff@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: 6.1-RELEASE: TIMEOUT - WRITE_DMA retrying Message-ID: <cd70c6810608160851x6c807f25r84373e02c2480e9c@mail.gmail.com> In-Reply-To: <720051dc0608160830l1ab00117oa96c9ebf534f8e2a@mail.gmail.com> References: <cd70c6810608160825u2b55103ey240ce0e803725c42@mail.gmail.com> <720051dc0608160830l1ab00117oa96c9ebf534f8e2a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I just got the message it panics with: ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=380273047 ad4: FAILURE - WRITE_DMA48 status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=380273047 g_vfs_done():ad4s1a[WRITE(offset=194699767808, length=2048)]error = 5 panic: newdirrem: not ATTACHED Also, you maybe very right about conflict with other hardware - it seemed to me that it's much less stable when intense HD operation is combined with network activity (i.e. downloading file via samba). I've tried to copy 3gig of archives over the net and I could not copy it after 3 attempts. Same time I've un-tarred those files locally on that server successfully after my 1st attempt. Any recommendations on what ~ 30 buck SATA card works OK with 6.1? I may opt out to take this one back and replace, unless someone willing to nail this down - I'm open for tests... On 8/16/06, James Seward <jamesoff@gmail.com> wrote: > On 8/16/06, Vlad <marchenko@gmail.com> wrote: > > I get this type of messages in on my FreeBSD. > > ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=70938623 > > Under steady IO load it panics, that started when we changed SATA > > controller (FreeBSD detects it as SiI 3512). I've tried to switch > > ports, cable, move card into a different PCI slot, disable ata dma in > > /boot/loader.conf - nothing helps. > > I had similar problems under 5.x and 6.x with a SI3112. My testing and > investigations back then suggested that some combinations of hardware > and the SI3112 just "don't get along" and I solved it by getting rid > of it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cd70c6810608160851x6c807f25r84373e02c2480e9c>