Selfhosted@lemmy.world•Proxmox Crashbymlfh@lm.mlfh.orgEnglish5 daysNot a disk issue, but looks instead like an issue with power management on that thunderbolt root port at 0000:80:1b.4. See this thread for proxmox-specific writeup: https://forum.proxmox.com/threads/kernel-7-0-x-regression-acs-violation-on-pcie-port-80-1b-4-causes-vm-freeze-—-arrow-lake-thunderbolt-5-intel-arc-b50-passthrough.184312/ And here for more: https://github.com/minisforum-docs/MS-02-Ultra/issues/10 Looks like you can resolve it for now by either reverting to 6.17.x kernel or creating a udev rule for the device. 30
Linux@lemmy.ml•Patch daybymlfh@lm.mlfh.orgEnglish15 daysNo, most of these existed pre-AI, and are just being discovered in large volumes by AI. 1
Not a disk issue, but looks instead like an issue with power management on that thunderbolt root port at 0000:80:1b.4. See this thread for proxmox-specific writeup: https://forum.proxmox.com/threads/kernel-7-0-x-regression-acs-violation-on-pcie-port-80-1b-4-causes-vm-freeze-—-arrow-lake-thunderbolt-5-intel-arc-b50-passthrough.184312/
And here for more: https://github.com/minisforum-docs/MS-02-Ultra/issues/10
Looks like you can resolve it for now by either reverting to 6.17.x kernel or creating a udev rule for the device.