From: Mattias Nissler <mattias.nissler@gmx.de>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
IvDoorn@gmail.com
Subject: Re: Spammed logs again rt2500pci 2.6.24-rc8
Date: Fri, 18 Jan 2008 11:56:05 +0100 [thread overview]
Message-ID: <1200653765.7492.10.camel@localhost> (raw)
In-Reply-To: <20080117225744.29aa214c@Varda>
Hi,
we currently think this is due to a race condition in the packet queue
code. Ivo is currently reworking the packet queues, which I hope will
resolve this situation.
Mattias
On Thu, 2008-01-17 at 22:57 +0100, Alejandro Riveira Fern=E1ndez wrote:
> Running
>=20
> Linux Varda 2.6.24-rc8 #1 SMP PREEMPT Wed Jan 16 15:09:43 CET 2008 x8=
6_64 GNU/Linux
>=20
> my logs are spmmed with:
>=20
>=20
> [20126.343240] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20126.343242] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20126.848277] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20126.848280] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20126.851693] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20126.851696] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20126.851854] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20126.851856] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20126.852082] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20126.852084] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20126.852224] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20126.852226] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20127.349691] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20127.349694] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20127.352425] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20127.352428] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20127.853345] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20127.853348] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20127.853699] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20127.853701] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20128.858569] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20128.858572] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20131.875550] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20131.875554] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20154.693853] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20154.693856] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20185.527974] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20185.527977] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20189.812334] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20189.812337] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20189.812374] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20189.812376] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20189.812507] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20189.812509] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20189.813100] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20189.813102] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20189.813474] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20189.813476] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20189.813909] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20189.813911] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20212.242858] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20212.242861] Please file bug report to http://rt2x00.serialmonkey.c=
om.
> [20212.243587] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at no=
n-free entry in the non-full queue 1.
> [20212.243589] Please file bug report to http://rt2x00.serialmonkey.c=
om.
>=20
>=20
> As the last time the thing is triggered with a p2p app making a lot o=
f connections (this time not bt but mldonkey)
> Back to top =09
> View user's profile Send private message =09
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wirel=
ess" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Mattias Nissler <mattias.nissler@gmx.de>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
IvDoorn@gmail.com
Subject: Re: Spammed logs again rt2500pci 2.6.24-rc8
Date: Fri, 18 Jan 2008 11:56:05 +0100 [thread overview]
Message-ID: <1200653765.7492.10.camel@localhost> (raw)
In-Reply-To: <20080117225744.29aa214c@Varda>
Hi,
we currently think this is due to a race condition in the packet queue
code. Ivo is currently reworking the packet queues, which I hope will
resolve this situation.
Mattias
On Thu, 2008-01-17 at 22:57 +0100, Alejandro Riveira Fernández wrote:
> Running
>
> Linux Varda 2.6.24-rc8 #1 SMP PREEMPT Wed Jan 16 15:09:43 CET 2008 x86_64 GNU/Linux
>
> my logs are spmmed with:
>
>
> [20126.343240] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20126.343242] Please file bug report to http://rt2x00.serialmonkey.com.
> [20126.848277] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20126.848280] Please file bug report to http://rt2x00.serialmonkey.com.
> [20126.851693] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20126.851696] Please file bug report to http://rt2x00.serialmonkey.com.
> [20126.851854] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20126.851856] Please file bug report to http://rt2x00.serialmonkey.com.
> [20126.852082] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20126.852084] Please file bug report to http://rt2x00.serialmonkey.com.
> [20126.852224] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20126.852226] Please file bug report to http://rt2x00.serialmonkey.com.
> [20127.349691] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20127.349694] Please file bug report to http://rt2x00.serialmonkey.com.
> [20127.352425] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20127.352428] Please file bug report to http://rt2x00.serialmonkey.com.
> [20127.853345] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20127.853348] Please file bug report to http://rt2x00.serialmonkey.com.
> [20127.853699] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20127.853701] Please file bug report to http://rt2x00.serialmonkey.com.
> [20128.858569] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20128.858572] Please file bug report to http://rt2x00.serialmonkey.com.
> [20131.875550] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20131.875554] Please file bug report to http://rt2x00.serialmonkey.com.
> [20154.693853] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20154.693856] Please file bug report to http://rt2x00.serialmonkey.com.
> [20185.527974] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20185.527977] Please file bug report to http://rt2x00.serialmonkey.com.
> [20189.812334] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20189.812337] Please file bug report to http://rt2x00.serialmonkey.com.
> [20189.812374] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20189.812376] Please file bug report to http://rt2x00.serialmonkey.com.
> [20189.812507] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20189.812509] Please file bug report to http://rt2x00.serialmonkey.com.
> [20189.813100] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20189.813102] Please file bug report to http://rt2x00.serialmonkey.com.
> [20189.813474] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20189.813476] Please file bug report to http://rt2x00.serialmonkey.com.
> [20189.813909] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20189.813911] Please file bug report to http://rt2x00.serialmonkey.com.
> [20212.242858] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20212.242861] Please file bug report to http://rt2x00.serialmonkey.com.
> [20212.243587] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
> [20212.243589] Please file bug report to http://rt2x00.serialmonkey.com.
>
>
> As the last time the thing is triggered with a p2p app making a lot of connections (this time not bt but mldonkey)
> Back to top
> View user's profile Send private message
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-01-18 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:57 Spammed logs again rt2500pci 2.6.24-rc8 Alejandro Riveira Fernández
2008-01-18 10:56 ` Mattias Nissler [this message]
2008-01-18 10:56 ` Mattias Nissler
2008-01-18 11:26 ` Alejandro Riveira Fernández
2008-01-18 11:26 ` Alejandro Riveira Fernández
2008-03-25 12:12 ` Spammed logs again rt2500pci 2.6.25-rc6-00268-gd2532dd Alejandro Riveira Fernández
2008-03-25 13:41 ` Ivo van Doorn
2008-03-25 13:46 ` Ivo van Doorn
2008-03-25 15:46 ` Alejandro Riveira Fernández
2008-03-25 15:46 ` Alejandro Riveira Fernández
2008-03-25 15:08 ` Alejandro Riveira Fernández
2008-03-25 15:08 ` Alejandro Riveira Fernández
2008-03-25 15:35 ` Ivo van Doorn
2008-03-25 15:35 ` Ivo van Doorn
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=1200653765.7492.10.camel@localhost \
--to=mattias.nissler@gmx.de \
--cc=IvDoorn@gmail.com \
--cc=ariveira@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.