168c:001c ath5k gets hard blocked status in rfkill after turning off and then on
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
After turning off wifi card and then turning it on in nm-applet card becomes hard blocked in rfkill
#> rfkill list:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
if I unload module an then load it again card still is hard blocked:
#> modprobe -r -f ath5k && sleep 5s && modprobe ath5k && rfkill list
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
if I kill process:
#> /usr/lib/
and then
#> modprobe -r -f ath5k && sleep 5s && modprobe ath5k && rfkill list
card becomes unlocked
#> rfkill list
4: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
but after awhile process /usr/lib/
4: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
#> lspci -vv:
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
Subsystem: Device 1a32:0100
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at d8000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath5k
Kernel modules: ath5k
---
AlsaVersion:
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Compiled on Apr 29 2010 for kernel 2.6.32-22-generic (SMP).
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdc440000 irq 28'
Mixer name : 'Conexant CX20549 (Venice)'
Components : 'HDA:14f15045,
Controls : 28
Simple ctrls : 12
DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
MachineType: BenQ Joybook R55v
Package: linux (not installed)
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=pl_PL.UTF-8
SHELL=/bin/bash
ProcVersionSign
Regression: No
RelatedPackageV
Reproducible: Yes
Tags: lucid networking needs-upstream-
Uname: Linux 2.6.32-22-generic x86_64
UserGroups:
dmi.bios.date: 02/06/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: NOTE BIOS Version Q4A06
dmi.board.name: Joybook R55v
dmi.board.vendor: BenQ
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Joybook R55v
dmi.product.
dmi.sys.vendor: BenQ
tags: | removed: needs-kernel-logs |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.
Please run the following command which will attach necessary information:
apport-collect 478036
if you are using Karmic Koala (9.10) or newer, or
apport-collect -p linux-image-`uname -r` 478036
if you are using Jaunty Jackalope (9.04)
Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python- launchpadlib' . Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.
If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options): signature > version.log
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeam/ KernelTeamBugPo licies. Thanks in advance!