How to check for hardware faults?

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I've seen some worrying messages in dmesg lately.
Specifically bunch of:
[ 19.367114] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 19.367148] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000081/00002000
[ 19.367172] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 19.367192] pcieport 0000:00:1c.5: [ 7] Bad DLLP
And:
[ 20.121489] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
[ 20.124485] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
Or:
[ 19.367213] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
[ 19.367218] pcieport 0000:00:1c.5: can't find device of ID00e5
And most worryingly:
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: firmware crashed! (guid a62c787e-4709-4d94-a1a7-4e9357c2555a)
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to get memcpy hi address for firmware address 4: -16
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to read firmware dump area: -16
(This one happens roughly 50% of the time on boot)
All of these started appearing in a fairly short time (~2 weeks) And since all of them could be caused by a hardware failure, I am most worried, is there a software way to test all or most of the hardware?
(Apart from the firmware crash, which causes the wifi to stop working, I did not see any impact of the previous errors)
hardware
add a comment |Â
up vote
0
down vote
favorite
I've seen some worrying messages in dmesg lately.
Specifically bunch of:
[ 19.367114] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 19.367148] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000081/00002000
[ 19.367172] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 19.367192] pcieport 0000:00:1c.5: [ 7] Bad DLLP
And:
[ 20.121489] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
[ 20.124485] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
Or:
[ 19.367213] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
[ 19.367218] pcieport 0000:00:1c.5: can't find device of ID00e5
And most worryingly:
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: firmware crashed! (guid a62c787e-4709-4d94-a1a7-4e9357c2555a)
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to get memcpy hi address for firmware address 4: -16
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to read firmware dump area: -16
(This one happens roughly 50% of the time on boot)
All of these started appearing in a fairly short time (~2 weeks) And since all of them could be caused by a hardware failure, I am most worried, is there a software way to test all or most of the hardware?
(Apart from the firmware crash, which causes the wifi to stop working, I did not see any impact of the previous errors)
hardware
Could be the new kernel you have has issues with the old firmware you've installed. How did you install the firmware?
â Fabby
2 mins ago
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've seen some worrying messages in dmesg lately.
Specifically bunch of:
[ 19.367114] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 19.367148] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000081/00002000
[ 19.367172] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 19.367192] pcieport 0000:00:1c.5: [ 7] Bad DLLP
And:
[ 20.121489] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
[ 20.124485] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
Or:
[ 19.367213] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
[ 19.367218] pcieport 0000:00:1c.5: can't find device of ID00e5
And most worryingly:
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: firmware crashed! (guid a62c787e-4709-4d94-a1a7-4e9357c2555a)
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to get memcpy hi address for firmware address 4: -16
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to read firmware dump area: -16
(This one happens roughly 50% of the time on boot)
All of these started appearing in a fairly short time (~2 weeks) And since all of them could be caused by a hardware failure, I am most worried, is there a software way to test all or most of the hardware?
(Apart from the firmware crash, which causes the wifi to stop working, I did not see any impact of the previous errors)
hardware
I've seen some worrying messages in dmesg lately.
Specifically bunch of:
[ 19.367114] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 19.367148] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000081/00002000
[ 19.367172] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
[ 19.367192] pcieport 0000:00:1c.5: [ 7] Bad DLLP
And:
[ 20.121489] ath10k_pci 0000:03:00.0: Unknown eventid: 118809
[ 20.124485] ath10k_pci 0000:03:00.0: Unknown eventid: 90118
Or:
[ 19.367213] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: 0000:00:1c.5
[ 19.367218] pcieport 0000:00:1c.5: can't find device of ID00e5
And most worryingly:
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: firmware crashed! (guid a62c787e-4709-4d94-a1a7-4e9357c2555a)
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to get memcpy hi address for firmware address 4: -16
Nov 06 19:03:16 3c86-notebook kernel: ath10k_pci 0000:03:00.0: failed to read firmware dump area: -16
(This one happens roughly 50% of the time on boot)
All of these started appearing in a fairly short time (~2 weeks) And since all of them could be caused by a hardware failure, I am most worried, is there a software way to test all or most of the hardware?
(Apart from the firmware crash, which causes the wifi to stop working, I did not see any impact of the previous errors)
hardware
hardware
asked 6 mins ago
Meowxiik
61
61
Could be the new kernel you have has issues with the old firmware you've installed. How did you install the firmware?
â Fabby
2 mins ago
add a comment |Â
Could be the new kernel you have has issues with the old firmware you've installed. How did you install the firmware?
â Fabby
2 mins ago
Could be the new kernel you have has issues with the old firmware you've installed. How did you install the firmware?
â Fabby
2 mins ago
Could be the new kernel you have has issues with the old firmware you've installed. How did you install the firmware?
â Fabby
2 mins ago
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f480196%2fhow-to-check-for-hardware-faults%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
Could be the new kernel you have has issues with the old firmware you've installed. How did you install the firmware?
â Fabby
2 mins ago