From: Gregoire Gentil <gregoire@gentil.com>
To: linux-rt-users@vger.kernel.org
Subject: TI wl1271 wireless bug with 3.4-rt17
Date: Sun, 02 Sep 2012 23:24:47 -0700 [thread overview]
Message-ID: <50444D2F.3040607@gentil.com> (raw)
In-Reply-To: <20120902194911.GT28643@pengutronix.de>
Hello,
I'm trying to debug a wifi bug with 3.4-rt17 applied, running on an
OMAP4 ARM board such as Pandaboard.
Wi-Fi works perfectly well without rt patches. It also works quite well
with rt patches AND without wifi module loaded. But with both rt patches
and wifi module, the system is very flaky and even if I manage to launch
a big download, I get a kernel hang. I managed to get a trace:
BUG: scheduling while atomic: irq/213-wl12xx/1588/0x00010002
Modules linked in: omapdce(C) wl12xx wlcore omaprpc(C) mac80211 d
[<c001beb4>] (unwind_backtrace+0x0/0xf0) from [<c0613548>] (dump)
[<c0613548>] (dump_stack+0x20/0x24) from [<c0073908>] (__schedul)
[<c0073908>] (__schedule_bug+0x54/0x60) from [<c0614818>] (__sch)
[<c0614818>] (__schedule+0x74/0x6c0) from [<c0614f60>] (schedule)
[<c0614f60>] (schedule+0xa0/0xb8) from [<c0615eb8>] (rt_spin_loc)
[<c0615eb8>] (rt_spin_lock_slowlock+0x198/0x288) from [<c06160a8)
[<c06160a8>] (rt_spin_lock+0x18/0x1c) from [<bf0c6b24>] (wl12xx_)
[<bf0c6b24>] (wl12xx_hardirq+0x2c/0xa4 [wlcore]) from [<c00bd4f0)
[<c00bd4f0>] (handle_irq_event_percpu+0xac/0x24c) from [<c00bd70)
[<c00bd70c>] (handle_irq_event+0x7c/0x9c) from [<c00c08f0>] (han)
[<c00c08f0>] (handle_level_irq+0xe4/0x134) from [<c00bcf58>] (ge)
[<c00bcf58>] (generic_handle_irq+0x34/0x3c) from [<c03217e8>] (g)
[<c03217e8>] (gpio_irq_handler+0x160/0x1a4) from [<c00bcf58>] (g)
[<c00bcf58>] (generic_handle_irq+0x34/0x3c) from [<c001449c>] (h)
[<c001449c>] (handle_IRQ+0x88/0xc8)
Source code including the function wl12xx_hardirq is here:
http://dev.omapzoom.org/?p=integration/kernel-ubuntu.git;a=blob;f=drivers/net/wireless/ti/wlcore/main.c;h=45fe911a6504f92dddff5a9415bb77a643b3c4a9;hb=f84c72f6b36418ff11d16808c16a7c3216730bb0
Any idea what could be wrong and how I could debug and fix this situation?
Many thanks in advance,
Grégoire
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-03 6:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 20:48 Don't reference non-standard realtime group Uwe Kleine-König
2012-09-02 19:49 ` Uwe Kleine-König
2012-09-03 6:10 ` "g_serial: fix deadlock with PREEMPT_RT enabled" still not integrated Gregoire Gentil
2012-09-03 6:24 ` Gregoire Gentil [this message]
2012-09-04 14:11 ` TI wl1271 wireless bug with 3.4-rt17 Josh Cartwright
2012-09-05 1:22 ` Gregoire Gentil
2012-09-06 3:48 ` Josh Cartwright
2012-09-06 4:22 ` Gregoire Gentil
2012-09-09 22:42 ` Gregoire Gentil
2012-09-09 22:51 ` how to put in higher priority a thread in rt-kernel? Gregoire Gentil
2012-09-10 3:52 ` Mike Galbraith
2012-09-10 5:23 ` Gregoire Gentil
2012-09-10 16:20 ` Clark Williams
2012-10-15 23:13 ` Don't reference non-standard realtime group John Kacur
2012-10-16 18:26 ` Josh Cartwright
2012-10-18 16:13 ` Josh Cartwright
2012-10-19 2:12 ` Clark Williams
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=50444D2F.3040607@gentil.com \
--to=gregoire@gentil.com \
--cc=linux-rt-users@vger.kernel.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.