All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220224] Kernel 6.15 causes crash (general protection fault) due to amd_sfh module
Date: Fri, 13 Jun 2025 13:00:04 +0000	[thread overview]
Message-ID: <bug-220224-215701-9eBZOA54QI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220224-215701@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=220224

--- Comment #8 from g.molinaro@linuxmail.org ---
Quick update.

Before leaving work for launch, I removed the blacklist file and did
`mkinitcpio -P` before shutting down the laptop. I left it connected to the
power supply and left. Upon coming back, I tried to boot into all the installed
kernels: arch-6.15.2, cachyos-6.15.2 and cachyos-lts-6.12.33. And ALL WORKED,
with the amd_sfh module loaded, without issues. Sadly, I was in a hurry and
forgot to save the logs.

Barring some gremlings, nothing had changed in my system (no updates at least),
so I decided to shutdown the PC and unplug it from the wall in order for the EC
to reset at least partially, then powered it back up multiple times, both on
battery and wall power without blacklisting the module. The results are as
follows:

6.15.2-arch1-1 : now boots up without issues (it didn't before);
6.15.2-cashyos-2 : DOES NOT BOOT
6.13.33-lts-cachyos : boots as always.

So it would seems that the issue is now somehow limited (at least for now), to
the cachyos kernel. I have ho idea how or why aarch is now working while it
wasn't before or how they all worked fine the first time.

This time tho, I have updated logs:

- Output of journalctl -k -b -1 for the failed attempt with the cachyos kernel;
- Output of journalctl -k -b for the successful boot with the arch kernel;
- Output of dmesg for the arch kernel;
- Output of dmesg -S for the arch kernel;
- A New screenshot of the kernel panic message with the 6.15.2-cachyos kernel.

More tests to follow...

---
As a side note, I found out there's a BIOS update available for this laptop (I
stopped looking at the website after a couple of years of silence). I have no
idea what it's about, and I'm holding off installing it for the moment not to
invalidate previous testing... but I'm curious if I should just to see if it
changes something. I'm open to suggestions.
---

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-06-13 13:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 20:47 [Bug 220224] New: Kernel 6.15 causes crash (general protection fault) due to amd_sfh module bugzilla-daemon
2025-06-12 20:49 ` [Bug 220224] " bugzilla-daemon
2025-06-12 20:50 ` bugzilla-daemon
2025-06-12 20:51 ` bugzilla-daemon
2025-06-12 21:14 ` bugzilla-daemon
2025-06-12 21:28 ` bugzilla-daemon
2025-06-13  1:59 ` bugzilla-daemon
2025-06-13 10:40 ` bugzilla-daemon
2025-06-13 13:00 ` bugzilla-daemon [this message]
2025-06-13 13:01 ` bugzilla-daemon
2025-06-13 13:02 ` bugzilla-daemon
2025-06-13 13:03 ` bugzilla-daemon
2025-06-13 13:04 ` bugzilla-daemon
2025-06-13 13:04 ` bugzilla-daemon
2025-06-13 13:36 ` bugzilla-daemon
2025-06-13 14:29 ` bugzilla-daemon
2025-06-13 14:33 ` bugzilla-daemon
2025-06-13 14:34 ` bugzilla-daemon
2025-06-13 14:43 ` bugzilla-daemon
2025-06-13 15:00 ` bugzilla-daemon
2025-06-13 15:03 ` bugzilla-daemon
2025-06-13 15:05 ` bugzilla-daemon
2025-06-13 15:09 ` bugzilla-daemon
2025-06-18 17:32 ` bugzilla-daemon
2025-06-18 17:41 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-220224-215701-9eBZOA54QI@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.