Bug#1103397: linux-image-amd64: Kernel Panic: copy_fpstate_to_sigframe crashes.
- To: Larry Wei <larryw3i@yeah.net>, 1103397@bugs.debian.org
- Cc: Ben Hutchings <ben@decadent.org.uk>, TonyWWang-oc@zhaoxin.com, "Chang S. Bae" <chang.seok.bae@intel.com>, Lyle Li <LyleLi@zhaoxin.com>, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, aruna.ramakrishna@oracle.com, pbonzini@redhat.com, levymitchell0@gmail.com, attofari@amazon.de, linux-kernel@vger.kernel.org, CobeChen@zhaoxin.com, TimGuo@zhaoxin.com, LeoLiu-oc@zhaoxin.com
- Subject: Bug#1103397: linux-image-amd64: Kernel Panic: copy_fpstate_to_sigframe crashes.
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Thu, 8 May 2025 22:15:45 +0200
- Message-id: <[🔎] aB0Q8S47iNeD1GOM@eldamar.lan>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 1103397@bugs.debian.org
- In-reply-to: <[🔎] 8bcebb19-17f6-47e6-976a-0c9560795cd7@yeah.net>
- References: <4ac9f677-699e-4ef1-b160-9f1c6fe8e820@yeah.net> <c566339b-d8d3-4f74-a3b8-8f373fbe3f47@yeah.net> <174486226753.86424.3234605951040281675.reportbug@zx2> <[🔎] 8bcebb19-17f6-47e6-976a-0c9560795cd7@yeah.net> <174486226753.86424.3234605951040281675.reportbug@zx2>
Hi Larry Wei, hi Ben,
For context this is about https://bugs.debian.org/1103397, and which
Ben did forward in
https://lore.kernel.org/regressions/dddb6b8d56e3f28b914e1e243f948457d53149ce.camel@decadent.org.uk/T/
On Thu, May 08, 2025 at 03:12:31AM +0800, Larry Wei wrote:
> Thank you all,
>
> I have pulled the newest `linux-next` changes and compiled it, my laptop
> boots well now! https://linux-hardware.org/?probe=271fabb7a4 , but it still
> prints some `WARNING` information at startup:
> https://linux-hardware.org/?probe=271fabb7a4&log=dmesg . May this output is
> useful for you maintainers.
>
> And, thank you all again.
Going thorough the bugs I notice there was a related upstream
discussion/patch relating to ae6012d72fa6 ("x86/pkeys: Ensure updated
PKRU value is XRSTOR'd") in the following:
https://lore.kernel.org/all/20250102075419.2559-1-TonyWWang-oc@zhaoxin.com/
There were some followups, but discussion ended on 18.01.2025.
Did this felt through the cracks?
Regards,
Salvatore
Reply to: