From: Brian Walker <walkerbm@charter.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] trouble with DWA-552 and ath9k
Date: Tue, 26 Jan 2010 19:52:07 -0500 [thread overview]
Message-ID: <4B5F8E37.4070901@charter.net> (raw)
In-Reply-To: <1264448097.10841.1.camel@mj>
On 01/25/2010 02:34 PM, Pavel Roskin wrote:
> On Mon, 2010-01-25 at 13:47 -0500, Brian Walker wrote:
>
>
>> Any update?
>>
> Please test your card with this patch:
> http://marc.info/?l=linux-wireless&m=126427347119805&w=2
>
> My Ubiquiti SR71-12 is working with it.
>
>
>> I see several new snapshots at
>> http://wireless.kernel.org/download/compat-wireless-2.6/
>>
> That patch has not been committed yet.
>
>
Thanks for the pointer to the patch. I have applied it to the 2010-01-24
version of compat-wireless, installed, and rebooted. Here is what is in
dmesg after booting:
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: UNDEFINED -> AWAKE
ath: serialize_regmode is 0
ath: Eeprom VER: 14, REV: 18
ath: EEPROM regdomain: 0x10
ath: EEPROM indicates we should expect a direct regpair map
ath: Country alpha2 being used: CO
ath: Regpair used: 0x10
ath: tx DMA: 512 buffers 1 desc/buf
ath: tx DMA map: f4c80000 (76320) -> 34c80000 (76320)
ath: beacon DMA: 4 buffers 1 desc/buf
ath: beacon DMA map: f4c3c000 (576) -> 34c3c000 (576)
ath: cachelsz 32 rxbufsize 3872
ath: rx DMA: 512 buffers 1 desc/buf
ath: rx DMA map: f4cc0000 (76320) -> 34cc0000 (76320)
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=0xfa3a0000, 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)
cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
(5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
(5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
then after boot and doing "ifconfig wlan0 up"
ath: Starting driver with initial channel: 2412 MHz
ath: ah->misc_mode 0x4
ath: Attach a VIF of type: 2
ath: ah->misc_mode 0x4
ath: BSS Changed PREAMBLE 0
ath: BSS Changed CTS PROT 0
ath: Marking phy0 as idle
ath: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: RTC stuck in MAC reset
ath: Chip reset failed
ath: Unable to reset channel 4198050593 (2412Mhz) <7>ath: not-idle:
enabling radio
ath: Set channel: 2412 MHz
ath: tx chmask: 1, rx chmask: 1
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Unable to stop TxDMA. Reset HAL!
ath: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: RTC stuck in MAC reset
ath: Chip reset failed
ath: Unable to reset hardware; reset status -22
ath: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff
ath: (2412 MHz) -> (2412 MHz), conf_is_ht40: 0
ath: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: RTC stuck in MAC reset
ath: Chip reset failed
ath: Unable to reset channel (2412 Mhz) reset status -22
ath: Unable to set channel
ath: Configure tx [queue/halq] [0/3], aifs: 2, cw_min: 7, cw_max: 15,
txop: 102
ath: Configure tx [queue/halq] [1/2], aifs: 2, cw_min: 15, cw_max: 31,
txop: 188
ath: Configure tx [queue/halq] [2/1], aifs: 3, cw_min: 31, cw_max:
1023, txop: 0
ath: Configure tx [queue/halq] [3/0], aifs: 7, cw_min: 31, cw_max:
1023, txop: 0
ath: Set HW RX filter: 0x2307
ath: Set HW RX filter: 0x2307
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath: Set HW RX filter: 0x2307
Those type messages repeat over and over after trying "iwlist wlan0
scan". Also, about half the time I boot and try "iwconfig wlan0 up" the
entire system just locks up. Other times the systems locks up (sometimes
hours, sometimes days) later for seemingly no reason. Before adding the
DWA-552 it had uptimes in excess of 100 days. I've taken to blacklisting
the ath9k module unless I am testing a driver fix because this machine
is my main firewall and fileserver.
Brian
next prev parent reply other threads:[~2010-01-27 0:52 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:43 [ath9k-devel] trouble with DWA-552 and ath9k Brian Walker
2009-12-18 3:12 ` Sujith
2009-12-18 3:51 ` Brian Walker
2009-12-18 4:44 ` Sujith
2009-12-18 11:55 ` Brian Walker
2009-12-19 3:05 ` Brian Walker
2009-12-22 4:58 ` Sujith
[not found] ` <4B30D348.3080600@charter.net>
2009-12-22 18:39 ` Brian Walker
2009-12-28 19:22 ` Brian Walker
2009-12-28 20:49 ` Pavel Roskin
2009-12-28 21:06 ` Brian Walker
2009-12-28 21:28 ` Pavel Roskin
2009-12-28 22:54 ` Brian Walker
2009-12-29 15:02 ` Pavel Roskin
2009-12-29 23:23 ` Brian Walker
2009-12-30 6:16 ` Pavel Roskin
2010-01-05 16:49 ` Brian Walker
2010-01-08 4:34 ` Sujith
2010-01-09 15:14 ` Brian Walker
2010-01-09 15:38 ` Pavel Roskin
2010-01-09 19:33 ` Brian Walker
2010-01-10 5:12 ` Sujith
2010-01-11 18:42 ` Brian Walker
2010-01-13 1:18 ` Brian Walker
2010-01-13 8:04 ` Sujith
2010-01-13 15:35 ` Pavel Roskin
2010-01-13 17:28 ` Pavel Roskin
2010-01-14 2:58 ` Brian Walker
2010-01-14 6:15 ` Pavel Roskin
2010-01-14 11:51 ` Brian Walker
2010-01-14 23:13 ` Pavel Roskin
2010-01-15 5:40 ` Pavel Roskin
2010-01-16 16:27 ` Brian Walker
2010-01-20 23:03 ` Pavel Roskin
2010-01-25 18:47 ` Brian Walker
2010-01-25 19:34 ` Pavel Roskin
2010-01-27 0:52 ` Brian Walker [this message]
2010-01-27 23:13 ` Pavel Roskin
2010-01-28 0:36 ` Brian Walker
2010-02-05 19:13 ` Brian Walker
2010-02-05 19:34 ` Pavel Roskin
2010-02-06 0:56 ` Brian Walker
2010-02-06 5:20 ` Pavel Roskin
2010-02-10 1:00 ` Brian Walker
2010-02-10 19:24 ` Pavel Roskin
2010-02-10 19:57 ` Brian Walker
2010-02-20 3:00 ` Brian Walker
2010-02-23 21:30 ` Pavel Roskin
2010-02-24 1:21 ` Brian Walker
2010-02-24 6:09 ` [ath9k-devel] hostapd-0.7-1 failed work with ath9k Zhang Yanfei-B21500
2010-02-24 6:42 ` Pavel Roskin
2010-03-02 10:20 ` yingqiang Ma
2010-03-03 2:01 ` Zhang Yanfei-B21500
2010-02-24 6:40 ` [ath9k-devel] trouble with DWA-552 and ath9k Pavel Roskin
2010-02-24 13:21 ` Brian Walker
2010-02-24 18:09 ` Pavel Roskin
2010-02-24 18:14 ` Pavel Roskin
2010-02-25 18:31 ` Pavel Roskin
2010-02-25 20:34 ` Peter Stuge
2010-02-26 1:10 ` Brian Walker
2010-02-26 23:35 ` Pavel Roskin
2010-03-02 0:48 ` Brian Walker
2010-03-03 4:31 ` Pavel Roskin
2010-03-02 0:55 ` Brian Walker
2010-03-03 4:33 ` Pavel Roskin
2010-03-08 2:20 ` Brian Walker
-- strict thread matches above, loose matches on Subject: below --
2009-12-17 19:52 Brian Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B5F8E37.4070901@charter.net \
--to=walkerbm@charter.net \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.