Kernel Panic 2.6.35-9.14

[fleamour]

Can reliably produce kernel panic (Caps Lock/Scroll Lock flashing & freeze) on latest Maverick kernel when removing power jack when battery full on IBM T21 ThinkPad laptop. I do not think this was an issue on earlier kernels.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-9-generic 2.6.35-9.14
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: CS46xx [Sound Fusion CS46xx], device 0: CS46xx [CS46xx]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CS46xx'/'Sound Fusion CS46xx at 0xe8100000/0xe8000000, irq 11'
   Mixer name : 'Cirrus Logic CS4297A rev 4'
   Components : 'AC97a:43525914'
   Controls : 45
   Simple ctrls : 26
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown'
   Mixer name : 'ThinkPad EC (unknown)'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 3 [21%] [on]
Date: Wed Jul 21 15:00:20 2010
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=d1e10cd4-47af-476e-a427-c87193edca08
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 26474BU
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-9-generic root=UUID=83e79ee4-5a3b-4be2-8c75-9039a47232bb ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.37
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 04/28/2004
dmi.bios.vendor: IBM
dmi.bios.version: KZET34WW (1.16 )
dmi.board.name: 26474BU
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvrKZET34WW(1.16):bd04/28/2004:svnIBM:pn26474BU:pvrNotAvailable:rvnIBM:rn26474BU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 26474BU
dmi.product.version: Not Available
dmi.sys.vendor: IBM

[fleamour (gtx-swift)]

Also random freeze with 2.6.35-8 & system will now not boot from any kernel. Will rewind to Lucid.

[Charlie Kravetz (cjkgeek)]

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[aleritty (aleritty)]

Also for me, only on maverick (i upgraded from lucid) the system completely freeze when I disconnect the power cable.
I my case the notebook freeze without kernel-panic blinkin' keyboard.

I'm on a different brand computer: acer aspire notebook, i don't know what package investigate to find more useful information.

[Charlie Kravetz (cjkgeek)]

aleritty: Please file a new bug by opeing the Terminal, and typing ubuntu-bug linux

This will attach the needed files to your bug, and give the developers a chance to see how to fix it. Thanks for helping.

[aleritty (aleritty)]

I filed this bug (i don't know why but was impossible to me add the data to this bug):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/665624

My bug is slightly different because my keyboard doent'blink and my system doesn't respond to sysrq!

[Joseph Salisbury (jsalisbury)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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