From: Stanislaw Gruszka <stf_xl@wp.pl>
To: "Tuomas Räsänen" <tuomasjjrasanen@opinsys.fi>
Cc: Ivo van Doorn <IvDoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
tuomasjjrasanen@tjjr.fi, Veli-Matti Lintu <vmlintu@opinsys.fi>
Subject: Re: PROBLEM: skb_push called from rt2x00 panics occasionally
Date: Thu, 30 Jan 2014 20:39:06 +0100 [thread overview]
Message-ID: <20140130193906.GA2977@localhost.localdomain> (raw)
In-Reply-To: <879434908.52885.1391085222657.JavaMail.zimbra@opinsys.fi>
On Thu, Jan 30, 2014 at 12:33:42PM +0000, Tuomas Räsänen wrote:
> =================================================
> skb_push called from rt2x00 panics occasionally
> =================================================
>
> We have been experiencing occasional skb_push panics with rt2x00 driver
> throughout the stable v3.10 -series. Problems occur with hosts acting as
> accesspoints, managed by hostapd 2.0. Some hosts panic reportedly
> several times per week, some almost never. All hosts have identical
> kernels and WiFi adapters.
>
> We have not been able to reproduce panics in a controlled manner.
>
> I'd be very happy to get some advice how to proceed in debugging and fixing
> this problem and even better, to understand the whole issue
> thoroughly. Unfortunately, all I know now is that the skb headroom is
> not big enough for the frame the AP is trying to transmit, right?
> Hopefully someone can shed some light on this problem.
Yes, is possible that we have no headroom for frame retransmitted
several times, but I do not see bug in code for that so far.
We remove and add again l2 pad for retransmit frame, that should
not utilize more headroom than for first frame transmission (as long
mac80211 does not increase header length, but that seems to be not
possible and sensible).
For know you can try to increase headroom like on below patch or use
module with nohwcrypt=1. Please check if any of that stops panics or
just make it less reproducible.
You can also configure kdump to dump memory to see how skb looks when
kernel crashes.
Stanislaw
diff --git a/drivers/net/wireless/rt2x00/rt2x00.h b/drivers/net/wireless/rt2x00/rt2x00.h
index e4ba2ce..50fc3e7 100644
--- a/drivers/net/wireless/rt2x00/rt2x00.h
+++ b/drivers/net/wireless/rt2x00/rt2x00.h
@@ -115,7 +115,7 @@
* Constants for extra TX headroom for alignment purposes.
*/
#define RT2X00_ALIGN_SIZE 4 /* Only whole frame needs alignment */
-#define RT2X00_L2PAD_SIZE 8 /* Both header & payload need alignment */
+#define RT2X00_L2PAD_SIZE 12 /* Both header & payload need alignment */
/*
* Standard timing and size defines.
prev parent reply other threads:[~2014-01-30 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2018379362.52866.1391084425810.JavaMail.zimbra@opinsys.fi>
2014-01-30 12:33 ` PROBLEM: skb_push called from rt2x00 panics occasionally Tuomas Räsänen
2014-01-30 19:39 ` Stanislaw Gruszka [this message]
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=20140130193906.GA2977@localhost.localdomain \
--to=stf_xl@wp.pl \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tuomasjjrasanen@opinsys.fi \
--cc=tuomasjjrasanen@tjjr.fi \
--cc=users@rt2x00.serialmonkey.com \
--cc=vmlintu@opinsys.fi \
/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).