Bug 217386
Summary: | intel_powerclamp null pointer dereference in Linux 6.3.x | ||
---|---|---|---|
Product: | Power Management | Reporter: | Risto A. Paju (teknohog) |
Component: | Other | Assignee: | Rafael J. Wysocki (rjw) |
Status: | NEW --- | ||
Severity: | normal | CC: | srinivas.pandruvada |
Priority: | P3 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | Subsystem: | ||
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg-6.3.1
dmesg-6.3.1 on an i5-7300HQ Patch to fix |
The affected CPU is an i3-2310M. I tested the same on a newer Intel laptop with an i5-7300HQ, and there's no sign of the bug there. Created attachment 304202 [details]
dmesg-6.3.1 on an i5-7300HQ
Well, I managed to trigger the bug on an i5-7300HQ too.
Created attachment 304209 [details]
Patch to fix
Thanks for reporting. Please try the attached.
I can reproduce and this patch fixed. Please try.
(In reply to Srinivas Pandruvada from comment #3) > Created attachment 304209 [details] > Patch to fix > > Thanks for reporting. Please try the attached. > I can reproduce and this patch fixed. Please try. Tested on both machines, the patch fixes it in both cases. Thank you! Thanks. Submitted patch with Tested by tag. |
Created attachment 304199 [details] dmesg-6.3.1 I use intel_powerclamp on a Thinkpad X220i via a custom script for thermal management, and it triggers a kernel bug in Linux 6.3.0 and 6.3.1. The script has a part awk something > /sys/class/thermal/cooling_device4/cur_state and the awk process hangs, with the null pointer bug reported in dmesg. The script has worked fine for years, and for now I've switched back to the 6.2 series for this laptop.