[STAGING] Kernel panic after wake up from Hibernating/Suspending, in battery mode, using r8187se

Bug #665718 reported by amishaa
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Kernel panic after wake up from Hibernating/Suspending, in battery mode, using r8187se.
Every time I Suspend and then wake up, kernel panic happens.
If I rmmod r8187se it's doesn't happens.
http://pastebin.com/egrt5PL0 , http://pastebin.com/KdKeGf1c , http://pastebin.com/G8zHfUCU , http://pastebin.com/Wq9SZhdW
is syslog, messeges, debug and dmesg logs part containing full log between wake up and panic.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: misha 2203 F.... pulseaudio
CRDA: Error: [Errno 2] Нет такого файла или каталога
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd6300000 irq 49'
   Mixer name : 'Realtek ALC272'
   Components : 'HDA:10ec0272,1179ff88,00100001'
   Controls : 17
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd6210000 irq 50'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   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: Sun Oct 24 01:41:21 2010
HibernationDevice: RESUME=UUID=46b535a2-2fda-46f2-bd11-2209566e146b
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: TOSHIBA Satellite L500
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=UUID=38939dcd-861f-4064-8b57-ed102bc14240 ro quiet splash acpi_oci=Linux
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
StagingDrivers: r8187se
Title: [STAGING]
dmi.bios.date: 02/12/10
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.50
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NSWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 9
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvr1.50:bd02/12/10:svnTOSHIBA:pnSatelliteL500:pvrPSLS9E-02D00GRU:rvnTOSHIBA:rnNSWAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A:
dmi.product.name: Satellite L500
dmi.product.version: PSLS9E-02D00GRU
dmi.sys.vendor: TOSHIBA

Revision history for this message
amishaa (amishaa) wrote :
Revision history for this message
Robie Basak (racb) wrote :

This could be a duplicate of bug 663784; there's a workaround described there. I think the common factor might be the r8187se module.

Revision history for this message
Tim Thomas (tim-loadedguntheory) wrote :

The fix in 663784 worked for me.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

amishaa, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please 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'.

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'.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Remote bug watches

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