https://bugs.freedesktop.org/show_bug.cgi?id=107065
Andrey Grodzovsky changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |andrey.grodzov...@amd.com
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #26 from Andrey Grodzovsky ---
(In reply to dwagner from comment #25)
> Created attachment 140634 [details]
> dmesg before and after S3 sleep with commit "updating plane ..." reverted
Reverting the patch makes the TTM eviction
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #25 from dwagner ---
Created attachment 140634
--> https://bugs.freedesktop.org/attachment.cgi?id=140634=edit
dmesg before and after S3 sleep with commit "updating plane ..." reverted
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #24 from dwagner ---
> > Reverting the commit "drm: Stop updating plane->crtc/fb/old_fb on atomic
> > drivers" for me only changes that after S3 resume, the very picture that was
> > visible before S3 sleep is displayed again - but
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #23 from Andrey Grodzovsky ---
(In reply to dwagner from comment #22)
> (In reply to Andrey Grodzovsky from comment #21)
> > I found the offending patch - drm: Stop updating plane->crtc/fb/old_fb on
> > atomic drivers
> > Not sure
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #22 from dwagner ---
(In reply to Andrey Grodzovsky from comment #21)
> I found the offending patch - drm: Stop updating plane->crtc/fb/old_fb on
> atomic drivers
> Not sure yet what's going on there and not sure it will fix you
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #21 from Andrey Grodzovsky ---
(In reply to dwagner from comment #20)
> (In reply to Andrey Grodzovsky from comment #19)
> > I was able to reproduce this instantly without even using page tables CPU
> > update mode. Looks like a
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #20 from dwagner ---
(In reply to Andrey Grodzovsky from comment #19)
> I was able to reproduce this instantly without even using page tables CPU
> update mode. Looks like a regression since S3 was working fine for long
> time. Were
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #19 from Andrey Grodzovsky ---
(In reply to Andrey Grodzovsky from comment #18)
> (In reply to dwagner from comment #17)
> > Interesting observation: If I first switch from the X11 display to the
> > console display (with Alt-F2),
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #18 from Andrey Grodzovsky ---
(In reply to dwagner from comment #17)
> Interesting observation: If I first switch from the X11 display to the
> console display (with Alt-F2), and then enter "echo mem >/sys/power/state"
> on the
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #17 from dwagner ---
Interesting observation: If I first switch from the X11 display to the console
display (with Alt-F2), and then enter "echo mem >/sys/power/state" on the
console, above described crashes upon S3 resume do not
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #16 from dwagner ---
(In reply to Andrey Grodzovsky from comment #15)
> We have only minor differences but I can't reproduce it. Maybe the resume
> failure is indeed due the eviction failure during suspend. Is S3 failure is
>
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #15 from Andrey Grodzovsky ---
(In reply to dwagner from comment #14)
> (In reply to Andrey Grodzovsky from comment #13)
> > What ASIC are you using ? I also tested with
> > gfx8 ASIC and haven't observed any issues with resume. Did
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #14 from dwagner ---
(In reply to Andrey Grodzovsky from comment #13)
> What ASIC are you using ? I also tested with
> gfx8 ASIC and haven't observed any issues with resume. Did you update the
> firmware for this ASIC to latest #
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #13 from Andrey Grodzovsky ---
(In reply to dwagner from comment #12)
> (In reply to Andrey Grodzovsky from comment #10)
> > Created attachment 140418 [details] [review] [review]
> > drm/amdgpu: Verify root PD is mapped into kernel
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #12 from dwagner ---
(In reply to Andrey Grodzovsky from comment #10)
> Created attachment 140418 [details] [review]
> drm/amdgpu: Verify root PD is mapped into kernel address space.
>
> dwagner, please try this patch. Fixes the
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #11 from Christian König ---
(In reply to Andrey Grodzovsky from comment #10)
> Created attachment 140418 [details] [review]
> drm/amdgpu: Verify root PD is mapped into kernel address space.
>
> dwagner, please try this patch.
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #10 from Andrey Grodzovsky ---
Created attachment 140418
--> https://bugs.freedesktop.org/attachment.cgi?id=140418=edit
drm/amdgpu: Verify root PD is mapped into kernel address space.
dwagner, please try this patch. Fixes the
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #9 from Andrey Grodzovsky ---
(In reply to Andrey Grodzovsky from comment #8)
> (In reply to dwagner from comment #7)
> > (In reply to Andrey Grodzovsky from comment #6)
> > > So with Arch Linux kernel it happens only during S3 but
https://bugs.freedesktop.org/show_bug.cgi?id=107065
--- Comment #8 from Andrey Grodzovsky ---
(In reply to dwagner from comment #7)
> (In reply to Andrey Grodzovsky from comment #6)
> > So with Arch Linux kernel it happens only during S3 but with
> > amd-staging-drm-next it happens once you
https://bugs.freedesktop.org/show_bug.cgi?id=107065
dwagner changed:
What|Removed |Added
Summary|"BUG: unable to handle |"BUG: unable to handle
21 matches
Mail list logo
