Bug 473142 - System hang after wireless connection with NM is completed
Summary: System hang after wireless connection with NM is completed
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 11
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 513462
TreeView+ depends on / blocked
Reported: 2008-11-26 19:06 UTC by Jurgen Kramer
Modified: 2010-06-28 10:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-28 10:50:24 UTC
Type: ---

Attachments (Terms of Use)
dmesg output up to hang (53.87 KB, text/plain)
2008-11-26 19:06 UTC, Jurgen Kramer
no flags Details

Description Jurgen Kramer 2008-11-26 19:06:36 UTC
Created attachment 324778 [details]
dmesg output up to hang

Description of problem:
Complete system hang after NM connects to my wireless network

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

How reproducible:

Steps to Reproduce:
1. Boot in level 5
2. Login to system
3. NM connects to wireless network
Actual results:
System hang after connection is made

Expected results:
Normal functioning system after wireless connection is ready

Additional info:
System: Asus R50A UMPC
Wireless driver: libertas_sdio
Encryption used: WPA-PSK

When using the wireless card from the shell in level 3 (manual connection with wpa_supplicant) the wireless connection works flawlessly. I can even download and install 150MB of updates without problem.

When in X NM shows my and other neighbouring networks with their signal levels just fine. But after the connection is made, complete system hang.

When giving NM the wrong password for my network, it tries to connect and fails (obviously). System keeps working normally after that.

Comment 1 Jurgen Kramer 2008-11-26 19:17:37 UTC
Current running kernel is actually: kernel-

Comment 2 Dan Williams 2008-11-28 17:37:17 UTC
If the box ever hangs, it's a kernel problem, not a NetworkManager problem.  The issue is likely that the driver/hardware don't properly handle concurrent requests sometimes, and I know that's the case because I'm also the libertas driver maintainer upstream :)

What exact Libertas 8686 firmware version are you running, and where did you get it from?

Comment 3 Jurgen Kramer 2008-11-29 09:33:50 UTC
I guess you are right it being a kernel problem :). I hope this is fixable.

I've downloaded the firmware directly from the Marvell site (filename: SD-8686-LINUX26-SYSKT-9.70.3.p24-26409.P45-GPL.zip). The driver reports it as: 

libertas: 00:19:88:05:7e:84, fw 9.70.3p24, cap 0x00000303

I could not find any other version on the net.

BTW building and testing a out-of-kernel driver to test is not a problem :)

sha1sum's of the firmware files are:
89bf5c3c0711ab5f1957f426d4268d53a29b231d  helper_sd.bin
6afc08a13682833bae9374456b217a9e1847d707  sd8686.bin

Comment 4 Jurgen Kramer 2008-12-05 16:56:59 UTC
I did some more testing. Enabling libertas debugging does not really help, the generated messages cannot be captured :(. I've also tried a connection with any encryption, the system still hangs solid after the IP address is registered.

BTW I tried a prerelease of Ubunty Jaunty (build 5-dec-08), the results are exactly the same. The also use a 2.6.27 kernel.

Anyway to move this further?

Comment 5 Jurgen Kramer 2009-03-13 14:28:19 UTC
Sorry to see this bug is not being picked up yet...

With the latest rawhide the problem still persists. The wireless adapter still works great when started from the command line but with NM it locks up the system after the connection is completed.

BTW the hard lock prevents me from getting anything useful from the log messages.

Comment 6 Bug Zapper 2009-06-09 09:56:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:

Comment 7 Dan Williams 2009-11-06 06:57:19 UTC
Does this happen on later kernels, specifically 2.6.29 and later?

Comment 8 Jurgen Kramer 2009-11-06 08:08:51 UTC
Sorry, I no longer have the hardware. So I am not able to test it further. I guess this bug can be closed.

Comment 9 Bug Zapper 2010-04-27 12:22:53 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 

Comment 10 Bug Zapper 2010-06-28 10:50:24 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.