From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Andrew Lutomirski <luto@mit.edu>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: kicking rings considered harmful
Date: Tue, 27 Sep 2011 11:57:49 +0200 [thread overview]
Message-ID: <CAKMK7uFvG+A8EDzf7Kk_PpDUSwhq7LfujJ5gSTSRgo_STmx9qg@mail.gmail.com> (raw)
In-Reply-To: <CAObL_7FCinDjX43-aDJYC7dsC-jCx1k1e3y+T5q11=i=Vnc7UA@mail.gmail.com>
On Mon, Sep 26, 2011 at 21:07, Andrew Lutomirski <luto@mit.edu> wrote:
> On Sep 26, 2011 9:00 PM, "Daniel Vetter" <daniel.vetter@ffwll.ch> wrote:
>>
>> Only do it in the hope of resurrecting the gpu. Disable when reset is
>> disabled because it seems to tremendously increases our changes to
>> actually capture an error_state before the system goes all belly-up.
>>
>> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> ---
>> Hi Andrew,
>>
>> Can you please apply this patch and boot your system with
>>
>
> Will do in a couple days. I'm several thousand miles from that computer
> right now :)
No problem. Something else to try: Are you by chance running with
DMAR/VT-d enabled? If so, please disable it (either in the BIOS or
with intel_iommu=off) and see whether that works around the semaphore
hangs.
Perhaps do this before trying out the patch, doesn't require a new kernel ;-)
Thanks a lot, Daniel
--
Daniel Vetter
daniel.vetter@ffwll.ch - +41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2011-09-27 9:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 5:38 [2.6.39 regression] hard lock when GNOME starts Andrew Lutomirski
2011-05-13 16:07 ` Andrew Lutomirski
2011-05-13 16:14 ` [PATCH] drm/i915: Revert i915.semaphore=1 default from 47ae63e0 Andy Lutomirski
2011-05-15 23:09 ` Keith Packard
2011-05-19 19:56 ` Keith Packard
2011-05-19 20:50 ` Andrew Lutomirski
2011-05-24 17:10 ` Andrew Lutomirski
2011-05-24 17:46 ` Keith Packard
2011-05-24 20:05 ` Ivan Bulatovic
2011-06-07 7:12 ` Eric Anholt
2011-06-10 14:06 ` Andrew Lutomirski
2011-08-22 16:53 ` Jesse Barnes
2011-08-31 18:24 ` Ben Widawsky
2011-08-31 18:30 ` Andrew Lutomirski
2011-08-31 19:07 ` Keith Packard
2011-08-31 19:37 ` Andrew Lutomirski
2011-09-26 17:59 ` [PATCH] drm/i915: kicking rings considered harmful Daniel Vetter
2011-09-26 19:07 ` Andrew Lutomirski
2011-09-27 9:57 ` Daniel Vetter [this message]
2011-09-27 5:22 ` Ben Widawsky
2011-09-27 10:03 ` Daniel Vetter
2011-09-27 16:46 ` Ben Widawsky
2011-09-27 17:31 ` Chris Wilson
2011-09-27 18:03 ` Daniel Vetter
2011-09-27 19:38 ` Ben Widawsky
2011-09-27 21:54 ` Chris Wilson
2011-09-28 1:34 ` Ben Widawsky
2011-09-28 8:47 ` Chris Wilson
2011-09-28 8:53 ` Daniel Vetter
2011-10-03 20:21 ` Andrew Lutomirski
2011-10-03 21:02 ` 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=CAKMK7uFvG+A8EDzf7Kk_PpDUSwhq7LfujJ5gSTSRgo_STmx9qg@mail.gmail.com \
--to=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luto@mit.edu \
/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.