From: Ben Widawsky <ben@bwidawsk.net>
To: Oscar Dario Trujillo Tejada <oscardt19@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Intel Crash
Date: Mon, 15 Jul 2013 21:17:20 -0700 [thread overview]
Message-ID: <20130715211720.00006639@unknown> (raw)
In-Reply-To: <CA+kWBoL79O_BwnnGgRTMdR-akL7D63SYWEuDKL78gjbQ85+Y+Q@mail.gmail.com>
On Mon, 15 Jul 2013 21:59:09 -0600
Oscar Dario Trujillo Tejada <oscardt19@gmail.com> wrote:
> Sorry about this but, I dont know a better place to send it
> please read the bug report that I put in archlinux bug tracker
>
> https://bugs.archlinux.org/task/36155?project=1&cat%5B0%5D=10&string=xf86-video-intel
>
I am far from equipped to debug ddx problems without debug symbols,
though Chris can probably make something of it when he wakes up.
Generally you should file bugs on bugs.freedesktop.org - with more or
less what you included.
See:
https://01.org/linuxgraphics/documentation/how-report-bugs-0
I will say that if it is indeed cpuid related - I am going to have a
good, long, laugh. But from the CompositePicture in the bt, I assume
it's unlikely.
next prev parent reply other threads:[~2013-07-16 4:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 3:59 Intel Crash Oscar Dario Trujillo Tejada
2013-07-16 4:17 ` Ben Widawsky [this message]
2013-07-16 4:23 ` Oscar Dario Trujillo Tejada
2013-07-16 8:17 ` Chris Wilson
2013-07-16 14:13 ` Oscar Dario Trujillo Tejada
2013-07-16 14:31 ` Chris Wilson
2013-07-16 15:58 ` Oscar Dario Trujillo Tejada
2013-07-16 16:55 ` Chris Wilson
2013-07-17 3:51 ` Oscar Dario Trujillo Tejada
2013-07-17 9:41 ` Chris Wilson
2013-07-17 17:53 ` Oscar Dario Trujillo Tejada
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=20130715211720.00006639@unknown \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=oscardt19@gmail.com \
/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.