From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
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: Spammed logs again rt2500pci 2.6.25-rc6-00268-gd2532dd
Date: Tue, 25 Mar 2008 13:12:50 +0100 [thread overview]
Message-ID: <20080325131250.5167e311@Varda> (raw)
In-Reply-To: <20080117225744.29aa214c@Varda>
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.
next prev parent reply other threads:[~2008-03-25 13:35 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
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 ` Alejandro Riveira Fernández [this message]
2008-03-25 13:41 ` Spammed logs again rt2500pci 2.6.25-rc6-00268-gd2532dd 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=20080325131250.5167e311@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 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.