Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752507AbbBSQOs (ORCPT ); Thu, 19 Feb 2015 11:14:48 -0500 Received: from mail-ie0-f178.google.com ([209.85.223.178]:41236 "EHLO mail-ie0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751634AbbBSQOr (ORCPT ); Thu, 19 Feb 2015 11:14:47 -0500 MIME-Version: 1.0 In-Reply-To: References: <20150218222544.GA17717@twins.programming.kicks-ass.net> Date: Thu, 19 Feb 2015 08:14:46 -0800 X-Google-Sender-Auth: 72H3KV6pKmqYqxDw4cbck59fGis Message-ID: Subject: Re: smp_call_function_single lockups From: Linus Torvalds To: Rafael David Tinoco 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: 943 Lines: 21 On Thu, Feb 19, 2015 at 7:42 AM, Rafael David Tinoco wrote: > > Just a quick feedback, We were able to reproduce the lockup with this > proposed patch (3.19 + patch). Unfortunately we had problems with the > core file and I have only the stack trace for now but I think we are > able to reproduce it again and provide more details (sorry for the > delay... after a reboot it took some days for us to reproduce this > again). > > It looks like RIP is still smp_call_function_single. 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. 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/