From: Andrew Lutomirski <luto@mit.edu>
To: Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Revert i915.semaphore=1 default from 47ae63e0
Date: Wed, 31 Aug 2011 15:37:34 -0400 [thread overview]
Message-ID: <CAObL_7Hi+c2aEtEMzrMNnrQXfnUmNY_ZnP==xCd7egMoKBow_g@mail.gmail.com> (raw)
In-Reply-To: <yunmxepe6wl.fsf@aiko.keithp.com>
[-- Attachment #1.1: Type: text/plain, Size: 566 bytes --]
Yes. I suspect that, as soon as any 3D happens, the machine locks hard.
How does it even get into a state that makes the hardware reset button not
work?
On Aug 31, 2011 3:08 PM, "Keith Packard" <keithp@keithp.com> wrote:
> On Wed, 31 Aug 2011 14:30:00 -0400, Andrew Lutomirski <luto@mit.edu>
wrote:
>
>> Yes. On the latest -rc, the system still freezes hard when mutter starts
up
>> if I set i915.semaphores=1.
>
> Ok. You said that you were running compiz before and that failed, and
> are now running mutter and that fails also?
>
> --
> keith.packard@intel.com
[-- Attachment #1.2: Type: text/html, Size: 850 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
next prev parent reply other threads:[~2011-08-31 19:37 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 [this message]
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
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='CAObL_7Hi+c2aEtEMzrMNnrQXfnUmNY_ZnP==xCd7egMoKBow_g@mail.gmail.com' \
--to=luto@mit.edu \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
/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;
as well as URLs for NNTP newsgroup(s).