From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Cc: cl@linux.com, Tejun Heo <tj@kernel.org>,
mika.j.penttila@gmail.com, Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"H. Peter Anvin" <hpa@zytor.com>,
yasu.isimatu@gmail.com, isimatu.yasuaki@jp.fujitsu.com,
kamezawa.hiroyu@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
gongzhaogang@inspur.com, Len Brown <len.brown@intel.com>,
Len Brown <lenb@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
chen.tang@easystack.cn, "Rafael J. Wysocki" <rafael@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v7 0/5] Make cpuid <-> nodeid mapping persistent
Date: Thu, 19 May 2016 14:58:54 +0200 [thread overview]
Message-ID: <CAJZ5v0hWdmQO_KukE7ewsPSWsYMi8K2B0rs0vRtE1t9jU=pWAQ@mail.gmail.com> (raw)
In-Reply-To: <573D9842.8040203@cn.fujitsu.com>
On Thu, May 19, 2016 at 12:41 PM, Zhu Guihua <zhugh.fnst@cn.fujitsu.com> wrote:
> Hi Rafael,
Hi,
> This patch set was reported a kernel panic from Intel LKP team.
> I do some investigation for this. I found that this panic was caused
> because of Intel test machine. On their machine, the acpi tables has
> something wrong. The proc_id of processors which are not present
> cannot be assigned correctly, they are assigned the same value.
> The wrong value will be used by our patch, and lead to panic.
Well, if there's a system that works before your patch and doesn't
work after it, the patch has to be modified to let the system still
work.
Maybe you can detect the firmware defect in question and work around
it so as to avoid the panic?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-19 12:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 10:39 Zhu Guihua
2016-05-19 10:39 ` [PATCH v7 1/5] x86, memhp, numa: Online memory-less nodes at boot time Zhu Guihua
2016-05-19 10:40 ` [PATCH v7 2/5] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus " Zhu Guihua
2016-05-19 10:40 ` [PATCH v7 3/5] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping Zhu Guihua
2016-05-19 10:40 ` [PATCH v7 4/5] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Zhu Guihua
2016-05-19 10:40 ` [PATCH v7 5/5] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Zhu Guihua
2016-05-19 10:41 ` [PATCH v7 0/5] Make cpuid <-> nodeid mapping persistent Zhu Guihua
2016-05-19 12:58 ` Rafael J. Wysocki [this message]
2016-05-19 14:46 ` Peter Zijlstra
2016-05-23 7:02 ` Zhu Guihua
2016-05-25 20:37 ` Tejun Heo
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='CAJZ5v0hWdmQO_KukE7ewsPSWsYMi8K2B0rs0vRtE1t9jU=pWAQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chen.tang@easystack.cn \
--cc=cl@linux.com \
--cc=gongzhaogang@inspur.com \
--cc=hpa@zytor.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mika.j.penttila@gmail.com \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=x86@kernel.org \
--cc=yasu.isimatu@gmail.com \
--cc=zhugh.fnst@cn.fujitsu.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