Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/528161
Title:
Intel wifi cards fail (temperature-dependently?)
Status in Intel Linux Wireless:
Unknown
Status in linux package in Ubuntu:
Won't Fix
Bug description:
At university, we suffer from wifi disconnections with notebooks using
the iwlagn driver, especially with the Intel WiFi 5100 card.
It seems the hotter the air or the device is, the more it rejects to
connect to any type of wifi network. In dmesg, messages like the
following appear:
[ 84.893229] wlan0: direct probe to 00:1c:4a:44:44:e7 (try 1)
[ 85.092149] wlan0: direct probe to 00:1c:4a:44:44:e7 (try 2)
[ 85.292149] wlan0: direct probe to 00:1c:4a:44:44:e7 (try 3)
[ 85.492147] wlan0: direct probe to 00:1c:4a:44:44:e7 timed out
[ 96.318074] wlan0: direct probe to 00:1c:4a:44:44:e7 (try 1)
[ 96.516177] wlan0: direct probe to 00:1c:4a:44:44:e7 (try 2)
[ 96.716086] wlan0: direct probe to 00:1c:4a:44:44:e7 (try 3)
[ 96.916169] wlan0: direct probe to 00:1c:4a:44:44:e7 timed out
... and so on.
For some of my friends, the problem is not that serious as it appears only in
very hot rooms with their laptops.
For others, like me, the problem is critical because our machines do not
connect to _any_ network if the temperature is below 10°C.
The problem started in January 2010 and (whyever) gets worse. Until
February, I had decent disconnects, but could still connect at home,
while now, at the end of February I cannot connect to networks
anymore.
I *guess* the problem was introduced with one of the 2.6.32-rc
kernels. The killer flaw is that it does not go away switching back to
one of the old kernels (.31 from Karmic, .28 from Jaunty) which worked
fine over months before or forward to .33.
It seems to have done something hardware/firmware related or any other crazy
voodoo.
The problem is present over (most probably) all distributions - we use
Debian, Ubuntu and Arch Linux. It might be possible that more people will run
into this with Lucid.
Someone reported it here: new upstream bug:
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2171
(old bug was http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2157)
To manage notifications about this bug go to:
https://bugs.launchpad.net/intellinuxwireless/+bug/528161/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
