From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [git pull] drm next tree Date: Wed, 23 Mar 2011 08:22:26 -0700 Message-ID: <20110323082226.04510229@jbarnes-desktop> References: <4D89E5E1.3070402@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <4D89E5E1.3070402@earthlink.net> Sender: linux-kernel-owner@vger.kernel.org To: sclark46@earthlink.net Cc: Linus Torvalds , Dave Airlie , Chris Wilson , Keith Packard , DRI mailing list , linux-kernel@vger.kernel.org List-Id: dri-devel@lists.freedesktop.org On Wed, 23 Mar 2011 08:21:53 -0400 Stephen Clark wrote: > On 03/22/2011 10:19 PM, Linus Torvalds wrote: > > So I had hoped - yes, very na=EFve of me, I know - that this merge > > window would be different. > > > > But it's not. > > > > On Wed, Mar 16, 2011 at 9:09 PM, Dave Airlie wro= te: > > =20 > >> i915: big 855 fix, lots of output setup refactoring, lots of misc = fixes. > >> =20 > > .. and apparently a lot of breakage too. My crappy laptop that I ab= use > > for travel is - once more - broken by the updates. I cannot suspend > > and resume, because every resume seems to fail. > > > > One of the more useful failures was: > > > > [ 61.656055] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer > > elapsed... GPU hung > > [ 61.656079] [drm] capturing error event; look for more informati= on > > in /debug/dri/0/i915_error_state > > [ 61.664387] [drm:i915_wait_request] *ERROR* i915_wait_request > > returns -11 (awaiting 2 at 0, next 3) > > > > and I'm attaching the error_state file from that particular case he= re. > > In other cases it seems to just hang entirely. > > > > Keith/Jesse/Chris - I don't know that it's i915, and it will take > > forever to bisect (I'll try). But it does seem pretty likely. > > > > Linus > > =20 > Why can't the gpu be reset/restarted when this happens? When a nic ca= rd=20 > gets hung it is reinitialized > and restarted why not the gpu? Yeah, we try to restart in this case, but often just end up back in the same situation when the app runs again. We could be meaner about things and SIGILL the app, but often it's an innocent bystander, and the real problem is kernel object synchronization and/or the DRI driver generating bad commands. --=20 Jesse Barnes, Intel Open Source Technology Center