From: Russell Senior <seniorr@aracnet.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Adrian Chadd <adrian@freebsd.org>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] kernel panic on MIPS + ath5k + Wistron CM9 radio
Date: Wed, 04 May 2011 12:55:41 -0700 [thread overview]
Message-ID: <861v0e8cle.fsf@coulee.tdb.com> (raw)
In-Reply-To: <4DC05536.4010303@openwrt.org> (Felix Fietkau's message of "Tue\, 03 May 2011 21\:19\:18 +0200")
>>>>> "Felix" == Felix Fietkau <nbd@openwrt.org> writes:
>> Well, I see the same on FreeBSD/MIPS whenever an Atheros device is
>> fondled incorrectly. Either because the chip isn't yet fully awake
>> or the register plainly doesn't exist.
>>
>> See if you can add some debugging in ath5k_hw_reset_tx_queue() to
>> see which register is being read/written before the PCI bus error
>> occurs.
Felix> If I read the trace correctly, the accessed register is 0x111c,
Felix> which is AR5K_QUEUE_DFS_MISC(7). If I remember correctly, queue
Felix> 7 is the beacon queue. Access to this register should never
Felix> fail unless the hardware is in sleep mode, or there is some
Felix> other PCI related issue. Unfortunately, this issue might be
Felix> caused by something entirely different that is not visible in
Felix> the stack trace. I have observed that messing up the internal
Felix> state of a PCI card can trigger an error that only shows up
Felix> much later and thus can only be found by doing a thorough code
Felix> review or by analyzing PCI traces.
I wonder what is special about MIPS (relative to x86, where I don't
see the panics).
--
Russell Senior ``I have nine fingers; you have ten.''
seniorr@aracnet.com
next prev parent reply other threads:[~2011-05-04 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 19:39 kernel panic on MIPS + ath5k + Wistron CM9 radio Russell Senior
2011-05-03 6:18 ` Adrian Chadd
2011-05-03 6:56 ` [ath5k-devel] " Peizhao Hu
2011-05-03 19:19 ` Felix Fietkau
2011-05-04 19:55 ` Russell Senior [this message]
2011-05-06 1:57 ` Peizhao Hu
2011-05-04 14:39 ` Russell Senior
2011-05-04 14:47 ` Felix Fietkau
[not found] ` <86liyjjo0a.fsf@coulee.tdb.com>
2011-05-31 17:30 ` Russell Senior
2011-05-31 18:16 ` Sedat Dilek
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=861v0e8cle.fsf@coulee.tdb.com \
--to=seniorr@aracnet.com \
--cc=adrian@freebsd.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).