From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30227] New: Radom X.org freeze by a GPU lockup
Date: Thu, 16 Sep 2010 05:56:48 -0700 (PDT) [thread overview]
Message-ID: <bug-30227-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=30227
Summary: Radom X.org freeze by a GPU lockup
Product: DRI
Version: XOrg CVS
Platform: PowerPC
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: kronat@tiscali.it
Created an attachment (id=38743)
--> (https://bugs.freedesktop.org/attachment.cgi?id=38743)
dmesg after the fail
Apparently random GPU lockup (ati r300), with X.org freeze.
It happens more frequently if I compile and I switch over many applications
(firefox, terminal, opera). Attached there is the dmesg after the fail (I could
continue to work on others console - ctrl+alt+f1,2,3..).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-09-16 12:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 12:56 bugzilla-daemon [this message]
2010-09-16 12:59 ` [Bug 30227] Radom X.org freeze by a GPU lockup bugzilla-daemon
2010-09-16 13:17 ` bugzilla-daemon
2010-09-16 15:38 ` bugzilla-daemon
2010-09-16 15:38 ` bugzilla-daemon
2010-09-16 15:42 ` bugzilla-daemon
2010-09-16 19:00 ` bugzilla-daemon
2010-09-17 10:11 ` bugzilla-daemon
2010-09-18 10:59 ` bugzilla-daemon
2010-09-18 11:01 ` bugzilla-daemon
2010-09-18 11:12 ` bugzilla-daemon
2011-02-09 16:08 ` [Bug 30227] [RADEON:KMS:AGP:R300:PPC] random X " bugzilla-daemon
2011-03-24 17:03 ` bugzilla-daemon
2011-12-10 17:24 ` bugzilla-daemon
2011-12-15 18:12 ` bugzilla-daemon
2012-01-06 18:37 ` bugzilla-daemon
2019-11-19 8:15 ` bugzilla-daemon
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=bug-30227-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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.