From owner-freebsd-current Fri Nov 6 23:35:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05650 for freebsd-current-outgoing; Fri, 6 Nov 1998 23:35:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05641 for ; Fri, 6 Nov 1998 23:35:44 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id IAA10255; Sat, 7 Nov 1998 08:32:38 +0100 (CET) To: Peter Wemm cc: Bill Paul , current@FreeBSD.ORG Subject: Re: Grrr... calcru: negative time blah blah blah In-reply-to: Your message of "Sat, 07 Nov 1998 12:42:13 +0800." <199811070442.MAA18044@spinner.netplex.com.au> Date: Sat, 07 Nov 1998 08:32:38 +0100 Message-ID: <10253.910423958@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811070442.MAA18044@spinner.netplex.com.au>, Peter Wemm writes: >> 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? > >Just a thought that might be worth checking into.. Is the kstack growing >down into struct pstats, the sigacts, and perhaps pcb? This would be >highly dependent on interrupt handlers, machine load (amount of nesting) >etc and could explain why it hits some more than others. Peter, this would probably lead to much more bogosity than what we see here, but you suggestion for a trapdoor under the stack is certainly worthwhile in its own right. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message