From: Ivo van Doorn <ivdoorn@gmail.com>
To: Adam Baker <linux@baker-net.org.uk>
Cc: linux-wireless@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: Re: Kernel BUG when using ad-hoc mode in rt2x00
Date: Tue, 14 Aug 2007 11:57:51 +0200 [thread overview]
Message-ID: <200708141157.52235.IvDoorn@gmail.com> (raw)
In-Reply-To: <200708082324.17186.linux@baker-net.org.uk>
On Thursday 09 August 2007, Adam Baker wrote:
> I've been seeing crashes when attempting to run an RT73 based device in ad-hoc
> mode (I'm using the rt2x00 git tree). I recently managed to capture the
> console output when it crashes and it all seems to point more to mac80211
> than the rt2x00 driver so I thought I'd ask here.
>
> a) If anyone can see anything obvious wrong in the trace
> b) If anyone has recently tested ad-hoc mode with another driver and can
> confirm it works.
>
> The sequence of events that leads to the crash is
> iwconfig wlan1 mode ad-hoc
> ifconfig wlan1 192.168.0.230
> iwconfig wlan1 channel 11
> iwconfig wlan1 essid test
>
> then attempt a scan from another device.
>
> My guess is that the lockdep warning is caused by trying to lock something in
> which the actual lock object has become corrupted hence it shortly afterwards
> deadlocks.
Well not a lot of responses so far. ;)
Adam, could you try below patch to see if that helps?
rt73usb_reset_tsf should be allowed to sleep, but perhaps this is not
really the case after all. :S
If the below patch does not work, then the bug really is inside mac80211
since all other callbacks are either not linked to adhoc or are not being scheduled
by rt2x00.
Ivo
---
diff --git a/drivers/net/wireless/rt73usb.c b/drivers/net/wireless/rt73usb.c
index 98d3acc..589d16f 100644
--- a/drivers/net/wireless/rt73usb.c
+++ b/drivers/net/wireless/rt73usb.c
@@ -1831,7 +1831,6 @@ static u64 rt73usb_get_tsf(struct ieee80211_hw *hw)
return tsf;
}
-#endif
static void rt73usb_reset_tsf(struct ieee80211_hw *hw)
{
@@ -1840,6 +1839,7 @@ static void rt73usb_reset_tsf(struct ieee80211_hw *hw)
rt73usb_register_write(rt2x00dev, TXRX_CSR12, 0);
rt73usb_register_write(rt2x00dev, TXRX_CSR13, 0);
}
+#endif
static const struct ieee80211_ops rt73usb_mac80211_ops = {
.tx = rt2x00mac_tx,
@@ -1858,8 +1858,8 @@ static const struct ieee80211_ops rt73usb_mac80211_ops = {
* See comment at the rt73usb_get_tsf function.
*/
.get_tsf = rt73usb_get_tsf,
-#endif
.reset_tsf = rt73usb_reset_tsf,
+#endif
.beacon_update = rt2x00usb_beacon_update,
};
next prev parent reply other threads:[~2007-08-14 9:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 22:24 Kernel BUG when using ad-hoc mode in rt2x00 Adam Baker
2007-08-14 9:57 ` Ivo van Doorn [this message]
2007-08-15 9:50 ` Johannes Berg
2007-08-15 21:49 ` Adam Baker
2007-08-16 13:48 ` Johannes Berg
2007-08-16 15:25 ` Adam Baker
2007-08-16 15:35 ` Johannes Berg
2007-08-16 21:43 ` Adam Baker
2007-08-17 10:13 ` Johannes Berg
2007-08-20 20:21 ` Adam Baker
2007-08-21 10:34 ` Johannes Berg
2007-09-25 21:09 ` Johannes Berg
2007-09-25 21:20 ` Johannes Berg
2007-09-27 22:00 ` Adam Baker
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=200708141157.52235.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@baker-net.org.uk \
--cc=rt2400-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).