Re: [GIT pull] printk updates for 4.15

[Linus Torvalds]

On Wed, Nov 15, 2017 at 4:37 PM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
>
> This broke stuff because the historic behaviour was to not advance on
> resume and the change caused massive timer expiries right after resume
> which confused the hell out of things, because timers fired immediately
> which were not expected to fire as they were implicitely relying on suspend
> not affecting clock monotonic.

Ahh, now that you mention it, I remember that. Things coming to a
complete halt because every single X event timer and network timer all
firing at resume.

If the timer wheel thing doesn't happen any more, I'd still be willing
to try it out, but you're right, it might be much worse than I
thought.

             Linus