From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: rt2400-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
IvDoorn@gmail.com
Subject: Spammed logs again rt2500pci 2.6.24-rc8
Date: Thu, 17 Jan 2008 22:57:44 +0100 [thread overview]
Message-ID: <20080117225744.29aa214c@Varda> (raw)
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
next reply other threads:[~2008-01-17 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:57 Alejandro Riveira Fernández [this message]
2008-01-18 10:56 ` Spammed logs again rt2500pci 2.6.24-rc8 Mattias Nissler
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:08 ` Alejandro Riveira Fernández
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=20080117225744.29aa214c@Varda \
--to=ariveira@gmail.com \
--cc=IvDoorn@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 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).