>>>>> "Felix" == Felix Fietkau <nbd@xxxxxxxxxxx> writes: >> 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. Felix> If I read the trace correctly, the accessed register is 0x111c, Felix> which is AR5K_QUEUE_DFS_MISC(7). If I remember correctly, queue Felix> 7 is the beacon queue. Access to this register should never Felix> fail unless the hardware is in sleep mode, or there is some Felix> other PCI related issue. Unfortunately, this issue might be Felix> caused by something entirely different that is not visible in Felix> the stack trace. I have observed that messing up the internal Felix> state of a PCI card can trigger an error that only shows up Felix> much later and thus can only be found by doing a thorough code Felix> review or by analyzing PCI traces. I wonder what is special about MIPS (relative to x86, where I don't see the panics). -- Russell Senior ``I have nine fingers; you have ten.'' seniorr@xxxxxxxxxxx -- 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
