Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752339AbbBWOBM (ORCPT ); Mon, 23 Feb 2015 09:01:12 -0500 Received: from mail-qc0-f171.google.com ([209.85.216.171]:45583 "EHLO mail-qc0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752028AbbBWOBL (ORCPT ); Mon, 23 Feb 2015 09:01:11 -0500 MIME-Version: 1.0 X-Originating-IP: [191.180.238.226] In-Reply-To: References: <20150218222544.GA17717@twins.programming.kicks-ass.net> Date: Mon, 23 Feb 2015 11:01:09 -0300 Message-ID: Subject: Re: smp_call_function_single lockups From: Rafael David Tinoco To: Linus Torvalds Cc: Peter Zijlstra , LKML , Thomas Gleixner , Jens Axboe , Frederic Weisbecker , Gema Gomez , chris.j.arges@canonical.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 996 Lines: 28 On Thu, Feb 19, 2015 at 2:14 PM, Linus Torvalds wrote: > > Hmm. Still just the stack trace for the CPU that is blocked (CPU0), if > you can get the core-file to work and figure out where the other CPU > is, that would be good. > This is v3.19 + your patch (smp acquire/release) - (nested kvm with 2 vcpus on top of proliant with x2apic cluster mode and acpi_idle) * http://people.canonical.com/~inaddy/lp1413540/STACK_TRACE.txt http://people.canonical.com/~inaddy/lp1413540/BACKTRACES.txt http://people.canonical.com/~inaddy/lp1413540/FOREACH_BT.txt * It looks like we got locked because of reentrant flush_tlb_* through smp_call_* but I'll leave it to you. let me know if you need any more info.. - Rafael Tinoco -- 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/