Date: Sun, 19 Jun 2005 20:04:11 -0500 From: twesky <twesky@gmail.com> To: Martin <nakal@nurfuerspam.de> Cc: freebsd-stable@freebsd.org Subject: Re: ATA_DMA errors (and fs corruption!) Message-ID: <8d02aed005061918049c8fd8@mail.gmail.com> In-Reply-To: <42B5DAEA.4040908@nurfuerspam.de> References: <8d02aed00506181404642100b9@mail.gmail.com> <42B5DAEA.4040908@nurfuerspam.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Here is my controller: atapci0: <Intel ICH4 UDMA100 controller> port 0x1860-0x186f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 The last known good stable version for me was aprox April 25, my next cvsup was May 17, but I have problems with 5.4 Release so I assume (probably incorrectly) that something changed between April 25 and 5.4R. I don't exactly recall my shutdown errors, but I did have to restore my file systems to get my laptop back to a functioning state. On 6/19/05, Martin <nakal@nurfuerspam.de> wrote: > twesky wrote: > > I am having ATA_DMA errors on 5.4R and 5 STABLE up to June 16 (haven't > > done a cvsup again). It doesn't happen on 5.3R or lower. >=20 > I have got same problem. I tried yesterday's kernel and I got lots of > ATA DMA errors. A question: do you have a VIA IDE controller like mine? >=20 > atapci0: <VIA 8235 UDMA133 controller> port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 >=20 > atapci0@pci0:17:1: class=3D0x01018a card=3D0x05711849 chip=3D0x05711= 106 > rev=3D0x06 hdr=3D0x00 > vendor =3D 'VIA Technologies Inc' > device =3D 'VT82xxxx EIDE Controller (All VIA Chipsets)' > class =3D mass storage > subclass =3D ATA >=20 > Today, I noticed, the short experiment with the latest -STABLE destroyed > a part of my /usr partition. It looked like this (with May 9th kernel > today): >=20 > kernel: handle_workitem_freeblocks: block count > kernel: bad block 50333952, ino 1743780 > kernel: pid 56 (syncer), uid 0 inumber 1743780 on /usr: bad block > kernel: bad block 3221252091, ino 1743780 > klotz kernel: pid 56 (syncer), uid 0 inumber 1743780 on /usr: bad block > kernel: bad block 144119931884736777, ino 1743780 > kernel: pid 56 (syncer), uid 0 inumber 1743780 on /usr: bad block > kernel: bad block 72340173158093844, ino 1743780 > kernel: pid 56 (syncer), uid 0 inumber 1743780 on /usr: bad block > kernel: bad block 1104111992832, ino 1743780 > kernel: pid 56 (syncer), uid 0 inumber 1743780 on /usr: bad block > kernel: handle_workitem_freeblocks: block count > kernel: handle_workitem_freeblocks: block count > kernel: bad block 1865342872522620032, ino 1743783 >=20 > While shutting down I got this: >=20 > Jun 19 22:04:21 klotz kernel: /usr: unmount pending error: blocks > -3561100369582 68157 files 0 >=20 > I restored the fs in single-user mode. And now it runs fine with > the kernel (May 9th). >=20 > See also my earlier post. >=20 > Martin >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d02aed005061918049c8fd8>