Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753654AbaLUXtF (ORCPT ); Sun, 21 Dec 2014 18:49:05 -0500 Received: from arcturus.aphlor.org ([188.246.204.175]:57254 "EHLO arcturus.aphlor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752581AbaLUXtD (ORCPT ); Sun, 21 Dec 2014 18:49:03 -0500 X-Greylist: delayed 4553 seconds by postgrey-1.27 at vger.kernel.org; Sun, 21 Dec 2014 18:49:03 EST Date: Sun, 21 Dec 2014 17:32:04 -0500 From: Dave Jones To: Linus Torvalds Cc: Thomas Gleixner , Chris Mason , Mike Galbraith , Ingo Molnar , Peter Zijlstra , =?iso-8859-1?Q?D=E2niel?= Fraga , Sasha Levin , "Paul E. McKenney" , Linux Kernel Mailing List , Suresh Siddha , Oleg Nesterov , Peter Anvin Subject: Re: frequent lockups in 3.18rc4 Message-ID: <20141221223204.GA9618@codemonkey.org.uk> Mail-Followup-To: Dave Jones , Linus Torvalds , Thomas Gleixner , Chris Mason , Mike Galbraith , Ingo Molnar , Peter Zijlstra , =?iso-8859-1?Q?D=E2niel?= Fraga , Sasha Levin , "Paul E. McKenney" , Linux Kernel Mailing List , Suresh Siddha , Oleg Nesterov , Peter Anvin References: <20141219145528.GC13404@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Report: Spam report generated by SpamAssassin on "arcturus.aphlor.org" Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Authenticated-User: davej@codemonkey.org.uk Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Dec 21, 2014 at 02:19:03PM -0800, Linus Torvalds wrote: > > So the range of 1-251 seconds is not entirely random. It's all in > > that "32-bit HPET range". > > DaveJ, I assume it's too late now, and you don't effectively have any > access to the machine any more, but "hpet=disable" or "nohpet" on the > command line might be worth trying if you ever see that piece of > hardware again. I can give it a try tomorrow. I'm probably saying goodbye to that machine on Tuesday, so we'll have 24hrs of testing at least. > And for posterity, do you have a dmidecode with motherboard/BIOS > information for the problematic machine? And your configuration? I can grab that in the morning too. > And finally, and stupidly, is there any chance that you have anything > accessing /dev/hpet? Not knowingly at least, but who the hell knows what systemd has its fingers in these days. Dave -- 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/