From: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Pageflip failure on SNB devices running 3.13.3
Date: Tue, 25 Feb 2014 17:13:55 +0000 [thread overview]
Message-ID: <4176777.J3KWrgyv88@f19simon> (raw)
In-Reply-To: <20140225165259.GA3815@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
On Tuesday 25 February 2014 16:52:59 Chris Wilson wrote:
> On Tue, Feb 25, 2014 at 02:52:00PM +0000, Simon Farnsworth wrote:
> > I've put a dmesg from a failed system at http://90.155.96.198/sfarnsworth/flip-fail.txt - it's 11.3MB, so can't be attached. I've spotted the MCH_SSKPD
> > message, but I also get the failures on systems that don't output that
> > message.
> >
> > Any ideas? Or should I file a bug?
>
> Let's capture as much as possible in a bug. Can you try the stall
> detection w/a (if it is not already enabled)?
> -Chris
>
Filed as https://bugs.freedesktop.org/show_bug.cgi?id=75502
I'm not sure what you mean by "stall detection w/a"; I've not deliberately
disabled anything, so it should be in its default state. We can follow
through on the bug if there's something I need to turn on, though.
--
Simon Farnsworth
Software Engineer
ONELAN Ltd
http://www.onelan.com
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-02-25 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 14:52 Pageflip failure on SNB devices running 3.13.3 Simon Farnsworth
2014-02-25 16:52 ` Chris Wilson
2014-02-25 17:13 ` Simon Farnsworth [this message]
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=4176777.J3KWrgyv88@f19simon \
--to=simon.farnsworth@onelan.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.