On Feb 24, 2009, at 7:42 PM, Larry Finger wrote:
Francesco Gringoli wrote:
On Feb 24, 2009, at 5:35 PM, Larry Finger wrote:
Francesco Gringoli wrote:
What about drop info from dmesg? Another try could be halve the dma
queue, I believe now it is 64 slots. Could you give a try setting
it
to 32?
The RX DMA queue was 64 and TX was 256. Both will be 32 in my next
run.
I don't understand the "drop info from dmesg" part.
Sorry Larry,
sometimes when I modify something, I can read
[334415.451028] b43-phy244 debug: RX: Packet dropped
in the dmesg because the received bytes were not correctly copied
between the "air-buffer" to the internal buffer and finally to the
rx-fifo along with the rxheader.
Did you notice something similar?
I hadn't noticed them before, but I do see one of these messages
just before
some of my out-of-order cookies. There is no associated diagnostic
message, thus
it must come from the status.rate_index test. I'll see if I can get
some info
from there.
Larry
Larry, take care that they are not due to massive usage of b43-fwdump.
Sometime this utility forces the firmware to slow down and produce
such messages. If you didn't use the utility and got that message
anyway, we can try to investigate on this.
Cheers,
-FG
-------
Francesco Gringoli, PhD - Assistant Professor
Dept. of Electrical Engineering for Automation
University of Brescia
via Branze, 38
25123 Brescia
ITALY
Ph: ++39.030.3715843
FAX: ++39.030.380014
WWW: http://www.ing.unibs.it/~gringoli
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
