Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#10252 - iwl3945 fails to connect to 11a networks
Attached to Project:
Arch Linux
Opened by Johannes Krampf (wuischke) - Tuesday, 22 April 2008, 07:07 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 19 May 2009, 15:49 GMT
Opened by Johannes Krampf (wuischke) - Tuesday, 22 April 2008, 07:07 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 19 May 2009, 15:49 GMT
|
DetailsDescription: After selecting a channel available in EU and US I could successfully scan for my 11a network. I can't, however, connect and get a weird error.
PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 100002, writing 100006) Registered led device: iwl-phy0:radio Registered led device: iwl-phy0:assoc Registered led device: iwl-phy0:RX Registered led device: iwl-phy0:TX ------------[ cut here ]------------ WARNING: at kernel/mutex-debug.c:82 debug_mutex_unlock+0x115/0x120() Modules linked in: i915 drm aes_x86_64 aes_generic ipv6 cpufreq_ondemand joydev firewire_ohci firewire_core crc_itu_t serio_raw ohci1394 psmouse i2c_i801 sdhci pcspkr ricoh_mmc mmc_core ieee1394 i2c_core video container output intel_agp sg thermal fan evdev button battery ac acpi_cpufreq freq_table processor snd_hda_intel snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_hwdep snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd soundcore arc4 ecb iwl3945 mac80211 led_class cfg80211 e100 mii rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sd_mod usbhid hid ff_memless usb_storage sr_mod cdrom ehci_hcd uhci_hcd usbcore ata_piix ahci ata_generic pata_acpi libata scsi_mod dock Pid: 1407, comm: iwl3945 Not tainted 2.6.25-ARCH #1 Call Trace: [<ffffffff8023a4d4>] warn_on_slowpath+0x64/0xb0 [<ffffffff8815dda5>] :mac80211:ieee80211_master_start_xmit+0x465/0x870 [<ffffffff80333d18>] scnprintf+0x48/0x60 [<ffffffff8025d1c5>] debug_mutex_unlock+0x115/0x120 [<ffffffff8045dedc>] __mutex_unlock_slowpath+0x7c/0x170 [<ffffffff8817bb03>] :iwl3945:iwl3945_mac_config_interface+0x43/0x3e0 [<ffffffff8814668c>] :mac80211:__ieee80211_if_config+0x8c/0x100 [<ffffffff8814dcb3>] :mac80211:ieee80211_sta_set_bssid+0xb3/0xd0 [<ffffffff881545d4>] :mac80211:ieee80211_sta_work+0x504/0x700 [<ffffffff881540d0>] :mac80211:ieee80211_sta_work+0x0/0x700 [<ffffffff8024d966>] run_workqueue+0x86/0x150 [<ffffffff8024dacf>] worker_thread+0x9f/0x110 [<ffffffff80251cf0>] autoremove_wake_function+0x0/0x30 [<ffffffff8024da30>] worker_thread+0x0/0x110 [<ffffffff80251957>] kthread+0x47/0x90 [<ffffffff80237507>] schedule_tail+0x27/0x60 [<ffffffff8020d638>] child_rip+0xa/0x12 [<ffffffff80251910>] kthread+0x0/0x90 [<ffffffff8020d62e>] child_rip+0x0/0x12 ---[ end trace 7f764aa038f04a69 ]--- wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0e:8e:04:53:fa ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: authenticate with AP 00:0e:8e:04:53:fa wlan0: authenticate with AP 00:0e:8e:04:53:fa wlan0: authentication with AP 00:0e:8e:04:53:fa timed out Additional info: * kernel26 2.6.25-1 * compat-wireless 2008_04_20-1 Steps to reproduce: I have to identically configured networks (only ESSID different) using wpa on a dual-band router. There are no problems connecting to the 11g network, but netcfg2 will fail to connect to the 11a network, stating that the wireless association failed and in dmesg I'll see the timed out part of above message or a connection attempt to another, unrelated AP. I tried to use WEP and manual connection, but I got above error message. |
This task depends upon

This should be fixed by now (I can successfully connect to 11a networks), can you confirm that?

Status?

Sorry for not answering earlier - yes, it has been fixed and the bug can be closed.