From owner-freebsd-alpha Mon Nov 9 09:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24315 for freebsd-alpha-outgoing; Mon, 9 Nov 1998 09:01:15 -0800 (PST) (envelope-from owner-freebsd-alpha@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 JAA24287; Mon, 9 Nov 1998 09:01:00 -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 RAA21804; Mon, 9 Nov 1998 17:53:53 +0100 (CET) To: shimon@simon-shapiro.org cc: Doug Rabson , freebsd-alpha@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: tco_forward recursing In-reply-to: Your message of "Mon, 09 Nov 1998 12:38:44 EST." Date: Mon, 09 Nov 1998 17:53:53 +0100 Message-ID: <21802.910630433@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If you get this message once, your timecounter warranty expired 10 msec ago, and the system may be totally hosed in more than a few interesting ways. Tco_forward() should NEVER recurse like that. I have no explanation as to how this may or can happen. Stick a call to the debugger there and go look at how it happens. If the recursion is through hardclock() some splmumble() must be missing somewhere, if it comes through settime() somebody who shouldn't are messing with the system time do that at a very inopportune time. Sorry for my lack of detailed diagnosis... Poul-Henning In message , Simon Shapiro writes : > >Doug Rabson, On 08-Nov-98 you wrote: >> On Sat, 7 Nov 1998, Simon Shapiro wrote: >> >> > What is this error message and why does it happen? >> >> I think its something to do with the timecounter code. You could try >> asking phk about it. What is happening to the machine when you get the >> message? > >I have some patches from Poul, so I will cc him on this reply, just in >case. the machine rapidly and endlessly loops on this message and appears >dead otherwise (totally stops responding), but that can be due to >overloading the serial console. It seems like NFS triggers it more than >anything else. I copied /usr/src and /usr/ports fomr an nfs mount to a >local disk with no ill effects. IT does this reliably if you try to >compile across NFS. > >Simon > > -- 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-alpha" in the body of the message