Bug 923394 - oops when suspending with bluetooth networking in use
Summary: oops when suspending with bluetooth networking in use
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-19 18:14 UTC by Allison Karlitskaya
Modified: 2013-07-24 18:56 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-24 18:56:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg of the crash, from UEFI pstore (10.11 KB, text/plain)
2013-03-19 18:14 UTC, Allison Karlitskaya
no flags Details

Description Allison Karlitskaya 2013-03-19 18:14:34 UTC
Created attachment 712875 [details]
dmesg of the crash, from UEFI pstore

Description of problem:

I have an N9 and I often use bluetooth tethering to get online when away from home.  If I suspend my laptop without first disconnecting from my phone then 'bad things' happen.

Bad things are sometimes that the suspend doesn't complete and I get a black screen, or that I get the black screen on wakeup.  Sometimes the machine will wake up, but very quickly I will notice problems (like inability to create new processes).

Sometimes I get a straight kernel panic on suspend.

Version-Release number of selected component (if applicable):

This is stock Fedora 18.  Kernel is 3.8.2-206.fc18.x86_64.

How reproducible:

Something goes wrong 100% of the time.  It's often a kernel panic.

Steps to Reproduce:
1. Pair a phone with a DUN profile.  Set it up for tethering.
2. Connect under the "Mobile Broadband" section in the gnome-shell network menu.
3. Close the laptop lid.
  
Actual results:

Sometimes a panic (flashing caps lock LED), sometimes other 'bad things' as described above.

Expected results:

Suspend with working resume.  Probably should disconnect from the phone as well.

Additional info:

With mjg59's help I managed to pull a dmesg of the crash out of UEFI pstore.  I attach that here.

Comment 1 Josh Boyer 2013-07-02 19:16:34 UTC
Are you still seeing this with 3.9.8 or newer?

Comment 2 Josh Boyer 2013-07-24 18:56:31 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.