linux-kernel - Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents

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]

Date:	Mon, 24 Sep 2007 17:18:22 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents

On Monday, 24 September 2007 16:23, Thomas Gleixner wrote:
> On Mon, 2007-09-24 at 15:52 +0200, Rafael J. Wysocki wrote:
> > > > > So I really wonder, why noacpitimer on the kernel command line makes any
> > > > > difference. I'm confused.
> > > > 
> > > > \metoo
> > > > 
> > > > Well, it was probably read as "noacpi". :-)
> > > 
> > > Hmm, ACPI is in the log all over the place.
> > 
> > Well, "noacpi" seems to be a synonym for "pci=noacpi".
> > 
> > Anyway, it causes acpi_disable_pci() to be executed, which according to
> > Documentation/kernel-parameters.txt means "Do not use ACPI for IRQ routing or
> > for PCI scanning" (it works like this on x86_64 too, although the doc says it's
> > x86_32-specific).
> 
> Hrm. The local apic timer calibration does not use anything which is
> related to interrupts, but if we use the local APIC timer we switch off
> PIT.
> 
> Can you boot Linus latest (w/o hrt patches) and add "apicmaintimer" to
> the kernel command line please ?

Works, dmesg attached.

Greetings,
Rafael

View attachment "2.6.23-rc7test.log" of type "text/x-log" (41552 bytes)