All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59592] New: Reproducable GPU lockups since 3.8
Date: Sat, 19 Jan 2013 18:31:55 +0000	[thread overview]
Message-ID: <bug-59592-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1734 bytes --]

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

          Priority: medium
            Bug ID: 59592
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Reproducable GPU lockups since 3.8
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: nine@detonation.org
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 73293
  --> https://bugs.freedesktop.org/attachment.cgi?id=73293&action=edit
dmesg after lockups

Since upgrading my kernel to 3.8.0-rc3 using openSUSE packages, I reproducably
get GPU lockups when running FlightGear right after the simulation starts.
Takes a couple of minutes with some screen blanking to quit the application
again. Afterwards the system continues running fine. Activating KDE's desktop
effects may produce the same behaviour.

I'm using the following versions:
Mesa-9.1_git20130117-230.1.x86_64
libdrm2-2.4.99_git20130117-1.1.x86_64

X.Org X Server 1.12.3
Release Date: 2012-07-09
[    17.264] X Protocol Version 11, Revision 0
[    17.264] Build Operating System: openSUSE SUSE LINUX
[    17.264] Current Operating System: Linux sphinx 3.8.0-rc3-1-desktop #1 SMP
PREEMPT Thu Jan 10 20:49:22 UTC 2013 (7ce28dd) x86_64
[    17.264] Kernel command line: BOOT_IMAGE=/vmlinuz-3.8.0-rc3-1-desktop
root=/dev/mapper/system-root resume=/dev/system/swap quiet splash=silent
[    17.264] Build Date: 08 January 2013  11:56:04AM


I could do some git bisecting on the kernel or on Mesa if it helps and I'm
fluent in C. Just tell me how I can help fixing this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3153 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-01-19 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-19 18:31 bugzilla-daemon [this message]
2013-01-20 18:46 ` [Bug 59592] Radeon HD 5670: reproducable GPU lockups since kernel 3.8 bugzilla-daemon
2013-01-21 17:28 ` bugzilla-daemon
2013-01-21 21:27 ` bugzilla-daemon
2013-01-24 22:03 ` bugzilla-daemon
2013-01-24 22:14 ` [Bug 59592] Radeon HD 5670: reproducable GPU lockups with htile enabled bugzilla-daemon
2013-02-08  2:10 ` bugzilla-daemon
2013-02-12 18:57 ` bugzilla-daemon
2013-02-12 22:05 ` bugzilla-daemon
2013-02-13  1:09 ` bugzilla-daemon
2013-03-02  7:00 ` bugzilla-daemon
2013-04-24 19:23 ` bugzilla-daemon
2013-04-30 20:03 ` bugzilla-daemon
2013-05-06 14:47 ` 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-59592-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.