From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tarkan Erimer <tarkan.erimer@f-secure.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6
Date: Mon, 19 Sep 2011 11:10:35 +0100 [thread overview]
Message-ID: <aefc95$1fgrb6@orsmga001.jf.intel.com> (raw)
In-Reply-To: <4E770FF5.8030207@f-secure.com>
On Mon, 19 Sep 2011 12:48:37 +0300, Tarkan Erimer <tarkan.erimer@f-secure.com> wrote:
> Hi,
>
> I'm having constant X crashes (Almost every 30 mins.) on Intel Graphics.
> Below is the error message after X crashes :
>
> [ 113.264775] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
Sigh. A debugging message left at DRM_ERROR.
> [ 113.265289] [drm] Changing LVDS panel from (-hsync, -vsync) to
> (+hsync, -vsync)
This is just an info message as a few kernel releases ago we started
honouring LVDS sync from the EDID and so we wanted to make sure that no
regressions correlated with actually doing as we were told.
> [ 114.141640] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
> [ 4955.770011] [drm:intel_disable_transcoder] *ERROR* failed to disable
> transcoder
This is one the true error in the midst of this spew.
Aside from the one modesetting error, these messages are all secondary
to the crash (and are really just debugging spew whilst switching
modes from X to console, console to X). Can you please attach the
Xorg.log containing the crash? Or maybe gdm.log etc? Also what happens
regularly every 30minutes; a particular screensaver or dpms?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-19 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 9:48 [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6 Tarkan Erimer
2011-09-19 10:10 ` Chris Wilson [this message]
2011-09-19 13:06 ` Tarkan Erimer
2011-09-19 13:33 ` Chris Wilson
2011-09-20 6:02 ` Tarkan Erimer
2011-09-20 7:34 ` Chris Wilson
2011-09-20 7:55 ` Tarkan Erimer
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='aefc95$1fgrb6@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkan.erimer@f-secure.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 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.