From: ebiederm@xmission.com (Eric W. Biederman)
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: <vgoyal@in.ibm.com>,
"Konstantin Baydarov" <kbaidarov@ru.mvista.com>,
"RT" <linux-rt-users@vger.kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"Andi Kleen" <ak@suse.de>
Subject: Re: [PATCH] kexec: reenable HPET before kexec
Date: Mon, 27 Aug 2007 12:33:00 -0600 [thread overview]
Message-ID: <m1zm0c4ylf.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <653FFBB4508B9042B5D43DC9E18836F501522051@scsmsx415.amr.corp.intel.com> (Venkatesh Pallipadi's message of "Mon, 27 Aug 2007 11:26:29 -0700")
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> writes:
> - Another thing to try is to disable HPET and boot with PIT in the first
> kernel. Just to check whether PIT never works on this platform or the
> first kernel is doing something to stop PIT. You can try "hpet=disable"
> boot option for that.
I don't know what the original patch looked like. It doesn't
seem to have made it to any mailling lists to which I'm subscribed.
But I'm wondering of there is a bug in the shutdown routines for
the pit or the hpet that is causing problems. As this is
a normal kexec those routines will get called.
Eric
next prev parent reply other threads:[~2007-08-27 18:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:55 Konstantin Baydarov
2007-08-20 18:26 ` Andi Kleen
2007-08-20 21:10 ` Konstantin Baydarov
2007-08-20 21:31 ` Daniel Walker
2007-08-21 13:01 ` Konstantin Baydarov
2007-08-23 9:08 ` Vivek Goyal
2007-08-23 11:49 ` Konstantin Baydarov
2007-08-27 5:36 ` Vivek Goyal
2007-08-27 18:26 ` Pallipadi, Venkatesh
2007-08-27 18:33 ` Eric W. Biederman [this message]
2007-08-28 12:58 ` Konstantin Baydarov
2007-08-30 7:32 ` Eric W. Biederman
2007-08-30 16:07 ` Konstantin Baydarov
2007-08-30 18:04 ` Eric W. Biederman
2007-08-31 10:31 ` Konstantin Baydarov
2007-09-17 9:47 ` Konstantin Baydarov
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=m1zm0c4ylf.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=kbaidarov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=vgoyal@in.ibm.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
all inboxes | Powered by JetHome®