(SOLVED) Constant error loop

[sojkovec]

Greetings,

since updating to kernel 5.15.62 there is constant loop of this error in /var/log/messages:

Code: Select all

Aug 27 11:20:40 sojkovec-pc kernel: [  109.260774] [drm] PCI error: detected callback, state(1)!!
Aug 27 11:20:40 sojkovec-pc kernel: [  109.260796] snd_hda_intel 0000:0b:00.1: AER: can't recover (no error_detected callback)
Aug 27 11:20:40 sojkovec-pc kernel: [  109.260803] pcieport 0000:0a:00.0: AER: device recovery failed
Aug 27 11:20:40 sojkovec-pc kernel: [  109.271603] pcieport 0000:00:03.1: AER: Multiple Uncorrected (Non-Fatal) error received: 0000:0a:00.0
Aug 27 11:20:40 sojkovec-pc kernel: [  109.271714] pcieport 0000:0a:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Aug 27 11:20:40 sojkovec-pc kernel: [  109.271720] pcieport 0000:0a:00.0:   device [1002:1479] error status/mask=00100000/00000000
Aug 27 11:20:40 sojkovec-pc kernel: [  109.271726] pcieport 0000:0a:00.0:    [20] UnsupReq               (First)
Aug 27 11:20:40 sojkovec-pc kernel: [  109.271732] pcieport 0000:0a:00.0: AER:   TLP Header: 34000000 0b000010 00000000 84288428


This will eventually eat all free space in system partition (log file size grows quickly), preventing system from booting. So far I fell back to older kernel version. Is this a bug?

Thanks.

[morgano]

Thank you for telling.

Please issue a bug at https://bugs.mageia.org/ and we will address it ASAP
If this is your first time, consult https://wiki.mageia.org/en/How_to_report_a_bug_properly

Or ask back here if you need other help

[morgano]

I issued https://bugs.mageia.org/show_bug.cgi?id=30779 for this.

[davidwhodgins]

My searching on the error indicates it's hardware problem. The kernel update
just made it get reported instead of silently ignored.
From https://forums.unraid.net/topic/103901- ... us-errors/
Try adding "pcie_aspm=off" (without the quotes) to the kernel boot parameter.
https://wiki.mageia.org/en/How_to_set_up_kernel_options

[sojkovec]

Thank you. Adding the boot parameter has fixed it for me since I do not experience an actual hw problem.