From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756152Ab2BAKvq (ORCPT ); Wed, 1 Feb 2012 05:51:46 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:61208 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753845Ab2BAKvo (ORCPT ); Wed, 1 Feb 2012 05:51:44 -0500 Message-ID: <4F291935.2030205@gmail.com> Date: Wed, 01 Feb 2012 18:51:33 +0800 From: Cong Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: TAO HU CC: Don Zickus , linux-kernel@vger.kernel.org, Ingo Molnar , linux-arm-kernel@lists.infradead.org, linux-omap Subject: Re: In many cases softlockup can not be reported after disabling IRQ for long time References: <20120131154748.GA5650@redhat.com> In-Reply-To: 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 (Please don't top-reply.) On 02/01/2012 10:18 AM, TAO HU wrote: > Hi, Don > > Thanks for your feedback! > > Unfortunately, the hardlockup depends on NMI which is not available on > ARM (Cortex-A9) per my understanding. > Our system uses OMAP4430. Any more suggestions? When there is no NMI, touch_nmi_watchdog() actually touches softlockup watchdog: #if defined(ARCH_HAS_NMI_WATCHDOG) || defined(CONFIG_HARDLOCKUP_DETECTOR) #include extern void touch_nmi_watchdog(void); #else static inline void touch_nmi_watchdog(void) { touch_softlockup_watchdog(); } #endif so you need to check if other places calling touch_nmi_watchdog() especially on ARM.