revalidation failed errors with AMD chipset and SATA drives

Bug #483805 reported by Alen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading some hardware (MBO, GPU and CPU), the system often does not boot, drops to busybox shell with the message: dev/disk/by-uuid/.... does not exist.
I'm having a multi boot ubuntu intrepid, jaunty and karmic, each on it's own partition and all installations have the same problem. Sometimes i need to restart the system 3-4 times until it boots succesfully. Old MBO was nvidia 6100/430 chipset and never had any problems. New MBO has AMD 770 + SB710 Chipset, there are 4 SATA disks attached, tried changing the settings in BIOS 'no raid' or 'AHCI' and it didn't help.
I'm attaching a couple of dmesg outputs: two from 9.04 (succesfull and unsuccesfull), and from 8.10 with succesfull boot.
Googling around didn't help much, there are some hints about some race condition between SATA and USB, after a couple of failed boots, tried disconnecting USB mouse and the system booted OK, maybe a coincidence?
Here is the link:
http://linux.dell.com/wiki/index.php/Ubuntu_7.04/Issues/USB-SATA_race_condition_causes_hang
Following a part of dmesg, the failing disk (HDS722580VLSA80) is the one with the / partition:

[ 1.598968] ahci 0000:00:11.0: version 3.0
[ 1.598983] ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 1.599073] ahci 0000:00:11.0: irq 2301 for MSI/MSI-X
[ 1.599171] ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
[ 1.599235] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part
[ 1.599678] scsi0 : ahci
[ 1.599789] scsi1 : ahci
[ 1.599877] scsi2 : ahci
[ 1.599964] scsi3 : ahci
[ 1.600055] scsi4 : ahci
[ 1.600141] scsi5 : ahci
[ 1.600259] ata1: SATA max UDMA/133 abar m1024@0xf9eff800 port 0xf9eff900 irq 2301
[ 1.600323] ata2: SATA max UDMA/133 abar m1024@0xf9eff800 port 0xf9eff980 irq 2301
[ 1.600387] ata3: SATA max UDMA/133 abar m1024@0xf9eff800 port 0xf9effa00 irq 2301
[ 1.600451] ata4: SATA max UDMA/133 abar m1024@0xf9eff800 port 0xf9effa80 irq 2301
[ 1.600514] ata5: SATA max UDMA/133 abar m1024@0xf9eff800 port 0xf9effb00 irq 2301
[ 1.600578] ata6: SATA max UDMA/133 abar m1024@0xf9eff800 port 0xf9effb80 irq 2301
[ 2.084024] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.090078] ata1.00: HPA unlocked: 160834367 -> 160836480, native 160836480
[ 2.090137] ata1.00: ATA-6: HDS722580VLSA80, V32OA6MA, max UDMA/100
[ 2.090191] ata1.00: 160836480 sectors, multi 0: LBA48
[ 7.092013] ata1.00: qc timeout (cmd 0x27)
[ 7.092076] ata1.00: failed to read native max address (err_mask=0x4)
[ 7.092131] ata1.00: revalidation failed (errno=-5)
[ 7.576024] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 17.580018] ata1.00: qc timeout (cmd 0x27)
[ 17.580081] ata1.00: failed to read native max address (err_mask=0x4)
[ 17.580136] ata1.00: revalidation failed (errno=-5)
[ 17.580191] ata1: limiting SATA link speed to 1.5 Gbps
[ 17.580244] ata1.00: limiting speed to UDMA/100:PIO3
[ 18.064024] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 28.064020] ata1.00: qc timeout (cmd 0x27)
[ 28.064083] ata1.00: failed to read native max address (err_mask=0x4)
[ 28.064137] ata1.00: revalidation failed (errno=-5)
[ 28.064190] ata1.00: disabled
[ 28.080021] ata1: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x6 frozen t4
[ 28.080086] ata1: SError: { HostInt }
[ 28.080140] ata1: hard resetting link
[ 28.564024] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 28.564083] ata1: EH complete

Revision history for this message
Alen (cshadow) wrote :
Revision history for this message
Alen (cshadow) wrote :
Revision history for this message
Alen (cshadow) wrote :
Revision history for this message
Alen (cshadow) wrote :
Revision history for this message
Alen (cshadow) wrote :
Revision history for this message
Alen (cshadow) wrote :
Revision history for this message
Alen (cshadow) wrote :

Attaching dmesg from ubuntu karmic, kernel 2.6.31-14 where after a couple of revalidation fails, disk gets validated and boot continues (lines 618-640 in the file).

Andy Whitcroft (apw)
tags: added: kernel-series-unknown
tags: added: karmic
removed: kernel-series-unknown
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Alen,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 483805

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.