<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/drivers/net/wireless, branch v3.9-rc5</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>rtlwifi: usb: add missing freeing of skbuff</title>
<updated>2013-03-18T19:20:38+00:00</updated>
<author>
<name>Jussi Kivilinna</name>
<email>jussi.kivilinna@iki.fi</email>
</author>
<published>2013-03-17T09:54:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=36ef0b473fbf43d5db23eea4616cc1d18cec245f'/>
<id>36ef0b473fbf43d5db23eea4616cc1d18cec245f</id>
<content type='text'>
Signed-off-by: Jussi Kivilinna &lt;jussi.kivilinna@iki.fi&gt;
Acked-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Jussi Kivilinna &lt;jussi.kivilinna@iki.fi&gt;
Acked-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mwifiex: cancel cmd timer and free curr_cmd in shutdown process</title>
<updated>2013-03-18T19:20:38+00:00</updated>
<author>
<name>Bing Zhao</name>
<email>bzhao@marvell.com</email>
</author>
<published>2013-03-16T01:47:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=084c7189acb3f969c855536166042e27f5dd703f'/>
<id>084c7189acb3f969c855536166042e27f5dd703f</id>
<content type='text'>
curr_cmd points to the command that is in processing or waiting
for its command response from firmware. If the function shutdown
happens to occur at this time we should cancel the cmd timer and
put the command back to free queue.

Cc: &lt;stable@vger.kernel.org&gt; # 3.8
Tested-by: Marco Cesarano &lt;marco@marvell.com&gt;
Signed-off-by: Bing Zhao &lt;bzhao@marvell.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
curr_cmd points to the command that is in processing or waiting
for its command response from firmware. If the function shutdown
happens to occur at this time we should cancel the cmd timer and
put the command back to free queue.

Cc: &lt;stable@vger.kernel.org&gt; # 3.8
Tested-by: Marco Cesarano &lt;marco@marvell.com&gt;
Signed-off-by: Bing Zhao &lt;bzhao@marvell.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mwifiex: skip pending commands after function shutdown</title>
<updated>2013-03-18T19:20:38+00:00</updated>
<author>
<name>Bing Zhao</name>
<email>bzhao@marvell.com</email>
</author>
<published>2013-03-16T01:47:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=a3e240cacc93a06bff3313e28938e980d01a2160'/>
<id>a3e240cacc93a06bff3313e28938e980d01a2160</id>
<content type='text'>
During rmmod mwifiex_sdio processing FUNC_SHUTDOWN command is
sent to firmware. Firmware expcets only FUNC_INIT once WLAN
function is shut down.

Any command pending in the command queue should be ignored and
freed.

Cc: &lt;stable@vger.kernel.org&gt; # 3.8
Tested-by: Daniel Drake &lt;dsd@laptop.org&gt;
Tested-by: Marco Cesarano &lt;marco@marvell.com&gt;
Signed-off-by: Bing Zhao &lt;bzhao@marvell.com&gt;
Signed-off-by: Amitkumar Karwar &lt;akarwar@marvell.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
During rmmod mwifiex_sdio processing FUNC_SHUTDOWN command is
sent to firmware. Firmware expcets only FUNC_INIT once WLAN
function is shut down.

Any command pending in the command queue should be ignored and
freed.

Cc: &lt;stable@vger.kernel.org&gt; # 3.8
Tested-by: Daniel Drake &lt;dsd@laptop.org&gt;
Tested-by: Marco Cesarano &lt;marco@marvell.com&gt;
Signed-off-by: Bing Zhao &lt;bzhao@marvell.com&gt;
Signed-off-by: Amitkumar Karwar &lt;akarwar@marvell.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>mwifiex: fix race when queuing commands</title>
<updated>2013-03-18T19:20:36+00:00</updated>
<author>
<name>Amitkumar Karwar</name>
<email>akarwar@marvell.com</email>
</author>
<published>2013-03-16T01:47:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=00d7ea11ff0783e24fe70778f3141270b561aaa1'/>
<id>00d7ea11ff0783e24fe70778f3141270b561aaa1</id>
<content type='text'>
Running the following script repeatedly on XO-4 with SD8787
produces command timeout and system lockup.

insmod mwifiex_sdio.ko
sleep 1
ifconfig eth0 up
iwlist eth0 scan &amp;
sleep 0.5
rmmod mwifiex_sdio

mwifiex_send_cmd_async() is called for sync as well as async
commands. (mwifiex_send_cmd_sync() internally calls it for
sync command.)

"adapter-&gt;cmd_queued" gets filled inside mwifiex_send_cmd_async()
routine for both types of commands. But it is used only for sync
commands in mwifiex_wait_queue_complete(). This could lead to a
race when two threads try to queue a sync command with another
sync/async command simultaneously.

Get rid of global variable and pass command node as a parameter
to mwifiex_wait_queue_complete() to fix the problem.

Cc: &lt;stable@vger.kernel.org&gt; # 3.8
Reported-by: Daniel Drake &lt;dsd@laptop.org&gt;
Tested-by: Daniel Drake &lt;dsd@laptop.org&gt;
Tested-by: Marco Cesarano &lt;marco@marvell.com&gt;
Signed-off-by: Amitkumar Karwar &lt;akarwar@marvell.com&gt;
Signed-off-by: Bing Zhao &lt;bzhao@marvell.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Running the following script repeatedly on XO-4 with SD8787
produces command timeout and system lockup.

insmod mwifiex_sdio.ko
sleep 1
ifconfig eth0 up
iwlist eth0 scan &amp;
sleep 0.5
rmmod mwifiex_sdio

mwifiex_send_cmd_async() is called for sync as well as async
commands. (mwifiex_send_cmd_sync() internally calls it for
sync command.)

"adapter-&gt;cmd_queued" gets filled inside mwifiex_send_cmd_async()
routine for both types of commands. But it is used only for sync
commands in mwifiex_wait_queue_complete(). This could lead to a
race when two threads try to queue a sync command with another
sync/async command simultaneously.

Get rid of global variable and pass command node as a parameter
to mwifiex_wait_queue_complete() to fix the problem.

Cc: &lt;stable@vger.kernel.org&gt; # 3.8
Reported-by: Daniel Drake &lt;dsd@laptop.org&gt;
Tested-by: Daniel Drake &lt;dsd@laptop.org&gt;
Tested-by: Marco Cesarano &lt;marco@marvell.com&gt;
Signed-off-by: Amitkumar Karwar &lt;akarwar@marvell.com&gt;
Signed-off-by: Bing Zhao &lt;bzhao@marvell.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k: limit tx path hang check to normal data queues</title>
<updated>2013-03-18T19:20:35+00:00</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-03-15T15:18:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=01d4ab96d2e7fceaad204e5a8710ce34e229b8c5'/>
<id>01d4ab96d2e7fceaad204e5a8710ce34e229b8c5</id>
<content type='text'>
The beacon and multicast-buffer queues are managed by the beacon
tasklet, and the generic tx path hang check does not help in any way
here. Running it on those queues anyway can introduce some race
conditions leading to unnecessary chip resets.

Cc: stable@vger.kernel.org
Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The beacon and multicast-buffer queues are managed by the beacon
tasklet, and the generic tx path hang check does not help in any way
here. Running it on those queues anyway can introduce some race
conditions leading to unnecessary chip resets.

Cc: stable@vger.kernel.org
Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>ath9k_hw: revert chainmask to user configuration after calibration</title>
<updated>2013-03-18T19:20:34+00:00</updated>
<author>
<name>Felix Fietkau</name>
<email>nbd@openwrt.org</email>
</author>
<published>2013-03-15T13:53:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=74632d11a133b5baf6b9d622dd19d2f944d93d94'/>
<id>74632d11a133b5baf6b9d622dd19d2f944d93d94</id>
<content type='text'>
The commit 'ath9k_hw: fix calibration issues on chainmask that don't
include chain 0' changed the hardware chainmask to the chip chainmask
for the duration of the calibration, but the revert to user
configuration in the reset path runs too early.

That causes some issues with limiting the number of antennas (including
spurious failure in hardware-generated packets).

Fix this by reverting the chainmask after the essential parts of the
calibration that need the workaround, and before NF calibration is run.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Reported-by: Wojciech Dubowik &lt;Wojciech.Dubowik@neratec.com&gt;
Tested-by: Wojciech Dubowik &lt;Wojciech.Dubowik@neratec.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The commit 'ath9k_hw: fix calibration issues on chainmask that don't
include chain 0' changed the hardware chainmask to the chip chainmask
for the duration of the calibration, but the revert to user
configuration in the reset path runs too early.

That causes some issues with limiting the number of antennas (including
spurious failure in hardware-generated packets).

Fix this by reverting the chainmask after the essential parts of the
calibration that need the workaround, and before NF calibration is run.

Signed-off-by: Felix Fietkau &lt;nbd@openwrt.org&gt;
Reported-by: Wojciech Dubowik &lt;Wojciech.Dubowik@neratec.com&gt;
Tested-by: Wojciech Dubowik &lt;Wojciech.Dubowik@neratec.com&gt;
Cc: stable@vger.kernel.org
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>iwl3945: fix length of dma buffers</title>
<updated>2013-03-18T19:20:34+00:00</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>sgruszka@redhat.com</email>
</author>
<published>2013-03-14T11:48:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=7f42ace3118afedbd1848a349d01a11d9ca13d41'/>
<id>7f42ace3118afedbd1848a349d01a11d9ca13d41</id>
<content type='text'>
commit bdb084b22d8aee66c87af5e9c36bd6cf7f3bccfd
Author: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Date:   Wed Feb 13 15:49:08 2013 +0100

    iwlegacy: more checks for dma mapping errors

broke il3945_tx_skb() dma buffer length settings, what results on
firmware errors like showed below and make 3945 device non usable.

iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008.
iwl3945 0000:02:00.0: Loaded firmware version: 15.32.2.9
iwl3945 0000:02:00.0: Start IWL Error Log Dump:
iwl3945 0000:02:00.0: Status: 0x000202E4, count: 1
iwl3945 0000:02:00.0: Desc 	Time	   asrtPC blink2 ilink1  nmiPC   Line
iwl3945 0000:02:00.0: SYSASSERT     (0x5) 0000208934 0x008B6 0x0035E 0x00320 0x00000 267
iwl3945 0000:02:00.0: Error Reply type 0x00000001 cmd

Reported-by: Zdenek Kabelac &lt;zkabelac@redhat.com&gt;
Reported-by: Krzysztof Kolasa &lt;kkolasa@winsoft.pl&gt;
Reported-by: Pedro Francisco &lt;pedrogfrancisco@gmail.com&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commit bdb084b22d8aee66c87af5e9c36bd6cf7f3bccfd
Author: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Date:   Wed Feb 13 15:49:08 2013 +0100

    iwlegacy: more checks for dma mapping errors

broke il3945_tx_skb() dma buffer length settings, what results on
firmware errors like showed below and make 3945 device non usable.

iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008.
iwl3945 0000:02:00.0: Loaded firmware version: 15.32.2.9
iwl3945 0000:02:00.0: Start IWL Error Log Dump:
iwl3945 0000:02:00.0: Status: 0x000202E4, count: 1
iwl3945 0000:02:00.0: Desc 	Time	   asrtPC blink2 ilink1  nmiPC   Line
iwl3945 0000:02:00.0: SYSASSERT     (0x5) 0000208934 0x008B6 0x0035E 0x00320 0x00000 267
iwl3945 0000:02:00.0: Error Reply type 0x00000001 cmd

Reported-by: Zdenek Kabelac &lt;zkabelac@redhat.com&gt;
Reported-by: Krzysztof Kolasa &lt;kkolasa@winsoft.pl&gt;
Reported-by: Pedro Francisco &lt;pedrogfrancisco@gmail.com&gt;
Signed-off-by: Stanislaw Gruszka &lt;sgruszka@redhat.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>rtlwifi: rtl8192cu: Fix problem that prevents reassociation</title>
<updated>2013-03-13T18:18:53+00:00</updated>
<author>
<name>Larry Finger</name>
<email>Larry.Finger@lwfinger.net</email>
</author>
<published>2013-03-13T15:28:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=9437a248e7cac427c898bdb11bd1ac6844a1ead4'/>
<id>9437a248e7cac427c898bdb11bd1ac6844a1ead4</id>
<content type='text'>
The driver was failing to clear the BSSID when a disconnect happened. That
prevented a reconnection. This problem is reported at
https://bugzilla.redhat.com/show_bug.cgi?id=789605,
https://bugzilla.redhat.com/show_bug.cgi?id=866786,
https://bugzilla.redhat.com/show_bug.cgi?id=906734, and
https://bugzilla.kernel.org/show_bug.cgi?id=46171.

Thanks to Jussi Kivilinna for making the critical observation
that led to the solution.

Reported-by: Jussi Kivilinna &lt;jussi.kivilinna@iki.fi&gt;
Tested-by: Jussi Kivilinna &lt;jussi.kivilinna@iki.fi&gt;
Tested-by: Alessandro Lannocca &lt;alessandro.lannocca@gmail.com&gt;
Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The driver was failing to clear the BSSID when a disconnect happened. That
prevented a reconnection. This problem is reported at
https://bugzilla.redhat.com/show_bug.cgi?id=789605,
https://bugzilla.redhat.com/show_bug.cgi?id=866786,
https://bugzilla.redhat.com/show_bug.cgi?id=906734, and
https://bugzilla.kernel.org/show_bug.cgi?id=46171.

Thanks to Jussi Kivilinna for making the critical observation
that led to the solution.

Reported-by: Jussi Kivilinna &lt;jussi.kivilinna@iki.fi&gt;
Tested-by: Jussi Kivilinna &lt;jussi.kivilinna@iki.fi&gt;
Tested-by: Alessandro Lannocca &lt;alessandro.lannocca@gmail.com&gt;
Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>rt2x00: fix rt2x00 to work with the new ralink SoC config symbols</title>
<updated>2013-03-13T18:18:53+00:00</updated>
<author>
<name>John Crispin</name>
<email>blogic@openwrt.org</email>
</author>
<published>2013-03-13T12:20:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=5818a46a999ad9546e68e8765a3ca1d9d87f9b4a'/>
<id>5818a46a999ad9546e68e8765a3ca1d9d87f9b4a</id>
<content type='text'>
Since v3.9-rc1 the kernel has basic support for Ralink WiSoC. The config symbols
are named slightly different than before. Fix the rt2x00 to match the new
symbols.

The commit causing this breakage is:
commit ae2b5bb6570481b50a7175c64176b82da0a81836
Author: John Crispin &lt;blogic@openwrt.org&gt;
Date:   Sun Jan 20 22:05:30 2013 +0100
MIPS: ralink: adds Kbuild files

Signed-off-by: John Crispin &lt;blogic@openwrt.org&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since v3.9-rc1 the kernel has basic support for Ralink WiSoC. The config symbols
are named slightly different than before. Fix the rt2x00 to match the new
symbols.

The commit causing this breakage is:
commit ae2b5bb6570481b50a7175c64176b82da0a81836
Author: John Crispin &lt;blogic@openwrt.org&gt;
Date:   Sun Jan 20 22:05:30 2013 +0100
MIPS: ralink: adds Kbuild files

Signed-off-by: John Crispin &lt;blogic@openwrt.org&gt;
Acked-by: Gertjan van Wingerde &lt;gwingerde@gmail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>rtlwifi: rtl8192cu: Fix schedule while atomic bug splat</title>
<updated>2013-03-08T20:58:07+00:00</updated>
<author>
<name>Larry Finger</name>
<email>Larry.Finger@lwfinger.net</email>
</author>
<published>2013-02-27T20:10:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=664899786cb49cb52f620e06ac19c0be524a7cfa'/>
<id>664899786cb49cb52f620e06ac19c0be524a7cfa</id>
<content type='text'>
When run at debug 3 or higher, rtl8192cu reports a BUG as follows:

BUG: scheduling while atomic: kworker/u:0/5281/0x00000002
INFO: lockdep is turned off.
Modules linked in: rtl8192cu rtl8192c_common rtlwifi fuse af_packet bnep bluetooth b43 mac80211 cfg80211 ipv6 snd_hda_codec_conexant kvm_amd k
vm snd_hda_intel snd_hda_codec bcma rng_core snd_pcm ssb mmc_core snd_seq snd_timer snd_seq_device snd i2c_nforce2 sr_mod pcmcia forcedeth i2c_core soundcore
 cdrom sg serio_raw k8temp hwmon joydev ac battery pcmcia_core snd_page_alloc video button wmi autofs4 ext4 mbcache jbd2 crc16 thermal processor scsi_dh_alua
 scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc scsi_dh ata_generic pata_acpi pata_amd [last unloaded: rtlwifi]
Pid: 5281, comm: kworker/u:0 Tainted: G        W    3.8.0-wl+ #119
Call Trace:
 [&lt;ffffffff814531e7&gt;] __schedule_bug+0x62/0x70
 [&lt;ffffffff81459af0&gt;] __schedule+0x730/0xa30
 [&lt;ffffffff81326e49&gt;] ? usb_hcd_link_urb_to_ep+0x19/0xa0
 [&lt;ffffffff8145a0d4&gt;] schedule+0x24/0x70
 [&lt;ffffffff814575ec&gt;] schedule_timeout+0x18c/0x2f0
 [&lt;ffffffff81459ec0&gt;] ? wait_for_common+0x40/0x180
 [&lt;ffffffff8133f461&gt;] ? ehci_urb_enqueue+0xf1/0xee0
 [&lt;ffffffff810a579d&gt;] ? trace_hardirqs_on+0xd/0x10
 [&lt;ffffffff81459f65&gt;] wait_for_common+0xe5/0x180
 [&lt;ffffffff8107d1c0&gt;] ? try_to_wake_up+0x2d0/0x2d0
 [&lt;ffffffff8145a08e&gt;] wait_for_completion_timeout+0xe/0x10
 [&lt;ffffffff8132ab1c&gt;] usb_start_wait_urb+0x8c/0x100
 [&lt;ffffffff8132adf9&gt;] usb_control_msg+0xd9/0x130
 [&lt;ffffffffa057dd8d&gt;] _usb_read_sync+0xcd/0x140 [rtlwifi]
 [&lt;ffffffffa057de0e&gt;] _usb_read32_sync+0xe/0x10 [rtlwifi]
 [&lt;ffffffffa04b0555&gt;] rtl92cu_update_hal_rate_table+0x1a5/0x1f0 [rtl8192cu]

The cause is a synchronous read from routine rtl92cu_update_hal_rate_table().
The resulting output is not critical, thus the debug statement is
deleted.

Reported-by: Jussi Kivilinna &lt;jussi.kivilinna@mbnet.fi&gt;
Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When run at debug 3 or higher, rtl8192cu reports a BUG as follows:

BUG: scheduling while atomic: kworker/u:0/5281/0x00000002
INFO: lockdep is turned off.
Modules linked in: rtl8192cu rtl8192c_common rtlwifi fuse af_packet bnep bluetooth b43 mac80211 cfg80211 ipv6 snd_hda_codec_conexant kvm_amd k
vm snd_hda_intel snd_hda_codec bcma rng_core snd_pcm ssb mmc_core snd_seq snd_timer snd_seq_device snd i2c_nforce2 sr_mod pcmcia forcedeth i2c_core soundcore
 cdrom sg serio_raw k8temp hwmon joydev ac battery pcmcia_core snd_page_alloc video button wmi autofs4 ext4 mbcache jbd2 crc16 thermal processor scsi_dh_alua
 scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc scsi_dh ata_generic pata_acpi pata_amd [last unloaded: rtlwifi]
Pid: 5281, comm: kworker/u:0 Tainted: G        W    3.8.0-wl+ #119
Call Trace:
 [&lt;ffffffff814531e7&gt;] __schedule_bug+0x62/0x70
 [&lt;ffffffff81459af0&gt;] __schedule+0x730/0xa30
 [&lt;ffffffff81326e49&gt;] ? usb_hcd_link_urb_to_ep+0x19/0xa0
 [&lt;ffffffff8145a0d4&gt;] schedule+0x24/0x70
 [&lt;ffffffff814575ec&gt;] schedule_timeout+0x18c/0x2f0
 [&lt;ffffffff81459ec0&gt;] ? wait_for_common+0x40/0x180
 [&lt;ffffffff8133f461&gt;] ? ehci_urb_enqueue+0xf1/0xee0
 [&lt;ffffffff810a579d&gt;] ? trace_hardirqs_on+0xd/0x10
 [&lt;ffffffff81459f65&gt;] wait_for_common+0xe5/0x180
 [&lt;ffffffff8107d1c0&gt;] ? try_to_wake_up+0x2d0/0x2d0
 [&lt;ffffffff8145a08e&gt;] wait_for_completion_timeout+0xe/0x10
 [&lt;ffffffff8132ab1c&gt;] usb_start_wait_urb+0x8c/0x100
 [&lt;ffffffff8132adf9&gt;] usb_control_msg+0xd9/0x130
 [&lt;ffffffffa057dd8d&gt;] _usb_read_sync+0xcd/0x140 [rtlwifi]
 [&lt;ffffffffa057de0e&gt;] _usb_read32_sync+0xe/0x10 [rtlwifi]
 [&lt;ffffffffa04b0555&gt;] rtl92cu_update_hal_rate_table+0x1a5/0x1f0 [rtl8192cu]

The cause is a synchronous read from routine rtl92cu_update_hal_rate_table().
The resulting output is not critical, thus the debug statement is
deleted.

Reported-by: Jussi Kivilinna &lt;jussi.kivilinna@mbnet.fi&gt;
Signed-off-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Cc: Stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
