Bug 61431 - When a DUN connection is disconnected and reconnect using a Wireless connection the system freezes totally
Summary: When a DUN connection is disconnected and reconnect using a Wireless connecti...
Status: CLOSED OBSOLETE
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-16 09:24 UTC by Nix\
Modified: 2014-05-08 05:38 UTC (History)
4 users (show)

See Also:
Kernel Version: >= 3.8, 3.10.12
Subsystem:
Regression: No
Bisected commit-id:

Attachments
config file used in 3.10.12 kernel (99.94 KB, application/octet-stream)
2013-09-16 09:24 UTC, Nix\ 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Nix\ 2013-09-16 09:24:16 UTC 
Created attachment 108471 [details]
config file used in 3.10.12 kernel

system: CentOS 6.4 i686
SELinux enabled: yes
bug kernel tested: 3.10.12
non-bug kernel tested: 3.4.61 3.4.62 3.2.50 3.2.51
When?: Always
custom cmdline: security=selinux selinux=1 nordrand crashkernel=0@0
hardware: Lenovo t400
wifi card: 03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
External tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165433

When a DUN connection is enabled using network manager from gnome 2.28 on CentOS 6.4 i686, and is disconnected and later reconnect to a wireless WiFi connection the system freezes totally or kernel panic.

3.4.x branch is not affected. The bug is reported in launchpad, and still since 3.8 branch, so the regression is introduced in 3.8 and still in 3.10.12 stable long term.

Steps to reproduce it:

1.- Use a vanilla kernel 3.10.12
2.- Connect a DUN connection to a cellphone using network manager
3.- Disconnect the DUN connection from network manager
4.- Connect to a WiFi connection
5.- Crash

Attach .config of 3.10.12.
Comment 1 John W. Linville 2013-09-16 12:43:58 UTC 
Hmmm...not sure if this is Bluetooth or 802.11 driver...
Comment 2 Nix\ 2013-09-17 12:48:12 UTC 
(In reply to John W. Linville from comment #1)
> Hmmm...not sure if this is Bluetooth or 802.11 driver...

No idea, but using 3.4.x and 3.2.x no problems. The bug was introduced in 3.8 branch.
Comment 3 Emmanuel Grumbach 2014-03-18 06:18:02 UTC 
does the bug still occur on recent kernel?
Note You need to log in before you can comment on or make changes to this bug.