Package: linux-image-amd64
Version: 6.12.22-1
Severity: important
Dear Maintainer,
After linux-image-6.11.9-amd64, my laptop has never booted from linux-image- amd64 any more. It shows "Kernel panic" after Grub. I took a screenshot for that. I do hope you maintainers can SAVE my laptop.
The Kernel panic print as follow: --------------------------------------------------------------------------------
0.93186510ops: general protection fault, naybe for address 0x0: 0000 [#1] PREEMPT SMP NOPTI
0.9318931 CPU: 1 UID:0 PID:1 Comn: init Not tainted 6.12.22-and64 #1 Debian 6.12.22-1
0.9319151 Harduare nane: GITSIAR GDC-1461/GM-1461,BIOS 03.04 08/03/2023 0.9319321 RIP: 0010:copy_fpstate_to_sigframe+0x1eb/0x3c0
0.9319521 Code: b9 01 00 00 00 of 01 d0 48 c1 e2 20 89 c0 48 01 c2 48 81 ca ff
02 00 00 49 21 d5 e9 f4 fe ff ff 0f 1f 44 00 00 b9 01 00 0 0 <0f> 01 d0 48 c1 e2 20 89 c0 48 8d 8d 00 02 00 00 48 01 d0 4c 21 e8
0.9319911 RSP:0018:ffffa6844002bc28EFLAGS:00010246[...]
0.9320061RAX: 0 RBX: 00000000 RcX: 00000001
Control: tag -1 moreinfo
On Thu, 17 Apr 2025 11:57:47 +0800 root <larryw3i@yeah.net> wrote:
Package: linux-image-amd64We got a #GP exception on an XGETBV instruction, which means "ECX
Version: 6.12.22-1
Severity: important
Dear Maintainer,
After linux-image-6.11.9-amd64, my laptop has never booted from linux-image- >> amd64 any more. It shows "Kernel panic" after Grub. I took a screenshot for >> that. I do hope you maintainers can SAVE my laptop.
The Kernel panic print as follow:
--------------------------------------------------------------------------------
0.93186510ops: general protection fault, naybe for address 0x0: 0000 [#1]
PREEMPT SMP NOPTI
0.9318931 CPU: 1 UID:0 PID:1 Comn: init Not tainted 6.12.22-and64 #1 Debian >> 6.12.22-1
0.9319151 Harduare nane: GITSIAR GDC-1461/GM-1461,BIOS 03.04 08/03/2023
0.9319321 RIP: 0010:copy_fpstate_to_sigframe+0x1eb/0x3c0
0.9319521 Code: b9 01 00 00 00 of 01 d0 48 c1 e2 20 89 c0 48 01 c2 48 81 ca ff
02 00 00 49 21 d5 e9 f4 fe ff ff 0f 1f 44 00 00 b9 01 00 0 0 <0f> 01 d0 48 c1
e2 20 89 c0 48 8d 8d 00 02 00 00 48 01 d0 4c 21 e8
specifies a reserved or unimplemented XCR address". So this instruction
is wrongly being used on a CPU that doesn't support it.
To help confirm this, please can you send the contents of /proc/cpuinfo?
0.9319911 RSP:0018:ffffa6844002bc28EFLAGS:00010246[...]
0.9320061RAX: 0 RBX: 00000000 RcX: 00000001
ECX is 1 (= XCR_XFEATURE_IN_USE_MASK). So this is a use of xfeatures_in_use() inlined into copy_fpstate_to_sigframe().
Since this is a regression after 6.11.9, my guess is that this is caused
by:
commit dd9478d54c738e86692b83cc992dc4fb643bcdbf
Author: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
Date: Tue Nov 19 17:45:20 2024 +0000
x86/pkeys: Ensure updated PKRU value is XRSTOR'd
[ Upstream commit ae6012d72fa60c9ff92de5bac7a8021a47458e5b ]
which went into 6.12.5 and adds a call to xfeatures_in_use() without an obvious CPU feature check. (The added call is not directly in copy_fpstate_to_sigframe() but it's in a function that can be inlined
into it.)
Ben.
Thanks for your replying, the `Probe URL` of my laptop: https://linux-hardware.org/?probe=58facb533d , and `cpuinfo` is:[...]
larry@zx2:~/Downloads$ sudo cat /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 7
model : 59
model name : ZHAOXIN KaiXian KX-6000G/4@3.0GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca[...]
cmov pat pse36 clflush acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl nonstop_tsc
cpuid aperfmperf pni pclmulqdq monitor vmx smx est tm2 ssse3 cx16 xtpr
pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c
rdrand rng rng_en ace ace_en ace2 phe phe_en pmm pmm_en lahf_lm abm 3dnowprefetch ibrs ibpb tpr_shadow ept vpid fsgsbase tsc_adjust bmi1
smep bmi2 invpcid rdseed adx smap sha_ni xsaveopt dtherm hwp
hwp_act_window hwp_epp hwp_pkg_req vnmi umip pku ospke rdpid arch_capabilities
vmx flags : vnmi invvpid ept_x_only ept_1gb tsc_offset vtpr mtf ept vpid unrestricted_guest ple
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 ,
it should not need to wait for
the next release cycle, right?
Looking at what has changed in linux-next, this appears to be the fix:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 482 |
Nodes: | 16 (2 / 14) |
Uptime: | 60:01:17 |
Calls: | 9,567 |
Calls today: | 1 |
Files: | 13,663 |
Messages: | 6,143,311 |