September 23, 20232 yr I am seeing the following error. What could be causing it? Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 514 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: It has been corrected by h/w and requires no further action Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: event severity: corrected Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: Error 0, type: corrected Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: section_type: PCIe error Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: port_type: 0, PCIe end point Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: version: 0.2 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: command: 0x0406, status: 0x0010 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: device_id: 0000:62:00.0 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: slot: 0 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: secondary_bus: 0x00 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: vendor_id: 0x144d, device_id: 0xa80a Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: class_code: 010802 Sep 23 14:18:28 HuskyServer kernel: {9}[Hardware Error]: bridge: secondary_status: 0x0000, control: 0x0000 Sep 23 14:18:28 HuskyServer kernel: nvme 0000:62:00.0: AER: aer_status: 0x00000001, aer_mask: 0x00000000 Sep 23 14:18:28 HuskyServer kernel: nvme 0000:62:00.0: [ 0] RxErr (First) Sep 23 14:18:28 HuskyServer kernel: nvme 0000:62:00.0: AER: aer_layer=Physical Layer, aer_agent=Receiver ID Edited September 23, 20232 yr by almulder
September 23, 20232 yr Author 10 minutes ago, Mainfrezzer said: Your asus hyper m.2 card most likely. Is it something I need to worry about? I have 2 installed and using the NVMEs in them. (is there a fix)
September 23, 20232 yr You probably would have to run "pcie_aspm=off" in your syslinux config to get rid of it. Its Asus ive lost faith at this point.
September 23, 20232 yr Author 3 minutes ago, Mainfrezzer said: You probably would have to run "pcie_aspm=off" in your syslinux config to get rid of it. Its Asus ive lost faith at this point. I have made the change and will reboot later once mover finishes. (in a few hours). Thanks for the help.
September 23, 20232 yr mhmm thats unfortunate. overall i would say its save to ignore ("It has been corrected by h/w and requires no further action") But i did find this post on level1tech with a "hacky way", in the bottom of the comment chain, to disabling the logging for that issue https://forum.level1techs.com/t/asus-pro-ws-wrx80e-sage-dmesg-is-full-of-corrected-pcie-and-or-aer-errors/178004 i would just leave it as is, as long its just throwing a fuzz from time to time in the logs. Edited September 23, 20232 yr by Mainfrezzer
September 23, 20232 yr Author 23 minutes ago, Mainfrezzer said: mhmm thats unfortunate. overall i would say its save to ignore ("It has been corrected by h/w and requires no further action") But i did find this post on level1tech with a "hacky way", in the bottom of the comment chain, to disabling the logging for that issue https://forum.level1techs.com/t/asus-pro-ws-wrx80e-sage-dmesg-is-full-of-corrected-pcie-and-or-aer-errors/178004 i would just leave it as is, as long its just throwing a fuzz from time to time in the logs. ya I did notice I missed the e, so I guess I deleted my post as you repiled, but I did fix that and issue still there. Guess I will leave as is until I notice an issue. (did notice a bit of a speed increase when booting when i updated it) For reference to others this is what my line looks like now. label Unraid OS GUI Mode menu default kernel /bzimage append pci=realloc=off pcie_aspm=off isolcpus=18-31,50-63 initrd=/bzroot,/bzroot-gui Edited September 23, 20232 yr by almulder
September 23, 20232 yr Author 35 minutes ago, Mainfrezzer said: But i did find this post on level1tech with a "hacky way", in the bottom of the comment chain, to disabling the logging for that issue https://forum.level1techs.com/t/asus-pro-ws-wrx80e-sage-dmesg-is-full-of-corrected-pcie-and-or-aer-errors/178004 Thanks for that link. I think I have tracked down my issue to my 980 Pro NVME. Its the only one throwing the error. All my other NVMEs in my cards are 990 Pros 2TB (Except for a 980 pro 1TB) IOMMU group 13: [144d:a80a] 62:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO [N:0:6:1] disk Samsung SSD 980 PRO 2TB__1 /dev/nvme0n1 2.00TB Seems other have the same issue if they are not the 990 Pros. I have ordered a replacement 990 (I can use the 980 elsewhere) And I believe this will solve my issue. (Hopefully). Thanks again so much for helping. (Google was not my friend this time, did not think to search for my motherboard as the issue / card)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.