2.6.27-2.3 fails to boot on Compaq Presario S6010V:
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Stefan Bader | ||
Intrepid |
Won't Fix
|
High
|
Stefan Bader |
Bug Description
SRU Justification:
Impact (from patch): "We found a situation on Linus' machine that the Nvidia timer quirk hit on a Intel chipset system. the problem is that the system has a fancy Nvidia card with an own PCI bridge, and the early-quirks code looking for any NVidia bridge triggered on it incorrectly. This didn't lead a boot failure by luck, but the timer routing code selecting the wrong timer first and some ugly messages. It might lead to real problems on other systems."
Fix: "I checked all the devices which are currently checked for by early_quirks and it turns out they are all located in the root bus zero. So change the early-quirks loop to only scan bus 0. This incidently also saves quite some unnecessary scanning work, because early_quirks doesn't go through all the non root busses. The graphics card is not on bus 0, so it is not matched anymore."
Testcase: See below.
Kubuntu Intrepid Ibex (8.10) alpha5 will not boot on my computer with the 2.6.27-2.3 kernel. The 2.6.26 kernel works fine. I have tested with the livecd and have received similar results. My computer is a Compaq Presario S6010V. Specs are something like:
-Pentium Celeron 2.5 GHZ
-640 MB RAM (DDR)
-Nvidia GeForce4 MX 440
Here are screenshots:
This is basically at the start of the boot. The errors look suspicious.
http://
Then after that sometimes it goes on after "Loading Hardware drivers" and throws a bunch of errors about not being able to launch some executables from /sbin. Other times stuff just crashes. Sort of hard to get good info since it all goes by so fast.
On the LiveCD it proceeds to "Loading Hardware Drivers" then throws 3 lines of SQAUSHFS errors after which it hangs indefinitely.
After some investigation, I found out that switching the videocard in use from PCI (my Geforce4) to onboard in the BIOS avoids this crash, so it could be something fiddly triggered by my videocard or the BIOS or some combination of the two.
Related branches
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → High |
status: | Incomplete → Triaged |
Changed in linux: | |
assignee: | ubuntu-kernel-team → colin-king |
milestone: | none → ubuntu-8.10 |
Changed in linux: | |
assignee: | ben-collins → stefan-bader-canonical |
assignee: | ben-collins → stefan-bader-canonical |
Changed in linux: | |
status: | Incomplete → In Progress |
description: | updated |
Changed in linux: | |
status: | In Progress → Incomplete |
Hi Jonathan,
Looking at the picture you attached, I'm curious if you'd take a look at bug 246269 as this may be a duplicate of that based on the error messages. Thanks.