From: Paul Bolle <pebolle@tiscali.nl>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlegacy: print how long queue was actually stuck
Date: Mon, 02 Jul 2012 11:32:43 +0200 [thread overview]
Message-ID: <1341221563.1911.141.camel@x61.thuisdomein> (raw)
In-Reply-To: <20120702090602.GA8286@redhat.com>
On Mon, 2012-07-02 at 11:06 +0200, Stanislaw Gruszka wrote:
> On Sat, Jun 30, 2012 at 03:20:06PM +0200, Paul Bolle wrote:
> For some reason we are not able to authenticate, what itself is a
> problem. Maybe this is wrong key offset problem and that will
> be fixed by Emmanuel patch.
Which I can only try if we fix the small problem you mentioned in your
comment on Emmanuel's patch (reference
<20120702082653.GA2479@redhat.com>, not yet archived on lkml.org), can't
I?
> Regarding "Queue 2 stuck", there is another fix in iwlwifi that
> did not make to iwlegacy, which perhaps could help. If not here
> then maybe on suspend.
>
> commit 342bbf3fee2fa9a18147e74b2e3c4229a4564912
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Sun Mar 4 08:50:46 2012 -0800
>
> iwlwifi: always monitor for stuck queues
>
> I'm attaching iwlegacy version of it.
Thanks, I'll try it. The explanation of the iwlwifi commit makes a lot
of sense: it seems to match the events found in the logs of this laptop.
That's encouraging. Should I report whether the iwlegacy version works
or not?
> > 2) It's always "Queue 2" that's stuck. What does that queue do?
>
> It's TX queue, probably one used for default traffic i.e. for Best
> Effort category (others are Video, Voice and Background).
I see.
Any thoughts on my patch (ie, the patch that is actually the subject of
this thread?
Paul Bolle
next prev parent reply other threads:[~2012-07-02 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 8:36 [PATCH] iwlegacy: print how long queue was actually stuck Paul Bolle
2012-06-30 13:20 ` Paul Bolle
[not found] ` <1341062406.1911.76.camel-uMdlDhfIn7prKue/0VVhAg@public.gmane.org>
2012-06-30 18:18 ` Emmanuel Grumbach
2012-06-30 19:11 ` Paul Bolle
2012-07-02 9:06 ` Stanislaw Gruszka
2012-07-02 9:32 ` Paul Bolle [this message]
[not found] ` <1341221563.1911.141.camel-uMdlDhfIn7prKue/0VVhAg@public.gmane.org>
2012-07-02 9:39 ` Stanislaw Gruszka
2012-07-02 9:53 ` Paul Bolle
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=1341221563.1911.141.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sgruszka@redhat.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