Re: [Bug #10616] Horrendous Audio Stutter - current git

[Frans Pop]

On Sunday 11 May 2008, you wrote:
> On Sun, May 11, 2008 at 05:28:47PM -0400, Parag Warudkar wrote:
> > On Sun, May 11, 2008 at 4:04 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote:
> > > This message has been generated automatically as a part of a report
> > > of recent regressions.
> > >
> > > The following bug entry is on the current list of known regressions
> > > from 2.6.25.  Please verify if it still should be listed.
> > >
> > >
> > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=10616
> > > Subject         : Horrendous Audio Stutter - current git
> >
> > Still present both in Linus tree and sched-devel - root cause is not
> > yet well understood per Ingo.
> >
> > Worked around by disabling GROUP_SCHED stuff by default (commit
> > aac6abca858386438d9a7233c3471d2ecfa2f704 ).
>
> What causes this regression?
>
> Is this commit 018d6db4cb5bbdcd65424a16f2dcca692ed32ae4
> (sched: re-do "sched: fix fair sleepers") that had already been reverted
> in 2.6.25 for causing such regressions or is this caused by a different
> commit?

No, it's not that commit. That commit also caused a (less severe and fairly 
hard to reproduce) latency issue, but that has now been fixed by the patch 
listed in the BR (committed as a992241de614dd2b7c97a9ba64e28c0e563f19bf).


The issue reported by Parag as "Horrendous Audio Stutter" (and confirmed by 
me) is much more severe and is indeed related to group scheduling.

The group scheduling related issue disappeared for me with -rc1 after 
reverting the following two commits (as suggested by Mike Galbraith):
- 7ba2e74ab5a0518bc953042952dd165724bc70c9
  sched: debug: show a weight tree
- 8f1bc385cfbab474db6c27b5af1e439614f3025c
  sched: fair: weight calculations

Given the confusing and partially incorrect information in this BR, it seems 
best to me to close it and open a new one for the issue reported by Parag.

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/