On Fri, Apr 09, 2010 at 09:46:08AM +0530, Raghu Ramaraj wrote:
As I said, it's probable that your hardware (either wireless device or
PCI) doesn't work correctly.
Yes - the error refers to the attempt of the driver to turn on the
onboard cpu and then read some values from MMIO space. This is the
first thing the driver does. It tries for 200 reads/writes, and if
there is no positive response by then, it gives up. While the
onboard chip is down, it returns 0xffffffff on every read.
FWIW I have an old Atheros card which behaves in exactly this manner.
So, you can try moving the device to a computer and see if it's the
platform or the device.
--
Bob Copeland %% www.bobcopeland.com
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.orghttps://lists.ath5k.org/mailman/listinfo/ath5k-devel