sata init pb with kernel 2.6.22-12 / ubuntu 7.10

Bug #147158 reported by jairbubbles
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

On my system the Ubuntu 7.10 live cd crashes at loading. 7.04 works fine and after a dist-upgrade I could launch 7.10 only with kernel 2.6.20.
Launching kernel 2.6.22-12 always end to that error :

ata1 : qc timeout (cmd 0xec)
ata1 : Failed to IDENTIFY (I/O Error, err_mask = 0x4)

My SATA controller is a VT8251, I have only one SATA hard drive connected (Samsung SP2504C)

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full output of 'sudo lspci -vvnn' from the 2.6.20 kernel as an attachment to your bug report? Additionally it would be interesting to see if the Gutsy Live CD will boot if you pas s the 'all_generic_ide' option to the kernel. Thanks in advance.

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
jairbubbles (jairbubbles) wrote :

Here is the output of 'sudo lspci -vvnn' ...

Revision history for this message
jairbubbles (jairbubbles) wrote :

I added "all_generic_ide" in the Grub menu and I was able to boot with 2.6.22 (seems pretty slow though).

Revision history for this message
jairbubbles (jairbubbles) wrote :

Everything is fine with the last kernel 2.6.22.13 !

Revision history for this message
Vinay Augustine (v) wrote :

I have a machine with VT8251 (an Asus A8V-XE motherboard) that just crashed. I found this relevant thread: http://forums.gentoo.org/viewtopic-t-551503.html which mentions similar error messages.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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