Bug 806655 - Intel 6230N cannot maintain AP association with kernel-3.3.0-4.fc16.x86_64
Summary: Intel 6230N cannot maintain AP association with kernel-3.3.0-4.fc16.x86_64
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-25 19:10 UTC by neochi808
Modified: 2013-02-13 13:54 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 13:54:21 UTC
Type: ---


Attachments (Terms of Use)
dmesg kernel-3.3.0-4.fc16.x86_64 (122.76 KB, text/plain)
2012-03-27 04:18 UTC, neochi808
no flags Details
dmesg kernel-3.2.9-2.fc16.x86_64 (107.48 KB, text/plain)
2012-03-27 04:19 UTC, neochi808
no flags Details

Description neochi808 2012-03-25 19:10:09 UTC
Description of problem: Updated to kernel-3.3.0-4.fc16.x86_64
No longer maintain link with wireless access point.

Version-Release number of selected component (if applicable):
kernel-3.3.0-4.fc16.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot kernel-3.3.0-4.fc16.x86_64
2. Login to GNOME desktop
3. Wireless network connection keeps cycling last AP
  
Actual results:
Cannot maintain association with AP

Expected results:
Works fine with kernel-3.2.9-2.fc16.x86_64

Additional info:
Using Intel 6230N wireless/bluetooth mini-pcie

Comment 1 John W. Linville 2012-03-26 17:15:22 UTC
It is difficult to know where to start -- the wireless code in those two kernels should be identical.

Please attach the output of running 'dmesg' after a few connection attempts.

Comment 2 neochi808 2012-03-27 04:18:27 UTC
Created attachment 572919 [details]
dmesg kernel-3.3.0-4.fc16.x86_64

Comment 3 neochi808 2012-03-27 04:19:51 UTC
Created attachment 572920 [details]
dmesg kernel-3.2.9-2.fc16.x86_64

attached for comparison

Comment 4 John W. Linville 2012-03-27 13:05:05 UTC
I think this has something to do with how NetworkManager handles IPv6 configuration failures.  I understand that the version in Rawhide might address this issue.

In the meantime, you should edit your wireless connection, and set IPV6 Settings to Ignore.  That should prevent the disconnection loop.

Comment 5 John W. Linville 2012-03-27 13:15:37 UTC
See bug 785772 and bug 806932 for more information.

Comment 6 neochi808 2012-03-29 16:16:55 UTC
(In reply to comment #4)
> I think this has something to do with how NetworkManager handles IPv6
> configuration failures.  I understand that the version in Rawhide might address
> this issue.
> 
> In the meantime, you should edit your wireless connection, and set IPV6
> Settings to Ignore.  That should prevent the disconnection loop.


IPV6 is already set to ignore, does not appear related to bug 806932.
It's the same version on NM running between kernel versions, yet booting into kernel-3.3.0-4.fc16.x86_64 doesn't maintain association with my AP.


Is the version in rawhide newer than the upcoming 17 Beta?

Comment 7 neochi808 2012-04-01 06:08:20 UTC
Boot kernel: append ipv6.disable=1
Issue not observed.

Appears IP6 related.

Comment 8 Fedora End Of Life 2013-01-16 13:12:12 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Fedora End Of Life 2013-02-13 13:54:25 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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