From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Crash in agg-tx.c, with ath9k and lots of STA VIFs.
Date: Tue, 05 Oct 2010 09:56:06 +0200 [thread overview]
Message-ID: <1286265366.3641.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CAA5861.4020503@candelatech.com>
On Mon, 2010-10-04 at 15:42 -0700, Ben Greear wrote:
> I did find a similar crash while debugging a kernel with just symbols
> compiled in (not kgdb) though:
Doesn't seem all that similar...
> The interesting thing to me is that the 00100104 address is the same in
> both crashes, though this one is in a different method.
except for that maybe. But this is LIST_POISON1, and with seemingly
different lists. It may be faster to reproduce if you enable slab/slub
debugging.
> Also, this is with power-save NOT disabled (I was hoping to
> hit some debugging code I put in for the other crash..hit this instead.)
>
> Oct 4 15:26:15 localhost kernel: BUG: unable to handle kernel paging request at 00100104
> Oct 4 15:26:15 localhost kernel: IP: [<fc77e038>] cfg80211_unlink_bss+0x4d/0x8d [cfg80211]
Looks like a mac80211 bug, but you snipped the stack trace.
johannes
next prev parent reply other threads:[~2010-10-05 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 18:51 Crash in agg-tx.c, with ath9k and lots of STA VIFs Ben Greear
2010-10-04 19:01 ` Johannes Berg
2010-10-04 19:04 ` Ben Greear
2010-10-04 19:10 ` Johannes Berg
2010-10-04 21:12 ` Luis R. Rodriguez
2010-10-04 21:13 ` Luis R. Rodriguez
2010-10-04 21:38 ` Ben Greear
2010-10-04 22:42 ` Ben Greear
2010-10-05 7:56 ` Johannes Berg [this message]
2010-10-05 16:24 ` Ben Greear
2010-10-04 23:48 ` Luis R. Rodriguez
2010-10-05 3:39 ` Ben Greear
2010-10-05 6:09 ` Luis R. Rodriguez
2010-10-05 3:43 ` Ben Greear
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=1286265366.3641.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 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.