From owner-freebsd-current Fri Nov 17 18: 9:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9611537B4C5 for ; Fri, 17 Nov 2000 18:09:11 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA21567 for ; Fri, 17 Nov 2000 21:09:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAI29Bt50968; Fri, 17 Nov 2000 21:09:11 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 17 Nov 2000 21:09:10 -0500 (EST) To: current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... In-Reply-To: <200011171826.LAA75925@harmony.village.org> References: <2967.974461715@axl.fw.uunet.co.za> <200011171826.LAA75925@harmony.village.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14869.58485.15187.975790@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh writes: > In message <2967.974461715@axl.fw.uunet.co.za> Sheldon Hearn writes: > : The problem with a hard lock-up out of which you can't escape into the > : debugger is that it makes meaningful bug reports impossible. My non-SMP > : workstation has exhibited apparently arbitrary lock-ups since the advent > : of SMPng. > > You can also short IOCHK to ground to get an NMI which kicks you into > the debugger, even in an interrupt context. I have a card I built > from an old multi-function card to do this. I think it is A1 and A2, > but I don't have my ISA bus spec handy. Or you can use an alpha; most of which have a halt button that will drop you into the SRM console. ;) Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message