public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
	openwrt-devel@lists.openwrt.org
Cc: Marek Lindner <lindner_marek@yahoo.de>,
	sven@narfation.org, Gabor Juhos <juhosg@openwrt.org>
Subject: AR9330 hornet board stops beaconing after a few days (0xdeadbeef)
Date: Mon, 13 Aug 2012 18:53:40 +0200	[thread overview]
Message-ID: <20120813165340.GA10044@pandem0nium> (raw)

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

Hello ath9k fellows,

I'm using a pretty new AR9330 rev1/hornet based AP at home. After some
days (5 days this time), it suddenly stops beaconing. dmesg shows nothing,
hostapd is still running, but what I can see is:

cat /sys/kernel/debug/ieee80211/phy0/ath9k/regdump
0x000000 0xdeadbeef
0x000004 0xdeadbeef
0x000008 0xdeadbeef
0x00000c 0xdeadbeef
0x000010 0xdeadbeef
0x000014 0xdeadbeef
[...]
0x001ff4 0xdeadbeef
0x001ff8 0xdeadbeef
0x001ffc 0xdeadbeef
0x002000 0xbadc0ffe
0x002004 0xbadc0ffe
0x002008 0xbadc0ffe
0x00200c 0xbadc0ffe
0x002010 0xbadc0ffe
[...]
0x003ff0 0xbadc0ffe
0x003ff4 0xbadc0ffe
0x003ff8 0xbadc0ffe
0x003ffc 0xbadc0ffe
0x004000 0x00000000
0x004004 0x0102420b
0x004008 0x00000000
0x00400c 0x00000000
[...] (some more sane looking registers here, and then zeros)
0x004ef8 0x00000000
0x004efc 0x00000000
0x004f00 0xdeadbeef
0x004f04 0xdeadbeef
0x004f08 0xdeadbeef
[...] (and the rest is mostly deadbeef)

Also /sys/kernel/debug/ieee80211/phy0/ath9k/dma shows a lot of deadbeef.

I'm using OpenWRT r31729, a single AP bridged with Ethernet. It is normal
home usage, i.e. a few laptops and android phones doing not so much traffic.
The box stops working out of the blue after a few days without any outside
event (at least none I'm aware of). Sometimes this problem does not occur for
2 weeks, sometimes after 12 hours, I couldn't find an easy way to reproduce it
yet. As said, the box is perfectly reachable via SSH, no errors in syslog or
anywhere else. Also an ifconfig wlan0 down and up seems to fix the problem.

I'll try a new firmware with more debugging turned on, but have any of you
seen this problem? Any input would be very much appreciated. I have a complete
/sys/kernel/debug log from a working and a non-working system, along with
more info (brctl, ip config, etc) which I'd love to share with anyone interested
- it's too much to post on a public ml.

Thank you very much
Cheers,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2012-08-13 17:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 16:53 Simon Wunderlich [this message]
2012-08-19 22:04 ` AR9330 hornet board stops beaconing after a few days (0xdeadbeef) Simon Wunderlich
2012-08-22  5:20   ` Mohammed Shafi
2012-08-22 18:57     ` Adrian Chadd
2012-08-23  9:28       ` Simon Wunderlich
2012-08-23 17:10         ` Gabor Juhos
2012-08-23 19:26           ` Adrian Chadd
2012-08-23 14:59     ` Mohammed Shafi
2012-08-23 15:19       ` Sven Eckelmann
2012-08-23 15:27         ` Sven Eckelmann
2012-09-02 20:01       ` Simon Wunderlich
2012-09-03 13:53         ` Mohammed Shafi
2012-09-03 14:34           ` Sven Eckelmann
2012-09-04 17:12           ` Simon Wunderlich
2012-09-05  5:12             ` Mohammed Shafi
2012-09-05 14:08               ` Adrian Chadd
2012-09-05 14:20                 ` Sven Eckelmann
2012-09-13 16:51                   ` Simon Wunderlich
2012-09-13 16:59                     ` Adrian Chadd
2012-09-13 17:55                     ` [OpenWrt-Devel] " Felix Fietkau
2012-09-14  9:47                       ` [RFC] ath9k: Work around complete stuck of hw Sven Eckelmann
2012-09-14 11:33                         ` Felix Fietkau
2012-09-23 10:04                           ` Sven Eckelmann
2013-11-20 20:57   ` [OpenWrt-Devel] AR9330 hornet board stops beaconing after a few days (0xdeadbeef) Bastian Bittorf
2013-11-20 21:00     ` Sven Eckelmann

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=20120813165340.GA10044@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=juhosg@openwrt.org \
    --cc=lindner_marek@yahoo.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=sven@narfation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox