[sata_sil] fails to mount root filesystem on Shuttle SN85g4(v2)

Bug #69356 reported by Alex Mauer
This bug report is a duplicate of:  Bug #33269: root filesystem fails to mount. Edit Remove
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
New
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upon upgrading my desktop (a Shuttle SN85g4 version 2) to Edgy today, I found that it would no longer boot.

On investigation, I found that it was hanging while "Waiting for root filesystem..."

I scrolled back a bit and found (copied by hand, typographical errors are possible, even probable):

ata1: SATA max UDMA/100 cmd 0xE0828080 ctl 0xE082808A bmdma 0xE0828000 irq 161
ata2: SATA max UDMA/100 cmd 0xE08280C0 ctl 0xE08280CA bmdma 0xE0828008 irq 161
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 ATA-6, max UDMA/133, [number] sectors: LBA48
ata1: qc timeout (cmd0xef)
ata1: failed to set xfermode (err_mask=0x4)
scsi0: sata_sil
ata2: SATA link down (SStatus 0)
scsi1: sata_sil

The system still boots fine using the latest Dapper kernel (2.6.15-27-k7)

Output from LSPCI:
00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev a6)
00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
00:05.0 Ethernet controller: nVidia Corporation nForce3 Ethernet (rev a5)
00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 Multimedia audio controller: Creative Labs SB Audigy (rev 03)
01:05.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 03)
01:05.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port
01:06.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
01:07.0 RAID bus controller: Silicon Image, Inc. SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
02:00.0 VGA compatible controller: nVidia Corporation NV36.1 [GeForce FX 5700 Ultra] (rev a1)

Revision history for this message
Alex Mauer (hawke) wrote :

Oh, and if it's not clear from the above, I'm using a SATA drive attached to ata1.

Revision history for this message
Alex Mauer (hawke) wrote :

It also doesn't work on Feisty, kernels 2.6.20-5 through 2.6.20-8. Still works fine with Dapper kernel 2.6.15-28-k7

Revision history for this message
Chuck Short (zulcss) wrote :

Please attach the full dmesg and the output of lspci -nvv.

Thanks

Changed in linux-source-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
Alex Mauer (hawke) wrote :

Attached please find the output of lspci -nvv (made when running kernel 2.6.15-28-k7; I don't know if that matters)

Any suggestions on how I might obtain the full dmesg when the system won't boot?

Let me know if you mean the dmesg of kernel 2.6.15-28-k7, but I assume you don't.

Revision history for this message
Chuck Short (zulcss) wrote :

Do you get a shell when you boot your computer?

Revision history for this message
Alex Mauer (hawke) wrote :

No, not with kernel 2.6.20. If it will help, I can hand-copy the last portion of kernel output on bootup as I did in the intial bug report. The output does differ somewhat from 2.6.17.

Chuck Short (zulcss)
Changed in linux-source-2.6.20:
assignee: nobody → zulcss
status: Needs Info → Confirmed
Revision history for this message
Alex Mauer (hawke) wrote :

Portion of the dmesg that appears to deal with the hard drive:

ata1: SATA max UDMA/100 cmd 0xE0828080 ctl 0xE082808A bmdma 0xE0828000 irq 19
ata2: SATA max UDMA/100 cmd 0xE08280C0 ctl 0xE08280CA bmdma 0xE0828008 irq 19
scsi0: sata_sil
ata1: SATA link up 1.5Gbps (SStatus 113 SControl 310)
ata1.00: ATA-6, max UDMA/133, 488397168 sectors: LBA48
ata1.00: dev 0 multi count 16
--PAUSE about 30 secs--
ata1.00: qc timeout (cmd 0xef)
ata1.00: failed to set xfermode (err_mask=0x4)
ata1.00: limiting speed to UDMA/66
ata1: failed to recover some devices, retrying in 5 secs
--PAUSE about 30 secs--
ata1: SATA link up 1.5Gbps (SStatus 113 SControl 310)
ata1.00: ATA-6, max UDMA/133, 488397168 sectors: LBA48
ata1.00: dev 0 multi count 16
ata1.00: qc timeout (cmd 0xef)
ata1.00: failed to set xfermode (err_mask=0x4)
ata1.00: limiting speed to PIO0
ata1: failed to recover some devices, retrying in 5 secs
--PAUSE about 30 secs--

After this it goes off on a tangent about USB devices (which it fails to enable).

Revision history for this message
Gaëtan Petit (gaetanp) wrote :

this bug is a duplicate of mine : #83313

hopefully this has been package in today 2.6.20.2
see bug 7996 on kernel.org bugzilla : http://bugzilla.kernel.org/show_bug.cgi?id=7996

Revision history for this message
Alex Mauer (hawke) wrote :

I think It's more likely that your bug #83313 is a duplicate of this, given the bug numbers (this one came first)

Revision history for this message
Alex Mauer (hawke) wrote :

Actually it sounds like this might be a different problem since it didn't work for me on edgy either. And bug #83313 is with a different chipset (intel instead of SiI). Hopefully it'll be fixed with the same kernel fix though. Fingers crossed.

Revision history for this message
Oleksij Rempel (olerem) wrote :

Please try Ubuntu Gutsy if it fixed for you.

Changed in linux-source-2.6.20:
assignee: zulcss → ubuntu-kernel-team
Revision history for this message
Alex Mauer (hawke) wrote :

I don't actually have a SATA drive in the machine in question at the moment, so I cannot currently test this.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.