Date: Fri, 06 Nov 1998 20:30:23 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Bill Paul <wpaul@skynet.ctr.columbia.edu> Cc: current@FreeBSD.ORG Subject: Re: Grrr... calcru: negative time blah blah blah Message-ID: <5140.910380623@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 06 Nov 1998 14:05:07 EST." <199811061905.OAA15554@skynet.ctr.columbia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>Actually, looking at the patch closer, I realize now that none of the >warning messages actually triggered. However each time, the calcru >messages did appear and the system console response became sluggish. > >I'm starting to think the problem in this case is an interrupt storm, >but I'm not sure how to debug it. (Already answered in more detail), but yes, this sounds very probable for this (and maybe other cases as well). The difference between the timecounter code and the previous "tick++" code is that the former would just loose track of 10 msec per lost hardclock(), whereas the timecounter code fails less gracefully. I have no good advise on debugging a problem like this, except to try to disable the interrupt in hardware. We're talking video card, right ? Cut the trace on the board, you don't need that interrupt... -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5140.910380623>