-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'timekeeping watchdog: Marking clocksource 'tsc' as unstable, because the skew is too large' - may lead to connection and privacy issues #2044
Comments
Does it happen after system suspend? That may cause
But how that would lead to privacy problems? AFAIR you've told that slightly different time in VMs is actually a good thing for privacy. In addition to Whonix using its own time synchronization mechanism, it should actually improve privacy ( |
Marek Marczykowski-Górecki:
No system suspend involved. (I personally use this almost never except
Yes, but 1) and 2) both require a functional VM clock to begin with. If
sdwdate has a certain range of accuracy. While I am experiencing only |
The message you've included shouldn't result in huge clock jumps. Pausing a VM (including system suspend) without synchronizing the clock afterwards will. But it is unrelated situation. |
I see.
|
This bug report has seen no activity in a very long time, and it is not assigned to any current release milestone. It looks like it was left open by mistake, so I'm closing it now. However, if anyone is still affected by this bug on a currently-supported release, please leave a comment, and we'll be happy to reopen this. Thank you. |
Just pausing a VM for a host suspend breaks 'tsc' clocksource. QubesOS/qubes-issues#7404 QubesOS/qubes-issues#2044
There is no need to disable virtual (dummy) interfaces before suspend, it matters only for physical ones. Especially, do not de-configure dummy eth1 used by Whonix, as there is nothing to turn it back on after resume. QubesOS/qubes-issues#2044 QubesOS/qubes-issues#7404
There is no need to disable virtual (dummy) interfaces before suspend, it matters only for physical ones. Especially, do not de-configure dummy eth1 used by Whonix, as there is nothing to turn it back on after resume. QubesOS/qubes-issues#2044 QubesOS/qubes-issues#7404 (cherry picked from commit ce8bfa0)
Qubes OS version (e.g.,
R3.1
):R3.1
Affected TemplateVMs (e.g.,
fedora-23
, if applicable):debian-8, Fedora-23, Whonix 13, probably every template
Actual behavior:
A two seconds time draft. (VM clock is two seconds faster.)
Does not always happen. If I spot this in one already running VM, I spot this in any already running VM that I test.
Full dmesg attached below.
Expected behavior:
None of this should be happening.
Steps to reproduce the behavior:
No cause / effect witnessed yet. Please run
dmesg | grep clock
in your AppVMs every now and then (on various computers). If we are lucky you will be able to reproduce it yourself.General notes:
Impact: Anonymity / Whonix is affected by this bug. Might break connectivity for some users. (#1779) On my systems, I witnessed only small skews yet, but for other users it may be much bigger and therefore causing Tor connection interruptions. Possibly also worsening privacy / fingerprinting.
Related issues:
#1779
The text was updated successfully, but these errors were encountered: