From owner-freebsd-stable@FreeBSD.ORG Tue Feb 10 06:07:25 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A342F106566C; Tue, 10 Feb 2009 06:07:25 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 722828FC08; Tue, 10 Feb 2009 06:07:25 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from [192.168.1.132] (adsl-1-207-86.bna.bellsouth.net [65.1.207.86]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n1A66dJY052310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2009 01:06:41 -0500 (EST) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: "Bruce M. Simpson" In-Reply-To: <4990BC99.1070108@FreeBSD.org> References: <329181233306971@webmail57.yandex.ru> <985A59F2-20CC-4779-A000-018E52B5BFA9@jump-ing.de> <101781233319948@webmail36.yandex.ru> <4983A3AE.90804@FreeBSD.org> <498F901A.7000900@FreeBSD.org> <1234159237.23838.3.camel@ferret.2hip.net> <4990835A.3020303@FreeBSD.org> <1234208586.1524.17.camel@ferret.2hip.net> <4990BC99.1070108@FreeBSD.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-pDhaORuYHyDjB+7pVlxu" Organization: FreeBSD Date: Tue, 10 Feb 2009 01:07:14 -0500 Message-Id: <1234246034.1524.27.camel@ferret.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_00, MIME_QP_LONG_LINE, RCVD_IN_PBL, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: "S.N.Grigoriev" , Markus Hitter , freebsd-stable@freebsd.org Subject: Re: Unhappy Xorg upgrade X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 06:07:25 -0000 --=-pDhaORuYHyDjB+7pVlxu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2009-02-09 at 23:30 +0000, Bruce M. Simpson wrote: > Robert Noland wrote: > > ... > > Ok, that is odd... Once drm is loaded and X opens it, the ddx driver > > should request that the irq handler be installed. At that point, dmesg > > should show something resembling the following. > > > > vgapci0: child drm0 requested pci_enable_busmaster > > info: [drm] AGP at 0xc0000000 256MB > > info: [drm] Initialized i915 1.6.0 20080730 > > drm0: [ITHREAD] > > =20 >=20 > Yes, I normally see output similar to this when X is started. >=20 > > ... > > > > Does the issue still occur if drm is disabled? > > =20 >=20 > Just tried disabling DRM w/ 'Options "DRI" "off"' in Section "Device". > DRM is indeed disabled -- no dmesg output and not loaded by X. >=20 > However the problem is still there. >=20 > BTW: This Radeon card does have MSI capabilities according to lspci,=20 > however they do not appear to be enabled either by FreeBSD or by X. I=20 > was about to point the finger at interrupt filters, however that blows=20 > that theory out of the water. >=20 > FWIW the IBM T43 here has an i915GM, and USB is working just fine and=20 > dandy. The main data point which sticks out is the fact that the=20 > affected machine is amd64. >=20 > Now that DRM has been disabled on my box, this would point the finger at=20 > the X userland. >=20 > I don't see any obvious nasties in my Section "Device", although I do=20 > pass a BusID and BusType to prevent X from trying to use the second head=20 > with RandR (lots of pain with fubar DVI cables when I first purchased=20 > the monitor). >=20 > I skimmed pci_user.c, thinking libpciaccess just thunks to it via=20 > /dev/pci, it appears there's no instrumentation there I can turn on to=20 > see what userland is actually frobbing. Ok, lets try another test... There is a scanpci util in the libpciaccess port. We don't install it, but it does get built. Build the port and run scanpci -v as root from the console. That should poke all the pci devices on the box and tell you about them. See if that is able to trigger the issue. robert. > thanks, > BMS > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --=20 Robert Noland FreeBSD --=-pDhaORuYHyDjB+7pVlxu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEABECAAYFAkmRGZEACgkQM4TrQ4qfRONIFwCfUt7MWo2OQIIdIjeqxwO4XIeS dIkAn2mw2zrU/0/PClUYR+u92nSoqQ75 =lgzg -----END PGP SIGNATURE----- --=-pDhaORuYHyDjB+7pVlxu--