* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
@ 2016-10-21 16:19 sonofagun
2016-10-21 16:47 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-21 16:19 UTC (permalink / raw)
To: linux-kernel
Sorry for the late reply! This machine has caused nothing but trouble.
HP will not fix it and we will not choose their laptops anymore...
My brother told me that we apply a quirk to the last Ontario APUs that
do not need it but I did not think it would be an issue since they have
fixed the error.
It seems better this way so that only affected APUs are patched. Be
patient, we are compiling the new patch right now but compiling is run
on a different high end AMD machine of my brother. Tomorrow I will have
access to the laptop and I will update the kernel and send you the V2
patch. Compiling to that laptop would possibly need a whole day even
with AC power!
Do you want /proc/cpuinfo on the V2 patch e-mail? Both CPUs needed?
Here is a dump from an older installation some months ago I kept on my
disk(tomorrow I will dump it again if you want):
processor : 0
vendor_id : AuthenticAMD
cpu family : 20
model : 2
model name : AMD E-300 APU with Radeon(tm) HD Graphics
stepping : 0
microcode : 0x5000119
cpu MHz : 1300.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate
vmmcall arat npt lbrv svm_lock nrip_save pausefilter
bugs : fxsave_leak sysret_ss_attrs
bogomips : 2594.69
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
processor : 1
vendor_id : AuthenticAMD
cpu family : 20
model : 2
model name : AMD E-300 APU with Radeon(tm) HD Graphics
stepping : 0
microcode : 0x5000119
cpu MHz : 1300.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid
aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate
vmmcall arat npt lbrv svm_lock nrip_save pausefilter
bugs : fxsave_leak sysret_ss_attrs
bogomips : 2594.69
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
> Then, keep that *whole* changelog above when sending v2 of the patch
What do you mean? It is not clear to me, Do you mean all the info we
wrote on the e-mail, your comments or both?
We have many AMD machines and we will need your help next week to patch
our Phenom(tm) II X6. Let's finish this
patch first and we will fix that too but it appears to be much more
difficult...
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-21 16:19 [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun
@ 2016-10-21 16:47 ` Borislav Petkov
2016-10-21 21:51 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-21 16:47 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
Hi Ioannis,
first of all, when you reply to a mail on lkml, please use the "reply-to-all"
functionality of your mail client - otherwise replies might get missed on such a
high volume mailing list.
On Fri, Oct 21, 2016 at 07:19:07PM +0300, sonofagun@openmailbox.org wrote:
> Sorry for the late reply! This machine has caused nothing but trouble. HP
> will not fix it and we will not choose their laptops anymore...
You're not the only one making this experience.
> My brother told me that we apply a quirk to the last Ontario APUs that do
> not need it but I did not think it would be an issue since they have fixed
> the error.
No, you need to apply the fix only on the models which need it.
> It seems better this way so that only affected APUs are patched. Be patient,
> we are compiling the new patch right now but compiling is run on a different
> high end AMD machine of my brother. Tomorrow I will have access to the
> laptop and I will update the kernel and send you the V2 patch. Compiling to
> that laptop would possibly need a whole day even with AC power!
You can build somewhere else and copy the kernel to the laptop. That's
how I do it.
> Do you want /proc/cpuinfo on the V2 patch e-mail? Both CPUs needed?
No, I just wanted to see them and you've pasted them here. Thanks.
> Here is a dump from an older installation some months ago I kept on my
> disk(tomorrow I will dump it again if you want):
No need, one is enough :)
> > Then, keep that *whole* changelog above when sending v2 of the patch
> What do you mean? It is not clear to me, Do you mean all the info we wrote
> on the e-mail, your comments or both?
All the info you wrote in the first mail.
> We have many AMD machines and we will need your help next week to patch our
> Phenom(tm) II X6.
Why, what's wrong with that one? That one should be all fixed! :-)
I have such box too and it runs fine.
> Let's finish this patch first and we will fix that too but it appears
> to be much more difficult...
Don't hesitate to ask if you need help...
HTH.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-21 16:47 ` Borislav Petkov
@ 2016-10-21 21:51 ` sonofagun
2016-10-21 23:01 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-21 21:51 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
Thank you for your time! I have chosen reply to list and all recipients,
it must work now.
My brother rejected the proposed patch because it does not provide
equivalent functionality with the original.
Our initial patch would fix 3 broken models and 1 working model. Your
patch will only work for 1 model. Only machines having our APU will be
fixed. All B0 APUs will be unpatched. This is not right. Check the
revision guide to verify that.
To avoid unneeded complexity we propose this patch as V2, do you agree?
+#define MSR_AMD64_IC_CFG 0xC0011021
+
+static void init_amd_on(struct cpuinfo_x86 *c)
+{
+ /*
+ * Apply erratum 688 fix so machines without a BIOS
+ * fix work.
+ */
+
+ u32 val = pci_read_config(0, 0x18, 0x4, 0x164);
+
+ if (!(val & BIT(2))) {
+ msr_set_bit(MSR_AMD64_IC_CFG, 3);
+ msr_set_bit(MSR_AMD64_IC_CFG, 14);
+}
static void init_amd_bd(struct cpuinfo_x86 *c)
{
u64 value;
@@ -738,6 +750,7 @@ static void init_amd(struct cpuinfo_x86
case 0xf: init_amd_k8(c); break;
case 0x10: init_amd_gh(c); break;
case 0x12: init_amd_ln(c); break;
+ case 0x14: init_amd_on(c); break;
case 0x15: init_amd_bd(c); break;
}
Please advice to proceed!
> Why, what's wrong with that one? That one should be all fixed! :-)
>
> I have such box too and it runs fine.
erratum 721 :-(
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-21 21:51 ` sonofagun
@ 2016-10-21 23:01 ` Borislav Petkov
2016-10-22 11:16 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-21 23:01 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Sat, Oct 22, 2016 at 12:51:32AM +0300, sonofagun@openmailbox.org wrote:
> Thank you for your time! I have chosen reply to list and all recipients, it
> must work now.
Yes, exactly what I had in mind.
> My brother rejected the proposed patch because it does not provide
> equivalent functionality with the original.
>
> Our initial patch would fix 3 broken models and 1 working model. Your patch
> will only work for 1 model. Only machines having our APU will be fixed. All
> B0 APUs will be unpatched. This is not right. Check the revision guide to
> verify that.
Right you are: I read too much into the description of bit 2 of
D18F4x164. Of course we want to apply that fix to to ON-Bs too.
> To avoid unneeded complexity we propose this patch as V2, do you agree?
>
> +#define MSR_AMD64_IC_CFG 0xC0011021
> +
> +static void init_amd_on(struct cpuinfo_x86 *c)
> +{
> + /*
> + * Apply erratum 688 fix so machines without a BIOS
> + * fix work.
> + */
> +
> + u32 val = pci_read_config(0, 0x18, 0x4, 0x164);
> +
> + if (!(val & BIT(2))) {
> + msr_set_bit(MSR_AMD64_IC_CFG, 3);
> + msr_set_bit(MSR_AMD64_IC_CFG, 14);
Yes, that should work fine.
Btw, there's missing a closing } for the if-test here.
> +}
> static void init_amd_bd(struct cpuinfo_x86 *c)
> {
> u64 value;
> @@ -738,6 +750,7 @@ static void init_amd(struct cpuinfo_x86
> case 0xf: init_amd_k8(c); break;
> case 0x10: init_amd_gh(c); break;
> case 0x12: init_amd_ln(c); break;
> + case 0x14: init_amd_on(c); break;
> case 0x15: init_amd_bd(c); break;
> }
>
> Please advice to proceed!
Right, please send a tested version of the above with the explanation
text from your initial submission.
Thanks.
> erratum 721 :-(
Hmm, interesting.
Do you have a way to trigger that one?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-21 23:01 ` Borislav Petkov
@ 2016-10-22 11:16 ` sonofagun
2016-10-22 14:12 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-22 11:16 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
Patch does not compile.
I tried to add pci.h but did nothing.
I converted pci_read_config to pci_read_config_dword but again nothing.
On 2016-10-22 02:01, Borislav Petkov wrote:
> Do you have a way to trigger that one?
To be honest I can't say. My brother's machine(s) has random crashes
from time to time. We suspect that this erratum is to blame. He must
have kept some information at least from one of those crashes but there
was no time to analyze them till now. Finding those logs on our disks
needs a big effort but it will be done! We are willing to discover the
trouble maker no matter what it takes. To do that the machine must be
stripped off from all cards and then put on quarantine. Then we can
connect it with a another machine with an RS-232 cable to see what is
wrong. After that we must test it on a different motherboard we have. I
think we have one with a BIOS from a different BIOS vendor. We will
surely inform you on this one as we can't do such a patch. So we will
focus on triggering this bug. One thing is sure, its BIOS has no
workaround for that erratum.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-22 11:16 ` sonofagun
@ 2016-10-22 14:12 ` Borislav Petkov
2016-10-23 9:39 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-22 14:12 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Sat, Oct 22, 2016 at 02:16:41PM +0300, sonofagun@openmailbox.org wrote:
> Patch does not compile.
Yeah, it needs more work.
Try the version below. It needs to be done differently because we need
PCI extended config space access to be enabled in order to check bit 2.
> To be honest I can't say. My brother's machine(s) has random crashes from
> time to time. We suspect that this erratum is to blame. He must have kept
> some information at least from one of those crashes but there was no time to
> analyze them till now. Finding those logs on our disks needs a big effort
> but it will be done! We are willing to discover the trouble maker no matter
> what it takes. To do that the machine must be stripped off from all cards
> and then put on quarantine. Then we can connect it with a another machine
> with an RS-232 cable to see what is wrong. After that we must test it on a
> different motherboard we have. I think we have one with a BIOS from a
> different BIOS vendor. We will surely inform you on this one as we can't do
> such a patch. So we will focus on triggering this bug. One thing is sure,
> its BIOS has no workaround for that erratum.
Ok, good. Let me know how it goes.
Thanks.
---
>From ddce976ba7fc44922a6c4e9e58bbdf65c65c4ae4 Mon Sep 17 00:00:00 2001
From: Borislav Petkov <bp@suse.de>
Date: Sat, 22 Oct 2016 15:23:54 +0200
Subject: [PATCH] E688, v1
Signed-off-by: Borislav Petkov <bp@suse.de>
---
diff --git a/arch/x86/kernel/amd_nb.c b/arch/x86/kernel/amd_nb.c
index 4fdf6230d93c..bfde06b1a587 100644
--- a/arch/x86/kernel/amd_nb.c
+++ b/arch/x86/kernel/amd_nb.c
@@ -15,6 +15,8 @@
static u32 *flush_words;
+#define PCI_DEVICE_ID_AMD_CNB17H_F4 0x1704
+
const struct pci_device_id amd_nb_misc_ids[] = {
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_K8_NB_MISC) },
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_10H_NB_MISC) },
@@ -24,6 +26,7 @@ const struct pci_device_id amd_nb_misc_ids[] = {
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_15H_M60H_NB_F3) },
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_16H_NB_F3) },
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_16H_M30H_NB_F3) },
+ { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_CNB17H_F3) },
{}
};
EXPORT_SYMBOL(amd_nb_misc_ids);
@@ -34,6 +37,7 @@ static const struct pci_device_id amd_nb_link_ids[] = {
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_15H_M60H_NB_F4) },
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_16H_NB_F4) },
{ PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_16H_M30H_NB_F4) },
+ { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_CNB17H_F4) },
{}
};
@@ -274,11 +278,46 @@ void amd_flush_garts(void)
}
EXPORT_SYMBOL_GPL(amd_flush_garts);
+static void __fix_erratum_688(void *info)
+{
+#define MSR_AMD64_IC_CFG 0xC0011021
+
+ msr_set_bit(MSR_AMD64_IC_CFG, 3);
+ msr_set_bit(MSR_AMD64_IC_CFG, 14);
+}
+
+/* Apply erratum 688 fix so machines without a BIOS fix work. */
+static __init void fix_erratum_688(void)
+{
+ struct pci_dev *F4;
+ u32 val;
+
+ if (boot_cpu_data.x86 != 0x14)
+ return;
+
+ if (!amd_northbridges.num)
+ return;
+
+ F4 = node_to_amd_nb(0)->link;
+ if (!F4)
+ return;
+
+ if (pci_read_config_dword(F4, 0x164, &val))
+ return;
+
+ if (val & BIT(2))
+ return;
+
+ on_each_cpu(__fix_erratum_688, NULL, 0);
+}
+
static __init int init_amd_nbs(void)
{
amd_cache_northbridges();
amd_cache_gart();
+ fix_erratum_688();
+
return 0;
}
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply related [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-22 14:12 ` Borislav Petkov
@ 2016-10-23 9:39 ` sonofagun
2016-10-23 9:57 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-23 9:39 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
Last night attempt failed as patch does not apply to 4.8. Neither 4.8.1
nor 4.8.4. Did you switch to 4.9? Please use 4.8 as we prefer to avoid
rc kernels as we had casualties in the past. Do you want to add changes
by hand?
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-23 9:39 ` sonofagun
@ 2016-10-23 9:57 ` Borislav Petkov
2016-10-23 17:06 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-23 9:57 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Sun, Oct 23, 2016 at 12:39:37PM +0300, sonofagun@openmailbox.org wrote:
> Last night attempt failed as patch does not apply to 4.8. Neither 4.8.1 nor
> 4.8.4. Did you switch to 4.9? Please use 4.8 as we prefer to avoid rc
> kernels as we had casualties in the past. Do you want to add changes by
> hand?
Are you sure you did it right?
I saved the mail I sent you before in /tmp/e688.mail.
$ git checkout v4.8.1
Previous HEAD position was e58b634ca001... Merge branch 'tip-microcode-rc1+' into rc1+1
HEAD is now at a7fac751ddba... Linux 4.8.1
$ patch -p1 --dry-run -i /tmp/e688.mail
checking file arch/x86/kernel/amd_nb.c
$ git checkout v4.8.3
Previous HEAD position was a7fac751ddba... Linux 4.8.1
HEAD is now at 1888926ea8d2... Linux 4.8.3
$ patch -p1 --dry-run -i /tmp/e688.mail
checking file arch/x86/kernel/amd_nb.c
$ git checkout v4.8
Previous HEAD position was 1888926ea8d2... Linux 4.8.3
HEAD is now at c8d2bc9bc39e... Linux 4.8
$ patch -p1 --dry-run -i /tmp/e688.mail
checking file arch/x86/kernel/amd_nb.c
Now you only have to remove "--dry-run"
Paste here the error messages when trying to apply it.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-23 9:57 ` Borislav Petkov
@ 2016-10-23 17:06 ` sonofagun
2016-10-23 17:25 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-23 17:06 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> Are you sure you did it right?
Yes and no.
I use the patchwork site and my brother uses an LKML mirror site. He
gets patches from there. This worked the with the first two patches but
the last one was a big one and that site truncated some bytes from a
line...Sorry for the trouble.
For reasons I cannot explain I haven't used git till now even though I
have downloaded it with its source files from the very first versions
that got released years ago.
Kernel is now ready and moved to USB stick. Testing is about to begin.
If everything works as expected I shall send V2 late at night! Thanks!!
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-23 17:06 ` sonofagun
@ 2016-10-23 17:25 ` Borislav Petkov
2016-10-23 21:02 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-23 17:25 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Sun, Oct 23, 2016 at 08:06:44PM +0300, sonofagun@openmailbox.org wrote:
> I use the patchwork site and my brother uses an LKML mirror site. He gets
> patches from there. This worked the with the first two patches but the last
> one was a big one and that site truncated some bytes from a line...Sorry for
> the trouble.
You can simply save the email text if your mail client doesn't mangle
white space. Alternatively, there's
https://patchwork.kernel.org/project/LKML/list/
which people do use.
> Kernel is now ready and moved to USB stick. Testing is about to begin. If
> everything works as expected I shall send V2 late at night! Thanks!!
Good.
But you don't need to send v2 - you just need to say whether my version
fixes it for you or not. If not, then I need to stare at it more. :)
In any case, I tested it on my ON-B0 box and it looked good.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-23 17:25 ` Borislav Petkov
@ 2016-10-23 21:02 ` sonofagun
2016-10-23 21:39 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-23 21:02 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> In any case, I tested it on my ON-B0 box and it looked good.
Good to hear but something is still wrong on my laptop as nothing worked
as expected :(
Since I have a working custom kernel including the fix from my original
patch it was clear from boot that the last patched kernel did not touch
the MSR we want to modify at all. The machine was slower compared with
my kernel using the original patch. As I use the show_msr option, a
quick look at the dmesg proved that easily. Nowadays that processors
have many cores, I wonder if the kernel should report which CPU MSRs are
displayed at dmesg.
Take your time to see what is wrong, we already have one working kernel
for our machine :)
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-23 21:02 ` sonofagun
@ 2016-10-23 21:39 ` Borislav Petkov
2016-10-24 11:38 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-23 21:39 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Mon, Oct 24, 2016 at 12:02:39AM +0300, sonofagun@openmailbox.org wrote:
> Good to hear but something is still wrong on my laptop as nothing worked as
> expected :(
Hmm, so did you apply the patch correctly?
Send me arch/x86/kernel/amd_nb.c after you've applied the patch.
Then, boot the kernel with my patch applied, send me full dmesg,
the .config used and do as root:
$ rdmsr --all 0xc0011021
and paste the output here please.
For that you'd need the msr-tools package and you'd need to modprobe
msr.ko if you haven't done so.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-24 11:38 ` sonofagun
@ 2016-10-24 9:35 ` Borislav Petkov
2016-10-24 13:13 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-24 9:35 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Mon, Oct 24, 2016 at 02:38:06PM +0300, sonofagun@openmailbox.org wrote:
> The patch is not equivalent to the original. As a result it behaves
> differently. To be specific, using dmesg I get the expected value from the
> affected MSR with the original patch. With the latest patch, patching of the
> MSR occurs after dmesg prints the MSR information. That is why I thought it
> did nothing.
Gah, that "show_msr" is crap - it gets issued too early and we can -
and we do - set MSRs later too. Oh and it prints only the BSP. I should
probably rip it out - there's msr-tools for that which is much better.
> rdmsr --all 0xc0011021 returns the expected results on all CPUs with both
> patches. I have the impression that the system boots slower because the fix
> is applied later compared to the original patch.
Could be - setting those bits 3 in 14 in that MSR is probably disabling
some hw features which may impact performance.
> Could you please use perf and tell me what values do you get at perf
> branch-misses right after boot on your ON-B0 box? Launching firefox with
> only one tab gives you similar numbers?
Sure, give me the exact command you're executing so that I can do it here.
> If you need anything more, feel free to ask.
Out of pure interest: do you remember how exactly you did reproduce this
issue?
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-23 21:39 ` Borislav Petkov
@ 2016-10-24 11:38 ` sonofagun
2016-10-24 9:35 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-24 11:38 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> Hmm, so did you apply the patch correctly?
Yes
The patch is not equivalent to the original. As a result it behaves
differently. To be specific, using dmesg I get the expected value from
the affected MSR with the original patch. With the latest patch,
patching of the MSR occurs after dmesg prints the MSR information. That
is why I thought it did nothing.
rdmsr --all 0xc0011021 returns the expected results on all CPUs with
both patches. I have the impression that the system boots slower because
the fix is applied later compared to the original patch.
Since the code works there is no need to attach the compile config so I
attach a dmesg and rdmsr --all 0xc0011021.
Could you please use perf and tell me what values do you get at perf
branch-misses right after boot on your ON-B0 box? Launching firefox with
only one tab gives you similar numbers?
If you need anything more, feel free to ask.
$ rdmsr --all 0xc0011021
1020c008
1020c008
$ dmesg
[ 0.000000] Linux version 4.8.4-vnl-14h-688-amd64 (root@FXLSI) (gcc
version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #1 SMP Sun Oct
23 16:19:41 EEST 2016
[ 0.000000] Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.4-vnl-14h-688-amd64
root=UUID=124d207f-6ec4-4270-a1a3-2878e0756f25 ro quiet show_msr=1
clocksource=hpet hpet=verbose acpi_sleep=s3_beep mce=bootlog
pcie_aspm.policy=powersave debug=y splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Legacy x87 FPU detected.
[ 0.000000] x86/fpu: Using 'eager' FPU context switches.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff]
usable
[ 0.000000] BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000dfb3efff]
usable
[ 0.000000] BIOS-e820: [mem 0x00000000dfb3f000-0x00000000dfbbefff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000dfbbf000-0x00000000dfebefff]
ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000dfebf000-0x00000000dfef4fff]
ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000dfef5000-0x00000000dfefffff]
usable
[ 0.000000] BIOS-e820: [mem 0x00000000dff00000-0x00000000dfffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000206ffffff]
usable
[ 0.000000] BIOS-e820: [mem 0x0000000207000000-0x000000021effffff]
reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: Hewlett-Packard Presario CQ57 Notebook PC/3577, BIOS
F.47 12/17/2011
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==>
reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x207000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-through
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0C0000000 mask FE0000000 write-back
[ 0.000000] 3 base 0DFEBD000 mask FFFFFF000 uncachable
[ 0.000000] 4 base 0FFE00000 mask FFFE00000 write-protect
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] TOM2: 000000021f000000 aka 8688M
[ 0.000000] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC-
WT
[ 0.000000] e820: last_pfn = 0xdff00 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] mapped
at [ffffa0e7400fe1b0]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffffa0e740099000] 99000 size
24576
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] BRK [0x8222a000, 0x8222afff] PGTABLE
[ 0.000000] BRK [0x8222b000, 0x8222bfff] PGTABLE
[ 0.000000] BRK [0x8222c000, 0x8222cfff] PGTABLE
[ 0.000000] BRK [0x8222d000, 0x8222dfff] PGTABLE
[ 0.000000] BRK [0x8222e000, 0x8222efff] PGTABLE
[ 0.000000] BRK [0x8222f000, 0x8222ffff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x33a42000-0x35d18fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000FE020 000024 (v02 HPQOEM)
[ 0.000000] ACPI: XSDT 0x00000000DFEF4120 00006C (v01 HPQOEM SLIC-MPC
00000001 01000013)
[ 0.000000] ACPI: FACP 0x00000000DFEF3000 0000F4 (v04 HPQOEM SLIC-MPC
00000001 ACPI 00040000)
[ 0.000000] ACPI: DSDT 0x00000000DFEDE000 01009F (v01 HP INSYDE
F0000000 ACPI 00040000)
[ 0.000000] ACPI: FACS 0x00000000DFC96000 000040
[ 0.000000] ACPI: FACS 0x00000000DFC96000 000040
[ 0.000000] ACPI: HPET 0x00000000DFEF2000 000038 (v01 HP INSYDE
00000001 ACPI 00040000)
[ 0.000000] ACPI: APIC 0x00000000DFEF1000 000084 (v02 HP INSYDE
00000001 ACPI 00040000)
[ 0.000000] ACPI: MCFG 0x00000000DFEF0000 00003C (v01 HP INSYDE
00000001 ACPI 00040000)
[ 0.000000] ACPI: ASF! 0x00000000DFEEF000 0000A5 (v32 HP INSYDE
00000001 ACPI 00040000)
[ 0.000000] ACPI: BOOT 0x00000000DFEDD000 000028 (v01 HP INSYDE
00000001 ACPI 00040000)
[ 0.000000] ACPI: SLIC 0x00000000DFEDC000 000176 (v01 HPQOEM SLIC-MPC
00000001 ACPI 00040000)
[ 0.000000] ACPI: SSDT 0x00000000DFEDB000 0003DE (v01 HP INSYDE
00000001 AMD 00000001)
[ 0.000000] ACPI: SSDT 0x00000000DFED9000 00168E (v02 HP INSYDE
00000001 MSFT 04000000)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem
0x0000000000000000-0x0000000206ffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x206ff9000-0x206ffdfff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000001000-0x0000000000ffffff]
[ 0.000000] DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
[ 0.000000] Normal [mem 0x0000000100000000-0x0000000206ffffff]
[ 0.000000] Device empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000001000-0x000000000009efff]
[ 0.000000] node 0: [mem 0x0000000000100000-0x00000000dfb3efff]
[ 0.000000] node 0: [mem 0x00000000dfef5000-0x00000000dfefffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x0000000206ffffff]
[ 0.000000] Initmem setup node 0 [mem
0x0000000000001000-0x0000000206ffffff]
[ 0.000000] On node 0 totalpages: 1993448
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3998 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 14254 pages used for memmap
[ 0.000000] DMA32 zone: 912202 pages, LIFO batch:31
[ 0.000000] Normal zone: 16832 pages used for memmap
[ 0.000000] Normal zone: 1077248 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[ 0.000000] IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI
0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low
level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x43538210 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdfb3f000-0xdfbbefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdfbbf000-0xdfebefff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdfebf000-0xdfef4fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xdff00000-0xdfffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xe0000000-0xf7ffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec01000-0xfec0ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec10000-0xfec10fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfec11000-0xfedfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
[ 0.000000] PM: Registered nosave memory: [mem 0xfee01000-0xffdfffff]
[ 0.000000] PM: Registered nosave memory: [mem 0xffe00000-0xffffffff]
[ 0.000000] e820: [mem 0xe0000000-0xf7ffffff] available for PCI
devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] clocksource: refined-jiffies: mask: 0xffffffff
max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256
nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] percpu: Embedded 36 pages/cpu @ffffa0e946c00000 s107544
r8192 d31720 u524288
[ 0.000000] pcpu-alloc: s107544 r8192 d31720 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on.
Total pages: 1962277
[ 0.000000] Policy zone: Normal
[ 0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.4-vnl-14h-688-amd64
root=UUID=124d207f-6ec4-4270-a1a3-2878e0756f25 ro quiet show_msr=1
clocksource=hpet hpet=verbose acpi_sleep=s3_beep mce=bootlog
pcie_aspm.policy=powersave debug=y splash vt.handoff=7
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA -
bailing!
[ 0.000000] Memory: 7727548K/7973792K available (8592K kernel code,
1419K rwdata, 3784K rodata, 1536K init, 1264K bss, 246244K reserved, 0K
cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4,
Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64,
nr_cpu_ids=4
[ 0.000000] NR_IRQS:16640 nr_irqs:456 16
[ 0.000000] spurious 8259A interrupt: IRQ7.
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet: hpet_enable(865):
[ 0.000000] hpet: ID: 0x43538210, PERIOD: 0x429b17e
[ 0.000000] hpet: CFG: 0x0, STATUS: 0x0
[ 0.000000] hpet: COUNTER_l: 0x0, COUNTER_h: 0x0
[ 0.000000] hpet: T0: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T0: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T0 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: T1: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T1: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T1 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: T2: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T2: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T2 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: hpet_enable(904):
[ 0.000000] hpet: ID: 0x43538210, PERIOD: 0x429b17e
[ 0.000000] hpet: CFG: 0x0, STATUS: 0x0
[ 0.000000] hpet: COUNTER_l: 0x0, COUNTER_h: 0x0
[ 0.000000] hpet: T0: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T0: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T0 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: T1: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T1: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T1 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: T2: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T2: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T2 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 133484873504 ns
[ 0.000000] hpet: hpet_set_periodic(320):
[ 0.000000] hpet: ID: 0x43538210, PERIOD: 0x429b17e
[ 0.000000] hpet: CFG: 0x3, STATUS: 0x0
[ 0.000000] hpet: COUNTER_l: 0xc6a, COUNTER_h: 0x0
[ 0.000000] hpet: T0: CFG_l: 0x801c, CFG_h: 0xc00000
[ 0.000000] hpet: T0: CMP_l: 0xea65, CMP_h: 0x0
[ 0.000000] hpet: T0 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: T1: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T1: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T1 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet: T2: CFG_l: 0x8010, CFG_h: 0xc00000
[ 0.000000] hpet: T2: CMP_l: 0xffffffff, CMP_h: 0x0
[ 0.000000] hpet: T2 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1297.292 MHz processor
[ 0.000087] Calibrating delay loop (skipped), value calculated using
timer frequency.. 2594.58 BogoMIPS (lpj=5189168)
[ 0.000111] pid_max: default: 32768 minimum: 301
[ 0.000142] ACPI: Core revision 20160422
[ 0.028627] ACPI: 3 ACPI AML tables successfully acquired and loaded
[ 0.028736] Security Framework initialized
[ 0.028749] Yama: becoming mindful.
[ 0.028783] AppArmor: AppArmor initialized
[ 0.030409] Dentry cache hash table entries: 1048576 (order: 11,
8388608 bytes)
[ 0.037032] Inode-cache hash table entries: 524288 (order: 10,
4194304 bytes)
[ 0.040032] Mount-cache hash table entries: 16384 (order: 5, 131072
bytes)
[ 0.040084] Mountpoint-cache hash table entries: 16384 (order: 5,
131072 bytes)
[ 0.040948] CPU: Physical Processor ID: 0
[ 0.040972] CPU: Processor Core ID: 0
[ 0.040984] mce: CPU supports 6 MCE banks
[ 0.041015] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
[ 0.041026] Last level dTLB entries: 4KB 512, 2MB 8, 4MB 4, 1GB 0
[ 0.042115] Freeing SMP alternatives memory: 32K (ffffffff9f0e4000 -
ffffffff9f0ec000)
[ 0.048858] ftrace: allocating 32760 entries in 128 pages
[ 0.089386] smpboot: APIC(0) Converting physical 0 to logical package
0
[ 0.089411] smpboot: Max logical packages: 2
[ 0.089846] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.234587] smpboot: CPU0: AMD E-300 APU with Radeon(tm) HD Graphics
(family: 0x14, model: 0x2, stepping: 0x0)
[ 0.234615] MSR00000000: 0000000000000000
[ 0.234625] MSR00000001: 0000000000000000
[ 0.234647] MSR00000010: 000000039a2dc212
[ 0.234663] MSR0000001b: 00000000fee00900
[ 0.234680] MSR0000002a: 0000000000000000
[ 0.234743] MSR0000008b: 0000000005000101
[ 0.234803] MSR000000e7: 000000039a30d756
[ 0.234812] MSR000000e8: 0000000398f9c3ac
[ 0.234833] MSR000000fe: 0000000000000508
[ 0.234907] MSR00000174: 0000000000000010
[ 0.234916] MSR00000175: 0000000000000000
[ 0.234926] MSR00000176: 000000009e860b20
[ 0.234936] MSR00000179: 0000000000000106
[ 0.234945] MSR0000017a: 0000000000000000
[ 0.234954] MSR0000017b: 0000000000000037
[ 0.235015] MSR000001d9: 0000000000000000
[ 0.235025] MSR000001db: 0000000000000000
[ 0.235033] MSR000001dc: 0000000000000000
[ 0.235042] MSR000001dd: 0000000000000000
[ 0.235051] MSR000001de: 0000000000000000
[ 0.235078] MSR00000200: 0000000000000006
[ 0.235087] MSR00000201: 0000000f80000800
[ 0.235096] MSR00000202: 0000000080000006
[ 0.235106] MSR00000203: 0000000fc0000800
[ 0.235114] MSR00000204: 00000000c0000006
[ 0.235123] MSR00000205: 0000000fe0000800
[ 0.235132] MSR00000206: 00000000dfebd000
[ 0.235141] MSR00000207: 0000000ffffff800
[ 0.235149] MSR00000208: 00000000ffe00005
[ 0.235159] MSR00000209: 0000000fffe00800
[ 0.235168] MSR0000020a: 00000000e0000001
[ 0.235177] MSR0000020b: 0000000fff000000
[ 0.235185] MSR0000020c: 0000000000000000
[ 0.235194] MSR0000020d: 0000000000000000
[ 0.235203] MSR0000020e: 0000000000000000
[ 0.235212] MSR0000020f: 0000000000000000
[ 0.235257] MSR00000250: 0606060606060606
[ 0.235270] MSR00000258: 0606060606060606
[ 0.235279] MSR00000259: 0000000000000000
[ 0.235297] MSR00000268: 0404040404040404
[ 0.235305] MSR00000269: 0404040404040404
[ 0.235314] MSR0000026a: 0404040404040404
[ 0.235323] MSR0000026b: 0404040404040404
[ 0.235333] MSR0000026c: 0404040404040404
[ 0.235341] MSR0000026d: 0404040404040404
[ 0.235350] MSR0000026e: 0404040404040404
[ 0.235359] MSR0000026f: 0404040404040404
[ 0.235373] MSR00000277: 0407010600070106
[ 0.235457] MSR000002ff: 0000000000000c00
[ 0.235608] MSR00000400: 0000000000000f4c
[ 0.235617] MSR00000401: 0000000000000000
[ 0.235626] MSR00000402: 0000000000000000
[ 0.235634] MSR00000403: 0000000000000000
[ 0.235643] MSR00000404: 000000000000025c
[ 0.235652] MSR00000405: 0000000000000000
[ 0.235661] MSR00000406: 0000000000000000
[ 0.235670] MSR00000407: 0000000000000000
[ 0.235679] MSR00000408: 00000000000031f0
[ 0.235688] MSR00000409: 0000000000000000
[ 0.235697] MSR0000040a: 0000000000000000
[ 0.235705] MSR0000040b: 0000000000000000
[ 0.235714] MSR0000040c: 0000000000000000
[ 0.235723] MSR0000040d: 0000000000000000
[ 0.235732] MSR0000040e: 0000000000000000
[ 0.235741] MSR0000040f: 0000000000000000
[ 0.235750] MSR00000410: 0000000002033b20
[ 0.235759] MSR00000411: 0000000000000000
[ 0.235768] MSR00000412: 0000000000000000
[ 0.235777] MSR00000413: 0000000000000000
[ 0.235786] MSR00000414: 0000000000000001
[ 0.235794] MSR00000415: 0000000000000000
[ 0.235803] MSR00000416: 0000000000000000
[ 0.235812] MSR00000417: 0000000000000000
[ 0.235891] MSRc0000080: 0000000000000d01
[ 0.235900] MSRc0000081: 0023001000000000
[ 0.235910] MSRc0000082: ffffffff9e85f310
[ 0.235919] MSRc0000083: ffffffff9e860b80
[ 0.235928] MSRc0000084: 0000000000047700
[ 0.236005] MSRc0000100: 0000000000000000
[ 0.236014] MSRc0000101: ffffa0e946c00000
[ 0.236023] MSRc0000102: 0000000000000000
[ 0.236032] MSRc0000103: 0000000000000000
[ 0.236465] MSRc0010000: 0000000000000000
[ 0.236474] MSRc0010001: 0000000000000000
[ 0.236483] MSRc0010002: 0000000000000000
[ 0.236492] MSRc0010003: 0000000000000000
[ 0.236501] MSRc0010004: 0000000000000000
[ 0.236510] MSRc0010005: 0000000000000000
[ 0.236519] MSRc0010006: 0000000000000000
[ 0.236528] MSRc0010007: 0000000000000000
[ 0.236541] MSRc0010010: 0000000000760000
[ 0.236553] MSRc0010015: 0000000001000011
[ 0.236561] MSRc0010016: 0000000000000000
[ 0.236570] MSRc0010017: 0000000000000000
[ 0.236579] MSRc0010018: 0000000000000000
[ 0.236588] MSRc0010019: 0000000000000000
[ 0.236597] MSRc001001a: 00000000e0000000
[ 0.236607] MSRc001001d: 000000021f000000
[ 0.236618] MSRc001001f: 0400000000000200
[ 0.236628] MSRc0010022: 0000000000000000
[ 0.236645] MSRc0010030: 30332d4520444d41
[ 0.236654] MSRc0010031: 6977205550412030
[ 0.236663] MSRc0010032: 6f65646152206874
[ 0.236672] MSRc0010033: 444820296d74286e
[ 0.236681] MSRc0010034: 6369687061724720
[ 0.236689] MSRc0010035: 0000000000000073
[ 0.236703] MSRc001003e: 00000000207e0001
[ 0.236713] MSRc001003f: 0000000020000000
[ 0.236724] MSRc0010043: 0000000000000020
[ 0.236733] MSRc0010044: 0000000000000040
[ 0.236742] MSRc0010045: 0000000000000000
[ 0.236751] MSRc0010046: 0000000000000000
[ 0.236759] MSRc0010047: 0000000000000000
[ 0.236768] MSRc0010048: 0000000000000000
[ 0.236777] MSRc0010049: 0000000000000000
[ 0.236789] MSRc0010050: 0000000000000000
[ 0.236798] MSRc0010051: 0000000000000000
[ 0.236807] MSRc0010052: 0000000000000000
[ 0.236816] MSRc0010053: 0000000000000000
[ 0.236825] MSRc0010054: 0000000000000000
[ 0.236833] MSRc0010055: 0000000000000000
[ 0.236843] MSRc0010056: 0000000000000000
[ 0.236852] MSRc0010058: 00000000f8000019
[ 0.236861] MSRc0010059: 0000000000000000
[ 0.236870] MSRc001005a: 0000000000000000
[ 0.236879] MSRc001005b: 0000000000000000
[ 0.236888] MSRc001005c: 0000000000000000
[ 0.236897] MSRc001005d: 0000000000000000
[ 0.236907] MSRc0010060: 0000000000000000
[ 0.236917] MSRc0010061: 0000000000000020
[ 0.236927] MSRc0010062: 0000000000000000
[ 0.236936] MSRc0010063: 0000000000000000
[ 0.236945] MSRc0010064: 8000012b00002020
[ 0.236955] MSRc0010065: 8000011c00002e22
[ 0.236964] MSRc0010066: 800002a500005440
[ 0.236974] MSRc0010067: 0000000000000000
[ 0.236982] MSRc0010068: 0000000000000000
[ 0.236992] MSRc0010069: 0000000000000000
[ 0.237001] MSRc001006a: 0000000000000000
[ 0.237010] MSRc001006b: 0000000000000000
[ 0.237022] MSRc0010070: 0000000000000000
[ 0.237032] MSRc0010071: 002e008264002020
[ 0.237042] MSRc0010073: 000000000000f7ff
[ 0.237051] MSRc0010074: 0000000000000000
[ 0.237152] MSRc0010111: 00000000000a0000
[ 0.237162] MSRc0010112: 00000000dff00000
[ 0.237171] MSRc0010113: 0000000ffff06603
[ 0.237180] MSRc0010114: 0000000000000008
[ 0.237188] MSRc0010115: 0000000000000000
[ 0.237198] MSRc0010117: 0000000000000000
[ 0.237207] MSRc0010118: 0000000000000000
[ 0.237216] MSRc0010119: 0000000000000000
[ 0.237225] MSRc001011a: 0000000000000000
[ 0.237257] MSRc0010140: 0000000000000004
[ 0.237266] MSRc0010141: 0000000000000000
[ 0.237275] MSRc0011000: 0000000000000000
[ 0.237283] MSRc0011001: 0000000000000000
[ 0.237294] MSRc0011004: 00802209178bfbff
[ 0.237303] MSRc0011005: 000035ff2fd3fbff
[ 0.237312] MSRc0011006: 0000000000000000
[ 0.237320] MSRc0011007: 0000000000000000
[ 0.237329] MSRc0011008: 0000000000000000
[ 0.237338] MSRc0011009: 0000000000000000
[ 0.237347] MSRc001100a: 0000000000000000
[ 0.237356] MSRc001100b: 0000000000000000
[ 0.237365] MSRc001100c: 0000000000000000
[ 0.237374] MSRc001100e: 0000000000000000
[ 0.237383] MSRc001100f: 0000000000000000
[ 0.237392] MSRc0011010: 0000000000000000
[ 0.237401] MSRc0011011: 000000000000001e
[ 0.237411] MSRc0011014: 0000000000000000
[ 0.237420] MSRc0011015: 0000000000000000
[ 0.237428] MSRc0011016: 0000000000000000
[ 0.237437] MSRc0011017: 0000000000000000
[ 0.237446] MSRc0011018: 0000000000000000
[ 0.237458] MSRc001101d: 0000000000000000
[ 0.237466] MSRc001101e: 0000000000000020
[ 0.237476] MSRc001101f: 0400000000000200
[ 0.237485] MSRc0011020: 0000001002040000
[ 0.237494] MSRc0011021: 0000000010208000
[ 0.237503] MSRc0011022: 0600001800000000
[ 0.237512] MSRc0011023: 0000000000000000
[ 0.237521] MSRc0011024: 0000000000000000
[ 0.237530] MSRc0011025: 0000000000000000
[ 0.237539] MSRc0011026: 0000000000000000
[ 0.237548] MSRc0011027: 0000000000000000
[ 0.237557] MSRc0011028: 0000000000000000
[ 0.237566] MSRc0011029: 00000000000a1000
[ 0.237574] MSRc001102a: 0000000000008000
[ 0.237583] MSRc001102b: 0000000003c00000
[ 0.237593] MSRc001102e: 0000000000000000
[ 0.237603] MSRc0011030: 0000000000000000
[ 0.237612] MSRc0011031: 0000000000000000
[ 0.237621] MSRc0011032: 0000000000000000
[ 0.237630] MSRc0011033: 0000000000000000
[ 0.237639] MSRc0011034: 0000000000000000
[ 0.237647] MSRc0011035: 0000000000000000
[ 0.237657] MSRc0011036: 0000000000000000
[ 0.237666] MSRc0011037: 0000000000000000
[ 0.237674] MSRc0011038: 0000000000000000
[ 0.237683] MSRc0011039: 0000000000000000
[ 0.237692] MSRc001103a: 0000000000000100
[ 0.237704] Performance Events: AMD PMU driver.
[ 0.237723] ... version: 0
[ 0.237732] ... bit width: 48
[ 0.237741] ... generic registers: 4
[ 0.237749] ... value mask: 0000ffffffffffff
[ 0.237758] ... max period: 00007fffffffffff
[ 0.237767] ... fixed-purpose events: 0
[ 0.237776] ... event mask: 000000000000000f
[ 0.239783] NMI watchdog: enabled on all CPUs, permanently consumes
one hw-PMU counter.
[ 0.240244] x86: Booting SMP configuration:
[ 0.240260] .... node #0, CPUs: #1
[ 0.321032] x86: Booted up 1 node, 2 CPUs
[ 0.321063] smpboot: Total of 2 processors activated (5189.12
BogoMIPS)
[ 0.322761] devtmpfs: initialized
[ 0.323024] x86/mm: Memory block size: 128MB
[ 0.332055] evm: security.selinux
[ 0.332069] evm: security.SMACK64
[ 0.332078] evm: security.SMACK64EXEC
[ 0.332087] evm: security.SMACK64TRANSMUTE
[ 0.332096] evm: security.SMACK64MMAP
[ 0.332104] evm: security.ima
[ 0.332112] evm: security.capability
[ 0.332485] PM: Registering ACPI NVS region [mem
0xdfbbf000-0xdfebefff] (3145728 bytes)
[ 0.332870] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.332990] pinctrl core: initialized pinctrl subsystem
[ 0.333398] RTC time: 9:43:04, date: 10/24/16
[ 0.337828] NET: Registered protocol family 16
[ 0.349008] cpuidle: using governor ladder
[ 0.361010] cpuidle: using governor menu
[ 0.361046] PCCT header not found.
[ 0.361354] Simple Boot Flag at 0x44 set to 0x1
[ 0.361407] ACPI FADT declares the system doesn't support PCIe ASPM,
so disable it
[ 0.361424] ACPI: bus type PCI registered
[ 0.361436] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.361755] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem
0xf8000000-0xfbffffff] (base 0xf8000000)
[ 0.361777] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in
E820
[ 0.361800] PCI: Using configuration type 1 for base access
[ 0.362818] mtrr: your CPUs had inconsistent variable MTRR settings
[ 0.362840] mtrr: probably your BIOS does not setup all CPUs.
[ 0.362849] mtrr: corrected configuration.
[ 0.377995] HugeTLB registered 1 GB page size, pre-allocated 0 pages
[ 0.378019] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.379387] ACPI: Added _OSI(Module Device)
[ 0.379409] ACPI: Added _OSI(Processor Device)
[ 0.379419] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.379429] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.379881] ACPI: Executed 1 blocks of module-level executable AML
code
[ 0.390909] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.392104] ACPI : EC: EC started
[ 0.959016] ACPI: Interpreter enabled
[ 0.959105] ACPI: (supports S0 S3 S4 S5)
[ 0.959117] ACPI: Using IOAPIC for interrupt routing
[ 0.959696] PCI: Using host bridge windows from ACPI; if necessary,
use "pci=nocrs" and report a bug
[ 1.040850] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 1.040886] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM
ClockPM Segments MSI]
[ 1.041769] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME
AER PCIeCapability]
[ 1.041789] acpi PNP0A08:00: FADT indicates ASPM is unsupported,
using BIOS configuration
[ 1.041833] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain
0000 [bus 00-3f] only partially covers this bridge
[ 1.042087] acpi PNP0A08:00: ignoring host bridge window [mem
0x000cc000-0x000cffff window] (conflicts with Video ROM [mem
0x000c0000-0x000ce5ff])
[ 1.042674] PCI host bridge to bus 0000:00
[ 1.042693] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7
window]
[ 1.042706] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff
window]
[ 1.042719] pci_bus 0000:00: root bus resource [mem
0x000a0000-0x000bffff window]
[ 1.042736] pci_bus 0000:00: root bus resource [mem
0x000c0000-0x000c3fff window]
[ 1.042753] pci_bus 0000:00: root bus resource [mem
0x000c4000-0x000c7fff window]
[ 1.042769] pci_bus 0000:00: root bus resource [mem
0x000c8000-0x000cbfff window]
[ 1.042785] pci_bus 0000:00: root bus resource [mem
0x000d0000-0x000d3fff window]
[ 1.042802] pci_bus 0000:00: root bus resource [mem
0x000d4000-0x000d7fff window]
[ 1.042818] pci_bus 0000:00: root bus resource [mem
0x000d8000-0x000dbfff window]
[ 1.042834] pci_bus 0000:00: root bus resource [mem
0x000dc000-0x000dffff window]
[ 1.042850] pci_bus 0000:00: root bus resource [mem
0x000e0000-0x000e3fff window]
[ 1.042866] pci_bus 0000:00: root bus resource [mem
0x000e4000-0x000e7fff window]
[ 1.042882] pci_bus 0000:00: root bus resource [mem
0x000e8000-0x000ebfff window]
[ 1.042898] pci_bus 0000:00: root bus resource [mem
0x000ec000-0x000effff window]
[ 1.042914] pci_bus 0000:00: root bus resource [mem
0xe0000000-0xf7ffffff window]
[ 1.042930] pci_bus 0000:00: root bus resource [mem
0xfc000000-0xfed3ffff window]
[ 1.042947] pci_bus 0000:00: root bus resource [mem
0xfed45000-0xffffffff window]
[ 1.042964] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 1.042992] pci 0000:00:00.0: [1022:1510] type 00 class 0x060000
[ 1.043276] pci 0000:00:01.0: [1002:9802] type 00 class 0x030000
[ 1.043308] pci 0000:00:01.0: reg 0x10: [mem 0xe0000000-0xefffffff
pref]
[ 1.043328] pci 0000:00:01.0: reg 0x14: [io 0x4000-0x40ff]
[ 1.043348] pci 0000:00:01.0: reg 0x18: [mem 0xf0400000-0xf043ffff]
[ 1.043438] pci 0000:00:01.0: supports D1 D2
[ 1.043733] pci 0000:00:11.0: [1002:4391] type 00 class 0x010601
[ 1.043772] pci 0000:00:11.0: reg 0x10: [io 0x4118-0x411f]
[ 1.043796] pci 0000:00:11.0: reg 0x14: [io 0x4124-0x4127]
[ 1.043819] pci 0000:00:11.0: reg 0x18: [io 0x4110-0x4117]
[ 1.043842] pci 0000:00:11.0: reg 0x1c: [io 0x4120-0x4123]
[ 1.043865] pci 0000:00:11.0: reg 0x20: [io 0x4100-0x410f]
[ 1.043888] pci 0000:00:11.0: reg 0x24: [mem 0xf0449000-0xf04493ff]
[ 1.044210] pci 0000:00:12.0: [1002:4397] type 00 class 0x0c0310
[ 1.044245] pci 0000:00:12.0: reg 0x10: [mem 0xf0448000-0xf0448fff]
[ 1.044462] pci 0000:00:12.0: System wakeup disabled by ACPI
[ 1.044668] pci 0000:00:12.2: [1002:4396] type 00 class 0x0c0320
[ 1.045328] pci 0000:00:12.2: reg 0x10: [mem 0xf0447000-0xf04470ff]
[ 1.048958] pci 0000:00:12.2: supports D1 D2
[ 1.048973] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
[ 1.049110] pci 0000:00:12.2: System wakeup disabled by ACPI
[ 1.049292] pci 0000:00:14.0: [1002:4385] type 00 class 0x0c0500
[ 1.049700] pci 0000:00:14.2: [1002:4383] type 00 class 0x040300
[ 1.049743] pci 0000:00:14.2: reg 0x10: [mem 0xf0440000-0xf0443fff
64bit]
[ 1.049861] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
[ 1.050111] pci 0000:00:14.3: [1002:439d] type 00 class 0x060100
[ 1.050441] pci 0000:00:14.4: [1002:4384] type 01 class 0x060401
[ 1.050650] pci 0000:00:14.4: System wakeup disabled by ACPI
[ 1.050799] pci 0000:00:14.5: [1002:4399] type 00 class 0x0c0310
[ 1.050834] pci 0000:00:14.5: reg 0x10: [mem 0xf0446000-0xf0446fff]
[ 1.051058] pci 0000:00:14.5: System wakeup disabled by ACPI
[ 1.051234] pci 0000:00:15.0: [1002:43a0] type 01 class 0x060400
[ 1.051370] pci 0000:00:15.0: supports D1 D2
[ 1.051513] pci 0000:00:15.0: System wakeup disabled by ACPI
[ 1.051701] pci 0000:00:15.1: [1002:43a1] type 01 class 0x060400
[ 1.051835] pci 0000:00:15.1: supports D1 D2
[ 1.051975] pci 0000:00:15.1: System wakeup disabled by ACPI
[ 1.052120] pci 0000:00:15.3: [1002:43a3] type 01 class 0x060400
[ 1.052254] pci 0000:00:15.3: supports D1 D2
[ 1.052541] pci 0000:00:16.0: [1002:4397] type 00 class 0x0c0310
[ 1.052575] pci 0000:00:16.0: reg 0x10: [mem 0xf0445000-0xf0445fff]
[ 1.052798] pci 0000:00:16.0: System wakeup disabled by ACPI
[ 1.052970] pci 0000:00:16.2: [1002:4396] type 00 class 0x0c0320
[ 1.053613] pci 0000:00:16.2: reg 0x10: [mem 0xf0444000-0xf04440ff]
[ 1.057251] pci 0000:00:16.2: supports D1 D2
[ 1.057266] pci 0000:00:16.2: PME# supported from D0 D1 D2 D3hot
[ 1.057405] pci 0000:00:16.2: System wakeup disabled by ACPI
[ 1.057586] pci 0000:00:18.0: [1022:1700] type 00 class 0x060000
[ 1.057847] pci 0000:00:18.1: [1022:1701] type 00 class 0x060000
[ 1.058098] pci 0000:00:18.2: [1022:1702] type 00 class 0x060000
[ 1.058348] pci 0000:00:18.3: [1022:1703] type 00 class 0x060000
[ 1.058628] pci 0000:00:18.4: [1022:1704] type 00 class 0x060000
[ 1.058879] pci 0000:00:18.5: [1022:1718] type 00 class 0x060000
[ 1.059131] pci 0000:00:18.6: [1022:1716] type 00 class 0x060000
[ 1.059382] pci 0000:00:18.7: [1022:1719] type 00 class 0x060000
[ 1.059846] pci 0000:00:14.4: PCI bridge to [bus 01] (subtractive
decode)
[ 1.059873] pci 0000:00:14.4: bridge window [io 0x0000-0x0cf7
window] (subtractive decode)
[ 1.059891] pci 0000:00:14.4: bridge window [io 0x0d00-0xffff
window] (subtractive decode)
[ 1.059908] pci 0000:00:14.4: bridge window [mem
0x000a0000-0x000bffff window] (subtractive decode)
[ 1.059925] pci 0000:00:14.4: bridge window [mem
0x000c0000-0x000c3fff window] (subtractive decode)
[ 1.059943] pci 0000:00:14.4: bridge window [mem
0x000c4000-0x000c7fff window] (subtractive decode)
[ 1.059961] pci 0000:00:14.4: bridge window [mem
0x000c8000-0x000cbfff window] (subtractive decode)
[ 1.059978] pci 0000:00:14.4: bridge window [mem
0x000d0000-0x000d3fff window] (subtractive decode)
[ 1.059995] pci 0000:00:14.4: bridge window [mem
0x000d4000-0x000d7fff window] (subtractive decode)
[ 1.060012] pci 0000:00:14.4: bridge window [mem
0x000d8000-0x000dbfff window] (subtractive decode)
[ 1.060029] pci 0000:00:14.4: bridge window [mem
0x000dc000-0x000dffff window] (subtractive decode)
[ 1.060046] pci 0000:00:14.4: bridge window [mem
0x000e0000-0x000e3fff window] (subtractive decode)
[ 1.060063] pci 0000:00:14.4: bridge window [mem
0x000e4000-0x000e7fff window] (subtractive decode)
[ 1.060080] pci 0000:00:14.4: bridge window [mem
0x000e8000-0x000ebfff window] (subtractive decode)
[ 1.060097] pci 0000:00:14.4: bridge window [mem
0x000ec000-0x000effff window] (subtractive decode)
[ 1.060114] pci 0000:00:14.4: bridge window [mem
0xe0000000-0xf7ffffff window] (subtractive decode)
[ 1.060132] pci 0000:00:14.4: bridge window [mem
0xfc000000-0xfed3ffff window] (subtractive decode)
[ 1.060149] pci 0000:00:14.4: bridge window [mem
0xfed45000-0xffffffff window] (subtractive decode)
[ 1.060412] pci 0000:02:00.0: [10ec:5209] type 00 class 0xff0000
[ 1.060464] pci 0000:02:00.0: reg 0x10: [mem 0xf0300000-0xf0300fff]
[ 1.060686] pci 0000:02:00.0: supports D1 D2
[ 1.060699] pci 0000:02:00.0: PME# supported from D1 D2 D3hot
[ 1.070840] pci 0000:00:15.0: PCI bridge to [bus 02-05]
[ 1.070911] pci 0000:00:15.0: bridge window [io 0x3000-0x3fff]
[ 1.070928] pci 0000:00:15.0: bridge window [mem
0xf0300000-0xf03fffff]
[ 1.070947] pci 0000:00:15.0: bridge window [mem
0xf0000000-0xf00fffff 64bit pref]
[ 1.071244] pci 0000:06:00.0: [10ec:8136] type 00 class 0x020000
[ 1.071292] pci 0000:06:00.0: reg 0x10: [io 0x2000-0x20ff]
[ 1.071347] pci 0000:06:00.0: reg 0x18: [mem 0xf0104000-0xf0104fff
64bit pref]
[ 1.071392] pci 0000:06:00.0: reg 0x20: [mem 0xf0100000-0xf0103fff
64bit pref]
[ 1.071561] pci 0000:06:00.0: supports D1 D2
[ 1.071575] pci 0000:06:00.0: PME# supported from D0 D1 D2 D3hot
D3cold
[ 1.082839] pci 0000:00:15.1: PCI bridge to [bus 06]
[ 1.082911] pci 0000:00:15.1: bridge window [io 0x2000-0x2fff]
[ 1.082934] pci 0000:00:15.1: bridge window [mem
0xf0100000-0xf01fffff 64bit pref]
[ 1.083296] pci 0000:07:00.0: [1814:5390] type 00 class 0x028000
[ 1.083363] pci 0000:07:00.0: reg 0x10: [mem 0xf0200000-0xf020ffff]
[ 1.094837] pci 0000:00:15.3: PCI bridge to [bus 07]
[ 1.094912] pci 0000:00:15.3: bridge window [mem
0xf0200000-0xf02fffff]
[ 1.129719] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.129977] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.130282] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.130628] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.130823] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.131092] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.131342] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.131589] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 10 11 12 14
15) *0
[ 1.132329] ACPI: Enabled 2 GPEs in block 00 to 1F
[ 1.132545] ACPI : EC: EC stopped
[ 1.132713] ACPI : EC: GPE = 0x3, I/O: command/status = 0x66, data =
0x62
[ 1.132727] ACPI : EC: EC started
[ 1.699553] vgaarb: setting as boot device: PCI:0000:00:01.0
[ 1.699577] vgaarb: device added:
PCI:0000:00:01.0,decodes=io+mem,owns=io+mem,locks=none
[ 1.699604] vgaarb: loaded
[ 1.699613] vgaarb: bridge control possible 0000:00:01.0
[ 1.700262] SCSI subsystem initialized
[ 1.700510] libata version 3.00 loaded.
[ 1.700614] ACPI: bus type USB registered
[ 1.700683] usbcore: registered new interface driver usbfs
[ 1.700723] usbcore: registered new interface driver hub
[ 1.700784] usbcore: registered new device driver usb
[ 1.701221] PCI: Using ACPI for IRQ routing
[ 1.704059] PCI: pci_cache_line_size set to 64 bytes
[ 1.704219] e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
[ 1.704233] e820: reserve RAM buffer [mem 0xdfb3f000-0xdfffffff]
[ 1.704245] e820: reserve RAM buffer [mem 0xdff00000-0xdfffffff]
[ 1.704256] e820: reserve RAM buffer [mem 0x207000000-0x207ffffff]
[ 1.704604] NetLabel: Initializing
[ 1.704617] NetLabel: domain hash size = 128
[ 1.704626] NetLabel: protocols = UNLABELED CIPSOv4
[ 1.704680] NetLabel: unlabeled traffic allowed by default
[ 1.705407] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 1.705438] hpet0: 3 comparators, 32-bit 14.318180 MHz counter
[ 1.707532] hpet: hpet_late_init(951):
[ 1.707583] hpet: ID: 0x43538210, PERIOD: 0x429b17e
[ 1.707595] hpet: CFG: 0x3, STATUS: 0x1
[ 1.707605] hpet: COUNTER_l: 0x179d24f, COUNTER_h: 0x0
[ 1.707617] hpet: T0: CFG_l: 0x8018, CFG_h: 0xc00000
[ 1.707629] hpet: T0: CMP_l: 0x17a70e5, CMP_h: 0x0
[ 1.707640] hpet: T0 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 1.707651] hpet: T1: CFG_l: 0x8010, CFG_h: 0xc00000
[ 1.707662] hpet: T1: CMP_l: 0xffffffff, CMP_h: 0x0
[ 1.707673] hpet: T1 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 1.707684] hpet: T2: CFG_l: 0x8010, CFG_h: 0xc00000
[ 1.707695] hpet: T2: CMP_l: 0x2f36080, CMP_h: 0x0
[ 1.707707] hpet: T2 ROUTE_l: 0x0, ROUTE_h: 0x0
[ 1.707868] clocksource: Switched to clocksource hpet
[ 1.734767] VFS: Disk quotas dquot_6.6.0
[ 1.734847] VFS: Dquot-cache hash table entries: 512 (order 0, 4096
bytes)
[ 1.735107] AppArmor: AppArmor Filesystem Enabled
[ 1.735287] pnp: PnP ACPI init
[ 1.735743] system 00:00: [mem 0xfec00000-0xfec00fff] could not be
reserved
[ 1.735761] system 00:00: [mem 0xfee00000-0xfee00fff] has been
reserved
[ 1.735782] system 00:00: Plug and Play ACPI device, IDs PNP0c02
(active)
[ 1.736420] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00
(active)
[ 1.736602] system 00:02: [io 0x0400-0x04cf] has been reserved
[ 1.736618] system 00:02: [io 0x04d0-0x04d1] has been reserved
[ 1.736631] system 00:02: [io 0x04d6] has been reserved
[ 1.736644] system 00:02: [io 0x0680-0x06ff] has been reserved
[ 1.736657] system 00:02: [io 0x077a] has been reserved
[ 1.736669] system 00:02: [io 0x0c00-0x0c01] has been reserved
[ 1.736681] system 00:02: [io 0x0c14] has been reserved
[ 1.736694] system 00:02: [io 0x0c50-0x0c52] has been reserved
[ 1.736706] system 00:02: [io 0x0c6c] has been reserved
[ 1.736718] system 00:02: [io 0x0c6f] has been reserved
[ 1.736730] system 00:02: [io 0x0cd0-0x0cdb] has been reserved
[ 1.736747] system 00:02: Plug and Play ACPI device, IDs PNP0c02
(active)
[ 1.737012] system 00:03: [mem 0x000e0000-0x000fffff] could not be
reserved
[ 1.737029] system 00:03: [mem 0xffffffb0-0xfffffffe] has been
reserved
[ 1.737043] system 00:03: [mem 0xffffff00-0xfffffffe] could not be
reserved
[ 1.737057] system 00:03: [mem 0xffe00000-0xffffffff] could not be
reserved
[ 1.737074] system 00:03: Plug and Play ACPI device, IDs PNP0c01
(active)
[ 1.769426] pnp 00:04: Plug and Play ACPI device, IDs PNP0303
(active)
[ 1.769546] pnp 00:05: Plug and Play ACPI device, IDs SYN1e4b SYN1e00
SYN0002 PNP0f13 (active)
[ 1.770847] pnp: PnP ACPI: found 6 devices
[ 1.788728] clocksource: acpi_pm: mask: 0xffffff max_cycles:
0xffffff, max_idle_ns: 2085701024 ns
[ 1.788874] pci 0000:00:14.4: PCI bridge to [bus 01]
[ 1.788908] pci 0000:00:15.0: PCI bridge to [bus 02-05]
[ 1.788923] pci 0000:00:15.0: bridge window [io 0x3000-0x3fff]
[ 1.788940] pci 0000:00:15.0: bridge window [mem
0xf0300000-0xf03fffff]
[ 1.788956] pci 0000:00:15.0: bridge window [mem
0xf0000000-0xf00fffff 64bit pref]
[ 1.788981] pci 0000:00:15.1: PCI bridge to [bus 06]
[ 1.788994] pci 0000:00:15.1: bridge window [io 0x2000-0x2fff]
[ 1.789014] pci 0000:00:15.1: bridge window [mem
0xf0100000-0xf01fffff 64bit pref]
[ 1.789037] pci 0000:00:15.3: PCI bridge to [bus 07]
[ 1.789053] pci 0000:00:15.3: bridge window [mem
0xf0200000-0xf02fffff]
[ 1.789082] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
[ 1.789095] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
[ 1.789108] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff
window]
[ 1.789120] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000c3fff
window]
[ 1.789133] pci_bus 0000:00: resource 8 [mem 0x000c4000-0x000c7fff
window]
[ 1.789145] pci_bus 0000:00: resource 9 [mem 0x000c8000-0x000cbfff
window]
[ 1.789158] pci_bus 0000:00: resource 10 [mem 0x000d0000-0x000d3fff
window]
[ 1.789171] pci_bus 0000:00: resource 11 [mem 0x000d4000-0x000d7fff
window]
[ 1.789183] pci_bus 0000:00: resource 12 [mem 0x000d8000-0x000dbfff
window]
[ 1.789196] pci_bus 0000:00: resource 13 [mem 0x000dc000-0x000dffff
window]
[ 1.789208] pci_bus 0000:00: resource 14 [mem 0x000e0000-0x000e3fff
window]
[ 1.789220] pci_bus 0000:00: resource 15 [mem 0x000e4000-0x000e7fff
window]
[ 1.789232] pci_bus 0000:00: resource 16 [mem 0x000e8000-0x000ebfff
window]
[ 1.789245] pci_bus 0000:00: resource 17 [mem 0x000ec000-0x000effff
window]
[ 1.789257] pci_bus 0000:00: resource 18 [mem 0xe0000000-0xf7ffffff
window]
[ 1.789270] pci_bus 0000:00: resource 19 [mem 0xfc000000-0xfed3ffff
window]
[ 1.789282] pci_bus 0000:00: resource 20 [mem 0xfed45000-0xffffffff
window]
[ 1.789296] pci_bus 0000:01: resource 4 [io 0x0000-0x0cf7 window]
[ 1.789308] pci_bus 0000:01: resource 5 [io 0x0d00-0xffff window]
[ 1.789320] pci_bus 0000:01: resource 6 [mem 0x000a0000-0x000bffff
window]
[ 1.789332] pci_bus 0000:01: resource 7 [mem 0x000c0000-0x000c3fff
window]
[ 1.789345] pci_bus 0000:01: resource 8 [mem 0x000c4000-0x000c7fff
window]
[ 1.789357] pci_bus 0000:01: resource 9 [mem 0x000c8000-0x000cbfff
window]
[ 1.789369] pci_bus 0000:01: resource 10 [mem 0x000d0000-0x000d3fff
window]
[ 1.789382] pci_bus 0000:01: resource 11 [mem 0x000d4000-0x000d7fff
window]
[ 1.789394] pci_bus 0000:01: resource 12 [mem 0x000d8000-0x000dbfff
window]
[ 1.789407] pci_bus 0000:01: resource 13 [mem 0x000dc000-0x000dffff
window]
[ 1.789419] pci_bus 0000:01: resource 14 [mem 0x000e0000-0x000e3fff
window]
[ 1.789432] pci_bus 0000:01: resource 15 [mem 0x000e4000-0x000e7fff
window]
[ 1.789444] pci_bus 0000:01: resource 16 [mem 0x000e8000-0x000ebfff
window]
[ 1.789456] pci_bus 0000:01: resource 17 [mem 0x000ec000-0x000effff
window]
[ 1.789469] pci_bus 0000:01: resource 18 [mem 0xe0000000-0xf7ffffff
window]
[ 1.789481] pci_bus 0000:01: resource 19 [mem 0xfc000000-0xfed3ffff
window]
[ 1.789494] pci_bus 0000:01: resource 20 [mem 0xfed45000-0xffffffff
window]
[ 1.789507] pci_bus 0000:02: resource 0 [io 0x3000-0x3fff]
[ 1.789518] pci_bus 0000:02: resource 1 [mem 0xf0300000-0xf03fffff]
[ 1.789531] pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf00fffff
64bit pref]
[ 1.789548] pci_bus 0000:06: resource 0 [io 0x2000-0x2fff]
[ 1.789560] pci_bus 0000:06: resource 2 [mem 0xf0100000-0xf01fffff
64bit pref]
[ 1.789578] pci_bus 0000:07: resource 1 [mem 0xf0200000-0xf02fffff]
[ 1.789676] NET: Registered protocol family 2
[ 1.790180] TCP established hash table entries: 65536 (order: 7,
524288 bytes)
[ 1.790718] TCP bind hash table entries: 65536 (order: 8, 1048576
bytes)
[ 1.791422] TCP: Hash tables configured (established 65536 bind
65536)
[ 1.791597] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[ 1.791735] UDP-Lite hash table entries: 4096 (order: 5, 131072
bytes)
[ 1.792128] NET: Registered protocol family 1
[ 1.792190] pci 0000:00:01.0: Video device with shadowed ROM at [mem
0x000c0000-0x000dffff]
[ 2.072669] PCI: CLS 64 bytes, default 64
[ 2.072882] Trying to unpack rootfs image as initramfs...
[ 3.649719] Freeing initrd memory: 35676K (ffffa0e773a42000 -
ffffa0e775d19000)
[ 3.649754] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 3.649768] software IO TLB [mem 0xdbb3f000-0xdfb3f000] (64MB) mapped
at [ffffa0e81bb3f000-ffffa0e81fb3efff]
[ 3.650212] LVT offset 0 assigned for vector 0x400
[ 3.650498] perf: AMD IBS detected (0x000000ff)
[ 3.650699] Scanning for low memory corruption every 60 seconds
[ 3.652131] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 3.652219] audit: initializing netlink subsys (disabled)
[ 3.652275] audit: type=2000 audit(1477302186.536:1): initialized
[ 3.653224] Initialise system trusted keyrings
[ 3.654149] workingset: timestamp_bits=40 max_order=21 bucket_order=0
[ 3.660336] zbud: loaded
[ 3.661683] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 3.662954] fuse init (API version 7.25)
[ 3.663924] Key type big_key registered
[ 3.665912] Key type asymmetric registered
[ 3.665936] Asymmetric key parser 'x509' registered
[ 3.666120] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 248)
[ 3.666279] io scheduler noop registered
[ 3.666292] io scheduler deadline registered (default)
[ 3.666329] io scheduler cfq registered
[ 3.668303] pcieport 0000:00:15.0: Signaling PME through PCIe PME
interrupt
[ 3.668324] pci 0000:02:00.0: Signaling PME through PCIe PME
interrupt
[ 3.668378] pcie_pme 0000:00:15.0:pcie001: service driver pcie_pme
loaded
[ 3.668449] pcieport 0000:00:15.1: Signaling PME through PCIe PME
interrupt
[ 3.668464] pci 0000:06:00.0: Signaling PME through PCIe PME
interrupt
[ 3.668518] pcie_pme 0000:00:15.1:pcie001: service driver pcie_pme
loaded
[ 3.668583] pcieport 0000:00:15.3: Signaling PME through PCIe PME
interrupt
[ 3.668598] pci 0000:07:00.0: Signaling PME through PCIe PME
interrupt
[ 3.668652] pcie_pme 0000:00:15.3:pcie001: service driver pcie_pme
loaded
[ 3.668679] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 3.668708] pciehp: PCI Express Hot Plug Controller Driver version:
0.4
[ 3.668809] vesafb: mode is 1366x768x32, linelength=5504, pages=0
[ 3.668822] vesafb: scrolling: redraw
[ 3.668833] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[ 3.668881] vesafb: framebuffer at 0xe0000000, mapped to
0xffffbcf841000000, using 4160k, total 4160k
[ 3.759420] Console: switching to colour frame buffer device 170x48
[ 3.849903] fb0: VESA VGA frame buffer device
[ 3.852348] ACPI: AC Adapter [AC] (on-line)
[ 3.853139] input: Lid Switch as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[ 3.855588] ACPI: Lid Switch [LID]
[ 3.856342] input: Power Button as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[ 3.857395] ACPI: Power Button [PWRB]
[ 3.857992] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 3.858922] ACPI: Power Button [PWRF]
[ 3.874013] thermal LNXTHERM:00: registered as thermal_zone0
[ 3.874745] ACPI: Thermal Zone [TSZ0] (47 C)
[ 3.875432] GHES: HEST is not enabled!
[ 3.876540] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 3.886583] Linux agpgart interface v0.103
[ 3.902531] brd: module loaded
[ 3.904920] ACPI: Battery Slot [BAT0] (battery absent)
[ 3.908726] loop: module loaded
[ 3.909840] libphy: Fixed MDIO Bus: probed
[ 3.910361] tun: Universal TUN/TAP device driver, 1.6
[ 3.910996] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 3.912225] PPP generic driver version 2.4.2
[ 3.913245] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
Driver
[ 3.914099] ehci-pci: EHCI PCI platform driver
[ 3.915097] QUIRK: Enable AMD PLL fix
[ 3.943428] ehci-pci 0000:00:12.2: EHCI Host Controller
[ 3.972048] ehci-pci 0000:00:12.2: new USB bus registered, assigned
bus number 1
[ 4.001009] ehci-pci 0000:00:12.2: applying AMD
SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[ 4.030130] ehci-pci 0000:00:12.2: debug port 1
[ 4.058722] ehci-pci 0000:00:12.2: irq 17, io mem 0xf0447000
[ 4.099889] ehci-pci 0000:00:12.2: USB 2.0 started, EHCI 1.00
[ 4.128590] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
[ 4.157641] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 4.186574] usb usb1: Product: EHCI Host Controller
[ 4.215266] usb usb1: Manufacturer: Linux 4.8.4-vnl-14h-688-amd64
ehci_hcd
[ 4.244246] usb usb1: SerialNumber: 0000:00:12.2
[ 4.273530] hub 1-0:1.0: USB hub found
[ 4.302000] hub 1-0:1.0: 5 ports detected
[ 4.331031] ehci-pci 0000:00:16.2: EHCI Host Controller
[ 4.359281] ehci-pci 0000:00:16.2: new USB bus registered, assigned
bus number 2
[ 4.387678] ehci-pci 0000:00:16.2: applying AMD
SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[ 4.416307] ehci-pci 0000:00:16.2: debug port 1
[ 4.444495] ehci-pci 0000:00:16.2: irq 17, io mem 0xf0444000
[ 4.487872] ehci-pci 0000:00:16.2: USB 2.0 started, EHCI 1.00
[ 4.515697] usb usb2: New USB device found, idVendor=1d6b,
idProduct=0002
[ 4.543722] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 4.571877] usb usb2: Product: EHCI Host Controller
[ 4.599761] usb usb2: Manufacturer: Linux 4.8.4-vnl-14h-688-amd64
ehci_hcd
[ 4.627702] usb usb2: SerialNumber: 0000:00:16.2
[ 4.655887] hub 2-0:1.0: USB hub found
[ 4.655931] tsc: Refined TSC clocksource calibration: 1297.236 MHz
[ 4.655943] clocksource: tsc: mask: 0xffffffffffffffff max_cycles:
0x12b2eaff38e, max_idle_ns: 440795221446 ns
[ 4.739122] hub 2-0:1.0: 4 ports detected
[ 4.767544] ehci-platform: EHCI generic platform driver
[ 4.795105] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 4.822413] ohci-pci: OHCI PCI platform driver
[ 4.849646] ohci-pci 0000:00:12.0: OHCI PCI host controller
[ 4.876413] ohci-pci 0000:00:12.0: new USB bus registered, assigned
bus number 3
[ 4.903403] ohci-pci 0000:00:12.0: irq 18, io mem 0xf0448000
[ 4.992080] usb usb3: New USB device found, idVendor=1d6b,
idProduct=0001
[ 5.019189] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 5.046306] usb usb3: Product: OHCI PCI host controller
[ 5.073168] usb usb3: Manufacturer: Linux 4.8.4-vnl-14h-688-amd64
ohci_hcd
[ 5.099934] usb 2-2: new high-speed USB device number 2 using
ehci-pci
[ 5.127892] usb usb3: SerialNumber: 0000:00:12.0
[ 5.156033] hub 3-0:1.0: USB hub found
[ 5.183466] hub 3-0:1.0: 5 ports detected
[ 5.211497] ohci-pci 0000:00:14.5: OHCI PCI host controller
[ 5.238855] ohci-pci 0000:00:14.5: new USB bus registered, assigned
bus number 4
[ 5.266327] ohci-pci 0000:00:14.5: irq 18, io mem 0xf0446000
[ 5.296353] usb 2-2: New USB device found, idVendor=0c45,
idProduct=6321
[ 5.323670] usb 2-2: New USB device strings: Mfr=2, Product=1,
SerialNumber=0
[ 5.351119] usb 2-2: Product: HP Webcam-101
[ 5.356095] usb usb4: New USB device found, idVendor=1d6b,
idProduct=0001
[ 5.356100] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 5.356104] usb usb4: Product: OHCI PCI host controller
[ 5.356107] usb usb4: Manufacturer: Linux 4.8.4-vnl-14h-688-amd64
ohci_hcd
[ 5.356110] usb usb4: SerialNumber: 0000:00:14.5
[ 5.356610] hub 4-0:1.0: USB hub found
[ 5.356706] hub 4-0:1.0: 2 ports detected
[ 5.357493] ohci-pci 0000:00:16.0: OHCI PCI host controller
[ 5.357511] ohci-pci 0000:00:16.0: new USB bus registered, assigned
bus number 5
[ 5.357579] ohci-pci 0000:00:16.0: irq 18, io mem 0xf0445000
[ 5.440130] usb usb5: New USB device found, idVendor=1d6b,
idProduct=0001
[ 5.440135] usb usb5: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 5.440139] usb usb5: Product: OHCI PCI host controller
[ 5.440142] usb usb5: Manufacturer: Linux 4.8.4-vnl-14h-688-amd64
ohci_hcd
[ 5.440145] usb usb5: SerialNumber: 0000:00:16.0
[ 5.440635] hub 5-0:1.0: USB hub found
[ 5.440737] hub 5-0:1.0: 4 ports detected
[ 5.441333] ohci-platform: OHCI generic platform driver
[ 5.441373] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.441585] i8042: PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:PS2M]
at 0x60,0x64 irq 1,12
[ 5.453053] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 5.453068] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 5.453527] mousedev: PS/2 mouse device common for all mice
[ 5.454131] rtc_cmos 00:01: RTC can wake from S4
[ 5.454359] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0
[ 5.454468] rtc_cmos 00:01: alarms up to one month, 114 bytes nvram,
hpet irqs
[ 5.454489] i2c /dev entries driver
[ 5.454677] device-mapper: uevent: version 1.0.3
[ 5.454929] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23)
initialised: dm-devel@redhat.com
[ 5.460892] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input3
[ 6.189183] usb 2-2: Manufacturer: DCPKP019I2FSPE
[ 6.215984] ledtrig-cpu: registered to indicate activity on CPUs
[ 6.244674] NET: Registered protocol family 10
[ 6.272449] NET: Registered protocol family 17
[ 6.298762] Key type dns_resolver registered
[ 6.325701] microcode: CPU0: patch_level=0x05000101
[ 6.351796] microcode: CPU1: patch_level=0x05000101
[ 6.377551] microcode: Microcode Update Driver: v2.01
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 6.405050] registered taskstats version 1
[ 6.430987] Loading compiled-in X.509 certificates
[ 6.470683] Loaded X.509 cert 'Build time autogenerated kernel key:
bd5c5bf929a74e67f0a7d5055b9a105521ee69f7'
[ 6.498268] zswap: loaded using pool lzo/zbud
[ 6.545826] Key type trusted registered
[ 6.593135] Key type encrypted registered
[ 6.620205] AppArmor: AppArmor sha1 policy hashing enabled
[ 6.620211] ima: No TPM chip found, activating TPM-bypass!
[ 6.620280] evm: HMAC attrs: 0x1
[ 6.647646] Magic number: 4:466:728
[ 6.674207] rtc_cmos 00:01: setting system clock to 2016-10-24
09:43:10 UTC (1477302190)
[ 6.674567] acpi_cpufreq: overriding BIOS provided _PSD data
[ 6.700842] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 6.700843] EDD information not available.
[ 6.701035] PM: Hibernation image not present or could not be loaded.
[ 6.867123] Freeing unused kernel memory: 1536K (ffffffff9ef64000 -
ffffffff9f0e4000)
[ 6.895335] Write protecting the kernel read-only data: 14336k
[ 6.925614] Freeing unused kernel memory: 1632K (ffffa0e7c1868000 -
ffffa0e7c1a00000)
[ 6.956878] Freeing unused kernel memory: 312K (ffffa0e7c1db2000 -
ffffa0e7c1e00000)
[ 7.500165] random: systemd-udevd: uninitialized urandom read (16
bytes read)
[ 7.502417] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.502554] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.508348] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.508604] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.508670] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.510340] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.510620] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.510860] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.511110] random: udevadm: uninitialized urandom read (16 bytes
read)
[ 7.756796] ACPI: Video Device [VGA] (multi-head: yes rom: no post:
no)
[ 7.779862] FUJITSU Extended Socket Network Device Driver - version
1.1 - Copyright (c) 2015 FUJITSU LIMITED
[ 7.807418] acpi device:00: registered as cooling_device2
[ 7.836062] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
[ 7.863766] wmi: Mapper loaded
[ 7.892557] ahci 0000:00:11.0: version 3.0
[ 7.915278] ahci 0000:00:11.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps
0x3 impl SATA mode
[ 7.938118] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo
pmp pio slum part ccc
[ 7.962890] scsi host0: ahci
[ 7.978423] rtsx_pci 0000:02:00.0: rtsx_pci_acquire_irq: pcr->msi_en
= 1, pci->irq = 27
[ 7.986217] [drm] Initialized drm 1.1.0 20060810
[ 8.032725] scsi host1: ahci
[ 8.055934] ata1: SATA max UDMA/133 abar m1024@0xf0449000 port
0xf0449100 irq 19
[ 8.079299] ata2: SATA max UDMA/133 abar m1024@0xf0449000 port
0xf0449180 irq 19
[ 8.114449] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 8.176010] r8169 0000:06:00.0: can't disable ASPM; OS doesn't have
ASPM control
[ 8.251248] r8169 0000:06:00.0 eth0: RTL8105e at 0xffffbcf840e66000,
ac:16:2d:50:01:9c, XID 00a00000 IRQ 28
[ 8.319014] [drm] radeon kernel modesetting enabled.
[ 8.363910] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[ 8.386953] AMD IOMMUv2 functionality not available on this system
[ 8.400350] r8169 0000:06:00.0 eno1: renamed from eth0
[ 8.446255] CRAT table not found
[ 8.469268] Finished initializing topology ret=0
[ 8.492752] kfd kfd: Initialized module
[ 8.516712] checking generic (e0000000 410000) vs hw (e0000000
10000000)
[ 8.540213] fb: switching to radeondrmfb from VESA VGA
[ 8.564084] Console: switching to colour dummy device 80x25
[ 8.565815] [drm] initializing kernel modesetting (PALM 0x1002:0x9802
0x103C:0x3577 0x00).
[ 8.565875] [drm] register mmio base: 0xF0400000
[ 8.565886] [drm] register mmio size: 262144
[ 8.566837] ATOM BIOS: HP
[ 8.566992] radeon 0000:00:01.0: VRAM: 384M 0x0000000000000000 -
0x0000000017FFFFFF (384M used)
[ 8.567013] radeon 0000:00:01.0: GTT: 1024M 0x0000000018000000 -
0x0000000057FFFFFF
[ 8.567030] [drm] Detected VRAM RAM=384M, BAR=256M
[ 8.567040] [drm] RAM width 32bits DDR
[ 8.567364] [TTM] Zone kernel: Available graphics memory: 3883368
kiB
[ 8.567377] [TTM] Zone dma32: Available graphics memory: 2097152
kiB
[ 8.567388] [TTM] Initializing pool allocator
[ 8.567411] [TTM] Initializing DMA pool allocator
[ 8.567500] [drm] radeon: 384M of VRAM memory ready
[ 8.567514] [drm] radeon: 1024M of GTT memory ready.
[ 8.567562] [drm] Loading PALM Microcode
[ 8.567919] [drm] Internal thermal controller without fan control
[ 8.568133] [drm] Found smc ucode version: 0x00010601
[ 8.568228] [drm] radeon: dpm initialized
[ 8.568620] [drm] GART: num cpu pages 262144, num gpu pages 262144
[ 8.578880] [drm] PCIE GART of 1024M enabled (table at
0x0000000000162000).
[ 8.579171] radeon 0000:00:01.0: WB enabled
[ 8.579189] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr
0x0000000018000c00 and cpu addr 0xffffa0e935c01c00
[ 8.579209] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr
0x0000000018000c0c and cpu addr 0xffffa0e935c01c0c
[ 8.579816] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffbcf841632118
[ 8.579838] [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[ 8.579847] [drm] Driver supports precise vblank timestamp query.
[ 8.579859] radeon 0000:00:01.0: radeon: MSI limited to 32-bit
[ 8.579956] radeon 0000:00:01.0: radeon: using MSI.
[ 8.580021] [drm] radeon: irq initialized.
[ 8.591737] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 8.592727] ata1.00: ATA-9: WDC WD10JFCX-68N6GN0, 82.00A82, max
UDMA/133
[ 8.592753] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth
31/32), AA
[ 8.593635] ata1.00: configured for UDMA/133
[ 8.594184] scsi 0:0:0:0: Direct-Access ATA WDC WD10JFCX-68N
0A82 PQ: 0 ANSI: 5
[ 8.597514] [drm] ring test on 0 succeeded in 1 usecs
[ 8.597550] [drm] ring test on 3 succeeded in 2 usecs
[ 8.599694] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 8.601697] ata2.00: ATAPI: hp DVD RW AD-7740H, 1.80, max
UDMA/100
[ 8.604083] ata2.00: configured for UDMA/100
[ 8.643505] [drm] ring test on 5 succeeded in 1 usecs
[ 8.663388] [drm] UVD initialized successfully.
[ 8.664518] [drm] ib test on ring 0 succeeded in 0 usecs
[ 8.664581] [drm] ib test on ring 3 succeeded in 0 usecs
[ 8.700713] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks:
(1.00 TB/932 GiB)
[ 8.700743] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 8.700949] sd 0:0:0:0: [sda] Write Protect is off
[ 8.700966] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 8.701061] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 8.701854] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 8.703454] scsi 1:0:0:0: CD-ROM hp DVD RW AD-7740H
1.80 PQ: 0 ANSI: 5
[ 8.730916] sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram
cd/rw xa/form2 cdda tray
[ 8.730948] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 8.731989] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 8.732332] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 8.756004] sda: sda1 sda2 sda3 sda4 sda5
[ 8.758524] sd 0:0:0:0: [sda] Attached SCSI disk
[ 9.020031] random: fast init done
[ 9.200086] [drm] ib test on ring 5 succeeded
[ 9.275722] [drm] radeon atom DIG backlight initialized
[ 9.275752] [drm] Radeon Display Connectors
[ 9.275762] [drm] Connector 0:
[ 9.275772] [drm] LVDS-1
[ 9.275780] [drm] HPD1
[ 9.275792] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438
0x643c 0x643c
[ 9.275806] [drm] Encoders:
[ 9.275815] [drm] LCD1: INTERNAL_UNIPHY
[ 9.275824] [drm] Connector 1:
[ 9.275832] [drm] HDMI-A-1
[ 9.275840] [drm] HPD2
[ 9.275850] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448
0x644c 0x644c
[ 9.275864] [drm] Encoders:
[ 9.275872] [drm] DFP1: INTERNAL_UNIPHY
[ 9.275881] [drm] Connector 2:
[ 9.275889] [drm] VGA-1
[ 9.275899] [drm] DDC: 0x64d8 0x64d8 0x64dc 0x64dc 0x64e0 0x64e0
0x64e4 0x64e4
[ 9.275912] [drm] Encoders:
[ 9.275921] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 9.302422] psmouse serio1: synaptics: queried max coordinates: x
[..5634], y [..4598]
[ 9.392020] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5,
id: 0x1e0b1, caps: 0xd00073/0x240000/0xa0400/0x0, board id: 1680, fw id:
706145
[ 9.451227] input: SynPS/2 Synaptics TouchPad as
/devices/platform/i8042/serio1/input/input6
[ 9.774078] [drm] fb mappable at 0xE0366000
[ 9.774102] [drm] vram apper at 0xE0000000
[ 9.774111] [drm] size 4325376
[ 9.774120] [drm] fb depth is 24
[ 9.774129] [drm] pitch is 5632
[ 9.774684] fbcon: radeondrmfb (fb0) is primary device
[ 10.293951] Console: switching to colour frame buffer device 170x48
[ 10.302508] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[ 10.320194] [drm] Initialized radeon 2.46.0 20080528 for 0000:00:01.0
on minor 0
[ 10.411116] microcode: CPU0: new patch_level=0x05000119
[ 10.420899] microcode: CPU1: new patch_level=0x05000119
[ 10.568079] PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
[ 10.568087] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
[ 10.568093] PM: Marking nosave pages: [mem 0xdfb3f000-0xdfef4fff]
[ 10.568132] PM: Marking nosave pages: [mem 0xdff00000-0xffffffff]
[ 10.569054] PM: Basic memory bitmaps created
[ 10.570119] PM: Basic memory bitmaps freed
[ 11.001313] EXT4-fs (sda3): mounted filesystem with ordered data
mode. Opts: (null)
[ 12.433512] random: crng init done
[ 12.619856] systemd[1]: systemd 229 running in system mode. (+PAM
+AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 12.623506] systemd[1]: Detected architecture x86-64.
[ 12.638216] systemd[1]: Set hostname to <APU>.
[ 15.094651] systemd[1]: Listening on Journal Socket.
[ 15.097166] systemd[1]: Created slice System Slice.
[ 15.098966] systemd[1]: Started Forward Password Requests to Wall
Directory Watch.
[ 15.116320] systemd[1]: Starting Uncomplicated firewall...
[ 15.118845] systemd[1]: Set up automount Arbitrary Executable File
Formats File System Automount Point.
[ 15.196272] systemd[1]: Starting Load Kernel Modules...
[ 15.198126] systemd[1]: Reached target User and Group Name Lookups.
[ 16.157817] lp: driver loaded but no devices found
[ 16.208199] ppdev: user-space parallel port driver
[ 16.545953] rts5208: module is from the staging directory, the
quality is unknown, you have been warned.
[ 19.519308] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[ 19.826655] systemd-journald[228]: Received request to flush runtime
journal from PID 1
[ 20.740769] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00,
revision 0
[ 20.740782] piix4_smbus 0000:00:14.0: Using register 0x2c for SMBus
port selection
[ 20.742025] piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller
at 0xb20
[ 21.033470] shpchp: Standard Hot Plug PCI Controller Driver version:
0.4
[ 22.283136] kvm: Nested Virtualization enabled
[ 22.283145] kvm: Nested Paging enabled
[ 22.467467] media: Linux media interface: v0.10
[ 22.687645] input: HP WMI hotkeys as /devices/virtual/input/input7
[ 22.703915] Linux video capture interface: v2.00
[ 22.721064] ACPI Error: Field [B128] at 1152 exceeds Buffer [NULL]
size 160 (bits) (20160422/dsopcode-236)
[ 22.721086] ACPI Error: Method parse/execution failed
[\_SB.WMID.HWCD] (Node ffffa0e93e8bd2d0), AE_AML_BUFFER_LIMIT
(20160422/psparse-542)
[ 22.721114] ACPI Error: Method parse/execution failed
[\_SB.WMID.WMAD] (Node ffffa0e93e8bdb18), AE_AML_BUFFER_LIMIT
(20160422/psparse-542)
[ 22.752753] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC270:
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 22.752768] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0
(0x0/0x0/0x0/0x0/0x0)
[ 22.752773] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1
(0x21/0x0/0x0/0x0/0x0)
[ 22.752776] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 22.752779] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 22.752784] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 22.752788] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12
[ 22.763940] input: HDA ATI SB Mic as
/devices/pci0000:00/0000:00:14.2/sound/card0/input8
[ 22.764232] input: HDA ATI SB Headphone as
/devices/pci0000:00/0000:00:14.2/sound/card0/input9
[ 22.959203] ACPI Error: Field [B128] at 1152 exceeds Buffer [NULL]
size 160 (bits) (20160422/dsopcode-236)
[ 22.959228] ACPI Error: Method parse/execution failed
[\_SB.WMID.HWCD] (Node ffffa0e93e8bd2d0), AE_AML_BUFFER_LIMIT
(20160422/psparse-542)
[ 22.959258] ACPI Error: Method parse/execution failed
[\_SB.WMID.WMAD] (Node ffffa0e93e8bdb18), AE_AML_BUFFER_LIMIT
(20160422/psparse-542)
[ 23.175145] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390,
rev 0502 detected
[ 23.180433] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5390
detected
[ 23.211968] uvcvideo: Found UVC 1.00 device HP Webcam-101 (0c45:6321)
[ 23.226461] uvcvideo 2-2:1.0: Entity type for entity Extension 4 was
not initialized!
[ 23.226488] uvcvideo 2-2:1.0: Entity type for entity Processing 3 was
not initialized!
[ 23.226493] uvcvideo 2-2:1.0: Entity type for entity Camera 1 was not
initialized!
[ 23.226760] input: HP Webcam-101 as
/devices/pci0000:00/0000:00:16.2/usb2/2-2/2-2:1.0/input/input10
[ 23.228852] usbcore: registered new interface driver uvcvideo
[ 23.228857] USB Video Class driver (1.1.1)
[ 23.415854] ieee80211 phy0: Selected rate control algorithm
'minstrel_ht'
[ 23.440388] rt2800pci 0000:07:00.0 wlo1: renamed from wlan0
[ 23.764132] Adding 8000508k swap on /dev/sda4. Priority:-1 extents:1
across:8000508k FS
[ 24.608375] Adding 8000508k swap on /dev/sda5. Priority:-2 extents:1
across:8000508k FS
[ 24.870440] audit: type=1400 audit(1477302208.716:2):
apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=547
comm="apparmor_parser"
[ 24.870463] audit: type=1400 audit(1477302208.716:3):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=547
comm="apparmor_parser"
[ 24.870478] audit: type=1400 audit(1477302208.716:4):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=547
comm="apparmor_parser"
[ 24.870492] audit: type=1400 audit(1477302208.716:5):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/connman/scripts/dhclient-script" pid=547
comm="apparmor_parser"
[ 24.900860] audit: type=1400 audit(1477302208.748:6):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/snapd/snap-confine" pid=552 comm="apparmor_parser"
[ 24.900883] audit: type=1400 audit(1477302208.748:7):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper"
pid=552 comm="apparmor_parser"
[ 24.994109] audit: type=1400 audit(1477302208.840:8):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/telepathy/mission-control-5" pid=553
comm="apparmor_parser"
[ 24.994134] audit: type=1400 audit(1477302208.840:9):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/telepathy/telepathy-*" pid=553 comm="apparmor_parser"
[ 24.994149] audit: type=1400 audit(1477302208.840:10):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/telepathy/telepathy-*//pxgsettings" pid=553
comm="apparmor_parser"
[ 24.994165] audit: type=1400 audit(1477302208.840:11):
apparmor="STATUS" operation="profile_load"
name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=553
comm="apparmor_parser"
[ 33.331935] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 33.681889] r8169 0000:06:00.0 eno1: link down
[ 33.682043] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 33.735900] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 33.736091] ieee80211 phy0: rt2x00lib_request_firmware: Info -
Loading firmware file 'rt2860.bin'
[ 33.788077] ieee80211 phy0: rt2x00lib_request_firmware: Info -
Firmware detected - version: 0.34
[ 33.939313] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 34.552796] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 40.269162] Bluetooth: Core ver 2.21
[ 40.269219] NET: Registered protocol family 31
[ 40.269222] Bluetooth: HCI device and connection manager initialized
[ 40.269234] Bluetooth: HCI socket layer initialized
[ 40.269241] Bluetooth: L2CAP socket layer initialized
[ 40.269259] Bluetooth: SCO socket layer initialized
[ 40.405984] Netfilter messages via NETLINK v0.30.
[ 42.117110] ACPI Error: Field [B128] at 1152 exceeds Buffer [NULL]
size 160 (bits) (20160422/dsopcode-236)
[ 42.117136] ACPI Error: Method parse/execution failed
[\_SB.WMID.HWCD] (Node ffffa0e93e8bd2d0), AE_AML_BUFFER_LIMIT
(20160422/psparse-542)
[ 42.117170] ACPI Error: Method parse/execution failed
[\_SB.WMID.WMAD] (Node ffffa0e93e8bdb18), AE_AML_BUFFER_LIMIT
(20160422/psparse-542)
[ 46.782960] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 46.782966] Bluetooth: BNEP filters: protocol multicast
[ 46.782979] Bluetooth: BNEP socket layer initialized
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-24 9:35 ` Borislav Petkov
@ 2016-10-24 13:13 ` sonofagun
2016-10-24 17:14 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-24 13:13 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> Sure, give me the exact command you're executing so that I can do it
> here.
No command needed, just type:
sudo perf stat -a
and immediately exit with ctrl+C. That will give you a glimpse. See "%
of all branches"
next open firefox, rerun the same command after firefox launches and
immediately exit with ctrl+C
On that piece of crap I get branch-misses above 10% from boot without
executing anything and perf does not like it so it displays it with red
colour.
On my quad core kabini APU, in order to get 9% branch-misses I have to
open 50 tabs on firefox. Something is terribly wrong here.
> Out of pure interest: do you remember how exactly you did reproduce
> this
> issue?
Yes, using Ubuntu 16.04 will just crash everything! For example I had
crashes with the software updater program. Moreover firefox would become
unresponsive even with one tab.
Luckily initial tests of 16.10 seem promising as it is lighter and
consumes 3~5% less RAM! Debian which was lighter was more responsive and
had no crashes except an oops from adobe flash.
I believe that the bug is triggered by the unusually high branch-misses
specific to this machine. After the fix, I got better OS and program
responsiveness.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-24 13:13 ` sonofagun
@ 2016-10-24 17:14 ` Borislav Petkov
2016-10-24 20:39 ` sonofagun
2016-10-28 16:21 ` Borislav Petkov
0 siblings, 2 replies; 24+ messages in thread
From: Borislav Petkov @ 2016-10-24 17:14 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Mon, Oct 24, 2016 at 04:13:25PM +0300, sonofagun@openmailbox.org wrote:
> No command needed, just type: sudo perf stat -a and immediately exit
> with ctrl+C. That will give you a glimpse. See "% of all branches"
$ ./perf stat -a --repeat 10 sleep 1s
Performance counter stats for 'system wide' (10 runs):
2013.974964 cpu-clock (msec) # 1.999 CPUs utilized ( +- 0.02% )
88 context-switches # 0.044 K/sec ( +- 2.05% )
2 cpu-migrations # 0.001 K/sec ( +- 8.55% )
75 page-faults # 0.037 K/sec ( +- 0.42% )
81,177,296 cycles # 0.040 GHz ( +- 0.76% ) (66.62%)
0 stalled-cycles-frontend (66.63%)
0 stalled-cycles-backend # 0.00% backend cycles idle (66.64%)
9,602,846 instructions # 0.12 insn per cycle ( +- 2.08% ) (66.65%)
1,698,414 branches # 0.843 M/sec ( +- 4.26% ) (66.75%)
327,945 branch-misses # 19.31% of all branches ( +- 1.76% ) (66.72%)
1.007545371 seconds time elapsed ( +- 0.02% )
Now disable erratum workaround:
$ wrmsr --all 0xc0011021 0x10008000
$ rdmsr --all 0xc0011021
10008000
10008000
$ ./perf stat -a --repeat 10 sleep 1s
Performance counter stats for 'system wide' (10 runs):
2012.521775 cpu-clock (msec) # 1.999 CPUs utilized ( +- 0.02% )
91 context-switches # 0.045 K/sec ( +- 2.62% )
3 cpu-migrations # 0.001 K/sec ( +- 13.07% )
75 page-faults # 0.037 K/sec ( +- 0.66% )
82,215,531 cycles # 0.041 GHz ( +- 1.08% ) (66.60%)
0 stalled-cycles-frontend (66.60%)
0 stalled-cycles-backend # 0.00% backend cycles idle (66.62%)
9,444,884 instructions # 0.11 insn per cycle ( +- 2.11% ) (66.70%)
1,484,480 branches # 0.738 M/sec ( +- 5.16% ) (66.78%)
303,382 branch-misses # 20.44% of all branches ( +- 1.44% ) (66.70%)
1.006812225 seconds time elapsed ( +- 0.02% )
so that doesn't tell me a whole lot.
> next open firefox, rerun the same command after firefox launches and
> immediately exit with ctrl+C On that piece of crap I get branch-misses
> above 10% from boot without executing anything and perf does not like
> it so it displays it with red colour. On my quad core kabini APU,
> in order to get 9% branch-misses I have to open 50 tabs on firefox.
> Something is terribly wrong here.
Well, Ontario is a small core and with the erratum workaround in place,
it does get a bit worse too, apparently.
Let's see how many branch misses we get when starting firefox:
* with workaround:
$ echo 3 > /proc/sys/vm/drop_caches && ./perf stat ./firefox.sh
Performance counter stats for './firefox.sh':
257.037242 task-clock (msec) # 0.103 CPUs utilized
332 context-switches # 0.001 M/sec
6 cpu-migrations # 0.023 K/sec
1,022 page-faults # 0.004 M/sec
213,464,893 cycles # 0.830 GHz (63.29%)
0 stalled-cycles-frontend (62.76%)
0 stalled-cycles-backend # 0.00% backend cycles idle (66.88%)
106,763,405 instructions # 0.50 insn per cycle (73.54%)
23,794,511 branches # 92.572 M/sec (73.32%)
2,629,193 branch-misses # 11.05% of all branches (66.16%)
2.501140816 seconds time elapsed
* without it:
$ echo 3 > /proc/sys/vm/drop_caches && ./perf stat ./firefox.sh
Performance counter stats for './firefox.sh':
196.561165 task-clock (msec) # 0.082 CPUs utilized
276 context-switches # 0.001 M/sec
9 cpu-migrations # 0.046 K/sec
932 page-faults # 0.005 M/sec
162,697,731 cycles # 0.828 GHz (70.27%)
0 stalled-cycles-frontend (65.15%)
0 stalled-cycles-backend # 0.00% backend cycles idle (70.58%)
96,363,308 instructions # 0.59 insn per cycle (69.86%)
22,215,057 branches # 113.019 M/sec (61.63%)
935,833 branch-misses # 4.21% of all branches (66.72%)
2.392346081 seconds time elapsed
Btw, the script simply starts firefox, sleeps 2s and kills it.
Hohumm, yeah, the workaround impacts the number of branch misses. It
probably disables some branch predictor optimization or so, which is
"problematic" in certain scenarios.
I guess we still want it because first we should not explode and then go
fast :)
> Yes, using Ubuntu 16.04 will just crash everything! For example I had
> crashes with the software updater program. Moreover firefox would become
> unresponsive even with one tab.
Ok, lemme install 16.04 on that box and see if I can reproduce.
I'm thinking currently that if it is not easily triggerable, I could
make the erratum workaround off by default and have a command line
option which people can enable in case they experience any of the
issues...
> Luckily initial tests of 16.10 seem promising as it is lighter and
> consumes 3~5% less RAM! Debian which was lighter was more responsive
> and had no crashes except an oops from adobe flash. I believe that the
> bug is triggered by the unusually high branch-misses specific to this
> machine. After the fix, I got better OS and program responsiveness.
Ok.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-24 17:14 ` Borislav Petkov
@ 2016-10-24 20:39 ` sonofagun
2016-10-25 9:29 ` Borislav Petkov
2016-10-28 16:21 ` Borislav Petkov
1 sibling, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-24 20:39 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> so that doesn't tell me a whole lot.
It does to me! That cpu family is "broken" both on B0 and C0. I think
that a CPU at 30% load should not have >31% branch misses. For example
with 5% CPU usage you can't expect to get 10% branch-misses...
> Well, Ontario is a small core and with the erratum workaround in place,
> it does get a bit worse too, apparently.
Yes but on C0 I got better results. Maybe the BIOS vendor got similar
results and did not apply the fix. They use the same BIOS for all
machines B0, C0 and that could be the reason for not applying the 688
workaround.
I think we are going to the wrong place here but I will not try to
influence you at all. I only apply the fix once per boot and I think
that we are not supposed to apply, remove and then reapply workarounds
on the fly. Be carefull, you might hang your machine, brick your board
or destroy your APU!
The truth is that my system behaves better with the patch.
The problem is that there is no way to get what I need! That is the
E-300 datasheet...They give everything for the north and the south but
we have poor documentation for the APU itself...I will contact AMD to
see if I can get the APU datasheet so that we have a clue what those
bits actualy do.
> Hohumm, yeah, the workaround impacts the number of branch misses. It
> probably disables some branch predictor optimization or so, which is
> "problematic" in certain scenarios.
That is obvious. You can't say what it does, it might disable an
internal buffer or force a CPU subsystem to run at a lower frequency,
who knows?
> I guess we still want it because first we should not explode and then
> go
> fast :)
Exactly. I agree with that as I want to eliminate the crashes. Keep in
mind that speed is something that all those APUs do not have and will
never have, stability is what we are trying to improve.
> I'm thinking currently that if it is not easily triggerable, I could
> make the erratum workaround off by default and have a command line
> option which people can enable in case they experience any of the
> issues...
No problem, it is up to you. As I said above, I will not try to change
your mind.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-24 20:39 ` sonofagun
@ 2016-10-25 9:29 ` Borislav Petkov
2016-10-25 13:16 ` sonofagun
0 siblings, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-25 9:29 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Mon, Oct 24, 2016 at 11:39:47PM +0300, sonofagun@openmailbox.org wrote:
> It does to me! That cpu family is "broken" both on B0 and C0. I think
> that a CPU at 30% load should not have >31% branch misses. For example
> with 5% CPU usage you can't expect to get 10% branch-misses...
Why not? It all depends on the load type, working set and the access
patterns. There's no strong correlation between the load of a machine
and the amount of branch misses...
> Yes but on C0 I got better results. Maybe the BIOS vendor got similar
> results and did not apply the fix.
Well, there's a C0 stepping which doesn't need the fix because it was
fixed in the silicon.
You can check that by doing:
setpci -s 0x18.4 0x164.l
and looking at bit 2. If it is set, the erratum is fixed.
> They use the same BIOS for all machines B0, C0 and that could be the
> reason for not applying the 688 workaround. I think we are going to
> the wrong place here but I will not try to influence you at all. I
> only apply the fix once per boot and I think that we are not supposed
> to apply, remove and then reapply workarounds on the fly.
No, I don't mean that - I'm talking about *not* applying it by default
and when people start seeing issues like that, they can boot their
machines with something like "enable_e688_workaround" or so and it will
get applied then. I.e., an "opt-in" deal.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-25 9:29 ` Borislav Petkov
@ 2016-10-25 13:16 ` sonofagun
0 siblings, 0 replies; 24+ messages in thread
From: sonofagun @ 2016-10-25 13:16 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> Why not? It all depends on the load type, working set and the access
> patterns. There's no strong correlation between the load of a machine
> and the amount of branch misses...
Yes I did not say that there is a linear correlation but that does not
mean that those two numbers move opposite to each other. On all our
systems running more tasks that consume more CPU and memory result in
increased branch misses.
It is normal as one thread might block another and a third thread might
wait for the first thread to finish in order to resume.
It is not normal to have increased misses only when the OS is loaded
and running in idle without doing anything. Unless you are talking for
AMD F14.
I wonder if we should just flush the L2 and disable it completely on AMD
F14. Since this is an APU I have no idea if the onboard graphics can
operate properly without L2.
> setpci -s 0x18.4 0x164.l
>
> and looking at bit 2. If it is set, the erratum is fixed.
Will do but there is no meaning as I already told you on the first mail
that D18F4x164 is 00000003h. It will not change.
> No, I don't mean that - I'm talking about *not* applying it by default
> and when people start seeing issues like that, they can boot their
> machines with something like "enable_e688_workaround" or so and it will
> get applied then. I.e., an "opt-in" deal.
Yes I got it. I have no problem, you are free to do what you think is
the best solution. Just ensure that it will not be possible to apply the
fix to F16.
Even if you decide to not include the fix at all in the kernel, I still
have the patch for my system and it works.
Did you get any crashes on your B0 box with Ubuntu? Is it a desktop
system or a laptop?
The irony is that this laptop was bought without USB3 on purpose to
achieve maximum stability... Luckily we didn't stick to the original
plan to buy two laptops :)
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-24 17:14 ` Borislav Petkov
2016-10-24 20:39 ` sonofagun
@ 2016-10-28 16:21 ` Borislav Petkov
2016-10-31 21:54 ` sonofagun
1 sibling, 1 reply; 24+ messages in thread
From: Borislav Petkov @ 2016-10-28 16:21 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Mon, Oct 24, 2016 at 07:14:50PM +0200, Borislav Petkov wrote:
> > Yes, using Ubuntu 16.04 will just crash everything! For example I had
> > crashes with the software updater program. Moreover firefox would become
> > unresponsive even with one tab.
>
> Ok, lemme install 16.04 on that box and see if I can reproduce.
Ok, Ubuntu 16.04.1 is running on the box now, no issues so far. Any
special workload I should run?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-28 16:21 ` Borislav Petkov
@ 2016-10-31 21:54 ` sonofagun
2016-10-31 22:59 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-31 21:54 UTC (permalink / raw)
To: Borislav Petkov; +Cc: linux-kernel, Nikos Barkas
> Ok, Ubuntu 16.04.1 is running on the box now, no issues so far. Any
> special workload I should run?
No, will simply crash without running something special! If you get no
issues then that is bad news. I get frequent and repeatable crashes. I
forgot to mention that all those crashes occur at program launch. If the
program launches, it does not crash. Unfortunately with Ubuntu it is not
possible to keep oopses from the error report program. On the laptop we
have a Debian installation, I will switch to it and get crash
information there so that we figure out why it behaves that way. Besides
that, I have some more tests to do but I am running out of ideas so I
might not be able to help you more on it as my laptop appears to be
really broken! Poor performance might be the result here and not the
cause of my issues. The 688 fix just makes the system respond better. As
far as I am concerned, I do not wish any module options for turning on
the fix. I would prefer to use DMI maching for this specific machine and
thus having the fix automatically.
All subsystems of the laptop appear to be good(RAM has been tested and
the HDD has passed our test). There is a sound issue on the HDA but such
issues are common on most laptops and will be dealt soon.
> Is it a desktop system or a laptop?
I got no reply on this question so I suppose you have a desktop. Since
my APU is installed on a laptop, I expect different behaviour.
There were many intel based laptops that had fewer lanes on the DMI
interconnect bridging northbridge and southbridge. Maybe my laptop has
the A-Link in reduced mode. That could explain my performance issues. It
must be easy to verify that as all documents are available for its
northbridge and southbridge. I will check the settings of both chips
thoroughly.
My brother has spotted a C70 board. Normally I would not buy it but it
has a better but slower(without CPB) F14 CPU and I am curious if it will
behave better like your board does. I might order it if it is still
available.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-31 21:54 ` sonofagun
@ 2016-10-31 22:59 ` Borislav Petkov
0 siblings, 0 replies; 24+ messages in thread
From: Borislav Petkov @ 2016-10-31 22:59 UTC (permalink / raw)
To: sonofagun; +Cc: linux-kernel, Nikos Barkas
On Mon, Oct 31, 2016 at 11:54:44PM +0200, sonofagun@openmailbox.org wrote:
> No, will simply crash without running something special! If you get no
> issues then that is bad news. I get frequent and repeatable crashes. I
> forgot to mention that all those crashes occur at program launch. If the
> program launches, it does not crash. Unfortunately with Ubuntu it is not
> possible to keep oopses from the error report program.
Can't you enable crash dumps?
$ ulimit -c unlimited
That should reenable core dumping which can then be examined with gdb.
You could put the program executable and the core somewhere on the web
so that I can take a look...
In any case, I'd like to see what those crashes look like. Can you send
dmesg, does it even say something in dmesg related to those crashes?
> On the laptop we have a Debian installation, I will switch to it and
> get crash information there so that we figure out why it behaves that
> way. Besides that, I have some more tests to do but I am running out
> of ideas so I might not be able to help you more on it as my laptop
> appears to be really broken!
Maybe a hw issue? RAM broken, cooling failing...
> Poor performance might be the result here and not the cause of my
> issues. The 688 fix just makes the system respond better. As far as I
> am concerned, I do not wish any module options for turning on the fix.
> I would prefer to use DMI maching for this specific machine and thus
> having the fix automatically.
The problem with DMI strings is that then we have to always go and
update them. And that's always a PITA.
I'm just trying to avoid an unnecessary performance penalty to users
with the erratum workaround where the erratum itself didn't even occur
in the first place. Like in my case, for example. I've never had any
issues with that machine for the time I've been using it.
> All subsystems of the laptop appear to be good(RAM has been tested and
> the HDD has passed our test). There is a sound issue on the HDA but
> such issues are common on most laptops and will be dealt soon.
If by "tested" you mean, you ran memtest on it, memtest is notorious for
not always catching faulty DIMMs.
> > Is it a desktop system or a laptop?
> I got no reply on this question so I suppose you have a desktop.
Oh sorry, I must've missed that question. No, the Ontario I have is a
laptop, something like this one:
https://support.lenovo.com/de/en/documents/pd015763
x121e with an AMD CPU, I *think* it is E-350.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
2016-10-19 13:58 sonofagun
@ 2016-10-19 15:00 ` Borislav Petkov
0 siblings, 0 replies; 24+ messages in thread
From: Borislav Petkov @ 2016-10-19 15:00 UTC (permalink / raw)
To: sonofagun, Nikos Barkas; +Cc: linux-kernel
On Wed, Oct 19, 2016 at 04:58:08PM +0300, sonofagun@openmailbox.org wrote:
>
> AMD F14h machines have an erratum which can cause unpredictable program
> behaviour under specific branch conditions. The workaround is to set
> MSRC001_1021[14] and MSRC001_1021[3]. Both bits are reserved for this MSR,
> so we trust AMD suggestions. Since there is no BIOS update containing that
> workaround for some machines, we do it ourselves unconditionally on this
> family too. Our Compaq CQ57 laptop which has broken firmware in various
> areas does not contain both workarounds(MSRc0011021: 0000000010208000)...
...
> +#define MSR_AMD64_IC_CFG 0xC0011021
> +
> +static void init_amd_on(struct cpuinfo_x86 *c)
> +{
> + /*
> + * Apply erratum 688 fix unconditionally so machines without a BIOS
> + * fix work.
> + */
> + msr_set_bit(MSR_AMD64_IC_CFG, 3);
> + msr_set_bit(MSR_AMD64_IC_CFG, 14);
> +}
You can't force this unconditionally. Look at the suggested workaround:
"BIOS should set MSRC001_1021[14] = 1b and MSRC001_1021[3] = 1b. This
workaround is required only when bit 2 of Fixed Errata Status Register
(D18F4x164[2]) = 0b."
So you need to do something like this:
if (c->x86_model == 2 && c->x86_mask == 0) {
u32 val = pci_read_config(0, 0x18, 0x4, 0x164);
if (!(val & BIT(2))) {
msr_set_bit(MSR_AMD64_IC_CFG, 3);
msr_set_bit(MSR_AMD64_IC_CFG, 14);
}
}
Also, please paste /proc/cpuinfo from that machine.
Then, keep that *whole* changelog above when sending v2 of the patch - I like
the level of detail of your explanation! ;-)
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
^ permalink raw reply [flat|nested] 24+ messages in thread
* [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
@ 2016-10-19 13:58 sonofagun
2016-10-19 15:00 ` Borislav Petkov
0 siblings, 1 reply; 24+ messages in thread
From: sonofagun @ 2016-10-19 13:58 UTC (permalink / raw)
To: linux-kernel
AMD F14h machines have an erratum which can cause unpredictable program
behaviour under specific branch conditions. The workaround is to set
MSRC001_1021[14] and MSRC001_1021[3]. Both bits are reserved for this
MSR, so we trust AMD suggestions. Since there is no BIOS update
containing that workaround for some machines, we do it ourselves
unconditionally on this family too. Our Compaq CQ57 laptop which has
broken firmware in various areas does not contain both
workarounds(MSRc0011021: 0000000010208000)...
HP does not release a proper BIOS even though we have contacted them and
requested an updated BIOS that will fix all errors we spotted. As it is
not currently covered by any warranty, they do not support it. HP does
not care, but Linux kernel cares to patch out-of-warranty hardware with
crappy firmware!
Thanks to the author of commit d1992996753132e2dafe955cccb2fb0714d3cfc4
(x86/AMD: Apply erratum 665 on machines without a BIOS fix) as he paved
the way to this fix. That patch was not applicable on our machine but it
brought back to surface a long standing bug of our E-300 laptop. Poor
performance under Debian was observed and things got worse after
switching to Ubuntu as crashes became more frequent! As a result the
laptop got replaced with a desktop.
After some time, we decided to dig deeper and see what is wrong with our
laptop. Actually perf proved that something was terrible wrong as
branch-misses reached 40% within a minute after booting the E-300
ontario C0 APU! Disabling the second CPU did not help either. CPU
Revision Guide erratum 688 seemed promising as it described our issues
and we prepared a fix. Now the laptop works and has both
workarounds(MSRc0011021: 000000001020c008)! Since this erratum affects
many laptops and some tablets, we request to backport it to stable
kernels.
Tested on Compaq CQ57-499 laptop.
Signed-off-by: Ioannis Barkas <sonofagun@openmailbox.org>
Signed-off-by: Nikos Barkas <levelwol@gmail.com>
Cc: Borislav Petkov <bp@suse.de>
Cc: <stable@vger.kernel.org>
---
Hello we are Ioannis Barkas (sonofagun@openmailbox.org) and Nikos Barkas
(levelwol@gmail.com).
This patch was sent from my yahoo e-mail in the morning and got
rejected! Why?
Resending...
We have had poor performance on our AMD laptop with Debian for some
years. Initial value of MSRc0011021 is 0000000010208000h and D18F4x164
is 00000003h. Our laptop was not usable even with Ubuntu 16.04 using the
radeon driver. What is worse, opening firefox with
https://planefinder.net/ after booting Ubuntu, resulted in firefox
crashes again and again. After this patch we have not met any problem
with that webpage and firefox. Unfortunately linux-tools were not
present for our custom kernel and perf could not be launched:( When the
patch arrives on Ubuntu 16.10 kernel, we shall recheck it. If
branch-misses remain above 10%, we will open a bug for it.
--- a/arch/x86/kernel/cpu/amd.c 2016-10-07 16:03:33.000000000 +0300
+++ b/arch/x86/kernel/cpu/amd.c 2016-10-12 13:25:34.791720549 +0300
@@ -680,6 +680,18 @@ static void init_amd_ln(struct cpuinfo_x
msr_set_bit(MSR_AMD64_DE_CFG, 31);
}
+#define MSR_AMD64_IC_CFG 0xC0011021
+
+static void init_amd_on(struct cpuinfo_x86 *c)
+{
+ /*
+ * Apply erratum 688 fix unconditionally so machines without a BIOS
+ * fix work.
+ */
+ msr_set_bit(MSR_AMD64_IC_CFG, 3);
+ msr_set_bit(MSR_AMD64_IC_CFG, 14);
+}
+
static void init_amd_bd(struct cpuinfo_x86 *c)
{
u64 value;
@@ -738,6 +750,7 @@ static void init_amd(struct cpuinfo_x86
case 0xf: init_amd_k8(c); break;
case 0x10: init_amd_gh(c); break;
case 0x12: init_amd_ln(c); break;
+ case 0x14: init_amd_on(c); break;
case 0x15: init_amd_bd(c); break;
}
^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2016-10-31 22:59 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-21 16:19 [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun
2016-10-21 16:47 ` Borislav Petkov
2016-10-21 21:51 ` sonofagun
2016-10-21 23:01 ` Borislav Petkov
2016-10-22 11:16 ` sonofagun
2016-10-22 14:12 ` Borislav Petkov
2016-10-23 9:39 ` sonofagun
2016-10-23 9:57 ` Borislav Petkov
2016-10-23 17:06 ` sonofagun
2016-10-23 17:25 ` Borislav Petkov
2016-10-23 21:02 ` sonofagun
2016-10-23 21:39 ` Borislav Petkov
2016-10-24 11:38 ` sonofagun
2016-10-24 9:35 ` Borislav Petkov
2016-10-24 13:13 ` sonofagun
2016-10-24 17:14 ` Borislav Petkov
2016-10-24 20:39 ` sonofagun
2016-10-25 9:29 ` Borislav Petkov
2016-10-25 13:16 ` sonofagun
2016-10-28 16:21 ` Borislav Petkov
2016-10-31 21:54 ` sonofagun
2016-10-31 22:59 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2016-10-19 13:58 sonofagun
2016-10-19 15:00 ` Borislav Petkov
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.