Bug 2282969
| Summary: | oops: Toggling turboboost 2times crashes ELN kernel | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Samuel Dobroň <sdobron> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, josef, kernel-maint, linville, masami256, mchehab, ptalbert, steved |
| Target Milestone: | --- | Keywords: | Regression, TestBlocker |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Samuel Dobroň
2024-05-23 12:34:01 UTC
Thanks Jan, I missed this. The same traceback is present in my reproducing jobs as well, i just manually double-checked it and your guess is right; After disabling turboboost for the first time, there is a following traceback (same as Jan's): $ echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo [ 754.950459] unchecked MSR access error: RDMSR from 0x771 at rIP: 0xffffffffa6ae6bf5 ) [ 754.960452] Call Trace: [ 754.962905] <TASK> [ 754.965012] ? show_trace_log_lvl+0x1b0/0x2f0 [ 754.969370] ? show_trace_log_lvl+0x1b0/0x2f0 [ 754.973730] ? __flush_smp_call_function_queue+0x95/0x400 [ 754.979130] ? ex_handler_msr.isra.0.cold+0x28/0x60 [ 754.984008] ? fixup_exception+0x157/0x380 [ 754.988109] ? gp_try_fixup_and_notify+0x1e/0xb0 [ 754.992727] ? exc_general_protection+0xff/0x410 [ 754.997347] ? asm_exc_general_protection+0x26/0x30 [ 755.002226] ? __pfx___rdmsr_on_cpu+0x10/0x10 [ 755.006587] ? __rdmsr_on_cpu+0x25/0x60 [ 755.010424] __flush_smp_call_function_queue+0x95/0x400 [ 755.015652] flush_smp_call_function_queue+0x2b/0x60 [ 755.020617] do_idle+0x9c/0xd0 [ 755.023678] cpu_startup_entry+0x29/0x30 [ 755.027604] rest_init+0xcc/0xd0 [ 755.030837] start_kernel+0x41f/0x420 [ 755.034503] x86_64_start_reservations+0x24/0x30 [ 755.039121] x86_64_start_kernel+0x97/0xa0 [ 755.043221] common_startup_64+0x13e/0x141 [ 755.047319] </TASK> But kernel doesn't panic, enabling TB doesn't throw anything: $ echo 0 > /sys/devices/system/cpu/intel_pstate/no_turbo And disabling it for 2nd time crashes the kernel with the traceback from issue description. Seems to be fixed since kernel-6.10.0-0.rc2.20240606git2df0193e62cf.27.eln137 (https://koji.fedoraproject.org/koji/taskinfo?taskID=118651345) This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. NOTE: This is an automated mass update. |