From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: [PATCH 2/2] tests: wedged + error_state read test Date: Wed, 04 Apr 2012 11:48:22 +0100 Message-ID: <1333536532_232842@CP5-2952> References: <1333519380-6756-1-git-send-email-ben@bwidawsk.net> <1333519380-6756-3-git-send-email-ben@bwidawsk.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from fireflyinternet.com (smtp.fireflyinternet.com [109.228.6.236]) by gabe.freedesktop.org (Postfix) with ESMTP id 872649EBBC for ; Wed, 4 Apr 2012 03:49:00 -0700 (PDT) In-Reply-To: <1333519380-6756-3-git-send-email-ben@bwidawsk.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org Cc: Ben Widawsky , Ben Widawsky List-Id: intel-gfx@lists.freedesktop.org On Tue, 3 Apr 2012 23:02:59 -0700, Ben Widawsky wrote: > +[[ `echo 1 | sudo tee ${i915_path}/i915_wedged` ]] || die "Couldn't write to ${i915_path}/i915_wedged" echo 1 | sudo tee $(i915_path)/i915_wedged || die ... > +cat $i915_path/i915_error_state > /dev/null 2>&1 cat $(i915_path)/i915_error_state > /dev/null 2>&1 || die ... Can we check for gen >= 6 before killing the GPU in an automated test? Or do we recommend reseting the GPU if i915_wedged remains set? -Chris -- Chris Wilson, Intel Open Source Technology Centre