Bug 13142
| Summary: | kernel-panic if the process.max_cstate=0 is added | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | ykzhao (yakui.zhao) |
| Component: | Power-Processor | Assignee: | ykzhao (yakui.zhao) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | acpi-bugzilla, lenb |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.28/2.6.29 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
the kernel-panic log on 2.6.28.3 kernel
[patch]: Add the module param check for processor.max_cstate patch vs 2.6.30-rc3 |
||
|
Description
ykzhao
2009-04-21 03:26:35 UTC
Created attachment 21063 [details]
the kernel-panic log on 2.6.28.3 kernel
If there is no boot option of "processor.max_cstate" or the max_cstate is not zero, the box can be booted correctly. Created attachment 21098 [details]
[patch]: Add the module param check for processor.max_cstate
Add the module param check for the processor.max_cstate.
If the module param is equal to or less than zero, it will be ignored. When it is beyond the threshold, it is also ignored.
thanks.
Created attachment 21099 [details]
patch vs 2.6.30-rc3
i thinkt the previous patch was overkill
because processor.max_cstate can be set only at init-time,
not at run-time. so this 3-liner should be sufficient.
shipping in 2.6.30-rc4 closed. |