Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755418AbaLVUGJ (ORCPT ); Mon, 22 Dec 2014 15:06:09 -0500 Received: from mail-qg0-f47.google.com ([209.85.192.47]:40778 "EHLO mail-qg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754764AbaLVUGH (ORCPT ); Mon, 22 Dec 2014 15:06:07 -0500 MIME-Version: 1.0 In-Reply-To: References: <20141219145528.GC13404@redhat.com> <20141221223204.GA9618@codemonkey.org.uk> Date: Mon, 22 Dec 2014 12:06:06 -0800 X-Google-Sender-Auth: UoLwc0VJxk0xpPsM1VRpYPfUplU Message-ID: Subject: Re: frequent lockups in 3.18rc4 From: Linus Torvalds To: Dave Jones , Thomas Gleixner , Chris Mason , Mike Galbraith , Ingo Molnar , Peter Zijlstra , =?UTF-8?Q?D=C3=A2niel_Fraga?= , Sasha Levin , "Paul E. McKenney" , Linux Kernel Mailing List , Suresh Siddha , Oleg Nesterov , Peter Anvin , John Stultz Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 22, 2014 at 11:47 AM, Linus Torvalds 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/