iwlist scan makes /home unmountable
Using debian unstable, 2.6.14-2-686-smp #2 SMP
$sudo dpkg -l wireless-tools madwifi-source
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name
Version Description
+++-====================================-====================================-========================================================================================
ii madwifi-source
0.svn20051110-1 source for the Multiband Atheros
Driver for WiFi (madwifi)
ii wireless-tools
27+28pre11-1 Tools for manipulating Linux
Wireless Extensions
$lsmod | grep -sir ath
ath_pci 84892 0
ath_rate_sample 16968 1 ath_pci
wlan 152092 3 ath_pci,ath_rate_sample
ath_hal 148560 3 ath_pci,ath_rate_sample
$iwlist ath0 scan
Warning: Driver for device ath0 has been compiled with version 19
of Wireless Extension, while this program supports up to version 18.
Some things may be broken...
Segmentation fault
Once this happens the system becomes crazy for example,
a. I cannot unmount /home partition after I execute the above command
b. Any command starting with sudo just hangs there. The system is still
responsive (I can open a konsole window etc.,)
lspci -vv gives
0000:02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211
802.11ab NIC (rev 01)
Subsystem: Askey Computer Corp.: Unknown device 7005
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 0x08 (32
bytes)
Interrupt: pin A routed to IRQ 193
Region 0: Memory at c2000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
Checked BTS and there is nothing reported regarding this problem
My questions are
1) Can someone reproduce this in the first place (so that I can report
it to b.d.o)?
2) Against which package should I report this bug
(madwifi-source/wireless-tools etc.,)
3) Is there any solution/work around/other command to check the
available wireless networks?
thanks
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
Reply to: