[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <aefc95$1fgrb6@orsmga001.jf.intel.com>
Date: Mon, 19 Sep 2011 11:10:35 +0100
From: Chris Wilson <chris@...is-wilson.co.uk>
To: Tarkan Erimer <tarkan.erimer@...ecure.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6
On Mon, 19 Sep 2011 12:48:37 +0300, Tarkan Erimer <tarkan.erimer@...ecure.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists