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: <1190661212.4035.242.camel@chaos>
Date:	Mon, 24 Sep 2007 21:13:32 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
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 Mon, 2007-09-24 at 21:11 +0200, Rafael J. Wysocki wrote:
> > /me scratches head
> 
> Retested.
> 
> > We know, that
> > - disabling local apic timers work
> 
> This works reproducibly accross the board.

Ok

> > - 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".

Did you connect this box to Andrews VAIO during KS ?

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

Ok. Can you add "nmi_watchdog=1" to the command line please. This runs
through the calibration of APIC, but registers it as a dummy clock
source (the PIT must run to make the watchdog work).

If it boots, please provide the output of /proc/timer_list

Thanks,	

	tlgx


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