Date: Fri, 6 Nov 1998 20:28:00 +0000 (GMT) From: Doug Rabson <dfr@nlsystems.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Bill Paul <wpaul@skynet.ctr.columbia.edu>, current@FreeBSD.ORG Subject: Re: Grrr... calcru: negative time blah blah blah Message-ID: <Pine.BSF.4.01.9811062027030.19324-100000@herring.nlsystems.com> In-Reply-To: <5140.910380623@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Nov 1998, Poul-Henning Kamp wrote: > > >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... Don't do that if you ever want to use this card for 3D graphics. The 3Dlabs cards work best when doing interrupt driven DMA for 3D. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 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?Pine.BSF.4.01.9811062027030.19324-100000>