All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: Matthias Klose <doko@cs.tu-berlin.de>
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] running gcc testsuite triggers ongoing page faults
Date: Sun, 11 Jan 2004 02:08:53 -0800	[thread overview]
Message-ID: <20040111100853.GF533@tausq.org> (raw)
In-Reply-To: <16385.5227.153358.397944@gargle.gargle.HOWL>

In reference to a message from Matthias Klose, dated Jan 11:
> I think I did see this first with gcc-3.3 from 20031229. Running the
> 3.3 testsuite (gcc) doesn't terminate. Instead, I see expect eating
> all CPU time, together with syslogd and klogd. /var get's filled with
> log messages in kern.log, syslog and debug.
> 
> The machine is a A500, kernel from the archives (kernel-image-2.4.21-64-smp_pa7.3)

jda sees this problem too, but we haven't been able to isolate it. if
you can find out which test case causes this we might be able to figure
it out.

also it appears that when running a UP kernel this doesn't happen.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2004-01-11  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11  9:16 [parisc-linux] running gcc testsuite triggers ongoing page faults Matthias Klose
2004-01-11 10:08 ` Randolph Chung [this message]
2004-01-11 11:39   ` Matthias Klose
2004-01-11 11:39   ` Matthias Klose
2004-01-11 14:25     ` Randolph Chung
2004-01-11 14:25     ` Randolph Chung
2004-01-11 10:08 ` Randolph Chung
2004-01-11 20:49 ` John David Anglin
2004-01-11 20:49 ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11  9:16 Matthias Klose

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=20040111100853.GF533@tausq.org \
    --to=tausq@debian.org \
    --cc=debian-hppa@lists.debian.org \
    --cc=doko@cs.tu-berlin.de \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.