All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tarkan Erimer <tarkan.erimer@f-secure.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "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 16:06:45 +0300	[thread overview]
Message-ID: <4E773E65.5040809@f-secure.com> (raw)
In-Reply-To: <aefc95$1fgrb6@orsmga001.jf.intel.com>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

On 09/19/2011 01:10 PM, Chris Wilson wrote:
> 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?

Hi Chris,

I did a bit more digging and found out that it mostly happens when 
trying to open some flash based sites on Firefox and Chromium. I've 
attached Xorg.log, but it seems like no errors related to these crashes. 
But kdm.log has some interesting error messages that may be useful. I've 
attached kdm.log as well.


Cheers,

Tarkan


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


[-- Attachment #2: Xorg.tar.xz --]
[-- Type: application/octet-stream, Size: 7192 bytes --]

[-- Attachment #3: kdm.tar.xz --]
[-- Type: application/octet-stream, Size: 3720 bytes --]

  reply	other threads:[~2011-09-19 13:06 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
2011-09-19 13:06   ` Tarkan Erimer [this message]
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=4E773E65.5040809@f-secure.com \
    --to=tarkan.erimer@f-secure.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.