From: Frans Pop <elendil@planet.nl>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: [rc8] Regression: key repeats and skips in music during compilation
Date: Mon, 7 Apr 2008 23:55:53 +0200 [thread overview]
Message-ID: <200804072355.55076.elendil@planet.nl> (raw)
In-Reply-To: <1207571115.15579.26.camel@twins>
On Monday 07 April 2008, you wrote:
> > Note that I can also reproduce the issue with a kernel that does *not*
> > have CONFIG_GROUP_SCHED set. I still get the music skips (maybe less
> > frequently, but that's hard to measure), and I've have also seen key
> > repeats once.
> >
> > Anything I can do to provide additional info on this?
>
> Could you try -rc5 !GROUP ?
Good call! Problem cannot be reproduced with -rc5 (without GROUP_SCHED set).
Music remains smooth during the compilation.
Do you have a particular change in mind or should I still provide the trace
info as suggested by Ingo? If so, I can probably do that tomorrow.
Cheers,
FJP
next prev parent reply other threads:[~2008-04-07 21:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 10:22 [rc8] Regression: key repeats and skips in music during compilation Frans Pop
2008-04-06 20:39 ` Rafael J. Wysocki
2008-04-07 9:21 ` Rafael J. Wysocki
2008-04-07 10:05 ` Frans Pop
2008-04-07 10:29 ` Rafael J. Wysocki
2008-04-07 11:24 ` Dhaval Giani
2008-04-07 12:03 ` Frans Pop
2008-04-07 12:25 ` Peter Zijlstra
2008-04-07 21:55 ` Frans Pop [this message]
2008-04-07 12:32 ` Ingo Molnar
[not found] ` <200804081137.20063.elendil@planet.nl>
2008-04-08 13:54 ` Ingo Molnar
2008-04-12 11:29 ` Richard Jonsson
2008-04-19 21:31 ` Richard Jonsson
2008-04-19 22:05 ` Frans Pop
2008-04-21 14:16 ` Richard Jonsson
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=200804072355.55076.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=vatsa@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.