| Bug ID | 99316 |
|---|---|
| Summary | Radeon crash when laptop on AC power |
| Product | DRI |
| Version | unspecified |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | major |
| Priority | medium |
| Component | DRM/Radeon |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | LordSamanon@gmail.com |
Created attachment=
128807 [details]
AC Power Unigine Heaven dmesg
I have a Dell laptop with an Intel iGPU and a Radeon dGPU (a Firepro W5130M,
recognized as a Radeon HD 8830M by lspci).
Whenever I attempt to use the Radeon card via DRI_PRIME=3D1 while the lapto=
p is
plugged in, the card crashes. When on battery the card performs fine.
One way I have tested this is with glxgears. Often glxgears will work the f=
irst
time it is run, but if it is closed and then opened a few seconds later, it
will crash.
I have also tried running programs like Portal 2 and Unigine Heaven. These
always hang. Unfortunately the error messages produced in dmesg are not the
most consistent. Sometimes I get a backtrace, sometimes even a kernel panic=
on
reboot.
I'll post the various logs I have. One thing I have found is that glxgears =
does
not crash if I use radeon.runpm=3D0, however it still hangs when running
something like Portal.
| What | Removed | Added |
|---|---|---|
| CC | LordSamanon@gmail.com |
Created attachment 12880=
8 [details]
AC Power Portal 2 dmesg
Created attachment 128809 =
[details]
AC Power glxgears
The last part of the log, 121 onward is the second failed attempt for glxge=
ars.
The previous part 94-96 is a successful glxgears attempt seconds earlier. T=
hese
logs are the only thing that have been consistent from my tests.
Possibly a duplicate of bug 98897. Does <= a href=3D"attachment.cgi?id=3D128780" name=3D"attach_128780" title=3D"fix">= attachment 128780 [details] [review] fix the issue?
Created attachment 128812 =
[details]
kernel panic
I get these sometimes when I reboot after testing the card. Usually after
testing it with something like Portal or Unigine Heaven. It doesn't always
happen.
Sorry it's a picture, I haven't been able to get kdump to work, though if
necessary I'll give it another try.
It's been a while, but this is still happening. I've moved dis= tro by now (Fedora 26) but I'm getting the exact same error. Though it's nearly identi= cal, I'll upload a new log generated by journalctl -b --no-pager | egrep 'radeon|drm|kernel' >> radeon_crash
| What | Removed | Added |
|---|---|---|
| Attachment #128807 is obsolete | 1 | |
| Attachment #128808 is obsolete | 1 | |
| Attachment #128809 is obsolete | 1 | |
| Attachment #128812 is obsolete | 1 |
Created attachment 132833 =
[details]
Crash on AC Power
Generated by journalctl -b --no-pager | egrep 'radeon|drm|kernel' >>
radeon_crash
after running DRI_PRIME=3D1 vblank_mode=3D0 glxgears
To clarify, since it has been a while, the radeon card crashes= when the laptop is plugged in, but not when it's unplugged. It has been like this as long a= s I have had it (since July 2016)
I have also a Dell notebook with the same dGPU, but cannot rep= roduce your error with Ubuntu 16.04 kernel 4.10.0. Instead I have the problem, that the dGPU only gets powered at a low freque= ncy, and becomes slower than the Intel GPU by doing so.=20 When I run glmark2, I look at "/sys/kernel/debug/dri/0/radeon_pm_info&= quot; and always see the following output: default engine clock: 925000 kHz current engine clock: 299990 kHz default memory clock: 1000000 kHz current memory clock: 148990 kHz voltage: 1225 mV PCIE lanes: 16 Btw.: This dGPU cannot be connected to a CRT directly, as there seems to be= no connection available at all.
| What | Removed | Added |
|---|---|---|
| Priority | medium | high |
| CC | mat42x@yahoo.de |
(In reply to Mathias from comment #10) > I have also a Dell notebook with the same dGPU, = but cannot reproduce your > error with Ubuntu 16.04 kernel 4.10.0. >=20 > Instead I have the problem, that the dGPU only gets powered at a low > frequency, and becomes slower than the Intel GPU by doing so.=20 >=20 > When I run glmark2, I look at "/sys/kernel/debug/dri/0/radeon_pm_= info" and > always see the following output: >=20 > default engine clock: 925000 kHz > current engine clock: 299990 kHz > default memory clock: 1000000 kHz > current memory clock: 148990 kHz > voltage: 1225 mV > PCIE lanes: 16 >=20 > Btw.: This dGPU cannot be connected to a CRT directly, as there seems = to be > no connection available at all. Is the GPU at low power while plugged in, or always? glmark2 while plugged in instantly crashes for me, but on battery I get a s= core of 1395 which is horrible compared to the 3680 from my integrated card. Plus horrible rendering artifacts. But I'm not sure if that is really related to= my main problem. This is "/sys/kernel/debug/dri/0/radeon_pm_info" on battery with = glmark2 for me: uvd vclk: 0 dclk: 0 power level 2 sclk: 40000 mclk: 30000 vddc: 900 vddci: 0 pcie gen: 3 Oddly enough, a completely different format than yours. This card seems to have a multitude of problems
Created attachmen=
t 133178 [details]
Rendering artifacts on battery
Perhaps not entirely related, but these are rendering artifacts while on
battery with glmark2. Note the horizontal lines, this is the main issue, th=
at
and major stuttering. glxgears produces similar results.
Hi! As an owner of the same GPU, I can confirm this bug still appears under lin= ux 4.15.0-rc7. The card card crashes or hangs when used with DRI_PRIME=3D1. After seeing t= his report, I tried with the laptop plugged out and it surprisingly did work. It would be nice to have a solution as the w5130m isn't currently supported= by amdgpu either leaving it unusable under linux.
(In reply to l.hartmail from comment #13) > Hi! > As an owner of the same GPU, I can confirm this bug still appears under > linux 4.15.0-rc7. > The card card crashes or hangs when used with DRI_PRIME=3D1. After see= ing this > report, I tried with the laptop plugged out and it surprisingly did wo= rk. >=20 > It would be nice to have a solution as the w5130m isn't currently supp= orted > by amdgpu either leaving it unusable under linux. Glad to finally find someone else with the same issue! I was beginning to t= hink I was the only one.
| 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/767.