Date: Mon, 22 Dec 2003 09:40:00 -0800 (PST) From: Mark Evenson <evenson@panix.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/60512: launching X freezes CURRENT Message-ID: <200312221740.hBMHe0kV042533@www.freebsd.org> Resent-Message-ID: <200312221750.hBMHoHuk061452@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 60512
>Category: misc
>Synopsis: launching X freezes CURRENT
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Dec 22 09:50:17 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Mark Evenson
>Release: CURRENT
>Organization:
>Environment:
FreeBSD quip 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Dec 22 10:28:51 CET 2003 realtime@quip:/usr/obj/usr/src-QUIP/sys/GENERIC i386
>Description:
invoking 'startx' completely freezes CURRENT built from cvsup of 20031217.
No panic, no messages, no nothing to go further on.
Hardware is a Thinkpad X20 part no. 2662-34U with a Rage Mobility P/M AGP 2x 4MB card.
Problem first occurred after building and installing CURRENT from end of November 2003 (something like 20031122). Since this was a transition over the "64bit statfs hump", I initially thought that this was a problem with something in userland that needed to be recompiled. I have since completely de-installed and re-built from scratch every package with a forwards and backwards dependency on XFree86-4 with the same results of crash.
Running xf86cfg works, making me suspect a problem with the "dri" module, but my knowledge of XFree86 is getting dated so the obvious route of commenting out "dri" and "glx" module load in XF86Config still results in a freeze.
I believe
>How-To-Repeat:
Install CURRENT on same hardware; invoke 'startx'.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312221740.hBMHe0kV042533>