linux-kernel - Re: Hard LOCKUP, maybe acpi related (present in 2.6.32 to 2.6.37, fixed in 2.6.38)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 May 2011 09:01:23 -0400
From:	Don Zickus <dzickus@...hat.com>
To:	Sebastian Färber <faerber@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Hard LOCKUP, maybe acpi related (present in 2.6.32 to 2.6.37,
 fixed in 2.6.38)

On Fri, Apr 29, 2011 at 12:50:35PM +0200, Sebastian Färber wrote:
> Hi,
> 
> I'm trying to track down a problem i have with newer hardware which seems
> fixed in 2.6.38.4 but which i can reproduce from 2.6.32 to 2.6.37
> I'm running a DEBUG Kernel with nmi_watchdog=1 and attached a backtrace
> of the lockup that happened on 2.6.37.6. I can also provide backtraces for
> 2.6.32 to 2.6.35 if necessary, they look very similar.

It looks like you are using the old nmi watchdog which may have given you
false positives.  Can you turn on the new nmi watchdog (for 2.6.36 or
later)?

CONFIG_LOCKUP_DETECTOR=y
CONFIG_HARDLOCKUP_DETECTOR=y

and see if that gives a more meaningful backtrace?

Cheers,
Don
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/