From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, rusty@rustcorp.com.au
Subject: Hackbench broken by 2.6.8-rc1+
Date: Tue, 27 Jul 2004 07:36:00 +1000 [thread overview]
Message-ID: <41057940.6090104@kolivas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
After a brief discussion with Rusty about hackbench he explained that it
was more a pass/fail benchmark than anything else - failing by running
forever. Well recently I noticed all kernels were doing it so did some
regression testing to see when it started. 2.6.7 runs fine, but
2.6.8-rc1 onwards get hard rebooted after 12 hours.
I've been using the 8x boxen at osdl with
TEST: hackbench on stp8-001 running PLM ID 3049 [ linux-2.6.7 ]
LILO: append = 'profile=2'
Script Params: 25 200
I'll investigate further to see if I can track down the patch that
started this but it may take some time. Suffice to say that the
2.6.8-rc* versions may not be safe in certain server settings until that
time.
Cheers,
Con
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
reply other threads:[~2004-07-26 21:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41057940.6090104@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.