From: Borislav Petkov <bp@alien8.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Tom Lendacky <thomas.lendacky@amd.com>
Cc: x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: General protection fault in `switch_mm_irqs_off()`
Date: Fri, 4 Jan 2019 16:47:10 +0100 [thread overview]
Message-ID: <20190104154710.GA18252@nazgul.tnic> (raw)
In-Reply-To: <65b3aa5c-c11b-6435-5761-3f1489f18ce5@molgen.mpg.de>
On Fri, Jan 04, 2019 at 01:41:25PM +0100, Paul Menzel wrote:
> Dear Linux folks,
>
>
> On 01/03/19 22:45, Paul Menzel wrote:
>
> > On the server board Asus KGPE-D16 with AMD Opteron 6278 processor updating the microcode update in the firmware from 0x0600062e to 0x0600063e seems to cause a general protection fault with Linux 4.14.87 and 4.20-rc7.
> >
> >> 46.859: [ 7.573240] microcode: CPU31: patch_level=0x0600063e
> >> 46.859: [ 7.578507] microcode: Microcode Update Driver: v2.2.
> >> 46.860: [ 7.578539] sched_clock: Marking stable (6510054745, 1068444659)->(7999876773, -421377369)
> >> 46.860: [ 7.593013] registered taskstats version 1
> >> 46.861: [ 7.598091] rtc_cmos 00:00: setting system clock to 2000-01-01 08:01:51 UTC (946713711)
> >> 46.862: [ 7.606575] ALSA device list:
> >> 46.862: [ 7.609802] No soundcards found.
> >> 46.865: [ 7.615887] Freeing unused kernel image memory: 1564K
> >> 46.871: [ 7.627073] Write protecting the kernel read-only data: 20480k
> >> 46.872: [ 7.634366] Freeing unused kernel image memory: 2016K
> >> 46.873: [ 7.640297] Freeing unused kernel image memory: 584K
> >> 46.874: [ 7.645521] Run /init as init process
> >> 46.877: [ 7.652262] general protection fault: 0000 [#1] SMP NOPTI
> >> 46.877: [ 7.657931] CPU: 18 PID: 0 Comm: swapper/18 Not tainted 4.20.0-rc7.mx64.237 #1
> >> 46.877: [ 7.665514] Hardware name: ASUS KGPE-D16/KGPE-D16, BIOS 4.9-103-g637bef2037 01/02/2019
> >> 46.878: [ 7.673804] RIP: 0010:switch_mm_irqs_off+0xb2/0x640
> >> 46.878: [ 7.678948] Code: 48 c1 ef 09 83 e7 01 48 09 c7 65 48 8b 05 8e 34 fc 7e 48 39 c7 74 15 48 09 f8 a8 01 74 0e b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 65 48 89 3d 6c 34 fc 7e 8b 05 9a ef a7 01 85 c0 0f 8f 41 04
> >> 46.879: [ 7.698394] RSP: 0018:ffffc90006343e20 EFLAGS: 00010046
> >> 46.879: [ 7.703844] RAX: 0000000000000001 RBX: ffff88981ca0b800 RCX: 0000000000000049
> >> 46.879: [ 7.711238] RDX: 0000000000000000 RSI: ffff88981b87cf80 RDI: ffff88981ca0b800
> >> 46.880: [ 7.718665] RBP: ffffc90006343e70 R08: 00000001c81bec00 R09: 0000000000000000
> >> 46.880: [ 7.726092] R10: ffffc90006343e88 R11: 0000000000000000 R12: ffffffff82479b40
> >> 46.880: [ 7.733494] R13: 0000000000000000 R14: 0000000000000012 R15: ffff88981dd50080
> >> 46.881: [ 7.740853] FS: 0000000000000000(0000) GS:ffff88981fa80000(0000) knlGS:0000000000000000
> >> 46.881: [ 7.749318] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> 46.881: [ 7.755281] CR2: 0000000000000000 CR3: 000000000240a000 CR4: 00000000000406e0
> >> 46.881: [ 7.762761] Call Trace:
> >> 46.881: [ 7.765369] ? __schedule+0x1b9/0x7b0
> >> 46.882: [ 7.769253] __schedule+0x1b9/0x7b0
> >> 46.882: [ 7.772930] schedule_idle+0x1e/0x40
> >> 46.882: [ 7.776744] do_idle+0x146/0x200
> >> 46.882: [ 7.780181] cpu_startup_entry+0x19/0x20
> >> 46.883: [ 7.784274] start_secondary+0x183/0x1b0
> >> 46.883: [ 7.788409] secondary_startup_64+0xa4/0xb0
> >> 46.883: [ 7.792766] Modules linked in:
> >> 46.883: [ 7.796105] ---[ end trace a423e363fe1ecf67 ]---
> >> 46.884: [ 7.800939] RIP: 0010:switch_mm_irqs_off+0xb2/0x640
> >> 46.884: [ 7.806048] Code: 48 c1 ef 09 83 e7 01 48 09 c7 65 48 8b 05 8e 34 fc 7e 48 39 c7 74 15 48 09 f8 a8 01 74 0e b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 65 48 89 3d 6c 34 fc 7e 8b 05 9a ef a7 01 85 c0 0f 8f 41 04
> >> 46.884: [ 7.825440] RSP: 0018:ffffc90006343e20 EFLAGS: 00010046
> >> 46.885: [ 7.830855] RAX: 0000000000000001 RBX: ffff88981ca0b800 RCX: 0000000000000049
> >> 46.885: [ 7.838230] RDX: 0000000000000000 RSI: ffff88981b87cf80 RDI: ffff88981ca0b800
> >> 46.885: [ 7.845614] RBP: ffffc90006343e70 R08: 00000001c81bec00 R09: 0000000000000000
> >> 46.886: [ 7.853047] R10: ffffc90006343e88 R11: 0000000000000000 R12: ffffffff82479b40
> >> 46.886: [ 7.860427] R13: 0000000000000000 R14: 0000000000000012 R15: ffff88981dd50080
> >> 46.886: [ 7.867862] FS: 0000000000000000(0000) GS:ffff88981fa80000(0000) knlGS:0000000000000000
> >> 46.886: [ 7.876320] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> 46.887: [ 7.882351] CR2: 0000000000000000 CR3: 000000000240a000 CR4: 00000000000406e0
> >> 46.887: [ 7.889746] Kernel panic - not syncing: Attempted to kill the idle task!
> >> 46.888: [ 7.896907] Kernel Offset: disabled
> >> 46.888: [ 7.900558] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---
> >
> > Please find the whole log, including the coreboot messages, attached. The time stamps in the beginning are from the script `readserial.py` from the SeaBIOS repository.
> >
> > Do you have an idea what is going on, and how to fix it?
>
> Decoding the code, give the output below.
>
> ```
> $ scripts/decodecode < /dev/shm/test.log
> [ 7.806048] Code: 48 c1 ef 09 83 e7 01 48 09 c7 65 48 8b 05 8e 34 fc 7e 48 39 c7 74 15 48 09 f8 a8 01 74 0e b9 49 00 00 00 b8 01 00 00 00 31 d2 <0f> 30 65 48 89 3d 6c 34 fc 7e 8b 05 9a ef a7 01 85 c0 0f 8f 41 04
> All code
> ========
> 0: 48 c1 ef 09 shr $0x9,%rdi
> 4: 83 e7 01 and $0x1,%edi
> 7: 48 09 c7 or %rax,%rdi
> a: 65 48 8b 05 8e 34 fc mov %gs:0x7efc348e(%rip),%rax # 0x7efc34a0
> 11: 7e
> 12: 48 39 c7 cmp %rax,%rdi
> 15: 74 15 je 0x2c
> 17: 48 09 f8 or %rdi,%rax
> 1a: a8 01 test $0x1,%al
> 1c: 74 0e je 0x2c
> 1e: b9 49 00 00 00 mov $0x49,%ecx
> 23: b8 01 00 00 00 mov $0x1,%eax
> 28: 31 d2 xor %edx,%edx
> 2a:* 0f 30 wrmsr <-- trapping instruction
> 2c: 65 48 89 3d 6c 34 fc mov %rdi,%gs:0x7efc346c(%rip) # 0x7efc34a0
> 33: 7e
> 34: 8b 05 9a ef a7 01 mov 0x1a7ef9a(%rip),%eax # 0x1a7efd4
> 3a: 85 c0 test %eax,%eax
> 3c: 0f .byte 0xf
> 3d: 8f 41 04 popq 0x4(%rcx)
>
> Code starting with the faulting instruction
> ===========================================
> 0: 0f 30 wrmsr
> 2: 65 48 89 3d 6c 34 fc mov %rdi,%gs:0x7efc346c(%rip) # 0x7efc3476
> 9: 7e
> a: 8b 05 9a ef a7 01 mov 0x1a7ef9a(%rip),%eax # 0x1a7efaa
> 10: 85 c0 test %eax,%eax
> 12: 0f .byte 0xf
> 13: 8f 41 04 popq 0x4(%rcx)
> ```
>
> So the problem is with the instruction *wrmsr* [1].
>
> The content of ECX, which according to [1] is written to, is not
> in the logs though, as far as I can see.
Of course it is:
> 1e: b9 49 00 00 00 mov $0x49,%ecx
which is strange.
Tom, is patch_level=0x0600063e on BD supposed to #GP when writing
MSR_IA32_PRED_CMD...
Thx.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2019-01-04 15:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 21:45 General protection fault in `switch_mm_irqs_off()` Paul Menzel
2019-01-04 12:41 ` Paul Menzel
2019-01-04 15:47 ` Borislav Petkov [this message]
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
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=20190104154710.GA18252@nazgul.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.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