Based on the logs provided, the primary difference causing the failure in the "bad boot" is related to the Time Stamp Counter (TSC) being marked as unstable, which is triggered by the laptop lid being closed during boot.
Here is the comparison and explanation:
1. Comparison of the Two Boots
Good Boot (Lid Open):
The system initializes the TSC (Time Stamp Counter) clock source correctly (clocksource: Switched to clocksource tsc).
The boot proceeds normally, and the graphical session starts without interruptions.
Bad Boot (Lid Closed):
Early in the boot (around timestamp 05:00:01), the kernel detects that the TSC is unreliable.
Log Message: clocksource: timekeeping watchdog on CPU7: Marking clocksource 'tsc' as unstable because the skew is too large.
Consequence: The system forces a switch to HPET (clocksource: Switched to clocksource hpet), which is a much older and slower timing method.
Result: This timing mismatch causes critical background services like Handheld Daemon (hhd) and the graphical session (Gamescope) to crash or hang. Specifically, hhd-ui crashes with a core dump, and the user session times out trying to reload, leading to the loop you see.
Based on the logs provided, the primary difference causing the failure in the "bad boot" is related to the Time Stamp Counter (TSC) being marked as unstable, which is triggered by the laptop lid being closed during boot.
Here is the comparison and explanation:
1. Comparison of the Two Boots
Good Boot (Lid Open):
The system initializes the TSC (Time Stamp Counter) clock source correctly (clocksource: Switched to clocksource tsc).
The boot proceeds normally, and the graphical session starts without interruptions.
Bad Boot (Lid Closed):
Early in the boot (around timestamp 05:00:01), the kernel detects that the TSC is unreliable.
Log Message: clocksource: timekeeping watchdog on CPU7: Marking clocksource 'tsc' as unstable because the skew is too large.
Consequence: The system forces a switch to HPET (clocksource: Switched to clocksource hpet), which is a much older and slower timing method.
Result: This timing mismatch causes critical background services like Handheld Daemon (hhd) and the graphical session (Gamescope) to crash or hang. Specifically, hhd-ui crashes with a core dump, and the user session times out trying to reload, leading to the loop you see.