Bug 1035056 - Wifi connection to WPA2 enterprise drop and need reboot to reconnect
Summary: Wifi connection to WPA2 enterprise drop and need reboot to reconnect
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-27 00:46 UTC by Lei Peng
Modified: 2015-08-31 15:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 14:42:20 UTC
Type: Bug


Attachments (Terms of Use)

Description Lei Peng 2013-11-27 00:46:24 UTC
Description of problem:

The wifi connection to a WPA2/PEAP wifi disconnected after random time from minutes to hours. Network manager tried to reconnect but failed. Only reboot can fix the problem.


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

Can't tell from which kernel version the problem started. There was no such problem when the fedora 19 first installed. 

The problem lasted with kernel 3.11.7-200.fc19.x86_64, interestingly disappeared with 3.11.8-200.fc19.x86_64 and happened again with 3.11.9-200.fc19.x86_64

Wireless controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]


How reproducible:
Connect to WPA2/PEAP and use the computer for a while until wifi connection failed.

Steps to Reproduce:
1.
2.
3.

Actual results:
Unable to reconnect unless reboot.

Expected results:


Additional info:

Info. from /var/log/message when problem occurred:
Nov 27 10:40:02 localhost NetworkManager[503]: <warn> Connection disconnected (reason -4)
Nov 27 10:40:02 localhost kernel: [ 3657.861548] cfg80211: Calling CRDA to update world regulatory domain
Nov 27 10:40:02 localhost NetworkManager[503]: <info> (wlp3s0): supplicant interface state: completed -> disconnected
Nov 27 10:40:02 localhost kernel: [ 3657.873524] cfg80211: World regulatory domain updated:
Nov 27 10:40:02 localhost kernel: [ 3657.873530] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 27 10:40:02 localhost kernel: [ 3657.873533] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.873536] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.873539] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.873541] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.873543] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.873575] cfg80211: Calling CRDA for country: AU
Nov 27 10:40:02 localhost kernel: [ 3657.877543] cfg80211: Regulatory domain changed to country: AU
Nov 27 10:40:02 localhost kernel: [ 3657.877549] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov 27 10:40:02 localhost kernel: [ 3657.877553] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.877556] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.877558] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2300 mBm)
Nov 27 10:40:02 localhost kernel: [ 3657.877560] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
Nov 27 10:40:02 localhost NetworkManager[503]: <info> (wlp3s0): supplicant interface state: disconnected -> scanning
Nov 27 10:40:02 localhost kernel: [ 3658.085543] wlp3s0: authenticate with ac:16:2d:de:56:70
Nov 27 10:40:02 localhost kernel: [ 3658.097142] wlp3s0: send auth to ac:16:2d:de:56:70 (try 1/3)
Nov 27 10:40:02 localhost NetworkManager[503]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
Nov 27 10:40:03 localhost kernel: [ 3659.331617] wlp3s0: send auth to ac:16:2d:de:56:70 (try 2/3)
Nov 27 10:40:04 localhost kernel: [ 3660.340760] wlp3s0: send auth to ac:16:2d:de:56:70 (try 3/3)
Nov 27 10:40:05 localhost NetworkManager[503]: <info> (wlp3s0): roamed from BSSID AC:16:2D:DE:56:70 (RMIT-University) to (none) ((none))
Nov 27 10:40:05 localhost kernel: [ 3661.340958] wlp3s0: authentication with ac:16:2d:de:56:70 timed out
Nov 27 10:40:05 localhost NetworkManager[503]: <info> (wlp3s0): supplicant interface state: authenticating -> disconnected

Comment 1 Lei Peng 2013-12-05 02:59:41 UTC
No one paid attention on this subject? Actually it's very annoying.

Comment 2 Lei Peng 2013-12-10 04:25:24 UTC
Just have the kernel updated to 3.11.10. Problem remains. Found a similar bug report:

https://bugzilla.redhat.com/show_bug.cgi?id=1020018

But the problem looks different from the message file.

Comment 3 Justin M. Forbes 2014-01-03 22:05:47 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 4 Michele Baldessari 2014-01-04 12:54:07 UTC
Hi Lei,

can you test with kernel 3.12.6-200.fc19 and also attach lspci -nvvv and dmidecode to this bz please?

Thanks,
Michele

Comment 5 Justin M. Forbes 2014-03-10 14:42:20 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.

Comment 6 Lei Peng 2014-06-09 11:35:34 UTC
Hi Michele, sorry for late response. It has been a long time since the problem disappeared. Unfortunately, I can't recall the kernel version which fixed it. Anyway, it's good to have a no bug wifi connection since then. 

Thanks,
Lei

Comment 7 Lei Peng 2015-08-31 15:33:22 UTC
Just ensure the closure.


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