All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60560] New: Kernel BUG/Oops during radeon gpu stall
Date: Tue, 16 Jul 2013 08:21:57 +0000	[thread overview]
Message-ID: <bug-60560-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=60560

            Bug ID: 60560
           Summary: Kernel BUG/Oops during radeon gpu stall
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.10
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: knut.tidemann@gmail.com
        Regression: No

Created attachment 106893
  --> https://bugzilla.kernel.org/attachment.cgi?id=106893&action=edit
dmesg output

I've noticed a kernel BUG/Oops during a GPU stall when playing Legend of
Grimrock (closed source).

The oops causes X to become a defunct process with no entires in the Xorg.log
file. The screen goes into standby mode and the only way to solve this is to
reboot the computer. The machine is responsive via ssh and I've attached my
dmesg output after the oops.

I have not played this game with another kernel, so I don't know if it's new or
not.

I have a Radeon HD 4850, on an Intel Core2Duo with 8GB of ram.

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

             reply	other threads:[~2013-07-16  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-16  8:21 bugzilla-daemon [this message]
2013-07-16 13:07 ` [Bug 60560] Kernel BUG/Oops during radeon gpu stall bugzilla-daemon
2013-07-16 13:08 ` 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-60560-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.