linux-kernel - Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD Phenom-II processor

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: <20090220123402.GA26418@elte.hu>
Date:	Fri, 20 Feb 2009 13:34:02 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andreas Herrmann <andreas.herrmann3@....com>
Cc:	Mark Hounschell <dmarkh@....rr.com>,
	Borislav Petkov <borislav.petkov@....com>,
	Mark Hounschell <markh@...pro.net>,
	john stultz <johnstul@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: PROBLEM: Can't boot a (HZ = 1000) kernel using an AMD
	Phenom-II processor


* Andreas Herrmann <andreas.herrmann3@....com> wrote:

> On Thu, Feb 19, 2009 at 10:54:19AM -0500, Mark Hounschell wrote:
> > Borislav Petkov wrote:
> > > On Thu, Feb 19, 2009 at 10:16:40AM -0500, Mark Hounschell wrote:
> > >> Andreas Herrmann wrote:
> > >>> Hi Mark,
> > >>>
> > >>> Can you please provide us output of lspci -vvxxx.
> > >>> (Please run this as root.)
> > >>>
> > 
> > Attached...
> > 
> > 
> > >>> Furthermore you can try booting your 1000HZ kernel
> > >>> with following kernel command lines:
> > >>>
> 
> Thanks for trying this out.
> But nothing suspicious found. I.e. timer/hpet interrupt is enabled
> and its routing seems to be ok.
> 
> Here's one more check that's worth trying: In one of your logs I've
> seen that HPET id reports 3 timers but later on 4 timers were detected
> for HPET.
> 
> To check what's going on I'd like to see the HPET 
> configuration in the course of booting your system.  Please 
> apply attached patch and boot with hpet=debug -- both with 
> 250HZ and with 1000HZ -- and provide dmesg output.

Mind sending this patch as a hpet=verbose feature patch which we 
could queue up for upstream merging? We have hpet problems 
frequently, so some built-in debug/verbosity trigger would be 
nice.

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