| Bug ID | 104064 |
|---|---|
| Summary | (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at drivers/gpu/drm/amd/= amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601 dm_suspend+0x4e/0x60 [amdgpu] |
| Product | DRI |
| Version | DRI git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | taijian@posteo.de |
Created attachment 135921<=
/a> [details]
relevant dmesg output
I am getting repeated gpu resets on 4.15-rc2 with my hybrid laptop
(i7-7700HQ/RX470) with amdgpu.dc=3D1 set on the command line. Something see=
ms to
be off with power management, as the dGPU does not fully power down, even w=
hen
not in use. dmesg attached, lspci follows.
Created attachment=
135922 [details]
relevant output of #lspci -vv
Created attac=
hment 137103 [details]
dmesg output without amdgpu.dc=3D1
I'm seemingly hitting this too, on 4.15. Note that I get it with or without
amdgpu.dc=3D1.
Might also be relevant that on 4.14 and earlier, I would get kernel oopsies=
on
resume from suspend, with a very similar dmesg output (oopsie would happen =
in
the same dm_suspend function and same stack trace, as far as I can recall).
While I don't have any saved dmesg's from that, I could boot an old kernel =
to
obtain one if it seems useful.
I have slightly different hardware (eg, Radeon RX 570), but it's also a hyb=
rid
laptop.
Probably also worth noting that as of 4.15, my laptop hangs wi= th a black screen on suspend/resume. Magic SysRq seems to be about the only thing the computer responds to if I close and then open the lid. It seems somewhat likely this= is related, due to my aforementioned kernel oopsies on resumes and the fact th= ey had very similar stack traces to these warnings. I'm not sure how to get any relevant logging output from these hangs though. Any suggestions?
We have a few new patches in our staging trees relating to sus= pend and driver unload. Would you be able to try amd-staging-drm-next or drm-next-4.17-wip from https://cgit.freedesktop.org/~agd5f/linux/?h=3Ddrm-next-4.17-wip and = see if the issue is fixed there?
I certainly wouldn't mind. I've never really done anything of the sort before however, so is there an = easy way for me to set it up? For reference, I'm on Ubuntu 17.10 and while I kno= w my way around git and compilers fairly well, I've never compiled or installed a custom kernel or kernel module before.
I'll give 4.17-wip a whirl, cloning and building right now.
Created attachment 13=
7643 [details]
snippet from make protocol
4.17-wip does not compile for me, see the attached error snippet.
(In reply to taijian from comment #7) > Created attachment 137643 [details] > snippet from make protocol >=20 > 4.17-wip does not compile for me, see the attached error snippet. Fixed.
| What | Removed | Added |
|---|---|---|
| Attachment #135921 is obsolete | 1 | |
| Attachment #137103 is obsolete | 1 | |
| Attachment #137643 is obsolete | 1 |
Created attachment 137646 [details]
dmesg with kernel amd-staging-4.17-wip-c6bcaec0aa3e
OK, so on boot everything seems fine and dandy, less error messages than
before.=20
However, please note the 213.xxx and 480.xxx marks: This is where I actually
use the dGPU (with DRI_PRIME=3D1 glxinfo). Something is clearly not right h=
ere...
Also, power consumption as per powertop has not improved over 4.15/16, the =
dGPU
clearly does not fully power down when not in use (~25W vs ~12W with amdgpu
blacklisted).
| What | Removed | Added |
|---|---|---|
| Attachment #137646 is obsolete | 1 |
Created attachment 137647 [details]
dmesg with kernel amd-staging-4.17-wip-c6bcaec0aa3e
accidentially uploaded the trunkated version... PEBKEC...
Addendum: What DOES work now without crashing the system is dy=
namically en- and
disabling the dGPU via
# echo "\\_SB.PCI0.PEG0.PEGP._{OFF|ON}" > /proc/acpi/call
So that is definitely progress!
(In reply to taijian from comment #11) > Addendum: What DOES work now without crashing th= e system is dynamically en- > and disabling the dGPU via >=20 > # echo "\\_SB.PCI0.PEG0.PEGP._{OFF|ON}" > /proc/acpi/call >=20 > So that is definitely progress! Are you messing with that while the driver is loaded? Doing so will cause problems because you're changing the hw state behind the driver's back.
(In reply to Alex Deucher from comment #12) > (In reply to taijian from comment #11) > > Addendum: What DOES work now without crashing the system is dynam= ically en- > > and disabling the dGPU via > >=20 > > # echo "\\_SB.PCI0.PEG0.PEGP._{OFF|ON}" > /proc/acpi= /call > >=20 > > So that is definitely progress! >=20 > Are you messing with that while the driver is loaded? Doing so will c= ause > problems because you're changing the hw state behind the driver's back= . Yeah, I know. The problem is that I cannot unload the driver, because modpr= obe always complains about it being in use. However, I found that with 4.17-wip= the system actually remains stable after disabling the hardware, as long as I d= on't try to use it - which was not the case before, where it would crash much faster. But seriously, what I'm doing is that I have two boot entries, one that blacklists amdgpu and does the acpi_call thingy and one that doesn't. So one for mobile usage, one for gaming. Would be nice, though, if I did not need = to reboot to switch between the two use cases...
Created attachment 137651
References:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id BCC4A6E7F8
for ; Tue, 27 Feb 2018 20:40:08 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1606335865==
Content-Type: multipart/alternative; boundary="15197640081.E411.1776"
Content-Transfer-Encoding: 7bit
--15197640081.E411.1776
Date: Tue, 27 Feb 2018 20:40:08 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #15 from taijian@posteo.de ---
(In reply to Alex Deucher from comment #14)
> Created attachment 137651 [details] [review]
> patch to test
>=20
> Can you try this patch and append amdgpu.force_atpx=3D1 to the kernel com=
mand
> line in grub? Does it help?
Nope. To be precise: After invoking 'DRI_PRIME=3D1 glxinfo', the system cra=
shed
before I was able to run dmesg (as in: the screen froze and it became
completely unresponsive). So that was not really an improvement. I'm gonna =
go
ahead and try the latest git head from that repo now, before I had only app=
lied
your patch on top of c6bcaec0aa3e.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15197640081.E411.1776
Date: Tue, 27 Feb 2018 20:40:08 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 15
on bug 10406=
4
from taijian@posteo.d=
e
(In reply to Alex Deucher from comment #14)
> Created attachment 1=
37651 [details] [review] [review]
> patch to test
>=20
> Can you try this patch and append amdgpu.force_atpx=3D1 to the kernel =
command
> line in grub? Does it help?
Nope. To be precise: After invoking 'DRI_PRIME=3D1 glxinfo', the system cra=
shed
before I was able to run dmesg (as in: the screen froze and it became
completely unresponsive). So that was not really an improvement. I'm gonna =
go
ahead and try the latest git head from that repo now, before I had only app=
lied
your patch on top of c6bcaec0aa3e.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15197640081.E411.1776--
--===============1606335865==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1606335865==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Tue, 27 Feb 2018 21:30:39 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id 67ED76E178
for ; Tue, 27 Feb 2018 21:30:39 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0282673707==
Content-Type: multipart/alternative; boundary="15197670390.a5c8F8.15288"
Content-Transfer-Encoding: 7bit
--15197670390.a5c8F8.15288
Date: Tue, 27 Feb 2018 21:30:39 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
taijian@posteo.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #137647|0 |1
is obsolete| |
--- Comment #16 from taijian@posteo.de ---
Created attachment 137668
--> https://bugs.freedesktop.org/attachment.cgi?id=3D137668&action=3Dedit
dmesg with kernel amd-staging-4.17-wip-d0d4f398ddc0
here is the new dmesg with all of todays patches applied (up to d0d4f398ddc=
0).=20
The usual (DRI_PRIME=3D1 glxinfo) happens at 66.xxx - and this time around,=
the
system did not crash!
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15197670390.a5c8F8.15288
Date: Tue, 27 Feb 2018 21:30:39 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
What
Removed
Added
Attachment #137647 is obsolete
1
Comme=
nt # 16
on bug 10406=
4
from taijian@posteo.d=
e
Created attachment 137668 [details]
dmesg with kernel amd-staging-4.17-wip-d0d4f398ddc0
here is the new dmesg with all of todays patches applied (up to d0d4f398ddc=
0).=20
The usual (DRI_PRIME=3D1 glxinfo) happens at 66.xxx - and this time around,=
the
system did not crash!
You are receiving this mail because:
- You are the assignee for the bug.
=
--15197670390.a5c8F8.15288--
--===============0282673707==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0282673707==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Tue, 27 Feb 2018 21:44:24 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id A419D6E82E
for ; Tue, 27 Feb 2018 21:44:24 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============2136624616==
Content-Type: multipart/alternative; boundary="15197678641.34Be.19654"
Content-Transfer-Encoding: 7bit
--15197678641.34Be.19654
Date: Tue, 27 Feb 2018 21:44:24 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #17 from taijian@posteo.de ---
And that was premature... The second invocation of DRI_PRIME=3D1 does crash=
the
system (as in: total freeze, nothing doing except for hard reboot).=20
The system starts up OK, power consumption is way down compared to before
(~11W), DRI_PRIME=3D1 glxinfo triggers the dGPU to on, then it turns off ag=
ain.
Everything fine so far. But the second invocation causes the system to die,=
and
this is consistent over several attempts now. So we are making progress, but
are not quite there yet...
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15197678641.34Be.19654
Date: Tue, 27 Feb 2018 21:44:24 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 17
on bug 10406=
4
from taijian@posteo.d=
e
And that was premature... The second invocation of DRI_PRIME=
=3D1 does crash the
system (as in: total freeze, nothing doing except for hard reboot).=20
The system starts up OK, power consumption is way down compared to before
(~11W), DRI_PRIME=3D1 glxinfo triggers the dGPU to on, then it turns off ag=
ain.
Everything fine so far. But the second invocation causes the system to die,=
and
this is consistent over several attempts now. So we are making progress, but
are not quite there yet...
You are receiving this mail because:
- You are the assignee for the bug.
=
--15197678641.34Be.19654--
--===============2136624616==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============2136624616==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Mar 2018 13:13:29 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id D5FDE6EC5C
for ; Thu, 1 Mar 2018 13:13:28 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1099115671==
Content-Type: multipart/alternative; boundary="15199100081.A0f3B1c0.32645"
Content-Transfer-Encoding: 7bit
--15199100081.A0f3B1c0.32645
Date: Thu, 1 Mar 2018 13:13:28 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #18 from taijian@posteo.de ---
Adding to the above comment after some further testing:
I rebuild earlier today with HEAD at c2637e788da7. Startup went well, error
messages were as before. I then launched Steam, which seemed to power up the
dGPU for a short time, before it turned off again. So far, so good.
I the started a gaming session, using the dGPU. Performance was about even =
with
4.16rc3 without dc. There were some artifacts/stuttering when scrolling, bu=
t I
read on Phoronix that dc likely works best with mesa 18.0/LLVM6, which are=
not
out yet. So nothing really worrying.
However, when I quit the game and wanted to do another dmesg dump to look at
and upload here, the computer froze again and became completely unresponsive
before I could get to that. So it seems that the problem is not with the dG=
PU
powering up for the second time, but with it powering down for the second t=
ime
in a session.
Any ideas why that might be or what kinds of test I could do to help narrow
this down?
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15199100081.A0f3B1c0.32645
Date: Thu, 1 Mar 2018 13:13:28 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 18
on bug 10406=
4
from taijian@posteo.d=
e
Adding to the above comment after some further testing:
I rebuild earlier today with HEAD at c2637e788da7. Startup went well, error
messages were as before. I then launched Steam, which seemed to power up the
dGPU for a short time, before it turned off again. So far, so good.
I the started a gaming session, using the dGPU. Performance was about even =
with
4.16rc3 without dc. There were some artifacts/stuttering when scrolling, bu=
t I
read on Phoronix that dc likely works best with mesa 18.0/LLVM6, which are=
not
out yet. So nothing really worrying.
However, when I quit the game and wanted to do another dmesg dump to look at
and upload here, the computer froze again and became completely unresponsive
before I could get to that. So it seems that the problem is not with the dG=
PU
powering up for the second time, but with it powering down for the second t=
ime
in a session.
Any ideas why that might be or what kinds of test I could do to help narrow
this down?
You are receiving this mail because:
- You are the assignee for the bug.
=
--15199100081.A0f3B1c0.32645--
--===============1099115671==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1099115671==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Mar 2018 14:44:51 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id B46E96ECAD
for ; Thu, 1 Mar 2018 14:44:51 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1624860796==
Content-Type: multipart/alternative; boundary="15199154914.F5defCEa.26367"
Content-Transfer-Encoding: 7bit
--15199154914.F5defCEa.26367
Date: Thu, 1 Mar 2018 14:44:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #19 from Alex Deucher ---
were you using the patch and module option from comment 14?
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15199154914.F5defCEa.26367
Date: Thu, 1 Mar 2018 14:44:51 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 19
on bug 10406=
4
from Alex Deucher
were you using the patch and module option from comment 14?
You are receiving this mail because:
- You are the assignee for the bug.
=
--15199154914.F5defCEa.26367--
--===============1624860796==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1624860796==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Mar 2018 16:11:44 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id 60EF36ECE9
for ; Thu, 1 Mar 2018 16:11:44 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0175658364==
Content-Type: multipart/alternative; boundary="15199207040.4D75969.17798"
Content-Transfer-Encoding: 7bit
--15199207040.4D75969.17798
Date: Thu, 1 Mar 2018 16:11:44 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #20 from taijian@posteo.de ---
(In reply to Alex Deucher from comment #19)
> were you using the patch and module option from comment 14?
I was using the drm-next-4.17-wip branch and pulled from commit=20=20=20=20=
=20=20=20=20
c2637e788da7a1cd535185e253ecc267b0410aff (current HEAD). I am fairly certain
that this does contain the patch you mentioned, amongst other things.=20
Kernel command line options used were amdgpu.dc=3D1 and amdgpu.force_atpx=
=3D1.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15199207040.4D75969.17798
Date: Thu, 1 Mar 2018 16:11:44 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 20
on bug 10406=
4
from taijian@posteo.d=
e
(In reply to Alex Deucher from comment #19)
> were you using the patch and module option from =
comment 14?
I was using the drm-next-4.17-wip branch and pulled from commit=20=20=20=20=
=20=20=20=20
c2637e788da7a1cd535185e253ecc267b0410aff (current HEAD). I am fairly certain
that this does contain the patch you mentioned, amongst other things.=20
Kernel command line options used were amdgpu.dc=3D1 and amdgpu.force_atpx=
=3D1.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15199207040.4D75969.17798--
--===============0175658364==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0175658364==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Mar 2018 16:39:07 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 6F5B36ECFF
for ; Thu, 1 Mar 2018 16:39:07 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1862582263==
Content-Type: multipart/alternative; boundary="15199223472.EBc99.24671"
Content-Transfer-Encoding: 7bit
--15199223472.EBc99.24671
Date: Thu, 1 Mar 2018 16:39:07 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #21 from taijian@posteo.de ---
Now testing the same build, but with amdgpu.dc=3D0 amdgpu.force_atpx=3D1.
Here the system does not crash on repeated invocations of the dGPU (via
DRI_PRIME=3D1 glxinfo), but it also does not fully power down, as confirmed=
by
powertop (26-28 W power consumption, vs ~12W with dc=3D1 and the dGPU not in
use).
So the option to force atpx apparently does nothing without dc. Is that
intended? (Sorry, I don't speak C, so I really cannot tell...)
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15199223472.EBc99.24671
Date: Thu, 1 Mar 2018 16:39:07 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 21
on bug 10406=
4
from taijian@posteo.d=
e
Now testing the same build, but with amdgpu.dc=3D0 amdgpu.forc=
e_atpx=3D1.
Here the system does not crash on repeated invocations of the dGPU (via
DRI_PRIME=3D1 glxinfo), but it also does not fully power down, as confirmed=
by
powertop (26-28 W power consumption, vs ~12W with dc=3D1 and the dGPU not in
use).
So the option to force atpx apparently does nothing without dc. Is that
intended? (Sorry, I don't speak C, so I really cannot tell...)
You are receiving this mail because:
- You are the assignee for the bug.
=
--15199223472.EBc99.24671--
--===============1862582263==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1862582263==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Mar 2018 16:48:20 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 246C66ED03
for ; Thu, 1 Mar 2018 16:48:20 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1953081927==
Content-Type: multipart/alternative; boundary="15199229001.dfab8ed.27311"
Content-Transfer-Encoding: 7bit
--15199229001.dfab8ed.27311
Date: Thu, 1 Mar 2018 16:48:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #22 from Alex Deucher ---
(In reply to taijian from comment #21)
> Now testing the same build, but with amdgpu.dc=3D0 amdgpu.force_atpx=3D1.
>=20
> Here the system does not crash on repeated invocations of the dGPU (via
> DRI_PRIME=3D1 glxinfo), but it also does not fully power down, as confirm=
ed by
> powertop (26-28 W power consumption, vs ~12W with dc=3D1 and the dGPU not=
in
> use).
>=20
> So the option to force atpx apparently does nothing without dc. Is that
> intended? (Sorry, I don't speak C, so I really cannot tell...)
Please attach your dmesg output. DC or not-DC shouldn't affect the runtime=
pm.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15199229001.dfab8ed.27311
Date: Thu, 1 Mar 2018 16:48:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 22
on bug 10406=
4
from Alex Deucher
(In reply to taijian from comment #21)
> Now testing the same build, but with amdgpu.dc=
=3D0 amdgpu.force_atpx=3D1.
>=20
> Here the system does not crash on repeated invocations of the dGPU (v=
ia
> DRI_PRIME=3D1 glxinfo), but it also does not fully power down, as conf=
irmed by
> powertop (26-28 W power consumption, vs ~12W with dc=3D1 and the dGPU =
not in
> use).
>=20
> So the option to force atpx apparently does nothing without dc. Is that
> intended? (Sorry, I don't speak C, so I really cannot tell...)
Please attach your dmesg output. DC or not-DC shouldn't affect the runtime=
pm.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15199229001.dfab8ed.27311--
--===============1953081927==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============1953081927==--
From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 104064] (DC 4.15-rc2) WARNING: CPU: 4 PID: 75 at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:601
dm_suspend+0x4e/0x60 [amdgpu]
Date: Thu, 01 Mar 2018 19:59:00 +0000
Message-ID:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id D47C06ED8E
for ; Thu, 1 Mar 2018 19:59:00 +0000 (UTC)
In-Reply-To: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============2104702325==
Content-Type: multipart/alternative; boundary="15199343401.4FfEbc.15043"
Content-Transfer-Encoding: 7bit
--15199343401.4FfEbc.15043
Date: Thu, 1 Mar 2018 19:59:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D104064
--- Comment #23 from taijian@posteo.de ---
Created attachment 137732
--> https://bugs.freedesktop.org/attachment.cgi?id=3D137732&action=3Dedit
dmesg with dc=3D1
Here is the first dmesg output. This was was generated with amdgpu.dc=3D1 a=
nd the
command "DRI_PRIME=3D1 glxgears || dmesg > dmesg.dc1.post". Shortly after w=
riting
the file, the computer then crashed again, so I was not able to collect any
more debugging data.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15199343401.4FfEbc.15043
Date: Thu, 1 Mar 2018 19:59:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated