I'll add my voice to this bug report as well. A MacBook (2nd gn white cover model) with latest Kubuntu (Linux jstalnak-MacBook 3.18.3-031803-generic #201501161810 SMP Fri Jan 16 18:12:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). This issue exists with all current kernels (3.16.x) and with kernels 3.18.3-031803 and 3.19.0-031900 both with the latest bwmc kernel source. Without the bwmc kernel source the enet/wireless is dead. With the bwmc kernel source in 3.18.3 all works, but the log entries continue. With kernel 3.19.0 networking works, but sound is dead, and log entries continue. Using one of the commandline ttys is impossible, as the error output interferes with entering passwords at the login prompts.
The frequency is about an entry per second in the kern.log and syslog.log. They begin at dmesg time point 150+ after boot concludes, so quite quickly after start up.
<dmesg>
[ 100.532832] nouveau W[ PCE0][0000:02:00.0] disabled, PCE0=1 to enable
[ 101.180152] nouveau W[ PCE0][0000:02:00.0] disabled, PCE0=1 to enable
[ 157.623413] ERROR @wl_dev_intvar_get : error (-1)
[ 157.623432] ERROR @wl_cfg80211_get_tx_power : error (-1)
</dmesg>
My present kern.log has 113,000+ "wl_cfg80211" entries. Which also makes using these logs for any purpose pragmatically impossible; given that the wl_dev and wl_cfg occur in pairs, that's 226,000 lines of utterly useless data.
I'll add my voice to this bug report as well. A MacBook (2nd gn white cover model) with latest Kubuntu (Linux jstalnak-MacBook 3.18.3- 031803- generic #201501161810 SMP Fri Jan 16 18:12:22 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). This issue exists with all current kernels (3.16.x) and with kernels 3.18.3-031803 and 3.19.0-031900 both with the latest bwmc kernel source. Without the bwmc kernel source the enet/wireless is dead. With the bwmc kernel source in 3.18.3 all works, but the log entries continue. With kernel 3.19.0 networking works, but sound is dead, and log entries continue. Using one of the commandline ttys is impossible, as the error output interferes with entering passwords at the login prompts.
The frequency is about an entry per second in the kern.log and syslog.log. They begin at dmesg time point 150+ after boot concludes, so quite quickly after start up.
<dmesg> get_tx_ power : error (-1)
[ 100.532832] nouveau W[ PCE0][0000:02:00.0] disabled, PCE0=1 to enable
[ 101.180152] nouveau W[ PCE0][0000:02:00.0] disabled, PCE0=1 to enable
[ 157.623413] ERROR @wl_dev_intvar_get : error (-1)
[ 157.623432] ERROR @wl_cfg80211_
</dmesg>
My present kern.log has 113,000+ "wl_cfg80211" entries. Which also makes using these logs for any purpose pragmatically impossible; given that the wl_dev and wl_cfg occur in pairs, that's 226,000 lines of utterly useless data.
How can I help?