[ath9k-devel] ath9k implicated in lockups, kernel 2.6.38

[Ben Greear <greearb@candelatech.com>]

On 05/19/2011 10:15 AM, Camilo Mesias wrote:
> Hi,
>
> On Thu, May 19, 2011 at 4:21 PM, Ben Greear<greearb@candelatech.com>  wrote:
>> Try yanking your NIC and see if the problems persist?
>
> Just to be clear, do you mean to remove the mini-pci express card from
> the netbook and run without it? I understand the driver wouldn't get
> loaded in that case anyway, so it would be a hardware equivalent to
> blacklisting the ath9k module (which completely cures the problem)

Ahh, I didn't realize you had blacklisted.  That does seem to implicate
ath9k.

>
>> Ath9k has it's issues, but it's surely not the only thing that
>> can lock up a system..and it usually spews all sorts of warnings/errors
>> before it does lock up a system.
>
> Not in this case it seems. Is there a way to increase the debug level?

Have you tried enabling sysrq and seeing if sysrq can print any CPU backtraces?

http://www.mjmwired.net/kernel/Documentation/sysrq.txt

If you can re-compile your kernel, make sure you have the
LOCKUP_DETECTOR enabled, and perhaps PROVE_LOCKING and other
mutex debugging.

>
>> And, recently it's been much more stable..so try a 2.6.39 kernel perhaps?
>
> I'll have a look in koji and see if I can grab any newer kernels.
>
> Who understands the suspend process and what happens to the driver's
> threads and resources? Is it documented anywhere?

I may have missed your initial report.  Does this happen only
when you suspend?  Can you give as many details as possible about
how you can cause this bug to happen (and not happen)?

Thanks,
Ben

>
> -Cam


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