From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: rt2400-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: rt2x00 is sapmming my logs
Date: Sat, 22 Dec 2007 17:31:53 +0100 [thread overview]
Message-ID: <20071222173153.42f574fd@Varda> (raw)
I have a rt2500pci card on an 64 bit system (Ubuntu) AMD X2 processor and i'm
trying latest vanilla kernels i've used a 2.6.24-rc5 kernel without mayor issues
(except that i have to issue a sudo iwconfig wlan0 rate 54M because it allways
connect at 1Mbit and it is dog slow) but now with v2.6.24-rc6-83-g5b825ed i
have my dmesg spammed with:
[ 1122.323489] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.323491] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.326139] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.326142] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.327508] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.327511] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.329405] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.329409] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.332519] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.332522] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.334444] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.334447] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.336847] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.336850] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.338654] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.338657] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.340844] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.340847] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.343035] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.343038] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.344301] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.344303] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.347146] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
[ 1122.347148] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1122.349381] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 0.
The connection seems top work anyways so i do not think this is critical.
Thanks in advance for your time.
next reply other threads:[~2007-12-22 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 16:31 Alejandro Riveira Fernández [this message]
2007-12-22 23:04 ` rt2x00 is sapmming my logs Rafael J. Wysocki
2007-12-22 23:04 ` Rafael J. Wysocki
2007-12-22 22:54 ` Alejandro Riveira Fernández
2007-12-22 22:54 ` Alejandro Riveira Fernández
2007-12-22 22:57 ` drago01
2007-12-22 23:20 ` Rafael J. Wysocki
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=20071222173153.42f574fd@Varda \
--to=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.