Messages in this thread | | | Date | Mon, 22 Dec 2014 12:06:06 -0800 | Subject | Re: frequent lockups in 3.18rc4 | From | Linus Torvalds <> |
| |
On Mon, Dec 22, 2014 at 11:47 AM, Linus Torvalds <torvalds@linux-foundation.org> wrote: > > .. and we might still lock up under some circumstances. But at least > from my limited testing, it is infinitely much better, even if it > might not be perfect. Also note that my "testing" has been writing > zero to the HPET lock (so the HPET clock difference tends to be pretty > specific), while my next step is to see what happens when I write > random values (and a lot of them). > > Since I expect that to cause more problems, I thought I'd send this > RFC out before I start killing my machine again ;)
Ok, not horrible. Although I'd suggest not testing in a terminal window while running X. The time jumping will confuse X input timing and the screensaver, to the point that the machine may not be dead, but it isn't exactly usable. Do it in a virtual console.
Again, making the limit tighter (one second?) and perhaps not trusting insane values too much at walltime clock update time either, might make it all work smoother still.
I did manage to confuse systemd with all the garbage the kernel spewed, with a lot of stuff like:
systemd-journald[779]: Failed to write entry (9 items, 276 bytes), ignoring: Invalid argument
showing up in the logs, but I'm writing this without having had to reboot the machine.
Linus
| |