From: Karl Hiramoto <karl@hiramoto.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] hostapd not sending beacons, and no traffic.
Date: Fri, 22 May 2009 17:38:04 +0200 [thread overview]
Message-ID: <4A16C6DC.7070502@hiramoto.org> (raw)
In-Reply-To: <4A16AD12.2020200@hiramoto.org>
Karl Hiramoto wrote:
> more info on this enabling debug in ath9k
>
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: receive FIFO overrun interrupt
> ath9k: 0xf0010071 => 0x10000
> ath9k: disable IER
> ath9k: new IMR 0x10000
> ath9k: 0x10000 => 0xf0010071
> ath9k: new IMR 0x918104b4
> ath9k: enable IER
> ath9k: AR_IMR 0x918104b4 IER 0x1
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
>
>
Some more info. If i rate limit the interface, this bug never occurs.
tc qdisc add dev wlan0_0 root handle 1: cbq avpkt 1000 bandwidth 20mbit
If i restart hostapd, the interface comes back OK.. Or anything that
calls ath_reset() will make it come back.
Reproducing this downloading a http large file, without QOS it's always
reproduceable. Usually It occurs before 2MB is downloaded.
This is on a 266 mhz IXP425. So maybee some kind of race happening here..
--
Karl
WARNING: multiple messages have this Message-ID (diff)
From: Karl Hiramoto <karl@hiramoto.org>
To: hostap@lists.shmoo.com,
linux-wireless <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [ath9k-devel] hostapd not sending beacons, and no traffic.
Date: Fri, 22 May 2009 17:38:04 +0200 [thread overview]
Message-ID: <4A16C6DC.7070502@hiramoto.org> (raw)
In-Reply-To: <4A16AD12.2020200@hiramoto.org>
Karl Hiramoto wrote:
> more info on this enabling debug in ath9k
>
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: receive FIFO overrun interrupt
> ath9k: 0xf0010071 => 0x10000
> ath9k: disable IER
> ath9k: new IMR 0x10000
> ath9k: 0x10000 => 0xf0010071
> ath9k: new IMR 0x918104b4
> ath9k: enable IER
> ath9k: AR_IMR 0x918104b4 IER 0x1
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
> ath9k: AR_INTR_SYNC_LOCAL_TIMEOUT
>
>
Some more info. If i rate limit the interface, this bug never occurs.
tc qdisc add dev wlan0_0 root handle 1: cbq avpkt 1000 bandwidth 20mbit
If i restart hostapd, the interface comes back OK.. Or anything that
calls ath_reset() will make it come back.
Reproducing this downloading a http large file, without QOS it's always
reproduceable. Usually It occurs before 2MB is downloaded.
This is on a 266 mhz IXP425. So maybee some kind of race happening here..
--
Karl
next prev parent reply other threads:[~2009-05-22 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 11:24 [ath9k-devel] hostapd not sending beacons, and no traffic Karl Hiramoto
2009-05-22 11:24 ` Karl Hiramoto
2009-05-22 13:48 ` [ath9k-devel] " Karl Hiramoto
2009-05-22 13:48 ` Karl Hiramoto
2009-05-22 15:38 ` Karl Hiramoto [this message]
2009-05-22 15:38 ` Karl Hiramoto
2009-05-22 18:06 ` Karl Hiramoto
2009-05-22 19:20 ` Karl Hiramoto
2009-05-22 19:20 ` Karl Hiramoto
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=4A16C6DC.7070502@hiramoto.org \
--to=karl@hiramoto.org \
--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.