[Bug 34626] New: Mesa-Gallium with R600 - Framerate limited to 60 fps after suspend-cycle
https://bugs.freedesktop.org/show_bug.cgi?id=34626
Summary: Mesa-Gallium with R600 - Framerate limited to 60 fps after suspend-cycle Product: DRI Version: XOrg CVS Platform: Other OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: peterle@hottemptation.org
Hello, I past I thought this is a bug of IOQuake3, but during switching between Mesa-Classic and Mesa-Gallium I recognized, that the problem only exists with Mesa-Gallium!
Reproduce: 1. $export vblank_mode=0 // switching of vsync 2. Launch an IOQuake3 based game (Quake3 Arena, OpenArena, World of Padman...) 3. check that VSYNC in IOQuake3 is also disabled! 4. Start a game and set "cg_drawpfs 1", know you should have at the top right corner a display with your current framerate which is hopefully over 60 fps 5. switch to a tty during playing (should be no problem with Kernel-Mode-Setting) 6. #pm-suspend (as root) 7. resume from suspend 8. switch back to X11/IOQuake3 -> framerate is limited to 60 fps
To fix this you have to relaunch IOQuake3 or simply type into quake-console "vid_restart". With Mesa-Classic and the R600-Driver this is not necessary, it displays always the maximum possible framerate.
Maybe Gallium doesn't read or forget the environment-variable export_vblank during resume from suspend?
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #1 from peterle@hottemptation.org 2011-02-23 08:18:54 PST --- Created an attachment (id=43710) --> (https://bugs.freedesktop.org/attachment.cgi?id=43710) output of dmesg
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #2 from peterle@hottemptation.org 2011-02-23 08:19:28 PST --- Created an attachment (id=43711) --> (https://bugs.freedesktop.org/attachment.cgi?id=43711) output of glxinfo
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #3 from peterle@hottemptation.org 2011-02-23 08:19:56 PST --- Created an attachment (id=43712) --> (https://bugs.freedesktop.org/attachment.cgi?id=43712) .config of kernel-2.6.38-rc6
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #4 from peterle@hottemptation.org 2011-02-23 08:20:14 PST --- Created an attachment (id=43713) --> (https://bugs.freedesktop.org/attachment.cgi?id=43713) output of lspci
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #5 from peterle@hottemptation.org 2011-02-23 08:20:49 PST --- Created an attachment (id=43714) --> (https://bugs.freedesktop.org/attachment.cgi?id=43714) output of complete package-list
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #6 from peterle@hottemptation.org 2011-02-23 08:21:20 PST --- Environment-Variables:
export R600_ENABLE_S3TC=1 export vblank_mode=0
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #7 from Michel Dänzer michel@daenzer.net 2011-02-23 08:45:26 PST --- (In reply to comment #7)
- switch to a tty during playing (should be no problem with
Kernel-Mode-Setting) 6. #pm-suspend (as root) 7. resume from suspend 8. switch back to X11/IOQuake3 -> framerate is limited to 60 fps
Does the problem also occur if you switch to console and back to X without a suspend/resume cycle in between?
Maybe Gallium doesn't read or forget the environment-variable export_vblank during resume from suspend?
No, the 3D driver is blissfully unaware of the suspend/resume cycle. The problem is more likely in the X server/driver or kernel.
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #8 from peterle@hottemptation.org 2011-02-23 09:08:40 PST --- If I only switch between console and X everything keeps fine.
https://bugs.freedesktop.org/show_bug.cgi?id=34626
peterle@hottemptation.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|Other |x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=34626
--- Comment #9 from Peter Weber peter.weber@ttyhoney.com 2011-11-19 09:40:14 PST --- I've tested this in the meantime also with a Intel based grapcis solution (Ironlake), it is not affected. But the Intel driver doesn't need the var vblank_mode for switching vsync off (only SwapbuffersWait). Maybe the setting of the var gets "lost" during suspend cycle?
https://bugs.freedesktop.org/show_bug.cgi?id=34626
Martin Peres martin.peres@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #10 from Martin Peres martin.peres@free.fr --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/180.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org