From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751780AbaKYRWJ (ORCPT ); Tue, 25 Nov 2014 12:22:09 -0500 Received: from mail-qg0-f51.google.com ([209.85.192.51]:52629 "EHLO mail-qg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750846AbaKYRWH convert rfc822-to-8bit (ORCPT ); Tue, 25 Nov 2014 12:22:07 -0500 MIME-Version: 1.0 In-Reply-To: <54741540.3010607@suse.com> References: <20141121142301.564f7eb7@gandalf.local.home> <20141124184856.GA9349@laptop.dumpdata.com> <54741540.3010607@suse.com> Date: Tue, 25 Nov 2014 09:22:04 -0800 X-Google-Sender-Auth: EctTo7rD9xU8-uCN1GfzwtoE3AY Message-ID: Subject: Re: frequent lockups in 3.18rc4 From: Linus Torvalds To: =?UTF-8?B?SsO8cmdlbiBHcm/Dnw==?= Cc: Konrad Rzeszutek Wilk , Josh Boyer , Andy Lutomirski , Steven Rostedt , Tejun Heo , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Peter Zijlstra , Frederic Weisbecker , Don Zickus , Dave Jones , "the arch/x86 maintainers" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 24, 2014 at 9:36 PM, Jürgen Groß wrote: > > Funny, during testing some patches related to Xen I hit the lockup > issue. It looked a little bit different, but a variation of your patch > solved my problem. > > I could reproduce the issue within a few minutes reliably without the > patch below. With it the machine survived 12 hours and is still running. Do you have a backtrace for the failure case? I have no problem applying this part of the patch (I really don't understand why x86-64 hadn't gotten the proper code from 32-bit), but I'd like to see (and document) where the fault happens for this. Since you can apparently reproduce this fairly easily with a broken kernel, getting a backtrace shouldn't be too hard? Linus