From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: nouveau X lockup on 36-rc (regression from 2.6.35) Date: Wed, 25 Aug 2010 15:55:06 +0200 Message-ID: <1282744506.3667.4.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from sipsolutions.net (he.sipsolutions.net [78.46.109.217]) by gabe.freedesktop.org (Postfix) with ESMTP id BE2C19E761 for ; Wed, 25 Aug 2010 07:23:00 -0700 (PDT) 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: Ben Skeggs , Francisco Jerez Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org Since 2.6.36-rc kernels (both rc1 and rc2) I've had X lockups where X sits in a loop just using CPU. The only kernel message I got this time was this one: [22290.792075] [drm] nouveau 0000:02:00.0: PFIFO_DMA_PUSHER - Ch 2 stracing X just repeats, in a loop, ioctl(9, 0x40086482, 0x7fff6a873af0) = ? ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) @ 0 (0) --- rt_sigreturn(0xe) = -1 EINTR (Interrupted system call) so apparently that ioctl never returns. 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. johannes