From: Samuel Flory <sflory@rackable.com>
To: Paul Larson <plars@linuxtestproject.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Cerberus
Date: Wed, 05 Feb 2003 14:14:55 -0800 [thread overview]
Message-ID: <3E418CDF.7020001@rackable.com> (raw)
In-Reply-To: 1044475584.30331.135.camel@plars
Paul Larson wrote:
>I saw a comment late last week that someone was seeing cerberus crash
>instantaneously with 2.5 on UP machines, so I decided to try to
>reproduce this problem. I got the latest version of ceerbuerus and put
>it on a single processor pIII-866 256MB ram, linux-2.5.59 kernel.
>Newburn has been running for just under 5 days now without so much as a
>hiccup.
>
>1. Has anyone had first hand experience with this instability?
>
>2. If so, were you just running the default newburn, or something else?
>Please let me know if you did something different that caused it to
>crash.
>
>
I've run Cerberus on a number of smp 2.5 kernels without issue. You
might try "./newburn -t -p 2". Remember that you can fine tune your
test by editing the newburn.tcf file.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
prev parent reply other threads:[~2003-02-05 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 20:06 Cerberus Paul Larson
2003-02-05 22:14 ` Samuel Flory [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=3E418CDF.7020001@rackable.com \
--to=sflory@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.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