From: Brian Walker <walkerbm@charter.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] trouble with DWA-552 and ath9k
Date: Sun, 07 Mar 2010 21:20:39 -0500 [thread overview]
Message-ID: <4B945EF7.6040900@charter.net> (raw)
In-Reply-To: <1267590819.2172.9.camel@mj>
On 03/02/2010 11:33 PM, Pavel Roskin wrote:
> On Mon, 2010-03-01 at 19:55 -0500, Brian Walker wrote:
>
>
>> Just used setpci -v -d *:* latency_timer=b0 to set the latency of all
>> devices to 176, did a modprobe ath9k and an ifconfig wlan0 up. System
>> didn't crash, but still getting:
>>
>> 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
>>
> I'm afraid the only sure way to set PCI latency is from BIOS.
>
>
My motherboard is a quite old (~11 years) Acer AX63 Pro. It does not
have any options in the bios to set the PCI latency. I am still
experiencing the following errors in my kernel logs:
Generic kernel compatibility enabled based on linux-next next-20100113
cfg80211: Calling CRDA to update world regulatory domain
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)
PCI: setting IRQ 5 as level-triggered
ath9k 0000:00:0a.0: found PCI INT A -> 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'
cfg80211: Calling CRDA for country: CO
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
egistered led device: ath9k-phy0::rx
phy0: Atheros AR9280 Rev:2 mem=0xfae00000, irq=5
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)
ath: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: Chip reset failed
ath: Unable to reset channel (2412 MHz), reset status -22
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: 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: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: Chip reset failed
ath: Unable to reset channel (2412 MHz), reset status -22
ath: Unable to set channel
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ath: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: Chip reset failed
ath: Unable to reset channel (2412 MHz), reset status -22
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: 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: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 !=
0x00000000
ath: Chip reset failed
ath: Unable to reset channel (2412 MHz), reset status -22
ath: Unable to set channel
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: Chip reset failed
ath: Unable to reset hardware; reset status -22
Since this appears to work for others with kernel
2.6.30.10-105.fc11.i686.PAE and wireless snapshot
compat-wireless-2010-03-07 I can only come to the conclusion that either
this card is incompatible with my motherboard or has a hardware problem.
Caveat emptor I suppose? As such, I'd recommend staying away from the A2
version of the DWA-552. Actually, I suggest staying away from all cards
from companies that reuse the same model number for cards with
completely different wireless chipsets.
Brian
next prev parent reply other threads:[~2010-03-08 2:20 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
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 [this message]
-- 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=4B945EF7.6040900@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.