rt2x00pci_write_tx_data: Error

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4907

storrgie

23-07-2008 10:38:20

[codelyar1ea9]Jul 22 22:52:02 BEAST kernel: [13067.357763] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
Jul 22 22:52:02 BEAST kernel: [13067.357765] Please file bug report to http://rt2x00.serialmonkey.com.
Jul 22 22:52:02 BEAST kernel: [13067.359851] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
Jul 22 22:52:02 BEAST kernel: [13067.359852] Please file bug report to http://rt2x00.serialmonkey.com.
Jul 22 22:52:02 BEAST kernel: [13067.365854] phy0 -> rt2x00pci_write_tx_data: Error - Arrived at non-free entry in the non-full queue 2.
Jul 22 22:52:02 BEAST kernel: [13067.365856] Please file bug report to http://rt2x00.serialmonkey.com.[/codelyar1ea9]

Getting a massive amount of these in my syslog when I run Vmware workstation with bridged networking.

I am running ubuntu 8.06 with a Linksys WMP54G Card v4.1


When I installed ubuntu the card picked right up so I never installed a driver, would installing a driver now help?

(New to linux)

Zi7

23-07-2008 13:46:19

When I installed ubuntu the card picked right up so I never installed a driver, would installing a driver now help?[/quote1najaaeo]
Indeed, it would -- as you'd have discovered had you read the first thread[/url1najaaeo] in this forum. ;)

storrgie

23-07-2008 14:13:47

Indeed, it would -- as you'd have discovered had you read the first thread[/url18j065bp] in this forum. ;)[/quote18j065bp]

Forgive me for being very new to this, but I did read this post and it appears that we are having different issues. For one he does not have 'rt2x00pci_write_tx_data error' coming up in his log, and for two he is trying to manipulate the mac address of the card while I am trying to use bridged networking in vmware.

I would appreciate some guidance on this issue, very new to linux.

IvD

23-07-2008 16:00:19

[quote3bo5xbeo]
phy0 -> rt2x00queue_write_tx_frame Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http//rt2x00.serialmonkey.com.
phy0 -> rt2x00queue_write_tx_frame Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http//rt2x00.serialmonkey.com.
phy0 -> rt2x00queue_write_tx_frame Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http//rt2x00.serialmonkey.com.
phy0 -> rt2x00queue_write_tx_frame Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http//rt2x00.serialmonkey.com.
phy0 -> rt2x00queue_write_tx_frame Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http//rt2x00.serialmonkey.com.
phy0 -> rt2x00queue_write_tx_frame Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http//rt2x00.serialmonkey.com.
[/quote3bo5xbeo]

Above is a direct quote from the topic Olivier referres to, if that isn't a "rt2x00queue_write_tx_frame Error" messages then I don't know what is...

Zi7

23-07-2008 16:10:52

Forgive me for being very new to this[/quotek39e89ib]
No problem with that. )

I did read this post and it appears that we are having different issues. For one he does not have 'rt2x00pci_write_tx_data error' coming up in his log, and for two he is trying to manipulate the mac address of the card while I am trying to use bridged networking in vmware.[/quotek39e89ib]
If you read carefully, he's actually dealing with 3 issues, one of them being about TX "arrived at non-free entry in non-full queue", which is pretty much your error. )
Admittedly, yours is triggered at rt2x00pci_write_tx_data() while his is triggered at rt2x00queue_write_tx_frame().

Sorry, i can't give you any VMware nor bridging specific advise at this point. Perhaps someone else can...

Edit Oops, race condition with Ivo. ;)

storrgie

23-07-2008 19:44:55

Above is a direct quote from the topic Olivier referres to, if that isn't a "rt2x00queue_write_tx_frame Error" messages then I don't know what is...[/quote3ip46m8k]

Did not realize that this error was correlated with mine, his specifying an error with being able to write to the queue seemed to be something very different that my error which was marked as pci.... causing me to automatically assume that my error was at another level completely, his being in the interpretation of information with the driver.... mine being the ability for the driver to communicate with my hardware.

Being very green, I apologize for the misconception as it should be my duty to investigate further.

As a course of action at this point, going back to Zi7's first reply, would installing a different version of the driver help? If this is the way to go, where could I find documentation to help me in this process as this is my first time running in linux (cant you tell by my choosing ubuntu?).

Thanks for the help

Zi7

24-07-2008 14:34:03

As a course of action at this point, going back to Zi7's first reply, would installing a different version of the driver help?[/quote3cbuo2ky]
As stated in my first post yes, it would.

If this is the way to go, where could I find documentation to help me in this process as this is my first time running in linux (cant you tell by my choosing ubuntu?).[/quote3cbuo2ky]
As stated in the thread i linked to in my first post, the driver version you need is so far only available in the development branch it won't work with your Ubuntu standard kernel, you'll need to recompile a kernel from rt2x00's git repository.
So, it means
[list3cbuo2ky][*3cbuo2ky]Get the rt2x00.git sources[/url3cbuo2ky][/*m3cbuo2ky]
[*3cbuo2ky][url=https://help.ubuntu.com/community/Kernel/Compile3cbuo2ky]Compile your kernel the Ubuntu way[/url3cbuo2ky][/*m3cbuo2ky][/listu3cbuo2ky]
This is quite an exercise. ;)

[quote="storrgie"3cbuo2ky]it should be my duty to investigate further.[/quote3cbuo2ky]
Investigating before asking for help is indeed very much appreciated in the linux community. ;)

Zi7

24-07-2008 15:35:08

By the way you're running the desktop release of Ubuntu, right?
What is your CPU (hardware and VMware)?

Thanks.

AdamBaker

24-07-2008 20:30:23

Whilst investigating before posting is always appreciated if you don't know what you are doing it isn't always easy. What is even more important is pointing out your level of knowledge and getting the details you do provide correct so someone can tell you what else you might need to do.

Whilst compiling a new kernel isn't that hard it isn't exactly trivial either so if you don't know what you are doing it is worth exploring alternatives. In your case (because you told us you are running ubuntu 8.06 by which I guess you really meant 8.04) the best alternative is probably to install the linux-backports-modules-hardy package which will install a newer version of the rt2x00 driver. It isn't quite the newest driver that you'd get if you used git to obtain the rt2x00 kernel image but it is a lot easier to try.

storrgie

25-07-2008 01:23:50

Beast (Primary Desktop)
Q6600@3.6Ghz (400x9, 65nm)
4x2GB@800Mhz
Abit IP35-Pro
Geforce 512MB 7950GT
Geforce 256MB 7800GTX
WRT54G
2x74GB Raptor, 4x500GB Caviar
2x20" Dell 2005FPW
Primary OS Ubuntu Desktop 8.04 x64
Secondary OS Windows Vista SP1 x64
VM XP Pro SP3 x32 (Development)
VM Ubuntu Desktop 8.04 x32 (Development)
VM Ubuntu Server 8.04 x64 (Development)
VM Vista SP1 x64 (Development)

Vmware workstation 6.04, with a patch for help with wireless bridge. There are many issues with getting wireless bridge to work under vmware, I found the patch here http//liken.otsoa.net/blog/index.php?e ... 301-173023

@AdamBaker, I will try this solution out tonight once I get my new HDD's staged... picked up 2 new 500GB drives.


Thanks very much guys, I will report back soon.

Zi7

25-07-2008 10:37:27

Beast (Primary Desktop)
Q6600@3.6Ghz (400x9, 65nm)
[...]
WRT54G
Primary OS Ubuntu Desktop 8.04 x64
Secondary OS Windows Vista SP1 x64
VM XP Pro SP3 x32 (Development)
VM Ubuntu Desktop 8.04 x32 (Development)
VM Ubuntu Server 8.04 x64 (Development)
VM Vista SP1 x64 (Development)[/quote18vku1t8]
Nice piece of equipment, storrgie, i'm jealous! ;)
So, what is the exact setup(s) you're running when these error messages spawn?

Agreeing with AdamBaker the backports modules might help.

storrgie

25-07-2008 13:03:44

Indeed the backport modules seem to have solved my issue. I rigorously checked the syslog every 10 minutes for about 4 hours last night as I ran high traffic.

Over night there was no issues whatsoever.

@Zi7 To answer the question about what exactly I am running

There is a local coffee shop that shares wireless access for free, I anonymously drop off 10$ a month in their mailbox. For this 10$ a month fee I cut myself out a 100Kbs (limiting my bandwidth) connection on their network 24/7. I run a Windows XP VM that runs utorrent/peerguardian, but is essentially a honeypot with zero protection from firewall/viruscanner.

As for my host OS, I mainly stick to using FF,Evolution,Gimp, Coding and watching movies so not alot of network traffic. I didnt notice the issue, or experience kernal panic until I started using vmware with bridged networking for this filesharing.

@Community

I will set up another vm of ubuntu and go through the exercise of compiling my own kernel, this is something a linux user should be comfortable with.

@Community

I have another machine that is running linux now

MobileBeast (Primary Laptop)
T9300@2.5Ghz (45nm)
2x2GB@667Mhz
Dell M4300 Precision Workstation
Quadro 512MB 360m
15.4" WSXGA+ W/ truelife

Not sure exactly what the specs are on the wireless card, will check tonight. My question is regarding an external card. I have been looking at orinoco gold cards, but this machine only has a PCexpress slot. I would like a card that I can put into promiscuous mode, this coffee shop is a bluster of activity and I would like to learn how to do some analysis on wireless traffic.

Any suggestions for a card?