https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #11 from kyle.de...@mykolab.com ---
> systemd-udevd
This is not systemd's fault, but indicative of something hanging in kernel
land, which udevd ends up being blocked on.
Experienced this a few major kernel releases ago, which were
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #10 from freedesktop@nentwig.biz ---
So, there's 4.19rc1-amd-next \o/
echo: write error: Device or resource busy
This started to happen with 4.18. dmesg:
[ 171.245467] Freezing of tasks failed after 20.006 seconds (1 tasks ref
https://bugs.freedesktop.org/show_bug.cgi?id=107154
Christian König changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #8 from freedesktop@nentwig.biz ---
Created attachment 140528
--> https://bugs.freedesktop.org/attachment.cgi?id=140528&action=edit
dmesg 4.14 LTS
Sorry, forgot about the requested 4.14 dmesg log. Attached as well.
This is: bo
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #7 from freedesktop@nentwig.biz ---
Sure, attached. AMD staging kernel. I don't know how to tell whether DC=1 is
really enabled, so I did two runs: one with amdgpu.dc=1 as boot parameter and
one with /etc/modprobe.d/ on top of tha
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #6 from freedesktop@nentwig.biz ---
Created attachment 140526
--> https://bugs.freedesktop.org/attachment.cgi?id=140526&action=edit
dmesg /etc/modprobe.d/
Booted with amdgpu.dc=1 in /etc/modprobe.d/
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #5 from freedesktop@nentwig.biz ---
Created attachment 140525
--> https://bugs.freedesktop.org/attachment.cgi?id=140525&action=edit
dmesg amdgpu.dc=1
Booted with amdgpu.dc=1.
--
You are receiving this mail because:
You are th
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #4 from Christian König ---
Do you have a full dmesg?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
h
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #3 from Michel Dänzer ---
Please attach the full dmesg output.
Can you bisect between 4.14 and 4.15?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #2 from freedesktop@nentwig.biz ---
(In reply to dwagner from comment #1)
> I currently work around S3 resume crashes by switching to the console
> display before enterin S3 sleep - but this is really an awkward work-around.
Oh,
https://bugs.freedesktop.org/show_bug.cgi?id=107154
--- Comment #1 from dwagner ---
Indeed, crashes upon S3 resumes have been abundant with amdgpu.dc=1 for many
months now, and seemingly for more than one reason.
One bug I reported in August 2017 with
https://bugs.freedesktop.org/show_bug.cgi?id
https://bugs.freedesktop.org/show_bug.cgi?id=107154
Bug ID: 107154
Summary: [drm] GPU recovery disabled.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: nor
12 matches
Mail list logo
