[Madwifi-users] Interrupt problems in 11g-only master mode (AR5212).
Status: Beta
Brought to you by:
otaku
From: DOm <ang...@ti...> - 2004-08-10 16:50:13
|
Hallo, i start this new thread to try to discover what causes the problem. Many of us have some instability and get system unresponsive when using madwifi in 11g-only master mode. Someone suggested to investigate using a system profile, but i'm not very used to these tools. Anyway, i tried to use oprofile (http://oprofile.sf.net) to see what causes the interrupt storm (at least _i_ think it is an interrupt problem). I use my pci card in master mode, but i have not a bridge setup, i route packet on the wired lan using: sysctl -w net.ipv4.ip_forward=1 I turned on debug messages of dev.ath.debug to print interrupt information with: sysctl -w dev.ath.debug=0x000000001000 under normal operation (ping or no manual action) the debug output is: ath_intr: status 0x10000 ath_intr: status 0x40 repeatedly, but when the system become slow, that is when i try to use the full bandwidth (for example using wget on the client), i get this output: ath_intr: status 0x10000 ath_beacon_tasklet: beacon queue 9 did not stop? sometime happen that the system do not become slow but stop trasmitting packets and output such a message: ath_hardstart: discard, no xmit buf I'm not able to understand where the problem is from the system profiler output, so i send you a file with a filtered output (only kernel and ath* stuff). If it is not enough, please give me more instruction on how to proceed. In the second attached file there is a summary of my system, to help you to know my machine. I made a script to generate such file and to add a bit of provacy (masking mac addresses and ipv6 addresses, and wep keys), if you are interested in such a dummy script i can post it, maybe it can be useful for other bug reports. I hope you can guess where is the problem. Goodbye, ANgelus. |