[Kernel Regression] Wireless card disconnects when PC too hot

[djipey]

Im' french and noob, so please excuse my english and my mistakes. I'm going to try to do my best.

On Ubuntu Lucid Lynx, with a Aspire 7520 and a wireless card AR7005EG, when the temperature of my PC increases too much, i lost the wireless. For example, when the acpi parameter of my conky indicates 80°C (it's just an indication, just remember it's a little bit hot), my card seems to disconnect.
But when i downgrade to Karmic koala, i don't have anymore this problem. My acpi can go over 90°C whithout connection problem.
(I know it's hot, but it has been like that since the beginning).
When i just apply the updates to Karmic koala after an install (from the distibution proposed by default on ubuntu.fr), i have connection problems too. I think one of the packages installed during this update is responsible.

I tried to boot on the old kernel(2.6.31-14-generic) proposed during the boot after an upgrade to Lucid from Karmic, and i still have the problem. I think this is not a kernel or driver problem, because when my PC is cool down or when i am on Karmic, everything is ok.

ProblemType: Bug
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: djipey 1881 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xf2680000 irq 21'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250126,00100003 HDA:14f12c06,10250126,00100000'
   Controls : 11
   Simple ctrls : 8
Date: Tue Jul 6 10:44:23 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=/dev/sda5
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Acer Aspire 7520
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=4179e8c6-3897-4958-9ed0-5de95680a99a ro quiet splash
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/07/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.08
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.08:bd09/07/2007:svnAcer:pnAspire7520:pvrV1.08:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 7520
dmi.product.version: V1.08
dmi.sys.vendor: Acer

[Jeremy Foshee (jeremyfoshee)]

Hi djipey,

If you could also please 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[djipey (jeanpatrick-francoia)]

I tried the lastest version of the kernel, find on http://kernel.ubuntu.com/~kernel-ppa/mainline/ and in the sub-folder:v2.6.35-rc4-maverick/.

I booted on this kernel, but i didn't get any graphical environment. Just a black screen blinking, with :
ah5k phy0: gain calibration timeout.

Let me know if i did something wrong. Thanks for your help.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.