Control: tags -1 + moreinfo On Mon, Jul 26, 2021 at 02:35:55AM -0500, nelson g wrote: > Package: linux-image-amd64 > Version: 5.10.46-2 > Severity: normal > X-Debbugs-Cc: ledu...@hotmail.com > > Hello, > > My system is stuck with HPET clocksource > > dmesg | egrep -i 'tsc|hpet|clocksource' > [ 0.000000] tsc: Fast TSC calibration using PIT > [ 0.000000] tsc: Detected 2096.096 MHz processor > [ 0.004968] ACPI: HPET 0x00000000B90A3000 000038 (v01 LENOVO TP-R11 > 00001210 PTEC 00000002) > [ 0.005018] ACPI: Reserving HPET table memory at [mem > 0xb90a3000-0xb90a3037] > [ 0.014115] ACPI: HPET id: 0x43538210 base: 0xfed00000 > [ 0.014183] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: > 0xffffffff, max_idle_ns: 7645519600211568 ns > [ 0.059588] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, > max_idle_ns: 133484873504 ns > [ 0.079620] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: > 0x1e36c89f085, max_idle_ns: 440795235573 ns > [ 0.199622] TSC synchronization [CPU#0 -> CPU#1]: > [ 0.199622] Measured 5479288407 cycles TSC warp between CPUs, turning off > TSC clock. > [ 0.199622] tsc: Marking TSC unstable due to check_tsc_sync_source failed > [ 0.216551] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, > max_idle_ns: 7645041785100000 ns > [ 0.373390] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 > [ 0.373393] hpet0: 3 comparators, 32-bit 14.318180 MHz counter > [ 0.375642] clocksource: Switched to clocksource hpet > [ 0.392540] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, > max_idle_ns: 2085701024 ns > [ 1.137978] rtc_cmos 00:01: alarms up to one month, y3k, 114 bytes nvram, > hpet irqs > > > Sorry to bother but I'd like to report to debian this known bug in > bugzilla.kernel = https://bugzilla.kernel.org/show_bug.cgi?id=202525 and > Lenovo > = https://forums.lenovo.com/t5/Other-Linux-Discussions/Clocksource-falling- > back-to-HPET-bec-TSC-is-unstable-ThinkPad-E14-Gen-2-maybe-others/m-p/5036464
If I did follow correctly the bugzilla entry then this is actually something which needs to be fixed in firmware. So I would tend to close this one again. Regards, Salvatore
