https://bugzilla.suse.com/show_bug.cgi?id=1224820 Bug ID: 1224820 Summary: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: aaron.w2@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- I recently assembled a computer based on the ASUS WRX90E Sage motherboard and a 32-core AMD Threadripper PRO CPU. In the BIOS, I enabled 64-bit PCIe remapping support to allow the OS to remap devices to 64-bit address space. For some odd reason, however, the system went into standby and could not recover. Pressing Control+Alt+F10 reported problems remapping the PCIe devices, and then there was a failure with BTRFS reading bad data, and the system hung. The NVME drive is an old Intel PCIe card I had lying around that only had light usage. I strongly suspect there are compatibility issues with the new motherboard chipset since it is pretty new. The WRX90 chipset is only used in two motherboards I am aware of, the ASUS board and an ASRock board. I could not capture the messages directly since the FS went read-only and it started spewing a ton of BTRFS errors before I could capture the screen. As for why it went into suspend mode to begin with, I have no idea. The reason I know it did is I sshed into the box remotely and got a broadcast message: Broadcast message from aaronw@localhost (Tue 2024-05-21 14:09:53 PDT): The system will suspend now! I will try disabling S4/S5 support in the BIOS and see if that helps and I can also try disabling the 64-bit PCIe remapping as well. System specs: ASUS Pro WRX90E Sage SE EEB motherboard with latest BIOS firmware AMD Threadripper Pro 7975WX CPU Gigabyte Ge-Force RTX4090 Windforce V2 24G graphics card Intel NVME drive Kingston Fury Renegade Pro 128GB ECC Registered DDR5 (PC5 48000) memory. -- You are receiving this mail because: You are on the CC list for the bug.