Hardy: ata errors stop the boot process for 10 minutes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
Hardy |
Fix Released
|
High
|
Tim Gardner |
Bug Description
Binary package hint: linux-image-
Yesterday my desktop running Ubuntu Hardy (x86_64) started showing boot problems: showing a blank screen (with blinking cursor) or showing the boot splash going forward & backward, with the disk silent, not progressing until I get bored and reboot.
When I boot in rescue mode, I see the following errors (just after it correctly detects my hard drive on ata1):
[ 28.820922] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 28.824248] ata1.00: ATA-7: SAMSUNG SP2004C, VM100-50, max UDMA7
[ 28.824290] ata1.00: 390721968 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 28.853832] ata1.00: configured for UDMA/133
[ 31.171096] ata2: classification failed
[ 31.171136] ata2: reset failed (errno=-22), retrying in 8 secs
[ 39.482420] ata2: classification failed
[ 39.482460] ata2: reset failed (errno=-22), retrying in 10 secs
[ 49.472609] ata2: classification failed
[ 49.473157] ata2: reset failed (errno=-22), retrying in 35 secs
[ 83.799319] ata2: limiting SATA link speed to 1.5 Gbps
[ 84.438170] ata2: classfication failed, assuming ATA
[ 84.438218] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 310)
[ 114.409170] ata2.00: qc timeout (cmd 0xec)
[ 114.409219] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 114.409260] ata2: failed to recover some devices, retrying in 5 secs
and then it starts repeating, with longer timeouts. This goes on for 10 minutes, in the middle of which I get an (initramfs) prompt because /dev/disk/
When the 10 minutes pass, I see
[ 356.102791] ata2: classfication failed, assuming ATA
[ 356.102837] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 310)
[ 356.102997] scsi 0:0:0:0: Direct-Access ATA SAMSUNG SP2004C VM10 PQ: 0 ANSI: 5
then my hard disk becomes visible in /dev, and I can press Ctrl+D to continue booting.
This does not happen if I boot the older 2.6.22-14-generic kernel (version 2.6.22-14.47). (What happens is my X become unhappy because I didn't have nvidia's binary blob installed for that kernel).
/var/log/dpkg.log tells me I got 2.6.24-19-generic (version 2.6.24-19.34) on June 26. /var/log/kern.log tells me that I successfully booted this kernel on June 26 (several times), 27 and 28. The first boot problems appeared only yesterday. Since then I've been having boot problems every day. Reinstalling the kernel didn't help.
As far as I can tell, ata1 has my SATA hard disk, while ata2 is supposed to have my DVD drive (which also has problems working in Windows). They're both attached to a JMicron RAID controller (that had problems loading GRUB until I reflashed it with a newer firmware).
$ lspci -nn -s 02:
02:00.0 SATA controller [0106]: JMicron Technologies, Inc. JMB361 AHCI/IDE [197b:2361] (rev 02)
02:00.1 IDE interface [0101]: JMicron Technologies, Inc. JMB361 AHCI/IDE [197b:2361] (rev 02)
$ ls -l /dev/disk/by-path/
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
pci-0000:
(sda through sdd represent the multi-format card reader attached through USB)
The DVD drive seems to work (i.e. "eject" opens the tray) despite the long pause.
I searched on launchpad and while I found some similar-looking bugs, none of them mentioned ata classification errors. Not being sure, I'm filing a new bug.
Changed in linux: | |
status: | Unknown → Fix Released |
Changed in linux: | |
assignee: | nobody → timg-tpi |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04.2 |
status: | New → In Progress |
milestone: | ubuntu-8.04.2 → ubuntu-8.10-beta |
Changed in linux: | |
importance: | Unknown → Medium |
Seems to me your problem is described here: kerneltrap. org/mailarchive /git-commits- head/2008/ 6/20/2184924
http://