Cannot boot in 2.6.31.16 kernel

Bug #499569 reported by Amanda Bee
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I recently installed a bunch of updates, including karmic and an update to the 2.6.31.16 kernel, which hangs on boot. I can boot into the prior kernel fine, though. In /var/log/messages, I see a lot of instances of "ath5k phy0: unsupported jumbo" that correlate to various boot attempts. It gets through a lot of the boot process and then stops with a black screen and a single, unblinking cursor at the top left corner of the screen.

I can interrupt Grub and boot into the prior kernel just fine. So I could just do that, but I'm wondering whether there is more I could do to actually resolve this issue.

Dec 2 08:38:47 brahms kernel: [ 3943.804290] ath5k phy0: unsupported jumbo
Dec 2 08:53:36 brahms -- MARK --
[...]
Dec 2 14:33:36 brahms -- MARK --
Dec 2 14:41:27 brahms kernel: [25703.446882] ath5k phy0: unsupported jumbo

I tried posting this as a question: https://answers.launchpad.net/ubuntu/+question/94883 and got a couple of folks pointing me towards a wireless problem, which I think is different.

I can't boot at all. Well before I see a login screen the boot process hangs and stays hung. The screen is black and the cursor is a non-blinking underline. So I don't think wireless drivers are the issue.

I'm using a Thinkpad x40.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

apport-collect 499569

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Amanda Bee (amandabee) wrote : apport-collect data

AlsaDevices:
 total 0
 drwxr-xr-x 2 root root 80 2009-12-22 17:02 by-path
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp1', '/dev/dsp', '/dev/snd/by-path', '/dev/sequencer2', '/dev/sequencer', '/dev/seq'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card1.Codecs.codec97.0.mc97.1.1:
 1-1/0: Conexant id 23

 Extended modem ID: codec=1 LIN1
 Modem status : PRA(GPIO) PRB(res) PRC(ADC1) PRD(DAC1) PRE(ADC2) PRF(DAC2) PRG(HADC) PRH(HDAC)
 Line1 rate : 8000Hz
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=4839265d-9f8a-4af1-97a8-9413ede840ec
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 2372NU5
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=/dev/mapper/brahms-root ro
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-17.58-generic
RelatedPackageVersions:
 linux-restricted-modules-2.6.28-17-generic 2.6.28-17.22
 linux-firmware 1.25
RfKill: Can't open RFKILL control device: No such file or directory
Uname: Linux 2.6.28-17-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev scanner video
WpaSupplicantLog:

dmi.bios.date: 12/14/2004
dmi.bios.vendor: IBM
dmi.bios.version: 1UET94WW (1.44 )
dmi.board.name: 2372NU5
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: 70002515
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1UET94WW(1.44):bd12/14/2004:svnIBM:pn2372NU5:pvrThinkPadX40:rvnIBM:rn2372NU5:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2372NU5
dmi.product.version: ThinkPad X40
dmi.sys.vendor: IBM

Revision history for this message
Amanda Bee (amandabee) wrote : BootDmesg.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card0.Amixer.info.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card0.Amixer.values.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card0.Codecs.codec97.0.ac97.0.0.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card0.Codecs.codec97.0.ac97.0.0.regs.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card1.Amixer.info.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card1.Amixer.values.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Card1.Codecs.codec97.0.mc97.1.1.regs.txt
Revision history for this message
Amanda Bee (amandabee) wrote : CurrentDmesg.txt
Revision history for this message
Amanda Bee (amandabee) wrote : IwConfig.txt
Revision history for this message
Amanda Bee (amandabee) wrote : Lspci.txt
Revision history for this message
Amanda Bee (amandabee) wrote : PciMultimedia.txt
Revision history for this message
Amanda Bee (amandabee) wrote : ProcCpuinfo.txt
Revision history for this message
Amanda Bee (amandabee) wrote : ProcInterrupts.txt
Revision history for this message
Amanda Bee (amandabee) wrote : ProcModules.txt
Revision history for this message
Amanda Bee (amandabee) wrote : UdevDb.txt
Revision history for this message
Amanda Bee (amandabee) wrote : UdevLog.txt
Revision history for this message
Amanda Bee (amandabee) wrote : WifiSyslog.gz
Revision history for this message
Amanda Bee (amandabee) wrote : XsessionErrors.txt
Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
^_Pepe_^ (jose-angel-fernandez-freire) wrote :

Hi Amanda,

Please, can you confirm that 2.6.31-15 kernel worked normally?

Thanks in advance.

tags: added: karmic
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Amanda Bee (amandabee) wrote :

Pepe,

Yes, 2.6.31-15 worked normally as far as I could tell.

Thanks,
Amanda

Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: regression-potential
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Amanda,

Can you boot the 2.6.31-16 kernel but remove the "quiet" and "splash" boot options:

https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Bootloader

Are there any errors printed to the screen prior to the hang? If so you paste the messages here (maybe take a digital photo of your screen and attach it). Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

It also might not hurt to try the even newer 2.6.31-17.54 kernel update. Thanks.

Revision history for this message
Amanda Bee (amandabee) wrote :

Thanks Leann. It took me a bit to get to this. Answers:

I'm not getting any errors. Just a cursor at the top left corner of the black screen. Nothing else. The last thing I see before it switches over to the blank screen is "Starting AppArmor profiles" -- it runs through a bunch of stuff and then says:

Preparing Restricted Drivers ...
Starting AppArmor profiles ...

Disabling "quiet" doesn't do anything for me. I don't have a "splash" option set that I could find in my kernel parameters. Starting in the "recovery mode" does get me to a shell with 2.6.31.16.

While mucking around in /boot/grub/menu.lst I did find the option to stop hiding the list of available kernels. Which makes booting up at least a little easier.

Revision history for this message
Amanda Bee (amandabee) wrote :

Okay: I spent some time reviewing syslogs and it seems that I have some major disk corruption going on (tons of null characters followed by a dump of some random config file in the syslog, for instance). Which would be consistent with the 2.6.31.x kernels borking since (this is where it gets a little foggy) something changed in the way that graphics are loaded with these kernels.

So I've still got problems but my problem is probably not with the kernel.

Revision history for this message
Andy Whitcroft (apw) wrote :

When you see the black screen does attempting to switch VT to VT-7 help any? It sounds a bit like the plymouth race condition. You could try booting without 'splash' on the kernel command line to see if that helps.

Revision history for this message
Amanda Bee (amandabee) wrote :

Andy ... I'm afraid the only VT I know is the green mountain state. It is too short a term to feed to the borg for assistance, too.

(however, see my last comment, re. disk corruption)

tags: added: regression-update
removed: regression-potential
Revision history for this message
Brian Murray (brian-murray) wrote :

I've removed the regression tag since this is likely a hardware issue and not kernel related.

tags: removed: regression-update
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.