From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Bob Copeland <bcopeland@gmail.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Soeren Sonnenburg <kernel@nn7.de>,
ath5k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org,
linville@tuxdriver.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [ath5k-devel] ath5k_pci: gain calibration timeout / unable to reset hardware -11
Date: Tue, 23 Dec 2008 00:37:05 +0200 [thread overview]
Message-ID: <1229985425.17866.0.camel@maxim-laptop> (raw)
In-Reply-To: <b6c5339f0812221348o411c4fabse2d0138acfb4f87f@mail.gmail.com>
On Mon, 2008-12-22 at 16:48 -0500, Bob Copeland wrote:
> On Mon, Dec 22, 2008 at 4:39 PM, Jiri Slaby <jirislaby@gmail.com> wrote:
> >>
> >> Does the _HW lockup_ happen even with 2.6.28? The lockup should be gone there
> >> (with the messages still present).
> >
> > I see Bob already replied, ignore me, he knows better.
>
> I thought Felix's patch had gone into .28, but in fact it hasn't.
> We should probably get it in or queue it for .28.1 -- it's a two
> liner that will fix a lot of people's setups.
>
> John, if you're reading, that's 23c401574b16cb2b6d2231ba405ebf85b8c87de5
> in wireless-testing.
>
> The lockup can still occur, but it's a lot less frequent with his patch.
>
Happens about 1 in 10 times on resume from ram.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2008-12-22 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 5:31 Soeren Sonnenburg
2008-12-22 20:53 ` Bob Copeland
2008-12-23 8:42 ` Soeren Sonnenburg
2008-12-22 20:58 ` Andrew Morton
2008-12-22 21:37 ` Jiri Slaby
2008-12-22 21:39 ` Jiri Slaby
2008-12-22 21:48 ` [ath5k-devel] " Bob Copeland
2008-12-22 22:37 ` Maxim Levitsky [this message]
2008-12-22 22:38 ` Nick Kossifidis
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=1229985425.17866.0.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=bcopeland@gmail.com \
--cc=jirislaby@gmail.com \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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
all inboxes | Powered by JetHome®