cmdthor Posted June 11, 2019 Share Posted June 11, 2019 Hello, require some help understanding why the log fills up, from what i can discern from the diagnostics it is the same error reported endlessly " Tower kernel: pcieport 0000:80:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Tower kernel: pcieport 0000:8tower-diagnostics-20190611-1848.zip0:03.0: device [8086:2f08] error status/mask=00001000/00002000 Tower kernel: pcieport 0000:80:03.0: [12] Timeout Tower kernel: pcieport 0000:80:03.0: AER: Corrected error received: 0000:80:03.0 Tower kernel: pcieport 0000:80:03.0: AER: Multiple Corrected error received: 0000:80:03.0 Tower kernel: pcieport 0000:80:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Tower kernel: pcieport 0000:80:03.0: device [8086:2f08] error status/mask=00001000/00002000 Tower kernel: pcieport 0000:80:03.0: [12] Timeout Tower kernel: pcieport 0000:80:03.0: AER: Corrected error received: 0000:80:03.0 " dev with id: [8086:2f08] is ID IOMMU group 31:[8086:2f08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 (rev 01) PCI Slot 3 (1,2,3...not counting from 0) i have a GTX 1060 assigned to PLEX for transcoding witch tested with passtrough on VM works just fine PCI Slot 4 (1,2,3...not counting from 0) is a ROG GTX 1070 assigned to windows VM for gaming, witch also works just fine worth mentioning is that after a fresh restart i start all containers, all VM-s and everything works without errors i'm attaching the diagnostics, a hint to what might be causing this would be appreciated. TY Quote Link to comment
Frank1940 Posted June 11, 2019 Share Posted June 11, 2019 You might want to try googling this problem (using a portion of the error message like: AER: Multiple Corrected error ) Apparently, it error is coming from something problem with one (or more) of your pcie slots. Quote Link to comment
AgentXXL Posted June 12, 2019 Share Posted June 12, 2019 (edited) I'm noticing a similar problem but my log is showing as full (100%) on the unRAID dashboard. When I go to the System Log page in unRAID (under Tools), all I get is the following error message: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 20 I can't download the log either - it tries but gives me an empty file. I've noticed that I'm seeing lots of performance issues that also may be related - usual tasks are now maxing out my CPU (i7-6700K) on all cores. A reboot didn't help. Should I be re-doing the unRAID USB key to wipe out the corrupted log file? I've backed up the USB key (Flash) from the unRAID interface. Or can I try and locate the log file and delete it via SSH? Suggestions? EDIT: a 2nd reboot seems to have cleared/reset the log back to 1%. Performance is still seeing 100% utilization on a few cores and webGUI for both the main unRAID page and the various Docker containers are all sluggish. Edited June 12, 2019 by AgentXXL Added info re: 2nd reboot Quote Link to comment
Recommended Posts
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.