From: "Randy.Dunlap" <rddunlap@osdl.org>
To: root@mauve.demon.co.uk
Cc: stephane.wirtel@belgacom.net, linux-kernel@vger.kernel.org
Subject: Re: How to test the new kernel 2.6.0-test1 ?
Date: Wed, 16 Jul 2003 08:16:39 -0700 [thread overview]
Message-ID: <20030716081639.4f40b6b0.rddunlap@osdl.org> (raw)
In-Reply-To: <200307161025.LAA01549@mauve.demon.co.uk>
On Wed, 16 Jul 2003 11:25:18 +0100 (BST) root@mauve.demon.co.uk wrote:
| > I am using the kernel 2.6.0-test1 on my computer, and it works perfectly.
| >
| > Which are the weaknesses of the new kernel, an idea ?
|
| It almost certainly has bugs.
| Most of the ones present probably don't show up much on an average
| machine, with an average load.
|
| Try the edge cases, such as plugging in twenty thousand USB mice, running
| it on a 386/20 with 4Mb ram, unplugging USB devices when in use, ...
|
| The rarer bugs that do present on an average machine, with average loading
| just need more people to test, and report oopses or other errors related
| to the kernel.
|
| Just running it helps, if only because it lowers the probability of such
| bugs being present before 2.6.0 is released.
The I/O schedulers and process(or) scheduler want to be beaten on
very badly. For process scheduler, try playing music and writing
a CD while building kernels etc. and see how well you can move the
mouse around in X.
--
~Randy
| http://developer.osdl.org/rddunlap/ | http://www.xenotime.net/linux/ |
next prev parent reply other threads:[~2003-07-16 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 8:27 Stephane Wirtel
2003-07-16 10:25 ` root
2003-07-16 15:16 ` Randy.Dunlap [this message]
2003-07-16 17:33 ` 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=20030716081639.4f40b6b0.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@mauve.demon.co.uk \
--cc=stephane.wirtel@belgacom.net \
/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
all inboxes | Powered by JetHome®