From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757894Ab3HNPYL (ORCPT ); Wed, 14 Aug 2013 11:24:11 -0400 Received: from g6t0187.atlanta.hp.com ([15.193.32.64]:40577 "EHLO g6t0187.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750861Ab3HNPYJ (ORCPT ); Wed, 14 Aug 2013 11:24:09 -0400 Message-ID: <520BA109.1000501@hp.com> Date: Wed, 14 Aug 2013 11:23:53 -0400 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Ingo Molnar CC: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Arnd Bergmann , linux-arch@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, Peter Zijlstra , Steven Rostedt , Andrew Morton , Greg Kroah-Hartman , Matt Fleming , Michel Lespinasse , Andi Kleen , Rik van Riel , "Paul E. McKenney" , Linus Torvalds , Raghavendra K T , George Spelvin , Harvey Harrison , "Chandramouleeswaran, Aswin" , "Norton, Scott J" Subject: Re: [PATCH v3 0/3] qrwlock: Introducing a queue read/write lock implementation References: <1375315259-29392-1-git-send-email-Waiman.Long@hp.com> <520A811A.7080907@hp.com> <20130814102041.GG10849@gmail.com> In-Reply-To: <20130814102041.GG10849@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/14/2013 06:20 AM, Ingo Molnar wrote: > * Waiman Long wrote: > >> >> I would like to share with you a rwlock related system crash that I >> encountered during my testing with hackbench on an 80-core DL980. The >> kernel crash because of a "watchdog detected hard lockup on cpu 79". The >> crashing CPU was running "write_lock_irq(&tasklist_lock)" in >> forget_original_parent() of the exit code path when I interrupted the >> hackbench which was spawning thousands of processes. Apparently, the >> remote CPU was not able to get the lock for a sufficient long time due >> to the unfairness of the rwlock which I think my version of queue rwlock >> will be able to alleviate this issue. >> >> So far, I was not able to reproduce the crash. I will try to see if I >> could more consistently reproduce it. > Was it an actual crash/lockup, or a longish hang followed by a lock > detector splat followed by the system eventually recovering back to > working order? > > Thanks, > > Ingo It was an actual crash initiated by the NMI handler. I think the system was in a halt state after that. Regards, Longman