linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pu Wen <puwen@hygon.cn>
To: Rong Chen <rong.a.chen@intel.com>
Cc: bp@alien8.de, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, thomas.lendacky@amd.com,
	helgaas@kernel.org, linux-kernel@vger.kernel.org,
	linux-arch@vger.kernel.org, linux-pci@vger.kernel.org,
	lkp@01.org
Subject: Re: [LKP] [x86/pci] 7ffb31888c: PANIC:early_exception
Date: Thu, 20 Sep 2018 16:47:19 +0800	[thread overview]
Message-ID: <7e9e862a-e890-775f-ed92-74c591c7deb6@hygon.cn> (raw)
In-Reply-To: <dfc09a36-cfc5-0479-a862-696c224f9a19@intel.com>

On 2018/9/20 8:26, Rong Chen wrote:
> On 09/19/2018 09:53 PM, Pu Wen wrote:
>> I cannot reproduce this panic on Hygon Dhyana platform. I tired lkp-tests
>> both in Ubuntu 16.04 (with gcc-5) and Ubuntu 18.04 (with gcc-7).
>> What kind of host do you use to run the qemu? A Intel one or AMD one?
> It's a Intel one,
> 
> model: Nehalem-EX
> memory: 224G
> nr_node: 4
> nr_cpu: 64
> nr_socket: 4
> brand: Intel(R) Xeon(R) CPU X7560 @ 2.27GHz

I reproduced the PANIC by running lkp-tests with a Intel machine.

The reason is that the function early_is_amd_nb is called even if
running on Intel machine. At this case the misc_ids is NULL so the
PANIC occur.

I'll rework a patch to solve this problem, either restore the default
value of misc_ids with the original AMD one or not call early_is_amd_nb
on Intel platform.

-- 
Regards,
Pu Wen

  parent reply	other threads:[~2018-09-20  8:47 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:28 [PATCH v7 00/16] Add support for Hygon Dhyana Family 18h processor Pu Wen
2018-09-17 13:28 ` Pu Wen
2018-09-17 13:29 ` [PATCH v7 01/16] x86/cpu: Create Hygon Dhyana architecture support file Pu Wen
2018-09-17 13:29   ` Pu Wen
2018-09-17 13:29 ` [PATCH v7 02/16] x86/cpu: Get cache info and setup cache cpumap for Hygon Dhyana Pu Wen
2018-09-17 13:29   ` Pu Wen
2018-09-17 13:29 ` [PATCH v7 03/16] x86/cpu/mtrr: Support TOP_MEM2 and get MTRR number Pu Wen
2018-09-17 13:29   ` Pu Wen
2018-09-17 13:30 ` [PATCH v7 04/16] x86/smpboot: SMP init no delay and not flush caches before sleep Pu Wen
2018-09-17 13:30   ` Pu Wen
2018-09-17 13:30 ` [PATCH v7 05/16] perf/x86: Add Hygon Dhyana support to PMU infrastructure Pu Wen
2018-09-17 13:30   ` Pu Wen
2018-09-17 13:30 ` [PATCH v7 06/16] x86/alternative: Init ideal_nops for Hygon Dhyana Pu Wen
2018-09-17 13:30   ` Pu Wen
2018-09-17 13:30 ` [PATCH v7 07/16] x86/pci: Add Hygon Dhyana support to PCI and north bridge Pu Wen
2018-09-17 13:30   ` Pu Wen
2018-09-19  3:19   ` [LKP] [x86/pci] 7ffb31888c: PANIC:early_exception kernel test robot
2018-09-19 13:53     ` Pu Wen
2018-09-19 13:53       ` Pu Wen
2018-09-20  0:26       ` Rong Chen
2018-09-20  0:26         ` Rong Chen
2018-09-20  8:47         ` Pu Wen [this message]
2018-09-20  8:47           ` Pu Wen
2018-09-20  9:39           ` Thomas Gleixner
2018-09-20  9:39             ` Thomas Gleixner
2018-09-23 10:05             ` Pu Wen
2018-09-23 10:05               ` Pu Wen
2018-09-17 13:31 ` [PATCH v7 08/16] x86/apic: Add Hygon Dhyana support to APIC Pu Wen
2018-09-17 13:31   ` Pu Wen
2018-09-17 13:31 ` [PATCH v7 09/16] x86/bugs: Add mitigation to spectre and no meltdown for Hygon Dhyana Pu Wen
2018-09-17 13:31   ` Pu Wen
2018-09-17 13:32 ` [PATCH v7 10/16] x86/mce: Add Hygon Dhyana support to MCE infrastructure Pu Wen
2018-09-17 13:32   ` Pu Wen
2018-09-17 13:32 ` [PATCH v7 11/16] x86/kvm: Add Hygon Dhyana support to KVM infrastructure Pu Wen
2018-09-17 13:32   ` Pu Wen
2018-09-17 13:33 ` [PATCH v7 12/16] x86/xen: Add Hygon Dhyana support to Xen Pu Wen
2018-09-17 13:33   ` Pu Wen
2018-09-17 13:33 ` [PATCH v7 13/16] ACPI, x86: Add Hygon Dhyana support Pu Wen
2018-09-17 13:33   ` Pu Wen
2018-09-17 13:33 ` [PATCH v7 14/16] cpufreq, " Pu Wen
2018-09-17 13:33   ` Pu Wen
2018-09-17 13:34 ` [PATCH v7 15/16] EDAC, amd64: " Pu Wen
2018-09-17 13:34   ` Pu Wen
2018-09-17 13:35 ` [PATCH v7 16/16] cpupower, x86: " Pu Wen
2018-09-17 13:35   ` Pu Wen

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=7e9e862a-e890-775f-ed92-74c591c7deb6@hygon.cn \
    --to=puwen@hygon.cn \
    --cc=bp@alien8.de \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mingo@redhat.com \
    --cc=rong.a.chen@intel.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@kernel.org \
    /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).