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:	Thu, 22 Mar 2007 21:42:09 +0100
From:	"Stefan Prechtel" <stefan.prechtel@...glemail.com>
To:	"Grzegorz Chwesewicz" <grzegorz.chwesewicz@...lan.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>, "Andi Kleen" <ak@...e.de>,
	linux-kernel@...r.kernel.org, "Len Brown" <lenb@...nel.org>,
	"john stultz" <johnstul@...ibm.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Adrian Bunk" <bunk@...sta.de>,
	"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: [PATCH] i386: disable local apic timer via command line or dmi quirk

2007/3/21, Grzegorz Chwesewicz <grzegorz.chwesewicz@...lan.com>:
> On Wed, 21 Mar 2007 15:09:30 +0100, Ingo Molnar wrote
> > * Thomas Gleixner <tglx@...utronix.de> wrote:
> >
> > > The local APIC timer stops to work in deeper C-States. This is handled
> > > by the ACPI code and a broadcast mechanism in the clockevents / tick
> > > managment code.
> > >
> > > Some systems do not expose the deeper C-States to the kernel, but
> > > switch into deeper C-States behind the kernels back. This delays the
> > > local apic timer interrupts for ever and makes the systems unusable.
> > >
> > > Add a command line option to disable the local apic timer and a dmi
> > > quirk for known broken systems.
>
> Confirming that my machine on 2.6-git with this patch works just like on
> 2.6.20. Great work.
>
> --
> Greetings - Grzegorz Chwesewicz

Works here too, thx ;)

Kind regards,
Stefan Prechtel
-
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