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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1172162526.3531.275.camel@laptopd505.fenrus.org>
Date:	Thu, 22 Feb 2007 17:42:06 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	tglx@...utronix.de, Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Luca Tettamanti <kronos.it@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: NO_HZ: timer interrupt stuck [Re: Linux 2.6.21-rc1]

On Thu, 2007-02-22 at 17:27 +0100, Pierre Ossman wrote:
> Thomas Gleixner wrote:
> >
> > Here is the reason. The local APIC stops working in C3 state and we fall
> > back to the PIT in that case. Not really exciting for dynticks, but the
> > only way to keep the system alive. There is a patch coming up from
> > Intel, which finds out how to use HPET even if it is not enabled by the
> > BIOS. This will still end up on IRQ#0, but will give way longer idle
> > sleeps than the PIT.
> >
> >   
> 
> So then the next two questions are; is it possible to disable C3 

yeah there is a commandline thingy for it
> and is
> it a net power gain to get rid of the wakeups in favor of having C3.

no; c3 saves a TON more power. 

you can try enabling HPET in your BIOS...

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ