Bug 436595 - 2.6.24.3 hard system hang during bluetooth association
Summary: 2.6.24.3 hard system hang during bluetooth association
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-08 07:22 UTC by Stephen Warren
Modified: 2008-09-05 05:13 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-09-05 05:13:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stephen Warren 2008-03-08 07:22:10 UTC
Description of problem:
I just got a phone with bluetooth and was experimenting trying to get bitpim
working with it. Under 2.6.23.15-137, I could pair my laptop and the phone
(although that's about as far as I could get). Under 2.6.24.3-12, once I've
completed the pairing process, a notification pops up on the laptop about
"creating binding" or someting like that. At this point, the capslock and
scroll-lock LEDs on my keyboard start flasing about once a second, and the
system is locked up hard.

This is a Dell Inspiron 9300 laptop with built-in Bluetooth adapter, and a
Verizon LG VX8350 phone.

Version-Release number of selected component (if applicable):
kernel-2.6.24.3-12.fc8.i686

How reproducible:
Tried twice, happened twice.

Steps to Reproduce:
1. Enable laptop to be visible over bluetooth
2. On phone, search for devices to pair with, see laptop, and select it.
3. Enter PIN on phone
4. Respond to notification on laptop about pairing request. Type PIN there
5. Pairing process is basically done. After a very short time, the laptop hangs
hard.
  
Actual results:
System hangs.

Expected results:
System doesn't hang

Additional info:
N/A

Comment 1 Stephen Warren 2008-03-18 04:34:36 UTC
kernel-2.6.24.3-34.fc8.i686 doesn't fix this.


Comment 2 Stephen Warren 2008-09-05 05:13:02 UTC
Closing; this issue is no longer present in kernel-2.6.25.14-108.fc9.i686.


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