From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Sergei Antonov <saproj@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: USB rt2x00 driver regression
Date: Fri, 31 Jan 2014 13:16:22 +0100 [thread overview]
Message-ID: <20140131121621.GA19138@redhat.com> (raw)
In-Reply-To: <CABikg9w7JjdeD7EU1cw9A-aARddDigDZzaxoL5yk6YeFtJB4hw@mail.gmail.com>
On Wed, Jan 29, 2014 at 06:45:31PM +0100, Sergei Antonov wrote:
> > On older kernels "TX status timeout" messages were only enabled if
> > kernel was compiled with CONFIG_RT2X00_DEBUG option , so perhaps
> > that is the reason why you did not see them on older kernel with
> > older firmware. But if really TX status timeouts start to happen after
> > firmware update, we should fix our driver to better talk to the
> > firmware, though I do not have idea how. If not, we should probably
> > disable those messages in non-debug mode as it was on old kernels.
>
> Yes, it could have been due to CONFIG_RT2X00_DEBUG=n that I didn't
> have warnings.
I will move those annoying messages back to debug level, they are
printed by default by mistake anyway.
> The AP with which I have the warnings is another Linux computer with
> hostapd-2.0. Can it be the cause of this "TX status" thing?
It can be that AP does not ACK some frames for some reason and we see
those warnings. Could you please provide me details about that AP (what
H/W and driver is used and hostapd config file), I will see if I could
reproduce those messages locally.
Stanislaw
next prev parent reply other threads:[~2014-01-31 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 18:28 USB rt2x00 driver regression Sergei Antonov
2014-01-17 10:06 ` Stanislaw Gruszka
2014-01-19 10:57 ` Sergei Antonov
2014-01-19 12:19 ` Igor Gnatenko
2014-01-19 15:34 ` Sergei Antonov
2014-01-19 18:20 ` Gabor Juhos
2014-01-20 11:20 ` Sergei Antonov
2014-01-20 18:50 ` Stanislaw Gruszka
2014-01-22 11:27 ` Sergei Antonov
2014-01-22 16:25 ` Stanislaw Gruszka
2014-01-29 17:45 ` Sergei Antonov
2014-01-31 12:16 ` Stanislaw Gruszka [this message]
2014-02-07 10:11 ` Sergei Antonov
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=20140131121621.GA19138@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=saproj@gmail.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).