mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "M. Edward Borasky" <znmeb@aracnet.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Cerberus testing of 2.4.17-rc1
Date: Sun, 23 Dec 2001 21:37:48 -0800	[thread overview]
Message-ID: <HBEHIIBBKKNOBLMPKCBBCEJPEEAA.znmeb@aracnet.com> (raw)
In-Reply-To: <3C1E19E7.88C62DAC@redhat.com>

Has this been fixed?
--
M. Edward Borasky
znmeb@borasky-research.net
http://www.borasky-research.net

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Bob Matthews
> Sent: Monday, December 17, 2001 8:15 AM
> To: Marcelo Tosatti; linux-kernel@vger.kernel.org
> Subject: Re: Cerberus testing of 2.4.17-rc1
>
>
> Bob Matthews wrote:
>
> > Hardware:  8 x PIII, 16G RAM, 20G Swap, 2 x Sym53c899.
> > Kernel: 2.4.17-rc1, configured with SMP, HIGHMEM=64G, plus necessary
> > drivers.
> >
> > After 10-30 minutes of testing (it's different each time) the machine
> > starts to slow down.  Eventually, the machine appears to stall
> > completely.  The timer for the test harness continues to tick, and I can
> > change virtual consoles, so the machine is not completely hung.  When
> > the machine gets into this state, the test suite stops making progress.
> > Also, input typed to the virtual consoles is not echoed.
> >
> > <SysRq><P> <T> and <M> print only the column headings, but not any data,
> > so that is as complete a bug report as I can give you at this time.
>
> The machine never made any more observable progress, and eventually
> oopsed after approx. 48 hours.


      reply	other threads:[~2001-12-24  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C1A6E09.497899C7@redhat.com>
2001-12-17 16:14 ` Bob Matthews
2001-12-24  5:37   ` M. Edward Borasky [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=HBEHIIBBKKNOBLMPKCBBCEJPEEAA.znmeb@aracnet.com \
    --to=znmeb@aracnet.com \
    --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

all inboxes | Powered by JetHome®