intel 5100 wifi link - drops connection to access point/router every few minutes

Bug #307307 reported by dracflamloc
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On my laptop with an intel 5100 wifi link - it drops connection to access point/router every few minutes (but appears to still be working/up even though its not). It may be because of high network utilization, because dmesg has some messages from the iwlagn driver about something being 'too large', followed by messages about my manual reconnection to the router since.

To re-enable the wifi connection i have to disable it and re-enable it.

Revision history for this message
jbourdon (jean-louis-bourdon) wrote :

running ubuntu 8.10, 32 bits, on a laptop (HP HDX 16) which has the same chip (intel 5100 AGN)
No problem whatsoever... connection does not drop, and no messages from network manager either.

Maybe you should post the actual "messages from the iwlagn driver about something being 'too large', "

if I can help in anyway let me know

Revision history for this message
emilio (emiliomaggio) wrote :

I have a similar problem with a dell latitude e4300 and a belkin N1 router. The problem is limited to high bandwidth situations (e.g., playing youtube videos). The connection drops (although the network icon status does not change) and then is again active in about one minute.

Revision history for this message
zoryfl (zoryfl) wrote :

Using a Latitude E4300 with an Intel Corporation Wireless WiFi Link 5100 as well (running Archlinux 64bit).
Driver is: iwlwifi-5000-ucode 5.4.A.11-1

Everything works fine for me, never had any problems.

Revision history for this message
emilio (emiliomaggio) wrote :

This is the sysloog output while playing a video with iplayer.

Mar 21 16:43:00 emilio-laptop2 kernel: [ 7789.706638] wlan0: deauthenticated
Mar 21 16:43:00 emilio-laptop2 NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 0
Mar 21 16:43:00 emilio-laptop2 NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Mar 21 16:43:01 emilio-laptop2 kernel: [ 7790.709053] wlan0: authenticate with AP 00:17:3f:92:22:9b
Mar 21 16:43:01 emilio-laptop2 kernel: [ 7790.711045] wlan0: authenticated
Mar 21 16:43:01 emilio-laptop2 kernel: [ 7790.711053] wlan0: associate with AP 00:17:3f:92:22:9b
Mar 21 16:43:01 emilio-laptop2 kernel: [ 7790.715008] wlan0: RX ReassocResp from 00:17:3f:92:22:9b (capab=0x411 status=0 aid=1)
Mar 21 16:43:01 emilio-laptop2 kernel: [ 7790.715014] wlan0: associated
Mar 21 16:43:01 emilio-laptop2 kernel: [ 7790.715081] wlan0 (WE) : Wireless Event too big (342)
Mar 21 16:43:01 emilio-laptop2 NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 4
Mar 21 16:43:02 emilio-laptop2 NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 5
Mar 21 16:43:02 emilio-laptop2 NetworkManager: <info> (wlan0): supplicant connection state change: 5 -> 6
Mar 21 16:43:02 emilio-laptop2 NetworkManager: <info> (wlan0): supplicant connection state change: 6 -> 7
Mar 21 16:46:13 emilio-laptop2 kernel: [ 7982.511013] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.

Revision history for this message
emilio (emiliomaggio) wrote :

In my case installing ubuntu 9.04 beta solved the problem.

Revision history for this message
wlx (wangliangxu) wrote :

I have the same problem, ubuntu 9.04, dell e4200.
When downloading some big files, it is occasionally drop the connection.

Revision history for this message
David Tombs (dgtombs) wrote :

Thank you for your report. Unfortunately there is not enough information in this report to fix the issue, so I am closing this bug. Please change the status back to 'New' if you can provide more information. Sorry for the inconvenience.

@wlx: I would suggest filing your own bug report using 'ubuntu-bug network-manager'.

affects: ubuntu → network-manager (Ubuntu)
Changed in network-manager (Ubuntu):
status: New → Invalid
Revision history for this message
Tony Espy (awe) wrote :

I would also state that the original bug report was filed in 2008, and was incomplete at the time ( simple 1 paragraph description, no 'how-to-reproduce', log files, etc... ). In addition, the original reporter has never commented since originally describing the bug.

@dracflamloc

If you still are experiencing the problem, please re-test with 9.10 and report your results.

@David Tombs

In the future you can ask people to use "apport-collect -p network-manager <bug number>" instead of asking them to file a new bug via "ubuntu-bug". This is documented on the Wiki "Reporting Ubuntu Bugs" page.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.