[Expired for linux-signed-hwe (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Has the problem been observed in kernel versions 5.x? Like in Ubuntu
20.04 onward?
** Changed in: linux-signed-hwe (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I'm seeing the same thing. Basically, any use of clock_gettime now
requires a syscall (isntead of using vsdo). The applications I'm running
do a lot of clock_gettime's, and basically cannot run performantly
anymore after this happens.
This machine is a:
System Information
Manufacturer: Ali
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821441
Ti
** Summary changed:
- Clocksource changes from TRC to HPET after sleep. Kills performance.
+ Clocksource changes from TSC to HPET after sleep. Kills performance.
** Description changed:
This has been verified with a freshly reset bios. Every time I sleep
- Ubuntu and wake, the clock gets switc
