Bug#991509: marked as done (linux-image-amd64: marking TSC unstable due to check_tsc_sync_source failed (AMD Ryzen))
Your message dated Mon, 26 Jul 2021 21:07:49 +0200
with message-id <YP8IBb/G3s9Ar9YU@eldamar.lan>
and subject line Re: Bug#991509: linux-image-amd64: marking TSC unstable due to check_tsc_sync_source failed (AMD Ryzen)
has caused the Debian Bug report #991509,
regarding linux-image-amd64: marking TSC unstable due to check_tsc_sync_source failed (AMD Ryzen)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
991509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991509
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.10.46-2
Severity: normal
X-Debbugs-Cc: ledufff@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
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8),
LANGUAGE=es_CO:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-amd64 depends on:
ii linux-image-5.10.0-8-amd64 5.10.46-2
linux-image-amd64 recommends no packages.
linux-image-amd64 suggests no packages.
--- End Message ---
--- Begin Message ---
hi,
On Mon, Jul 26, 2021 at 01:12:47PM +0200, Salvatore Bonaccorso wrote:
> 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: ledufff@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.
As confirmed offlist, going ahead now with the closure. Thanks for the
turnaround.
Regards,
Salvatore
--- End Message ---
Reply to: