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] [day] [month] [year] [list]

Message-ID: <BANLkTi=oqFwfm2q12FyVR0xSOKABG-PtPA@mail.gmail.com>
Date:	Tue, 3 May 2011 20:51:37 +0200
From:	Sebastian Färber <faerber@...il.com>
To:	Don Zickus <dzickus@...hat.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)

>
> 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?

I've recompiled 2.6.36.4 and 2.6.37.6 with both options enabled and
removed "nmi_watchdog=1" from the
kernel cmdline.
I'll get back to you if i get another lockup, could take a few days
unfortunatly.
Thanks for your help!

Regards,
Sebastian
--
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/