From: Michael Buesch <mb@bu3sch.de>
To: "Jory A. Pratt" <anarchy@nctv.com>
Cc: netdev@vger.kernel.org
Subject: Re: bcm43xx scan oops!!!
Date: Tue, 10 Oct 2006 23:06:16 +0200 [thread overview]
Message-ID: <200610102306.16143.mb@bu3sch.de> (raw)
In-Reply-To: <452BACF2.60900@nctv.com>
On Tuesday 10 October 2006 16:23, Jory A. Pratt wrote:
> Michael Buesch wrote:
> > On Tuesday 10 October 2006 05:14, Jory A. Pratt wrote:
> >
> >> http://home.nctv.com/anarchy/dscape-clean.jpg
> >>
> >
> > That's hardly readable.
> > But which firmware are you running? v4.x by chance?
> >
> >
> Just for completeness I just tested with v4.x firmware and still get the
> panic
4.x firmware won't work. Make sure to use 3.x.
I am not sure what happens.
Any chance to get a more complete oops message? I am also interrested
in the start of the oops message. In particular I would like to see if this
is a NULL pointer bug, machine check or something else.
The backtrace is a little big weird. So I am not sure what happens.
And, Please make _really_ sure to use 3.x firmware. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2006-10-10 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 3:14 bcm43xx scan oops!!! Jory A. Pratt
2006-10-10 10:17 ` Michael Buesch
2006-10-10 13:38 ` Jory A. Pratt
[not found] ` <452BACF2.60900@nctv.com>
2006-10-10 21:06 ` Michael Buesch [this message]
2006-10-10 21:44 ` Jory A. Pratt
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=200610102306.16143.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=anarchy@nctv.com \
--cc=netdev@vger.kernel.org \
/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).