wireless handler loop forever if we start thru recovery mode

Bug #885884 reported by swndtan
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

If I start my Ubuntu-Natty Nerwhall on recovery mode with a given access point with security,
when I choose resume boot, there is a looping process on wireless handler ( take a long time for this process to identified ),
and, if you turn off your wireless button, and then, the bug comes up ( which is looping process and there is no way to cancel up with Ctrl-C or else ).

my quick-fix, is turn off my wireless button and force restart the system.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: suwanditan 2303 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd0640000 irq 45'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,14c00235,00100002 HDA:11c11040,11c10001,00100200'
   Controls : 21
   Simple ctrls : 11
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=77d19f70-b040-4505-a905-c7007816563c
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: COMPAL HGL31I
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=c8c4c277-3594-410d-ae2f-950bc58a94f3 ro single
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-11-generic N/A
 linux-backports-modules-2.6.38-11-generic N/A
 linux-firmware 1.52
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: natty
Uname: Linux 2.6.38-11-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/10/2007
dmi.bios.vendor: COMPAL
dmi.bios.version: 116A
dmi.board.name: HGL3X
dmi.board.vendor: COMPAL
dmi.board.version: Null
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: COMPAL
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr116A:bd07/10/2007:svnCOMPAL:pnHGL31I:pvr-:rvnCOMPAL:rnHGL3X:rvrNull:cvnCOMPAL:ct10:cvrN/A:
dmi.product.name: HGL31I
dmi.product.version: -
dmi.sys.vendor: COMPAL

swndtan (swndtan)
summary: - wireless handler loop forever if we start thru recovery choice on grub
+ wireless handler loop forever if we start thru recovery mode
description: updated
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.

Please run the following command which will attach necessary information:

apport-collect 885884

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
swndtan (swndtan) wrote : AcpiTables.txt

apport information

tags: added: apport-collected natty
description: updated
Revision history for this message
swndtan (swndtan) wrote : AlsaDevices.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : AplayDevices.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : BootDmesg.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : CurrentDmesg.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : IwConfig.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : Lspci.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : Lsusb.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : PciMultimedia.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : ProcCpuinfo_.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : ProcInterrupts.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : ProcModules.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : UdevDb.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : UdevLog.txt

apport information

Revision history for this message
swndtan (swndtan) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

swndtan, 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 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.11-rc5

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: Confirmed → Incomplete
tags: added: needs-upstream-testing
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.