linux-kernel - Re: [patches] Re: [PATCH] [14/19] i386: Disable nmi watchdog on all ThinkPads

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:	Sat, 21 Oct 2006 14:14:40 -0400
From:	Dave Jones <davej@...hat.com>
To:	Andi Kleen <ak@...e.de>
Cc:	patches@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [patches] Re: [PATCH] [14/19] i386: Disable nmi watchdog on all ThinkPads

On Sat, Oct 21, 2006 at 08:11:56PM +0200, Andi Kleen wrote:
 > 
 > >  > -	if (nmi_watchdog == NMI_DEFAULT && dmi_get_year(DMI_BIOS_DATE) >= 2004)
 > >  > +	   Probably safe on most older systems too, but let's be careful.
 > >  > +	   IBM ThinkPads use INT10 inside SMM and that allows early NMI inside SMM
 > >  > +	   which hangs the system. Disable watchdog for all thinkpads */
 > >  > +	if (nmi_watchdog == NMI_DEFAULT && dmi_get_year(DMI_BIOS_DATE) >= 2004 &&
 > >  > +		!dmi_name_in_vendors("ThinkPad"))
 > >  >  		nmi_watchdog = NMI_LOCAL_APIC;
 > > 
 > > This is going to get some people scratching their heads wondering
 > > why it isn't working if they ever try nmi_watchdog on one of these.
 > > How about adding an explanitory printk ?
 > 
 > When you enable it manually then NMI_DEFAULT won't be set and this code
 > is never executed.
 > 
 > BTW their machines will likely not stay up long enough that they can
 > see the printk (unless Lenovo fixes that particular bug in the future,
 > they are aware of it)

Ouch, nasty.  I'm surprised no-one complained about this earlier.

	Dave


-- 
http://www.codemonkey.org.uk
-
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/