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: <9f444c64-c221-e729-7eb5-fc4f093c16d3@molgen.mpg.de>
Date:   Mon, 7 Jan 2019 16:33:59 +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/07/19 16:24, Thomas Gleixner wrote:

> On Mon, 31 Dec 2018, Paul Menzel 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?


Kind regards,

Paul


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ