ata1 timeouts on 2.6.34-rc1
I am on 2.6.34-r1 and I get the same ATA timeouts as Linus gets here:
http://lkml.org/lkml/2010/3/9/345
ata1: clearing spurious IRQ
ata1: lost interrupt (Status 0x50)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: failed command: WRITE DMA
ata1.00: cmd ca/00:08:75:98:89/00:00:00:00:00/e3 tag 0 dma 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
ata1: clearing spurious IRQ
ata1: lost interrupt (Status 0x50)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:5d:ba:7b/00:00:00:00:00/e4 tag 0 dma 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
ata1: clearing spurious IRQ
ata1: lost interrupt (Status 0x50)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:7d:7b:7d/00:00:00:00:00/e4 tag 0 dma 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
ata1: clearing spurious IRQ
ata1: lost interrupt (Status 0x50)
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:00:1d:a2:68/00:00:00:00:00/ea tag 0 dma 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: soft resetting link
ata1.00: configured for UDMA/133
ata1.00: device reported invalid CHS sector 0
ata1: EH complete
I am also on an Intel SSD (160 GB). Every timeout blocks my PC for some seconds.
Best
Zeno
Quoted 1 line · Zeno Davatz
I am also on an Intel SSD (160 GB). Every timeout blocks my PC for some seconds.
PLEASE provide full information standard to any bug report. Just posting that you have a timeout tells us nothing about the hardware involved.
lspci and full dmesg output is needed, at a minimum.
Jeff
Quoted 10 lines · Jeff Garzik
Quoted 3 lines · Zeno Davatz
I am also on an Intel SSD (160 GB). Every timeout blocks my PC for some seconds.
PLEASE provide full information standard to any bug report. Just posting that you have a timeout tells us nothing about the hardware involved.
lspci and full dmesg output is needed, at a minimum.
lspci:
00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory Controller Hub (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 0e)
00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 05)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 05)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 05)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 05)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 05)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d5) 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 05)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 05)
00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 05)
02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
02:06.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller (rev 05)
/var/log/messages
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 completeLet me know if I can supply you with anymore information. Also see attached lspci-v file.
Best
Zeno
Quoted 51 lines · Zeno Davatz
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 completeQuoted 3 lines
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
Quoted 53 lines · Jeff Garzik
Quoted 52 lines · Zeno Davatz
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
Quoted 4 lines
Quoted 3 lines
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.
This is the first message I get after boot that concerns ata:
Mar 10 08:11:13 zenogentoo ata1: clearing spurious IRQ
Mar 10 08:11:44 zenogentoo ata1: lost interrupt (Status 0x50)
Mar 10 08:11:44 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x6 frozen
Mar 10 08:11:44 zenogentoo ata1.00: failed command: WRITE DMA
Mar 10 08:11:44 zenogentoo ata1.00: cmd
ca/00:08:75:98:89/00:00:00:00:00/e3 tag 0 dma 4096 out
Mar 10 08:11:44 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00
Emask 0x4 (timeout)
Mar 10 08:11:44 zenogentoo ata1.00: status: { DRDY }
Mar 10 08:11:44 zenogentoo ata1: soft resetting link
Mar 10 08:11:44 zenogentoo ata1.00: configured for UDMA/133
Mar 10 08:11:44 zenogentoo ata1.00: device reported invalid CHS sector 0
Mar 10 08:11:44 zenogentoo ata1: EH completeand then it continues with:
Mar 10 08:26:14 zenogentoo ata1: clearing spurious IRQ
Mar 10 08:26:44 zenogentoo ata1: lost interrupt (Status 0x50)
Mar 10 08:26:44 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x6 frozen
Mar 10 08:26:44 zenogentoo ata1.00: failed command: READ DMA
Mar 10 08:26:44 zenogentoo ata1.00: cmd
c8/00:00:5d:ba:7b/00:00:00:00:00/e4 tag 0 dma 131072 in
Mar 10 08:26:44 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00
Emask 0x4 (timeout)
Mar 10 08:26:44 zenogentoo ata1.00: status: { DRDY }
Mar 10 08:26:44 zenogentoo ata1: soft resetting link
Mar 10 08:26:44 zenogentoo ata1.00: configured for UDMA/133
Mar 10 08:26:44 zenogentoo ata1.00: device reported invalid CHS sector 0
Mar 10 08:26:44 zenogentoo ata1: EH completeand so on:
Mar 10 09:35:56 zenogentoo ata1: clearing spurious IRQ
Mar 10 09:36:27 zenogentoo ata1: lost interrupt (Status 0x50)
Mar 10 09:36:27 zenogentoo ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x6 frozen
Mar 10 09:36:27 zenogentoo ata1.00: failed command: READ DMA
Mar 10 09:36:27 zenogentoo ata1.00: cmd
c8/00:00:7d:7b:7d/00:00:00:00:00/e4 tag 0 dma 131072 in
Mar 10 09:36:27 zenogentoo res 40/00:00:00:00:00/00:00:00:00:00/00
Emask 0x4 (timeout)
Mar 10 09:36:27 zenogentoo ata1.00: status: { DRDY }
Mar 10 09:36:27 zenogentoo ata1: soft resetting link
Mar 10 09:36:27 zenogentoo ata1.00: configured for UDMA/133
Mar 10 09:36:27 zenogentoo ata1.00: device reported invalid CHS sector 0
Mar 10 09:36:27 zenogentoo ata1: EH completeI can send you my complete /var/log/messages file if you want.
Best
Zeno
Quoted 54 lines · Zeno Davatz
Quoted 53 lines · Jeff Garzik
Quoted 52 lines · Zeno Davatz
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
Quoted 6 lines
Quoted 4 lines
Quoted 3 lines
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.
This is the first message I get after boot that concerns ata:
Not -after- boot, full dmesg including boot, please. Run /bin/dmesg just after booting.
Jeff
Quoted 60 lines · Jeff Garzik
Quoted 59 lines · Zeno Davatz
Quoted 57 lines · Jeff Garzik
Quoted 55 lines · Zeno Davatz
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 completeLet me know if I can supply you with anymore information. Also see attached lspci-v file.
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
need full dmesg from boot, not just error snippet.
This is the first message I get after boot that concerns ata:
Not -after- boot, full dmesg including boot, please. Run
/bin/dmesgjust after booting.
Ok, thanks for the tip, see attachment.
Best
Zeno