From: Larry Finger <Larry.Finger@lwfinger.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: REGRESSION: crash in wireless-testing smoketest
Date: Wed, 08 Feb 2012 09:37:28 -0600 [thread overview]
Message-ID: <4F3296B8.2050007@lwfinger.net> (raw)
In-Reply-To: <4F327C30.8060802@broadcom.com>
On 02/08/2012 07:44 AM, Arend van Spriel wrote:
> On 02/08/2012 02:02 PM, Johannes Berg wrote:
>>> I rerun the test on a kernel with some more lock checking and got lucky.
>>>
>>> Feb 8 08:40:17 lb-bun-10 kernel: [ 514.512283] wlan0: authenticate
>>> with 98:fc:11:8e:94:57
>>> Feb 8 08:40:17 lb-bun-10 kernel: [ 514.512515] wlan0: send auth to
>>> 98:fc:11:8e:94:57 (try 1/3)
>>> Feb 8 08:40:17 lb-bun-10 kernel: [ 514.514184] BUG: unable to handle
>>> kernel NULL pointer dereference at 00000004
>>
>> ...
>>
>>> Apparently, minstrel_ht expects some tx_status field filled in by
>>> brcmsmac/mac80211. Have not found the problem yet.
>>
>> So the patch you sent fixes this? Just making sure it's not a different
>> thing.
>>
>> johannes
>>
>
> Yes. I should probably have referred to this thread.
I have also seen the same crash in minstrel_tx_status, but it showed up in the
middle of revising p54usb to use asynchronous firmware loading, and I thought I
had some kind of subtle timing problem in the initialization. I certainly will
test the patch and report back.
Larry
prev parent reply other threads:[~2012-02-08 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 14:41 REGRESSION: crash in wireless-testing smoketest Arend van Spriel
2012-02-07 14:59 ` Johannes Berg
2012-02-07 17:25 ` Arend van Spriel
2012-02-07 20:32 ` Johannes Berg
2012-02-08 10:02 ` Arend van Spriel
2012-02-08 13:02 ` Johannes Berg
2012-02-08 13:44 ` Arend van Spriel
2012-02-08 15:37 ` Larry Finger [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=4F3296B8.2050007@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).