From: Bob Peterson <rpeterso@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Andreas Gruenbacher <agruenba@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Whitehouse <swhiteho@redhat.com>,
Mel Gorman <mgorman@techsingularity.net>,
linux-mm <linux-mm@kvack.org>
Subject: Re: CONFIG_VMAP_STACK, on-stack struct, and wake_up_bit
Date: Thu, 27 Oct 2016 14:51:30 -0400 (EDT) [thread overview]
Message-ID: <411894642.13576957.1477594290544.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161027123623.j2jri5bandimboff@pd.tnic>
| Here's a fix which works here - I'd appreciate it if you ran it and
| checked the microcode was applied correctly, i.e.:
|
| $ dmesg | grep -i microcode
|
| before and after the patch. Please paste that output in a mail too.
Hi Borislav,
Sorry it's taken me so long. I've been having issues.
I couldn't recreate that first boot failure, even using .config.old,
and even after removing (rm -fR) my linux.git and untarring it from the
original tarball, doing a make clean, etc.
The output before and after your new patch are the same (except for the times):
# dmesg | grep -i microcode
[ 5.291679] microcode: microcode updated early to new patch_level=0x010000d9
[ 5.298761] microcode: CPU0: patch_level=0x010000d9
[ 5.303648] microcode: CPU1: patch_level=0x010000d9
[ 5.308529] microcode: CPU2: patch_level=0x010000d9
[ 5.313414] microcode: CPU3: patch_level=0x010000d9
[ 5.360834] microcode: CPU4: patch_level=0x010000d9
[ 5.365719] microcode: CPU5: patch_level=0x010000d9
[ 5.370602] microcode: CPU6: patch_level=0x010000d9
[ 5.375486] microcode: CPU7: patch_level=0x010000d9
[ 5.380372] microcode: CPU8: patch_level=0x010000d9
[ 5.385256] microcode: CPU9: patch_level=0x010000d9
[ 5.390142] microcode: CPU10: patch_level=0x010000d9
[ 5.395102] microcode: CPU11: patch_level=0x010000d9
[ 5.437813] microcode: CPU12: patch_level=0x010000d9
[ 5.442785] microcode: CPU13: patch_level=0x010000d9
[ 5.447755] microcode: CPU14: patch_level=0x010000d9
[ 5.452724] microcode: CPU15: patch_level=0x010000d9
[ 5.457756] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
# uname -a
Linux intec2 4.9.0-rc2+ #2 SMP Thu Oct 27 14:29:32 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
Regards,
Bob Peterson
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Andreas Gruenbacher <agruenba@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Steven Whitehouse <swhiteho@redhat.com>,
Mel Gorman <mgorman@techsingularity.net>,
linux-mm <linux-mm@kvack.org>
Subject: Re: CONFIG_VMAP_STACK, on-stack struct, and wake_up_bit
Date: Thu, 27 Oct 2016 14:51:30 -0400 (EDT) [thread overview]
Message-ID: <411894642.13576957.1477594290544.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20161027123623.j2jri5bandimboff@pd.tnic>
| Here's a fix which works here - I'd appreciate it if you ran it and
| checked the microcode was applied correctly, i.e.:
|
| $ dmesg | grep -i microcode
|
| before and after the patch. Please paste that output in a mail too.
Hi Borislav,
Sorry it's taken me so long. I've been having issues.
I couldn't recreate that first boot failure, even using .config.old,
and even after removing (rm -fR) my linux.git and untarring it from the
original tarball, doing a make clean, etc.
The output before and after your new patch are the same (except for the times):
# dmesg | grep -i microcode
[ 5.291679] microcode: microcode updated early to new patch_level=0x010000d9
[ 5.298761] microcode: CPU0: patch_level=0x010000d9
[ 5.303648] microcode: CPU1: patch_level=0x010000d9
[ 5.308529] microcode: CPU2: patch_level=0x010000d9
[ 5.313414] microcode: CPU3: patch_level=0x010000d9
[ 5.360834] microcode: CPU4: patch_level=0x010000d9
[ 5.365719] microcode: CPU5: patch_level=0x010000d9
[ 5.370602] microcode: CPU6: patch_level=0x010000d9
[ 5.375486] microcode: CPU7: patch_level=0x010000d9
[ 5.380372] microcode: CPU8: patch_level=0x010000d9
[ 5.385256] microcode: CPU9: patch_level=0x010000d9
[ 5.390142] microcode: CPU10: patch_level=0x010000d9
[ 5.395102] microcode: CPU11: patch_level=0x010000d9
[ 5.437813] microcode: CPU12: patch_level=0x010000d9
[ 5.442785] microcode: CPU13: patch_level=0x010000d9
[ 5.447755] microcode: CPU14: patch_level=0x010000d9
[ 5.452724] microcode: CPU15: patch_level=0x010000d9
[ 5.457756] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
# uname -a
Linux intec2 4.9.0-rc2+ #2 SMP Thu Oct 27 14:29:32 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
Regards,
Bob Peterson
next prev parent reply other threads:[~2016-10-27 18:52 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 12:51 CONFIG_VMAP_STACK, on-stack struct, and wake_up_bit Andreas Gruenbacher
2016-10-26 15:51 ` Andy Lutomirski
2016-10-26 16:32 ` Linus Torvalds
2016-10-26 16:32 ` Linus Torvalds
2016-10-26 17:15 ` Linus Torvalds
2016-10-26 17:58 ` Linus Torvalds
2016-10-26 17:58 ` Linus Torvalds
2016-10-26 18:04 ` Bob Peterson
2016-10-26 18:04 ` Bob Peterson
2016-10-26 18:10 ` Linus Torvalds
2016-10-26 18:10 ` Linus Torvalds
2016-10-26 19:11 ` Bob Peterson
2016-10-26 19:11 ` Bob Peterson
2016-10-26 21:01 ` Bob Peterson
2016-10-26 21:01 ` Bob Peterson
2016-10-26 21:30 ` Linus Torvalds
2016-10-26 21:30 ` Linus Torvalds
2016-10-26 22:45 ` Borislav Petkov
2016-10-26 22:45 ` Borislav Petkov
2016-10-26 23:13 ` Borislav Petkov
2016-10-26 23:13 ` Borislav Petkov
2016-10-27 0:37 ` Bob Peterson
2016-10-27 12:36 ` Borislav Petkov
2016-10-27 12:36 ` Borislav Petkov
2016-10-27 18:51 ` Bob Peterson [this message]
2016-10-27 18:51 ` Bob Peterson
2016-10-27 19:19 ` Borislav Petkov
2016-10-27 19:19 ` Borislav Petkov
2016-10-27 21:03 ` Bob Peterson
2016-10-27 21:03 ` Bob Peterson
2016-10-27 21:19 ` Borislav Petkov
2016-10-27 21:19 ` Borislav Petkov
2016-10-28 8:37 ` [tip:x86/urgent] x86/microcode/AMD: Fix more fallout from CONFIG_RANDOMIZE_MEMORY=y tip-bot for Borislav Petkov
2016-10-28 8:37 ` tip-bot for Borislav Petkov
2016-10-26 20:31 ` CONFIG_VMAP_STACK, on-stack struct, and wake_up_bit Mel Gorman
2016-10-26 20:31 ` Mel Gorman
2016-10-26 21:26 ` Linus Torvalds
2016-10-26 21:26 ` Linus Torvalds
2016-10-26 22:03 ` Mel Gorman
2016-10-26 22:03 ` Mel Gorman
2016-10-26 22:09 ` Linus Torvalds
2016-10-26 22:09 ` Linus Torvalds
2016-10-26 23:07 ` Mel Gorman
2016-10-26 23:07 ` Mel Gorman
2016-10-27 8:08 ` Peter Zijlstra
2016-10-27 8:08 ` Peter Zijlstra
2016-10-27 9:07 ` Mel Gorman
2016-10-27 9:07 ` Mel Gorman
2016-10-27 9:44 ` Peter Zijlstra
2016-10-27 9:44 ` Peter Zijlstra
2016-10-27 9:59 ` Mel Gorman
2016-10-27 9:59 ` Mel Gorman
2016-10-27 11:56 ` Nicholas Piggin
2016-10-27 11:56 ` Nicholas Piggin
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=411894642.13576957.1477594290544.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
--cc=agruenba@redhat.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mgorman@techsingularity.net \
--cc=peterz@infradead.org \
--cc=swhiteho@redhat.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.