wireless network has problem connecting and sometimes disconnect

Bug #569841 reported by Yves Dorfsman
170
This bug affects 34 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
Nominated for Lucid by grego77

Bug Description

Binary package hint: network-manager

Lenovo T60 with an Intel wireless card.

Wireless worked flawlessly in 9.04 and 9.10. My other computers still running 9.10 don't have any problem on the same wireless routes.

Just upgraded to 10.4 beta and often runs into these two problems.

1) after resuming from suspend, it cannot connect. Looking at daemon.log I see:

NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> associated
aristotle wpa_supplicant[1055]: WPA: Could not verify EAPOL-Key MIC - dropping packet
aristotle avahi-daemon[911]: Registering new address record for fe80::21c:bfff:fe08:704a on wlan0.*.
aristotle wpa_supplicant[1055]: WPA: Could not verify EAPOL-Key MIC - dropping packet
aristotle wpa_supplicant[1055]: WPA: Could not verify EAPOL-Key MIC - dropping packet

2) sometimes it just disconnect. This seems to be related to traffic, it only happens when streaming video from the net (youtube, vimeo, etc...). Doing a tail -f on daemon.log, this appears at the exact time that I loose my connection:

wpa_supplicant[1055]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
Architecture: i386
Date: Sun Apr 25 10:44:32 2010
IpRoute:
 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.173 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 192.168.2.43 dev wlan0 proto static
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: network-manager

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :
Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I noticed, and re-created in a consistent manner the CTRL-EVENT-DISCONNECTED error by following these steps:

-get a wireless connection
-go to maps.google.ca
-pick an address, any address (say, "eiffel tower, paris, france")
-switch to google street view (drag the little orange guy and drop it on the map)
-click on one of the arrow to move down a street, keep clicking to move down the street

Depending on the street, by the sixth time you click, it will disconnect, but sometimes as quick as on the third time.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I had said that the disconnection happened on some youtube videos, but I wasn't bale to find one that make it consistently happen. Vimeo on the other hand does. Try to watch:

http://vimeo.com/5427104

Make my wireless disconnect before I reach the 30 second mark, every single time, consistently.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I noticed that over 60 people followed this bug, but only one person (me!) says it affects them.

This bug has been opened for 10 days but has yet to be assigned.

If you are experiencing the problems described here, please open an account on launchpad and click on "this bug affect you" link:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/569841/+affectsmetoo

Thank you.

Revision history for this message
AndyVoutour (andyvoutour) wrote :

i get a different EAPOL error

- May 8 13:28:56 BENDER wpa_supplicant[836]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet

but the same CTRL-EVENT-DISCONNECTED error:

- May 8 13:35:26 BENDER wpa_supplicant[836]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
- May 8 13:35:28 BENDER wpasupplicant[836]: CTRL-EVENT-CONNECTED - Connection to 00:18:d1:e3:ac:66 completed (reauth) [id=0 idstr=]

RT73 chipset, using rt73usb kernel module, for the record, not the same intel chipset as the original poster.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I followed the instructions at:
http://live.gnome.org/NetworkManager/Debugging

And captured the wpa debug output while making the network fail by going down a street in google street view, and have attached the result, and have attached the result.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

And here is the debug output of wpasupplicant while trying to re-connect and getting "WPA: Could not verify EAPOL-Key MIC - dropping packet". I ended up having to turn off the network and back on before it could connect.

Revision history for this message
Barry Gaunt (barry-gaunt) wrote :

Same H/w as OP on Ubuntu 10.04.
Tried Google Map experiment same result - on 5th or 6th double click on StreetView lost connection. Just zooming in on map breaks connection.

Loses connection on YouTube as well.

Everything works fine on 9.04 and 9.10 and Windows 7 and Mac and Android and iPhone.

Same symptoms also with wicd network manager.

Connection takes long time be to established - sometimes but not always failing several times with bad password.
Retrying without changing password sometimes works sometimes not. Looks as if authentication is not properly taking place. Using WPA/WPA2.

Tried changing channel on wlan but same symptoms. Currently using channel 13 @ -45dbm (all other external wlans < -90dbm)

Revision history for this message
Barry Gaunt (barry-gaunt) wrote :

Back to Network Manager. When connection lost, then disabling wireless, enabling wireless, and reconnect to access point works sporadically.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

Barry: Was yours a fresh install or an upgrade from 9.10 (mine was an upgrade)?

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I too tried wicd and get the same problems. so it looks like it's not a network-manager issue, but either a wpasupplicant or a kernel driver problem.

affects: network-manager (Ubuntu) → wpasupplicant (Ubuntu)
Changed in wpasupplicant (Ubuntu):
status: New → Confirmed
Revision history for this message
Barry Gaunt (barry-gaunt) wrote :

I installed a fresh copy of Ubuntu 10.04 Netbook Edition onto a thinkpad T60 with a freshly installed Windows 7.

Revision history for this message
Jean-luc Henry (jlhenry) wrote :

I was disconnected twice while viewing this video: http://www.youtube.com/watch?v=Z9Ctt7FGFBo (it's in HD... so high traffic may be...?!).

Using Ubuntu 10.04 on Thinkpad T60. To get back my wifi, I had to manualy disconnect the wifi with my laptop switch, wait, then put on the switch.

Here is my log when I got disconnected:
May 17 07:17:59 2010 kernel: [ 1812.500037] No probe response from AP 00:25:86:d6:80:7e after 500ms, disconnecting.
May 17 07:17:59 2010 wpa_supplicant[981]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
May 17 07:17:59 2010 NetworkManager: <info> (wlan0): supplicant connection state: completed -> disconnected
May 17 07:17:59 2010 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
May 17 07:18:00 2010 kernel: [ 1813.129047] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
May 17 07:18:00 2010 kernel: [ 1813.129054] iwl3945 0000:03:00.0: Error setting new configuration (-110).
May 17 07:18:00 2010 kernel: [ 1813.632032] iwl3945 0000:03:00.0: Error sending REPLY_SCAN_CMD: time out after 500ms.
May 17 07:18:01 2010 kernel: [ 1814.128039] iwl3945 0000:03:00.0: Error sending REPLY_RXON: time out after 500ms.
May 17 07:18:01 2010 kernel: [ 1814.128046] iwl3945 0000:03:00.0: Error setting new configuration (-110).

Revision history for this message
Chenf (chenlao-hotmail) wrote :

Yes, this bug affects me too. It happened several times, most of during view the flash video with firefox.
My laptop also is T60, with fresh installed lucid. And the first log entry is:
wpa_supplicant[1011]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

Revision history for this message
kittens (maxonemillionone) wrote :

I have the same spec's as Chenf.

This is fucked up dude. I'm already thinking of switching back to backtrack 4. I thought upgrading the kernel would solve the problem but it didn't.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

People with T60 with a non-intel wireless card do not have this problem, this seems specific to the Intel 3945GB.

It'd be interesting to find if people with this card but other machines than the Lenovo Thinkpad T60 have the same problem...

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I have created two bug with the wpa-supplicant author:

http://w1.fi/bugz/show_bug.cgi?id=362

http://w1.fi/bugz/show_bug.cgi?id=363

Revision history for this message
countzero (countzeros) wrote :

Dell inspiron 6400 with Intel 3945 does have this problem

Revision history for this message
Jakob Schiøtz (schiotz) wrote :

I think there might be an issue with the Intel 3945 driver in the kernel. I tried to downgrade wpa_supplicant to the version used in Karmic, that did not help. I also tried to uninstall Network Manager and configure manually, but still the same problem. That leaves the kernel as the most obvious thing having changed since Karmic. Hmm, it should be possible to try the old kernel ....

I see this problem after upgrading my Thinkpad T60 after upgrading from Karmic to Lucid. It often takes up to 10 min before I can get it to connect, then it disconnects after an hour. Signal strength seems to have some influence, the problem gets much worse if I move away from the router.

Revision history for this message
Jakob Schiøtz (schiotz) wrote :

I can now confirm that it is indeed the kernel causing these trouble. I installed the kernel linux-image-2.6.31-21-generic from karmic-updates, and my wireless connection is again rock stable. Of cause installing a kernel from an old version of Ubuntu is kind of worrying, but a part from a broken boot splash screen I have seen no ill effects.

Since I do not own this bug, I can't change the package it affects, but it should probably be set to the kernel, and perhaps iwl3945 should be mentioned in the title, in the hope that somebody responsible for those parts sees the bug :-)

/Jakob

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

Thansk Jakob!

Good catch, and it actually make sense since wpa_supplicant works with the other cards...

Yves Dorfsman (dorfsmay)
affects: wpasupplicant (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
assignee: nobody → Ubuntu Kernel Network Team (ubuntu-kernel-network)
Revision history for this message
m'ric (petite-loutre) wrote :

hello guys,
is there any other way to solve the problem than downgrading the kernel ???
thanks a lot in advance !

Revision history for this message
chastell (chastell) wrote :

You can try upgrading the kernel instead – actually, checking whether a mainline 2.6.33 and/or 2.6.34 kernel fixes this bug would be quite beneficial: https://wiki.ubuntu.com/KernelTeam/MainlineBuilds

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

Thanks for the link Shot!

I have just upgraded to 2.6.34-020634rc7 following the procedure describe in the link:

-reconnection after resume or failure *seems* faster (well it has been faster, but I've only upgraded 10 minutes ago and had to go through 10 re-connection only, including a few suspend/resume tests. In the past, reconnection time was very inconsistent (from instant to re-trying for 20 minutes), so maybe I just hit a lucky strike)

-failing under load is still the same. Thanks Barry for the zooming trick in street view... zoom 2 or 3 times and you lose the connection.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I created a new bug report on the intellinuxwireless bugzilla:
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2213

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

removed Kernel Network team as that is not a generally viewed team anymore.

~JFo

Changed in linux (Ubuntu):
assignee: Ubuntu Kernel Network Team (ubuntu-kernel-network) → nobody
Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

It was a lucky strike... tonight I cannot reconnect, worse than before.

Downloading the kernel seems to be the only solution for now.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

Created http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2216 for the issue of not being able to re-connect.

Revision history for this message
More (more.linux) wrote :

I have the same problem on my Dell Inspiron 9400 with a Intel® PRO/Wireless 3945ABG wireless card. The connection drops when using Google Maps, Youtube or other big downloads.

Also tested the linux-backports-modules-wireless-lucid-generic packages, but no luck there. Never had any problems on Ubuntu 9.10 or 9.04 with this laptop. Also tested with Win XP on this laptop. No problems so it's not the router or laptop.

Revision history for this message
More (more.linux) wrote :

Followed Jakob's advise and reverted to the Ubuntu 9.10 kernel 2.6.31-21. Now the "wireless dropping the connection" problem is gone.

Revision history for this message
grego77 (gregory-cordani) wrote :

True...but we are now stuck in an older kernel...

Revision history for this message
Bert Haskins (bhaskins) wrote :

Same problem, disconnect on anything but small download.. hard to reconnect, but with Atheros and Intel 2200BG mini-pci cards. Comp is A31.
Was/is fine with 9.10.
Also has total lockup with suspend to ram... requires powerdown

Revision history for this message
grego77 (gregory-cordani) wrote :
Revision history for this message
Jakob Schiøtz (schiotz) wrote :

It may be a duplicate, but I am not sure. That problem seems to affect Karmic as well, this problem certainly did not, and is in fact solved by downgrading to the Karmic kernel. Also, this bug is certainly not related to the network manager package, as I tried uninstalling it and configured the network manually. Finally, the other bug describes changing to WPA2 / AES on the access point as a workaround, I tried that to no avail.

Revision history for this message
More (more.linux) wrote :

@Gregory Cordani: This is definitively NOT a duplicate. The dmesg messages shown in bug 425455 don't show up in this problem. The disconnect isn't after 30 seconds, but 100% reproducible after zooming in on google maps or using youtube. My system is running WPA2 - AES and is affected by this bug as of Ubuntu 10.04. It never ever showed up in Ubuntu 9.10 or 9.04. I'm still using the same hardware.

Also if the bug was caused by the Network Manager tool the problem should also happen when using the older 2.6.31-21 kernel, but it doesn't. So this really looks like a kernel problem instead of a Network Manager problem.

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

I can confirm this issue.

I'm running Ubuntu 10.04 on a ThinkPad T60p with an Intel 3945ABG wireless chip, and I've experienced many of these symptoms. The Google Maps/YouTube stuff, I haven't noticed, but the frequent disconnecting I have.

Lately, it's been taking twenty minutes of trying to connect, timing out, and trying again to connect with my WPA2 network. And like Jakob pointed out, the problem seems to be related to my proximity to the router. The farther away I am, the more trouble I have connecting. I've tried both Wicd and Network Manager, and neither have been of any use.

I downgraded the kernel to the latest Karmic version, as Jakob suggested, and things *seem* to be working better. I was connected instantly on reboot and I haven't had any connection dropping problems yet. Here's hoping . . .

Revision history for this message
Andreas (andreas-kotowicz) wrote :

I have one laptop with a iwl3945 card. I've successfully managed to get the v2.6.33.5-lucid kernel to run (I couldn't get the system to boot with 2.6.34 and 2.6.35). I still get the disconnects, but now network manager will successfully reconnect - I don't need to first turn off and then turn on the wireless system anymore. So it's a partial improvement. Furthermore, it clearly a traffic issue that leads to the problem: Once a certain amount of data get's downloaded via the wireless device, I get the disconnects.

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

Here's something interesting:

Last night, I installed mplayer using Synaptic. Shortly after the install, my wireless connection went sour. Basically the same symptoms I had before I downgraded to the Karmic kernel. I uninstalled mplayer and all did an apt-get autoremove to get rid of all the unnecessary dependencies, but I still wasn't able to get a connection. This morning, I connected without a hitch, and I've had no issues at all today.

It's probably nothing . . . maybe just a fluke. But I thought I'd mention it anyway.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

Andreas: I think the reconnection is fast because you recently rebooted. I had the same experience with the 2.6.35 kernel, but after a day or so, it went back to taking ages to re-connect.

Chris: Did you check what packages were installed with mplayer? Did it install a new kernel? So far, everything seems to point to the kernel.

Revision history for this message
Dave Walton (diggernet) wrote :

I am seeing this problem, too. Fresh install of 10.04 on a Thinkpad T60 with Intel 3945ABG.
In my case, I see the disconnect when running Google Earth, but I haven't yet tried doing any of the other things that are reported to trigger it. This is a test install on a spare partition, and I've been testing the usability of Google Earth on 10.04.

What I see is that while running Google Earth, the network connection will drop. After a LONG time, it will fail to reconnect and prompts me for the connection settings again. Re-entering them doesn't help. The only way I've been able to regain the connection is by disabling and re-enabling networking, then turning the hardware wi-fi switch off for a bit then back on. That doesn't always work, and eventually seems to stop working at all. At that point, the only fix I've found is a reboot.

Based on some helpful advice, I tried installing this kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/

I saw a noticeable improvement in Google Earth frame rate, but the network problems are still there. Slightly worse, even, in that at least once the connection dropped and Ubuntu didn't even notice it had dropped. Still thought it had a network connection, only it didn't work.

Right now, this problem is keeping me from even considering upgrading from 8.10 to 10.04. I'd really like to get past it and move on to testing other things. It appears that the workaround until this gets fixed is to downgrade the kernel. But my experience in tinkering with the kernel is very limited. Could someone give some easy-to-follow instructions for safely installing whatever version of the kernel will work around the problem?

Thanks.

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

Hey Dave,

Downgrading the kernel really isn't all that difficult. As a matter of fact, it took me more time to find the kernel and reconfigure GRUB 2 (I was familiar with the earlier version of GRUB) than it took to do the install. Here's what you'll need to do:

Download the kernel of your choice. I'm using 2.6.31-21, but it looks like 2.6.31-22 came out since then. I know for a fact that the former works . . . not so sure about the latter, so YMMV.

Here's a link to 2.6.31-21: http://packages.ubuntu.com/karmic-updates/linux-image-2.6.31-21-generic

Here's a link to 2.5.31-22: http://packages.ubuntu.com/karmic/linux-image-2.6.31-22-generic

Once you get the kernel downloaded, install it. It's just a *.deb, so it shouldn't be too hard.

After that, you'll need to edit GRUB so that it boots the older kernel by default. Otherwise, GRUB will keep booting the newest kernel and the problem won't get fixed. To do that, type cat /boot/grub/grub.cfg into a terminal and scroll until you find the section that contains the kernel you just installed (either 2.6.31-21 or -22).

Press Ctrl+Shift+C to copy the quoted text after "menuentry." Mine reads 'Ubuntu, with Linux 2.6.31-21-generic'.

Next, in a terminal, type sudo pico /etc/default/grub. Next to GRUB_DEFAULT=, paste the text you just copied by pressing Ctrl+Shift+V. This forces GRUB to pick that exact entry each time the computer boots. You could also control the default entry by entering the number of the entry (0 for the first entry, 1 for the second, and so on), but the number of an entry will change when you update kernels in the future. Setting the default using the exact name is much safer.

Also, you'll probably want to change GRUB_TIMEOUT= to something greater than 0. Punch in a (small) number to control how many seconds the GRUB menu appears at boot. I think it's helpful to have GRUB show up, even if it's only for a second or two. That way, if something goes wrong, you have easy access to alternate kernels, memtest, and recovery modes.

Make sure to run sudo update-grub after you finish editing /etc/default/grub. Restart your computer, and hopefully the kernel downgrade will fix your wireless issues. Be warned that swapping the kernel *may* mess up your boot splash screen. Everything will load properly, but it won't necessarily look pretty and you might get an odd error message or two. If that happens, don't panic. Just let it run its course and be patient :-).

Revision history for this message
More (more.linux) wrote :

The latest kernel( 2.6.32-23-generic) update doesn't fix the problem. Wireless still is dropped when zooming in using http://maps.google.com

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

I'm glad someone tried the latest kernel. I was planning on asking about it sooner or later anyway.

It's interesting that a kernel upgrade didn't change anything. To me, it seems like this bug is a pretty major issue; not being able to reliably use WiFi is a huge lack of functionality, especially for a laptop. And I could be wrong about this, but isn't the Intel 3945 a pretty common wireless card?

In spite of all that, I haven't seen any real progress towards a solution. Are the developers aware of the issue? Are steps being made to fix it?

As far as I can tell, the bug hasn't been assigned to anyone and it's importance hasn't been determined yet. Can we get those things changed? I've got a bad feeling that as long as this isn't assigned to anyone, it isn't going to get remedied any time soon.

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

In my experience, the newer kernel, 2.6.32, is even worse.

I have opened tickets on the intel website (search this thread for intellinuxwireless), but the developers are asking that somebody gives then a log of the iwl3945 compiled with debug mode before they'll look at it.

I am a bit disappointed by intel, I have a feeling the developers are actually people from the community who aren't intel employees. I specifically bought a laptop with an intel card because they work(ed) well on Linux, I expect a hardware vendor to put some effort to make a good driver for their piece of hardware if they want my money.

I have compiled a iwl3945.ko with the debug option, but it won't load:
FATAL: Error inserting iwl3945 (/lib/modules/2.6.32-21-generic-pae/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko): Invalid module format
I don't have a lot of time on my hands right now, I am hoping to be able to get to it in a few weeks.

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

Hey Yves,

Thanks for the effort, and thanks for reporting the bug in the first place---both here and to Intel.

I'll have a LOT of time on my hands this next week and if it's not too complicated, I'd be willing to do the debug compile. Is there a how-to or tutorial of some sort you could point me towards?

Thanks!

Revision history for this message
Dave Walton (diggernet) wrote :

Hi Chris,

Thanks for the downgrade details. It went quite smoothly. Unfortunately, I couldn't tell whether it fixed the problem or not, and it wouldn't matter if it did. Downgrading to 2.6.32 made Google Earth unusable (which is exactly the reason I never upgraded to 9.04 or 9.10 in the first place). So it looks like my only hope for 10.04 is if there's a resolution to this bug.

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

Hey Dave,

I'm glad the how-to worked for ya :-).

On the other hand, it would've been nice if it had actually fixed the problem. I was under the impression that you were having trouble getting wireless in general, but after re-reading your first post, I realized that your problem was with Google Earth triggering a connection drop.

It's interesting that you're able to connect in the first place, actually, because with the newest kernels, I'm not even able to do that. It's hard to drop a connection that you're never able to establish, ya know? What's your secret ;-)?

Revision history for this message
Dave Walton (diggernet) wrote :

Chris: That's a really good question. I haven't had any problem getting a connection right after boot. It just drops under load. Mine is a fresh install on a spare partition, with very little done to it. I don't think you've said what yours is. I've got a T60, you've got a T60p. I'm using WEP (yuck), you are using WPA2. Maybe that's the secret?

Revision history for this message
Andreas (andreas-kotowicz) wrote :

the problem completely vanished for me on two different laptops once I installed http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-maverick/. I did some heavy stress test, downloading a couple GB of iso images and I get no more disconnects! previously I got disconnects after 200MB or so. Maybe this will work for other people too.

Revision history for this message
seagullplayer77 (seagullplayer77) wrote :

Hey Andreas,

I'm on vacation right at the moment and I'm not in the mood to start experimenting, but I'll try the kernel upgrade when I get home.

Even so, it would be nice if the devs came up with a Lucid kernel that fixed the issue. We've either been downgrading to Karmic kernels or upgrading to Maverick kernels, and those are both workarounds, no matter how you slice it. I'll try the Maverick kernel later, but I'd still like a working Lucid kernel.

Revision history for this message
Martin Jinoch (jinoch) wrote :

I can confirm that installing http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-maverick/ solved this problem on my ThinkPad T60 (model 2007-F4G)

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I installed 2.6.35 on two different T60 2007-67U:

-it fixed the bandwidth issue, I was able to navigate every which way in google map streetview, and watch several Vimeo videos

-reconnecting after a suspend/resume cycle is still an issue, it actually seems worse.

Revision history for this message
Martin Jinoch (jinoch) wrote :

#52: strange, reconnecting after resume from "Suspend to memory" is way faster on my T60 2007-F4G with 2.6.35 kernel than it was with ubuntu 10.04 default kernel

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

more progress... wicd was competing with network-manager!

I do feel like an idiot about this, but here we go:
Way back in May, when we suspected network-manager was the issue, somebody suggested to use "wicd" instead. This did not help, and we quickly came to the conclusion that the issue was the intel driver.

One of the issue I have had, is that it would take 5 or 10 minutes before getting a connection, get a connection, and within 10 seconds loose that connection, and it would do that again and again. Eventually, it would connect and stay connected. Tonight, my disk kept spinning and stopping while I was just reading a long email, wondering what was going on, I ran top, and found "wicd" running (don't think that's what made the disk spin up, but that's a different story). I removed wicd, and tried suspend/resume cycles several times, and it now takes only 5 to 10 minutes to connect, once it connects, it does not loose that connection again. I am now able to connect with 2.6.35, in less than 10 minutes, (and if not, rebooting fixes it). And I have done more testing with 2.6.35, it does not fail under load.

To check:
dpkg -l wicd-daemon

If it lists it with "ii" at the front, it means it is installed. then:

dpkg -r wicd-daemon wicd-gtk

Also, follow the link from Andreas and Martin to download 2.6.35, installing it is as simple as "dpkg -i linux-image-2.6.35*", 2.6.35 does NOT fail under load. It would be nice if Intel fixed that bug in 2.6.32, 33, and 34, but I have a feeling it is not going to happen.

Revision history for this message
More (more.linux) wrote :

Since I updated my system to kernel 2.6.35 some 4 days ago all the problems with the wireless dropping is gone. Used the system intense (google maps, youtube, torrents and other stuff) and not one connection drop. My system is running smoothly on that new kernel and I'm going to stay there.

Thanks for the 2.6.35 kernel tip Andreas.

Revision history for this message
grego77 (gregory-cordani) wrote :

Hi all !
I upgraded also to kernel 2.6.35, but unfortunately, I still have the disconnections when under heavy trafic...
It worked perfectly with kernel 2.6.31...

can you tell me if the issue is tha same as yours ???

Thank you

Revision history for this message
chokuchou (chokuchou-gmail-deactivatedaccount) wrote :

The bug doesn't appear in mainline 2.6.36-999.201010311115

Revision history for this message
Wendell Nichols (wcn00) wrote :

My machine is a t61p with intel wireless. This bug commenced at kernel 2.6.32-26. I have hardcoded my boot to use 2.6.32-25 and will not update till this is fixed.
In case my symptoms are a little different:
-I suspend the machine to memory
-I resume from suspend (running on battery)
-after about 2 minutes the wireless fails. I "usually" see messages like:
Dec 21 16:31:55 bilbo kernel: [ 8402.312727] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1c:f0:f7:5a:ab tid = 0
Dec 21 20:07:09 bilbo kernel: [21316.072171] CE: hpet increasing min_delta_ns to 75936 nsec
Dec 21 20:58:55 bilbo kernel: [24422.680917] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1c:f0:f7:5a:ab tid = 0
Dec 22 00:31:23 bilbo kernel: [37169.999403] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1c:f0:f7:5a:ab tid = 0
Dec 22 04:54:54 bilbo kernel: [52981.350721] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1c:f0:f7:5a:ab tid = 0

in the log when this occurs.
So for now I'm halted at kernel 2.6.32-25 and can go no further.
wcn

Revision history for this message
Yves Dorfsman (dorfsmay) wrote :

I have been using Ubuntu 10.10 with stock kernel 2.6.35 for a while now, and this working fine and stable now, I think it's fair to close this bug now - I have just closed the two Intel bugs report on this. It would be nice if the fixes were ported back to 10.04 but I doubt it will.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Wendell Nichols (wcn00) wrote :

Well it turns out that the 2.6.35 is available via Synaptic so I installed it. Had to force the reinstall of the nvidia driver. My wireless is now working ok. So I guess we can close this.
thnx.
wcn

Revision history for this message
Andreas (andreas-kotowicz) wrote :

I still have this problem on my ubuntu 10.10 with 2.6.35-24.

Revision history for this message
Jule Slootbeek (jslootbeek) wrote :

I'm having this problem on Ubuntu 16.04 with 4.4.0-29.
It occurs consistently every time after a reboot when I open Chromium (50.0.2661.102-0ubuntu0.16.04.1.1237) and play a YouTube video. It will disconnect once (about 3-4 minutes into a video) an when I re-connect to the same WiFi AP it will stay connected.

Jun 30 09:03:51 dolphy wpa_supplicant[1009]: enp2s10: CTRL-EVENT-DISCONNECTED bssid=58:6d:8f:b7:5c:98 reason=0
Jun 30 09:03:51 dolphy wpa_supplicant[1009]: ioctl[SIOCSIWENCODEEXT]: Invalid argument
Jun 30 09:03:51 dolphy wpa_supplicant[1009]: message repeated 2 times: [ ioctl[SIOCSIWENCODEEXT]: Invalid argument]
Jun 30 09:03:51 dolphy NetworkManager[833]: <info> [1467291831.4681] device (enp2s10): supplicant interface state: completed -> disconnected
Jun 30 09:03:51 dolphy wpa_supplicant[1009]: enp2s10: Associated with 58:6d:8f:b7:5c:98
Jun 30 09:03:51 dolphy NetworkManager[833]: <info> [1467291831.4769] device (enp2s10): supplicant interface state: disconnected -> associated
Jun 30 09:03:51 dolphy NetworkManager[833]: <info> [1467291831.4958] device (enp2s10): supplicant interface state: associated -> 4-way handshake
Jun 30 09:03:51 dolphy wpa_supplicant[1009]: enp2s10: WPA: Key negotiation completed with 58:6d:8f:b7:5c:98 [PTK=CCMP GTK=TKIP]
Jun 30 09:03:51 dolphy wpa_supplicant[1009]: enp2s10: CTRL-EVENT-CONNECTED - Connection to 58:6d:8f:b7:5c:98 completed [id=0 id_str=]
Jun 30 09:03:51 dolphy NetworkManager[833]: <info> [1467291831.5177] device (enp2s10): supplicant interface state: 4-way handshake -> completed
Jun 30 09:03:52 dolphy wpa_supplicant[1009]: enp2s10: WPA: Key negotiation completed with 58:6d:8f:b7:5c:98 [PTK=CCMP GTK=TKIP]
Jun 30 09:03:58 dolphy wpa_supplicant[1009]: message repeated 6 times: [ enp2s10: WPA: Key negotiation completed with 58:6d:8f:b7:5c:98 [PTK=CCMP GTK=TKIP]]
Jun 30 09:04:00 dolphy wpa_supplicant[1009]: enp2s10: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
Jun 30 09:05:53 dolphy wpa_supplicant[1009]: message repeated 98 times: [ enp2s10: WPA: EAPOL-Key Replay Counter did not increase - dropping packet]

Revision history for this message
Adam Kessel (adam-rosi-kessel) wrote :

I'm experiencing the same behavior with Ubuntu 20.04 on an older laptop with a Dell/Broadcom BCM43228 NIC. Kernel is 5.4.0-52-generic. Below is an example from syslog. Periodically the WiFi just stops working and takes a long while to resume again. Anyone have any tips from troubleshooting/fixing??

NetworkManager[720]: <info> [1604262830.0384] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
NetworkManager[720]: <info> [1604262830.0388] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
NetworkManager[720]: <info> [1604262830.0394] manager: NetworkManager state is now CONNECTED_LOCAL
NetworkManager[720]: <info> [1604262830.0424] manager: NetworkManager state is now CONNECTED_SITE
NetworkManager[720]: <info> [1604262830.0438] policy: set '(network name)' (wlp2s0) as default for IPv4 routing and DNS
NetworkManager[720]: <info> [1604262830.0455] device (wlp2s0): Activation: successful, device activated.
systemd[1]: systemd-rfkill.service: Succeeded.
wpa_supplicant[765]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
wpa_supplicant[765]: message repeated 6 times: [ wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet]
chromium_chromium.desktop[6308]: [6308:6451:1101/153351.623591:ERROR:connection_factory_impl.cc(428)] Failed to connect to MCS endpoint with error -105
wpa_supplicant[765]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
wpa_supplicant[765]: message repeated 8 times: [ wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet]
systemd-resolved[619]: Using degraded feature set (UDP) for DNS server 192.168.4.1.
wpa_supplicant[765]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
wpa_supplicant[765]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
wpa_supplicant[765]: wlp2s0: WPA: Key negotiation completed with 48:dd:0c:c3:47:66 [PTK=CCMP GTK=CCMP]
wpa_supplicant[765]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
wpa_supplicant[765]: message repeated 15 times: [ wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet]
systemd-resolved[619]: Using degraded feature set (UDP) for DNS server 68.237.161.12.
systemd-resolved[619]: Using degraded feature set (TCP) for DNS server 192.168.4.1.
systemd-resolved[619]: Failed to send hostname reply: Invalid argument
systemd-resolved[619]: message repeated 2 times: [ Failed to send hostname reply: Invalid argument]
wpa_supplicant[765]: wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
wpa_supplicant[765]: message repeated 30 times: [ wlp2s0: WPA: EAPOL-Key Replay Counter did not increase - dropping packet]

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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