[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

HDD-Probleme seit Kernel 2.6.30



Hllo zusammen,

seitdem ich auf meinem Debian-SID-System den Linux-Kernel 2.6.30 (SID-Version) installiert 
habe, kommt es in unregelmäßigen Abständen zu Abstürzen, da das System nicht mehr auf die 
Festplatte zugreifen kann. Im Kernel-Log tauchen dann regelmäßig solche Meldungen auf:

-----------------8<------------------------8<---------------------------8<--------------------------------

[ 6855.816187] ata1.00: exception Emask 0x0 SAct 0x3f SErr 0x0 action 0x6 frozen
[ 6855.816208] ata1.00: cmd 61/08:00:21:18:18/00:00:13:00:00/40 tag 0 ncq 4096 out
[ 6855.816212]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6855.816219] ata1.00: status: { DRDY }
[ 6855.816234] ata1.00: cmd 61/08:08:a1:b9:26/00:00:02:00:00/40 tag 1 ncq 4096 out
[ 6855.816237]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6855.816244] ata1.00: status: { DRDY }
[ 6855.816258] ata1.00: cmd 61/08:10:81:c3:53/00:00:02:00:00/40 tag 2 ncq 4096 out
[ 6855.816261]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6855.816267] ata1.00: status: { DRDY }
[ 6855.816281] ata1.00: cmd 61/08:18:c9:c3:53/00:00:02:00:00/40 tag 3 ncq 4096 out
[ 6855.816284]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6855.816291] ata1.00: status: { DRDY }
[ 6855.816305] ata1.00: cmd 61/08:20:89:18:2d/00:00:0c:00:00/40 tag 4 ncq 4096 out
[ 6855.816308]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6855.816315] ata1.00: status: { DRDY }
[ 6855.816329] ata1.00: cmd 61/10:28:d1:69:99/00:00:0c:00:00/40 tag 5 ncq 8192 out
[ 6855.816332]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 6855.816338] ata1.00: status: { DRDY }
[ 6855.816351] ata1: hard resetting link
[ 6861.176106] ata1: link is slow to respond, please be patient (ready=0)
[ 6865.824164] ata1: COMRESET failed (errno=-16)
[ 6865.824178] ata1: hard resetting link
[ 6871.184164] ata1: link is slow to respond, please be patient (ready=0)
[ 6875.832158] ata1: COMRESET failed (errno=-16)
[ 6875.832173] ata1: hard resetting link
[ 6881.195691] ata1: link is slow to respond, please be patient (ready=0)
[ 6910.876157] ata1: COMRESET failed (errno=-16)
[ 6910.876173] ata1: limiting SATA link speed to 1.5 Gbps
[ 6910.876179] ata1: hard resetting link
[ 6915.900191] ata1: COMRESET failed (errno=-16)
[ 6915.900204] ata1: reset failed, giving up
[ 6915.900211] ata1.00: disabled
[ 6915.900257] ata1: EH complete
[ 6915.900299] sd 2:0:0:0: [sda] Unhandled error code
[ 6915.900304] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 6915.900313] end_request: I/O error, dev sda, sector 211380689
[ 6915.900335] Buffer I/O error on device dm-0, logical block 18917966
[ 6915.900340] lost page write due to I/O error on dm-0
[ 6915.900358] Buffer I/O error on device dm-0, logical block 18917967
[ 6915.900363] lost page write due to I/O error on dm-0
[ 6915.900388] sd 2:0:0:0: [sda] Unhandled error code
[ 6915.900392] sd 2:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 6915.900400] end_request: I/O error, dev sda, sector 204281993
[ 6915.900409] Buffer I/O error on device dm-0, logical block 18030629
[ 6915.900414] lost page write due to I/O error on dm-0

-----------------8<------------------------8<---------------------------8<--------------------------------

Wenn ich das richtig verstehe, schaltet der Treiber nach diversen Timeouts den ATA-Port 
einfach ab. Mit dem 2.6.29er-Kernel taucht das Problem nicht auf. 

Kennt irgendjemand einen Workaround für das Phänomen oder kann mir bei der weiteren 
Eingrenzung des Fehlers helfen?

Viele Grüße

Matthias


P.S.: 
Ausgabe von lspci:


00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 
0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated 
Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics 
Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 
02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 
02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 
(rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 
02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 
02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 
02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 
(rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 
02)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI 
Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
02:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05)
02:09.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
02:09.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
02:09.3 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet 
Controller (rev 12)
0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network 
Connection (rev 02)





Reply to: