Opened 2 days ago
Last modified 45 hours ago
#19341 new bug
CPUidle module caused some machines to hard crash at boot
Reported by: | pokeypkk | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Power | Version: | R1/beta5 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
When booting R1/beta5 and nightly builds on certain machines the module CPUidle caused some machines to hard crash when the system booted. By turning off the module at the boot menu the system proceeds as normal.
Tested with R1/beta5 and nightly build href58455
Attachments (4)
Change History (12)
comment:1 by , 2 days ago
Component: | System/Kernel → Drivers/Power |
---|---|
Milestone: | R1/beta6 → Unscheduled |
by , 2 days ago
Attachment: | IMG_7076.jpeg added |
---|
by , 2 days ago
Attachment: | IMG_7080.jpeg added |
---|
follow-up: 4 comment:3 by , 2 days ago
These crashes are unrelated to the CPUidle module and are expected when you have "onscreen debug" combined with "onscreen paging" enabled. What happens when booting with onscreen paging disabled?
comment:4 by , 2 days ago
Once onscreen paging was disabled, there is a text boot process and the system still landed on the desktop with a hard crash.
However, during the boot process I've taken a video of the boot process as it did not page the process, and I've noticed a few key things that might be related to the issue:
found cpuidle module: power/cpuidle/intel_cstates/vl.
.
.
.
driver busses/i2c/pch_i2c/device/vl init failed: General system error
api_als: api_als_init driver device disabled
driver drivers/sensor/acpi_als/driver vl init failed: General system error
comment:5 by , 2 days ago
None of those are related here.
Please attach a screenshot of the hard crash at the desktop without paging.
by , 2 days ago
Attachment: | HaikuCrash.jpeg added |
---|
by , 2 days ago
Attachment: | syslog.txt added |
---|
comment:6 by , 2 days ago
I have attached the desktop screenshot as well as the full syslog file for your information.
Note that the desktop looks normal with no verbose output following the boot process, however I could not do anything with internal and external input devices, and the clock does not update.
comment:8 by , 45 hours ago
Correct, and on the next boot I disabled cpuidle the system no longer hangs
Please attach a picture of the crash.