From: Jeff Garzik <jgarzik@pobox.com>
To: Paul Larson <plars@linuxtestproject.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.60 cheerleading...
Date: Wed, 12 Feb 2003 11:09:22 -0500 [thread overview]
Message-ID: <3E4A71B2.8040007@pobox.com> (raw)
In-Reply-To: <1045065615.22294.11.camel@plars>
Paul Larson wrote:
> On Wed, 2003-02-12 at 09:52, Jeff Garzik wrote:
>
>>Just to counteract all the 2.5.60 bug reports...
>>
>>After the akpm wave of compile fixes, I booted 2.5.60-BK on my Wal-Mart
>>PC [via epia], and ran LTP on it, while also stressing it using
>>fsx-linux in another window. The LTP run showed a few minor failures,
>>but overall 2.5.60-BK is surviving just fine, and with no corruption.
>
> Can you send me your list of failures and version of LTP? I'd like to
> make sure they match up with the known list of problems.
Version is CVS-latest, checked out last night.
Some of the failures were obvious: kernel module syscalls were failing,
as I would expect them to if they had not been updated for 2.5.x module
support. There were also a couple signal-related things, IIRC.
Unexpected failures included some file locking test failures.
Anyway, don't worry... you will be getting more concrete info soon :) I
am tracking down right now why the 2.5.x floppy driver ends all I/O
requests with an error. After that, I'll have output from a full LTP
run for you :)
next prev parent reply other threads:[~2003-02-12 16:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 15:52 2.5.60 cheerleading Jeff Garzik
2003-02-12 16:00 ` Paul Larson
2003-02-12 16:09 ` Jeff Garzik [this message]
2003-02-12 18:07 ` Dave Jones
2003-02-12 18:44 ` John Bradford
2003-02-12 18:17 ` Scott Robert Ladd
2003-02-12 18:41 ` John Bradford
2003-02-12 18:55 ` Dave Jones
2003-02-12 18:43 ` Paul Larson
2003-02-12 19:33 ` Edesio Costa e Silva
2003-02-13 15:29 ` Paul Larson
2003-02-13 15:54 ` Jörn Engel
2003-02-13 16:03 ` Dave Jones
2003-02-13 16:55 ` Paul Larson
2003-02-13 17:11 ` John Bradford
2003-02-13 18:04 ` Paul Larson
2003-02-13 18:23 ` John Bradford
2003-02-13 21:16 ` Paul Larson
2003-02-13 21:38 ` Jeff Garzik
2003-02-13 21:54 ` John Bradford
2003-02-13 21:57 ` Paul Larson
2003-02-13 22:11 ` John Bradford
2003-02-13 22:20 ` Valdis.Kletnieks
2003-02-13 22:39 ` Paul Larson
2003-02-13 22:43 ` Randy.Dunlap
2003-02-13 22:53 ` Paul Larson
2003-02-13 22:58 ` John Bradford
2003-02-14 6:36 ` Paul Larson
2003-02-20 22:29 ` Timothy D. Witham
2003-02-20 22:42 ` Jeff Garzik
2003-02-20 22:46 ` Timothy D. Witham
2003-02-14 1:21 ` Martin J. Bligh
2003-02-14 1:32 ` Linus Torvalds
2003-02-14 3:24 ` Mike Dresser
2003-02-14 9:08 ` John Bradford
2003-02-14 4:10 ` Werner Almesberger
2003-02-13 17:06 ` Jeff Garzik
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=3E4A71B2.8040007@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.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