error after new motherboard install

[Lou]

just swapped out my board for evga z170 classified with 1151 i7 cpu and 16 gig of quad channel ram. I now am getting this error in my sys log.

 

Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: [ 7] Bad DLLP Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6 Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: device [8086:a116] error status/mask=00000001/00002000 Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: [ 0] Receiver Error (First) Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6 Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: device [8086:a116] error status/mask=00000001/00002000 Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: [ 0] Receiver Error (First) Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6 Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) Oct 31 19:30:06 Unraid kernel: pcieport 0000:00:1c.6: device [8086:a116] error status/mask=00000080/00002000

any idea or help on this one

thanks

Lou

unraid-diagnostics-20181031-1940.zip

Edited November 1, 2018 by Lou
attched log file

[trurl]

Are you experiencing any actual symptoms related to this?

 

You should always go to Tools - Diagnostics and post the complete zip.

[Lou]

12 minutes ago, trurl said:

Are you experiencing any actual symptoms related to this?

 

You should always go to Tools - Diagnostics and post the complete zip.

 

sorry it now attached should i shut down the server in the meantime?

Lou

Edited November 1, 2018 by Lou

[Lou]

Its filling my log file full ,then a full memory error in the syslog and nothing else is logged until i reboot. I just attached my diagnostics zip file.

I had no error with the other board only when I did the change over. 

[JorgeB]

That's usually caused by an addon PCI card, most likely a disk controller, switching slots might fix it, especially switching from a CPU to a PCH slot or vice versa, also look for a bios update.

 

If that doesn't work try these options:

 

[Lou]

3 hours ago, johnnie.black said:

That's usually caused by an addon PCI card, most likely a disk controller, switching slots might fix it, especially switching from a CPU to a PCH slot or vice versa, also look for a bios update.

 

If that doesn't work try these options:

 

Thank you for the reply. Do you think replacing the pci card I have (Marvell) with a different type of cards possibly LSI, would possibly resolve this problem? for now I shut of the VM to see how it reacts but I would like to have the VM option for future. does using pcie_aspm=off have any operation effects or is this masking the error and it still going on in the background. I will try all other option in the attached post above but at this point not sure what is the best route moving forward is. should I look at a different motherboard ?

Thanks again for the input.

Lou

[JorgeB]

3 minutes ago, Lou said:

Do you think replacing the pci card I have (Marvell) with a different type of cards possibly LSI, would possibly resolve this problem?

If the SASLP is the culprit yes, both to get rid of the errors and because those controllers have known issues.

 

I never researched what using the other options does exactly, you'll need to google it, but I believe solving the problem a different way and not having to use them would always be best

 

 

[Lou]

So it seems that disabling VM solved the problem for now no more error messages flooding the syslog for the last 6 hours. I'll have to move the cards around into different slots to see if that helps and purchase some LSI cards I do want to have the VM option for future. Forgot to mention the bios is up to date.

Thanks

Lou

Edited November 1, 2018 by Lou