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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200709242111.07806.rjw@sisk.pl>
Date:	Mon, 24 Sep 2007 21:11:06 +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 18:46, Thomas Gleixner wrote:
> On Mon, 2007-09-24 at 17:18 +0200, Rafael J. Wysocki wrote:
> > > > 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.
> 
> /me scratches head

Retested.

> We know, that
> - disabling local apic timers work

This works reproducibly accross the board.

> - local apic timers (which turn off PIT) work. when noacpiFSCKEDPARSING

This stopped working, although it evidently worked yesterday (wtf?).

There seems to be a history effect in the box, to make things more
"interesting".

> is given on the kernel command line.
> 
> I have no clue, what might be the difference of noacpiFSCKEDPARSING. The
> boot log is not giving any hint at all.
> 
> acpi_disable_pci() sets acpi_pci_disabled and acpi_noirq to 1.
> 
> What happens, if you set "acpi=noirq" instead ?

That obviously doesn't help.

I think the only solid data point so far is that "noapictimer" makes the box
boot.

Greetings,
Rafael
-
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/