mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernie Innocenti <bernie@codewiz.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: ath9k-devel@venema.h4ckr.net, lkml <linux-kernel@vger.kernel.org>,
	Danny Clark <dclark@fsf.org>
Subject: ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
Date: Thu, 12 Nov 2009 16:16:45 -0500	[thread overview]
Message-ID: <1258060605.2953.1029.camel@giskard> (raw)

I've recently replaced the built-in Intel 5300 AGN of my Lenovo X200s
with an Atheros AR5008 express card. The operation requires a hacked
BIOS with no hw whitelist check--Thanks for the DRM, Lenovo).

The ath9k driver works great, but occasionally the interface
disassociates spontaneously and won't get back to work until I manually
unload and reload the ath9k module. It's hard to reproduce, but seems to
happen more frequently with some access points.

I'm seeing it both in Ubuntu Karmic (linux-image_2.6.31.14.48) and
Fedora Rawhide (kernel-2.6.31.5-127).

Dmesg contains:

[46623.757586] wlan1: associated
[47222.920159] wlan1: no probe response from AP 00:14:a8:53:3c:80 - disassociating
[47223.063855] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[47224.042616] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020

lspci -vv says:

03:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
	Subsystem: Atheros Communications Inc. Device 0032
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at f2500000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ath9k
	Kernel modules: ath9k

Best regards,

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/


                 reply	other threads:[~2009-11-12 21:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1258060605.2953.1029.camel@giskard \
    --to=bernie@codewiz.org \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=dclark@fsf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®