https://bugzilla.suse.com/show_bug.cgi?id=1187329 https://bugzilla.suse.com/show_bug.cgi?id=1187329#c6 Lee Duncan <lduncan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(dave@redmoor.org. | |uk) --- Comment #6 from Lee Duncan <lduncan@suse.com> --- Even with the panic output, I have no idea what the issue is. I looked over the pm80* patches I added for SLE-15-SP3, and none of the 32 commits looks suspect, on the surface. Can you try passing in the "logging_level" parameter to pm80xx? I believe it's something like "pm80xx.logging_level=4095" on the boot command line. I _think_ this will work, because it seems like you are already accessing the disc by the time this panic occurs, and the panic is in the pm80xx module. Lastly, I'm not clear on which version of Leap worked and which one didn't. I am checking on SLES 15.3 (same kernel), and it has 5.3.18-57-default. You said that "5.3.18-lp152.75" worked? Where did that version come from? -- You are receiving this mail because: You are on the CC list for the bug.