From: Mohammed Shafi <shafi.ath9k@gmail.com>
To: Tony Houghton <h@realh.co.uk>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
ath9k-devel@lists.ath9k.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Jouni Malinen <jmalinen@atheros.com>,
Senthil Balasubramanian <senthilkumar@atheros.com>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>,
Vivek Natarajan <vnatarajan@atheros.com>
Subject: Re: [ath9k-devel] ath9k causes lockups since kernel 2.6.35
Date: Fri, 25 Feb 2011 21:37:25 +0530 [thread overview]
Message-ID: <AANLkTinu9NgnZZmieh2PU6e-iShOkapV9kcVe8YGtPHG@mail.gmail.com> (raw)
In-Reply-To: <20110225144718.63550601@realh.co.uk>
On Fri, Feb 25, 2011 at 8:17 PM, Tony Houghton <h@realh.co.uk> wrote:
> On Fri, 25 Feb 2011 13:21:32 +0530
> Mohammed Shafi <shafi.ath9k@gmail.com> wrote:
>
>> > Tony Houghton wrote:
>> >
>> >> With 2.6.37 I can not use suspend on my Compaq/HP 311c (Intel Atom
>> >> N270/NVidia Ion LE). Originally the machine just kept locking up without
>> >> even blanking the display when I tried to suspend (using the GNOME menu
>> >> or by shutting the lid).
>
> [Snip]
>
> The above was from my original message before I worked out that the
> problem was in the wireless because disabling and reneabling wireless,
> killing the ath9k module etc, would often produce similar crashes, but
> suspend seems to do it more consistently.
Ok.
>
>> >> booting, but it's always a complete lock-up ie the keyboard is
>> >> completely responsive, including caps lock, the mouse won't move if the
>
> I meant *un*responsive of course!
>
>> >> I haven't tried looking in logs because the crashes are so severe I
>> >> don't think they'd be able to record anything useful.
Can you please get those messages with net console ?
>
> If I enable debugging is there a way to get it to sync to disc after
> every message? I think the developers are going to need at least that
> information to be able to track this down.
Yes sure, that could narrow down the issue.
>
>> is this issue still reproducible ?
>
> Yes :-(.
It would be highly helpful if this issue is reproducible in the latest
wireless testing or compat wireless. It will help us to fix it cleanly
>
>> Apart from this reporting I have not seen any other issues for AR9285.
>
> Strange, isn't it. I can't be the only person trying to use a recent
> version of Linux on one of these netbooks, but I couldn't find any
> similar complaints on Google. Maybe mine has an obscure fault which is
> only triggered by a feature supported in the newer kernels.
>
also need to rule out its a platform independent issue.
next prev parent reply other threads:[~2011-02-25 16:07 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 [this message]
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
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=AANLkTinu9NgnZZmieh2PU6e-iShOkapV9kcVe8YGtPHG@mail.gmail.com \
--to=shafi.ath9k@gmail.com \
--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).