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 15:09:55 +0000 [thread overview]
Message-ID: <bug-220224-215701-efoD5MrOI1@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 #22 from g.molinaro@linuxmail.org ---
Ok, I will work with downstream and forward eventual results here.
My only concern about the BIOS update is about tainting the testing enviroment
for this bug. I will delay it for now, along with other OS updates, at least
until I'm finished testing with downstream. Thanks.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-06-13 15:09 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
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 [this message]
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-efoD5MrOI1@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