Intel iwlagn driver hangs from time to time

[jsweiss]

Binary package hint: ubuntu-docs

Hello,
I have a problem with the iwlagn driver. everything works perfect, except it somehow "hangs" from time to time. There is no exact time frame for hanging, sometimes it works perfectly for days, other times dies 2 times in 10 minutes. The wireless network disconnects, and it does not show any available network (the AP is not the problem, as other devices do work. also there is not a hardware issue,because on windows i did not have this problem).
When the wifi adapter hangs, i get this in the dmesg:

[ 7952.460205] wlan0: no probe response from AP XX:XX:XX:XX:XX - disassociating
[ 7953.060210] iwlagn 0000:05:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 7953.060223] iwlagn 0000:05:00.0: Error setting new RXON (-110)
[ 7953.560245] iwlagn 0000:05:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
[ 7954.060057] iwlagn 0000:05:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 7954.060069] iwlagn 0000:05:00.0: Error setting new RXON (-110)
[ 7954.560235] iwlagn 0000:05:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 7954.560247] iwlagn 0000:05:00.0: Error setting new RXON (-110)
[ 7959.060105] iwlagn 0000:05:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 7959.060116] iwlagn 0000:05:00.0: Error setting new RXON (-110)
[ 7959.560264] iwlagn 0000:05:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
[ 7960.060248] iwlagn 0000:05:00.0: Error sending REPLY_RXON: time out after 500ms.
[ 7960.060260] iwlagn 0000:05:00.0: Error setting new RXON (-110)

The only solution for the wifi network to recover is to remove and then re-insert the module. If i use the wireless on/off switch on the laptop, it still does not work.
If i do:
rmmod iwlagn iwlcore
modprobe iwlagn
modprobe iwlcore
the wifi card finds the access point again.

The system is as follows:
Linux user-laptop 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 2010 x86_64 GNU/Linux
Ubuntu 9.10

System is a Sony Vaio VGN-SR59VG (german version), and the wireless adapter is
  *-network
       description: Wireless interface
       product: Wireless WiFi Link 5100
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:05:00.0
       logical name: wmaster0
       version: 00
       serial: xx:xx:xx:xx:xx:xx
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list logical ethernet physical wireless
       configuration: broadcast=yes driver=iwlagn ip=192.168.1.101 latency=0 multicast=yes wireless=IEEE 802.11abgn
       resources: irq:31 memory:d1500000-d1501fff

This is getting annoying some times, especially because sometimes it works for ways, other times it dies 2 times in 10 minutes .

Any help would be appreciated.

Julien

[Mitch Towner (kermiac)]

not an ubuntu-docs issue

[Jeremy Foshee (jeremyfoshee)]

jsweiss,
     Please run 'apport-collect -p linux 518196' so that the collected logs for this issue can be attached to this bug.

Thanks!

-JFo

[jsweiss (juliensweiss)]

Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: user 4085 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd5200000 irq 22'
   Mixer name : 'Realtek ALC262'
   Components : 'HDA:10ec0262,104d2d00,00100302 HDA:14f12c06,104d1700,00100000'
   Controls : 18
   Simple ctrls : 11
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd0030000 irq 17'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,104d2d00,00100100'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [off]
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: Sony Corporation VGN-SR59VG_H
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-19-generic root=UUID=2cebe356-2708-47eb-9821-27eba1d664e8 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-generic N/A
 linux-firmware 1.25
Uname: Linux 2.6.31-19-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data
WifiSyslog:

dmi.bios.date: 08/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R4090Y1
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR4090Y1:bd08/05/2009:svnSonyCorporation:pnVGN-SR59VG_H:pvrC60389VN:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-SR59VG_H
dmi.product.version: C60389VN
dmi.sys.vendor: Sony Corporation

[jsweiss (juliensweiss)]

Done.

Thanks
Jeremy Foshee wrote:
> jsweiss,
> Please run 'apport-collect -p linux 518196' so that the collected logs for this issue can be attached to this bug.
>
> Thanks!
>
> -JFo
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

[dave945 (dave-dtabor)]

I think I may have the same or a similar bug. Ubuntu Karmic was working very well until yesterday and I think a kernel patch may have done me in. Here's the info I have:

[dave945 (dave-dtabor)]

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tabord 1998 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc220000 irq 17'
   Mixer name : 'Conexant CX20561 (Hermosa)'
   Components : 'HDA:14f15051,17aa2100,00100000 HDA:14f12c06,17aa2122,00100000'
   Controls : 14
   Simple ctrls : 7
CheckboxSubmission: 78f0d12e26671bc09b495230bb082922
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=0a6b324d-4259-494d-945f-5fd16b10475c
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: LENOVO 20823GU
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic root=UUID=4eca727b-6dec-49c4-931c-7cd930d4675e ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-19-generic N/A
 linux-firmware 1.25
Uname: Linux 2.6.31-19-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/22/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7VET66WW (2.16 )
dmi.board.name: 20823GU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7VET66WW(2.16):bd04/22/2009:svnLENOVO:pn20823GU:pvrThinkPadT500:rvnLENOVO:rn20823GU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20823GU
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO

[dave945 (dave-dtabor)]

this is a lenovo T500 laptop that dual-boots Ubuntu 9.10 Karmic and.. and ... W... W... Windows Visssss ta Vista, which DOES connect to my network. The Wireless access point is a apple airport base station extreme 802.11b/g/n of recent vintage.
Dave

[dave945 (dave-dtabor)]

this is a lenovo T500 laptop that dual-boots Ubuntu 9.10 Karmic and.. and ... W... W... Windows Visssss ta Vista, which DOES connect to my network. The Wireless access point is a apple airport base station extreme 802.11b/g/n of recent vintage.
Dave

[Russell Robinson (russellr-openconcepts)]

Similar problem on Dell Latitude E6500.

/var/log/messages message is: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Did not happen in Jaunty - only since upgrading to Karmic, and then only recently (last week or so). Recent kernel update?

[jsweiss (juliensweiss)]

Forgot to mention the AP is a HUAWAI D100 router. But i guess it is not
too important,
as i have a Nokia phone , another laptop and this same laptop on Windows
with
no issues. Also i have not tried other Linux distributions, as the
laptop is new.

[Jeremy Foshee (jeremyfoshee)]

set to triaged with a low initial importance. This has been added to my list for review.

-JFo

[Chase Douglas (chasedouglas)]

Could anyone affected please test two things:

1. linux-backports-modules-wireless-karmic-generic (newer versions of the wireless drivers)
    a. Go to System -> Administration -> Software Sources
    b. Ensure the box for "Community-maintained Open Source software (universe)" is checked
    c. Install the linux-backports-modules-wireless-karmic-generic (either through apt-get install or through Synaptic Package Manager)
    d. Restart and test the new drivers
2. Lucid
    a. Download one of the daily lucid isos from http://cdimage.ubuntu.com/daily-live/current/ and test this in Lucid (you don't need to install it, just boot it up to test)

If either of these seems to have the issue fixed we can then begin to focus on finding a particular patch to fix the issue.

Thanks

[dave945 (dave-dtabor)]

This did not get it working for me.

Strangely, if I boot with a wired connection, my wireless works, even if
I disconnect eth0:

Feb 27 17:02:19 tabord-laptop kernel: [ 14.108311]
ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 27 17:02:19 tabord-laptop kernel: [ 14.109658] iwlagn
0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
Feb 27 17:02:19 tabord-laptop firmware.sh[1125]: Cannot find firmware
file 'lbm-iwlwifi-5000-2.ucode'
Feb 27 17:02:19 tabord-laptop kernel: [ 14.145588] iwlagn
0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
Feb 27 17:02:19 tabord-laptop kernel: [ 14.249646] iwlagn
0000:03:00.0: loaded firmware version 8.24.2.12
Feb 27 17:02:19 tabord-laptop kernel: [ 14.397123] Registered led
device: iwl-phy0::radio
Feb 27 17:02:19 tabord-laptop kernel: [ 14.397141] Registered led
device: iwl-phy0::assoc
Feb 27 17:02:19 tabord-laptop kernel: [ 14.397156] Registered led
device: iwl-phy0::RX
Feb 27 17:02:19 tabord-laptop kernel: [ 14.397169] Registered led
device: iwl-phy0::TX
Feb 27 17:02:19 tabord-laptop kernel: [ 14.416539]
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 27 17:02:19 tabord-laptop kernel: [ 14.499530] mtrr: no more MTRRs
available
Feb 27 17:02:19 tabord-laptop kernel: [ 14.499583] mtrr: no more MTRRs
available
Feb 27 17:02:20 tabord-laptop kernel: [ 15.470226] Bluetooth: BNEP
(Ethernet Emulation) ver 1.3
Feb 27 17:02:20 tabord-laptop kernel: [ 15.470229] Bluetooth: BNEP
filters: protocol multicast
Feb 27 17:02:20 tabord-laptop kernel: [ 15.475449] Bridge firewalling
registered
Feb 27 17:02:20 tabord-laptop kernel: [ 15.534876] ppdev: user-space
parallel port driver
Feb 27 17:02:22 tabord-laptop kernel: [ 17.317221] e1000e: eth0 NIC
Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Feb 27 17:02:22 tabord-laptop kernel: [ 17.317395]
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Feb 27 17:02:26 tabord-laptop kernel: [ 21.242404] IBM TrackPoint
firmware: 0x0e, buttons: 3/3
Feb 27 17:02:26 tabord-laptop kernel: [ 21.482140] input: TPPS/2 IBM
TrackPoint as /devices/platform/i8042/serio1/serio2/input/input15
Feb 27 17:02:43 tabord-laptop kernel: [ 38.318873]
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 27 17:02:43 tabord-laptop kernel: [ 38.318905] cfg80211: Calling
CRDA for country: US
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320698] cfg80211:
Regulatory domain: US
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320700] (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320703] (5170000 KHz -
5250000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320706] (5735000 KHz -
5835000 KHz @ 40000 KHz), (10000 mBi, 10000 mBm)
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320709] cfg80211:
Regulatory domain: US
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320711] (start_freq -
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320713] (2402000 KHz -
2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
Feb 27 17:02:43 tabord-laptop kernel: [ 38.320716] (517...

[dave945 (dave-dtabor)]

After unplugging eth0, wlan0 runs for about a minute then quits. Here is the sequence of events:

Feb 27 17:31:43 tabord-laptop kernel: [ 47.352057] wlan0: no IPv6 routers present
Feb 27 17:31:50 tabord-laptop kernel: [ 54.364177] e1000e: eth0 NIC Link is Down
Feb 27 17:31:50 tabord-laptop NetworkManager: <info> (eth0): carrier now OFF (device state 8, deferring action for 4 seconds)
Feb 27 17:31:55 tabord-laptop NetworkManager: <info> (eth0): device state change: 8 -> 2 (reason 40)
Feb 27 17:31:55 tabord-laptop NetworkManager: <info> (eth0): deactivating device (reason: 40).
Feb 27 17:31:55 tabord-laptop NetworkManager: <info> (eth0): canceled DHCP transaction, dhcp client pid 1794
Feb 27 17:31:55 tabord-laptop NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess#012
Feb 27 17:31:55 tabord-laptop avahi-daemon[968]: Withdrawing address record for 10.0.1.17 on eth0.
Feb 27 17:31:55 tabord-laptop avahi-daemon[968]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.17.
Feb 27 17:31:55 tabord-laptop avahi-daemon[968]: Interface eth0.IPv4 no longer relevant for mDNS.
Feb 27 17:31:55 tabord-laptop NetworkManager: <info> Policy set 'Auto Tabor (5 GHz)' (wlan0) as default for routing and DNS.
Feb 27 17:32:04 tabord-laptop wpa_supplicant[1356]: CTRL-EVENT-SCAN-RESULTS
Feb 27 17:32:28 tabord-laptop anacron[2450]: Anacron 2.3 started on 2010-02-27
Feb 27 17:32:28 tabord-laptop anacron[2450]: Normal exit (0 jobs run)
Feb 27 17:32:28 tabord-laptop kernel: [ 91.927340] CPU0 attaching NULL sched-domain.
Feb 27 17:32:28 tabord-laptop kernel: [ 91.927344] CPU1 attaching NULL sched-domain.
Feb 27 17:32:28 tabord-laptop kernel: [ 91.934050] thinkpad_acpi: EC reports that Thermal Table has changed
Feb 27 17:32:28 tabord-laptop kernel: [ 91.940567] CPU0 attaching sched-domain:
Feb 27 17:32:28 tabord-laptop kernel: [ 91.940570] domain 0: span 0-1 level MC
Feb 27 17:32:28 tabord-laptop kernel: [ 91.940572] groups: 0 1
Feb 27 17:32:28 tabord-laptop kernel: [ 91.940576] CPU1 attaching sched-domain:
Feb 27 17:32:28 tabord-laptop kernel: [ 91.940577] domain 0: span 0-1 level MC
Feb 27 17:32:28 tabord-laptop kernel: [ 91.940579] groups: 1 0
Feb 27 17:32:44 tabord-laptop wpa_supplicant[1356]: CTRL-EVENT-SCAN-RESULTS
Feb 27 17:32:44 tabord-laptop wpa_supplicant[1356]: Trying to associate with 00:1f:f3:f8:a1:db (SSID='Tabor (5 GHz)' freq=5745 MHz)
Feb 27 17:32:44 tabord-laptop NetworkManager: <info> (wlan0): supplicant connection state: completed -> associating
Feb 27 17:32:44 tabord-laptop wpa_supplicant[1356]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Feb 27 17:32:44 tabord-laptop NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Feb 27 17:32:44 tabord-laptop kernel: [ 107.648220] wlan0: deauthenticating from f8:1e:df:fa:e6:1c by local choice (reason=3)
Feb 27 17:32:44 tabord-laptop kernel: [ 107.651297] wlan0: direct probe to AP 00:1f:f3:f8:a1:db (try 1)
Feb 27 17:32:44 tabord-laptop kernel: [ 107.652818] wlan0: direct probe responded
Feb 27 17:32:44 tabord-laptop kernel: [ 107.652825] wlan0: authenticate w...

[dave945 (dave-dtabor)]

This time, I booted to linux and it worked (don't know for how long it
will last):

Feb 27 22:45:43 tabord-laptop kernel: [ 12.470749] iwlagn: Intel(R)
Wireless WiFi Link AGN driver for Linux, 1.3.27ks
Feb 27 22:45:43 tabord-laptop kernel: [ 12.470752] iwlagn:
Copyright(c) 2003-2009 Intel Corporation
Feb 27 22:45:43 tabord-laptop kernel: [ 12.470830] iwlagn
0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Feb 27 22:45:43 tabord-laptop kernel: [ 12.470906] iwlagn
0000:03:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54
Feb 27 22:45:43 tabord-laptop kernel: [ 12.513637] iwlagn
0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
Feb 27 22:45:43 tabord-laptop kernel: [ 12.547322] input: HDA Intel
Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Feb 27 22:45:43 tabord-laptop kernel: [ 12.547382] input: HDA Intel
Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
Feb 27 22:45:43 tabord-laptop kernel: [ 12.547429] input: HDA Intel
Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
Feb 27 22:45:43 tabord-laptop kernel: [ 12.547473] input: HDA Intel
Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input13
Feb 27 22:45:43 tabord-laptop kernel: [ 12.720221] pcmcia_socket
pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.
Feb 27 22:45:43 tabord-laptop kernel: [ 12.721953] pcmcia_socket
pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
Feb 27 22:45:43 tabord-laptop kernel: [ 12.722685] pcmcia_socket
pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
Feb 27 22:45:43 tabord-laptop kernel: [ 12.723262] pcmcia_socket
pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
Feb 27 22:45:43 tabord-laptop kernel: [ 12.723993] pcmcia_socket
pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
Feb 27 22:45:43 tabord-laptop kernel: [ 12.816328]
ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 27 22:45:43 tabord-laptop kernel: [ 12.817604] iwlagn
0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
Feb 27 22:45:43 tabord-laptop firmware.sh[1074]: Cannot find firmware
file 'lbm-iwlwifi-5000-2.ucode'
Feb 27 22:45:43 tabord-laptop kernel: [ 12.860701] iwlagn
0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
Feb 27 22:45:43 tabord-laptop kernel: [ 12.934285] Synaptics Touchpad,
model: 1, fw: 7.0, id: 0x1c0b1, caps: 0xd04791/0xb00000
Feb 27 22:45:43 tabord-laptop kernel: [ 12.934290] serio: Synaptics
pass-through port at isa0060/serio1/input0
Feb 27 22:45:43 tabord-laptop kernel: [ 12.949384] iwlagn
0000:03:00.0: loaded firmware version 8.24.2.12
Feb 27 22:45:43 tabord-laptop kernel: [ 13.000010] input: SynPS/2
Synaptics TouchPad as /devices/platform/i8042/serio1/input/input14
Feb 27 22:45:43 tabord-laptop kernel: [ 13.058703] usb 4-2: new full
speed USB device using uhci_hcd and address 3
Feb 27 22:45:43 tabord-laptop kernel: [ 13.098558] Registered led
device: iwl-phy0::radio
Feb 27 22:45:43 tabord-laptop kernel: [ 13.098574] Registered led
device: iwl-phy0::assoc
Feb 27 22:45:43 tabord-laptop kernel: [ 13.098588] Registered led
device: iwl-phy0::RX
Feb 27 22:45:43 tabord-laptop ke...

[Chase Douglas (chasedouglas)]

@dave945:

There's something interesting in your logs. Both boot dmesg logs when the wireless wasn't working properly had loaded the iwlwifi-5000-2.ucode properly. When you installed the linux-backports-modules package it started to look for lbm-iwlwifi-5000-2.ucode firmware file instead (note the prefixed "lbm-"). It then fell back to lbm-iwlwifi-5000-1.ucode, which it found. I am wondering if this is a firmware issue.

By default you should have both iwlwifi-5000-1.ucode and iwlwifi-5000-2.ucode in /lib/firmware/. Assuming you do, try the following test:

1. move /lib/firmware/iwlwifi-5000-2.ucode to /lib/firmware/iwlwifi-5000-2.ucode.backup
2. restart

If it gets better, do the opposite. Move the ucode file back to where it was and then restart to confirm that the wireless behaves poorly again. Please post your results in this bug report.

Thanks

[dave945 (dave-dtabor)]

Chase,
Thanks for the tip. I did as you suggested. I renamed the file and restarted the laptop and networking worked. Then I named it back and rebooted: no wlan0. Feeling we were on to something, I renamed the file back to .backup and rebooted thinking to write in and report a positive diagnosis. Unfortunately, wlan0 is still not functioning, even though it appears to be OK as reported by syslog. This makes me wonder if (a) it could be hardware, or (b) if the driver could have messed up the hardware. As an additional data point, Windows Vista on this same laptop which has always connected before, stopped working today.
Thanks,
Dave

PS: let me know if you would like me to upload any logs.

Oh, also, you mentioned lbm-prefixed drivers in your previous note. I don't seem to have any. here's what I have:

tabord@tabord-laptop:/lib/firmware$ ls -lart *iwlwifi*
-rw-r--r-- 1 root root 459992 2009-11-30 06:29 iwlwifi-6000-4.ucode
-rw-r--r-- 1 root root 337400 2009-11-30 06:29 iwlwifi-5150-2.ucode
-rw-r--r-- 1 root root 353240 2009-11-30 06:29 iwlwifi-5000-2.ucode.backup
-rw-r--r-- 1 root root 345008 2009-11-30 06:29 iwlwifi-5000-1.ucode
-rwxr-xr-x 1 root root 187972 2009-11-30 06:29 iwlwifi-4965-2.ucode
-rw-r--r-- 1 root root 187608 2009-11-30 06:29 iwlwifi-4965-1.ucode
-rwxr-xr-x 1 root root 150100 2009-11-30 06:29 iwlwifi-3945-2.ucode
-rw-r--r-- 1 root root 149652 2009-11-30 06:29 iwlwifi-3945-1.ucode
-rw-r--r-- 1 root root 335056 2009-11-30 06:29 iwlwifi-1000-3.ucode
tabord@tabord-laptop:/lib/firmware$ ls -lart lbm*
ls: cannot access lbm*: No such file or directory

[Chase Douglas (chasedouglas)]

@dave945:

Please attach a dmesg log now. I'd like to see what's in the log now that wifi isn't working.

Also, try running 'rfkill list'. Maybe something (perhaps windows?) set a block.

[dave945 (dave-dtabor)]

Chase,
tabord@tabord-laptop:~$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

Also, Vista wifi is working today.
I will attach /var/log/dmesg

Thanks,
David

[Chase Douglas (chasedouglas)]

@dave945:

Something odd is going on here. In the first dmesg where things began to work, the -2 firmware wasn't found and the following was output:

Feb 27 22:45:43 tabord-laptop kernel: [ 12.817604] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
Feb 27 22:45:43 tabord-laptop firmware.sh[1074]: Cannot find firmware file 'lbm-iwlwifi-5000-2.ucode'
Feb 27 22:45:43 tabord-laptop kernel: [ 12.860701] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
Feb 27 22:45:43 tabord-laptop kernel: [ 12.949384] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12

However, in your last dmesg (where things are broken), we see:

[ 12.917423] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
[ 12.938337] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2
[ 12.938341] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
[ 13.049180] iwlagn 0000:03:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.
[ 13.049185] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12

Note that in this log we see it complain about how the -1 ucode is deprecated. If the same driver were used in both tests, we should see the message output in both logs. Do you know if the driver itself has changed between these tests? Did you update your kernel or linux-backports-modules?

[dave945 (dave-dtabor)]

Chase,
I haven't updated anything, but I see your point. Should I install
linux-backports again?
Thanks,
Dave

On 3/3/2010 9:41 AM, Chase Douglas wrote:
> @dave945:
>
> Something odd is going on here. In the first dmesg where things began to
> work, the -2 firmware wasn't found and the following was output:
>
> Feb 27 22:45:43 tabord-laptop kernel: [ 12.817604] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
> Feb 27 22:45:43 tabord-laptop firmware.sh[1074]: Cannot find firmware file 'lbm-iwlwifi-5000-2.ucode'
> Feb 27 22:45:43 tabord-laptop kernel: [ 12.860701] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
> Feb 27 22:45:43 tabord-laptop kernel: [ 12.949384] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
>
> However, in your last dmesg (where things are broken), we see:
>
> [ 12.917423] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-2.ucode
> [ 12.938337] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware file req failed: -2
> [ 12.938341] iwlagn 0000:03:00.0: firmware: requesting lbm-iwlwifi-5000-1.ucode
> [ 13.049180] iwlagn 0000:03:00.0: Loaded firmware lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.
> [ 13.049185] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12
>
> Note that in this log we see it complain about how the -1 ucode is
> deprecated. If the same driver were used in both tests, we should see
> the message output in both logs. Do you know if the driver itself has
> changed between these tests? Did you update your kernel or linux-
> backports-modules?
>
>

[Chase Douglas (chasedouglas)]

@dave945:

I'm not real sure what the best way forward is now. You can try various combinations of firmware and drivers to see if any work, and if you find anything be sure to let us know. The latest compat-wireless tree may include some fixes that affect you. Some newer drivers can be found in the linux-backports-modules package available in the karmic pre-proposed ppa: https://launchpad.net/~kernel-ppa/+archive/pre-proposed/.

However, your issues are a little beyond my experience. I suggest going through the documentation at http://linuxwireless.org/en/users/Documentation/Reporting_bugs to check some more variables and then report a bug to the linux-wireless mailing list. If you do report a bug to the mailing list, please include a link to your message in a comment here.

[jsweiss (juliensweiss)]

Hello,

Tried all the firmware images, with same result.
Also tried ndiswrapper, but it looks like this driver is not supported.

However, i tried a different thing ... i changed on the wifi router
(Huawei D100)
the WiFI security settings from Encryption mode : WPA-PSK, WPA
Encryption: TKIP
to WPA2-PSK, Encryption AES. I don't know if this is the reason, but
until now,
everything looks good. I also changed the firmware to the latest version
(8.24.2.12).
Ill post back after i test it for more time, as the problem usually
appears totally
random (sometimes once or twice in 2, 3 days, other times twice in 10
minutes).
The Huawei router is also Linux based, for more details you can check the
Huawei website.
Note: I have also been for 3 days in a hotel which had a wifi hotspot
that was
totally open, and it worked without any problems ...

J

Chase Douglas wrote:
> @dave945:
>
> I'm not real sure what the best way forward is now. You can try various
> combinations of firmware and drivers to see if any work, and if you find
> anything be sure to let us know. The latest compat-wireless tree may
> include some fixes that affect you. Some newer drivers can be found in
> the linux-backports-modules package available in the karmic pre-proposed
> ppa: https://launchpad.net/~kernel-ppa/+archive/pre-proposed/.
>
> However, your issues are a little beyond my experience. I suggest going
> through the documentation at
> http://linuxwireless.org/en/users/Documentation/Reporting_bugs to check
> some more variables and then report a bug to the linux-wireless mailing
> list. If you do report a bug to the mailing list, please include a link
> to your message in a comment here.
>
>

[Chase Douglas (chasedouglas)]

@jsweiss:

Thanks for that input. There are often issues with various combinations of wireless cards and routers. That's something we should always keep in mind when we are working on wireless issues. I'm sure others have brands they like, but I try to use Apple routers personally because they seem to be the most compatible and stable brand of routers I've ever used.

[Chase Douglas (chasedouglas)]

@dave945:

Can you try what jsweiss has tried? First, trying to use WPA2-PSK using AES, and then trying other routers if possible?

[jsweiss (juliensweiss)]

@Chase

True, i really did not think about the router issue till now. To be honest,
in Windows 7 i did not have the chance to try it too much, because i
just deleted
it and installed Linux ... I cannot use an Apple router, as i have a
3G/WCDMA connection
and so far the Huawei router makes sense. I will switch to an Option
router soon, which
has same features and as i understand, it is a lot better (and quite
more expensive).

If this change does not work, the next on the list is a Netgear 3G/UMTS
router which
i have handy (got it in the store and can take it back in 2 weeks if its
not good). But i hope
that for now i solved the issue with the WPA2-PSK - AES combination.

I don't know if my issue is similar to Dave's issue, as for him there
were instances when
the wifi did not work at all ... For me it worked all the time, and died
at random periods of
time, as explained.

I will keep on testing, and keep everyone updated, this might not be a
module/firmware issue
after all ...

J

Chase Douglas wrote:
> @jsweiss:
>
> Thanks for that input. There are often issues with various combinations
> of wireless cards and routers. That's something we should always keep in
> mind when we are working on wireless issues. I'm sure others have brands
> they like, but I try to use Apple routers personally because they seem
> to be the most compatible and stable brand of routers I've ever used.
>
>

[jsweiss (juliensweiss)]

Chase:

Also, when i had a DSL or Cable connection, the Linksys routers looked
very good for me ... I do not
remember the exact model, but it was a router with Gigabit ethernet,
suitable for gaming, and was
the only one that did not crash when used at full speed (6Mbit DSL) or
when used with torrents ...

J

Chase Douglas wrote:
> @jsweiss:
>
> Thanks for that input. There are often issues with various combinations
> of wireless cards and routers. That's something we should always keep in
> mind when we are working on wireless issues. I'm sure others have brands
> they like, but I try to use Apple routers personally because they seem
> to be the most compatible and stable brand of routers I've ever used.
>
>

[dave945 (dave-dtabor)]

@Chase,
I switched my Apple Airport Base station extreme from WPA/WPA2 Personal
to WPA2 Personal and booted from Windows Vista into Ubuntu Karmic.
After unplugging the eth0 cable, the wlan0 connection is working. If
memory serves, this would work for a little while and then go bad. So
far however, this seems to be working! So to summarize, if we set the
router to the highest level of security, the driver can connect. It's
only in WPA "fallback mode" that the problem manifests.

13.852635] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux,
1.3.27ks
[ 13.852638] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[ 13.852702] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
[ 13.852710] iwlagn 0000:03:00.0: setting latency timer to 64
[ 13.852733] iwlagn 0000:03:00.0: Detected Intel Wireless WiFi Link
5100AGN REV=0x54
[ 13.891900] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24
802.11a channels
[ 13.891959] alloc irq_desc for 33 on node -1
[ 13.891961] alloc kstat_irqs on node -1
[ 13.891979] iwlagn 0000:03:00.0: irq 33 for MSI/MSI-X
[ 13.898444] phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 13.902784] pcmcia_socket pcmcia_socket0: cs: IO port probe
0x100-0x3af: clean.
[ 13.907234] pcmcia_socket pcmcia_socket0: cs: IO port probe
0x3e0-0x4ff: excluding 0x4d0-0x4d7
[ 13.907930] pcmcia_socket pcmcia_socket0: cs: IO port probe
0x820-0x8ff: clean.
[ 13.908582] pcmcia_socket pcmcia_socket0: cs: IO port probe
0xc00-0xcf7: clean.
[ 13.909277] pcmcia_socket pcmcia_socket0: cs: IO port probe
0xa00-0xaff: clean.
[ 14.011004] Synaptics Touchpad, model: 1, fw: 7.0, id: 0x1c0b1, caps:
0xd04791/0xb00000
[ 14.011014] serio: Synaptics pass-through port at isa0060/serio1/input0
[ 14.019469] EXT4-fs (sda5): internal journal on sda5:8
[ 14.052474] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio1/input/input14
[ 14.228774] e1000e 0000:00:19.0: irq 31 for MSI/MSI-X
[ 14.287750] e1000e 0000:00:19.0: irq 31 for MSI/MSI-X
[ 14.287979] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 14.289348] iwlagn 0000:03:00.0: firmware: requesting
lbm-iwlwifi-5000-2.ucode
[ 14.304014] iwlagn 0000:03:00.0: lbm-iwlwifi-5000-2.ucode firmware
file req failed: -2
[ 14.304018] iwlagn 0000:03:00.0: firmware: requesting
lbm-iwlwifi-5000-1.ucode
[ 14.329993] iwlagn 0000:03:00.0: Loaded firmware
lbm-iwlwifi-5000-1.ucode, which is deprecated. Please use API v2 instead.
[ 14.329997] iwlagn 0000:03:00.0: loaded firmware version 8.24.2.12

I'm going to re-instate the lbm-iwlwifi-5000-2.ucode firmware driver and
see what happens...

Dave

Chase Douglas wrote:
> @dave945:
>
> Can you try what jsweiss has tried? First, trying to use WPA2-PSK using
> AES, and then trying other routers if possible?
>
>

[jsweiss (juliensweiss)]

Hello,
Now testing with an Belkin wifi router, everything seems ok. Security is
open.

[jsweiss (juliensweiss)]

Hello,
After extensive testing with various WiFi routers, i consider
this issue resolved. I don't know about the others, but i am
sure that my problem was a wrong combination of router
and security settings. I also don't know if this happens only
on Linux or also on Windows, as i did not get to test the
windows behavior for long, and the problem showed up
at random times. Thanks everyone of the advice.

On 03/05/2010 01:19 PM, Chase Douglas wrote:
> @dave945:
>
> Can you try what jsweiss has tried? First, trying to use WPA2-PSK using
> AES, and then trying other routers if possible?
>
>

[Scott Moser (smoser)]

@Chase,
  I had previously seen this from time to time on Karmic, and still on lucid. It bit me twice today while I was away from the machine, had to have someone reload modules for me.
  I use WEP auth, dd-wrt router (linksys wlan-54G).
If you need anything, feel free to ping me and I can test.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]