regular kernel panic on Ubuntu 11.10

[pnael]

I get regular kernel panic since I installed Ubuntu 11.10. I don't have any specific steps to reproduce it. Sometimes it is every 10 minutes sometimes I can work several hours without any issues.

WORKAROUND: sudo touch /etc/pm/power.d/wireless

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.20
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: philippe 1579 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Generic'/'HD-Audio Generic at 0xd0244000 irq 42'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card0.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Card1.Amixer.info:
 Card hw:1 'SB'/'HDA ATI SB at 0xd0240000 irq 16'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,103c1611,00100105'
   Controls : 14
   Simple ctrls : 9
Date: Thu Oct 20 17:22:33 2011
HibernationDevice: RESUME=UUID=77fa59e0-3741-4a24-a442-2fea7c55e87e
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=43c5cd62-3883-47cf-a5e8-0608d907c022 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.12
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1611
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.39
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.12:bd04/26/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr0589100000252B00000320100:rvnHewlett-Packard:rn1611:rvr96.39:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm1 Notebook PC
dmi.product.version: 0589100000252B00000320100
dmi.sys.vendor: Hewlett-Packard

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

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

Thanks in advance.

[pnael (philippe-nael)]

tested linux-image-3.1.0-030100rc10-generic without success. Got a kernel panic

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to capture a screen shot of the panic information when it happens again?

[Joseph Salisbury (jsalisbury)]

Also, this issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[ZigBee (kozinov)]

I can confirm this problem. Same occurs on my hp dm1 after update to 11.10. Also i'm not sure this is kernel related bug. Ubuntu 11.04 with custom 3.0.4 kernel (with default ubuntu config and patchset) works like a charm. May be i'm wrong.

[pnael (philippe-nael)]

Yes 3.0.4 kernel seems stable. I'll do additionnal tests with 3.1.0.

I'll publish then the panic information.

[pnael (philippe-nael)]

panic pictures are attached (sorry for the bad quality but I don't have a good camera available).
All kernels are crashing from 3.0.0 to 3.1.0 including 3.0.4.
It crashes only when the laptop is on battery. I can work for hours when using ac, then switching to battery will make a kernel panic usually within a few minutes.
Philippe

[Joseph Salisbury (jsalisbury)]

@pnael,

This may be a duplicate of bug 869502. Can you refer to comment #50 in that bug? Basically we would like you to test the following two kernels and see if the issue happens on v3.0.7 and not v3.0.6:

v3.0.6 - http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.6-oneiric/

v3.0.7 - http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.7-oneiric/

[pnael (philippe-nael)]

v 3.0.6 does panic. I'll test 3.0.7 later.

If i read the comment from the other bug, it may be link ith the wireless card.
One difference when working on battery is power management is set to on.
I'll disable it and do some extra tests (including 3.0.7 testing) and update you.
My test :

philippe@heracles:~$ iwconfig wlan0 # with power adapter
wlan0 IEEE 802.11bgn ESSID:"nael_ssid"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:19:70:59:62:9A
          Bit Rate=19.5 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=33/70 Signal level=-77 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:23 Invalid misc:145 Missed beacon:0
philippe@heracles:~$ iwconfig wlan0 # on battery
wlan0 IEEE 802.11bgn ESSID:"nael_ssid"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:19:70:59:62:9A
          Bit Rate=39 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=35/70 Signal level=-75 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:23 Invalid misc:145 Missed beacon:0

philippe@heracles:~$ sudo iwconfig wlan0 power off
philippe@heracles:~$ iwconfig wlan0 # on battery
wlan0 IEEE 802.11bgn ESSID:"nael_ssid"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:19:70:59:62:9A
          Bit Rate=39 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=33/70 Signal level=-77 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:23 Invalid misc:145 Missed beacon:0

[pnael (philippe-nael)]

Results of the testing.

3.0.0 : kernel panic on battery mode
3.0.4 : kernel panic on battery mode
3.0.6 : kernel panic on battery mode
3.0.7 : crash but I was unable to get a panic screen. The laptop fully freezes regularly.
3.1.0 : kernel panic on battery mode

Then I start again some testing by disabling power management on wlan0 ("sudo iwconfig wlan power off")
3.0.0 : no crash after 6 hours
3.0.6 : no crash after 4 hours
3.0.7 : no crash after 3 hours

I am not 100% sure since this can be very random but it looks the issue has something to do with the power management of the wireless card module.

[ddave01 (ddave01)]

I have just upgraded four netbooks to 11.10. Two Wind (Medion E1210) and two EEEpc.

One Wind netbook goes into panic when on battery and I believe it is related to wireless adapter.

The wireless connection has at times difficulty connecting. Timing out but eventually connects.

The second Wind netbook has not had a panic but it has no battery and runs on mains only.

The Asus EEEpc whilst on battery just now went into panic and attached is photo of the screen.

[Woody (wo0dy)]

This is also an issue with ubuntu 11.10 on Dell latitude D610 when on AC power.
Attached is a screen shot.

[geoland (cheshire-r)]

Toshiba dynabook - less frequent with 3.0.0-12. With previous kernel versions when using a browser. Often, soon after coming out of suspend. Unable to get screen shot.

[michael (elefantenmann2)]

Same problem here, kernel panic occurs with ubuntu 11.10 when on battery power. It does not occur on ac power.

[pnael (philippe-nael)]

For me as a workaround, you just need to disable powersaving mode on the wireless card :
>sudo touch /etc/pm/power.d/wireless

[Bogdan Radu (bog-radu)]

The workaround Philippe Nael wrote (comment #17) works for me. I went from getting a kernel panic within 5 minutes of going into battery mode to not getting it for the duration of my Eee 1000HE's battery life (so, hours)

[penalvch (penalvch)]

pnael, 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 test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[pnael (philippe-nael)]

Hello. I guess this ticket should be closed now. I used the workaround for
some time and now with 13.10 & 13.04 I had no issue anymore.

Regards

Philippe
Le 9 nov. 2013 19:10, "Christopher M. Penalver" <
<email address hidden>> a écrit :

> pnael, 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 test for this with the latest development release
> of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
> /daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available (not the
> daily folder, but the one all the way at the bottom) following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Once you've tested the upstream
> kernel, please comment on which kernel version specifically you tested. If
> this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.12
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
>
> ** Description changed:
>
> - I get regular kernel panic since I installed Ubuntu 11.10. I don't have
> any specific steps to reproduce it.
> - Sometimes it is every 10 minutes sometimes I can work several hours
> without any issues.
> + I get regular kernel panic since I installed Ubuntu 11.10. I don't have
> + any specific steps to reproduce it. Sometimes it is every 10 minutes
> + sometimes I can work several hours without any issues.
>
> - It is installed on a HP dm1 laptop.
> + WORKAROUND: sudo touch /etc/pm/power.d/wireless
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.10
> Package: linux-image-3.0.0-12-generic 3.0.0-12.20
> ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
> Uname: Linux 3.0.0-12-generic i686
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
> ApportVersion: 1.23-0ubuntu3
> Architecture: i386
> ArecordDevices:
> - **** List of CAPTURE Hardware Devices ****
> - card 1: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
> - Subdevices: 1/1
> - Subdevice #0: subdevice #0
> + **** List of CAPTURE Hardware Devices *...

[penalvch (penalvch)]

pnael, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/878919/comments/20 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.