From: Pavel Roskin <proski@gnu.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
linux-kernel@vger.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit
Date: Sat, 31 May 2008 12:50:36 -0400 [thread overview]
Message-ID: <1212252636.2766.10.camel@rd> (raw)
In-Reply-To: <200805311841.46740.mb@bu3sch.de>
On Sat, 2008-05-31 at 18:41 +0200, Michael Buesch wrote:
> On Saturday 31 May 2008 18:34:29 Stefanik G=E1bor wrote:
> > "BUG: unable to handle kernel NULL pointer dereference at 00000004
> > IP: [<f8dd3a99>] :b43:b43_generate_txhdr+0x6a9/0x790
>=20
> So can you put a few printks into the function to see where it derefe=
rences
> a NULL pointer? (or use gdb to lookup the offset).
u8 key_idx =3D info->control.hw_key->hw_key_idx;
info->control.hw_key is NULL.
--=20
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
linux-kernel@vger.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit
Date: Sat, 31 May 2008 12:50:36 -0400 [thread overview]
Message-ID: <1212252636.2766.10.camel@rd> (raw)
In-Reply-To: <200805311841.46740.mb@bu3sch.de>
On Sat, 2008-05-31 at 18:41 +0200, Michael Buesch wrote:
> On Saturday 31 May 2008 18:34:29 Stefanik Gábor wrote:
> > "BUG: unable to handle kernel NULL pointer dereference at 00000004
> > IP: [<f8dd3a99>] :b43:b43_generate_txhdr+0x6a9/0x790
>
> So can you put a few printks into the function to see where it dereferences
> a NULL pointer? (or use gdb to lookup the offset).
u8 key_idx = info->control.hw_key->hw_key_idx;
info->control.hw_key is NULL.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-05-31 16:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 14:23 Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit Stefanik Gábor
2008-05-31 14:23 ` Stefanik Gábor
2008-05-31 15:11 ` Michael Buesch
2008-05-31 15:11 ` Michael Buesch
2008-05-31 16:34 ` Stefanik Gábor
2008-05-31 16:41 ` Michael Buesch
2008-05-31 16:41 ` Michael Buesch
2008-05-31 16:50 ` Pavel Roskin [this message]
2008-05-31 16:50 ` Pavel Roskin
2008-05-31 17:54 ` Michael Buesch
2008-05-31 17:54 ` Michael Buesch
2008-05-31 20:22 ` Johannes Berg
2008-05-31 20:29 ` Stefanik Gábor
2008-05-31 20:29 ` Stefanik Gábor
2008-05-31 20:48 ` Michael Buesch
2008-05-31 20:48 ` Michael Buesch
[not found] ` <20080602000841.qjrd66s3esgscko0-cebfxv@fcnzpbc.arg@webmail.spamcop.net>
2008-06-02 4:33 ` Pavel Roskin
2008-06-02 7:47 ` Johannes Berg
2008-05-31 16:48 ` Pavel Roskin
2008-05-31 16:48 ` Pavel Roskin
2008-05-31 16:54 ` Stefanik Gábor
2008-05-31 17:06 ` Pavel Roskin
2008-05-31 17:06 ` Pavel Roskin
2008-05-31 17:59 ` Michael Buesch
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=1212252636.2766.10.camel@rd \
--to=proski@gnu.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--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 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.