Kernel 3.5.0-27 fails to boot

Bug #1167341 reported by Jeff Williams
This bug report is a duplicate of:  Bug #1167114: Ubuntu Kernel 3.5.0-27 does not boot. Edit Remove
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Running Ubuntu 12.04LTS x86-64 on a Sager P170EM Core i7 laptop, after upgrading to kernel 3.5.0-27 the screen turns off upon starting the kernel boot. There does not appear to be a running kernel at this point. ctrl-alt-delete will immediately reboot the system. Selecting the previous kernel, 3.5.0-26, yields a functioning Ubuntu system. Selecting single-user mode for the kernel boot of 3.5.0-27 also results in the LCD shutdown and no evidence of a running kernel.

In performing a google search to see if there was a simple fix for this (e.g. GRUB configuration fix), I noticed that this problem is reported in other forums for some IBM Thinkpads.

Running through a few earlier kernels in the 3.5.0 series, every one I tried yielded a working Ubuntu system. Running the memory test found no issues on my hardware.

Given that there is no kernel output (even alt-F1 yields nothing), there is no further information I can provide on this failure.

lsb_release -rd output:
Description: Ubuntu 12.04.2 LTS
Release: 12.04

apt-cache output:
Installed: 3.5.0-27.46~precise1

Expected result: system boot
Actual result: LCD shutdown, no evidence of kernel boot

Tags: precise
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1167341

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Jeff Williams (nonrepeatedmeme) wrote :

As indicated in the initial submission, there is no running kernel when this occurs and, therefore, no way to run "apport-collect 1167341".

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → High
Revision history for this message
Ulf Andersson (uanderss) wrote :

I can confirm this.
I have Ubuntu 12.10 and Thinkpad T410. It stops directly before "Ubuntu" splashscreen.
Nothing in the dmesg or syslog.

Revision history for this message
volker (volker-fr) wrote :

I can confirm this bug. It happens on a Lenovo ThinkPad T420 with Ubuntu 12.10.

I removed the boot option 'quiet splash' and the kernel starts to boot, but then LCD gets blank again after a few seconds and the system does not show any output (sysreq key for reboot works).

Using the recovery mode of 3.5.0-27 boots up, shows the recovery menu, but something starts to hang the system just on the build in grub reconfiguration on or directly after mounting the partition RW.

Revision history for this message
James McPhee (jmcphe) wrote :

I can also confirm this bug. Dell Latitude E6520. Ubuntu 12.10.

Same symptoms with 3.5.0-27 kernel packages. Booted to 3.5.0-26 succeeds.

Revision history for this message
Igor A Tarasov (dicr) wrote :

This bug also affected me.
Last working kernel was 3.5.0-26.
Starting from 3.5.0-27 and 3.5.0-28 system booting with the black screen.
Workaround is to add 'nomodeset' boot option, but the screen resolution in Gnome will not proportional.

Revision history for this message
Alec MacLean (alec-g) wrote :

This bug also affects me on a DELL XPS (L702X).

Starting from 3.5.0-27 only gives black screen and no keyboard response (cannot Ctrl-Alt-Del).
I'm a noob, so afraid cannot offer much more insight than this, sorry.

Working with kernel 3.5.0-26 via "Advanced options" from GRUB.

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.