3.7 kernels do not boot

[ill]

when using the 3.7 kernels from http://kernel.ubuntu.com/, the machine no longer boots up, and crashes when starting.
---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ill 1724 F.... xfce4-volumed
                      ill 1736 F.... pulseaudio
 /dev/snd/controlC1: ill 1724 F.... xfce4-volumed
                      ill 1736 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 12.10
InstallationDate: Installed on 2012-07-28 (107 days ago)
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.5.0-18-generic root=UUID=d1b86751-29b4-4068-bebb-3d662aa6d99b ro rootflags=subvol=@ xbmc=autostart
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-18-generic N/A
 linux-backports-modules-3.5.0-18-generic N/A
 linux-firmware 1.95
RfKill:

Tags: quantal
Uname: Linux 3.5.0-18-generic x86_64
UpgradeStatus: Upgraded to quantal on 2012-10-12 (32 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/04/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 5001
dmi.board.name: M2N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1077822/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

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

apport-collect 1077822

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.

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[ill (illumilore)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 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.7-rc5-raring/

[Joseph Salisbury (jsalisbury)]

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.

[Joseph Salisbury (jsalisbury)]

@ill

Can you provide some additional details on your testing of the mainline kernel? Did you see the same errors, or new errors? Also, it would be helpful if you could gather additional data, mentioned in comment #17.

Thanks in advance!

[Mario Lopez (mariolcp)]

I have the same motherboard and exact same issue I've tried every release of the 3.7 kernel and all of em give me the exact same error as displayed on your picture above.

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

v3.5.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7-quantal/
v3.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/
v3.7-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/

You don't have to test every kernel, just up until the kernel that first has this bug.

Thanks in advance!

[ill (illumilore)]

For me, the 3.6 and 3.7 kernels never booted. I tested various rc builds and the final for 3.6. The 3.5.7 kernels work fine.

[Joseph Salisbury (jsalisbury)]

Does the v3.6-rc1 kernel[0] boot? If not, we can perform a bisect between v3.5 final and v3.6-rc1. It would probably also be good to confirm v3.5 final[1] does not have this bug as well, so we know we have the correct starting/ending versions(To rule out this being fixed in a 3.5 stable release).

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc1-quantal/
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-quantal/

[ill (illumilore)]

the bug happens somewhere between 3.6rc1 and 3.5

[Joseph Salisbury (jsalisbury)]

I can bisect between those releases. It looks like the latest mainline kernel tested was v3.7-rc5, requested in comment #16. The v3.7 final kernel is now released. Can you test the v3.7 kernel before I start the bisect? It is available from:

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

[ill (illumilore)]

Same thing happens with 3.7 final.

[Leo (llenchikk)]

I have same issue with 13.04 live-usb dated 2012-12-29 and
with 12.04 with 3.7.1 kernel from http://kernel.ubuntu.com/~kernel-ppa/ .
29122012223.jpg - attachment with messages right after boot stops.

[Erick Brunzell (lbsolost)]

I may very well be mistaken but I think bug #1082673 may be a duplicate. You can see what happens when I try to run Lubuntu i386 20130104 on this hardware in the linked photo:

AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
nVidia MCP61 High Definition Audio (rev a2)
nVidia MCP61 Ethernet (rev a2)
2GB DDR2 RAM

http://ubuntuforums.org/attachment.php?attachmentid=229583&d=1357344337

It doesn't matter if I choose check for defects, try w/o installing, or install .... always the same failed boot.

[Joseph Salisbury (jsalisbury)]

One additional request before I bisect between v3.5 final and v3.6-rc1. The v3.8-rc2 kernel is now available. Can you test that kernel to see if it also has the bug? If it does, I'll kick off the bisect. The v3.8-rc2 kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc2-raring/

[Leo (llenchikk)]

The v3.8-rc2 kernel has this bug for me.
Ubuntu 12.04.
Photo attached.

[ill (illumilore)]

Still happening with 3.8 rc2

[Erick Brunzell (lbsolost)]

Re: comment #29;

I've found that I can boot the live media using the "acpi=off" boot parameter. The screen resolution is low but that can be resolved post-installation by installing the proper nVidia drivers.

But I'm a real dummy when it comes to kernel problems so this should be verified by someone else.

[Joseph Salisbury (jsalisbury)]

I started a bisect between v3.5 and v3.6-rc1. The first test kernel is built up to commit:
614a6d4341b3760ca98a1c2c09141b71db5d1e90

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

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.

[Leo (llenchikk)]

 614a6d4341b3760ca98a1c2c09141b71db5d1e90 kernel works for me.

[Mateusz Stachowski (stachowski-mateusz)]

Your kernel packages are incomplete (Mainline Kernels always consists of four packages). I wasn't able to boot to graphical mode because modules didn't build [NVIDIA, VirtualBox and OSSv4 (Open Sound System)]. If there was a linux-headers-3.5..._all.deb package than I wouldn't had that problem. This means that this kernel isn't affected by the bug.

I've also checked 3.6rc1 and this kernel doesn't work at all (it stops at usb modem HUAWEI).

[Joseph Salisbury (jsalisbury)]

@ill

Can you also confirm that the test kernel posted in comment #34 does not have this bug? If so, I'll update the bisect and build the next kernel.

[Mateusz Stachowski (stachowski-mateusz)]

I installed today 3.8rc3 from Mainline Kernel PPA and it booted succesfully. There also was no problem with building the modules [NVIDIA 313.09, VirtualBox 4.2.6 and OSS v4.2 build 2007 (Open Sound System)].

That's the first kernel after the 3.5 series that works on my machine (3.8rc1 and rc2 won't boot).

Ubuntu 12.10 64-bits
AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ × 2
GeForce 9600 GT/PCIe/SSE2

[Leo (llenchikk)]

@Mateusz
I also was able to boot with 3.8rc3.
But there was about 1 minute latency so I captured errors.

On photo: after latest error boot continued well.

[ill (illumilore)]

The 3.5 commit build doesn't install correctly for me.

Selecting previously unselected package linux-headers-3.5.0-030500-generic.
(Reading database ... 162351 files and directories currently installed.)
Unpacking linux-headers-3.5.0-030500-generic (from linux-headers-3.5.0-030500-generic_3.5.0-030500.201301150952_amd64.deb) ...
Selecting previously unselected package linux-image-3.5.0-030500-generic.
Unpacking linux-image-3.5.0-030500-generic (from linux-image-3.5.0-030500-generic_3.5.0-030500.201301150952_amd64.deb) ...
Done.
Selecting previously unselected package linux-image-extra-3.5.0-030500-generic.
Unpacking linux-image-extra-3.5.0-030500-generic (from linux-image-extra-3.5.0-030500-generic_3.5.0-030500.201301150952_amd64.deb) ...
dpkg: dependency problems prevent configuration of linux-headers-3.5.0-030500-generic:
 linux-headers-3.5.0-030500-generic depends on linux-headers-3.5.0-030500; however:
  Package linux-headers-3.5.0-030500 is not installed.

dpkg: error processing linux-headers-3.5.0-030500-generic (--install):
 dependency problems - leaving unconfigured
Setting up linux-image-3.5.0-030500-generic (3.5.0-030500.201301150952) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.5.0-030500-generic /boot/vmlinuz-3.5.0-030500-generic
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
    import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3.5.0-030500-generic (x86_64)
Consult /var/lib/dkms/nvidia-current/304.64/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.5.0-030500-generic /boot/vmlinuz-3.5.0-030500-generic
update-initramfs: Generating /boot/initrd.img-3.5.0-030500-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.5.0-030500-generic /boot/vmlinuz-3.5.0-030500-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.5.0-030500-generic /boot/vmlinuz-3.5.0-030500-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.5.0-030500-generic /boot/vmlinuz-3.5.0-030500-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.5.0-030500-generic
Found initrd image: /boot/initrd.img-3.5.0-030500-generic
Found linux image: /boot/vmlinuz-3.5.0-21-generic
Found initrd image: /boot/initrd.img-3.5.0-21-generic
Found linux image: /boot/vmlinuz-3.5.0-17-generic
Found initrd image: /boot/initrd.img-3.5.0-17-generic
Found memtest86+ image: /@/boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda2
done
Setting up linux-image-extra-3.5.0-030500-generic (3.5.0-030500.201301150952) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.5.0-030500-generic /boot/vmlinuz-3.5.0-030500-generic
Traceback (most recent call last):
  File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module>
    import apport
ImportError: No module named apport
Error! Bad return status for module build on kernel: 3....

[Leo (llenchikk)]

@ill
I had same errors.
But kernel appeared in GRUB list and I was able to boot.

[Joseph Salisbury (jsalisbury)]

@ill, when you have a chance, can you also test the v3.8-rc3 kernel and see if it resolves this bug for you? If it does, it might be better for me to perform a reverse bisect to identify the commit that fixes versus continuing a normal bisect to find the bad commit.

[Mario Lopez (mariolcp)]

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc7-raring/ works great on my machine

[Joseph Salisbury (jsalisbury)]

@ill, Can you also test the latest v3.8 kernel and confirm if this bug is resolved or not? If it is, please change the status to Fix Released.

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

[ill (illumilore)]

This bug is about the 3.7 kernels. Why are the 3.8 kernels relevant to this?

[Joseph Salisbury (jsalisbury)]

The 3.7 kernel is not supported in any Ubuntu releases. The 3.8 kernel will be the kernel used for Raring.

[Joseph Salisbury (jsalisbury)]

Is there a reason why you specifically require the 3.7 kernel?

[Kenneth Solbø Andersen (ksa618)]

I was affected by this bug, and have been running on 3.5.0 because of it. Today I decided to try booting with 3.8.0-9, and it worked fine.

[Launchpad Janitor (janitor)]

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

[Joseph Salisbury (jsalisbury)]

The 3.7 kernel is not supported in any Ubuntu release.