8086:4235 Wi-fi doesn't work when booting or resuming from suspend while on battery

[Emmanuel Pacaud]

When I start my laptop, running on batteries, wifi failed to work properly.

Network manager shows a message saying my laptop is connected to my wifi network, but in fact the newtork is unreachable. After a while, network manager shows a "broken network" icon (with the red exclamation mark).

I'm able to make the wifi works by switching off then on the radio devices (RF_KILL switch).

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pacaud 1692 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 46'
   Mixer name : 'Intel Cantiga HDMI'
   Components : 'HDA:111d76b2,1028024d,00100302 HDA:80862802,80860101,00100000'
   Controls : 24
   Simple ctrls : 15
Date: Fri Sep 3 16:40:41 2010
HibernationDevice: RESUME=UUID=cc09a956-c9d4-47d9-92de-2019d1b828de
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100819)
MachineType: Dell Inc. Latitude E4300
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=a7fab861-76ed-4615-be73-119fe181d4af ro quiet splash
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 08/02/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0D201R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/02/2010:svnDellInc.:pnLatitudeE4300:pvr:rvnDellInc.:rn0D201R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4300
dmi.sys.vendor: Dell Inc.

[Jeremy Foshee (jeremyfoshee)]

Hi Emmanuel,

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.]

[Emmanuel Pacaud (emmanuel-pacaud)]

It seems to work fine with:

/home/pacaud/Bureau/linux-image-2.6.36-999-generic_2.6.36-999.201010160905_amd64.deb

[Brian Ealdwine (eode)]

I am also affected by this bug.

Installing the mainline kernel, linux-image-2.6.36-999-generic_2.6.36-999.201010231120_amd64.deb, in
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-10-23-maverick
fixed the problem.

Consequentially, I'm removing the tag as mentioned above.

[Brian Ealdwine (eode)]

(tag already removed)

[penalvch (penalvch)]

Emmanuel Pacaud, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]