linux-kernel - Re: PROBLEM: sata_sil24 lockups under heavy i/o

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45A092B7.4070301@gmail.com>
Date:	Sun, 07 Jan 2007 15:27:03 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Mark Wagner <mark@...fear.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: sata_sil24 lockups under heavy i/o

Hello,

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.

-- 
tejun

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