From: Salvatore Bonaccorso <carnil@debian.org>
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: Re: Bug#1103397: linux-image-amd64: Kernel Panic: copy_fpstate_to_sigframe crashes.
Date: Thu, 8 May 2025 22:15:45 +0200 [thread overview]
Message-ID: <aB0Q8S47iNeD1GOM@eldamar.lan> (raw)
In-Reply-To: <8bcebb19-17f6-47e6-976a-0c9560795cd7@yeah.net>
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
next prev parent reply other threads:[~2025-05-08 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ac9f677-699e-4ef1-b160-9f1c6fe8e820@yeah.net>
[not found] ` <c566339b-d8d3-4f74-a3b8-8f373fbe3f47@yeah.net>
2025-04-25 3:45 ` linux-image-amd64: Kernel Panic: copy_fpstate_to_sigfrane crashes Ben Hutchings
[not found] ` <174486226753.86424.3234605951040281675.reportbug@zx2>
[not found] ` <8bcebb19-17f6-47e6-976a-0c9560795cd7@yeah.net>
2025-05-08 20:15 ` Salvatore Bonaccorso [this message]
2025-05-09 3:31 ` Bug#1103397: linux-image-amd64: Kernel Panic: copy_fpstate_to_sigframe crashes Larry Wei
2025-05-09 3:49 ` Larry Wei
2025-05-09 8:31 ` Tony W Wang-oc
2025-05-09 9:08 ` Larry Wei
2025-05-09 9:53 ` Tony W Wang-oc
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=aB0Q8S47iNeD1GOM@eldamar.lan \
--to=carnil@debian.org \
--cc=1103397@bugs.debian.org \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=LyleLi@zhaoxin.com \
--cc=TimGuo@zhaoxin.com \
--cc=TonyWWang-oc@zhaoxin.com \
--cc=aruna.ramakrishna@oracle.com \
--cc=attofari@amazon.de \
--cc=ben@decadent.org.uk \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=larryw3i@yeah.net \
--cc=levymitchell0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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.