From owner-freebsd-bugs@FreeBSD.ORG  Mon Jan 17 04:50:00 2005
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4E48C16A4CE; Mon, 17 Jan 2005 04:50:00 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2642043D48; Mon, 17 Jan 2005 04:50:00 +0000 (GMT)
	(envelope-from anholt@FreeBSD.org)
Received: from freefall.freebsd.org (anholt@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j0H4o0E4092679;
	Mon, 17 Jan 2005 04:50:00 GMT
	(envelope-from anholt@freefall.freebsd.org)
Received: (from anholt@localhost)
	by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j0H4o00m092675;
	Mon, 17 Jan 2005 04:50:00 GMT
	(envelope-from anholt)
Date: Mon, 17 Jan 2005 04:50:00 GMT
From: Eric Anholt <anholt@FreeBSD.org>
Message-Id: <200501170450.j0H4o00m092675@freefall.freebsd.org>
To: anholt@FreeBSD.org, freebsd-bugs@FreeBSD.org, anholt@FreeBSD.org
Subject: Re: kern/71547: [hang] xorg hangs on startup, maybe due to
	R200_cp_microcode not loading.
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2005 04:50:00 -0000

Synopsis: [hang] xorg hangs on startup, maybe due to R200_cp_microcode not loading.

Responsible-Changed-From-To: freebsd-bugs->anholt
Responsible-Changed-By: anholt
Responsible-Changed-When: Mon Jan 17 04:49:39 GMT 2005
Responsible-Changed-Why: 
Looks like another report of nforce2 agp issues.

http://www.freebsd.org/cgi/query-pr.cgi?pr=71547