On Wed, Jul 06, 2022 at 01:48:39AM -0400, Mohamed Aslan wrote: > > This is expected behavior with the patch. > > > > cpu0's TSC is way out of sync with every > > other CPU's TSC, so the TSC is marked > > as a bad timecounter and a different one is > > chosen. > > Yes, I can see. Just want to add that without your latest patch the > kernel chooses the TSC as clocksource, however only the *user* TSC > was disabled (cpu1: disabling user TSC (skew=-5028216492)). > > > Are you running the latest BIOS available > > for your machine? > > No, I don't think I am.
First, you need to update to the latest firmware. Maybe they already fixed the problem. I don't see any mention of the TSC in the BIOS changelog for the e495 but maybe you'll get lucky. Second, if they haven't fixed the problem with the latest firmware, I recommend you reach out to Lenovo and report the problem. Lenovo seem to have been sympathetic to reports about TSC desync in the past on other models and issued firmware fixes. For example, the v1.28 firmware for the ThinkPad A485 contained a fix for what I assume is a very similar problem to the one you're having: https://download.lenovo.com/pccbbs/mobiles/r0wuj65wd.txt And this forum post, for example, got some response from Lenovo staff: https://forums.lenovo.com/t5/ThinkPad-T400-T500-and-newer-T-series-Laptops/T14s-G1-AMD-TSC-clock-unusable/m-p/5070296?page=1 So, open a post for your model and cite the other posts. They might not be sympathetic to the fact that you're seeing the issue on OpenBSD. If that's a problem you should be able to reproduce the problem with a recent Linux kernel. The Linux kernel runs a similar sync test during boot and will complain if the TSCs are not synchronized. Honestly, to save time you may want to just boot up a supported Linux distribution and grab the error message before you ask for support.
