Public bug reported:
Summary: System won't enter suspend after idle over 20 minutes
Steps to reproduce:
1. install manifest and boot into OS
2. idle system for 20 mins
Expected result:
System could enter suspend after idle over 20 minutes
Actual result:
System won't enter suspend after idle over 20 minutes
Failure rate: 3/3
Dmesg:
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping
watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too
large:
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet'
wd_now: e336cfbb wd_last: e2e9b5c5 mask: ffffffff
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc'
cs_now: 6299ac5acc cs_last: 6250285866 mask: ffffffffffffffff
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC
unstable due to clocksource watchdog
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after
boot, most likely due to broken BIOS. Use 'tsc=unstable'.
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking
unstable (158972862012, 149405080)<-(159105581047, 17903053)
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to
clocksource hpet
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1839818
Title:
System won't enter suspend after idle over 20 minutes (TSC unstable)
Status in OEM Priority Project:
New
Status in linux-oem package in Ubuntu:
New
Bug description:
Summary: System won't enter suspend after idle over 20 minutes
Steps to reproduce:
1. install manifest and boot into OS
2. idle system for 20 mins
Expected result:
System could enter suspend after idle over 20 minutes
Actual result:
System won't enter suspend after idle over 20 minutes
Failure rate: 3/3
Dmesg:
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource:
timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the
skew is too large:
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet'
wd_now: e336cfbb wd_last: e2e9b5c5 mask: ffffffff
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc'
cs_now: 6299ac5acc cs_last: 6250285866 mask: ffffffffffffffff
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC
unstable due to clocksource watchdog
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable
after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking
unstable (158972862012, 149405080)<-(159105581047, 17903053)
Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched
to clocksource hpet
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1839818/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
