Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 May 2004 18:25:26 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: NFS or ATA driver causes FS corruption?
Message-ID:  <Pine.BSF.4.53.0405081806240.66978@e0-0.zab2.int.zabbadoz.net>
In-Reply-To: <4044297F.1080701@DeepCore.dk>
References:  <20040302031226.GA670@xor.obsecurity.org> <4044297F.1080701@DeepCore.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 1 Mar 2004, it was written:

Hi,

> Kris Kennaway wrote:
> > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=9440
> > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=20904
> > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=117560
> > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=206664
> > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=30312
>
> The above means that *something* is stomping on the taskqueue that
> should take care of returning finished requests to the system (they are
> finished as the interrupt has been seen). I can avoid this by putting it
> all back in interrupt context again as it was before, but it would be
> better to get whatever it is that causes this fixed..

I have just setup my new amd64 machine and started to copy srces of
HEAD over to it when it suddenly stopped responding (pings still worked).
Didn't use NFS but a tar pipe over ssh for some reason.

I am not yet on serial console so I went to the screen and got s.th.
like the above plus some

ad10: WARNING - WRITE_DMA interrupt was seen but taskqueue stalled LBA=...

from time to time;

the machine is running a 5.2.1 Release (as initial installation).

Is there any way to temporary disable s.th. so I can get a HEAD
srces copied, built and installed ?
would changing hw.ata.ata_dma=0 help ?
And is this problem already fix in HEAD at all ?


Some specs (if it helps):

atapci0: <Promise PDC20378 SATA150 controller> port 0xcc00-0xcc7f,0xdc00-0xdc0f,0xec00-0xec3f mem 0xf3a00000-0xf3a1ffff,0xf3b00000-0xf3b00fff irq 18 at device 8.0 on pci0

and

atapci1: <VIA 8237 SATA150 controller> port 0xd000-0xd0ff,0xd400-0xd40f,0xd800-0xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 20 at device 15.0 on pci0

both on board.


ad10: 156334MB <Maxtor 6Y160M0> [317632/16/63] at ata5-master UDMA100

the disk should be attached to the VIA controller.

-- 
Greetings

Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0405081806240.66978>