https://bugzilla.kernel.org/show_bug.cgi?id=204559
Maxim Sheviakov (shoeg...@tutanota.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #14 from the...@gmail.com ---
i have not seen the oops on a 5.3.x kernel (ubuntu eoan), even without tweaking
the runpm setting (again, only saw it a few times on an earlier kernel).
--
You are receiving this mail because:
You are wa
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #13 from Maxim Sheviakov (shoeg...@tutanota.com) ---
I'm on kernel 5.4.7 now and seems like this particular issue is fixed - I tried
playing some movies with runpm enabled and things seemed to be okay. Though it
looks like dGPU perform
https://bugzilla.kernel.org/show_bug.cgi?id=204559
the...@gmail.com changed:
What|Removed |Added
CC||the...@gmail.com
--- Comment #12 from
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #11 from Christopher Snowhill (kod...@gmail.com) ---
Oops, I neglected to mention: The system is non-responsive to input devices, as
the USB input appears to all be completely powered off after the GPU crashes,
but the network interfac
https://bugzilla.kernel.org/show_bug.cgi?id=204559
Christopher Snowhill (kod...@gmail.com) changed:
What|Removed |Added
CC||kod...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #9 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Thanks for your explanation. By the way, disabling runpm also seems to fix the
other issue with disabling the display after activating the lockscreen as a
powersaving measure.
Is ther
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #8 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to Maxim Sheviakov from comment #7)
> By the way, how *exactly* does disabling runpm affect the system? Does it
> leave the discrete GPU always-on or vice verse? Or does it var
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #7 from Maxim Sheviakov (shoeg...@tutanota.com) ---
By the way, how *exactly* does disabling runpm affect the system? Does it leave
the discrete GPU always-on or vice verse? Or does it vary on each system?
I have tried running The Crew
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #6 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Created attachment 284345
--> https://bugzilla.kernel.org/attachment.cgi?id=284345&action=edit
dmesg -w with runpm=0 parameter
I have left my laptop with a video playing for about
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #5 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Created attachment 284341
--> https://bugzilla.kernel.org/attachment.cgi?id=284341&action=edit
dmesg -w without runpm parameter
Here's the whole dmesg from a fresh boot up until th
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #4 from Alex Deucher (alexdeuc...@gmail.com) ---
Looks like your system has two GPUs. Can you try booting with amdgpu.runpm=0?
Does that fix the issue?
--
You are receiving this mail because:
You are watching the assignee of the bu
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) ---
You can fetch the output before the hang.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel ma
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #2 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Created attachment 284337
--> https://bugzilla.kernel.org/attachment.cgi?id=284337&action=edit
journalctl --dmesg output
As I can't run dmesg after the system's hung, here's journa
https://bugzilla.kernel.org/show_bug.cgi?id=204559
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
15 matches
Mail list logo
