linux-kernel - Re: [Bug #10616] Horrendous Audio Stutter

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <82e4877d0805111459jf4891fbpff5a91b08e32db01@mail.gmail.com>
Date:	Sun, 11 May 2008 17:59:21 -0400
From:	"Parag Warudkar" <parag.warudkar@...il.com>
To:	"Adrian Bunk" <bunk@...nel.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Peter Zijlstra" <peterz@...radead.org>,
	"Frans Pop" <elendil@...net.nl>
Subject: Re: [Bug #10616] Horrendous Audio Stutter - current git

On Sun, May 11, 2008 at 5:41 PM, Adrian Bunk <bunk@...nel.org> 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@...k.pl> 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?

GROUP_SCHED stuff.

>
> 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?

Both current -git and sched-devel have this problem - that means it's
unrelated to the commit you refer to unless it was reintroduced in a
different form but same effect.

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