Opened 34 hours ago

Last modified 26 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)

IMG_7076.jpeg (3.5 MB ) - added by pokeypkk 30 hours ago.
IMG_7080.jpeg (4.5 MB ) - added by pokeypkk 30 hours ago.
HaikuCrash.jpeg (2.0 MB ) - added by pokeypkk 27 hours ago.
syslog.txt (500.5 KB ) - added by pokeypkk 27 hours ago.

Change History (12)

comment:1 by waddlesplash, 34 hours ago

Component: System/KernelDrivers/Power
Milestone: R1/beta6Unscheduled

Please attach a picture of the crash.

by pokeypkk, 30 hours ago

Attachment: IMG_7076.jpeg added

by pokeypkk, 30 hours ago

Attachment: IMG_7080.jpeg added

comment:2 by pokeypkk, 30 hours ago

Related information has already been added.

comment:3 by waddlesplash, 30 hours 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?

in reply to:  3 comment:4 by pokeypkk, 28 hours 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 waddlesplash, 28 hours ago

None of those are related here.

Please attach a screenshot of the hard crash at the desktop without paging.

by pokeypkk, 27 hours ago

Attachment: HaikuCrash.jpeg added

by pokeypkk, 27 hours ago

Attachment: syslog.txt added

comment:6 by pokeypkk, 27 hours 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:7 by waddlesplash, 27 hours ago

Ah, so it's just that the system hangs entirely, OK.

comment:8 by pokeypkk, 26 hours ago

Correct, and on the next boot I disabled cpuidle the system no longer hangs. This happens on some machines including MSI laptops.

Last edited 26 hours ago by pokeypkk (previous) (diff)
Note: See TracTickets for help on using tickets.