On Wed, Jul 06, 2022 at 08:20:05PM -0400, Mohamed Aslan wrote: > > 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. > > > > I can confirm that this is also the case with Linux. This is the > output of dmesg on Void Linux: > > [ 0.000000] tsc: Fast TSC calibration using PIT > [ 0.000000] tsc: Detected 2096.114 MHz processor > ... > ... > [ 1.314252] TSC synchronization [CPU#0 -> CPU#1]: > [ 1.314252] Measured 6615806646 cycles TSC warp between CPUs, turning off > TSC clock. > [ 1.314252] tsc: Marking TSC unstable due to check_tsc_sync_source failed > [ 1.314397] #2 #3 #4 #5 #6 #7
This is good news. My code isn't the only code finding a problem :) > > Not sure if Void is a Lenovo supported Linux distribution, still > though I think it's worth reporting. Probably not. Your laptop may not even be "Linux certified", but it's worth reporting all the same.
