From: Michael Frank <mhf@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test8/test9 repeatable lockups at high loads - please reproduce
Date: Tue, 28 Oct 2003 05:44:33 +0800 [thread overview]
Message-ID: <200310280544.33247.mhf@linuxmail.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 644 bytes --]
Using attached stress tests on a P4 with IDE, 2.6.0-test8/test9 lockup
repeatably within 5 minutes to an hour.
It is generally pssible to break into kdb debugger but not into kgdb.
Tests running fine with 2.4.22 and 2.4.21 for 100s of hours
Requirements:
gnu tool chain
X 3 or 4
configured ready to compile 2.4 or 2.6 kernel source tree linked to /usr/src/linuxtest
/tmp directory and/or $TEMP set to a user writable temporary directory
200MB spare disk space
How to use:
$ ln -s /usr/src/yourlinux /usr/src/linuxtest
$ tar jxf ti-tests.tar.bz2
to start the test:
$ ti-tests/ti 1
to stop the test
$ ti-tests/ti 0
Regards
Michael
[-- Attachment #2: ti-tests.tar.bz2 --]
[-- Type: application/x-tbz, Size: 35479 bytes --]
next reply other threads:[~2003-10-27 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 21:44 Michael Frank [this message]
2003-10-29 8:26 ` 2.6.0-test8/test9 repeatable lockups at high loads - please reproduce Michael Frank
2003-10-29 10:21 ` Michael Frank
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=200310280544.33247.mhf@linuxmail.org \
--to=mhf@linuxmail.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