| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 22 Dec 2007 17:31:53 +0100 From: Alejandro Riveira Fernández <ariveira@...il.com> To: rt2400-devel@...ts.sourceforge.net, linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org Subject: rt2x00 is sapmming my logs 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists