From owner-freebsd-current Fri Nov 17 10:32:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 300BA37B479 for ; Fri, 17 Nov 2000 10:32:45 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAHIp7725638; Fri, 17 Nov 2000 19:51:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... In-Reply-To: Your message of "Fri, 17 Nov 2000 11:26:02 MST." <200011171826.LAA75925@harmony.village.org> Date: Fri, 17 Nov 2000 19:51:07 +0100 Message-ID: <25636.974487067@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011171826.LAA75925@harmony.village.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. Bad news for you warner: On a too large sample of my newer motherboards this doesn't work anymore :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message