From nobody@FreeBSD.org  Mon Dec 22 09:40:01 2003
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 591AB16A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 22 Dec 2003 09:40:01 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7159D43D4C
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 22 Dec 2003 09:40:00 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id hBMHe0dL042542
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 22 Dec 2003 09:40:00 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id hBMHe0kV042533;
	Mon, 22 Dec 2003 09:40:00 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200312221740.hBMHe0kV042533@www.freebsd.org>
Date: Mon, 22 Dec 2003 09:40:00 -0800 (PST)
From: Mark Evenson <evenson@panix.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: launching X freezes CURRENT
X-Send-Pr-Version: www-2.0

>Number:         60512
>Category:       misc
>Synopsis:       launching X freezes CURRENT
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    anholt
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 22 09:50:17 PST 2003
>Closed-Date:    Sun May 09 17:38:36 PDT 2004
>Last-Modified:  Sun May 09 17:38:36 PDT 2004
>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:

From: John Byrnes <jb1@alfred.edu>
To: freebsd-gnats-submit@FreeBSD.org, evenson@panix.com
Cc:  
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Thu, 22 Jan 2004 22:01:48 -0500

 I have the same problem on a thinkpad A22m.  Almost exact same symptoms.
 
 John

From: Daniel Roethlisberger <daniel@roe.ch>
To: freebsd-gnats-submit@FreeBSD.org
Cc: evenson@panix.com, jb1@alfred.edu
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Sat, 31 Jan 2004 02:55:57 +0100

 I might have the same problem here with 5.2-RELEASE on an Thinkpad A20p
 (2629-62G; ATI Rage Mobility 128, r128.ko) -- seemingly random but not
 infrequent freezes when starting X with startx or shutting down the X
 server, sometimes still in graphical mode, sometimes already in console.
 
 Cheers,
 Dan
 
 
 -- 
     Daniel Roethlisberger <daniel@roe.ch>
     OpenPGP key id 0x804A06B1 (1024/4096 DSA/ElGamal)
     144D 6A5E 0C88 E5D7 0775 FCFD 3974 0E98 804A 06B1
 !->

From: Teemu Koponen <tkoponen@niksula.hut.fi>
To: freebsd-gnats-submit@FreeBSD.org, evenson@panix.com
Cc:  
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Sun, 1 Feb 2004 19:53:26 +0200 (EET)

 Starting X always hangs 5.2-RELEASE Thinkpad X20 here too. The video card
 is ATI Rage Mobility P/M.
 
 Teemu
 
 --
 tkoponen@iki.fi # PGP public key: http://www.iki.fi/tkoponen/pgp.asc
 

From: Jan-Espen Pettersen <sigsegv@leakingmemory.org>
To: freebsd-gnats-submit@FreeBSD.org, evenson@panix.com
Cc:  
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Mon, 02 Feb 2004 01:07:54 +0100

 XFree86 freezes here too if I enable dri, but works fine without dri...
 
 Preloaded elf module "/boot/kernel/agp.ko" at 0xc082321c.
 agp0: <NVIDIA nForce2 AGP Controller> mem 0xe8000000-0xebffffff at 
 device 0.0 on pci0
 
 drm0: <ATI Radeon QY RV100 7000/VE> port 0xa000-0xa0ff mem 
 0xed000000-0xed00ffff,0xe0000000-0xe7ffffff irq 11 at device 0.0 on pci2
 info: [drm] AGP at 0xe8000000 64MB
 info: [drm] Initialized radeon 1.10.0 20020828 on minor 0
 
 System is an NF7-M motherboard with NForce2 chipset.
 
 It loops while doing an ioctl to /dev/dri/card0
 Here is a small part of ktrace of XFree86:
 
  49609 XFree86  CALL  ioctl(0x7,0x20006444 ,0)
  49609 XFree86  RET   ioctl -1 errno 16 Device busy
  49609 XFree86  CALL  ioctl(0x7,0x20006444 ,0)
  49609 XFree86  RET   ioctl -1 errno 16 Device busy
  49609 XFree86  CALL  ioctl(0x7,0x20006444 ,0)
  49609 XFree86  RET   ioctl -1 errno 16 Device busy
  49609 XFree86  CALL  ioctl(0x7,0x20006444 ,0)
  49609 XFree86  RET   ioctl -1 errno 16 Device busy
 *continues for ever*
 
 sys runs at nearly 100% after starting XFree86 (with dri), the console 
 dies and does never come up again. The kernel is up and userland works, 
 so I could ssh in and do ktrace, etc, and shutdown it 'cleanly'..
 
 Sorry, I don't have a null-modem cable yet..
 
 Jan-Espen Pettersen
 
 

From: Heiner <h.eichmann@gmx.de>
To: freebsd-gnats-submit@FreeBSD.org, evenson@panix.com
Cc:  
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Sat, 14 Feb 2004 14:13:19 +0100

 Same on my box. Its an old P3 with an old erazor graphics card. FreeBSd 4.8 + 
 latest XFree4 (till december) worked flawless. After deleting it completely, 
 I installed FreeBSD 5.2.1 with XFree86-4 from the ports cvs (beginning of 
 february). xf86cfg freezes the machine on exit. With the configuration file 
 from an old 4.8 backup, the command XFree86 freezes immediately. Freezes 
 means no reaction anymore. Even pings were not responded.
 
 What helped was to remove the lines
 
 	Load  "glx"
 	Load  "dri"
 	Load  "record"
 
 Note, that each of them will cause the problem. Without this three even kde is 
 running.
 
 
 Heiner
 

From: Mark Evenson <evenson@panix.com>
To: Heiner <h.eichmann@gmx.de>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/60512: launching X freezes CURRENT
Date: 15 Feb 2004 11:10:22 -0500

 Heiner <h.eichmann@gmx.de> writes:
 
 > Same on my box. Its an old P3 with an old erazor graphics card. FreeBSd 4.8 + 
 > latest XFree4 (till december) worked flawless. After deleting it completely, 
 > I installed FreeBSD 5.2.1 with XFree86-4 from the ports cvs (beginning of 
 > february). xf86cfg freezes the machine on exit. With the configuration file 
 > from an old 4.8 backup, the command XFree86 freezes immediately. Freezes 
 > means no reaction anymore. Even pings were not responded.
 > 
 > What helped was to remove the lines
 > 
 > 	Load  "glx"
 > 	Load  "dri"
 > 	Load  "record"
 > 
 > Note, that each of them will cause the problem. Without this three even kde is 
 > running.
 
 Thanks for the advice, but my situation seems to be even worse:  removing
 the XFree86 module loading doesn't seem to affect my box.  It will still
 freeze on startup most times, only sometimes it somehow "makes it through"
 the initialization phase, kicking itself all the way to actually working.
 
 Do you have any idea how to get some additional information out of the
 frozen box?  I wish I could see a backtrace or something to have an avenue
 for investigation, but no such luck.
 
 
 -- 
 Mark Evenson <evenson@panix.com>
 
 "A screaming comes across the sky.  It has happened before, but there is
 nothing to compare to it now."

From: Heiner <h.eichmann@gmx.de>
To: Mark Evenson <evenson@panix.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Mon, 16 Feb 2004 12:58:30 +0100

 After installing some new components (mainly kde stuff) the situation is worse 
 here as well. startx starts KDE but the only way to terminate it is to go to 
 the controlling terminal and press ctrl-C. The normal kde exits freezes BSD 
 completely. Even disabeling all drivers and upgrading to the latest 
 Xfree-Server port version does not help. As "freeze" also kills the disk 
 cache, all log file entries (if there are any) will not make it to the disk. 
 Disabeling the soft updates might help here. I will try if I find some time.
 
 
 Heiner
 

From: Heiner <h.eichmann@gmx.de>
To: Mark Evenson <evenson@panix.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Mon, 16 Feb 2004 21:09:51 +0100

 On my FreeBSD (5.2.x) there is a boot promt at the beginning. If I choose 2 
 (no acpi), all X-windows problems are gone! I can now start and finish KDE 
 without a single freeze (tested 6 times with 2 reboots in between).
 
 Heiner
 

From: "Benny" <mail1@nathalie.sweetfactory.org>
To: freebsd-gnats-submit@FreeBSD.org, evenson@panix.com
Cc:  
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Thu, 19 Feb 2004 14:13:25 +0100

 Hello, 
 
 seems as I have the same problem. If I'm trying to start X, the system 
 freezes. Even pings are not responded. Not always but every fourth time or 
 so.
 I tried to remove those modules from XF86Config, which are named in a former 
 posting(glx, dri, record), but it didn't help. So I disabled ACPI and it 
 worked. No freezes anymore. Only wanted to mention this... 
 
 
 with best regards,
  --- benny 
 
 

From: Daniel Roethlisberger <daniel@roe.ch>
To: freebsd-gnats-submit@FreeBSD.org, evenson@panix.com
Cc:  
Subject: Re: misc/60512: launching X freezes CURRENT
Date: Fri, 2 Apr 2004 14:04:31 +0200

 Not compiling SMP support into the kernel works around the problem for
 me without having to disable ACPI.
 -Dan
 
Responsible-Changed-From-To: freebsd-bugs->anholt 
Responsible-Changed-By: arved 
Responsible-Changed-When: Sun Apr 25 06:49:21 PDT 2004 
Responsible-Changed-Why:  
Over to dri Maintainer.  

http://www.freebsd.org/cgi/query-pr.cgi?pr=60512 
State-Changed-From-To: open->closed 
State-Changed-By: anholt 
State-Changed-When: Sun May 9 17:28:51 PDT 2004 
State-Changed-Why:  
This PR is uselessly filled with different reports.  Original reporter's issue 
can't be with the DRI, because his card doesn't support the DRI (as of the 
software in ports at the time).  Someone reports what could be a DRM issue, but 
information only shows that the card has hung and is being reset.  Another 
reports that any of 3 unrelated XFree86 modules causes the machine to hard-lock. 
Later he reports a hang (probably a panic) on exiting KDE unless ACPI is disabled, 
and another says disabling SMP does the same. 

Any of these as separate reports might have been interesting, but it's too hard 
to follow now, and little of it seems to relate to the DRM, anyway.  Close it. 
Those that are still having problems should file separate reports for separate 
issues. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=60512 
>Unformatted:
