From mboxrd@z Thu Jan 1 00:00:00 1970 From: Francisco Jerez Subject: Re: nouveau X lockup on 36-rc (regression from 2.6.35) Date: Mon, 30 Aug 2010 21:08:49 +0200 Message-ID: <87sk1v535q.fsf@riseup.net> References: <1282744506.3667.4.camel@jlt3.sipsolutions.net> <1283185822.3694.1.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1187629496==" Return-path: Received: from mx1.riseup.net (mx1.riseup.net [204.13.164.18]) by gabe.freedesktop.org (Postfix) with ESMTP id 4BFAD9E9AE for ; Mon, 30 Aug 2010 12:02:48 -0700 (PDT) In-Reply-To: <1283185822.3694.1.camel@jlt3.sipsolutions.net> (Johannes Berg's message of "Mon, 30 Aug 2010 18:30:22 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Johannes Berg Cc: "Rafael J. Wysocki" , Ben Skeggs , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1187629496== Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Johannes Berg writes: > On Wed, 2010-08-25 at 15:55 +0200, Johannes Berg wrote: >> Since 2.6.36-rc kernels (both rc1 and rc2) I've had X lockups where X >> sits in a loop just using CPU. >>=20 >> The only kernel message I got this time was this one: >>=20 >> [22290.792075] [drm] nouveau 0000:02:00.0: PFIFO_DMA_PUSHER - Ch 2 >>=20 >> stracing X just repeats, in a loop, >>=20 >> ioctl(9, 0x40086482, 0x7fff6a873af0) =3D ? ERESTARTSYS (To be restart= ed) >> --- SIGALRM (Alarm clock) @ 0 (0) --- >> rt_sigreturn(0xe) =3D -1 EINTR (Interrupted system= call) >>=20 >>=20 >> so apparently that ioctl never returns. >>=20 >> This has never happened on 2.6.35, and I've gone back now. Large screen >> updates seem to trigger it more likely, but I haven't found a way to >> really reproduce it. FWIW, I'm running with two screens connected. > > This problem persists in -rc3, where I'd hoped the nouveau changes would > actually fix it :-( In fact, it seems I was either "lucky" or it was > made easier to trigger, this time it already happened during my login. > That's already fixed in the nouveau kernel tree. > johannes --=-=-=-- --==-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iF4EAREIAAYFAkx8AcIACgkQg5k4nX1Sv1saLgD/ddgWckw7zMU/BnbrNyZTZkcE kA0urCIc5bZtndsQBTYA/0CoxPIiXTSnpkuvQBPdbgqO62AeNr714k5Im9+dM7Ev =8hGd -----END PGP SIGNATURE----- --==-=-=-- --===============1187629496== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1187629496==--