All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 45366] New: Radeon gpu lockups
Date: Sun, 29 Jan 2012 12:27:35 +0000	[thread overview]
Message-ID: <bug-45366-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=45366

             Bug #: 45366
           Summary: Radeon gpu lockups
    Classification: Unclassified
           Product: DRI
           Version: XOrg CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: ernstp@gmail.com


Created attachment 56286
  --> https://bugs.freedesktop.org/attachment.cgi?id=56286
GPU locksups log

I'm getting gpu lockups every now and then. More likely during with heavy
OpenGL usage, but Compiz is enough sometimes. I can switch to console and kill
the application and usually get a functioning system back.
Setup:
Intel Core i5 2500k
Radeon 6850
Ubuntu 11.10
Kernel: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
3D stack from xorg-edgers ppa

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-01-29 12:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 12:27 bugzilla-daemon [this message]
2012-02-20 16:06 ` [Bug 45366] Radeon gpu lockups bugzilla-daemon
2012-02-20 16:24 ` bugzilla-daemon
2012-02-20 16:25 ` bugzilla-daemon
2012-02-24 18:17 ` bugzilla-daemon
2012-03-17 10:39 ` bugzilla-daemon
2012-03-23 20:43 ` bugzilla-daemon
2012-04-08  5:05 ` bugzilla-daemon
2012-04-11 16:56 ` bugzilla-daemon
2012-05-14 16:49 ` 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-45366-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.