Bug 216780

Summary: problem of Mesa drawing boxes after resume from suspend with Geforce4 420 Go
Product: Drivers Reporter: Elmar Stellnberger (estellnb)
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: RESOLVED ANSWERED    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.15.79-desktop586 Subsystem:
Regression: No Bisected commit-id:
Attachments: after resume from s2ram: screen distortions in the status tray and on moving the Pidgin window
after resume from s2ram: the background box of the login screen is not drawn
before resume from s2ram: background box of login screen is drawn correctly

Description Elmar Stellnberger 2022-12-06 16:45:26 UTC
When it has finished to boot everything works correctly: I can move the Pidgin window or I can lock the screen: boxes are drawn correctly. Yet after resume from s2ram/suspend you can see a black box as the background of the status bar tray instead of a filled one, moving pidgin leads to box-shaped screen distortions and the background box of the login dialogue is not drawn any more. Using Mesa patches from Karol Herbst for gtk3 apps (https://gitlab.freedesktop.org/drm/nouveau/-/issues/174); xscreensaver as well as the drawing of the lxde status tray bar shall be independent from this however (non-gtk).

kernel modules used for dri (as returned by lspci): rivafb, nvidiafb, nouveau
kernel: 5.15.79-desktop586 SMP i686 i386 GNU/Linux
graphics card: NVIDIA Corporation NV17M [GeForce4 420 Go] (rev a3)
Comment 1 Elmar Stellnberger 2022-12-06 16:46:17 UTC
Created attachment 303369 [details]
after resume from s2ram: screen distortions in the status tray and on moving the Pidgin window
Comment 2 Elmar Stellnberger 2022-12-06 16:46:55 UTC
Created attachment 303370 [details]
after resume from s2ram: the background box of the login screen is not drawn
Comment 3 Elmar Stellnberger 2022-12-06 16:48:06 UTC
Created attachment 303371 [details]
before resume from s2ram: background box of login screen is drawn correctly

just tested:: same issue with suspend to disk
Comment 4 Artem S. Tashkinov 2022-12-06 17:37:05 UTC
Please report here instead https://gitlab.freedesktop.org/drm/nouveau/-/issues/
Comment 5 Elmar Stellnberger 2022-12-06 17:44:49 UTC
done: https://gitlab.freedesktop.org/drm/nouveau/-/issues/194
Comment 6 Elmar Stellnberger 2022-12-18 11:38:31 UTC
  Just for curiosity I have tested on that machine with different values for acpi_sleep:
acpi_sleep=s3_mode: white/bright character boxes, no resume
acpi_sleep=s3_bios: black screen, as usual but no resume
acpi_sleep=s3_bios,s3_mode: black screen, as usual but no resume

  Now I am a bit clueless since these three values were what I supposed to be the only values that can be passed to acpi_sleep. The default must be different since there it works. DidnĀ“t find respective docs. Perhaps I have not waited long enough for resume?
Comment 7 Elmar Stellnberger 2022-12-26 17:48:53 UTC
Did not re-test the acpi_sleep modes from above with kernel 6.1.0-desktop586, where the screen content was preserved directly after resume. kernel 6.1.1 no more exposes this feature.