From: Andrea Arcangeli <andrea@suse.de>
To: jogi@planetzork.ping.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-pre11: alsaplayer skiping during kernel build (-pre10 did not)
Date: Tue, 18 Sep 2001 17:44:34 +0200 [thread overview]
Message-ID: <20010918174434.I19092@athlon.random> (raw)
In-Reply-To: <20010918171416.A6540@planetzork.spacenet> <20010918172500.F19092@athlon.random> <20010918173515.B6698@planetzork.spacenet>
In-Reply-To: <20010918173515.B6698@planetzork.spacenet>; from jogi@planetzork.ping.de on Tue, Sep 18, 2001 at 05:35:15PM +0200
On Tue, Sep 18, 2001 at 05:35:15PM +0200, jogi@planetzork.ping.de wrote:
> Since I am not using md there are not that much changes left between
> -pre10 and -pre11. Or do you think that it is caused by the console
> locking changes?
certainly not from the console locking changes. Can you just go back to
pre10 and verify you don't get those skips to just to be 100% sure the
userspace config is the same?
The only scheduler change in pre11 is this one:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.10pre10aa1/00_sched-rt-fix-1
which should be infact a bugfix for rt threads, also discussed on l-k
recently, so it's not clear how this odd regression happened.
You can try to back it out and see if helps just in case.
Andrea
next prev parent reply other threads:[~2001-09-18 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 15:14 2.4.10-pre11: alsaplayer skiping during kernel build (-pre10 did not) jogi
2001-09-18 15:25 ` Andrea Arcangeli
2001-09-18 15:35 ` jogi
2001-09-18 15:44 ` Andrea Arcangeli [this message]
2001-09-18 15:51 ` jogi
2001-09-18 16:06 ` jogi
2001-09-18 19:28 ` Stephan von Krawczynski
2001-09-18 19:41 ` Andrea Arcangeli
2001-09-18 20:02 ` Andrew Morton
2001-09-18 20:18 ` Andrea Arcangeli
2001-09-19 12:37 ` Hugh Dickins
2001-09-19 13:21 ` jogi
2001-09-19 14:38 ` jogi
2001-09-18 15:25 ` jogi
2001-09-18 15:31 ` Andrea Arcangeli
2001-09-18 15:43 ` jogi
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=20010918174434.I19092@athlon.random \
--to=andrea@suse.de \
--cc=jogi@planetzork.ping.de \
--cc=linux-kernel@vger.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).