Bug 4515 - cfg80211 continually toggles wifi connectivity and calls CRDA
Summary: cfg80211 continually toggles wifi connectivity and calls CRDA
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-13 20:55 CET by Pierre Fortin
Modified: 2012-11-05 17:55 CET (History)
0 users

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description Pierre Fortin 2012-02-13 20:55:08 CET
Description of problem:  Before getting a kernel update on Feb 1, my wireless was working well. Then, kernel-desktop-2.6.38.8-10.mga-1-1.mga1.x86_64 and other packages got installed as part of regular updates.  Since then, my wireless card has been unusable.  Even starting up with the previous 2.6.38.7-tmb-laptop-1.mga, the wireless is unusable.  After many resolution attempts, I decided that the Broadcom based card was less than Linux friendly, and purchased an Intel WiMax 6250 card.    Sadly, it too is unstable with the same errors.  

/var/log/messages is FULL of these every 2-3 seconds:
[each line was prefixed with:
    Feb 13 13:44:54 hg kernel: cfg80211: 
 removed to avoid wrapping...]

Calling CRDA to update world regulatory domain
World regulatory domain updated:
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Calling CRDA for country: US
Regulatory domain changed to country: US
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
    (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

Updated; changed to US; updated; changed to US;............  :(

I've searched for all manner of variations for:
  wireless cfg80211 wpa_supplicant crda regulatory bouncing toggling
etc, all to no avail...  every time a "solution" looked promising... no go!


Version-Release number of selected component (if applicable):
kernel-desktop-2.6.38.8-10.mga-1-1.mga1.x86_64 et al...

Today, tried booting Windows 7, and after loading WiMax 6250 driver, all is well there.

There are hundreds of reports regarding this problem, including on wireless.kernel.org; but no solution that works here.

How reproducible:
Always. Forced to use wired network.

Steps to Reproduce:
1.  Run Mageia 1 pre-Feb 1 (earlier?)
2.  Apply updates 
3.  wireless now useless.
Comment 1 Manuel Hiebel 2012-02-14 00:24:41 CET
what is the output of lspcidrake -v ?

>There are hundreds of reports regarding this problem, including on
>wireless.kernel.org; but no solution that works here.
Then we can do nothing.

maybe it was the update of the broadcom-wl-driver.

I have also those line (with an bcm4313) but it works.
Manuel Hiebel 2012-02-14 00:32:59 CET

Source RPM: (none) => kernel

Comment 2 Pierre Fortin 2012-02-14 00:46:17 CET
Pushing it to kernel will probably get a "try kernel-3.x"...  :)  Is there a more recent kernel I can try?  Not really up to building my own kernel nowadays; too busy... and last time was 6-7 years ago...

Updated broadcom-wl-driver doesn't explain why "iwlagn" produces same results...

The wireless connects for a few seconds, then disconnects, then....ad nauseum, and the status is down during those intervals, so connections fail.  :(

Cheers
Comment 3 Manuel Hiebel 2012-11-05 16:51:04 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 
Mageia version prior to Mageia 1'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 Mageia 1 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 Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Pierre Fortin 2012-11-05 17:55:12 CET

Status: NEW => RESOLVED
Resolution: (none) => OLD


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