Public bug reported:

The iwlagn module disconnects from time to time (1minute - 3hours it
depends). There is no stack trace in the logs like in bug 346773 but the
reloading the module restores connection. The disconnection never (?)
happens when the card is busy. I have transmited multi-GB data sets and
it was working fine. But just let it get idle and it drops the
connection quickly.  Running constant local ping (eg. to your router)
helps usually but only with 1s ping intervals. If I ping with 10s or
more  intervals the connection is dropped anyway. I have upgraded to the
"proposed" repo kernel and it helped a little (with the standard kernel
I was getting the stack trace in the logs and usually it was necessary
to reboot to connect again). This is on Thinkpad X300. The connection is
WPA2 encrypted. The AP is very close (Linksys WPA200).
I consider this problem to be quite serious. I am kind of geek and I can
manage but for normal user this would be a real show-stopper.

I suspect that this is connected to other iwlagn bugs and ultimately to
the firmware bug. Here is a typical dmesg of the problem (first module
reload then error and disconnection):

[93143.276247] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 
1.3.27ks
[93143.276252] iwlagn: Copyright(c) 2003-2009 Intel Corporation
[93143.276371] iwlagn 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[93143.276418] iwlagn 0000:03:00.0: setting latency timer to 64
[93143.276706] iwlagn 0000:03:00.0: Detected Intel Wireless WiFi Link 4965AGN 
REV=0x4
[93143.319848] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 19 802.11a 
channels
[93143.319963] iwlagn 0000:03:00.0: irq 2299 for MSI/MSI-X
[93143.322482] phy0: Selected rate control algorithm 'iwl-agn-rs'
[93147.745638] iwlagn 0000:03:00.0: firmware: requesting 
lbm-iwlwifi-4965-2.ucode
[93147.756801] iwlagn 0000:03:00.0: loaded firmware version 228.57.2.23
[93147.959421] Registered led device: iwl-phy0::radio
[93147.959472] Registered led device: iwl-phy0::assoc
[93147.959512] Registered led device: iwl-phy0::RX
[93147.959552] Registered led device: iwl-phy0::TX
[93148.006653] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[93160.368562] wlan0: authenticate with AP ee6256b8
[93160.370442] wlan0: authenticated
[93160.370448] wlan0: associate with AP ee6256b8
[93160.372968] wlan0: RX AssocResp from ee6e004e (capab=0x411 status=0 aid=1)
[93160.372974] wlan0: associated
[93160.395175] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[93168.669923] wlan0: deauthenticated (Reason: 1)
[93169.669074] wlan0: direct probe to AP ee6256b8 try 1
[93169.671747] wlan0 direct probe responded
[93169.671753] wlan0: authenticate with AP ee6256b8
[93169.674109] wlan0: authenticated
[93169.674115] wlan0: associate with AP ee6256b8
[93169.676637] wlan0: RX ReassocResp from ed17004e (capab=0x411 status=0 aid=1)
[93169.676642] wlan0: associated
[93170.924095] wlan0: no IPv6 routers present
[97374.939513] iwlagn 0000:03:00.0: Microcode SW error detected.  Restarting 
0x2000000.
[97375.164930] Registered led device: iwl-phy0::radio
[97375.164973] Registered led device: iwl-phy0::assoc
[97375.165017] Registered led device: iwl-phy0::RX
[97375.165057] Registered led device: iwl-phy0::TX
[97377.969068] wlan0: beacon loss from AP ee6256b8 - sending probe request
[97381.981078] wlan0: beacon loss from AP ee6256b8 - sending probe request
[97385.993121] wlan0: beacon loss from AP ee6256b8 - sending probe request
[97388.001080] wlan0: beacon loss from AP ee6256b8 - sending probe request

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: LENOVO 6477W9D
Package: linux-image-2.6.28-13-generic 2.6.28-13.44
ProcCmdLine: root=UUID=3d7d9f0b-29c2-418b-ba95-789b2f04ce07 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-13.44-generic
SourcePackage: linux

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386

-- 
iwlagn module disconnects randomly
https://bugs.launchpad.net/bugs/390741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to