Re: ata1 timeouts on 2.6.34-rc1

[Jeff Garzik]

On 03/10/2010 10:41 AM, Zeno Davatz wrote:
> Mar 10 13:30:01 zenogentoo cron[12528]: (root) CMD (test -x
> /usr/sbin/run-crons&&  /usr/sbin/run-crons )
> Mar 10 13:33:32 zenogentoo sudo:     zeno : TTY=pts/0 ; PWD=/home/zeno
> ; USER=root ; COMMAND=/usr/bin/emerge --sync
> Mar 10 13:33:48 zenogentoo ata1: clearing spurious IRQ
> Mar 10 13:34:19 zenogentoo ata1: lost interrupt (Status 0x50)
> Mar 10 13:34:19 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x6 frozen
> Mar 10 13:34:19 zenogentoo ata1.00: failed command: READ DMA
> Mar 10 13:34:19 zenogentoo ata1.00: cmd
> c8/00:08:d5:20:cb/00:00:00:00:00/e9 tag 0 dma 4096 in
> Mar 10 13:34:19 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00
> Emask 0x4 (timeout)
> Mar 10 13:34:19 zenogentoo ata1.00: status: { DRDY }
> Mar 10 13:34:19 zenogentoo ata1: soft resetting link
> Mar 10 13:34:19 zenogentoo ata1.00: configured for UDMA/133
> Mar 10 13:34:19 zenogentoo ata1.00: device reported invalid CHS sector 0
> Mar 10 13:34:19 zenogentoo ata1: EH complete
> Mar 10 13:35:55 zenogentoo ata1: clearing spurious IRQ
> Mar 10 13:36:26 zenogentoo ata1: lost interrupt (Status 0x50)
> Mar 10 13:36:26 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x6 frozen
> Mar 10 13:36:26 zenogentoo ata1.00: failed command: WRITE DMA
> Mar 10 13:36:26 zenogentoo ata1.00: cmd
> ca/00:10:1d:ad:52/00:00:00:00:00/e6 tag 0 dma 8192 out
> Mar 10 13:36:26 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00
> Emask 0x4 (timeout)
> Mar 10 13:36:26 zenogentoo ata1.00: status: { DRDY }
> Mar 10 13:36:26 zenogentoo ata1: soft resetting link
> Mar 10 13:36:26 zenogentoo ata1.00: configured for UDMA/133
> Mar 10 13:36:26 zenogentoo ata1.00: device reported invalid CHS sector 0
> Mar 10 13:36:26 zenogentoo ata1: EH complete
> Mar 10 13:40:01 zenogentoo cron[12707]: (root) CMD (test -x
> /usr/sbin/run-crons&&  /usr/sbin/run-crons )
> Mar 10 13:48:05 zenogentoo sudo:     zeno : TTY=pts/0 ; PWD=/home/zeno
> ; USER=root ; COMMAND=/usr/bin/emerge portage
> Mar 10 13:49:22 zenogentoo ata1: clearing spurious IRQ
> Mar 10 13:49:53 zenogentoo ata1: lost interrupt (Status 0x50)
> Mar 10 13:49:53 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x6 frozen
> Mar 10 13:49:53 zenogentoo ata1.00: failed command: WRITE DMA
> Mar 10 13:49:53 zenogentoo ata1.00: cmd
> ca/00:08:05:21:df/00:00:00:00:00/ef tag 0 dma 4096 out
> Mar 10 13:49:53 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00
> Emask 0x4 (timeout)
> Mar 10 13:49:53 zenogentoo ata1.00: status: { DRDY }
> Mar 10 13:49:53 zenogentoo ata1: soft resetting link
> Mar 10 13:49:53 zenogentoo ata1.00: configured for UDMA/133
> Mar 10 13:49:53 zenogentoo ata1.00: device reported invalid CHS sector 0
> Mar 10 13:49:53 zenogentoo ata1: EH complete
>
> Let me know if I can supply you with anymore information. Also see
> attached lspci-v file.


need full dmesg from boot, not just error snippet.

	Jeff

--
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/