Hardware error during system boot
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
Everything seems to be working correctly, but during the loading process of Manjaro Linux I see hardware errors shown on below picture (I have disabled splash screen).
Currently I use kernel 4.13.11-1.
Update: Errors do not show up when using kernel 4.9.61-3.
What is the cause of those errors and how can I get rid of them?
manjaro
asked Nov 10 '17 at 11:52
Luke
416
 |Â
show 7 more comments
up vote
3
down vote
favorite
Everything seems to be working correctly, but during the loading process of Manjaro Linux I see hardware errors shown on below picture (I have disabled splash screen).
Currently I use kernel 4.13.11-1.
Update: Errors do not show up when using kernel 4.9.61-3.
What is the cause of those errors and how can I get rid of them?
manjaro
asked Nov 10 '17 at 11:52
Luke
416
1
The 'mce' in those lines stands for 'machine check exception' and according to this Wikipedia article, it sounds like it might be fairly serious.
– Time4Tea
Nov 13 '17 at 3:53
1
Does that article help? Errors not showing up with the other kernel maybe because of (1) no mce reporting in older kernel, or (2) different code through boot doesn't cause that particular problem to happen.
– dirkt
Nov 15 '17 at 13:16
1
@Luke Basically the linux kernel can do microcode updates to the processor if its included before the initrd. The error you see could be the kernel trying to use the CPU in a way only meant for an updated microcode. Actually both AMD and Intel cpus do this. But AMD works automatically whereas intel is loaded manually. So I'll assume if thats it you must have an intel.
– jdwolf
Nov 17 '17 at 0:54
1
@Luke it happens automatically most of the time thats why.
– jdwolf
Nov 17 '17 at 0:57
1
@Luke wiki.archlinux.org/index.php/Microcode Try following that and you can rule it out at least. It can't really hurt much if its not it.
– jdwolf
Nov 17 '17 at 0:58
 |Â
show 7 more comments
up vote
3
down vote
favorite
up vote
3
down vote
favorite
Everything seems to be working correctly, but during the loading process of Manjaro Linux I see hardware errors shown on below picture (I have disabled splash screen).
Currently I use kernel 4.13.11-1.
Update: Errors do not show up when using kernel 4.9.61-3.
What is the cause of those errors and how can I get rid of them?
manjaro
asked Nov 10 '17 at 11:52
Luke
416
Everything seems to be working correctly, but during the loading process of Manjaro Linux I see hardware errors shown on below picture (I have disabled splash screen).
Currently I use kernel 4.13.11-1.
Update: Errors do not show up when using kernel 4.9.61-3.
What is the cause of those errors and how can I get rid of them?
manjaro
asked Nov 10 '17 at 11:52
Luke
416
edited Nov 15 '17 at 13:03
asked Nov 10 '17 at 11:52
Luke
416
asked Nov 10 '17 at 11:52
Luke
416
asked Nov 10 '17 at 11:52
Luke
416
416
1
The 'mce' in those lines stands for 'machine check exception' and according to this Wikipedia article, it sounds like it might be fairly serious.
– Time4Tea
Nov 13 '17 at 3:53
1
Does that article help? Errors not showing up with the other kernel maybe because of (1) no mce reporting in older kernel, or (2) different code through boot doesn't cause that particular problem to happen.
– dirkt
Nov 15 '17 at 13:16
1
@Luke Basically the linux kernel can do microcode updates to the processor if its included before the initrd. The error you see could be the kernel trying to use the CPU in a way only meant for an updated microcode. Actually both AMD and Intel cpus do this. But AMD works automatically whereas intel is loaded manually. So I'll assume if thats it you must have an intel.
– jdwolf
Nov 17 '17 at 0:54
1
@Luke it happens automatically most of the time thats why.
– jdwolf
Nov 17 '17 at 0:57
1
@Luke wiki.archlinux.org/index.php/Microcode Try following that and you can rule it out at least. It can't really hurt much if its not it.
– jdwolf
Nov 17 '17 at 0:58
 |Â
show 7 more comments
1
The 'mce' in those lines stands for 'machine check exception' and according to this Wikipedia article, it sounds like it might be fairly serious.
– Time4Tea
Nov 13 '17 at 3:53
1
Does that article help? Errors not showing up with the other kernel maybe because of (1) no mce reporting in older kernel, or (2) different code through boot doesn't cause that particular problem to happen.
– dirkt
Nov 15 '17 at 13:16
1
@Luke Basically the linux kernel can do microcode updates to the processor if its included before the initrd. The error you see could be the kernel trying to use the CPU in a way only meant for an updated microcode. Actually both AMD and Intel cpus do this. But AMD works automatically whereas intel is loaded manually. So I'll assume if thats it you must have an intel.
– jdwolf
Nov 17 '17 at 0:54
1
@Luke it happens automatically most of the time thats why.
– jdwolf
Nov 17 '17 at 0:57
1
@Luke wiki.archlinux.org/index.php/Microcode Try following that and you can rule it out at least. It can't really hurt much if its not it.
– jdwolf
Nov 17 '17 at 0:58
1
1
The 'mce' in those lines stands for 'machine check exception' and according to this Wikipedia article, it sounds like it might be fairly serious.
– Time4Tea
Nov 13 '17 at 3:53
The 'mce' in those lines stands for 'machine check exception' and according to this Wikipedia article, it sounds like it might be fairly serious.
– Time4Tea
Nov 13 '17 at 3:53
1
1
Does that article help? Errors not showing up with the other kernel maybe because of (1) no mce reporting in older kernel, or (2) different code through boot doesn't cause that particular problem to happen.
– dirkt
Nov 15 '17 at 13:16
Does that article help? Errors not showing up with the other kernel maybe because of (1) no mce reporting in older kernel, or (2) different code through boot doesn't cause that particular problem to happen.
– dirkt
Nov 15 '17 at 13:16
1
1
@Luke Basically the linux kernel can do microcode updates to the processor if its included before the initrd. The error you see could be the kernel trying to use the CPU in a way only meant for an updated microcode. Actually both AMD and Intel cpus do this. But AMD works automatically whereas intel is loaded manually. So I'll assume if thats it you must have an intel.
– jdwolf
Nov 17 '17 at 0:54
@Luke Basically the linux kernel can do microcode updates to the processor if its included before the initrd. The error you see could be the kernel trying to use the CPU in a way only meant for an updated microcode. Actually both AMD and Intel cpus do this. But AMD works automatically whereas intel is loaded manually. So I'll assume if thats it you must have an intel.
– jdwolf
Nov 17 '17 at 0:54
1
1
@Luke it happens automatically most of the time thats why.
– jdwolf
Nov 17 '17 at 0:57
@Luke it happens automatically most of the time thats why.
– jdwolf
Nov 17 '17 at 0:57
1
1
@Luke wiki.archlinux.org/index.php/Microcode Try following that and you can rule it out at least. It can't really hurt much if its not it.
– jdwolf
Nov 17 '17 at 0:58
@Luke wiki.archlinux.org/index.php/Microcode Try following that and you can rule it out at least. It can't really hurt much if its not it.
– jdwolf
Nov 17 '17 at 0:58
 |Â
show 7 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f403732%2fhardware-error-during-system-boot%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
The 'mce' in those lines stands for 'machine check exception' and according to this Wikipedia article, it sounds like it might be fairly serious.
– Time4Tea
Nov 13 '17 at 3:53
1
Does that article help? Errors not showing up with the other kernel maybe because of (1) no mce reporting in older kernel, or (2) different code through boot doesn't cause that particular problem to happen.
– dirkt
Nov 15 '17 at 13:16
1
@Luke Basically the linux kernel can do microcode updates to the processor if its included before the initrd. The error you see could be the kernel trying to use the CPU in a way only meant for an updated microcode. Actually both AMD and Intel cpus do this. But AMD works automatically whereas intel is loaded manually. So I'll assume if thats it you must have an intel.
– jdwolf
Nov 17 '17 at 0:54
1
@Luke it happens automatically most of the time thats why.
– jdwolf
Nov 17 '17 at 0:57
1
@Luke wiki.archlinux.org/index.php/Microcode Try following that and you can rule it out at least. It can't really hurt much if its not it.
– jdwolf
Nov 17 '17 at 0:58