From owner-freebsd-current Mon Apr 6 05:47:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19591 for freebsd-current-outgoing; Mon, 6 Apr 1998 05:47:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from psasolar.psa.pencom.com (psasolar.colltech.com [208.229.236.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19586 for ; Mon, 6 Apr 1998 05:47:21 -0700 (PDT) (envelope-from ejon@colltech.com) Received: (from ejon@localhost) by psasolar.psa.pencom.com (VER/What/1.0) id HAA17043; Mon, 6 Apr 1998 07:43:59 -0500 (CDT) Message-Id: <199804061243.HAA17043@psasolar.psa.pencom.com> 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: Mon, 6 Apr 1998 07:43:58 -0500 (CDT) Cc: freebsd-current@FreeBSD.ORG From: Eric "Two Cats" Jones X-Mailer: ELM [version 2.4ME+ PL31 (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, I had what I think is the same problem (although I was building directly from the XF86 source base, not the port: the port may avoid this problem). My problem was that the XF86 server code implements their own malloc, for which they need the hardware pagesize. The code checks whether to use sysconf(5) for this info by doing #ifdef _SC_PAGESIZE, which until about 3/28 was false. After 3/28, this value is defined, however the backend code would cause sysconf(_SC_PAGESIZE) to return -1, which XF86 didn't bother to check. It would later use this pagesize to calculate what size chunk to allocate off the heap, with disasterous consequences. There's a way to force the code to use the getpagesize(3) call, but I can't remember off the top of my head and I've deleted my distribution. Check xc/programs/Xserver/os/xalloc.c and look for _SC_PAGESIZE... you should be able to figure it out from there. I suspect your log messages are coincidental. Eric Jones Collective Technology Strange sunspot activity caused Oliver Banta to write: > 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. > [...] > > To make sure it wasn't something dumb on my part, I ran XF86Setup > which uses the XF86_VGA16 server, and it also core dumped on me. I > ran this when I originally installed 3.0-SNAP and it worked fine. > This is the error I get, in case it will help anyone figure out what's > wrong: > > Apr 4 04:03:12 knuth /kernel: forward_hardclock: checkstate 0 > Apr 4 04:03:13 knuth last message repeated 15 times > Apr 4 04:03:15 knuth /kernel: pid 12296 (XF86_VGA16), uid 0: exited on signal 6 > (core dumped) > > I am currently rebuilding world and will try again as soon as it > finishes. I will also try it with SMP not enabled to see if that > makes any difference. If anyone has any hints or suggestions, I'd > love to hear them. > > Cheers, > -- Oliver > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message