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: <1190755493.17409.72.camel@chaos>
Date:	Tue, 25 Sep 2007 23:24:53 +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

Rafael,

On Tue, 2007-09-25 at 23:28 +0200, Rafael J. Wysocki wrote:
> > I'm a bit confused by your earlier confirmation, that mainline w/o the
> > -hrt patches boots fine, when you add "apicmaintimer" to the kernel
> > command line. "apicmaintimer" stops the PIT like we do in -hrt and we
> > just use the local APIC timer for everything. Can you please retest and
> > confirm that this is correct ?
> 
> No, it's not.  The mainline _usually_ doesn't boot with "apicmaintimer".
> 
> It seems to me that _sometimes_ the CPU just doesn't enter this C1E state
> and then everything goes fine ...

I'm relieved. I really started to go nuts on this contradicting
patterns.

Your box seems to be worse than the VAIO, it has some random surprise
generator built in :)

> > Is the 32 bit kernel working on that box ?
> 
> Can't tell, I have only 64-bit userland here.

Should be fine. The check is there since late 2.6.21-rc. I really could
kick my own ass that I did not remember the nx6325 wreckage in the
2.6.21-rc time frame. Sigh, way too much broken hardware out there to
keep track of it.

> > Thanks for your patience.
> 
> Well, I'm only making sure that future kernels will run on my box. ;-)

Nothing wrong with that. Thanks again for your help,

	tglx


-
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