From owner-cvs-all Fri Jun 7 21:41:17 2002 Delivered-To: cvs-all@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1F38237B405; Fri, 7 Jun 2002 21:41:12 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA30562; Sat, 8 Jun 2002 14:38:30 +1000 Date: Sat, 8 Jun 2002 14:39:12 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "M. Warner Losh" Cc: jhb@FreeBSD.org, , , Subject: Re: cvs commit: src/sys/kern kern_sig.c In-Reply-To: <20020607.095516.116907129.imp@village.org> Message-ID: <20020608143156.K18237-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 7 Jun 2002, M. Warner Losh wrote: > In message: > John Baldwin writes: > : You mean the SIGXCPU that is commented out in mi_switch()? It will > : be turned back on when I or someone else figures out how to do it > : safely. :) > > I thought that was commented out due to a bug where time would go > backwards every so often, causing there to be 2^32 or so time to be > charged to the process, which put it over the limit. The quick fix for a locking bug in certain console driver(s) (of turning off the printfs) just broke the warning about the timecounter going backwards. The warning and the panic are still live in calcru(), but calcru() is not called nearly as often as mi_switch() so the problem is rarely detected there. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message