linux 3.8.0.10-generic does not boot

This change was made by a bot.

After March 5th morning update, Lenovo T430 2342CTO does not boot - graphic card not recognized.

Also facing this bug on my MacBook Pro 8,2 with 3.8.0-10. 3.8.0-9 still boots fine.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc1-raring/

In addition to the latest mainline kernel, it would be good to know what 3.8 kernel introduced this bug. Can folks affected by this bug test the following two upstream kernels:

v3.8.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.1-raring/
v3.8.2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.2-raring/

I just tested this and the 3.8.2 mainline kernel exhibits the same behavior. Recovery mode boots fine, but graphical boot just hangs with no explanation given (the output just stops at the normal filesystem mount dialog).

I'm confused by "test the latest v3.9 kernel"--there is only a linux-headers package in that folder, no linux-image--but I'm assuming that's just an error. 3.8.2 is the equivalent mainline kernel version to 3.8.0-10.

I tested mainline kernels 3.8.1 and 3.8.2. The bug is present in 3.8.2; 3.8.1 boots completely fine.

Thanks for testing. It appears this regression was introduced in v3.8.2.

I started a kernel bisect between v3.8.1 and v3.8.2. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
fd9471ef7e6ee38a7f29f5556928ddf4824f8bdd

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1146988

Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results.

One thing to note, you will need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance

I noticed a similar problem on one of my machines, which is introduced by:

commit 47f531e8ba3bc3901a0c493f4252826c41dea1a1
Author: Matt Fleming <email address hidden>
Date: Thu Jan 31 19:02:03 2013 +0000

    efivarfs: Validate filenames much more aggressively

Joe, you might just want to try reverting this commit to see if it fixes the issue. You'll also need to revert the following, which depends on that commit:

commit da27a24383b2b10bf6ebd0db29b325548aafecb4
Author: Matt Fleming <email address hidden>
Date: Fri Feb 1 11:02:28 2013 +0000

    efivarfs: guid part of filenames are case-insensitive

(Note that the SHA-1's here are different than the ones in the raring repository)

I'm also doing a git bisect and reverting the two commits that Seth mentioned does seem to solve the problem.

I've completed the bisect. The broken commit is da27a24383b2b10bf6ebd0db29b325548aafecb4. The commit 47f531e8ba3bc3901a0c493f4252826c41dea1a1 mentioned before is *not* broken (at least for my system). You can see this in my bisect log linked below.

Broken commit: http://paste.kde.org/690824/raw/
Bisect log (git bisect replay /path/to/log): http://paste.kde.org/690830/raw/

This possibly a dulicate of 1146868.

This bug was fixed in the package linux - 3.8.0-12.21

---------------
linux (3.8.0-12.21) raring; urgency=low

  [ Tim Gardner ]

  * [Config] CONFIG_PSTORE=n for x86
  * Release Tracking Bug
    - LP: #1152228

  [ Upstream Kernel Changes ]

  * Revert "efivarfs: guid part of filenames are case-insensitive"
    - LP: #1146988
  * Revert "efivarfs: Validate filenames much more aggressively"
    - LP: #1146988
  * mfd: rtsx: Optimize card detect flow
    - LP: #1148892
  * mfd: rtsx: Fix issue that booting OS with SD card inserted
    - LP: #1148892
 -- Tim Gardner <email address hidden> Wed, 06 Mar 2013 06:40:22 -0700

Can confirm that for me this bug is fixed with 3.8.0-12.21. Good job!

My problem is probably related to 982889. I encountered it in both 12.10 and 13.04. I was able to solve it by delaying lightdm in /etc/init/lightdm.conf.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.