From: Alexey Fisher <bug-track@fisher-privat.net>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: gpu freeze
Date: Sat, 30 Oct 2010 20:22:31 +0200 [thread overview]
Message-ID: <1288462951.5285.7.camel@zwerg> (raw)
What info should i collect if i get GPU hung?
I currently get one, with kernel 2.6.36-07532-gbbe2e11
it happened after i started video. Interesting is my PC worked 15 hours,
many things was done it was not first video. So fear i can't reproduce
or bisect it. This is first hung for some weeks or months...
--
Regards,
Alexey
next reply other threads:[~2010-10-30 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 18:22 Alexey Fisher [this message]
2010-10-30 19:09 ` gpu freeze Peter Clifton
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=1288462951.5285.7.camel@zwerg \
--to=bug-track@fisher-privat.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox