From: Bob Copeland <me@bobcopeland.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
linux-wireless@vger.kernel.org, linux-net@vger.kernel.org,
linux-mips@vger.kernel.org
Subject: Re: ath5k AP kernel panic when client uses SCP
Date: Sat, 24 Oct 2009 08:52:17 -0400 [thread overview]
Message-ID: <20091024125217.GA31897@hash.localnet> (raw)
In-Reply-To: <4AE2EC3E.3000503@wpkg.org>
>> I'll recompile...
>
> Is this one more useful?
Much! Thanks.
> [ 516.430000] ------------[ cut here ]------------
> [ 516.430000] WARNING: at net/core/dev.c:1566 skb_gso_segment+0x110/0x298()
> [ 516.440000] b44: caps=(0x0, 0x0) len=52 data_len=0 ip_summed=1
So this looks like the ethernet driver b44 instead of ath5k, I think.
> [ 516.450000] Modules linked in: configs aes_generic tun sch_sfq cls_fw sch_htb ipt_MASQUERADE iptable_nat nf_nat xt_MARK iptable_mangle ipt_ULOG xt_recent nf_conn1
> [ 516.480000] Call Trace:
> [ 516.480000] [<80013ac4>] dump_stack+0x8/0x34
> [ 516.480000] [<8002f2a0>] warn_slowpath_common+0x70/0x98
> [ 516.490000] [<8002f308>] warn_slowpath_fmt+0x24/0x30
> [ 516.490000] [<801f0398>] skb_gso_segment+0x110/0x298
...but this is higher up the stack. skb_gso_segment is about a year old
so it would be odd if there were a bug here. Can you do the following?
objdump -S net/core/dev.o, then find the address for skb_gso_segment,
it should look something like this (your numbers and disassembly will
differ):
00004190 <skb_gso_segment>:
*
* It may return NULL if the skb requires no segmentation. This is
* only possible when GSO is used for verifying header integrity.
*/
struct sk_buff *skb_gso_segment(struct sk_buff *skb, int features)
{
4190: 55 push %ebp
4191: 89 e5 mov %esp,%ebp
4193: 57 push %edi
4194: 56 push %esi
Then find whatever 0x4190 (your offset here) + 0x110 is, and pick about
10 lines before and after that and paste it -- the opcodes in the second
column should match up with the code lines below:
> [ 516.650000] [ 516.650000] [ 516.650000] Code: 3c048007 08010d50
> 248436fc <8c820000> 3042c000 10400003 00803821 0801ca7f 00000000 [
Or you can send me the whole objdump -S output off-list if that's easier.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-10-24 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 17:49 ath5k AP kernel panic when client uses SCP Tomasz Chmielewski
2009-10-11 17:55 ` Tomasz Chmielewski
2009-10-11 22:47 ` Bob Copeland
2009-10-12 8:13 ` Tomasz Chmielewski
2009-10-12 8:13 ` Tomasz Chmielewski
2009-10-23 13:15 ` Tomasz Chmielewski
2009-10-23 13:21 ` Gábor Stefanik
2009-10-23 13:24 ` Tomasz Chmielewski
2009-10-24 11:59 ` Tomasz Chmielewski
2009-10-24 12:52 ` Bob Copeland [this message]
2009-10-24 15:27 ` Tomasz Chmielewski
2009-10-24 16:09 ` Bob Copeland
2009-10-24 18:10 ` Tomasz Chmielewski
2009-10-25 20:19 ` Bob Copeland
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=20091024125217.GA31897@hash.localnet \
--to=me@bobcopeland.com \
--cc=linux-mips@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=netrolller.3d@gmail.com \
/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).