linux-kernel - Re: tsc: Fast TSC calibration failed with AMD B350M/Ryzen 3 2200G

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5656446a-eaef-aa94-8766-49fec24257c6@molgen.mpg.de>
Date:   Mon, 14 Jan 2019 11:09:35 +0100
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     x86@...nel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: tsc: Fast TSC calibration failed with AMD B350M/Ryzen 3 2200G

Dear Thomas,


On 01/11/19 21:43, Thomas Gleixner wrote:

> On Mon, 7 Jan 2019, Paul Menzel wrote:
>> On 01/07/19 16:24, Thomas Gleixner wrote:
>>>> Linux 4.19.13 from Debian Sid/unstable logs the message below on the board MSI
>>>> MS-7A37/B350M MORTAR with the processor AMD Ryzen 3 2200G.
>>>>
>>>> As a result, the early time stamps do not seem to be working.
>>>
>>>>> [    0.000000] DMI: Micro-Star International Co., Ltd. MS-7A37/B350M MORTAR (MS-7A37), BIOS 1.I0 11/06/2018
>>>>> [    0.000000] tsc: Fast TSC calibration failed
>>>
>>> And the further boot log says:
>>>
>>> [    0.036000] tsc: Unable to calibrate against PIT
>>> [    0.036000] tsc: using HPET reference calibration
>>> [    0.036000] tsc: Detected 3500.117 MHz processor
>>>
>>> So the quick calibration in early boot fails because the PIT seems not to
>>> do what the kernel expects. Nothing we can cure :(
>>
>> I see. Can AMD confirm that this is the expected behavior? If yes, should
>> the fast TSC calibration be skipped on these devices?
> 
> It should work and we really don't want to add cpu family/model based
> decisions whether we invoke something or not. Those tables are stale before
> they hit mainline.

Understood. If it’s supposed to work, any hints on how to debug this?

Does some Linux kernel developers have an AMD Ryzen system, and can reproduce
the issue?

It seems to fail with an AMD Ryzen 2400G too [1].

It also fails on an AMD Ryzen 7 1700 [2].

```
[ 0.000000] Linux version 4.15.0-kali3-amd64 (devel@...i.org) (gcc version 7.3.0 (Debian 7.3.0-16)) #1 SMP Debian 4.15.17-1kali1 (2018-04-25)
[…]
[ 0.008000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.028000] tsc: Fast TSC calibration failed
[ 0.032000] tsc: PIT calibration matches HPET. 1 loops
[ 0.032000] tsc: Detected 2994.246 MHz processor
[…]
[ 0.044000] smpboot: CPU0: AMD Ryzen 7 1700 Eight-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)
```

It *works* here on one system with AMD Ryzen 5 PRO 1500 and Linux 4.14.87.

```
[    0.000000] Linux version 4.14.87.mx64.236 (root@...earollingstone.molgen.mpg.de) (gcc version 7.3.0 (GCC)) #1 SMP Mon Dec 10 09:48:57 CET 2018
[…]
[    0.000000] tsc: Fast TSC calibration using PIT
[…]
[    0.035000] smpboot: CPU0: AMD Ryzen 5 PRO 1500 Quad-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)
```


Kind regards,

Paul


[1]: https://bbs.archlinux.org/viewtopic.php?pid=1781282#p1781282
[2]: https://forums.kali.org/showthread.php?40444-error-loading-amdgpu-drivers-AMD-RX580-driver


Download attachment "smime.p7s" of type "application/pkcs7-signature" (5174 bytes)