All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pilcher <arequipeno@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Sandy Bridge X crash - OpenGL/DPMS-related?
Date: Sun, 27 Mar 2011 09:23:29 -0500	[thread overview]
Message-ID: <imnh91$enr$1@dough.gmane.org> (raw)
In-Reply-To: <20110327034242.GS12056@debian.org>

On 03/26/2011 10:42 PM, Cyril Brulebois wrote:
> (see man 3 backtrace, which is used within X) the easiest way is to
> get X to dump a core, or to attach it from gdb (possibly from another
> machine); here's the doc I'm pointing Debian users to, instructions
> there should be quite portable across distros:
>   http://pkg-xorg.alioth.debian.org/howto/use-gdb.html

I will take a look at this.

> You may want to post kernel logs (see dmesg), and mention your kernel
> and X versions (unless everyone else knows what Fedora 15α ships).

Most of the gory details can be found at:

    https://bugzilla.redhat.com/show_bug.cgi?id=691084

Software versions are:

    xorg-x11-server-common-1.10.0-4.fc15.x86_64
    xorg-x11-server-Xorg-1.10.0-4.fc15.x86_64
    xorg-x11-drv-intel-2.14.0-4.fc15.x86_64
    mesa-dri-drivers-7.10.1-1.fc15.x86_64

Thanks!

-- 
========================================================================
Ian Pilcher                                         arequipeno@gmail.com
"If you're going to shift my paradigm ... at least buy me dinner first."
========================================================================

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2011-03-27 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 19:34 Sandy Bridge X crash - OpenGL/DPMS-related? Ian Pilcher
2011-03-27  3:42 ` Cyril Brulebois
2011-03-27 14:23   ` Ian Pilcher [this message]
2011-03-27 15:39     ` Ian Pilcher
2011-03-27 16:18       ` Ian Pilcher
2011-03-27 11:13 ` Ivan Bulatovic
2011-03-27 14:18   ` Ian Pilcher

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='imnh91$enr$1@dough.gmane.org' \
    --to=arequipeno@gmail.com \
    --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.