From: "Paul Rolland" <rol@as2917.net>
To: "'Paul Larson'" <plars@linuxtestproject.org>,
"'Rusty Lynch'" <rusty@linux.co.intel.com>
Cc: "'lkml'" <linux-kernel@vger.kernel.org>
Subject: Re: Available watchdog test cases
Date: Sun, 9 Mar 2003 10:40:58 +0100 [thread overview]
Message-ID: <008501c2e61f$fdd0a800$2101a8c0@witbe> (raw)
In-Reply-To: <1046880939.26974.21.camel@plars>
Just a quick question : is there an easy to force the kernel to Oops,
to make sure that the watchdog will even be working under such
conditions ?
I know people are all trying to avoid Oops... but I think the testplan
should include that too...
Regards,
Paul
> On Tue, 2003-03-04 at 15:04, Rusty Lynch wrote:
> > The test cases that I have been using for testing my
> watchdog work are
> > available at
> > http://www.stinkycat.com/patches/watchdog_stuff/watchdog_test.tar.gz
> >
> > The test are for both the legacy (well, current) /dev/watchdog
> > interface and my proposed sysfs based interface.
> Thanks a bunch Rusty, I'll take a look at them for LTP.
next prev parent reply other threads:[~2003-03-09 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 21:04 Available watchdog test cases Rusty Lynch
2003-03-05 16:15 ` Paul Larson
2003-03-09 9:40 ` Paul Rolland [this message]
2003-03-10 5:23 ` Rusty Lynch
2003-03-10 7:02 ` Paul Rolland
2003-03-11 4:35 ` Randy.Dunlap
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='008501c2e61f$fdd0a800$2101a8c0@witbe' \
--to=rol@as2917.net \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.org \
--cc=rusty@linux.co.intel.com \
/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