From owner-freebsd-current Wed Aug 19 23:14:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28549 for freebsd-current-outgoing; Wed, 19 Aug 1998 23:14:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.syracuse.net (zone.syracuse.net [205.232.47.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28541 for ; Wed, 19 Aug 1998 23:14:22 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by zone.syracuse.net (8.8.8/8.8.7) with SMTP id CAA25275; Thu, 20 Aug 1998 02:08:08 -0400 (EDT) Date: Thu, 20 Aug 1998 02:08:08 -0400 (EDT) From: Brian Feldman X-Sender: green@zone.syracuse.net To: Poul-Henning Kamp cc: Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-Reply-To: <534.903592714@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, how about we try out Mike's idea? Someone who experiences the SIGXCPU kill problem could try putting the following in kern/kern_synch.c line 638: if (switchtime.tv_usec < p->p_switchtime.tv_usec || switchtime.tv_sec < p->p_switchtime.tv_sec) panic("bogus microuptime twiddling"); And see if we get some nice panics and cores. Is it worth a shot? I've never gotten a SIGXCPU out of place, so my machine wouldn't be the one to test this on. Cheers, Brian Feldman green@unixhelp.org On Thu, 20 Aug 1998, Poul-Henning Kamp wrote: > In message <199808200451.VAA13481@usr02.primenet.com>, Terry Lambert writes: > >> >> It's probably a good idea to get this fixed ASAP, since people have been > >> >> complaining about this exact bug for months now. Would anyone like to give > >> >> me any pointers to where to start evaluating the code at, or what > >> >> functions this could be caused by? I think I'll check the process > >> >> accounting code first then the actual timing code, if noone has any better > >> >> ideas. > >> > > >> >My suggestion would be to implement this timing using a monoclock. > >> > >> I fully agree, great idea Terry! > >> > >> We've had that for several months already :-) > > > >Cool! Then we can mark this bug resolved! 8-). > > No, we can mark your diagnosis as wrong. :-) > > -- > 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