Hiroshi Shimamoto wrote: > Thomas Gleixner wrote: >> 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 ? > > Sorry, I'm not sure how I can get these informations. > Can you please tell me what I should do? > I'll continue to dig the issue. I attached the .config files and console logs. config32/64 are for 1st kernel, and cap32/64 are for 2nd capture kernel. kdump1.log is boot with nohpet on 32bit. kdump2.log is boot without nohpet on 32bit and the 2nd kernel hangs. kdump3.log is on 64bit. And the first kdump is failed because of without noapic. Thanks Hiroshi Shimamoto
Attachment:
configs.tar.bz2
Description: Binary data
Attachment:
consolelog.tar.bz2
Description: Binary data
- References:
- [PATCH 0/3] x86: unify crash_32/64.c
- From: Hiroshi Shimamoto <[email protected]>
- Re: [PATCH 0/3] x86: unify crash_32/64.c
- From: Vivek Goyal <[email protected]>
- Re: [PATCH 0/3] x86: unify crash_32/64.c
- From: Hiroshi Shimamoto <[email protected]>
- Re: [PATCH 0/3] x86: unify crash_32/64.c
- From: Hiroshi Shimamoto <[email protected]>
- Re: [PATCH 0/3] x86: unify crash_32/64.c
- From: Hiroshi Shimamoto <[email protected]>
- Re: [PATCH 0/3] x86: unify crash_32/64.c
- From: Thomas Gleixner <[email protected]>
- Re: [PATCH 0/3] x86: unify crash_32/64.c
- From: Hiroshi Shimamoto <[email protected]>
- [PATCH 0/3] x86: unify crash_32/64.c
- Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
- Next by Date: Re: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
- Previous by thread: Re: [PATCH 0/3] x86: unify crash_32/64.c
- Next by thread: 2.6.23-git Kconfig regression
- Index(es):
 |