unexpected softupdate inconsistency

Torfinn Ingolfsen torfinn.ingolfsen at broadpark.no
Thu Mar 11 08:49:13 PST 2004


On Thu, 11 Mar 2004 06:28:59 +0100
Manfred Lotz <manfred.lotz at web.de> wrote:

> atapci0: <SiS 5591 ATA100 controller> port 0x4000-0x400f at device 2.5
> on pci0
> 
> That's the controller where it happened to me. Is it also known to
> cause data corruption when used in DMA mode?

I see from your earlier post that your are running FrreeBSD 4.9.
What hardware exactly is it that you have?
I have a Shuttle SS51G, and there is a known "problem" with the ata controller on that machine.
See  http://geekinfo.net/article.php?story=20021229152603904
and PR 43345: http://www.freebsd.org/cgi/query-pr.cgi?pr=43345

Note: the patch there is _not_ the right solution. It works for me, but
I think this is just because I have a udma66 disk:
user at kg-work$ uname -a
FreeBSD kg-work.kg4.no 4.9-STABLE FreeBSD 4.9-STABLE #7: Sat Dec 13
17:10:15 CET 2003     root at kg-work.kg4.no:/usr/obj/usr/src/sys/SS51 
i386
user at kg-work$ dmesg | grep atapci
atapci0: <SiS 5591 ATA100 controller> port
0x4000-0x400f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 irq 11 at
device 2.5 on pci0

user at kg-work$ dmesg | grep ad0
ad0: 19470MB <IBM-DJNA-352030> [39560/16/63] at ata0-master UDMA66


Hope this helps.
-- 
Torfinn Ingolfsen,
Norway



More information about the freebsd-stable mailing list