| Summary: | Entire system stutters every so often when running proprietary game Minecraft | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | andre35822 |
| Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED NOTABUG | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | dmesg output when freezing occurs | ||
Forgot to mention I am on Arch Linux, kernel 4.3.3, mesa 11.1 and am using an AMD 7950. Thanks for the report. Did the messages [43513.525167] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_set_sw_state failed [43982.380508] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_restrict_performance_levels_before_switch failed occur at the same time as the stutter? That would point at a kernel problem. (In reply to Nicolai Hähnle from comment #2) > Thanks for the report. Did the messages > > [43513.525167] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_set_sw_state > failed > [43982.380508] [drm:si_dpm_set_power_state [radeon]] *ERROR* > si_restrict_performance_levels_before_switch failed > > occur at the same time as the stutter? That would point at a kernel problem. No messages appeared on my screen, what I have noticed is that whenever this freezing occurs, so does my entire system essentially (I can still hear audio from Skype or Mumble but I can't interact with things)...however those messages seem familiar..ahh I know. I think I have seen those messages occasionally show up on my screen when I log out/log back in. I think I started getting this since the 4.1 kernels.... I am not really sure what I can do to further help you but please let me know! Although, this portion is offtopic. I have another machine with an AMD 6570 or something and those messages would occasionally show up on Linux Mint 17.1 and the kernel that one uses is 3.18. Those messages would not be triggered by an application. They can only be triggered by manually changing the power state via sysfs or via a display change event such as switching between single and multi display. (In reply to Alex Deucher from comment #4) > Those messages would not be triggered by an application. They can only be > triggered by manually changing the power state via sysfs or via a display > change event such as switching between single and multi display. I think I have messed with the power state once by following the Arch Linux wiki, though the wiki said the methods provided would not be permanent so it isn't anything that I did right? Are these errors responsible for the problems I am getting in OP? Thanks again! Please run the game with the environment variable GALLIUM_HUD=fps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,GPU-load,num-bytes-moved,buffer-wait-time,num-compilations+num-shaders-created and attach a screenshot of the game window taken just after a freeze occurred. (In reply to Michel Dänzer from comment #6) > Please run the game with the environment variable > GALLIUM_HUD=fps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,GPU-load, > num-bytes-moved,buffer-wait-time,num-compilations+num-shaders-created and > attach a screenshot of the game window taken just after a freeze occurred. Um, my Linux knowledge is limited with this. I have minecraft-launcher in my /usr/bin folder, so what I did was I put the following in the terminal and hit enter /usr/share/minecraft/ GALLIUM_HUD=fps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,GPU-load,num-bytes-moved,buffer-wait-time,num-compilations+num-shaders-created The game loaded up but I don't know if what you want is working. What do you normally run to start minecraft from the terminal? I'll assume it's just minecraft, but if it is different just replace that part. Run: GALLIUM_HUD=fps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,GPU-load,num-bytes-moved,buffer-wait-time,num-compilations+num-shaders-created minecraft If it works, you should see a bunch of graphs appears on the screen. (In reply to Matthew Dawson from comment #8) > What do you normally run to start minecraft from the terminal? I'll assume > it's just minecraft, but if it is different just replace that part. Run: > > GALLIUM_HUD=fps,requested-VRAM+VRAM-usage,requested-GTT+GTT-usage,GPU-load, > num-bytes-moved,buffer-wait-time,num-compilations+num-shaders-created > minecraft > > If it works, you should see a bunch of graphs appears on the screen. That definitely did the trick, okay, thank you! I will play in the world and take a screenshot once a stutter happens! Oddly enough I can not seem to reproduce the bug. It appears to only ecounter whenever I am playing with another player...which is also when I have Skype open. Interesting..maybe Skype was the cause of this? I need to do some further tests now. Running applications in the background or networked game play will increase cpu use. It's not unreasonable for this to cause stuttering on a lower end cpu. Since there is not much else to go on here and radeonsi has received many updates to reduce various types of cpu use since this was reported I'm closing this bug for now. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 121117 [details] dmesg output when freezing occurs I have noticed that it occurs every once in a while, randomly, while playing the game, mostly when I am moving around/entering new areas where chunks have not loaded. I remember a few past mesa releases behind the game would have an insane amount of stutter (mesa 10.5 or so) whenever new chunks would load and I am guessing this is still the same issue just not as dramatic. I have no clue what info to provide you guys except to give you a dmesg output immediately after the stutter occurs.