From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [BUG] Atheros AR7010+AR9287: Scheduling while atomic: ksoftirqd/0/3/0x00000302
Date: Thu, 23 Jan 2014 20:44:43 +0100 [thread overview]
Message-ID: <52E1712B.70202@rempel-privat.de> (raw)
In-Reply-To: <trinity-b8018ef9-8037-4688-a363-2deb3aed68fc-1390501815918@3capp-1and1-bs02>
Hi Antonio,
You probably know more about this issue then me.
Insight of this mutex are some WMI commands, which are incredible slow
on some USB 2.0 devices.
Am 23.01.2014 19:30, schrieb mail at fuerstflorian.de:
> Hello all,
>
> my Raspberry Pi crashes about once a day with the following kernel message:
>
> [80526.425663] wlan0: AP xx:xx:xx:xx:xx:xx changed bandwidth, new config is 2462 MHz, width 1 (2462/0 MHz)
> [80527.347296] wlan0: AP xx:xx:xx:xx:xx:xx changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz)
> [80527.347683] BUG: scheduling while atomic: ksoftirqd/0/3/0x00000302
> [80527.421904] Modules linked in: arc4 ath9k_htc ath9k_common ath9k_hw ath mac80211 cfg80211 leds_gpio led_class spi_bcm2708 i2c_bcm2708 snd_bcm2835 snd_pcm snd_page_alloc snd_timer snd i2c_dev bcm2708_rng rng_core ipv6
> [80527.422023] CPU: 0 PID: 3 Comm: ksoftirqd/0 Tainted: G W 3.10.26-1-ARCH #1
> [80527.422096] [<c0012da8>] (unwind_backtrace+0x0/0xf0) from [<c0010ca8>] (show_stack+0x10/0x14)
> [80527.422147] [<c0010ca8>] (show_stack+0x10/0x14) from [<c059ae08>] (__schedule_bug+0x44/0x5c)
> [80527.422182] [<c059ae08>] (__schedule_bug+0x44/0x5c) from [<c05a15f0>] (__schedule+0x54c/0x5c4)
> [80527.422213] [<c05a15f0>] (__schedule+0x54c/0x5c4) from [<c05a1d58>] (schedule_preempt_disabled+0x14/0x20)
> [80527.422242] [<c05a1d58>] (schedule_preempt_disabled+0x14/0x20) from [<c05a0994>] (__mutex_lock_slowpath+0x9c/0x12c)
> [80527.422337] [<c05a0994>] (__mutex_lock_slowpath+0x9c/0x12c) from [<bf2898cc>] (ath9k_htc_sta_rc_update+0x30/0x98 [ath9k_htc])
> [80527.422841] [<bf2898cc>] (ath9k_htc_sta_rc_update+0x30/0x98 [ath9k_htc]) from [<bf1863b0>] (ieee80211_rx_handlers+0x1994/0x24a4 [mac80211])
> [80527.423397] [<bf1863b0>] (ieee80211_rx_handlers+0x1994/0x24a4 [mac80211]) from [<bf1872e0>] (ieee80211_prepare_and_rx_handle+0x234/0xb14 [mac80211])
> [80527.423946] [<bf1872e0>] (ieee80211_prepare_and_rx_handle+0x234/0xb14 [mac80211]) from [<bf187eb8>] (ieee80211_rx+0x2f8/0x7ec [mac80211])
> [80527.424283] [<bf187eb8>] (ieee80211_rx+0x2f8/0x7ec [mac80211]) from [<bf28848c>] (ath9k_rx_tasklet+0x3b0/0x68c [ath9k_htc])
> [80527.424347] [<bf28848c>] (ath9k_rx_tasklet+0x3b0/0x68c [ath9k_htc]) from [<c002a94c>] (tasklet_action+0x5c/0xa8)
> [80527.424377] [<c002a94c>] (tasklet_action+0x5c/0xa8) from [<c002a0b8>] (__do_softirq+0xcc/0x278)
> [80527.424402] [<c002a0b8>] (__do_softirq+0xcc/0x278) from [<c002a290>] (run_ksoftirqd+0x2c/0x48)
> [80527.424437] [<c002a290>] (run_ksoftirqd+0x2c/0x48) from [<c004b74c>] (smpboot_thread_fn+0x15c/0x208)
> [80527.424475] [<c004b74c>] (smpboot_thread_fn+0x15c/0x208) from [<c0043d70>] (kthread+0xa4/0xb0)
> [80527.424510] [<c0043d70>] (kthread+0xa4/0xb0) from [<c000dc18>] (ret_from_fork+0x14/0x3c)
>
> Some more information:
> W-LAN Chipset: ID 0cf3:7015 Atheros Communications, Inc. TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287]
> Kernel: Linux pi1 3.10.27-2-ARCH #1 PREEMPT Tue Jan 21 00:42:16 MST 2014 armv6l GNU/Linux
>
> Any suggestion?
>
> Many thanks in advance.
> Flo
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
--
Regards,
Oleksij
next prev parent reply other threads:[~2014-01-23 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 18:30 [ath9k-devel] [BUG] Atheros AR7010+AR9287: Scheduling while atomic: ksoftirqd/0/3/0x00000302 mail at fuerstflorian.de
2014-01-23 19:44 ` Oleksij Rempel [this message]
2014-01-23 22:03 ` Antonio Quartulli
[not found] ` <trinity-14f555a0-3945-448b-a908-b12f1cb532e3-1390546291559@3capp-1and1-bs03>
2014-01-24 6:55 ` mail at fuerstflorian.de
2014-01-27 19:02 ` Oleksij Rempel
2014-01-27 19:02 ` Oleksij Rempel
2014-01-27 19:12 ` Antonio Quartulli
2014-01-27 19:12 ` Antonio Quartulli
2014-01-27 22:22 ` Johannes Berg
2014-01-27 22:22 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E1712B.70202@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.