linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tarkan Erimer <tarkan.erimer@f-secure.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6
Date: Mon, 19 Sep 2011 12:48:37 +0300	[thread overview]
Message-ID: <4E770FF5.8030207@f-secure.com> (raw)

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
[  113.265289] [drm] Changing LVDS panel from (-hsync, -vsync) to 
(+hsync, -vsync)
[  114.141640] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 4955.770011] [drm:intel_disable_transcoder] *ERROR* failed to disable 
transcoder
[ 4955.777420] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 4955.938453] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 5255.360508] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 5255.527867] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 5744.182746] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 5744.349049] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8536.532605] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8536.533128] [drm] Changing LVDS panel from (+hsync, -vsync) to 
(-hsync, -vsync)
[ 8536.835206] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8605.034788] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8605.035302] [drm] Changing LVDS panel from (-hsync, -vsync) to 
(+hsync, -vsync)
[ 8606.110388] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8869.586751] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8869.587264] [drm] Changing LVDS panel from (+hsync, -vsync) to 
(-hsync, -vsync)
[ 8869.906322] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8950.401958] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
[ 8950.402472] [drm] Changing LVDS panel from (-hsync, -vsync) to 
(+hsync, -vsync)
[ 8951.066084] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH


Here is VGA info from lspci :

linux-ou2v:~ # lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)

And it's Xserver v1.11 and Intel Driver 2.16 with 
Kernel-3.1.0-rc6-2-desktop (opensuse). Also, this behavior happens from 
Linux-3.1-rc4 to rc6. At least these are the versions that I tried as 
3.1. Linux-3.0.x runs fine with same configuration.





-- 
Tarkan Erimer
IT Service Deployment / 3rd Level Support / Snr. Linux Engineer


             reply	other threads:[~2011-09-19  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19  9:48 Tarkan Erimer [this message]
2011-09-19 10:10 ` [BUG] i915 crashes X Server Constantly on Linux-3.1-rc4 to .rc6 Chris Wilson
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=4E770FF5.8030207@f-secure.com \
    --to=tarkan.erimer@f-secure.com \
    --cc=linux-kernel@vger.kernel.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 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).