From: Mohammed Shafi <shafi.wireless@gmail.com>
To: Tony Houghton <h@realh.co.uk>
Cc: Balasubramanian <senthilkumar@atheros.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Jouni Malinen <jmalinen@atheros.com>,
Jonathan Nieder <jrnieder@gmail.com>,
ath9k-devel@lists.ath9k.org,
Vasanthakumar Thiagarajan <vasanth@atheros.com>,
Senthil@venema.h4ckr.net,
Vivek Natarajan <vnatarajan@atheros.com>
Subject: Re: [ath9k-devel] ath9k causes lockups since kernel 2.6.35
Date: Thu, 3 Mar 2011 10:51:15 +0530 [thread overview]
Message-ID: <AANLkTinEA2NVxwWZJME-oChE6OEJc_TSTajMfe7f+3hm@mail.gmail.com> (raw)
In-Reply-To: <20110302163051.425d1419@toddler>
On Wed, Mar 2, 2011 at 10:00 PM, Tony Houghton <h@realh.co.uk> wrote:
> On Mon, 28 Feb 2011 11:06:54 +0530
> Mohammed Shafi <shafi.wireless@gmail.com> wrote:
>
>> On Sun, Feb 27, 2011 at 12:05 AM, Tony Houghton <h@realh.co.uk> wrote:
>> > I tried to reconfigure rsyslog to sync on each message but it
>> > didn't log anything useful :-(.
>>
>> I will try to reproduce here with my platform.
>
> Is this still not reproducible? I'd like to do more to help trace the
> problem but I'm a bit stuck. Is there something I can do to make sure
> all the debug/log messages from ath9k appear on the console?
sudo dmesg -n 8?
>
> I'm using rsyslog ATM, which is Debian's default logger AFAIK, but I'm
> willing to install something different if it will help capture these
> messages.
Tony, it looks like we are not having the card you are using. Any way
I will try to recreate the issue with the AR9285 card I have.
>
next prev parent reply other threads:[~2011-03-03 5:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 18:20 ath9k causes lockups since kernel 2.6.33 Tony Houghton
2011-02-24 20:02 ` ath9k causes lockups since kernel 2.6.35 Jonathan Nieder
2011-02-25 7:51 ` [ath9k-devel] " Mohammed Shafi
2011-02-25 8:44 ` Mohammed Shafi
2011-02-25 14:47 ` Tony Houghton
2011-02-25 16:07 ` Mohammed Shafi
2011-02-25 16:57 ` Tony Houghton
2011-02-26 18:35 ` Tony Houghton
2011-02-28 5:36 ` Mohammed Shafi
2011-03-02 16:30 ` Tony Houghton
2011-03-03 5:21 ` Mohammed Shafi [this message]
2011-03-03 14:31 ` Tony Houghton
2011-03-03 15:57 ` Mohammed Shafi
2011-03-03 19:16 ` Tony Houghton
2011-03-04 15:50 ` Mohammed Shafi
2011-03-06 22:04 ` Tony Houghton
2011-03-03 7:05 ` Vivek Natarajan
2011-02-25 7:57 ` Sedat Dilek
2011-02-25 14:35 ` Tony Houghton
2011-03-14 16:48 ` Could ath9k and rt2800pci bugs be related? Tony Houghton
2011-03-15 7:47 ` Mohammed Shafi
2011-03-15 13:19 ` Tony Houghton
2011-03-15 13:35 ` Mohammed Shafi
2011-03-15 15:17 ` Tony Houghton
2011-03-15 16:17 ` Mohammed Shafi
2011-03-15 17:15 ` Tony Houghton
2011-03-16 5:09 ` Mohammed Shafi
2011-03-15 15:24 ` Tony Houghton
2011-06-10 6:48 ` ath9k causes lockups since kernel 2.6.35 Adrian Chadd
2011-06-13 11:00 ` Stanislaw Gruszka
2011-06-27 10:33 ` Adrian Chadd
[not found] <AANLkTikvcwQx9p1O49DZDJBmWPte9_VVrwJOQgBjPri4@mail.gmail.com>
2011-03-10 11:41 ` [ath9k-devel] " Mohammed Shafi
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=AANLkTinEA2NVxwWZJME-oChE6OEJc_TSTajMfe7f+3hm@mail.gmail.com \
--to=shafi.wireless@gmail.com \
--cc=Senthil@venema.h4ckr.net \
--cc=ath9k-devel@lists.ath9k.org \
--cc=h@realh.co.uk \
--cc=jmalinen@atheros.com \
--cc=jrnieder@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=senthilkumar@atheros.com \
--cc=vasanth@atheros.com \
--cc=vnatarajan@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;
as well as URLs for NNTP newsgroup(s).