[Lucid] Wireless network often ruined after resume or normal boot

Bug #590030 reported by Lollerke
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

If resuming or booting ruins the wireless network I can't reenable it. Disabling and enabling wireless network,unplugging and plugging in the wireless device doesn't help. Only reboot solves the problem. This bug was not present in Karmic.

First error:
Jun 5 10:04:52 ecs kernel: [ 10.312712] ehci_hcd 0000:00:13.2: force halt; handhake f8058824 00004000 00000000 -> -110
Jun 5 10:04:52 ecs NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Jun 5 10:04:52 ecs NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-generic 2.6.32-22.36
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: janos 1282 F.... pulseaudio
CRDA: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfcff4000 irq 16'
   Mixer name : 'SigmaTel 92HD206X'
   Components : 'HDA:83847645,10192816,00100402'
   Controls : 37
   Simple ctrls : 24
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfea7c000 irq 18'
   Mixer name : 'Nvidia ID b'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Date: Sat Jun 5 10:14:45 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ECS A780GM-A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=5786f7c5-e4ba-4c7f-84cd-d859d1c8684d ro quiet splash
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 06/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.name: A780GM-A
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd06/12/2009:svnECS:pnA780GM-A:pvr1.0:rvnECS:rnA780GM-A:rvr1.0:cvnECS:ct3:cvr:
dmi.product.name: A780GM-A
dmi.product.version: 1.0
dmi.sys.vendor: ECS

Revision history for this message
Lollerke (pumba88) wrote :
Lollerke (pumba88)
description: updated
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Lollerke,

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

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Lollerke (pumba88) wrote :

How do I insert the nvidia kernel module into the new kernel? (I installed the nvidia driver from the hardware drivers application). Resume fails with the generic driver,so I cannot test this bug.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
tags: added: kernel-power
removed: needs-upstream-testing
Revision history for this message
penalvch (penalvch) wrote :

Lollerke, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.