* Unable to load iwlagn module: Failed to register hw (error -17)
@ 2009-07-15 4:25 John Ranson
2009-07-15 16:02 ` reinette chatre
0 siblings, 1 reply; 9+ messages in thread
From: John Ranson @ 2009-07-15 4:25 UTC (permalink / raw)
To: linux-wireless
I just installed the latest compat-wireless to get drivers for my
iwl4965 card. I can't load the iwlagn module. I'm running 2.6.30.
Is this a bug, or did I do something wrong?
John
Here is my dmesg output.
[ 4.201255] iwlagn: Intel(R) Wireless WiFi Link AGN driver for
Linux, 1.3.27kds
[ 4.201258] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[ 4.201389] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 4.201422] iwlagn 0000:03:00.0: setting latency timer to 64
[ 4.201490] ieee80211 phy0: U iwl_pci_probe pci_resource_len = 0x00002000
[ 4.201493] ieee80211 phy0: U iwl_pci_probe pci_resource_base =
ffffc20004088000
[ 4.201525] iwlagn 0000:03:00.0: Detected Intel Wireless WiFi Link
4965AGN REV=0x4
[ 4.201536] ieee80211 phy0: U iwl_prepare_card_hw iwl_prepare_card_hw enter
[ 4.201546] ieee80211 phy0: U iwl_set_hw_ready hardware ready
[ 4.221075] usb 1-1: new full speed USB device using uhci_hcd and address 2
[ 4.252084] ieee80211 phy0: U iwl_pci_probe MAC address: 00:13:e8:d3:9e:77
[ 4.252089] ieee80211 phy0: U iwl_set_rxon_chain rx_chain=0x2806
active=2 idle=2
[ 4.252092] ieee80211 phy0: U iwl_init_channel_map Initializing
regulatory info from EEPROM
[ 4.252095] ieee80211 phy0: U iwl_init_channel_map Parsing data for
56 channels.
[ 4.252117] ieee80211 phy0: U iwl_init_channel_map Ch. 1 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252121] ieee80211 phy0: U iwl_init_channel_map Ch. 2 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252125] ieee80211 phy0: U iwl_init_channel_map Ch. 3 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252129] ieee80211 phy0: U iwl_init_channel_map Ch. 4 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252132] ieee80211 phy0: U iwl_init_channel_map Ch. 5 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252136] ieee80211 phy0: U iwl_init_channel_map Ch. 6 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252140] ieee80211 phy0: U iwl_init_channel_map Ch. 7 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252143] ieee80211 phy0: U iwl_init_channel_map Ch. 8 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252147] ieee80211 phy0: U iwl_init_channel_map Ch. 9 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252151] ieee80211 phy0: U iwl_init_channel_map Ch. 10 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252155] ieee80211 phy0: U iwl_init_channel_map Ch. 11 [2.4GHz]
VALID IBSS ACTIVE WIDE (0x2b 14dBm): Ad-Hoc supported
[ 4.252158] ieee80211 phy0: U iwl_init_channel_map Ch. 12 Flags 0
[2.4GHz] - No traffic
[ 4.252160] ieee80211 phy0: U iwl_init_channel_map Ch. 13 Flags 0
[2.4GHz] - No traffic
[ 4.252163] ieee80211 phy0: U iwl_init_channel_map Ch. 14 Flags 0
[2.4GHz] - No traffic
[ 4.252165] ieee80211 phy0: U iwl_init_channel_map Ch. 183 Flags 0
[5.2GHz] - No traffic
[ 4.252168] ieee80211 phy0: U iwl_init_channel_map Ch. 184 Flags 0
[5.2GHz] - No traffic
[ 4.252170] ieee80211 phy0: U iwl_init_channel_map Ch. 185 Flags 0
[5.2GHz] - No traffic
[ 4.252173] ieee80211 phy0: U iwl_init_channel_map Ch. 187 Flags 0
[5.2GHz] - No traffic
[ 4.252175] ieee80211 phy0: U iwl_init_channel_map Ch. 188 Flags 0
[5.2GHz] - No traffic
[ 4.252178] ieee80211 phy0: U iwl_init_channel_map Ch. 189 Flags 0
[5.2GHz] - No traffic
[ 4.252180] ieee80211 phy0: U iwl_init_channel_map Ch. 192 Flags 0
[5.2GHz] - No traffic
[ 4.252183] ieee80211 phy0: U iwl_init_channel_map Ch. 196 Flags 0
[5.2GHz] - No traffic
[ 4.252186] ieee80211 phy0: U iwl_init_channel_map Ch. 7 Flags 0
[5.2GHz] - No traffic
[ 4.252188] ieee80211 phy0: U iwl_init_channel_map Ch. 8 Flags 0
[5.2GHz] - No traffic
[ 4.252191] ieee80211 phy0: U iwl_init_channel_map Ch. 11 Flags 0
[5.2GHz] - No traffic
[ 4.252193] ieee80211 phy0: U iwl_init_channel_map Ch. 12 Flags 0
[5.2GHz] - No traffic
[ 4.252196] ieee80211 phy0: U iwl_init_channel_map Ch. 16 Flags 0
[5.2GHz] - No traffic
[ 4.252198] ieee80211 phy0: U iwl_init_channel_map Ch. 34 Flags 0
[5.2GHz] - No traffic
[ 4.252201] ieee80211 phy0: U iwl_init_channel_map Ch. 36 [5.2GHz]
VALID WIDE (0x21 15dBm): Ad-Hoc not supported
[ 4.252204] ieee80211 phy0: U iwl_init_channel_map Ch. 38 Flags 0
[5.2GHz] - No traffic
[ 4.252207] ieee80211 phy0: U iwl_init_channel_map Ch. 40 [5.2GHz]
VALID WIDE (0x21 15dBm): Ad-Hoc not supported
[ 4.252210] ieee80211 phy0: U iwl_init_channel_map Ch. 42 Flags 0
[5.2GHz] - No traffic
[ 4.252214] ieee80211 phy0: U iwl_init_channel_map Ch. 44 [5.2GHz]
VALID WIDE (0x21 15dBm): Ad-Hoc not supported
[ 4.252216] ieee80211 phy0: U iwl_init_channel_map Ch. 46 Flags 0
[5.2GHz] - No traffic
[ 4.252220] ieee80211 phy0: U iwl_init_channel_map Ch. 48 [5.2GHz]
VALID WIDE (0x21 15dBm): Ad-Hoc not supported
[ 4.252224] ieee80211 phy0: U iwl_init_channel_map Ch. 52 [5.2GHz]
VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
[ 4.252227] ieee80211 phy0: U iwl_init_channel_map Ch. 56 [5.2GHz]
VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
[ 4.252231] ieee80211 phy0: U iwl_init_channel_map Ch. 60 [5.2GHz]
VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
[ 4.252234] ieee80211 phy0: U iwl_init_channel_map Ch. 64 [5.2GHz]
VALID RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
[ 4.252243] ieee80211 phy0: U iwl_init_channel_map Ch. 100 Flags 0
[5.2GHz] - No traffic
[ 4.252245] ieee80211 phy0: U iwl_init_channel_map Ch. 104 Flags 0
[5.2GHz] - No traffic
[ 4.252247] ieee80211 phy0: U iwl_init_channel_map Ch. 108 Flags 0
[5.2GHz] - No traffic
[ 4.252249] ieee80211 phy0: U iwl_init_channel_map Ch. 112 Flags 0
[5.2GHz] - No traffic
[ 4.252252] ieee80211 phy0: U iwl_init_channel_map Ch. 116 Flags 0
[5.2GHz] - No traffic
[ 4.252254] ieee80211 phy0: U iwl_init_channel_map Ch. 120 Flags 0
[5.2GHz] - No traffic
[ 4.252256] ieee80211 phy0: U iwl_init_channel_map Ch. 124 Flags 0
[5.2GHz] - No traffic
[ 4.252258] ieee80211 phy0: U iwl_init_channel_map Ch. 128 Flags 0
[5.2GHz] - No traffic
[ 4.252274] ieee80211 phy0: U iwl_init_channel_map Ch. 132 Flags 0
[5.2GHz] - No traffic
[ 4.252276] ieee80211 phy0: U iwl_init_channel_map Ch. 136 Flags 0
[5.2GHz] - No traffic
[ 4.252278] ieee80211 phy0: U iwl_init_channel_map Ch. 140 Flags 0
[5.2GHz] - No traffic
[ 4.252281] ieee80211 phy0: U iwl_init_channel_map Ch. 145 Flags 0
[5.2GHz] - No traffic
[ 4.252284] ieee80211 phy0: U iwl_init_channel_map Ch. 149 [5.2GHz]
VALID WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252287] ieee80211 phy0: U iwl_init_channel_map Ch. 153 [5.2GHz]
VALID WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252290] ieee80211 phy0: U iwl_init_channel_map Ch. 157 [5.2GHz]
VALID WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252293] ieee80211 phy0: U iwl_init_channel_map Ch. 161 [5.2GHz]
VALID WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252297] ieee80211 phy0: U iwl_init_channel_map Ch. 165 [5.2GHz]
VALID WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252300] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 1
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252303] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 5
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252306] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 2
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252309] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 6
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252312] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 3
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252315] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 7
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252318] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 4
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252321] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 8
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252324] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 5
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252327] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 9
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252330] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 6
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252333] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 10
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252336] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 7
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252339] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 11
[2.4GHz] (0x00 0dBm): Ad-Hoc not supported
[ 4.252342] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 36
[5.2GHz] WIDE (0x21 13dBm): Ad-Hoc not supported
[ 4.252346] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 40
[5.2GHz] WIDE (0x21 13dBm): Ad-Hoc not supported
[ 4.252349] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 44
[5.2GHz] WIDE (0x21 15dBm): Ad-Hoc not supported
[ 4.252352] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 48
[5.2GHz] WIDE (0x21 15dBm): Ad-Hoc not supported
[ 4.252355] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 52
[5.2GHz] RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
[ 4.252359] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 56
[5.2GHz] RADAR WIDE (0x31 15dBm): Ad-Hoc not supported
[ 4.252362] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 60
[5.2GHz] RADAR WIDE (0x31 14dBm): Ad-Hoc not supported
[ 4.252365] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 64
[5.2GHz] RADAR WIDE (0x31 14dBm): Ad-Hoc not supported
[ 4.252369] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 149
[5.2GHz] WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252372] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 153
[5.2GHz] WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252375] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 157
[5.2GHz] WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252379] ieee80211 phy0: U iwl_set_fat_chan_info FAT Ch. 161
[5.2GHz] WIDE (0x21 16dBm): Ad-Hoc not supported
[ 4.252383] ieee80211 phy0: U iwlcore_init_geos Channel 1
Freq=2412[2.4GHz] valid flag=0x20
[ 4.252386] ieee80211 phy0: U iwlcore_init_geos Channel 2
Freq=2417[2.4GHz] valid flag=0x20
[ 4.252388] ieee80211 phy0: U iwlcore_init_geos Channel 3
Freq=2422[2.4GHz] valid flag=0x20
[ 4.252391] ieee80211 phy0: U iwlcore_init_geos Channel 4
Freq=2427[2.4GHz] valid flag=0x20
[ 4.252394] ieee80211 phy0: U iwlcore_init_geos Channel 5
Freq=2432[2.4GHz] valid flag=0x0
[ 4.252396] ieee80211 phy0: U iwlcore_init_geos Channel 6
Freq=2437[2.4GHz] valid flag=0x0
[ 4.252399] ieee80211 phy0: U iwlcore_init_geos Channel 7
Freq=2442[2.4GHz] valid flag=0x0
[ 4.252401] ieee80211 phy0: U iwlcore_init_geos Channel 8
Freq=2447[2.4GHz] valid flag=0x10
[ 4.252404] ieee80211 phy0: U iwlcore_init_geos Channel 9
Freq=2452[2.4GHz] valid flag=0x10
[ 4.252406] ieee80211 phy0: U iwlcore_init_geos Channel 10
Freq=2457[2.4GHz] valid flag=0x10
[ 4.252409] ieee80211 phy0: U iwlcore_init_geos Channel 11
Freq=2462[2.4GHz] valid flag=0x10
[ 4.252412] ieee80211 phy0: U iwlcore_init_geos Channel 36
Freq=5180[5.2GHz] valid flag=0x26
[ 4.252415] ieee80211 phy0: U iwlcore_init_geos Channel 40
Freq=5200[5.2GHz] valid flag=0x16
[ 4.252417] ieee80211 phy0: U iwlcore_init_geos Channel 44
Freq=5220[5.2GHz] valid flag=0x26
[ 4.252420] ieee80211 phy0: U iwlcore_init_geos Channel 48
Freq=5240[5.2GHz] valid flag=0x16
[ 4.252422] ieee80211 phy0: U iwlcore_init_geos Channel 52
Freq=5260[5.2GHz] valid flag=0x2E
[ 4.252425] ieee80211 phy0: U iwlcore_init_geos Channel 56
Freq=5280[5.2GHz] valid flag=0x1E
[ 4.252428] ieee80211 phy0: U iwlcore_init_geos Channel 60
Freq=5300[5.2GHz] valid flag=0x2E
[ 4.252430] ieee80211 phy0: U iwlcore_init_geos Channel 64
Freq=5320[5.2GHz] valid flag=0x1E
[ 4.252433] ieee80211 phy0: U iwlcore_init_geos Channel 149
Freq=5745[5.2GHz] valid flag=0x26
[ 4.252435] ieee80211 phy0: U iwlcore_init_geos Channel 153
Freq=5765[5.2GHz] valid flag=0x16
[ 4.252438] ieee80211 phy0: U iwlcore_init_geos Channel 157
Freq=5785[5.2GHz] valid flag=0x26
[ 4.252441] ieee80211 phy0: U iwlcore_init_geos Channel 161
Freq=5805[5.2GHz] valid flag=0x16
[ 4.252443] ieee80211 phy0: U iwlcore_init_geos Channel 165
Freq=5825[5.2GHz] valid flag=0x36
[ 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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
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
0 siblings, 1 reply; 9+ messages in thread
From: reinette chatre @ 2009-07-15 16:02 UTC (permalink / raw)
To: John Ranson; +Cc: linux-wireless
Hi John,
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?
Reinette
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-15 16:02 ` reinette chatre
@ 2009-07-15 16:11 ` Johannes Berg
2009-07-15 16:16 ` reinette chatre
2009-07-15 16:25 ` Luis R. Rodriguez
0 siblings, 2 replies; 9+ messages in thread
From: Johannes Berg @ 2009-07-15 16:11 UTC (permalink / raw)
To: reinette chatre; +Cc: John Ranson, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
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.
John, can you poke around in sysfs, /sys/class/ieee80211/ and see if
there's anything there when loading fails?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-15 16:11 ` Johannes Berg
@ 2009-07-15 16:16 ` reinette chatre
2009-07-15 16:21 ` Johannes Berg
2009-07-15 16:25 ` Luis R. Rodriguez
1 sibling, 1 reply; 9+ messages in thread
From: reinette chatre @ 2009-07-15 16:16 UTC (permalink / raw)
To: Johannes Berg; +Cc: John Ranson, linux-wireless
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-15 16:16 ` reinette chatre
@ 2009-07-15 16:21 ` Johannes Berg
0 siblings, 0 replies; 9+ messages in thread
From: Johannes Berg @ 2009-07-15 16:21 UTC (permalink / raw)
To: reinette chatre; +Cc: John Ranson, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Wed, 2009-07-15 at 09:16 -0700, reinette chatre wrote:
> > -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".
Yes, it does that, but we don't ask it for a fixed name -- we allocate
"wlan%d" and in the same rtnl-locked section register it, so we should
always get a new number and be able to register that number.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-15 16:11 ` Johannes Berg
2009-07-15 16:16 ` reinette chatre
@ 2009-07-15 16:25 ` Luis R. Rodriguez
2009-07-16 3:58 ` John Ranson
1 sibling, 1 reply; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-07-15 16:25 UTC (permalink / raw)
To: Johannes Berg; +Cc: reinette chatre, John Ranson, linux-wireless
On Wed, Jul 15, 2009 at 9:11 AM, Johannes Berg<johannes@sipsolutions.net> 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.
We've had a lot of changes to compat-wireless recently so this is possible.
John, can you cat compat-release on your compat-wireless directory?
Luis
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-15 16:25 ` Luis R. Rodriguez
@ 2009-07-16 3:58 ` John Ranson
2009-07-16 16:13 ` Luis R. Rodriguez
0 siblings, 1 reply; 9+ messages in thread
From: John Ranson @ 2009-07-16 3:58 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: Johannes Berg, reinette chatre, linux-wireless
The release is master-2009-07-08-3-g3615cdf
/sys/class/ieee80211/ is empty
I'm running Gentoo on an Lenovo R61. I don't think that there is
anything too special about my configuration.
Is there any more information that I can provide that will help debug?
Thanks,
John
On Wed, Jul 15, 2009 at 9:25 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Wed, Jul 15, 2009 at 9:11 AM, Johannes Berg<johannes@sipsolutions.net> 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.
>
> We've had a lot of changes to compat-wireless recently so this is possible.
>
> John, can you cat compat-release on your compat-wireless directory?
>
> Luis
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-16 3:58 ` John Ranson
@ 2009-07-16 16:13 ` Luis R. Rodriguez
2009-07-26 2:41 ` John Ranson
0 siblings, 1 reply; 9+ messages in thread
From: Luis R. Rodriguez @ 2009-07-16 16:13 UTC (permalink / raw)
To: John Ranson; +Cc: Johannes Berg, reinette chatre, linux-wireless
On Wed, Jul 15, 2009 at 8:58 PM, John Ranson<ranson@analager.net> wrote:
> The release is master-2009-07-08-3-g3615cdf
>
> /sys/class/ieee80211/ is empty
>
> I'm running Gentoo on an Lenovo R61. I don't think that there is
> anything too special about my configuration.
>
> Is there any more information that I can provide that will help debug?
You can try wireless-testing directly:
http://wireless.kernel.org/en/developers/Documentation/git-guide
Luis
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Unable to load iwlagn module: Failed to register hw (error -17)
2009-07-16 16:13 ` Luis R. Rodriguez
@ 2009-07-26 2:41 ` John Ranson
0 siblings, 0 replies; 9+ messages in thread
From: John Ranson @ 2009-07-26 2:41 UTC (permalink / raw)
To: Luis R. Rodriguez; +Cc: Johannes Berg, reinette chatre, linux-wireless
Running wireless testing directly fixed this issue.
John
On Thu, Jul 16, 2009 at 9:13 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Wed, Jul 15, 2009 at 8:58 PM, John Ranson<ranson@analager.net> wrote:
>> The release is master-2009-07-08-3-g3615cdf
>>
>> /sys/class/ieee80211/ is empty
>>
>> I'm running Gentoo on an Lenovo R61. I don't think that there is
>> anything too special about my configuration.
>>
>> Is there any more information that I can provide that will help debug?
>
> You can try wireless-testing directly:
>
> http://wireless.kernel.org/en/developers/Documentation/git-guide
>
> Luis
>
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2009-07-26 2:41 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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).