From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Furniss Subject: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ? Date: Wed, 13 Apr 2011 21:01:42 +0100 Message-ID: <4DA60126.6030003@ukfsn.org> References: <20110406204327.GA11148@iram.es> <1302185075.24704.143.camel@thor.local> <20110411133128.GA24344@iram.es> <1302535963.24704.268.camel@thor.local> <20110412113033.GA16649@iram.es> <1302608770.27054.36.camel@thor.local> <20110412120055.GA7995@iram.es> <1302629362.15520.25.camel@thor.local> <20110413075943.GA27996@iram.es> <1302696736.15520.63.camel@thor.local> <20110413122751.GA21050@iram.es> <1302704124.15520.72.camel@thor.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <1302704124.15520.72.camel@thor.local> Sender: linux-kernel-owner@vger.kernel.org To: =?UTF-8?B?TWljaGVsIETDpG56ZXI=?= Cc: Gabriel Paubert , KH , linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org, LKML , Greg@freedesktop.org, =?UTF-8?B?VXdlIEtsZWluZS1Lw7ZuaWc=?= List-Id: dri-devel@lists.freedesktop.org Michel D=C3=A4nzer wrote: >>> That does sound like the GPU locks up. Do you get any messages in d= mesg >>> about lockups and attempts to reset the GPU at any time? >> >> No. > > Hmm, I guess the constant SIGALRMs might prevent the lockup detection > from kicking in... Maybe you can try starting the X server with > -dumbSched to see if that gets things along any further, but in the e= nd > there's probably no way around figuring out what causes the lockup an= d > fixing that anyway. I have an old AGP box that locks with 600g + agpgart - It used to give=20 GPU lockup to dmesg/log, but (I only test it occasionally) it doesn't=20 anymore. I can still sysrq OK. I wonder if something changed in recent months in the drm/whatever code= =20 that has changed/blocked the logging.