Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

Linux Operating SystemsOther Linux Discussions
All Forum Topics
Options

6 Posts

03-25-2021

Croatia

6 Signins

15 Page Views

  • Posts: 6
  • Registered: ‎03-25-2021
  • Location: Croatia
  • Views: 15
  • Message 11 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-12, 18:03 PM

Fixed in firmware 1.18 on L15 Ryzen Gen 1 (20U7).

Reply
Options

194 Posts

03-06-2021

Germany

85 Signins

1245 Page Views

  • Posts: 194
  • Registered: ‎03-06-2021
  • Location: Germany
  • Views: 1245
  • Message 12 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-18, 22:36 PM

@DaveOber @MarkRHPearson,

 

on the P14s the initial issue is fixed but I found a new bug because of the fix I assume.

 

Booting now with clocksource=hpet will or will not ( seems random ) break tsc now.

I'm not sure what is causing that or how to 100% to reproduce, since I get that 1 in

10+ boots, but I post the kernel messages for reference until I find more out.

 

Mai 19 00:03:36 frugalware kernel: clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc-early' as unstable because the skew is too large:
Mai 19 00:03:36 frugalware kernel: clocksource:                       'hpet' wd_now: e00985 wd_last: 73ad19 mask: ffffffff
Mai 19 00:03:36 frugalware kernel: clocksource:                       'tsc-early' cs_now: 5824f8bf2 cs_last: 52bf432ec mask: ffffffffffffffff
Mai 19 00:03:36 frugalware kernel: tsc: Marking TSC unstable due to clocksource watchdog
Mai 19 00:03:36 frugalware kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
Mai 19 00:03:36 frugalware kernel: sched_clock: Marking unstable (1088347816, 358934)<-(1464910851, -18373620)

 

That is on kernel 5.12.4.

Reply
Options

78 Posts

12-26-2020

Austria

43 Signins

605 Page Views

  • Posts: 78
  • Registered: ‎12-26-2020
  • Location: Austria
  • Views: 605
  • Message 13 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-18, 22:39 PM

@ osnix wrote:

Mai 19 00:03:36 frugalware kernel: tsc: Marking TSC unstable due to clocksource watchdog
Mai 19 00:03:36 frugalware kernel: TSC found unstable after boot, most likely due to broken BIOS. Use '=unstable'.

 

Back to the square one. Thank you for testing, any chance you have LTS kernel installed alongside the mainline? 5.12.XX is quite fresh.

Reply
Options

194 Posts

03-06-2021

Germany

85 Signins

1245 Page Views

  • Posts: 194
  • Registered: ‎03-06-2021
  • Location: Germany
  • Views: 1245
  • Message 14 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-18, 23:00 PM

@ jd_user wrote:

@ osnix wrote:

Mai 19 00:03:36 frugalware kernel: tsc: Marking TSC unstable due to clocksource watchdog
Mai 19 00:03:36 frugalware kernel: TSC found unstable after boot, most likely due to broken BIOS. Use '=unstable'.

 

Back to the square one. Thank you for testing, any chance you have LTS kernel installed alongside the mainline? 5.12.XX is quite fresh.

 

No, I don't but I can build and install any kernel.

However, that is not a kernel problem in 99.99999% of the case.

 

Also, kernel development is working the other way around if you find a bug.

 Like so:

 

1) Find a bug on some kernel/ HW combo and report it

2) You'll be asked to use the latest kernel code and see if you can reproduce it.

2a) If you can then you go to bisect the problem ( best is if you can find a working kernel first )

2b) If you can't is fixed already and once you / the devels find out what fix that is, stable people get notified.

3) Fix(es) are pushed to stable & LTS kernels

 

Here my personal note about LTS kernel(s) & new HW:

 

Those are the cause of most problems because newer HW needs

a newer kernel and newer firmware packages. And most of the users

don't understand this.

 

I will install some 5.10.x LTS tomorrow but first I need to find some reproducer,

or what exactly is causing this.

Reply
Options

6 Posts

03-25-2021

Croatia

6 Signins

15 Page Views

  • Posts: 6
  • Registered: ‎03-25-2021
  • Location: Croatia
  • Views: 15
  • Message 15 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-19, 15:05 PM

@ xkrx wrote:

Fixed in firmware 1.18 on L15 Ryzen Gen 1 (20U7).

 

Spoke too soon. On some boots I see (L15, firmware 1.18, kernel 5.10):

[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 1696.898 MHz processor
[    0.069394] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1875b4ef64c, max_idle_ns: 440795203028 ns
[    0.529793] clocksource: Switched to clocksource tsc-early
[    1.709410] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc-early' as unstable because the skew is too large:
[    1.709414] clocksource:                       'tsc-early' cs_now: 9dab26bca cs_last: 99a4b2255 mask: ffffffffffffffff
[    1.709419] tsc: Marking TSC unstable due to clocksource watchdog
[    1.709452] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.

 

Reply
Options

194 Posts

03-06-2021

Germany

85 Signins

1245 Page Views

  • Posts: 194
  • Registered: ‎03-06-2021
  • Location: Germany
  • Views: 1245
  • Message 16 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-19, 15:11 PM

@ xkrx wrote:

@ xkrx wrote:

Fixed in firmware 1.18 on L15 Ryzen Gen 1 (20U7).

 

Spoke too soon. On some boots I see (L15, firmware 1.18, kernel 5.10):

[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 1696.898 MHz processor
[    0.069394] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1875b4ef64c, max_idle_ns: 440795203028 ns
[    0.529793] clocksource: Switched to clocksource tsc-early
[    1.709410] clocksource: timekeeping watchdog on CPU2: Marking clocksource '-early' as unstable because the skew is too large:
[    1.709414] clocksource:                       '-early' cs_now: 9dab26bca cs_last: 99a4b2255 mask: ffffffffffffffff
[    1.709419] tsc: Marking TSC unstable due to clocksource watchdog
[    1.709452] TSC found unstable after boot, most likely due to broken BIOS. Use '=unstable'.

 

 

Yes, I saw that too, on the P14s, but is not always reproducible.

I'm still trying to figure what triggers that sometimes.

( it is something in the watchdog code now but not sure why only sometimes ).

 

Btw, can you post a full dmesg of that broken boot somewhere?

( or attach a log here ? )

 

Thx :)

Reply
Options

194 Posts

03-06-2021

Germany

85 Signins

1245 Page Views

  • Posts: 194
  • Registered: ‎03-06-2021
  • Location: Germany
  • Views: 1245
  • Message 17 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-19, 16:10 PM

@ osnix wrote:

@DaveOber @MarkRHPearson,

 

on the P14s the initial issue is fixed but I found a new bug because of the fix I assume.

 

Booting now with clocksource=hpet will or will not ( seems random ) break tsc now.

I' not sure what is causing that or how to 100% to reproduce, since I get that 1 in

10+ boots, but I post the kernel messages for reference until I find more out.

 

Mai 19 00:03:36 frugalware kernel: clocksource: timekeeping watchdog on CPU1: Marking clocksource '-early' as unstable because the skew is too large:
Mai 19 00:03:36 frugalware kernel: clocksource:                       '' wd_now: e00985 wd_last: 73ad19 mask: ffffffff
Mai 19 00:03:36 frugalware kernel: clocksource:                       '-early' cs_now: 5824f8bf2 cs_last: 52bf432ec mask: ffffffffffffffff
Mai 19 00:03:36 frugalware kernel: tsc: Marking TSC unstable due to clocksource watchdog
Mai 19 00:03:36 frugalware kernel: TSC found unstable after boot, most likely due to broken BIOS. Use '=unstable'.
Mai 19 00:03:36 frugalware kernel: sched_clock: Marking unstable (1088347816, 358934)<-(1464910851, -18373620)

 

That is on kernel 5.12.4.

@DaveOber , @MarkRHPearson ,

 

I have a reproducer for that.

 

Use latest BIOS, then boot a kernel ( 5.10++ tested ).

Open a terminal:

 

1) verify tsc is fine ( dmesg | grep tsc )

2) either use poweroff, or shutdown -h -f now and shut down the box.

3) wait 10 seconds at least then power on the box again.

4) goto 1. Now you should hit the bug. 

5) use reboot command to fix that.

 

( looks like reboot is fixing it, a shutdown will break it again .. )

 

Anyway, this means a shutdown/poweroff will trigger the bug

too.

 

It looks to me like some registers are left in a bad state,

and the Firmware itself seems to not check that on next boot.

 

Unfortunately, this is a wild guess, and I don't have any tools nor the firmware

source code to look at ;).

 

I hope this helps to find the issue.

 

Gabriel

Reply
Options

6 Posts

03-25-2021

Croatia

6 Signins

15 Page Views

  • Posts: 6
  • Registered: ‎03-25-2021
  • Location: Croatia
  • Views: 15
  • Message 18 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-19, 17:13 PM

@ osnix wrote:

@ xkrx wrote:

@ xkrx wrote:

Fixed in firmware 1.18 on L15 Ryzen Gen 1 (20U7).

 

Spoke too soon. On some boots I see (L15, firmware 1.18, kernel 5.10):

[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 1696.898 MHz processor
[    0.069394] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1875b4ef64c, max_idle_ns: 440795203028 ns
[    0.529793] clocksource: Switched to clocksource tsc-early
[    1.709410] clocksource: timekeeping watchdog on CPU2: Marking clocksource '-early' as unstable because the skew is too large:
[    1.709414] clocksource:                       '-early' cs_now: 9dab26bca cs_last: 99a4b2255 mask: ffffffffffffffff
[    1.709419] tsc: Marking TSC unstable due to clocksource watchdog
[    1.709452] TSC found unstable after boot, most likely due to broken BIOS. Use '=unstable'.

 

 

Yes, I saw that too, on the P14s, but is not always reproducible.

I' still trying to figure what triggers that sometimes.

( it is something in the watchdog code now but not sure why only sometimes ).

 

Btw, can you post a full dmesg of that broken boot somewhere?

( or attach a log here ? )

 

Thx :)

 

Sure.

https://pastebin.com/cDYUTJqx

Reply
Options

194 Posts

03-06-2021

Germany

85 Signins

1245 Page Views

  • Posts: 194
  • Registered: ‎03-06-2021
  • Location: Germany
  • Views: 1245
  • Message 19 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-19, 17:23 PM

@ xkrx wrote:

@ osnix wrote:

@ xkrx wrote:

@ xkrx wrote:

Fixed in firmware 1.18 on L15 Ryzen Gen 1 (20U7).

 

Spoke too soon. On some boots I see (L15, firmware 1.18, kernel 5.10):

[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 1696.898 MHz processor
[    0.069394] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1875b4ef64c, max_idle_ns: 440795203028 ns
[    0.529793] clocksource: Switched to clocksource tsc-early
[    1.709410] clocksource: timekeeping watchdog on CPU2: Marking clocksource '-early' as unstable because the skew is too large:
[    1.709414] clocksource:                       '-early' cs_now: 9dab26bca cs_last: 99a4b2255 mask: ffffffffffffffff
[    1.709419] tsc: Marking TSC unstable due to clocksource watchdog
[    1.709452] TSC found unstable after boot, most likely due to broken BIOS. Use '=unstable'.

 

 

Yes, I saw that too, on the P14s, but is not always reproducible.

I' still trying to figure what triggers that sometimes.

( it is something in the watchdog code now but not sure why only sometimes ).

 

Btw, can you post a full dmesg of that broken boot somewhere?

( or attach a log here ? )

 

Thx :)

 

Sure.

https://pastebin.com/cDYUTJqx

 

Thx, could you test something maybe ?

 

1) open a terminal and use reboot command to reboot the box

2) open a terminal and verify the bug is not there use: dmesg | grep tsc

3) shut down the box using shutdown -h now

4) wait at least 10sec then power on the box

5) verify you hit the bug: dmesg | grep tsc

 

If you could reproduce that way then I may have a workaround for now.

 

Append the following to your kernel command line ( better grub & rebuild your grub.cfg & initrd ):

 

tsc=nowatchdog

 

After, that try to reproduce again.

 

( note to clear the bug for the next boot you need to use reboot command )

 

Thx.

 

 

Reply
Options

194 Posts

03-06-2021

Germany

85 Signins

1245 Page Views

  • Posts: 194
  • Registered: ‎03-06-2021
  • Location: Germany
  • Views: 1245
  • Message 20 of 33

Re:Unusable TSC on P14s and X13 with the latest LTS kernel

2021-05-19, 17:31 PM

For all hitting this new TSC bug with BIOS 1.32, here a workaround,

for now:

 

1) open /etc/default/grub and append tsc=nowatchdog to GRUB_CMDLINE_LINUX,

or GRUB_CMDLINE_LINUX_DEFAULT ( depending on your Distribution ).

2) use your Distribution tool to rebuild the grub.cfg and initrd

3) if you see this bug in your dmesg, use:'  dmesg | grep tsc ' to verify,

then use the reboot command to reboot the box once.

After that shutdown/poweroff should work again.

 

Best Regards,

 

Gabriel

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms