| 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 [details]
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.
Please attach your full dmesg from boot, xorg log, and lspci -nn output.
Created attachment 114228 [details]
dmesg, ends when login prompt appears (non-graphical)
Created attachment 114265 [details]
Another crash, this time with running 4.0.0 kernel, which also gave me a trace.
| What | Removed | Added |
|---|---|---|
| Priority | medium | high |
| Severity | normal | critical |
Created attachment 114503 [details]
Same crash, this time with 3.19.2-1 kernel. Notice the mention of i915
I just downgraded, PRIME worked flawlessly up until 3.19, I was able to test up until 3.17.6-1 since the next one after that was the latest kernel in the [testing] repo aka 3.19.2-1
(In reply to Rafael Ristovski from comment #7) > I just downgraded, PRIME worked flawlessly up un= til 3.19, I was able to test > up until 3.17.6-1 since the next one after that was the latest kernel = in the > [testing] repo aka 3.19.2-1 Can you narrow it down further, ideally bisect?
(In reply to Michel D=C3=A4nzer from comment #8) > (In reply to Rafael Ristovski from comment #7) > > I just downgraded, PRIME worked flawlessly up until 3.19, I was a= ble to test > > up until 3.17.6-1 since the next one after that was the latest ke= rnel in the > > [testing] repo aka 3.19.2-1 >=20 > Can you narrow it down further, ideally bisect? I guess I could try, but not in the near future as I lack free time. Will report back once done or when any progress is made.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/593.