On 1/31/20 1:11 PM,
mmo...@disroot.org wrote:
> Hi everyone!
>
> Is anyone experiencing this issue on resume (VMs being killed randomly
> apparently due to clock skew that generates kernel panic) ??
> This is happening very often and it makes suspend useless.
>
> I'm using a Lenovo T480s.
>
> Any ideas are really appreciated!
>
> Thanks!
>
> December 22, 2019 8:13 PM,
mmo...@disroot.org
> <mailto:
mmo...@disroot.org> wrote:
>
> Hello,
>
> I've been struggle with this for months now.
> Whenever there's a resume from suspend some random AppVms are
> killed. Although this doesn't happen all the time it happens often
> enough on resume sufficiently to indicate an issue.
> It seems that the clock skew is too large resulting in a kernel
> panic that kills the AppVM as the error below shows.
>
> Is anyone experiencing the same issue? Is there any solution to this?
>
> Thank you in advance.
>
> /*[38009.358471] clocksource: timekeeping watchdog on CPU0: Marking
> clocksource 'tsc' as unstable because the skew is too large:
> [38009.358521] clocksource: 'xen' wd_now: 2697b2c28a19 wd_last:
> 2696858155d9 mask: ffffffffffffffff
> [38009.358558] clocksource: 'tsc' cs_now: ffffff40e6dd060e cs_last:
> 4900d58115e2 mask: ffffffffffffffff*
> [38009.358594] tsc: Marking TSC unstable On 1/31/20 1:11 PM,
mmo...@disroot.org wrote:> Hi everyone!
>
> Is anyone experiencing this issue on resume (VMs being killed randomly
> apparently due to clock skew that generates kernel panic) ??
> This is happening very often and it makes suspend useless.
>
> I'm using a Lenovo T480s.
>
> Any ideas are really appreciated!
>
> Thanks!
>
> December 22, 2019 8:13 PM,
mmo...@disroot.org
> <mailto:
mmo...@disroot.org> wrote:
>
> Hello,
>
> I've been struggle with this for months now.
> Whenever there's a resume from suspend some random AppVms are
> killed. Although this doesn't happen all the time it happens often
> enough on resume sufficiently to indicate an issue.
> It seems that the clock skew is too large resulting in a kernel
> panic that kills the AppVM as the error below shows.
>
> Is anyone experiencing the same issue? Is there any solution to this?
>
> Thank you in advance.
>
> /*[38009.358471] clocksource: timekeeping watchdog on CPU0: Marking
> clocksource 'tsc' as unstable because the skew is too large:
> [38009.358521] clocksource: 'xen' wd_now: 2697b2c28a19 wd_last:
> 2696858155d9 mask: ffffffffffffffff
> [38009.358558] clocksource: 'tsc' cs_now: ffffff40e6dd060e cs_last:
> 4900d58115e2 mask: ffffffffffffffff*
> 64616f6c00708019On 1/31/20 1:11 PM,
mmo...@disroot.org wrote:> Hi everyone!
>
> Is anyone experiencing this issue on resume (VMs being killed randomly
> apparently due to clock skew that generates kernel panic) ??
> This is happening very often and it makes suspend useless.
>
> I'm using a Lenovo T480s.
>
> Any ideas are really appreciated!
>
> Thanks!
>
> December 22, 2019 8:13 PM,
mmo...@disroot.org
> <mailto:
mmo...@disroot.org> wrote:
>
> Hello,
>
> I've been struggle with this for months now.
> Whenever there's a resume from suspend some random AppVms are
> killed. Although this doesn't happen all the time it happens often
> enough on resume sufficiently to indicate an issue.
> It seems that the clock skew is too large resulting in a kernel
> panic that kills the AppVM as the error below shows.
>
> Is anyone experiencing the same issue? Is there any solution to this?
>
> Thank you in advance.
>
> /*[38009.358471] clocksource: timekeeping watchdog on CPU0: Marking
> clocksource 'tsc' as unstable because the skew is too large:
> [38009.358521] clocksource: 'xen' wd_now: 2697b2c28a19 wd_last:
> 2696858155d9 mask: ffffffffffffffff
> [38009.358558] clocksource: 'tsc' cs_now: ffffff40e6dd060e cs_last:
> 4900d58115e2 mask: ffffffffffffffff*
> *[79152.716987] Kernel panic - not syncing: Fatal exception*
> [79152.717276] Kernel OffseThe tsc warnings happen a long time before the segfault, which looks like
> [79152.716864] R13: ffff8880f5b210c4 R14: 0000000000000001 R15:
> 0000000000080000
> [79152.716885] FS: 0000000000000000(0000) GS:ffff8880f5b00000(0000)
> knlGS:0000000000000000
> [79152.716906] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [79152.716923] CR2: 00007f088fac85ee CR3: 000000000220a004 CR4:
> 00000000003606e0
> [79152.716946] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> [79152.716967] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
> 0000000000000400
> *[79152.716987] Kernel panic - not syncing: Fatal exception*
> [79152.717276] Kernel OffseThe tsc warnings happen a long time before the segfault, which looks like
> *[79152.716987] Kernel panic - not syncing: Fatal exception*
> [79152.717276] Kernel Offset: disabled/
>
>
The tsc warnings happen some time before the segfault appears.
Rather, the segfault mentions python3.5 and systemctl, and the
code lines show that the kernel is trying to close a socket.
Also, the line
"[79152.712416] CPU: 1 PID: 2425 Comm: systemctl Tainted: G O"
is showing that a non-linux module has been loaded (the "O"). Do
you have a proprietary module that you load? (graphics, or network
drivers?). If you can try without those it may help.
Mike.