From: Daniel Phillips <phillips@bonn-fries.net>
To: Nicolas Pitre <nico@cam.org>
Cc: Anwar P <anwarp@mail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: What version of the kernel fixes these VM issues?
Date: Sat, 25 Aug 2001 00:35:59 +0200 [thread overview]
Message-ID: <20010824222924Z16116-32383+1243@humbolt.nl.linux.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0108241610560.25240-100000@xanadu.home>
In-Reply-To: <Pine.LNX.4.33.0108241610560.25240-100000@xanadu.home>
On August 24, 2001 10:12 pm, Nicolas Pitre wrote:
> On Fri, 24 Aug 2001, Daniel Phillips wrote:
>
> > On August 24, 2001 08:14 pm, Nicolas Pitre wrote:
> > > I have a totally different setup but I can reproduce the same behavior on
> > > the system I have here:
> > >
> > > ARM board with 32 MB RAM, no flash, NFS root.
> > > The kernel is based on 2.4.8-ac9 plus some small VM fixes from -ac10.
> > >
> > > My test consist in compiling gcc 3.0 while some MP3s are continously playing
> > > in the background. The gcc build goes pretty far along until both the mp3
> > > player and the gcc build completely jam.
> >
> > Which sound system, and which sound card driver?
>
> The driver is for the UDA1341 on a SA1110 chip written by myself. It is
> fully OSS compliant, no ALSA.
Your system should be able to handle that easily. Do you have some meminfo
output to look at? What about 2.4.9?
--
Daniel
next prev parent reply other threads:[~2001-08-24 22:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 8:47 Anwar P
2001-08-24 13:18 ` Daniel Phillips
2001-08-24 18:14 ` Nicolas Pitre
2001-08-24 18:25 ` Nicolas Pitre
2001-08-24 18:48 ` Mark Frazer
2001-08-24 19:53 ` Daniel Phillips
2001-08-24 19:56 ` Daniel Phillips
2001-08-24 20:12 ` Nicolas Pitre
2001-08-24 22:35 ` Daniel Phillips [this message]
2001-08-25 3:00 ` Nicolas Pitre
2001-08-25 4:31 ` Steve Kieu
2001-08-25 8:09 ` Russell King
2001-08-25 16:38 ` Daniel Phillips
2001-08-25 16:38 ` Daniel Phillips
2001-08-25 18:29 ` Nicolas Pitre
2001-08-25 18:51 ` Russell King
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=20010824222924Z16116-32383+1243@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=anwarp@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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
all inboxes | Powered by JetHome®