Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1365358 - Kernel scheduling leads to micropauses in games
Summary: Kernel scheduling leads to micropauses in games
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-09 05:18 UTC by Turgut Kalfaoglu
Modified: 2016-08-09 11:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-09 11:18:54 UTC


Attachments (Terms of Use)

Description Turgut Kalfaoglu 2016-08-09 05:18:07 UTC
Description of problem:

Running games under wine-1.9.15 leads to small pauses in the game, every two seconds. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install a game under wine or crossoffice, such as World of Warcraft
2. Try the game
3. During game play, a small pause is felt every two seconds.



Additional info:
I am told that this is due to the kernel scheduling. 
The real-time kernel should be able to fix this; however, Bumblebee does not work with the RT-kernel, because the new NVIDIA drivers refuse to be compiled under the RT-kernel. Hence, Fedora should include the precompiled drivers and the RT-kernel.

Comment 1 Josh Boyer 2016-08-09 11:18:54 UTC
This bug is a huge bucket of nope.  I'm sorry, but none of the things you're asking for are something that will be done.

If you have a suspected issue with the scheduler, contacting upstream is the best solution.


Note You need to log in before you can comment on or make changes to this bug.