From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Ben Widawsky <ben@bwidawsk.net>,
intel-gfx@lists.freedesktop.org,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH 2/2] tests: wedged + error_state read test
Date: Wed, 4 Apr 2012 13:09:24 +0200 [thread overview]
Message-ID: <20120404110924.GB4069@phenom.ffwll.local> (raw)
In-Reply-To: <1333536532_232842@CP5-2952>
On Wed, Apr 04, 2012 at 11:48:22AM +0100, Chris Wilson wrote:
> On Tue, 3 Apr 2012 23:02:59 -0700, Ben Widawsky <ben@bwidawsk.net> 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?
I've ditched this from the automated test list, fixed up the root
confusion (make test would already check for that), and fixed the bash
sourcing to also work when pwd != i-g-t/tests.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-04-04 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 6:02 [PATCH 0/3]: test case + fix for debugfs regression Ben Widawsky
2012-04-04 6:02 ` [PATCH 1/2] tests: use common code for scripts Ben Widawsky
2012-04-04 6:02 ` [PATCH 2/2] tests: wedged + error_state read test Ben Widawsky
2012-04-04 10:48 ` Chris Wilson
2012-04-04 11:09 ` Daniel Vetter [this message]
2012-04-04 6:03 ` [PATCH] drm/i915: VCS is not the last ring Ben Widawsky
2012-04-04 10:44 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120404110924.GB4069@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox