X86 platform drivers
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220224] New: Kernel 6.15 causes crash (general protection fault) due to amd_sfh module
Date: Thu, 12 Jun 2025 20:47:09 +0000	[thread overview]
Message-ID: <bug-220224-215701@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 220224
           Summary: Kernel 6.15 causes crash (general protection fault)
                    due to amd_sfh module
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: blocking
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: g.molinaro@linuxmail.org
        Regression: No

Created attachment 308234
  --> https://bugzilla.kernel.org/attachment.cgi?id=308234&action=edit
dmesg from successful boot (with module blacklisted)

On my MSI Alpha 15 B5EEK laptop (AMD Ryzen 7 5800H), the system fails to boot
on Linux 6.15 due to a general protection fault linked to the amd_sfh (Sensor
Fusion Hub) module.

The error occurs early in the boot process, and results in a kernel panic.
Booting with the amd_sfh module blacklisted resolves the issue. Additionally,
the latest LTS kernel (6.1.x) works fine with the module enabled.

System is running Arch Linux with linux-cachyos kernel 6.15.2-2.

No critical side effects are observed when the module is blacklisted — the
system appears stable and fully functional.

**Reproducible:** Always  
**Workaround:** Blacklist `amd_sfh` and rebuild initramfs


Hardware:

    Laptop: MSI Alpha 15 B5EEK

    CPU: AMD Ryzen 7 5800H with Radeon Graphics

    BIOS: E158LAMS.10B (05/18/2023)

Steps to Reproduce:

    Boot system with Linux 6.15 kernel

    Observe crash (kernel panic from general protection fault in amd_sfh)

    Boot with amd_sfh blacklisted — issue no longer occurs

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

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

             reply	other threads:[~2025-06-12 20:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 20:47 bugzilla-daemon [this message]
2025-06-12 20:49 ` [Bug 220224] Kernel 6.15 causes crash (general protection fault) due to amd_sfh module 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox