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
El Fri, 18 Jan 2008 11:56:05 +0100
Mattias Nissler <[email protected]> escribi=C3=B3:
> Hi,
>=20
> we currently think this is due to a race condition in the packet queu=
e
> code. Ivo is currently reworking the packet queues, which I hope will
> resolve this situation.
Thanks for the quick answer.=20
>=20
> Mattias
Regards;
Alejandro
>=20
> On Thu, 2008-01-17 at 22:57 +0100, Alejandro Riveira Fern=C3=A1ndez w=
rote:
> > Running
> >=20
> > Linux Varda 2.6.24-rc8 #1 SMP PREEMPT Wed Jan 16 15:09:43 CET 2008 =
x86_64 GNU/Linux
> >=20
> > my logs are spmmed with:
> >=20
> >=20
> > [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=
=2Ecom.
> > [20126.848277] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at =
non-free entry in the non-full queue 1.
>
>=20
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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
> You mean http://rt2x00.serialmonkey.com/phpBB2/index.php?
> 'ignored' is not the right word, more likely overlooked.
> There are quite a lot of messages and I don't always have time to answer them all.
> So there is no need to be upset about such thing, simply posting a reminder is usually
> enough to make it noticed by me...
I just checked the forums and apparently you mean that 8 replies to your topic including the
answer about "it has been fixed" in 2.1.0 counts as 'ignored'...
For reference:
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4512&highlight=
and yes the following topic was unanswered
http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4572&highlight=
but that topic is a duplicate of your fist topic, and I am not responding to forum spammers...
> > (Someone may want to change the web forums pointer in the logs to
> > the linux-wireless mailing list)
>
> What pointer? And rt2400-devel is the mailinglist for rt2x00...
> The MAINTAINERS file in the kernel tree indicates 2 mailinglists for rt2x00:
> [email protected]
> [email protected]
>
> Ivo
>
On Tuesday 25 March 2008, Alejandro Riveira Fern=C3=A1ndez wrote:
> El Tue, 25 Mar 2008 14:41:22 +0100
> Ivo van Doorn <[email protected]> escribi=C3=B3:
>=20
> > Hi,
> >=20
> > > Linux Varda 2.6.25-rc6-00268-gd2532dd #1 SMP PREEMPT Mon Mar 24 =
14:44:13 CET
> > > 2008 x86_64 GNU/Linux
> > >=20
> > >=20
> > > As the last time the thing is triggered with a p2p app making a =
lot of
> > > connections deluge
> > > =20
> > > My logs are spammed with the same msgs as other reports.
> > > If you need more info just ask.
> >=20
> > This issue has been resolved for 2.6.26. The fix for this bug is of=
such a scale
> > that it could not easily be merged for 2.6.25.
> >=20
> > > PS: i will not bother to make a report in the web forums becouse=
the last time
> > > i was ignored.
> >=20
> > You mean http://rt2x00.serialmonkey.com/phpBB2/index.php?
> > 'ignored' is not the right word, more likely overlooked.
>=20
> Fair enough; english is not my mother tongue so maybe i sounded
> harsher than intended. If that's the case my apologies
Ok.
> > There are quite a lot of messages and I don't always have time to a=
nswer them all.
> > So there is no need to be upset about such thing, simply posting a =
reminder is usually
> > enough to make it noticed by me...
> >=20
> > > (Someone may want to change the web forums pointer in the logs to=
=20
> > > the linux-wireless mailing list)
> >=20
> > What pointer? And rt2400-devel is the mailinglist for rt2x00...
> > The MAINTAINERS file in the kernel tree indicates 2 mailinglists fo=
r rt2x00:
> > [email protected]
> > [email protected]
>=20
> Well my opinion is that instead of the webpage the mailing list shou=
ld be the
> one being logged. Something like this (maybe use another define becou=
se
> DRV_PROJECT may be used elsewhere i havn't checked):
Well DRV_PROJECT is the link to the website, that contains more informa=
tion
about the project. When people want to report bugs they can choose to
use the bugzilla, forum or mailinglist.
So I don't see a big point in replacing the link.
Ivo
Running
Linux Varda 2.6.25-rc6-00268-gd2532dd #1 SMP PREEMPT Mon Mar 24 14:44:13 CET
2008 x86_64 GNU/Linux
As the last time the thing is triggered with a p2p app making a lot of
connections deluge
My logs are spammed with the same msgs as other reports.
If you need more info just ask.
PS: i will not bother to make a report in the web forums becouse the last time
i was ignored. (Someone may want to change the web forums pointer in the logs to
the linux-wireless mailing list)
[75175.740835] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75175.740838] Please file bug report to http://rt2x00.serialmonkey.com.
[75175.743362] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75175.743362] Please file bug report to http://rt2x00.serialmonkey.com.
[75179.886171] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75179.886174] Please file bug report to http://rt2x00.serialmonkey.com.
[75180.324393] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75180.324396] Please file bug report to http://rt2x00.serialmonkey.com.
[75182.986416] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75182.986419] Please file bug report to http://rt2x00.serialmonkey.com.
[75184.014045] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75184.014048] Please file bug report to http://rt2x00.serialmonkey.com.
[75185.044942] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75185.044945] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.251861] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.251864] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.252971] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.252974] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.253623] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.253625] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.254623] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.254626] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.256770] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.256773] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.257924] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.257927] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.258634] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.258637] Please file bug report to http://rt2x00.serialmonkey.com.
[75192.258725] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75192.258728] Please file bug report to http://rt2x00.serialmonkey.com.
[75193.278872] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75193.278875] Please file bug report to http://rt2x00.serialmonkey.com.
[75193.280526] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75193.280529] Please file bug report to http://rt2x00.serialmonkey.com.
[75193.282594] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75193.282597] Please file bug report to http://rt2x00.serialmonkey.com.
[75193.282664] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75193.282667] Please file bug report to http://rt2x00.serialmonkey.com.
[75193.283844] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75193.283847] Please file bug report to http://rt2x00.serialmonkey.com.
[75196.364655] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75196.364658] Please file bug report to http://rt2x00.serialmonkey.com.
[75196.365814] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75196.365817] Please file bug report to http://rt2x00.serialmonkey.com.
[75200.477524] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 1.
[75200.477527] Please file bug report to http://rt2x00.serialmonkey.com.
Hi,
> Linux Varda 2.6.25-rc6-00268-gd2532dd #1 SMP PREEMPT Mon Mar 24 14:44:13 CET
> 2008 x86_64 GNU/Linux
>
>
> As the last time the thing is triggered with a p2p app making a lot of
> connections deluge
>
> My logs are spammed with the same msgs as other reports.
> If you need more info just ask.
This issue has been resolved for 2.6.26. The fix for this bug is of such a scale
that it could not easily be merged for 2.6.25.
> PS: i will not bother to make a report in the web forums becouse the last time
> i was ignored.
You mean http://rt2x00.serialmonkey.com/phpBB2/index.php?
'ignored' is not the right word, more likely overlooked.
There are quite a lot of messages and I don't always have time to answer them all.
So there is no need to be upset about such thing, simply posting a reminder is usually
enough to make it noticed by me...
> (Someone may want to change the web forums pointer in the logs to
> the linux-wireless mailing list)
What pointer? And rt2400-devel is the mailinglist for rt2x00...
The MAINTAINERS file in the kernel tree indicates 2 mailinglists for rt2x00:
[email protected]
[email protected]
Ivo
El Tue, 25 Mar 2008 14:41:22 +0100
Ivo van Doorn <[email protected]> escribi=C3=B3:
> Hi,
>=20
> > Linux Varda 2.6.25-rc6-00268-gd2532dd #1 SMP PREEMPT Mon Mar 24 14=
:44:13 CET
> > 2008 x86_64 GNU/Linux
> >=20
> >=20
> > As the last time the thing is triggered with a p2p app making a lo=
t of
> > connections deluge
> > =20
> > My logs are spammed with the same msgs as other reports.
> > If you need more info just ask.
>=20
> This issue has been resolved for 2.6.26. The fix for this bug is of s=
uch a scale
> that it could not easily be merged for 2.6.25.
>=20
> > PS: i will not bother to make a report in the web forums becouse t=
he last time
> > i was ignored.
>=20
> You mean http://rt2x00.serialmonkey.com/phpBB2/index.php?
> 'ignored' is not the right word, more likely overlooked.
Fair enough; english is not my mother tongue so maybe i sounded
harsher than intended. If that's the case my apologies
> There are quite a lot of messages and I don't always have time to ans=
wer them all.
> So there is no need to be upset about such thing, simply posting a re=
minder is usually
> enough to make it noticed by me...
>=20
> > (Someone may want to change the web forums pointer in the logs to=20
> > the linux-wireless mailing list)
>=20
> What pointer? And rt2400-devel is the mailinglist for rt2x00...
> The MAINTAINERS file in the kernel tree indicates 2 mailinglists for =
rt2x00:
> [email protected]
> [email protected]
Well my opinion is that instead of the webpage the mailing list should=
be the
one being logged. Something like this (maybe use another define becouse
DRV_PROJECT may be used elsewhere i havn't checked):
diff --git a/drivers/net/wireless/rt2x00/rt2x00.h
b/drivers/net/wireless/rt2x00/rt2x00.h index 6c72542..2791f67 100644
--- a/drivers/net/wireless/rt2x00/rt2x00.h
+++ b/drivers/net/wireless/rt2x00/rt2x00.h
@@ -44,7 +44,7 @@
* Module information.
*/
#define DRV_VERSION "2.0.14"
-#define DRV_PROJECT "http://rt2x00.serialmonkey.com"
+#define DRV_PROJECT "<[email protected]>"
=20
/*
* Debug definitions.
>=20
> Ivo
El Tue, 25 Mar 2008 14:46:28 +0100
Ivo van Doorn <[email protected]> escribi=C3=B3:
>=20
> I just checked the forums and apparently you mean that 8 replies to y=
our topic including the
> answer about "it has been fixed" in 2.1.0 counts as 'ignored'...
>=20
> For reference:
> http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=3D4512&highligh=
t=3D
Yes that got attention; many thanks to the ones (including you) that a=
nswered.
>=20
> and yes the following topic was unanswered
> http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=3D4572&highligh=
t=3D
> but that topic is a duplicate of your fist topic, and I am not respon=
ding to forum spammers...
Different kernel version the problem persisted and i thought i let peo=
ple know
that there was still an issue. If that makes me a "forum spammer" then =
i am
one.=20
Anyway it seems that I am only wasting your time so I stop here.
Thanks for your time and work.
=20
=20