From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Walker Date: Sun, 07 Mar 2010 21:20:39 -0500 Subject: [ath9k-devel] trouble with DWA-552 and ath9k In-Reply-To: <1267590819.2172.9.camel@mj> References: <4B2A5FA8.8060905@charter.net> <19270.46529.788691.185819@gargle.gargle.HOWL> <4B489D63.9030305@charter.net> <19273.25018.877385.529083@gargle.gargle.HOWL> <4B4D1F4F.7090106@charter.net> <19277.32410.462158.258222@gargle.gargle.HOWL> <4B51E8FC.9030304@charter.net> <1264028629.10023.26.camel@mj> <4B5DE724.7000002@charter.net> <1264448097.10841.1.camel@mj> <4B5F8E37.4070901@charter.net> <1264634005.19648.59.camel@mj> <4B6C6DC9.9070001@charter.net> <1265398464.3576.7.camel@mj> <4B6CBE50.2050406@charter.net> <1265433611.3406.10.camel@ct> <4B720519.4020605@charter.net> <1265829871.31983.20.camel@mj> <4B7F505D.3030006@charter.net> <1266960630.16604.74.camel@mj> <4B847F26.1060902@charter.net> <1266993626.12741.4.camel@ct> <4B8527E8.2080808@charter.net> <1267034980.9225.36.camel@mj> <1267035256.9225.37.camel@mj> <1267122698.7508.20.camel@mj> <4B871F75.5050608@charter.net> <1267227305.2835.1.camel@mj> <4B8C6217.5020404@charter.net> <1267590819.2172.9.camel@mj> Message-ID: <4B945EF7.6040900@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 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