linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: tip/master broken with x2apic and kexec
Date: Tue, 13 Jul 2010 16:27:12 -0700	[thread overview]
Message-ID: <4C3CF650.30905@kernel.org> (raw)
In-Reply-To: <4C3CE210.2030902@zytor.com>

On 07/13/2010 03:00 PM, H. Peter Anvin wrote:
> On 07/12/2010 07:59 PM, Yinghai Lu wrote:
>> tip/master: 
>> system1: BIOS enabled x2apic, first kernel boot well, and when kexec second kernel will cause system instant reboot.
>>
>> system2: BIOS not enable x2apic, first kernel boot well and enable x2apic, and kexec second kernel well. but when kexec third kernel will case system instant reboot.
>>
>> linus' tree is ok.
>>
>> but for system2 if boot with nox2apic ,intr-remaping off, iommu off, the kexec loop test will pass.
>>
>> the problem looks start in recent two or three weeks.
>>
>> Any idea?
>>
>> bisecting will take a while, because the system post take a while everytime.
>>
>> Thanks
>>
>> Yinghai Lu
> 
> OK, I found the bug... if you could test out the patch which will be
> sent out shortly I would very much appreciate it.

not sure if your patch is the offending one now.

kL: kernel from linus tree
kT1: kernel from tip
kT2: kernel from tip with reverting your patch

BIOS-->kL ---> kL ---> kL....always working
BIOS-->kT1 ---> kT1 --->  kT1 : between second one and third one system reset instant...
BIOS-->kT2 ---> kT2 --->  kT2 : between second one and third one system reset instant...

BIOS-->kL ---> kL ---> kL ---> then kT1 ---> kT1 .... always working
BIOS-->kL ---> kL ---> kL ---> then kT2 ---> kT2 .... always working

looks like first kernel and second one can not be kernel from tip.

Yinghai

  reply	other threads:[~2010-07-13 23:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13  2:59 tip/master broken with x2apic and kexec Yinghai Lu
2010-07-13  3:29 ` Yinghai Lu
2010-07-13  6:40   ` H. Peter Anvin
2010-07-14  0:54   ` [tip:x86/alternatives] x86, alternatives: Fix one more open-coded 8-bit alternative number tip-bot for H. Peter Anvin
2010-07-14  0:54     ` [tip:x86/alternatives] x86, alternatives: BUG on encountering an invalid CPU feature number tip-bot for H. Peter Anvin
2010-07-13 22:00 ` tip/master broken with x2apic and kexec H. Peter Anvin
2010-07-13 23:27   ` Yinghai Lu [this message]
2010-07-14 20:35     ` Yinghai Lu
2010-07-14 21:05       ` Don Zickus
2010-07-14 22:07         ` Yinghai Lu
2010-07-14 21:23       ` Yinghai Lu
2010-07-14 22:57         ` Yinghai Lu
2010-07-15  0:03           ` Suresh Siddha
2010-07-15  2:01             ` Yinghai Lu
2010-07-15  7:00             ` [PATCH] x86: fix x2apic preenabled system with kexec Yinghai Lu
2010-07-15 18:16               ` Suresh Siddha
2010-07-15 20:10                 ` Yinghai Lu
2010-07-15 20:40                   ` Yinghai Lu
2010-07-17  0:48               ` [tip:x86/urgent] x86: Fix " tip-bot for Yinghai Lu

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=4C3CF650.30905@kernel.org \
    --to=yinghai@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).