From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Walker Date: Tue, 22 Dec 2009 13:39:30 -0500 Subject: [ath9k-devel] trouble with DWA-552 and ath9k In-Reply-To: <4B30D348.3080600@charter.net> References: <4B2A5FA8.8060905@charter.net> <19242.62265.487757.695747@gargle.gargle.HOWL> <4B2AFC5D.1060001@charter.net> <19243.2224.974537.876295@gargle.gargle.HOWL> <4B2C42FD.6000303@charter.net> <19248.21007.59863.967539@gargle.gargle.HOWL> <4B30D348.3080600@charter.net> Message-ID: <4B311262.2060503@charter.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 12/22/2009 09:10 AM, Brian Walker wrote: > cfg80211: World regulatory domain updated: > (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) > (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) > (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) > ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5 > PCI: setting IRQ 5 as level-triggered > ath9k 0000:00:0a.0: PCI INT A -> Link[LNKC] -> GSI 5 (level, low) -> > IRQ 5 > ath: EEPROM regdomain: 0x10 > ath: EEPROM indicates we should expect a direct regpair map > ath: Country alpha2 being used: CO > ath: Regpair used: 0x10 > phy0: Selected rate control algorithm 'ath9k_rate_control' > Registered led device: ath9k-phy0::radio > Registered led device: ath9k-phy0::assoc > Registered led device: ath9k-phy0::tx > Registered led device: ath9k-phy0::rx > phy0: Atheros AR9280 Rev:2 mem=0xfa4a0000, irq=5 > cfg80211: Calling CRDA for country: CO > cfg80211: Regulatory domain changed to country: CO > (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) > (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) > (5170000 KHz - 5250000 KHz @ 20000 KHz), (300 mBi, 1700 mBm) > (5250000 KHz - 5330000 KHz @ 20000 KHz), (300 mBi, 2300 mBm) > (5735000 KHz - 5835000 KHz @ 20000 KHz), (300 mBi, 3000 mBm) > ADDRCONF(NETDEV_UP): wlan0: link is not ready > > The system lockups seem to occur most often when the debugfs > filesystem is mounted. Also, curious why the driver is saying AR9280 > when lspci says AR922X? In /etc/modprobe.d/local.conf I have now set: > > options ath9k debug=0xffffffff > > since I do not seem to be getting any kind of debugging messages, but > I still don't see much in the way of debugging messages in the kernel > logs. > > Brian > > On 12/21/2009 11:58 PM, Sujith wrote: >> Brian Walker wrote: >>> I've recompiled compat-wireless-2009-12-11 with "CONFIG_ATH_DEBUG=y" >>> and >>> "CONFIG_ATH9K_DEBUGFS=y" in config.mk (and did make and then make >>> install), added "options ath9k debug=0x600" to the file >>> /etc/modprobe.d/local.conf (I am running Fedora 11) and rebooted. >>> >>> After rebooting, I did "mount -t debugfs none /sys/kernel/debug/". >>> Indeed, there is now a /sys/kernel/debug/ath9k directory. Am I looking >>> for anything in particular? The directory /sys/kernel/debug/ath9k/phy0/ >>> has the files: >>> >>> dma interrupt rcstat wiphy xmit >>> >>> I'm attaching the output of dmesg right after booting. >>> >>> Couple of other observations... If I rmmod ath9k and then try to >>> modprobe/insmod it again, I get an error that ath9k "failed to >>> initialize device" and "PCI INT A disabled". Sometimes after rebooting >>> and trying to use wlan0 the entire system just locks up. The most >>> recent >>> time this happened, I had just booted up and issued the command >>> "ifconfig wlan0 up". I was going to next issue the command "iwlist >>> wlan0 >>> scan", but the system had already locked up. The only way to recover is >>> to hit the reset button. >> Does the kernel lockup every time the interface is brought up ? >> If not, can you post the kernel log on doing 'ifconfig wlan0 up' ? >> >> Sujith