public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Erwin Rol <mailinglists@erwinrol.com>
Cc: Andi Kleen <ak@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: Display HPET timer option
Date: Thu, 1 Dec 2005 22:18:48 +0100	[thread overview]
Message-ID: <20051201211848.GE997@wotan.suse.de> (raw)
In-Reply-To: <1133471197.3604.3.camel@xpc.home.erwinrol.com>

On Thu, Dec 01, 2005 at 10:06:37PM +0100, Erwin Rol wrote:
> On Thu, 2005-12-01 at 21:43 +0100, Andi Kleen wrote:
> > On Thu, Dec 01, 2005 at 12:30:03PM -0800, Zwane Mwaikambo wrote:
> > > On Thu, 1 Dec 2005, Linus Torvalds wrote:
> > > 
> > > > On Thu, 1 Dec 2005, Zwane Mwaikambo wrote:
> > > > >
> > > > > Currently the HPET timer option isn't visible in menuconfig.
> > > > 
> > > > Do you want it to?
> > > > 
> > > > Why would you ever compile it out?
> > > 
> > > For timer testing purposes i sometimes would like not to use the HPET. 
> > > Would a runtime switch be preferred?
> > 
> > nohpet already exists.
> > 
> 
> And luckily it does cause without "nohpet" i can't boot my shuttle
> ST20G5, the NMI watchdog kills it because ti hangs when initializing the
> hpet. If the nmi watchdog is off it just hangs for ever. 

Can you give details on the machine? lspci, dmidecode, acpidmp output,
boot log from the hang case?

Then perhaps it can be blacklisted or the failure otherwise avoided.

[Looks like I finally need to add DMI decode support to x86-64 too :-/]

-Andi


  reply	other threads:[~2005-12-01 21:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 19:44 [PATCH] x86_64: Display HPET timer option Zwane Mwaikambo
2005-12-01 19:50 ` Linus Torvalds
2005-12-01 19:53   ` Andi Kleen
2005-12-01 20:30   ` Zwane Mwaikambo
2005-12-01 20:43     ` Andi Kleen
2005-12-01 21:06       ` Erwin Rol
2005-12-01 21:18         ` Andi Kleen [this message]
2005-12-08 13:53           ` Erwin Rol
2005-12-08 14:58           ` Erwin Rol
2005-12-08 15:23           ` Erwin Rol
2005-12-09 19:56           ` Erwin Rol
2005-12-01 23:13       ` Zwane Mwaikambo
2005-12-01 20:51     ` Zwane Mwaikambo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051201211848.GE997@wotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailinglists@erwinrol.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox