From owner-freebsd-current Fri Nov 6 12:10:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24427 for freebsd-current-outgoing; Fri, 6 Nov 1998 12:10:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24418 for ; Fri, 6 Nov 1998 12:10:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00446; Fri, 6 Nov 1998 12:04:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811062004.MAA00446@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul cc: phk@critter.freebsd.dk (Poul-Henning Kamp), current@FreeBSD.ORG Subject: Re: Grrr... calcru: negative time blah blah blah In-reply-to: Your message of "Fri, 06 Nov 1998 14:05:07 EST." <199811061905.OAA15554@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Nov 1998 12:04:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm starting to think the problem in this case is an interrupt storm, > but I'm not sure how to debug it. If I set up a second system to do > a remote gdb of the first one, can I single step through things like > interrupt handlers without Weird Things (tm) happening? Throw in a hack to register null interrupt handlers for all the free interrupts, then watch the interrupt stats. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message