linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Michael Buesch <mbuesch@freenet.de>
Subject: Re: Oops in ieee80211_register_hw
Date: Sun, 29 Apr 2007 21:01:44 +0200	[thread overview]
Message-ID: <200704292101.45018.mb@bu3sch.de> (raw)
In-Reply-To: <200704272026.11196.flamingice@sourmilk.net>

On Saturday 28 April 2007 02:26:06 Michael Wu wrote:
> On Friday 27 April 2007 17:37, Jiri Benc wrote:
> > has anyone an idea what's going on here?
> >
> > How to reproduce:
> > 1. modprobe bcm43xx_mac80211
> > 2. plug in my cardbus bcm4318 card
> > (note that if I swap these two steps, the oops doesn't occur)
> >
> > By adding debug printks, I located the place where the null dereference
> > happens. Please note that I have Michael Wu's latest patches applied.
> > It's in
> > 	name = wiphy_dev(local->hw.wiphy)->driver->name;
> > and wiphy_dev(local->hw.wiphy) is NULL.
> >
> I've attached a patch. I don't have the hardware so I don't know if it'll 
> work, but it seems right to me.

Thanks for that patch. It's almost right.
I committed the right fix.
http://bu3sch.de/gitweb?p=wireless-dev.git;a=commitdiff;h=7371ae7ba51fb380681584c9132540ff5a86604a

-- 
Greetings Michael.

      parent reply	other threads:[~2007-04-29 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 21:37 Oops in ieee80211_register_hw Jiri Benc
2007-04-28  0:26 ` Michael Wu
2007-04-28 12:31   ` Jiri Benc
2007-04-29 19:01   ` Michael Buesch [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=200704292101.45018.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mbuesch@freenet.de \
    /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).