All kernel's after 2.6.35-32-generic fail to boot

[Allan Shand]

I am currently running Ubuntu 10.10 however I have tried running 11.04/11.10 and 12.04(daily build) all of these have failed to boot during the kernel load sequence. Viewing the verbose boot the load stalls at this line

ohci_hcd 0000:00:12.1: irq 16, io mem 0xfe02d000

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-32-generic 2.6.35-32.66
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-32.66-generic 2.6.35.14
Uname: Linux 2.6.35-32-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: allan 2082 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 41
   Simple ctrls : 23
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Wed Feb 29 20:48:46 2012
HibernationDevice: RESUME=UUID=f469aa48-17db-4e4b-9157-ce50f3849eff
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-US2H
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-32-generic root=UUID=7a53d731-dcd9-4277-afd7-ddbe204e91c2 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38.10
RfKill:

SourcePackage: linux
dmi.bios.date: 12/15/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: GA-MA78GM-US2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/15/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78GM-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78GM-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA78GM-US2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
---
Architecture: amd64
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: maverick
Uname: Linux 3.3.0-030300rc5-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
---
Architecture: amd64
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: linux (not installed)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
Tags: maverick
Uname: Linux 3.3.0-030300rc6-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc5 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc5'.

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.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Allan Shand (ashand79)]

OK I have done a quick test with the 3.3 kernel installed on 10.10.

The kernel "technically" booted but there were a few soft reset errors then plymouth for a second or less then a lot of display flickering and finally a tty1 prompt.

Which logs would you like me to up-load and when should I get the log when logged in to the 3.3 kernel? or otherwise?

Thanks for the help

Allan

[Joseph Salisbury (jsalisbury)]

It would be great if you could run apport again with:
apport-collect 943585

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Allan Shand (ashand79)]

added "bot-stop-nagging" tag and changed status back to Confirmed as the kernel which has been tested is v3.3-rc5-precise

[Joseph Salisbury (jsalisbury)]

The v3.3-rc6 kernel was recently released. Would it be possible for you to test that kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc6-precise/

[Allan Shand (ashand79)]

Just did another apport-collect on the new kernel. Now when I booted using both these kernels I get these messages at boot

ata1:Softreset failed (device not ready)
ata3:Softreset failed (device not ready)

I think the ata1 message appears twice however the system boots. Also while installing the kernel I noticed a [fail] message when configuring the fglrx driver so I took a chance and disabled the fglrx driver and I was able to boot to the desktop.

So is it because the fglrx driver is for Ubuntu 10.10 and the Kernel is not, that they are having problems or is it a deeper problem than that?

[Joseph Salisbury (jsalisbury)]

Are you able to boot with the latest precise kernel[0] if you have fglrx disabled?

[0] https://launchpad.net/ubuntu/+source/linux/3.2.0-18.28/+build/3254748

[Allan Shand (ashand79)]

I have tested with the latest daily live image which contains the 3.2.0-18.28 but no dice it refuses to boot haven't done a verbose live boot yet I will try that in the next few days

[penalvch (penalvch)]

Allan Shand, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, 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 kernel in 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 and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream-VERSION-NUMBER', where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Launchpad Janitor (janitor)]

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