From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR5008 hanging computer
Date: Thu, 11 Mar 2010 03:01:16 -0500 [thread overview]
Message-ID: <1268294476.4089.15.camel@mj> (raw)
In-Reply-To: <167ae39b1002222302w715963f2m8efd7d27a37a8f39@mail.gmail.com>
On Tue, 2010-02-23 at 01:02 -0600, James Grossmann wrote:
> > Here is a dmesg containing a hang, the dmesg even notes that there was
> > a soft lockup.
> > I hope this helps, thanks in advance!
Sorry for delay.
Assuming the the EDX register holds the chip register number number, it
looks like a CPU lockup when AR_ISR_RAC is read in ath9k_hw_getisr(). I
have no idea how to work it around. Maybe somebody with access to
Atheros specifications could help?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-03-11 8:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 15:25 [ath9k-devel] AR5008 hanging computer James Grossmann
2010-02-12 22:53 ` Pavel Roskin
2010-02-12 23:35 ` James Grossmann
2010-02-12 23:42 ` hong zhang
2010-02-15 7:03 ` Pavel Roskin
[not found] ` <167ae39b1002152030s170128a0j362e7e9c61a4af42@mail.gmail.com>
[not found] ` <1266296860.17808.2.camel@mj>
2010-02-16 23:54 ` James Grossmann
2010-02-17 17:47 ` Pavel Roskin
2010-02-17 17:56 ` hong zhang
2010-02-17 18:15 ` Pavel Roskin
2010-02-18 12:58 ` [ath9k-devel] 802.11n in Ad-hoc mode Jónatan Muñoz
2010-02-24 7:02 ` Zhang Yanfei-B21500
2010-02-24 16:35 ` Jónatan Muñoz
2010-02-23 6:45 ` [ath9k-devel] AR5008 hanging computer James Grossmann
2010-02-23 7:02 ` James Grossmann
2010-03-11 8:01 ` Pavel Roskin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-18 20:31 Mark Sutton
2010-02-18 21:58 ` Mark Sutton
2010-02-19 1:36 ` Pavel Roskin
2010-03-05 23:04 ` Mark Sutton
2010-03-11 7:56 ` Pavel Roskin
2010-03-11 10:38 ` Peter Stuge
2010-04-17 17:49 ` Tomi Orava
2010-02-21 8:31 ` Tomi Orava
2010-02-22 18:02 ` Luis R. Rodriguez
2010-02-22 18:24 ` Tomi Orava
2010-02-22 18:34 ` Luis R. Rodriguez
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=1268294476.4089.15.camel@mj \
--to=proski@gnu.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.