[Kernel-packages] [Bug 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

2023-05-01 Thread Frederick Zhang
network works fine, but after some use it eventually breaks, and > i see these errors recently in the journal. > Can you try disabling ACPI? [1] Maybe it's somehow related? [1] https://bugzilla.kernel.org/show_bug.cgi?id=216863#c3 -- Frederick Zhang PGP: 8BFB EA5B 4C44 BFAC C8EC 5F93 1F92

[Kernel-packages] [Bug 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

2022-11-18 Thread Frederick Zhang
@Bjorn I backported these patches onto Arch and the warning logs were gone however the NIC issue still persisted. So I did a bisect and the commit that fixed it was [1]. So after applying [1], its parent e7fd8b684, and your patches, now everything is back to normal for me :D [1]

[Kernel-packages] [Bug 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

2022-11-12 Thread Frederick Zhang
@Bjorn I installed v6.1-rc4 and I was glad to find out it fixed my NIC issue :) Even the PXE boot option that mysteriously disappeared after reboots started showing up stably. In terms of the USB drive one, I realised that I'm not always to boot from USB Type-C drives after a shutdown in Windows

[Kernel-packages] [Bug 1990272] Re: PCIe Bus Error: Uncorrected, Transaction Layer, device [8086:51b0], AER UnsupReq

2022-11-10 Thread Frederick Zhang
I'm also experiencing this issue on a ThinkPad X1 Extreme Gen 5, and it actually causes some problems more than just logs being spammed. First of all, I noticed that this only happens after a reboot when I have an external display connected via USB Type-C. The other end can be HDMI 2.0 or