From: Ivan Bulatovic <combuster@gmx.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Revert i915.semaphore=1 default from 47ae63e0
Date: Tue, 24 May 2011 22:05:56 +0200 [thread overview]
Message-ID: <20110524220556.3003a0be@gmx.com> (raw)
In-Reply-To: <BANLkTim6hVTes8GJiPm4rZVxu4fy1L5CCA@mail.gmail.com>
On Tue, 24 May 2011 13:10:27 -0400
Andrew Lutomirski <luto@mit.edu> wrote:
> On Thu, May 19, 2011 at 4:50 PM, Andrew Lutomirski <luto@mit.edu>
> wrote:
> > On Thu, May 19, 2011 at 3:56 PM, Keith Packard <keithp@keithp.com>
> > wrote:
> >> On Fri, 13 May 2011 12:14:54 -0400, Andy Lutomirski <luto@MIT.EDU>
> >> wrote:
> >>
> >>> My Q67 / i7-2600 box has rev09 Sandy Bridge graphics. It hangs
> >>> instantly when GNOME loads and it hangs so hard the reset button
> >>> doesn't work. Setting i915.semaphore=0 fixes it.
> >>
> >> Can you describe precisely what hardware you have? The make and
> >> model of the motherboard and the exact model of CPU? I'd like to
> >> get this issue resolved for 2.6.40 and need to have a reliable way
> >> to reproduce the hang; replicating your hardware may be a good way
> >> of doing that.
> >
>
> I'm getting hangs on my X220 Core i7 laptop as well with 2.6.39 and
> i915.semaphores=1. They're not as reliable -- sometimes the system
> hangs on log in, sometimes after a few seconds, and sometimes it
> doesn't hang.
>
> --Andy
I haven't had GPU hangs since this patch:
https://bugs.freedesktop.org/show_bug.cgi?id=33921#c23
Poll the FIFO for free entries before writing the register
Gigabyte GA-H67MA-UD2H-B3 + i5 2400 here.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-05-24 20:12 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 [this message]
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
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=20110524220556.3003a0be@gmx.com \
--to=combuster@gmx.com \
--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 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).