[ath9k-devel] Seem to have fried my AR9300 NIC?

[Ben Greear <greearb@candelatech.com>]

On 07/23/2012 03:08 PM, Ben Greear wrote:
> On 07/23/2012 02:10 PM, Ben Greear wrote:
>> Came back after a 1 week vacation and found the 3.3.8+ kernel spitting
>> timeout errors, and network devices will not 'ifconfig foo up'.
>>
>> I rebooted into 3.5.0+, and see the same (or at least similar errors):
>
> Well, I replaced the NIC and the problem remains.
>
> Guess it's time to poke a bit deeper.

Ahh..so here's what happened.  I added code to set the rx-chainmask
and tx-chainmask from user-space app (via writing to appropriate debugfs
files).

Code assumed 0x7 by default, but this particular NIC is only 2x2.

When the chainmask is set wrong, the NIC gets into the broken state.

Changing it back to 0x3 fixes the problem.

Is that worth trying to fix in the driver, or should I just
fix it in user-space so that it never sets more than what
the eeprom reports as supported?

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com