Bugzilla – Bug 1213360
DPC RP PIO Log size 0 is Invalid
Last modified: 2023-07-26 06:12:00 UTC
Snapshot 20230714 with Kernel 6.4.2-1 makes my system unbootable with the error: DPC RP PIO Log size 0 is invalid Current fix is to use kernel 6.3.9 at boot. The error is there too but the system boots. It may be related to https://bugzilla.kernel.org/show_bug.cgi?id=209943 Operating System: openSUSE Tumbleweed 20230714 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-1-default (64-bit) Graphics Platform: X11 Processors: 16 × 13th Gen Intel® Core™ i7-1360P Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (13th Gen Intel Core) System Version: A6
Could you give the hardware details? e.g. the output of hwinfo on 6.3.9 kernel, as well as dmesg output.
Created attachment 868289 [details] hwinfo output 20230718 hwinfo piped into a text file
Created attachment 868290 [details] dmesg output 20230718 dmesg piped into text file
You already see the same error "DPC RP PIO Log Size 0 is invalid" in 6.3.x log. So the message itself might be a red herring, and the actual breakage could be something else. I'd try to disable the native graphics at first, e.g. pass nomodeset boot option.
Passing the command "nomodeset" had no affect. It still halted after the aforementioned error. I have locked my kernel package to prevent losing the 6.3 kernel, currently. Is there any other information I can provide or things I can test?
You are correct that it was a red herring. I will call this solved. I disabled the TMP module and now I am good to go. Thank you for helping me to investigate further! I have no interest in TPM anything, so nothing lost.
OK, thank you for the information update!
Just for context, here is the conversation happening on the Framework forum. https://community.frame.work/t/tracking-kernel-6-4-hang-at-boot-tpm-bug-confirmed/32956/10
OK, it seems that the upstream fixes have been backported to 6.4.5. https://bugzilla.kernel.org/show_bug.cgi?id=217631