From: Cyril Brulebois <kibi@debian.org>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Sandy Bridge X crash - OpenGL/DPMS-related?
Date: Sun, 27 Mar 2011 05:42:42 +0200 [thread overview]
Message-ID: <20110327034242.GS12056@debian.org> (raw)
In-Reply-To: <imlf3o$o35$1@dough.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 919 bytes --]
Hi,
Ian Pilcher <arequipeno@gmail.com> (26/03/2011):
> Fedora 15 Alpha on a brand new Sandy Bridge system (Core i7 2600
> with "Intel HD" graphics). Running KDE and using GLMatrix
> screensaver.
Fedora might have a better doc but…
> (I have installed the relevant debuginfo packages and reproduced the
> crash, but the backtrace in the X.org log doesn't appear to be using
> those symbols. Any way I can get a more useful backtrace?)
(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
You may want to post kernel logs (see dmesg), and mention your kernel
and X versions (unless everyone else knows what Fedora 15α ships).
KiBi.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-03-27 3:42 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 [this message]
2011-03-27 14:23 ` Ian Pilcher
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=20110327034242.GS12056@debian.org \
--to=kibi@debian.org \
--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.