linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jogi@planetzork.ping.de
To: "Andrea Arcangeli" <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-pre11: alsaplayer skiping during kernel build (-pre10 did not)
Date: 18 Sep 2001 17:43:02 +0200	[thread overview]
Message-ID: <20010918174302.C6698@planetzork.spacenet> (raw)
In-Reply-To: <20010918171416.A6540@planetzork.spacenet> <20010918172529.A6698@planetzork.spacenet> <20010918173142.G19092@athlon.random>
In-Reply-To: <20010918173142.G19092@athlon.random>; from andrea@suse.de on Tue, Sep 18, 2001 at 05:31:42PM +0200

On Tue, Sep 18, 2001 at 05:31:42PM +0200, Andrea Arcangeli wrote:
> On Tue, Sep 18, 2001 at 05:25:29PM +0200, jogi@planetzork.ping.de wrote:
> > On Tue, Sep 18, 2001 at 05:14:16PM +0200, jogi@planetzork.ping.de wrote:
> > > Hello Andrea,
> > > 
> > > I gave your new vm a try and I have to report a problem. System is an
> > > Athlon 1200 with 256MB memory. Workload:
> > 
> > Sorry to follow up on my own. But the problem seems to be worse than I
> > first thought. Kernel build is the first thing I test when I try a new
> > kernel :-)
> > 
> > So now I logged into X and even during starting of Mozilla or normal
> > web browsing alsaplayer is skiping *lots*. The system is not into swap
> > and has about 150MB cached. Just to let you know ...
> > 
> > I guess I will go back to -pre10 now. If you want to let me test some
> > things just let me know.
> 
> just make sure not to renice top at -10. Are you sure you reniced top at
> -10 also with pre10? Those issues shouldn't really vm related. I also
> profiled the new vm well and it never showed up in the toplist so I
> suspect you changed something in userspace. and of course I run xmms all
> the time too and it didn't skept one sample yet.

Ok, I just killed top. And it still is skiping lots although I do
not have any reniced jobs running. And yes, I had top running reniced
too on -pre10. I will boot -pre10 and check if it is skipping because
alsaplayer is currently skipping as hell (running make -j4 in the
background). Still no swap used. Strange. I will check xmms also and
let you know.

Regards,

   Jogi

-- 

Well, yeah ... I suppose there's no point in getting greedy, is there?

    << Calvin & Hobbes >>

      reply	other threads:[~2001-09-18 15:45 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
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 [this message]

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=20010918174302.C6698@planetzork.spacenet \
    --to=jogi@planetzork.ping.de \
    --cc=andrea@suse.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).