On 2011-05-03 8:18 AM, Adrian Chadd wrote:
Well, I see the same on FreeBSD/MIPS whenever an Atheros device is
fondled incorrectly. Either because the chip isn't yet fully awake or
the register plainly doesn't exist.
See if you can add some debugging in ath5k_hw_reset_tx_queue() to see
which register is being read/written before the PCI bus error occurs.
If I read the trace correctly, the accessed register is 0x111c, which is
AR5K_QUEUE_DFS_MISC(7). If I remember correctly, queue 7 is the beacon
queue. Access to this register should never fail unless the hardware is
in sleep mode, or there is some other PCI related issue. Unfortunately,
this issue might be caused by something entirely different that is not
visible in the stack trace. I have observed that messing up the internal
state of a PCI card can trigger an error that only shows up much later
and thus can only be found by doing a thorough code review or by
analyzing PCI traces.
- Felix
--
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
