On (04/20/18 06:37), David Herrmann wrote: > > I get lots of timer-errors on Arch-Linux booting current master, after > a suspend/resume cycle. Just a selection of errors I see on resume:
Hello David, Any chance you can revert the patches in question and test? I'm running ARCH (4.17.0-rc1-dbg-00042-gaa03ddd9c434) and suspend/resume cycle does not trigger any errors. Except for this one kernel: do_IRQ: 0.55 No irq handler for vector > systemd[1]: systemd-journald.service: Main process exited, > code=dumped, status=6/ABRT > rtkit-daemon[742]: The canary thread is apparently starving. Taking action. > systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! > systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)! > kernel: e1000e 0000:00:1f.6: Failed to restore TIMINCA clock rate delta: -22 > > Lots of crashes with SIGABRT due to these. > > I did not bisect it, but it sounds related to me. Also, user-space > uses CLOCK_MONOTONIC for watchdog timers. That is, a process is > required to respond to a watchdog-request in a given MONOTONIC > time-frame. If this jumps during suspend/resume, watchdogs will fire > immediately. I don't see how this can work with the new MONOTONIC > behavior? -ss