From: Tim Blechmann <tim@klingt.org>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
rjw@sisk.pl, IvDoorn@gmail.com, linville@tuxdriver.com,
linux-wireless@vger.kernel.org
Subject: Re: regression: rt2561 frequent "Arrived at non-free entry" errors in 2.6.32
Date: Mon, 07 Dec 2009 10:31:45 +0100 [thread overview]
Message-ID: <4B1CCB81.5060104@klingt.org> (raw)
In-Reply-To: <4B1BB44E.90706@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
On 12/06/2009 02:40 PM, Gertjan van Wingerde wrote:
> On 12/05/09 00:32, Andi Kleen wrote:
>> [Rafael, something for your regression list]
>>
>> I upgraded a system which was running 2.6.30 to 2.6.32.
>> It has a
>>
>> 06:02.0 Network controller: RaLink RT2561/RT61 802.11g PCI
>>
>> wireless PCI card. Now regularly even under moderate traffic
>> I see messages like
>>
>> phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
>> Please file bug report to http://rt2x00.serialmonkey.com.
>>
>> and loss of connectivity, often until the wireless connection
>> is restarted. This wasn't the case in 2.6.30, there the driver
>> ran stable without any problems. The problem currently
>> happens every few minutes.
>>
>
> Andi, Tim,
>
> Both of you have reported this problem on 2.6.32.
>
> In the past this always has occurred due to queue locking problems. This led me
> to audit the queue locking code, and that certainly looked suspicious to me.
>
> Would you be able to test whether the attached test patch fixes the problem for
> you. The patch basically applies proper queue locking to the code, although in
> a very course manner. The patch is relative to 2.6.32.
>
> Note: I am not 100% sure that this is where the problem is, but at least the test
> patch should confirm whether I am searching in the right direction.
the patch didn't cleanly apply to v2.6.32 and the patched kernel didn't
boot ... which tree should it be applied on?
tim
--
tim@klingt.org
http://tim.klingt.org
Im übrigen ist es gescheiter, sich warm zuzudecken als sich zu
betrinken.
Werner Schwab
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-12-07 9:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 23:32 regression: rt2561 frequent "Arrived at non-free entry" errors in 2.6.32 Andi Kleen
2009-12-06 13:40 ` Gertjan van Wingerde
2009-12-06 17:04 ` Andi Kleen
2009-12-06 17:20 ` Johannes Berg
2009-12-06 17:32 ` Andi Kleen
2009-12-07 9:31 ` Tim Blechmann [this message]
2009-12-07 21:58 ` Gertjan van Wingerde
2009-12-09 22:59 ` Tim Blechmann
2009-12-09 23:23 ` Gertjan van Wingerde
2009-12-09 23:49 ` Tim Blechmann
2009-12-07 23:06 ` Stefan Lippers-Hollmann
2009-12-08 9:57 ` Andi Kleen
2009-12-08 10:19 ` Gertjan van Wingerde
2009-12-08 21:42 ` Gertjan van Wingerde
2009-12-08 21:44 ` Johannes Berg
2009-12-08 21:56 ` Gertjan van Wingerde
2009-12-08 22:00 ` Johannes Berg
2009-12-08 22:49 ` Gertjan van Wingerde
2009-12-08 22:39 ` Stefan Lippers-Hollmann
2009-12-08 22:40 ` Johannes Berg
2009-12-08 22:44 ` Gertjan van Wingerde
2009-12-08 23:53 ` Stefan Lippers-Hollmann
2009-12-09 6:58 ` Gertjan van Wingerde
2009-12-09 8:24 ` Johannes Berg
2009-12-10 0:46 ` Stefan Lippers-Hollmann
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=4B1CCB81.5060104@klingt.org \
--to=tim@klingt.org \
--cc=IvDoorn@gmail.com \
--cc=andi@firstfloor.org \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
/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).