From: Thomas Gleixner <tglx@linutronix.de>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Cc: vgoyal@in.ibm.com, hbabu@us.ibm.com,
LKML <linux-kernel@vger.kernel.org>,
kexec@lists.infradead.org,
Venkatesch Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCH 0/3] x86: unify crash_32/64.c
Date: Sat, 27 Oct 2007 00:37:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0710270035110.3186@localhost.localdomain> (raw)
In-Reply-To: <47225F6C.5000708@ct.jp.nec.com>
On Fri, 26 Oct 2007, Hiroshi Shimamoto wrote:
Added Venki to CC
> > I'm now testing crash on 32bit, but there is an issue before
> > applying the patches. My machine stopped at checking 'hlt'
> > after kexec, showing below message.
> >
> > CPU: Intel(R) Xeon(TM) CPU 3.80GHz stepping 0a
> > Checking 'hlt' instruction...
> >
> v2.6.23.1 works fine for 1st kernel.
> > I'm investigating it..
>
> I found that the following patch makes my machine stopped.
> bfe0c1cc6456bba1f4e3cc1fe29c0ea578ac763a
> x86: HPET force enable for ICH5
>
> It means that after applied this patch, HPET is enabled
> automatically on 1st kernel and after crash/kexec the 2nd
> kernel stopped at checking 'hlt'.
>
> I also tested the latest kernel(2.6.24-rc1-gec3b67c1).
> Boot parameter "nohpet" resolves this issue and kdump
> works well on 32bit.
> So I guess HPET affects this.
> But I don't know why 64bit kernel with HPET is OK.
Hmm. Does the 64 bit code shutdown HPET and restore the IRQ routing to
PIT and 32 bit is missing this ?
tglx
next prev parent reply other threads:[~2007-10-26 22:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 1:18 Hiroshi Shimamoto
2007-10-20 1:21 ` [PATCH 1/3] x86: add lapic_shutdown for x86_64 Hiroshi Shimamoto
2007-10-24 6:29 ` Vivek Goyal
2007-10-24 21:27 ` Hiroshi Shimamoto
2007-10-25 0:28 ` Eric W. Biederman
2007-10-29 22:45 ` Hiroshi Shimamoto
2007-10-29 22:39 ` [PATCH] Revert " Hiroshi Shimamoto
2007-10-29 23:15 ` Arjan van de Ven
2007-10-30 0:05 ` Hiroshi Shimamoto
2007-10-30 1:06 ` Thomas Gleixner
2007-10-20 1:23 ` [PATCH 2/3] x86: add safe_smp_processor_id " Hiroshi Shimamoto
2007-10-24 6:31 ` Vivek Goyal
2007-10-24 9:01 ` Vivek Goyal
2007-10-20 1:24 ` [PATCH 3/3] x86: unify crash_32/64.c Hiroshi Shimamoto
2007-10-20 10:50 ` [PATCH 0/3] " Thomas Gleixner
2007-10-24 6:34 ` Vivek Goyal
2007-10-24 16:28 ` Hiroshi Shimamoto
2007-10-25 17:58 ` Hiroshi Shimamoto
2007-10-26 21:43 ` Hiroshi Shimamoto
2007-10-26 22:37 ` Thomas Gleixner [this message]
2007-10-27 0:13 ` Hiroshi Shimamoto
2007-10-27 1:15 ` Hiroshi Shimamoto
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=alpine.LFD.0.9999.0710270035110.3186@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=hbabu@us.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@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®