From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: display problems since: drm/i915/dp: workaround BIOS eDP bpp clamping issue
Date: Fri, 01 Nov 2013 18:04:24 -0300 [thread overview]
Message-ID: <52741758.5020809@opensuse.org> (raw)
In-Reply-To: <CAKMK7uHy35pcrFv9jMrMzUMupg0Gg-tPEkQH_X487ip_rTNa=w@mail.gmail.com>
El 01/11/13 17:20, Daniel Vetter escribió:
> Ok, gpu hang. Unfortunately this particular kernel doesn't bother to
> dump the hang state in this case, so can you please test with the
> latest drm-intel-nightly branch from
>
> http://cgit.freedesktop.org/~danvet/drm-intel/
>
> Dmesg should politely tell you to grab a file from sysfs once the gpu
> ring is stuck again, please attach that.
>
> Thanks, Daniel
>
OK, I merged drm-intel-nightly and the GPU no longer hangs, there is no
error in the logs, used it for a around 10/15 minutes with no issue,
previously it was just a matter of opening chromium with a youtube video
to get the hang 100% of the time.
--
"Judging by their response, the meanest thing you can do to people on
the Internet is to give them really good software for free". - Anil Dash
next prev parent reply other threads:[~2013-11-01 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5273D6EA.7040905@opensuse.org>
2013-11-01 18:45 ` display problems since: drm/i915/dp: workaround BIOS eDP bpp clamping issue Daniel Vetter
2013-11-01 20:02 ` Cristian Rodríguez
2013-11-01 20:20 ` Daniel Vetter
2013-11-01 21:04 ` Cristian Rodríguez [this message]
2013-11-01 22:18 ` Daniel Vetter
2013-11-01 23:03 ` Cristian Rodríguez
2013-11-04 15:30 ` Cristian Rodríguez
2013-11-04 18:30 ` Cristian Rodríguez
2013-11-04 18:40 ` Daniel Vetter
2013-11-04 18:54 ` Cristian Rodríguez
2013-11-04 19:32 ` Cristian Rodríguez
2013-11-04 20:08 ` Ville Syrjälä
2013-11-05 7:59 ` Jani Nikula
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=52741758.5020809@opensuse.org \
--to=crrodriguez@opensuse.org \
--cc=daniel@ffwll.ch \
--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.