Bug 15893 - wl module works but spews out error messages.
Summary: wl module works but spews out error messages.
Status: RESOLVED DUPLICATE of bug 16390
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-09 05:42 CEST by w unruh
Modified: 2016-06-15 17:13 CEST (History)
2 users (show)

See Also:
Source RPM: broadcom-wl
CVE:
Status comment:


Attachments
/var/log/messages kernel warning dump on loading module (19.43 KB, application/octet-stream)
2015-05-09 06:44 CEST, w unruh
Details

Description w unruh 2015-05-09 05:42:28 CEST
Description of problem: The broadcom-wl module (wl.ko.xz) works (ie connects well) but spews out error messages, both on installation and on running. 

The constant error message is 

03:56:53 syzygy kernel: [18940.770393] ERROR @wl_dev_intvar_get : error (-1)
May  9 03:56:53 syzygy kernel: [18940.770397] ERROR @wl_cfg80211_get_tx_power : error (-1)
This occurs about once a minute while the wireless is in use. 

In addition, on loading, a bunch of kernel error/warning dumps occur (see the attachment)
This occurs about 3 times on loading the module.





Version-Release number of selected component (if applicable): broadcom-wl-kernel-3.19.6-desktop-2.mga5-6.30.223.248-26.mga5.nonfree

(This was also a problem with 3.19.3)





Reproducible: 

Steps to Reproduce:
Comment 1 w unruh 2015-05-09 06:44:54 CEST
Created attachment 6482 [details]
/var/log/messages kernel warning dump on loading module

This is a kernel warning/error dump from /var/log/messages which occurs on loading the module.
David Walser 2015-05-09 12:17:17 CEST

CC: (none) => tmb

Samuel Verschelde 2015-06-06 15:20:16 CEST

Assignee: bugsquad => lists.jjorge
Whiteboard: (none) => MGA5TOO

Comment 2 José Jorge 2015-06-21 10:36:28 CEST
Unfortunately this is a closed source driver with a big binary than only Broadcom can update to fix Kernel 3.19 compatibility.

Feel free to report Upstream if you find a way to do it...

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

Comment 3 José Jorge 2015-07-27 12:22:22 CEST
Finaly it seems someone from Arch wrote a patch in the binary glue code that fixes also this bug : look at #16390 .
Comment 4 José Jorge 2015-07-27 12:23:02 CEST
Please try to update which is in testing.

*** This bug has been marked as a duplicate of bug 16390 ***

Resolution: WONTFIX => DUPLICATE

Comment 5 Christian Lohmaier 2016-06-15 17:13:11 CEST
FYI: the flooding of the logs is caused by calls to iwconfig â net_applet does regularily poll the networks using that command. So every minute you get the log-spam...


Workaround is to disable the network applet.

/usr/bin/net_applet
     in cronNetwork() 
        â checkWireless() 
           â network::monitor::list_wireless(â¦)

 â /usr/lib/libDrakX/network/monitor.pm 
     â  in list_wireless(â¦)
[â¦]
        if ($current_ap && exists $networks{$current_ap}) {
            foreach (`$::prefix/sbin/iwconfig $o_intf 2>/dev/null`) {
                my $quality = $_ =~ $quality_match && $eval_quality->($1);
                $networks{$current_ap}{signal_strength} = $quality if $quality;
            }
        }
[â¦]

â periodic calls to iwconfig, that in turn triggers the kernel message/spams the logs.

CC: (none) => lohmaier+mageia


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