Suspend to RAM works perfectly with NV40/NV46 (Geforce Go 7400),
but not suspend to disk (hibernation).
The resume after suspend to disk (hibernation) has as a result, a black
screen and it freezes ever keyboard
Only solution then, is hard poweroff...
Is suspend to disk (hibernation) supporte
nouveau's ->runtime_suspend hook calls drm_kms_helper_poll_disable(),
which waits for the output poll worker to finish if it's running.
The output poll worker meanwhile calls pm_runtime_get_sync() in
nouveau_connector_detect() which waits for the ongoing suspend to finish,
causing a deadlock.
Fix
Introduce a helper to determine if the current task is an output poll
worker.
This allows us to fix a long-standing deadlock in several DRM drivers
wherein the ->runtime_suspend callback waits for the output poll worker
to finish and the worker in turn calls a ->detect callback which waits
for run
Fix a deadlock on hybrid graphics laptops that's been present since 2013:
DRM drivers poll connectors in 10 sec intervals. The poll worker is
stopped on ->runtime_suspend with cancel_delayed_work_sync(). However
the poll worker invokes the DRM drivers' ->detect callbacks, which call
pm_runtime_g
Introduce a helper to retrieve the current task's work struct if it is
a workqueue worker.
This allows us to fix a long-standing deadlock in several DRM drivers
wherein the ->runtime_suspend callback waits for a specific worker to
finish and that worker in turn calls a function which waits for run
radeon's ->runtime_suspend hook calls drm_kms_helper_poll_disable(),
which waits for the output poll worker to finish if it's running.
The output poll worker meanwhile calls pm_runtime_get_sync() in
radeon's ->detect hooks, which waits for the ongoing suspend to finish,
causing a deadlock.
Fix by
amdgpu's ->runtime_suspend hook calls drm_kms_helper_poll_disable(),
which waits for the output poll worker to finish if it's running.
The output poll worker meanwhile calls pm_runtime_get_sync() in
amdgpu's ->detect hooks, which waits for the ongoing suspend to finish,
causing a deadlock.
Fix by
https://bugs.freedesktop.org/show_bug.cgi?id=71659
--- Comment #35 from dusan ---
I have Dell 6520 with NVS 4200M.
Problem is still there. With Mag6 64bit latest update. I mean problem is with
graphic ram manegement because when I play video (with XVideo) desktop is
freezing much sooner how when
https://bugs.freedesktop.org/show_bug.cgi?id=105045
Bug ID: 105045
Summary: System freeze with nouveau
Product: Mesa
Version: 17.3
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #1 from Sergey Tereschenko ---
Created attachment 137276
--> https://bugs.freedesktop.org/attachment.cgi?id=137276&action=edit
gnome-shell core dump
--
You are receiving this mail because:
You are the assignee for the bug.
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #2 from Sergey Tereschenko ---
Created attachment 137277
--> https://bugs.freedesktop.org/attachment.cgi?id=137277&action=edit
xwayland coredump
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are
https://bugs.freedesktop.org/show_bug.cgi?id=105045
Sergey Tereschenko changed:
What|Removed |Added
Priority|medium |high
--
You are receiving this ma
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #3 from Ilia Mirkin ---
This happens because GPU fault recovery currently leaves the process in a
totally broken state. (And all other processes that use the GPU, seemingly.)
The general approach has been to try to avoid the GPU fau
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #4 from Sergey Tereschenko ---
Can i just apply that patch to 17.3 or better build everything from git?
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #5 from Ilia Mirkin ---
(In reply to Sergey Tereschenko from comment #4)
> Can i just apply that patch to 17.3 or better build everything from git?
You can just apply it. There's other stuff that's gone in though... I was just
point
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #6 from Sergey Tereschenko ---
(In reply to Ilia Mirkin from comment #5)
> (In reply to Sergey Tereschenko from comment #4)
> > Can i just apply that patch to 17.3 or better build everything from git?
>
> You can just apply it. Ther
On 11 February 2018 at 09:38, Lukas Wunner wrote:
> Fix a deadlock on hybrid graphics laptops that's been present since 2013:
>
> DRM drivers poll connectors in 10 sec intervals. The poll worker is
> stopped on ->runtime_suspend with cancel_delayed_work_sync(). However
> the poll worker invokes
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #7 from Sergey Tereschenko ---
(In reply to Ilia Mirkin from comment #5)
> (In reply to Sergey Tereschenko from comment #4)
> > Can i just apply that patch to 17.3 or better build everything from git?
>
> You can just apply it. Ther
On Sun, Feb 11, 2018 at 06:58:11PM +, Mike Lothian wrote:
> On 11 February 2018 at 09:38, Lukas Wunner wrote:
> > The patches for radeon and amdgpu are compile-tested only, I only have a
> > MacBook Pro with an Nvidia GK107 to test. To test the patches, add an
> > "msleep(12*1000);" at the to
On Sun, Feb 11, 2018 at 08:23:14PM +0100, Lukas Wunner wrote:
> On Sun, Feb 11, 2018 at 06:58:11PM +, Mike Lothian wrote:
> > On 11 February 2018 at 09:38, Lukas Wunner wrote:
> > > The patches for radeon and amdgpu are compile-tested only, I only have a
> > > MacBook Pro with an Nvidia GK107
https://bugs.freedesktop.org/show_bug.cgi?id=105045
--- Comment #8 from Sergey Tereschenko ---
(In reply to Sergey Tereschenko from comment #7)
> (In reply to Ilia Mirkin from comment #5)
> > (In reply to Sergey Tereschenko from comment #4)
> > > Can i just apply that patch to 17.3 or better buil
Hi
I've not been able to reproduce the original problem you're trying to
solve on amdgpu thats with or without your patch set and the above
"trigger" too
Is anything else required to trigger it, I started multiple DRI_PRIME
glxgears, in parallel, serial waiting the 12 seconds and serial within
th
On Mon, Feb 12, 2018 at 12:35:51AM +, Mike Lothian wrote:
> I've not been able to reproduce the original problem you're trying to
> solve on amdgpu thats with or without your patch set and the above
> "trigger" too
>
> Is anything else required to trigger it, I started multiple DRI_PRIME
> glx
23 matches
Mail list logo
