https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118373
Bug ID: 118373
Summary: gcc-14.2 kernel panic on alderlake cpus
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: lancethepants at gmail dot com
Target Milestone: ---
I'm the maintainer of linux firewall distro (Tomato64) and I've recently
received several reports of what appears to be kernel panics on alderlake cpus.
After several weeks of troubleshooting I've narrowed it down to when our
toolchain was updated from gcc-14.1 to gcc-14.2.
When I go to our latest build, which has the alderlake issue and revert
gcc-14.2 to gcc-14.1 (and also binutils 2.43.1 to 2.42, although I don't think
is relevant), the kernel panics go away. Similarly when I go to our last known
good build that does not have the alderlake issue, and I make the singular
change from gcc-14.1 to gcc-14.2, the kernel panics show up.
We have experienced this issue over a range of kernel from 6.10.x, 6.11.x and
6.12.x. All the kernels we've run since the upgrade to gcc-14.2.
Kernel panics have been reported on the following alderlake cpus
n100
n305
Kernel panics do not appear on these reported cpus, including some 11th gen
ones.
Intel 11th Gen N5105
Intel I3-1115G4
Intel Celeron 3215U
Intel Celeron J6412
Intel i7-7550U
Intel i5-2400
The issue does not appear when running the firewall distro in Proxmox on an
alderlake device, only when running bare metal.
Also on one aarch64 device I support we do not see this issue.
We carry only a few kernel patches found here.
https://github.com/tomato64/tomato64/tree/master/tomato64/board/x86_64/linux-patches
And the kernel config here if relevant
https://github.com/tomato64/tomato64/blob/master/tomato64/board/x86_64/linux.config
Sorry not a very technical report, but I wanted to see if there's already known
issues with this combination.
