From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263909AbTLEHlG (ORCPT ); Fri, 5 Dec 2003 02:41:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263913AbTLEHlF (ORCPT ); Fri, 5 Dec 2003 02:41:05 -0500 Received: from aun.it.uu.se ([130.238.12.36]:30156 "EHLO aun.it.uu.se") by vger.kernel.org with ESMTP id S263909AbTLEHlC (ORCPT ); Fri, 5 Dec 2003 02:41:02 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16336.13962.285442.228795@alkaid.it.uu.se> Date: Fri, 5 Dec 2003 08:40:58 +0100 From: Mikael Pettersson To: Jesse Allen Cc: linux-kernel@vger.kernel.org Subject: Re: Catching NForce2 lockup with NMI watchdog In-Reply-To: <20031205045404.GA307@tesore.local> References: <20031205045404.GA307@tesore.local> X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jesse Allen writes: > Hi, > > I have a NForce2 board and can easily reproduce a lockup with grep on an IDE > hard disk at UDMA 100. The lockup occurs when both Local APIC + IO-APIC are > enabled. It was suggested to me to use NMI watchdog to catch it. However, the > NMI watchdog doesn't seem to work. > > When I set the kernel parameter "nmi_watchdog=1" I get this message in > /var/log/syslog: > Dec 4 20:10:30 tesore kernel: ..MP-BIOS bug: 8254 timer not connected to > IO-APIC > Dec 4 20:10:30 tesore kernel: timer doesn't work through the IO-APIC - > disabling NMI Watchdog! > > "nmi_watchdog=2" seems to work at first, In /var/log/messages: > Dec 4 20:13:11 tesore kernel: testing NMI watchdog ... OK. > but it still locks up. The NMI watchdog can only handle software lockups, since it relies on the CPU, and for nmi_watchdog=1 the I/O-APIC + bus, still running. Hardware lockups result in, well, hardware lockups :-(