wl continuously spams syslog

[C de-Avillez]

Since v6.20 the wl module keeps writing errors to the syslog, like:

Jan 27 13:54:39 xango3 kernel: [98488.573646] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:39 xango3 kernel: [98488.573654] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:44 xango3 kernel: [98492.676425] net_ratelimit: 32 callbacks suppressed
Jan 27 13:54:44 xango3 kernel: [98492.676431] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:44 xango3 kernel: [98492.676437] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:44 xango3 kernel: [98493.576872] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:44 xango3 kernel: [98493.576880] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:44 xango3 kernel: [98493.576890] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:44 xango3 kernel: [98493.576893] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:44 xango3 kernel: [98493.576902] ERROR @wl_dev_intvar_get : error (-1)
Jan 27 13:54:44 xango3 kernel: [98493.576905] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jan 27 13:54:45 xango3 kernel: [98493.673933] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:45 xango3 kernel: [98493.673941] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:50 xango3 kernel: [98498.661276] net_ratelimit: 22 callbacks suppressed
Jan 27 13:54:50 xango3 kernel: [98498.661282] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:50 xango3 kernel: [98498.661287] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:50 xango3 kernel: [98499.565463] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:50 xango3 kernel: [98499.565468] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:50 xango3 kernel: [98499.565473] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:50 xango3 kernel: [98499.565474] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:50 xango3 kernel: [98499.565478] ERROR @wl_dev_intvar_get : error (-1)
Jan 27 13:54:50 xango3 kernel: [98499.565480] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jan 27 13:54:51 xango3 kernel: [98499.658770] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:51 xango3 kernel: [98499.658778] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:52 xango3 dhclient: DHCPREQUEST of 192.168.1.133 on eth2 to 192.168.1.2 port 67
Jan 27 13:54:56 xango3 kernel: [98504.646146] net_ratelimit: 22 callbacks suppressed
Jan 27 13:54:56 xango3 kernel: [98504.646152] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:56 xango3 kernel: [98504.646158] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562569] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562574] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562578] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562580] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562584] ERROR @wl_dev_intvar_get : error (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562586] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jan 27 13:54:57 xango3 kernel: [98505.643813] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:57 xango3 kernel: [98505.643823] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
Uname: Linux 3.8.0-2-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
CheckboxSubmission: c8a7d84e13c3b258e707f056604eb0e0
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Sun Jan 27 13:59:38 2013
InstallationDate: Installed on 2012-07-02 (209 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120701)
MarkForUpload: True
SourcePackage: bcmwl
UpgradeStatus: Upgraded to raring on 2012-11-19 (69 days ago)

[Bernardo Reino (reinob)]

I had the same issue (12.04 with kernel 3.5 and the new dkms module). See here: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/923809/comments/22

Applying the user-ioctl.patch patch found here: https://aur.archlinux.org/packages.php?ID=19514 removed those two error/warning messages. Everything else continued to work OK.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Oedipe (oedipe)]

See bug #114281

Still left not assigned.... and affects thousands of users, even in tthe Ubuntu 12.0.4 LTS
Ubuntu is a "No go" for me actually.

[Oedipe (oedipe)]

Well, after some hours trying to solve the issue, i found the trick ! (it does work for me on a Lenovo with a BCM4312)

Uninstall completely bcmwl-kernel-source ! (seems buggy)

Install instead "b43-fwcutter" and "firmware-b43-lpphy-installer" (for BCM4312), or the others BCM installers according to your type of BCM.

Reboot => done ! No more "wl continuously spams syslog" and my wifi is stable and strong now.

[Wildman (sasha-mishchenko)]

I have this bug on Kubuntu 13.04 x64 with Acer TM B113-E notebook.
b43-fwcutter have not help for me.
I am reconfigure rsyslog.conf and add new line before /var/log/syslog rule:

:msg, contains, "ERROR @wl_cfg80211_get_station : Could not get" ~
*.*;auth,authpriv.none -/var/log/syslog

and rsyslog drops spam messages...

[Ma Hsiao-chun (mahsiaochun)]

I have a shit loads of "ERROR @wl_cfg80211_get_station : Wrong Mac address" but wl works better than b43 after all.

[Adam Porter (alphapapa)]

This is absolutely ridiculous! Raring has been out for months now, and this bug was reported months before:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114281
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1163401

I upgraded my perfectly-working netbook from Quantal to Raring and am greeted by non-functional wifi! What do we get? "Incomplete", "Undecided", "Medium"! This bug is COMPLETELY CONFIRMED AND COMPLETELY CRITICAL! Chalk yet another bug up for Ubuntu's Hall of Shame!

[Bernardo Reino (reinob)]

@Adam Porter,

YOU are completely ridiculous. This bug is about the wl module reporting too much on the kernel log, not about whatever problem you may have with Raring.

There is a patch that fixes this bug.

[Adam Porter (alphapapa)]

Bernardo,

The problem for some users seems to be that the wrong driver is being used. For myself and some others who commented here, using a different driver made the the card work and didn't print the messages. Those messages may be indicating a problem; if so, hiding them might not be the right thing to do.

This is all complicated by the fact that some people on this report use Raring and others use Precise. This is confusing because:

1. Raring uses 3.8, but Precise recently had 3.8 backported to it.
2. Precise had bcmwl 5.100.x but now has 6.20.x.
3. IIRC there were some problems building bcmwl on Precise that have since been fixed.

And it's also complicated by the facts that:

1. The reporter of this bug didn't report his hardware.
2. Not everyone on this report is using the same hardware.
3. Not everyone on this report is using the same version of Ubuntu.

From reading over 100 bug reports on bcmwl yesterday, my best understanding is that this bug is either:

a) a dupe of bug 1097519, meaning that if the best driver is selected by Ubuntu, the messages will not be printed and the card will work properly; or

b) a bug in which a newer driver was imperfectly backported to a backported kernel, leaving it in a state in which it performs correctly but prints useless errors.

Since we don't know everyone's hardware here, and since some are talking about Precise and some about Raring, and since the bug was originally filed against Raring, I don't think this bug is about option B. If that bug exists, I think it should be filed separately. But I'm not sure if that bug really exists, because it appears to me that when the right driver is used, the messages stop. From my understanding, the reporter of this bug probably can solve his problem by using the proper driver.

So my best understanding is that this is still a dupe of bug 1097519. If my reasoning is wrong, please explain.

[C de-Avillez (hggdh2)]

I am the OP. This did not need reporting the hardware at the time, and I am not sure it needs it now. The issue is quite simple: wl spams the log.

This happens with version 6.20.155.1+bdcom-0ubuntu6 on all Ubuntu versions.

By the way, wireless works perfectly here. *THAT* would need reporting the chip id, on the correct bug.

[Adam Porter (alphapapa)]

hggdh2,

> This did not need reporting the hardware at the time, and I am not sure it needs it now. The issue is quite simple: wl spams the log.

Are you kidding me? You think reporting a driver bug doesn't require reporting which of the 9+ different hardware it supports?

I will reiterate: I had this exact problem. I removed the wl driver (the bcmwl-kernel-source package), causing the in-tree driver to be used, and the problem was solved. Therefore it is a duplicate of bug 1097519, which states that the correct driver needs to be used.

If you disagree, you are going to have to prove that this bug exists by:

1. Reporting your hardware. Otherwise no one can take this report seriously.
2. Testing all the other drivers (b43, broadcom-sta, and brcmsmac) and proving they all have the same problem. If one of the other drivers works, then this bug report is moot.

Alternatively, you are going to have to explain why a driver developer needs to fix bcmwl-kernel-source when other existing drivers work fine, e.g. if one of the other three drivers doesn't work for you. But if that were the case, the solution might be to fix the other driver, not to fix this one. We need fewer redundant drivers, not more.

[Ma Hsiao-chun (mahsiaochun)]

Adam Porter: This a bug of a _specific_ driver. Whether your hardware works with alternative driver or not has _zero_ coreleation with this bug. Stop _spamming_.

[C de-Avillez (hggdh2)]

@Adam Porter: I think you are conflating two (or more) different issues. The issue on *this* bug is that bcmwl spams the logs. It is *NOT* that it does, or does not, work. It is *NOT* about the b43, broadcom-sta, or brcmsmac drivers. As far as this bug is concerned, these other drivers are irrelevant.

As such, this bug lives on its own. This bug, BTW, has been noticed elsewhere, and even a patch has been proposed. If, someday someone will submit a patch here for this bug or not is yet another problem. Perhaps I will do it, when I really get mad about it.

I understand your frustration, but you should not decide that *one* driver is THE Driver For All just because it works for you.

As such, marking Triaged.

[Adam Porter (alphapapa)]

hggdh2,

Wow, instead of just posting the output of $(lspci | grep Broadcom), you're refusing and arguing.

Again: If one of the other drivers works, then this bug report is moot. If brcmsmac (the in-tree driver, which is "Completely open source host drivers, no binary object files.") works, the solution to this bug is not to fix bcmwl (the out-of-tree, non-free, restricted driver), the solution is to use the driver that works.

Therefore you should test the other drivers. Here, I will help you test the in-tree one:

$ sudo apt-get remove bcmwl-kernel-source
$ sudo stop network-manager
$ sudo modprobe -r wl
$ sudo modprobe brcmsmac
$ sudo start network-manager
$ firefox

If the other drivers don't work, then fixing this driver might be the best solution, or fixing the free driver might be the best solution.

If you disagree and refuse to cooperate, okay; good luck getting a developer to work on this bug.

Ma Xiaojun,

If you don't understand the concept that there is no point in fixing non-free driver X if free driver Y works, then I probably can't convince you. Maybe someone else can. Good luck to you.

[C de-Avillez (hggdh2)]

$ lspci | grep Broadcom
03:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
$

There. Now that I have stated what is my Broadcom card, please DO NOT CHANGE THE BUG STATUS AGAIN. This is a *valid* bug, no matter what you think. Given that you are unable to understand that this is a valid bug, leave it alone.

[Adam Porter (alphapapa)]

http://wireless.kernel.org/en/users/Drivers/brcm80211#Supported_Chips

"BCM43224"

[Brian Murray (brian-murray)]

From what I can gather the original reporter was concerned about the excessive number of messages in their syslog regarding the wl driver. There is in fact a patch for this here:

http://pkgbuild.com/git/aur-mirror.git/commit/broadcom-wl?id=e87e8290a6d1abd88c064d51cc94f19b137bae11

here are the relevant bits:

++ if (err != -EINVAL) {
++ // Don't fill syslog with EINVAL error
++ WL_ERR(("Could not get rssi (%d)\n", err));

Generally, when there multiple issues in one bug report we stick with the original issue and ask other people experiencing different issues to submit new bug reports. As such it'd be great if Adam Porter could submit a new bug report regarding his issue of the incorrect driver being used. Once a new bug report has been created I'll personally ensure that someone looks at it.

[Adam Porter (alphapapa)]

On Tue, Jun 11, 2013 at 3:28 PM, Brian Murray <email address hidden> wrote:

> As such it'd be great if Adam Porter could
> submit a new bug report regarding his issue of the incorrect driver
> being used. Once a new bug report has been created I'll personally
> ensure that someone looks at it.

Again, it's bug 1097519.

[Bernardo Reino (reinob)]

No it's not 1097519.

This bug is about bcmwl, not about open-source vs closed-source policy decisions. BTW, the bcmwl driver is the *only* working driver for many chipsets, so whether the bug is reported in connection with a chipset supported by other driver IS IRRELEVANT. bcmwl has bugs that need to be fixed.

For this one we have a patch that solves the unnecessary syslog spamming AS WELL AS the ioctl() problem that prevents using tools such as iwconfig without sudo.

As such, this bug is not only triaged, but a fix is known (see post #18) and just needs to be applied to the default ubuntu-released packages.

[Dario Bertini (berdario)]

I'm affected by this bug, and I have a BCM4321 chip

Please note that the patch linked in comment #18 is NOT ENOUGH

that only deals with the "Could not get rssi" error (from get_station), but the log is being spammed also with messages of

"could not get rate" from get_station
"error" from invar_get
"error" from get_tx_power

[C de-Avillez (hggdh2)]

On Wed, Jun 12, 2013 at 10:27 AM, Dario Bertini <email address hidden> wrote:

> I'm affected by this bug, and I have a BCM4321 chip
>
> Please note that the patch linked in comment #18 is NOT ENOUGH
>
> that only deals with the "Could not get rssi" error (from get_station),
> but the log is being spammed also with messages of
>
> "could not get rate" from get_station
> "error" from invar_get
> "error" from get_tx_power

Yes, I know. The full patch seems to have been written for the 5.x version
of bcmwl; I am still looking for a more inclusive patch, or I will add the
other tests myself. Please note that all that would be done is prevent the
messages from being sent to the log.

> ..hggdh..
>

[ibere fernandes (ibere-fernandes)]

Lubuntu 12.04 kernel 3.2.0-48-generic.

I was getting the sys.log spammed by ERROR @wl_cfg80211.

I was using Broadcom Corporation BCM4321 for wireless and the driver was wl: bcmwl-kernel-source.

I uninstalled everything that was installed and at

http://wireless.kernel.org/en/users/Drivers/b43

I found the solution:
sudo apt-get install firmware-b43-installer

Now I have:
~$ lsmod | grep "b43\|ssb\|bcma\|wl"
b43 342801 0
mac80211 436493 1 b43
cfg80211 178877 2 b43,mac80211
bcma 25651 1 b43
ssb 50691 1 b43

and all tty consoles have no spamming errors like before.

[Benjamin Daines (benjamindaines)]

13.04 with kernel 3.8.0-26 and BCM4331 card.

bcmwl-kernel-source 6.20.155.1

dmesg output:
[ 6592.905573] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6594.903577] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6594.903582] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6596.902360] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6596.902371] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6596.903412] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6596.903421] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6598.900128] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6598.900139] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6600.898228] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6600.898232] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6602.895810] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6602.895813] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6602.896012] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6602.896014] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6604.895382] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6604.895394] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6606.892406] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6606.892417] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6608.890203] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6608.890214] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6608.890743] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6608.890749] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6610.888541] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6610.888552] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)

[acoundexist (dimitrys)]

A modified version of the wl driver (just commented the errors out, so they wont pop up) can be found here: http://www.mediafire.com/download/8gq5vz3bghi1hhu/wl.tar.gz

The compiled-binary version can be found here: http://www.mediafire.com/download/50hzvm0pbbcxzlq/wl.ko

It's not a permament fix but annoying errors will dissapear.

To install just run locate wl.ko, go in the directory that it pops up and replace the wl.ko file. Remember to always keep a copy of the original file, just in case.

Hope I helped someone.

P.S. I am not sure if download links like this are allowed.

[C de-Avillez (hggdh2)]

@accountexist: can you give us just the patch?

[Gurjeet Singh (gurjeet)]

@Adam,

    I used your instructions in comment #15 and although it seemed to work, but after the restart the wireless would not work. The reason was that immediately after the restart, before the reboot, the 'wl' driver was still loaded and continued to provide network access. But after the restart, when 'wl' was actually not loaded, and the b43 and bcma drivers were loaded and they did not work.

I am using MacBook Pro 9,1 (bought mid-2012).

I agree with your reasoning that if the in-tree drivers work, there's no need to fix the bcma/b43 non-free drivers, but as is evident in my case, the non-free drivers are the only ones that work, and hence the noise generated by the non-free driver in the syslog needs to be reduced/eliminated.

SInce these are actually kernel messages, and since kernel keeps a fixed size ring-buffers for kernel messages, after just a few minutes of strting the machine, the `dmesg` output has lost all the startup messages and is filled with these 'Could not get' messages. It even causes the syslog to cycle files much faster than it would otherwose do, and hence I lose the ability to go back in syslog history to diagnose any problems.

[Gurjeet Singh (gurjeet)]

For completeness:

I am using kernel 3.8:
    Linux work 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

On Ubuntu 12.04 installed using:
    sudo apt-get install linux-image-generic-lts-raring linux-headers-generic-lts-raring

[Bernardo Reino (reinob)]

@gurjeet,

I'd recommend you just download the saucy .deb and install it (http://packages.ubuntu.com/saucy/amd64/bcmwl-kernel-source/download for 64-bit).

It solves basically every problem the bcmwl driver had (ever) had. AFAIK.

[Gurjeet Singh (gurjeet)]

@Bernardo,

    Thanks so much!!! That indeed eliminated the clutter in kernel logs!

    I had added this line to syslog to prune out the messages from syslog (but not the kernel logs)

:msg, contains, "wl_cfg80211_get_station : Could not get " ~

    I can now remove this and live in peace with the stock syslog configuration!

Thanks again!

PS: The page at the link you sent is so confusing! They don't list a clickable file name anywhere, and have the mirror names instead, which actually link to the files.

[m1fcj (hakan-koseoglu)]

For Flying Spaghetti Monster's sake.... This bug still happens on Trusty. How hard is it to fix the issue so that my /var/log/syslog doesn't grow to multiple GBs in a single day and still remains useful?!

Stop bickering and put a simple fix in, i.e. only reporting the error once, not every two seconds!

The driver is still spamming the log every couple of seconds.

root@hakan-work:~# lspci|grep -i broad
02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n

root@hakan-work:~# tail -n 20 /var/log/syslog
Jun 23 07:12:27 hakan-work kernel: [58615.240360] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:27 hakan-work kernel: [58615.240366] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:29 hakan-work kernel: [58617.242963] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:29 hakan-work kernel: [58617.242967] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:31 hakan-work kernel: [58619.245942] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:31 hakan-work kernel: [58619.245955] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:33 hakan-work kernel: [58621.236626] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:33 hakan-work kernel: [58621.236630] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:35 hakan-work kernel: [58623.240581] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:35 hakan-work kernel: [58623.240585] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:37 hakan-work kernel: [58625.226418] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:37 hakan-work kernel: [58625.226423] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:39 hakan-work kernel: [58627.240999] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:39 hakan-work kernel: [58627.241003] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:41 hakan-work kernel: [58629.233176] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:41 hakan-work kernel: [58629.233180] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:43 hakan-work kernel: [58631.235820] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:43 hakan-work kernel: [58631.235828] ERROR @wl_cfg80211_get_tx_power : error (-1)
Jun 23 07:12:45 hakan-work kernel: [58633.236775] ERROR @wl_dev_intvar_get : error (-1)
Jun 23 07:12:45 hakan-work kernel: [58633.236779] ERROR @wl_cfg80211_get_tx_power : error (-1)

root@hakan-work:~# uname -a
Linux hakan-work 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[m1fcj (hakan-koseoglu)]

I must add, everything works just fine with the WiFi apart from the SSD getting hammered with repeated writes on to the syslog.