All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89536] GPU lockup and kernel OOPS when using PRIME
Date: Wed, 11 Mar 2015 16:44:26 +0000	[thread overview]
Message-ID: <bug-89536-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 89536
           Summary: GPU lockup and kernel OOPS when using PRIME
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: rafael.ristovski@gmail.com

Created attachment 114225
  --> https://bugs.freedesktop.org/attachment.cgi?id=114225&action=edit
Two of the kernel hangs, note one is an OOPS, while the other is not, I was
able to shut down the machine normally after the first OOPS as the kernel was
still responsive to power button events.

When running OpenGL applications with PRIME, the screen freezes and a kernel
OOPS is generated. This seems to happen either when the application starts, or
the window of the application is re-drawn (moving workspaces,
minimizing/maximizing) Crashes seem to be inconsistent as sometimes the kernel
just freezes and no OOPS is generated.

OS Details:
Archlinux with kernel 3.19.1-1
xorg-server 1.17.1-3
xf86-video-intel 2.99.917-4
xf86-video-ati 1:7.5.0-2
libdrm 2.4.59-1

Below is an attached kernel log with _TWO_ separate kernel hang, both caused by
running an OpenGL application with PRIME.

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

[-- Attachment #1.2: Type: text/html, Size: 3138 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:[~2015-03-11 16:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:44 bugzilla-daemon [this message]
2015-03-11 16:54 ` [Bug 89536] GPU lockup and kernel OOPS when using PRIME bugzilla-daemon
2015-03-11 17:02 ` bugzilla-daemon
2015-03-11 17:03 ` bugzilla-daemon
2015-03-11 17:04 ` bugzilla-daemon
2015-03-12 17:09 ` bugzilla-daemon
2015-03-14 18:58 ` bugzilla-daemon
2015-03-21 12:35 ` bugzilla-daemon
2015-03-21 13:24 ` bugzilla-daemon
2015-03-25  7:37 ` bugzilla-daemon
2015-03-25 13:54 ` bugzilla-daemon
2019-11-19  9:02 ` 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-89536-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.