mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Thomas Lendacky <Thomas.Lendacky@amd.com>,
	Borislav Petkov <bp@alien8.de>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"Jiri Kosina" <jikos@kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Tim Chen" <tim.c.chen@linux.intel.com>,
	"Kinky Nekoboi" <kinky_nekoboi@nekoboi.moe>,
	"Merlin Büge" <toni@bluenox07.de>,
	"Timothy Pearson" <tpearson@raptorengineering.com>,
	"Vikings GmbH" <hello@vikings.net>,
	"Piotr Król" <piotr.krol@3mdeb.com>,
	coreboot@coreboot.org
Subject: Re: General protection fault in `switch_mm_irqs_off()`
Date: Wed, 2 Oct 2019 17:52:36 +0200	[thread overview]
Message-ID: <f7f07e9e-010c-68d9-77c2-16bde71a0eb8@molgen.mpg.de> (raw)
In-Reply-To: <a536de63-bfbf-01dc-6fa0-90ccc3f759f1@amd.com>


[-- Attachment #1.1: Type: text/plain, Size: 6268 bytes --]

[CC: +affected coreboot folks, +coreboot mailing list]

Dear Thomas,


More affected people discussed this issue on the coreboot mailing list [1].

On 2019-01-14 18:37, Lendacky, Thomas wrote:
> On 1/14/19 11:09 AM, Paul Menzel wrote:

>> On 01/14/19 18:00, Lendacky, Thomas wrote:
>>> On 1/10/19 12:34 PM, Lendacky, Thomas wrote:
>>>> On 1/10/19 10:49 AM, Paul Menzel wrote:
>>>>> Dear Boris, dear Thomas,
>>>>>
>>>>>
>>>>> On 01/10/19 17:00, Borislav Petkov wrote:
>>>>>> On Thu, Jan 10, 2019 at 02:57:40PM +0100, Paul Menzel wrote:
>>>>>>> Thank you very much. Indeed, the machine does not crash. I used Linus’
>>>>>>> master branch for testing, and applied your patch on top. Please find
>>>>>>> the full log attached.
>>>>>>
>>>>>>> 80.649: [    3.197107] Spectre V2 : spectre_v2_user_select_mitigation: set X86_FEATURE_USE_IBPB
>>>>>>
>>>>>> This is amazing.
>>>>>>
>>>>>> Ok, next diff, same exercise. Thx.> 
>>>>>> ---
>>>>>> diff --git a/arch/x86/include/asm/nospec-branch.h b/arch/x86/include/asm/nospec-branch.h
>>>>>> index dad12b767ba0..528ef8336f5f 100644
>>>>>> --- a/arch/x86/include/asm/nospec-branch.h
>>>>>> +++ b/arch/x86/include/asm/nospec-branch.h
>>>>>> @@ -284,6 +284,12 @@ static inline void indirect_branch_prediction_barrier(void)
>>>>>>  {
>>>>>>  	u64 val = PRED_CMD_IBPB;
>>>>>>  
>>>>>> +	if (WARN_ON(boot_cpu_has(X86_FEATURE_USE_IBPB))) {
>>>>>> +		pr_info("%s: c: %px, array: 0x%x\n",
>>>>>> +			__func__, &boot_cpu_data, boot_cpu_data.x86_capability[7]);
>>>>>> +		return;
>>>>>> +	}
>>>>>> +
>>>>>>  	alternative_msr_write(MSR_IA32_PRED_CMD, val, X86_FEATURE_USE_IBPB);
>>>>>>  }
>>>>>>  
>>>>>> diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
>>>>>> index 8654b8b0c848..e818e5abe611 100644
>>>>>> --- a/arch/x86/kernel/cpu/bugs.c
>>>>>> +++ b/arch/x86/kernel/cpu/bugs.c
>>>>>> @@ -371,6 +371,9 @@ spectre_v2_user_select_mitigation(enum spectre_v2_mitigation_cmd v2_cmd)
>>>>>>  	if (boot_cpu_has(X86_FEATURE_IBPB)) {
>>>>>>  		setup_force_cpu_cap(X86_FEATURE_USE_IBPB);
>>>>>>  
>>>>>> +		pr_err("%s: set X86_FEATURE_USE_IBPB, c: %px, array: 0x%x\n",
>>>>>> +			__func__, &boot_cpu_data, boot_cpu_data.x86_capability[7]);
>>>>>> +
>>>>>>  		switch (cmd) {
>>>>>>  		case SPECTRE_V2_USER_CMD_FORCE:
>>>>>>  		case SPECTRE_V2_USER_CMD_PRCTL_IBPB:
>>>>>> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
>>>>>> index cb28e98a0659..8566737fa500 100644
>>>>>> --- a/arch/x86/kernel/cpu/common.c
>>>>>> +++ b/arch/x86/kernel/cpu/common.c
>>>>>> @@ -765,6 +765,9 @@ static void apply_forced_caps(struct cpuinfo_x86 *c)
>>>>>>  		c->x86_capability[i] &= ~cpu_caps_cleared[i];
>>>>>>  		c->x86_capability[i] |= cpu_caps_set[i];
>>>>>>  	}
>>>>>> +
>>>>>> +	if (c == &boot_cpu_data)
>>>>>> +		pr_info("%s: c: %px, array: 0x%x\n", __func__, c, c->x86_capability[7]);
>>>>>>  }
>>>>>>  
>>>>>>  static void init_speculation_control(struct cpuinfo_x86 *c)
>>>>>> @@ -778,6 +781,10 @@ static void init_speculation_control(struct cpuinfo_x86 *c)
>>>>>>  	if (cpu_has(c, X86_FEATURE_SPEC_CTRL)) {
>>>>>>  		set_cpu_cap(c, X86_FEATURE_IBRS);
>>>>>>  		set_cpu_cap(c, X86_FEATURE_IBPB);
>>>>>> +
>>>>>> +		pr_info("%s: X86_FEATURE_SPEC_CTRL: c: %px, array: 0x%x, CPUID: 0x%x\n",
>>>>>> +			__func__, c, c->x86_capability[7], cpuid_edx(7));
>>>>>> +
>>>>>>  		set_cpu_cap(c, X86_FEATURE_MSR_SPEC_CTRL);
>>>>>>  	}
>>>>>>  
>>>>>> @@ -793,9 +800,13 @@ static void init_speculation_control(struct cpuinfo_x86 *c)
>>>>>>  		set_cpu_cap(c, X86_FEATURE_MSR_SPEC_CTRL);
>>>>>>  	}
>>>>>>  
>>>>>> -	if (cpu_has(c, X86_FEATURE_AMD_IBPB))
>>>>>> +	if (cpu_has(c, X86_FEATURE_AMD_IBPB)) {
>>>>>>  		set_cpu_cap(c, X86_FEATURE_IBPB);
>>>>>>  
>>>>>> +		pr_info("%s: X86_FEATURE_AMD_IBPB: c: %px, array: 0x%x, CPUID: 0x%x\n",
>>>>>> +			__func__, c, c->x86_capability[7], cpuid_ebx(0x80000008));
>>>>>> +	}
>>>>>> +
>>>>>>  	if (cpu_has(c, X86_FEATURE_AMD_STIBP)) {
>>>>>>  		set_cpu_cap(c, X86_FEATURE_STIBP);
>>>>>>  		set_cpu_cap(c, X86_FEATURE_MSR_SPEC_CTRL);
>>>>>
>>>>> Please find the logs attached.
>>>>
>>>> Ah, so the CPUID value is showing X86_FEATURE_AMD_IBPB (not sure why the
>>>> cpuid command was showing a value of zero for EBX in your previous email).
>>>> Let me see what I can find out about this processor/firmware relation. I
>>>> wouldn't expect to see the #GP given that the firmware says IBPB is
>>>> supported.
>>>
>>> I'm not able to reproduce this issue on my family 21, model 1, stepping 2
>>> processor (AMD Opteron(TM) Processor 6274) as I am able to successfully
>>> write to the PRED_CMD MSR.
>>
>> It’s not exactly the same processor, but I guess the same family should be
>> good enough. What board do you have? Do you have two sockets, and both
>> populated?
> 
> Yes, It is a two-socket system with two processors installed.
> 
>> Here is an Asus KGPE-D16 with two AMD Opterons put in.
>>
>> Lastly, my microcode updates are applied in firmware, and not by GNU/Linux.
> 
> Ok, I was confused on how you had reported that, sorry.

Kinky reports, that populating the memory slots of both NUMA nodes fixes this.
Kinky, what slots do you have exactly populated?

I haven’t been able to verify that yet, but please find my output of
`sudo dmidecode -t memory` with a 8 * 16 GB system attached, which is
affected.

> Can we try an experiment where you use the older version of the Asus
> firmware but build an initramfs that will perform early microcode loading?
> I'm curious if things will work when loaded via Linux.

I believe the users reported that this works.

>>> Let's check the firmware file that you're loading. The one I'm using is:
>>>
>>> $ sha1sum /lib/firmware/amd-ucode/microcode_amd_fam15h.bin 
>>> 90896256951d8edf7baf8181ae11e2dc618a5171  /lib/firmware/amd-ucode/microcode_amd_fam15h.bin
>>>
>>> Does that match what you have?
>>
>> Yes, that matches exactly.
>>
>>     90896256951d8edf7baf8181ae11e2dc618a5171  3rdparty/blobs/cpu/amd/family_15h/microcode_amd_fam15h.bin


Kind regards,

Paul


[1]: https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/QZIVOD4UADLLPZEE7MFUUTQQM343GKOC/

[-- Attachment #1.2: asus-kgpe-d16-128-gb-dmidecode-t-memory.txt --]
[-- Type: text/plain, Size: 4779 bytes --]

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0006, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: Single-bit ECC
	Maximum Capacity: 256 GB
	Error Information Handle: Not Provided
	Number Of Devices: 8

Handle 0x0007, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 0 DIMM_A2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: 4E156411
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x0008, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 0 DIMM_B2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: 4D156411
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x0009, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 0 DIMM_C2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: 9B924E13
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x000A, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 0 DIMM_D2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: BF924E13
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x000B, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 1 DIMM_A2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: 93D4D012
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x000C, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 1 DIMM_B2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: 6B6FD112
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x000D, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 1 DIMM_C2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: F1136411
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V

Handle 0x000E, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x0006
	Error Information Handle: Not Provided
	Total Width: 72 bits
	Data Width: 64 bits
	Size: 16384 MB
	Form Factor: DIMM
	Set: None
	Locator: NODE 1 DIMM_D2
	Bank Locator: Not Specified
	Type: DDR3
	Type Detail: Synchronous Registered (Buffered)
	Speed: 800 MHz
	Manufacturer: Crucial
	Serial Number: F3146411
	Asset Tag: Not Specified
	Part Number: 36KSF2G72PZ-1G6P1 
	Rank: 2
	Configured Clock Speed: 800 MHz
	Minimum Voltage: 1.35 V
	Maximum Voltage: 1.5 V
	Configured Voltage: 1.5 V


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]

  reply	other threads:[~2019-10-02 15:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 21:45 Paul Menzel
2019-01-04 12:41 ` Paul Menzel
2019-01-04 15:47   ` Borislav Petkov
2019-01-04 17:32     ` Lendacky, Thomas
2019-01-04 16:42 ` Jiri Kosina
     [not found]   ` <cb7ba667-562b-1e4c-f16e-7c11804bc98a@molgen.mpg.de>
2019-01-09 13:16     ` Thomas Gleixner
2019-01-09 13:35       ` Paul Menzel
2019-01-09 14:29         ` Lendacky, Thomas
2019-01-09 14:34           ` Paul Menzel
2019-01-09 16:15             ` Lendacky, Thomas
2019-01-09 16:34               ` Paul Menzel
2019-01-09 21:11                 ` Borislav Petkov
     [not found]                   ` <9bbcbaa7-b164-fcef-0588-7c5f25aa2440@molgen.mpg.de>
2019-01-10 15:53                     ` Lendacky, Thomas
2019-01-10 16:02                       ` Borislav Petkov
2019-01-10 16:00                     ` Borislav Petkov
2019-01-10 16:49                       ` Paul Menzel
2019-01-10 18:34                         ` Lendacky, Thomas
2019-01-14 17:00                           ` Lendacky, Thomas
2019-01-14 17:09                             ` Paul Menzel
2019-01-14 17:37                               ` Lendacky, Thomas
2019-10-02 15:52                                 ` Paul Menzel [this message]
2019-01-09 13:19     ` Paul Menzel

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=f7f07e9e-010c-68d9-77c2-16bde71a0eb8@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bp@alien8.de \
    --cc=coreboot@coreboot.org \
    --cc=hello@vikings.net \
    --cc=jikos@kernel.org \
    --cc=kinky_nekoboi@nekoboi.moe \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piotr.krol@3mdeb.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.com \
    --cc=toni@bluenox07.de \
    --cc=tpearson@raptorengineering.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

all inboxes | Powered by JetHome®