Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

[Michael Madore]

Hi,

I am seeing the same problem on a SuperMicro X5DAE motherboard (E7505) 
with an SIIG Serial ATA adapter card.  This also uses the 3112 chip.

Mike Madore

Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

[lk]

>>while. The following errors were displayed on the console:
>>
>>    hde: dma_timer_expiry: dma_status == 0x21
>>    hde: timeout waiting for DMA

> On Saturday I tried a Seagate 120GiB SATA with my onboard SiI3112 on
> my ASUS P4G8X (with an Intel 7205 chipset). I suppose that David is

I am seeing the same problems with SiI3112 chipset adapters in a 
Supermicro motherboard with 7501 chipset.

I get the DMA timeouts after merely enabling DMA with hdparm- I never even 
get a chance to write anything to disk.

> somehow related to this chipset: I saw the exact same errors as David.
> I also tried several kernels: 2.4.20-ac2, 2.4.20-pre5-ac3, 2.4.20-pre7,
> 2.5.66, 2.4.20-8 from Redhat 9, ... with exactly the same result.

Same here.  I haven't seen DMA working with this chip yet.

Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

[Troy Rollo]

"Me too" - when I enable DMA it's not long before the system stops 
responding altogether. Without DMA, I get a data read rate of about 800KBps.

But also, I have two identical drives attached - hda and hde (both 
ST380023AS). Even if I don't turn on DMA, if I am using both fairly 
intensively at the same time (at least that's the only thing I can identify 
as an apparent common difference), one will (on random occasions) start 
returning errors for every access. If this happens to be the drive that the 
operating system is installed on, the result is somewhat fatal. If it's the 
other drive I can continue, but any attempt to access it fails. There are 
some syslog entries that appear to relate to this:

Apr 11 07:42:49 milat kernel: hde: status timeout: status=0xd0 { Busy }
Apr 11 07:42:49 milat kernel:
Apr 11 07:42:49 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset
Apr 11 07:42:49 milat kernel: hde: no DRQ after issuing WRITE
Apr 11 07:43:19 milat kernel: ide2: reset timed-out, status=0xd8
Apr 11 07:43:20 milat kernel: hde: status timeout: status=0xd8 { Busy }
Apr 11 07:43:20 milat kernel:
Apr 11 07:43:20 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset
Apr 11 07:43:20 milat kernel: hde: drive not ready for command
Apr 11 07:43:51 milat kernel: t: I/O error, dev 21:02 (hde), sector 6183724
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
sector 6183726
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
sector 6183728
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
sector 6183730
Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
sector 6183732
...

Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

[Andre Hedrick]

Gurr!!!!!!!

These drives were not to make it to market in the commom purchase
marketspace!

This is not a fun one to fix!

This is all I can say for now :-(

On Sat, 12 Apr 2003, Troy Rollo wrote:

> "Me too" - when I enable DMA it's not long before the system stops 
> responding altogether. Without DMA, I get a data read rate of about 800KBps.
> 
> But also, I have two identical drives attached - hda and hde (both 
> ST380023AS). Even if I don't turn on DMA, if I am using both fairly 
> intensively at the same time (at least that's the only thing I can identify 
> as an apparent common difference), one will (on random occasions) start 
> returning errors for every access. If this happens to be the drive that the 
> operating system is installed on, the result is somewhat fatal. If it's the 
> other drive I can continue, but any attempt to access it fails. There are 
> some syslog entries that appear to relate to this:
> 
> Apr 11 07:42:49 milat kernel: hde: status timeout: status=0xd0 { Busy }
> Apr 11 07:42:49 milat kernel:
> Apr 11 07:42:49 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset
> Apr 11 07:42:49 milat kernel: hde: no DRQ after issuing WRITE
> Apr 11 07:43:19 milat kernel: ide2: reset timed-out, status=0xd8
> Apr 11 07:43:20 milat kernel: hde: status timeout: status=0xd8 { Busy }
> Apr 11 07:43:20 milat kernel:
> Apr 11 07:43:20 milat kernel: ide2: reset phy, status=0x00000113, siimage_reset
> Apr 11 07:43:20 milat kernel: hde: drive not ready for command
> Apr 11 07:43:51 milat kernel: t: I/O error, dev 21:02 (hde), sector 6183724
> Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
> sector 6183726
> Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
> sector 6183728
> Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
> sector 6183730
> Apr 11 07:43:51 milat kernel: end_request: I/O error, dev 21:02 (hde), 
> sector 6183732
> ...
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Andre Hedrick
LAD Storage Consulting Group

Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

[Joshua Penix]

On Saturday 12 April 2003 01:06 am, Andre Hedrick wrote:
> Gurr!!!!!!!
>
> These drives were not to make it to market in the commom purchase
> marketspace!

Do you mean to say that the problem lies in the Seagate drives, not in the SiI 
3112 controller and/or its driver code?

I'm seeing SATA as a common component on quite a few motherboards, and am 
definitely seeing SATA drives in the retail channel.  In my experience, all 
of these pieces work flawlessly under Win2k and XP... would love for them to 
do the same under Linux.

> This is not a fun one to fix!
>
> This is all I can say for now :-(

Why no fun?  Why can't you say more?  We would really appreciate more 
specifics when you can.  If the problem lies with Seagate, I'd be happy to 
press the issue with them.

--Josh

DMA Timeouts with 3112 SATA Controller (status == 0x21)

[David Tymon]

Hi,

I am in the process of trying to setup a Dual Xeon machine with a Silicon
Image 3112 SATA controller. The system is booting from a parallel ATA disk and
there are two SATA disks being used to store data.

I was able to access the SATA drives, both in a raid0 and non-raid
configuration, using the driver (sii3112rl.o) with the machine. This module
was compiled for a uni-processor RH8.0 kernel (2.8.18-14). We were getting
transfer rates of around 40MB/s in non-raid and 80MB/s in raid0. There was no
SMP version of the module supplied so it was kind of useless to us.

So, I tried a 2.4.21-pre6 kernel (SMP with hyperthreading). The 3112
controller was identified at boot and I was able to access the disks. However,
hdparm was reporting very poor transfer rates, around 1.8MB/s. It turned out
that DMA was not enabled on the disks. When I enabled DMA I got back to a
transfer rate around 40MB/s. I set the transfer mode to udma6.

Then I tried to make an ext3 filesystem. mkfs would get up to around the 240th
inode table (ie: "Writing inode tables: 240/xyz") and then freeze up for a
while. The following errors were displayed on the console:

    hde: dma_timer_expiry: dma_status == 0x21
    hde: timeout waiting for DMA
    hde: timeout waiting for DMA
    hde: status timeout: status = 0xd8 {Busy}
    hde: drive not ready for command
    ide2: reset phy status=0x00000113 siimage_reset
    ide2: reset timed-out, status=0xd8
    hde: status timeout: status = 0xd8 {Busy}
    hde: drive not ready for command
    ide2: reset phy status=0x00000113 siimage_reset
    ide2: reset timed-out, status=0xd8

followed by loads of IO errors. After this, the disk was uncontactable. I
thought the problem might be with udma6 so I tried all of them but with the
same problems. I also tried 2.5.66 and a RedHat 2.4.20-2.54 kernel but these
had the same problems. If I turned DMA off I was able to make a filesystem
(although very slowly). I was also able to make a filesystem using the
original supplied driver.

The timeouts also occurred if I used the silraid module and accessed the disks
via /dev/ataraid/d0.

I could swap the drives for parallel ATA ones but would rather get the SATA
ones working if possible. I recall reading a message from Andre containing
performance details about a 3112 controller and Linux raid 1, so I presume
that it is possible to get this configuration going and it is just that I am a
doofus.

Here is some info on the machine:

# lspci
00:00.0 Host bridge: Intel Corp.: Unknown device 2550 (rev 03)
00:00.1 Class ff00: Intel Corp.: Unknown device 2551 (rev 03)
00:01.0 PCI bridge: Intel Corp.: Unknown device 2552 (rev 03)
00:02.0 PCI bridge: Intel Corp.: Unknown device 2553 (rev 03)
00:02.1 Class ff00: Intel Corp.: Unknown device 2554 (rev 03)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 02)
00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 02)
02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
04:02.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
05:02.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
05:03.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0d)
05:04.0 Unknown mass storage controller: CMD Technology Inc: Unknown device 3112 (rev 02)

# hdparm -i /dev/hde
/dev/hde:
 Model=ST3120023AS, FwRev=3.01, SerialNo=3KA1MN43
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=234441648
 IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: ATA/ATAPI-6 T13 1410D revision 2:  1 2 3 4 5 6

# hdparm -I /dev/hde
/dev/hde:
ATA device, with non-removable media
        Model Number:       ST3120023AS                             
        Serial Number:      3KA1MN43            
        Firmware Revision:  3.01    
Standards:
        Used: ATA/ATAPI-6 T13 1410D revision 2 
        Supported: 6 5 4 3 
Configuration:
        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        --
        CHS current addressable sectors:   16514064
        LBA    user addressable sectors:  234441648
        device size with M = 1024*1024:      114473 MBytes
        device size with M = 1000*1000:      120034 MBytes (120 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 4      Queue depth: 1
        Standby timer values: spec'd by Standard
        R/W multiple sector transfer: Max = 16  Current = 16
        Recommended acoustic management value: 128, current value: 0
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4 
             Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           *    READ BUFFER cmd
           *    WRITE BUFFER cmd
           *    Host Protected Area feature set
           *    Look-ahead
           *    Write cache
           *    Power Management feature set
                Security Mode feature set
           *    SMART feature set
           *    Mandatory FLUSH CACHE command 
           *    Device Configuration Overlay feature set 
                Automatic Acoustic Management feature set 
                SET MAX security extension
           *    DOWNLOAD MICROCODE cmd
           *    SMART self-test 
           *    SMART error logging 
Security: 
                supported
        not     enabled
        not     locked
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
HW reset results:
        CBLID- above Vih
        Device num = 0
Checksum: correct

# smartctl -v /dev/hde
Vendor Specific SMART Attributes with Thresholds:
Revision Number: 10
Attribute                    Flag     Value Worst Threshold Raw Value
(  1)Raw Read Error Rate     0x000f   066   060   034       0000083fe871
(  3)Spin Up Time            0x0003   100   100   000       000000000000
(  4)Start Stop Count        0x0032   100   100   020       000000000000
(  5)Reallocated Sector Ct   0x0033   100   100   036       000000000000
(  7)Seek Error Rate         0x000f   070   060   030       000000a93dad
(  9)Power On Hours          0x0032   100   100   000       0000000000ed
( 10)Spin Retry Count        0x0013   100   100   097       000000000000
( 12)Power Cycle Count       0x0032   100   100   020       000000000047
(194)Unknown Attribute       0x0022   036   051   000       000000000024
(195)Unknown Attribute       0x001a   066   060   000       0000083fe871
(197)Current Pending Sector  0x0012   100   100   000       000000000000
(198)Offline Uncorrectable   0x0010   100   100   000       000000000000
(199)UDMA CRC Error Count    0x003e   200   200   000       000000000000
(200)Unknown Attribute       0x0000   100   253   000       000000000000
(202)Unknown Attribute       0x0032   100   253   000       000000000000


Any help would be most appreciated.

Thanks
David
-- 
David Tymon
Senior Software Engineer               mailto:David.Tymon@safehouse.com.au
Safehouse International                        http://www.safehouse.com.au
Tel: +61 3 9827 5411 Fax: +61 3 9827 7411

Re: DMA Timeouts with 3112 SATA Controller (status == 0x21)

[Martin Aumueller]

Hi *,

On Saturday I tried a Seagate 120GiB SATA with my onboard SiI3112 on
my ASUS P4G8X (with an Intel 7205 chipset). I suppose that David is
using a similiar setup with an 7505 chipset? Perhaps the problem is
somehow related to this chipset: I saw the exact same errors as David.
I also tried several kernels: 2.4.20-ac2, 2.4.20-pre5-ac3, 2.4.20-pre7,
2.5.66, 2.4.20-8 from Redhat 9, ... with exactly the same result.

Martin