openSUSE Kernel Bugs

Download

kernel-bugs@lists.opensuse.org

May 2022

1 participants
222 discussions

[Bug 1199052] amd iommu- warning after resume
by bugzilla_noreply＠suse.com 01 May '22

01 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199052 https://bugzilla.suse.com/show_bug.cgi?id=1199052#c1 --- Comment #1 from Klaus Mueller <andihartmann(a)freenet.de> --- Additional info Inspecting the code based on the given line reveals, that the warn is based on this change: https://lore.kernel.org/all/20211123161038.48009-2-mlevitsk@redhat.com/ @@ -825,7 +836,7 @@ static int iommu_ga_log_enable(struct amd_iommu *iommu) break; } - if (i >= LOOP_TIMEOUT) + if (WARN_ON(i >= LOOP_TIMEOUT)) return -EINVAL; #endif /* CONFIG_IRQ_REMAP */ return 0; -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199052] New: amd iommu- warning after resume
by bugzilla_noreply＠suse.com 01 May '22

01 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199052 Bug ID: 1199052 Summary: amd iommu- warning after resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andihartmann(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 858553 --> http://bugzilla.opensuse.org/attachment.cgi?id=858553&action=edit iommu warning and lspci output I'm mainly running Leap 15.3 - but using own built 5.15.x kernel on base of RPM packets from the build service. Since version 5.15.24, I'm seeing the attached warning in messages after resume from s2ram. I couldn't see this warning while using 5.15.16. I directly switched to 5.15.24 ff. I detected massive amd iommu changes in 5.15.17 - that's why I believe those could be the reason. The attached file contains, too, the output of lspci -vvv Don't know if it's relevant, but the kernel is locked down here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Jump to page: