[quantal] Unable to boot into 3.5.0-17 kernel

[Joel Cross]

After upgrading to the latest kernel version, I am unable to boot, and receive just a blank screen. Removing the 'quiet splash $vt_handoff' options (but keeping nomodeset, which I normally use), I get a flashing cursor, but nothing else. I can boot into recovery mode and press 'resume boot', but X does not load.

(I reported this bug from 3.5.0-15, so some of the apport information could possibly be wrong)

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joel 1899 F.... pulseaudio
CRDA:
 country GB:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Fri Oct 12 14:10:47 2012
HibernationDevice: RESUME=UUID=84f3e7a4-c3af-4ac1-a789-cc554395a50b
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=305d65f0-a046-450b-a941-bcc858972377 ro quiet splash nomodeset vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-15-generic N/A
 linux-backports-modules-3.5.0-15-generic N/A
 linux-firmware 1.94
SourcePackage: linux
StagingDrivers: rts_pstor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.63
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 166F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.4B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.63:bd03/22/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr0690120000204710000620100:rvnHewlett-Packard:rn166F:rvr09.4B:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 0690120000204710000620100
dmi.sys.vendor: Hewlett-Packard

[Joseph Salisbury (jsalisbury)]

Does this issue also happen in the 3.5.0-16 kernel?

[Olivier Febwin (febcrash)]

Same problem on my DELL Latitude E6520

[Joel Cross (ukch)]

I can't tell, as I jumped straight from 0-15 to 0-17, and 0-16 isn't available from apt-get. Is there another way to install the 0-16 kernel from the repositories?

[Olivier Febwin (febcrash)]

and same problem with a live-usb daily quantal

[Olivier Febwin (febcrash)]

but it works fine with another machine

[Joseph Salisbury (jsalisbury)]

Can you test the following two upstream kernels? We can perform a kernel bisect if 3.5.4 does not have the bug, and 3.5.5 does:

v3.5.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.4-quantal/
v3.5.5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.5-quantal/

[Joel Cross (ukch)]

Both of those boot fine, although other errors (USB/Wifi) are envountered. Versions tested:

3.5.4-030504.201209142010
3.5.5-030505.201210021510

[Joseph Salisbury (jsalisbury)]

Can you also test the 3.5.0-16 kernel, which can be downloaded from:

https://launchpad.net/ubuntu/+source/linux/3.5.0-16.24/+build/3860892

[Joel Cross (ukch)]

3.5.0-16.24 boots fine, but has the same problem with USB devices not working. Should I raise a separate bug about that, or do you think the two are related?

[Joseph Salisbury (jsalisbury)]

Just to confirm, can you boot back into v3.5.0-17 and confirm the bug is back. If it is, this issue would be due to an Ubuntu specific change in 3.5.0-17 since the 3.5.4 and 3.5.5 upstream kernels boot fine.

If the bug comes back in 3.5.0-17, I can perform a kernel bisect between 3.5.0-16 and 3.5.0-17.

[Olivier Febwin (febcrash)]

It doesn't work for me with 3.5.0-16 ; 3.5.4 ; 3.5.5

[Joel Cross (ukch)]

Attempting to boot the 3.5.0-17.28 kernel (with the extras package installed) is no longer giving me a blank screen, but is still appearing to freeze after 'Loading initial ramdisk' is displayed.

[Olivier Febwin (febcrash)]

When I switch on my wifi button, Quantal boots with fine with 3.5.0-17 !

[Olivier Febwin (febcrash)]

*switch on my wifi with the hardware button

[Olivier Febwin (febcrash)]

Now, with wifi activated, i can boot on 3.5.5 kernel and 3.5.4

[penalvch (penalvch)]

Olivier FEBWIN, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

[Joseph Salisbury (jsalisbury)]

@Joel

Can you follow the "Boot options" instructions on the following wiki to enable additional output on boot:

https://wiki.ubuntu.com/DebuggingKernelBoot

As mentioned on the wiki, it would be great if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.

[Joel Cross (ukch)]

I've had a fiddle with the boot options, and it looks like it's actually booting OK (the text-based login screen briefly appears). I'm guessing the problem then is actually with starting the xserver, which for some reason irrevocably blanks the screen.

[Olivier Febwin (febcrash)]

@penalvch : OK, it's here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1074349
It's the same problem

[Joel Cross (ukch)]

@Joseph any update on this bug? Do you think it will be safe for me to upgrade to Raring, or should I stay on Quantal for now?

[Joseph Salisbury (jsalisbury)]

One option would be to boot Raring from a Live CD on your system. That will tell you if everything works ok before upgrading.

[penalvch (penalvch)]

Joel Cross, could you please provide the full computer model as noted on the sticker?

[Joel Cross (ukch)]

HP Pavilion g6. Other than that I don't know, as there is no sticker or anything.

[penalvch (penalvch)]

Joel Cross, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]