All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Cc: john stultz <johnstul@us.ibm.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Andi Kleen <ak@suse.de>, keith maanthey <kmannth@us.ibm.com>,
	Max Asbock <masbock@us.ibm.com>, Chris McDermott <lcm@us.ibm.com>
Subject: Re: i386 HPET code
Date: Thu, 3 Feb 2005 08:37:09 +0000	[thread overview]
Message-ID: <200502030837.09331.andrew@walrond.org> (raw)
In-Reply-To: <1107396306.2040.237.camel@cog.beaverton.ibm.com>

On Thursday 03 February 2005 02:05, john stultz wrote:
> Hey Venkatesh,
>  I've been looking into a bug where i386 2.6 kernels do not boot on IBM
> e325s if HPET_TIMER is enabled (hpet=disable works around the issue).
> When running x86-64 kernels, the issue isn't seen. It appears that after

FWIW The problem is not limited to the IBM e325. I cannot boot a HPET_TIMER 
enabled x86 kernel on any of the various Tyan and MSI opteron boards I have 
here without hpet=disable. x86_64 kernels work fine.

Andrew Walrond

  reply	other threads:[~2005-02-03  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  2:05 i386 HPET code john stultz
2005-02-03  8:37 ` Andrew Walrond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-03 14:28 Pallipadi, Venkatesh
2005-02-03 19:30 ` john stultz
2005-02-03 20:02   ` Venkatesh Pallipadi
2005-02-03 21:22     ` Andi Kleen
2005-02-04 17:22     ` Andrew Walrond
2005-02-03 21:30 ` Andi Kleen
2005-02-04 19:28   ` Vojtech Pavlik
2005-02-04 20:02   ` Vojtech Pavlik
2005-02-04 20:03     ` Vojtech Pavlik

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=200502030837.09331.andrew@walrond.org \
    --to=andrew@walrond.org \
    --cc=ak@suse.de \
    --cc=johnstul@us.ibm.com \
    --cc=kmannth@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masbock@us.ibm.com \
    --cc=venkatesh.pallipadi@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.