From owner-freebsd-current@FreeBSD.ORG Fri Aug 13 20:11:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8234116A4CE; Fri, 13 Aug 2004 20:11:38 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E18C743D49; Fri, 13 Aug 2004 20:11:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.201] ([192.168.0.201]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i7DKBYw7042907; Fri, 13 Aug 2004 14:11:35 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <411D1FE5.3080809@samsco.org> Date: Fri, 13 Aug 2004 14:09:09 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.1) Gecko/20040801 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lukas Ertl References: <20040813215227.F730@korben.in.tern> In-Reply-To: <20040813215227.F730@korben.in.tern> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Martin Blapp cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: Deadlocks with recent SMP current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 20:11:38 -0000 Lukas Ertl wrote: > On Fri, 13 Aug 2004, Robert Watson wrote: > >> will eventually get a solid hang. I tried it on a new SMP box with an >> NMI >> button I received yesterday but was unable to get into the debugger. I'm >> in the process of de-obfuscating the NMI path to increase the chances of >> successfully getting into the debugger and then I'll try again to see >> what >> I can figure out. > > > I have an NMI-enabled SMP box too, and the only message I got when > sending an NMI to the deadlocked system was 'kernel trap 12 with > interrupts disabled', but nothing more. > > If you want me to test something, feel free to shout out. > > cheers, > le > The NMI handler(s) try to do far too much and often get caught up in mutexes. I've locally changed it to just call either kdb_backtrace() or kdb_enter() and then reboot. We might want to consider looking for a general solution for this in 5.3. Scott