Re: PROBLEM: sata_sil24 lockups under heavy i/o

[Mark Wagner]

On Sun, Jan 07, 2007 at 03:27:03PM +0900, Tejun Heo wrote:

> Mark Wagner wrote:
> [--snip--]
> >NETDEV WATCHDOG: eth0: transmit timed out
> >eth0: transmit timed out, tx_status 00 status e000.
> [--snip--]
> >hda: DMA timeout error
> >hda: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
> >ide: failed opcode was: unknown
> >hda: status timeout: status=0xd0 { Busy }
> >ide: failed opcode was: unknown
> >hdb: DMA disabled
> >hda: no DRQ after issuing MULTWRITE_EXT
> >ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> >ata3.00: tag 0 cmd 0x60 Emask 0x4 stat 0x40 err 0x0 (timeout)
> >ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
> >ata4.00: tag 0 cmd 0x60 Emask 0x4 stat 0x40 err 0x0 (timeout)
> >ata4: hard resetting port
> >ata2.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen
> >ata2.00: tag 0 cmd 0x60 Emask 0x4 stat 0x40 err 0x0 (timeout)
> >ata2: hard resetting port
> >ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
> >ata1.00: tag 0 cmd 0x60 Emask 0x4 stat 0x40 err 0x0 (timeout)
> >ata1.00: tag 1 cmd 0x60 Emask 0x4 stat 0x40 err 0x0 (timeout)
> [--snip--]
> >i2c_adapter i2c-0: Transaction error!
> >i2c_adapter i2c-0: Transaction error!
> >i2c_adapter i2c-0: Transaction error!
> 
> It seems like your system is falling apart.  Timeouts are occurring 
> everywhere.  Either IRQ routing went wrong or your powersupply is not 
> providing enough power.  Adding two more disks to sil24 doesn't change 
> anything about IRQ routing.  If the system functioned okay w/ two disks 
> attached to sil24, give your system a better power supply or rewire 
> power cables such that each power lane is more equally loaded.

The sil24-connected sata drives are external and connected to their own
power supply.

I've replaced the sil24-based card with a Promise SATA300 TX4 controller
card and everything seems to work now.

Thanks,

Mark

-- 
Mark Wagner mark@xxxxxxxxxxx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/