On 02/20/2013 02:51 PM, Ben Greear wrote:
On 02/18/2013 06:14 PM, Sujith Manoharan wrote:
Ben Greear wrote:
On 02/11/2013 04:11 PM, Sujith Manoharan wrote:
Ben Greear wrote:
axq-qnum: 2 3 1 0
axq-depth: 0 0 0 0
axq-ampdu_depth: 0 0 0 0
axq-stopped 1 0 0 0
tx-in-progress 0 0 0 0
pending-frames 125 0 0 0
The frames appear to be stuck in the pending queue.
Any ideas on what code to go poking at?
xmit.c would be a good place. Can you also post the kernel log with some
debugging information ? debug=0x8f49 would be good.
I was 2/2 hitting the problem without debug set, but
had two clean runs with debugging enabled. Either I'm
unlucky, or enabling debugging messes with things enough
to make the problem go away :P
Maybe looking at the xmit number can give some info?
axq-qnum: 2 3 1 0
axq-depth: 0 0 0 0
axq-ampdu_depth: 0 0 0 0
axq-stopped 1 0 0 0
tx-in-progress 0 0 0 0
pending-frames 123 0 0 0
txq_headidx: 7 0 0 6
txq_tailidx: 7 0 0 6
For instance, in this case, why do we have pending frames, the axq-stopped,
and no axq depth? Is that an invalid state to begin with? Once
it gets in the hung state, those numbers never change. I'd assume
something should be poking more packets out of the pending frames
down into the axq logic?
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
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
