From: reinette chatre <reinette.chatre@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Ranson <ranson@analager.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Unable to load iwlagn module: Failed to register hw (error -17)
Date: Wed, 15 Jul 2009 09:16:13 -0700 [thread overview]
Message-ID: <1247674573.17896.1989.camel@rc-desk> (raw)
In-Reply-To: <1247674310.10754.19.camel@johannes.local>
On Wed, 2009-07-15 at 09:11 -0700, Johannes Berg wrote:
> Hi,
>
> > On Tue, 2009-07-14 at 21:25 -0700, John Ranson wrote:
> > > [ 4.252445] iwlagn 0000:03:00.0: Tunable channels: 11 802.11bg, 13
> > > 802.11a channels
> > > [ 4.252556] iwlagn 0000:03:00.0: irq 30 for MSI/MSI-X
> > > [ 4.252945] iwlagn 0000:03:00.0: Failed to register hw (error -17)
> > > [ 4.253255] iwlagn 0000:03:00.0: PCI INT A disabled
> > > [ 4.253263] iwlagn: probe of 0000:03:00.0 failed with error -17
> >
> > This is ieee80211_register_hw() returning error 17 (EEXIST). One spot I
> > saw where this can happen is if you are trying to register with the same
> > name (wlanX) already used by another netdevice. Does this sound possible
> > in your setup?
> >
> > Johannes - do you perhaps have an idea when this can happen?
>
> This is strange -- I've had one report of this with 3945 which went away
> and seemed to have been a compat only issue, I suspect this is also just
> a compat-wireless issue, but I have no idea.
>
> -EEXIST should only happen if something has already claimed something in
> sysfs, but not with netdevs (i.e. wlan0 would just be renamed to wlan1)
> and phy0 is numbered all the time so that can't be it either. I don't
> know.
fyi ... I based my response on register_netdevice() being able to return
-EEXIST at the time it checks for the existence of "name".
Reinette
next prev parent reply other threads:[~2009-07-15 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 4:25 Unable to load iwlagn module: Failed to register hw (error -17) John Ranson
2009-07-15 16:02 ` reinette chatre
2009-07-15 16:11 ` Johannes Berg
2009-07-15 16:16 ` reinette chatre [this message]
2009-07-15 16:21 ` Johannes Berg
2009-07-15 16:25 ` Luis R. Rodriguez
2009-07-16 3:58 ` John Ranson
2009-07-16 16:13 ` Luis R. Rodriguez
2009-07-26 2:41 ` John Ranson
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=1247674573.17896.1989.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ranson@analager.net \
/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