Intel Wireless driver dies randomly

[Ryan Morrison]

While using an Intel WiFi Link 5300 AGN wireless card, the following happens:

* Card makes a successful connection to wireless access point
* Card functions normally for a period of time (this can be 15 minutes - 3 hours or longer)
* Network access is lost, network manager continues to show association
* Network speed is reported as 1mbps or "unknown"
* Reassociation does not solve the issue. Reassociation may also take upwards of one minute to complete from this point on.
* Hardware switch toggle does not solve the issue.
* Reloading the driver via 'modprobe -r iwlagn && modprobe iwlagn' DOES solve the problem.
* There are no messages logged in dmesg during this time indicating the problem.

This bug does appear in 9.10 Karmic and 10.04 B2 Lucid. Attached are the recommended outputs for review.

[Tom Pringle (thomas-b-pringle)]

This bug also effects me. This may be a regression because I never observed the problem before this weekend and have been running lucid on this laptop for several months.

I have confirmed that
    modprobe -r iwlagn && modprobe iwlagn
resolves the problem

[Tom Pringle (thomas-b-pringle)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8700000 irq 22'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,161f207a,00100004'
   Controls : 19
   Simple ctrls : 11
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf8110000 irq 18'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 10.04
Frequency: I don't know.
HibernationDevice: RESUME=UUID=6234f1b6-b20f-4784-8771-a107da3127be
InstallationMedia:

MachineType: alienware Alienware M17
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=706e15a7-ceee-4a18-9c39-31870fa6ed8c ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Regression: No
RelatedPackageVersions: linux-firmware 1.34
Reproducible: No
Tags: lucid networking needs-upstream-testing
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/04/2009
dmi.bios.vendor: Intel
dmi.bios.version: W841.B14
dmi.board.name: alienware
dmi.board.vendor: alienware
dmi.board.version: alienware
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: alienware
dmi.chassis.version: alienware
dmi.modalias: dmi:bvnIntel:bvrW841.B14:bd03/04/2009:svnalienware:pnAlienwareM17:pvrW841.B14:rvnalienware:rnalienware:rvralienware:cvnalienware:ct1:cvralienware:
dmi.product.name: Alienware M17
dmi.product.version: W841.B14
dmi.sys.vendor: alienware

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

apport information

[Tom Pringle (thomas-b-pringle)]

update: the problem on my machine occurs whenever I bring the machine out of Sleep (suspend to ram). Based on that it must be a very recent regression because I typically put the machine to sleep a multiple times per day and I would have noticed this sooner if it wasn't a regression. (I've been running lucid on this machine for over a month.)

[Tom Pringle (thomas-b-pringle)]

I have not seen this problem in 5 days? Might be fixed?

[Ryan Morrison (ryan-morrison04)]

I haven't seen it for a few days either, Tom. However, I haven't put the computer to sleep as of yet, I may try that over the weekend and see if I can cause a reproduction of the problem. I do know with the Lucid release there were a lot of new packages pushed, one of which may have solved this.

[georg wiltschek (georg-wiltschek)]

Got the same problem on a Lenovo T500 with an Intel 5300 wifi-card. The connection dropped at least half a dozen times over the last hour and came back after a while. Reloading the iwlagn module makes the reconnection faster, but doesn't prevent further disconnects. No problems on 9.04 and Windows, only on 64-bit Lucid, which is not really usable due to this error :(

Here are some lines from dmesg:

[14883.540273] wlan0: deauthenticating from 00:18:39:d4:15:f5 by local choice (reason=3)
[14904.970696] wlan0: deauthenticating from 68:7f:74:27:37:81 by local choice (reason=3)
[14904.971187] wlan0: direct probe to AP 00:18:39:d4:15:f5 (try 1)
[14904.975196] wlan0: direct probe responded
[14904.975204] wlan0: authenticate with AP 00:18:39:d4:15:f5 (try 1)
[14904.976989] wlan0: authenticated
[14904.977026] wlan0: associate with AP 00:18:39:d4:15:f5 (try 1)
[14904.979245] wlan0: RX AssocResp from 00:18:39:d4:15:f5 (capab=0x411 status=0 aid=3)
[14904.979252] wlan0: associated
[15023.560415] wlan0: deauthenticating from 00:18:39:d4:15:f5 by local choice (reason=3)
[15045.042577] wlan0: deauthenticating from 68:7f:74:27:37:81 by local choice (reason=3)
[15045.042668] wlan0: direct probe to AP 00:18:39:d4:15:f5 (try 1)
[15045.047942] wlan0: direct probe responded
[15045.047951] wlan0: authenticate with AP 00:18:39:d4:15:f5 (try 1)
[15045.049733] wlan0: authenticated
[15045.049772] wlan0: associate with AP 00:18:39:d4:15:f5 (try 1)
[15045.053008] wlan0: RX AssocResp from 00:18:39:d4:15:f5 (capab=0x411 status=0 aid=3)
[15045.053015] wlan0: associated

[jmrk (joergen-kornfeld)]

Used lucid 64 with intel 5300 for a while before this bug appeared (so maybe really a regression) and I never had a problem on 9.10. It is very random for me, but I'm also using sleep mode several times a day. Thanks for this hint, maybe I can observe some regularity. One more thing: wifi hardware switch at notebook does help in my case (for a few minutes at least ;-) ).

[Andreas (andreas-kotowicz)]

the problem went away for me on lucid, after installing the 2.6.35 kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-maverick/). can someone confirm this?

[jmrk (joergen-kornfeld)]

The bug was fixed for me with 10.10.

[penalvch (penalvch)]

Ryan Morrison, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]