From owner-freebsd-current Sun Apr 5 16:10:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15548 for freebsd-current-outgoing; Sun, 5 Apr 1998 16:10:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15476 for ; Sun, 5 Apr 1998 16:10:06 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA00517; Sun, 5 Apr 1998 18:09:53 -0500 (EST) (envelope-from toor) Message-Id: <199804052309.SAA00517@dyson.iquest.net> Subject: Re: Current with XFree86 3.3.2 In-Reply-To: <199804052149.QAA01036@aenima.unixgeeks.net> from Oliver Banta at "Apr 5, 98 04:49:20 pm" To: obanta@unixgeeks.net (Oliver Banta) Date: Sun, 5 Apr 1998 18:09:53 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Banta said: > > I recently installed 3.0-980311-SNAP on a Dual PPro 180. X was > working fine until I did two things: 1) rebuilt world to -current as > of April 3 and 2) rebuilt XFree86 3.3.2 from /usr/ports/x11/XFree86/. > Now whenever I try to start any X server, it core dumps on me. > Current seems to have had severe problems in the timer/clock code for the last few days. The code seems to be okay now. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message