From: Larry Wei <larryw3i@yeah.net>
To: Salvatore Bonaccorso <carnil@debian.org>, 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: Fri, 9 May 2025 11:49:32 +0800 [thread overview]
Message-ID: <6cebe32d-0290-41d8-9629-d80ef3c159c3@yeah.net> (raw)
In-Reply-To: <aB0Q8S47iNeD1GOM@eldamar.lan>
Salvatore Bonaccorso,
Yes, let's just consider it as good. But in fact, there are still many
problems, such as the one mentioned above (
linux-hardware.org/?probe=271fabb7a4&log=dmesg ), and almost all laptops
using Zhaoxin CPUs cannot adjust the backlight brightness, which is
**VERY HARMFUL** to the eyes!
Regards,
larryw3i
On 5/9/25 04:15, Salvatore Bonaccorso wrote:
> Did this felt through the cracks?
next prev parent reply other threads:[~2025-05-09 4:21 UTC|newest]
Thread overview: 6+ 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>
[not found] ` <174486226753.86424.3234605951040281675.reportbug@zx2>
[not found] ` <8bcebb19-17f6-47e6-976a-0c9560795cd7@yeah.net>
2025-05-08 20:15 ` Salvatore Bonaccorso
2025-05-09 3:31 ` Larry Wei
2025-05-09 3:49 ` Larry Wei [this message]
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=6cebe32d-0290-41d8-9629-d80ef3c159c3@yeah.net \
--to=larryw3i@yeah.net \
--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=carnil@debian.org \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®