SATA DMA errors

From: <andrew_terekhov_at_yahoo.com>
Date: Fri, 7 Sep 2007 13:59:14 -0700 (PDT)
Current kernel/world (i386) from a few days ago on 2 different computers exhibits DMA read/write 
errors when accessing SATA drives. IDE drives work fine.

Errors are similar to described here:

http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076776.html
http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076699.html
http://lists.freebsd.org/pipermail/freebsd-questions/2007-August/156029.html

After a few DMA errors both systems usually hard lockup.

I took advice found here:

http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076219.html

and rebuilt both systems with 

*date=2007.06.16.03.00.00

The problem was gone - running for the second day with heavy use of SATA drives with no errors. 
Before it took a few minutes to bring down computers.


Hardware:

System 1:

atapci1: <SiS 180 SATA150 controller> port 0xe300-0xe307,0xe400-0xe403,0xe500-0xe507,0xe600-0xe603,0xe700-0xe70f irq 11 at device 5.0 on pci0
ad4: 305245MB <MAXTOR STM3320620AS 3.AAE> at ata2-master SATA150


System 2:

atapci2: <Promise PDC40779 SATA300 controller> port 0xcc00-0xcc7f,0xc800-0xc8ff mem 0xfeaff000-0xfeafffff,0xfeac0000-0xfeadffff irq 16 at device 3.0 on pci5
ad8: 194481MB <Maxtor 6L200M0 BACE1G10> at ata4-master SATA150
ad10: 286168MB <Seagate ST3300622AS 3.AAH> at ata5-master SATA300


It seems something was changed after 2007-06-16 that broke SATA in current.





       
____________________________________________________________________________________
Yahoo! oneSearch: Finally, mobile search 
that gives answers, not web links. 
http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
Received on Fri Sep 07 2007 - 19:25:55 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:17 UTC