linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 194963] New: schedutil governor causes audio problem in game
Date: Thu, 23 Mar 2017 10:40:58 +0000	[thread overview]
Message-ID: <bug-194963-137361@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=194963

            Bug ID: 194963
           Summary: schedutil governor causes audio problem in game
           Product: Power Management
           Version: 2.5
    Kernel Version: 4.10.4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: john.ettedgui@gmail.com
        Regression: No

Created attachment 255443
  --> https://bugzilla.kernel.org/attachment.cgi?id=255443&action=edit
dmesg

Hello,

I'm on the kernel 4.10.4 but I've had the same issues for a few weeks already,
definitely on .3 and probably on .2 but not sure anymore.

When I switched the cpu governor from ondemand or performance to schedutil, it
all seemed fine, but actually playing a game in wine gives me audio cracking
every now and then, fairly similarly to when we didn't have a pulseaudio
backend in wine. (I have not tried using only alsa).

Interestingly I've tried 2 different games in Wine and the problem only happens
with one, I assume the more CPU intensive one: StarCraft 2.

Restarting the computer, killing pulseaudio and restarting it, limiting the
apps opened, not of that changed anything, but switching the governor back
fixed it right away.

My CPU is an Intel i7 4790k, this is my kernel line:
linux   /vmlinuz-linux root=/dev/sda3 rw  rootfstype=btrfs raid=noautodetect
intel_iommu=on quiet add_efi_memmap clocksource=hpet hpet=enable splash
consoleblank=0 intel_pstate=disable sysrq_always_enabled=1


I am not sure what else to provide, there was nothing in dmesg that seemed
related, nor any error in Wine, please tell me how I can help.

Thank you,
John

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2017-03-23 10:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 10:40 bugzilla-daemon [this message]
2017-03-23 13:07 ` [Bug 194963] schedutil governor causes audio problem in game bugzilla-daemon
2017-03-23 14:31 ` bugzilla-daemon
2017-03-23 15:11 ` bugzilla-daemon
2017-03-23 23:03 ` bugzilla-daemon
2017-03-23 23:23 ` bugzilla-daemon
2017-03-24  0:40 ` bugzilla-daemon
2017-03-24  1:11 ` bugzilla-daemon
2017-03-24  4:02 ` bugzilla-daemon
2017-03-24 15:17 ` bugzilla-daemon
2017-03-24 23:06 ` bugzilla-daemon
2017-03-27 23:12 ` bugzilla-daemon
2017-03-27 23:14 ` bugzilla-daemon
2017-03-28 22:54 ` bugzilla-daemon
2017-03-29  0:28 ` bugzilla-daemon
2017-03-29  5:21 ` bugzilla-daemon
2017-03-29  6:27 ` bugzilla-daemon
2017-03-29 20:28 ` bugzilla-daemon
2017-03-30  3:32 ` bugzilla-daemon
2017-03-30 14:24 ` bugzilla-daemon
2017-03-31  3:51 ` bugzilla-daemon
2017-03-31  8:45 ` bugzilla-daemon
2017-03-31  8:57 ` bugzilla-daemon
2017-03-31  9:00 ` bugzilla-daemon
2017-05-07 14:58 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-194963-137361@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pm@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).