From: Paul Larson <plars@linuxtestproject.org>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Cerberus
Date: 05 Feb 2003 14:06:24 -0600 [thread overview]
Message-ID: <1044475584.30331.135.camel@plars> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
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.
Thanks,
Paul Larson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2003-02-05 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 20:06 Paul Larson [this message]
2003-02-05 22:14 ` Cerberus Samuel Flory
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=1044475584.30331.135.camel@plars \
--to=plars@linuxtestproject.org \
--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