public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@google.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc1-mm1
Date: Mon, 16 Oct 2006 16:56:35 +0100	[thread overview]
Message-ID: <4533ABB3.1070104@shadowen.org> (raw)
In-Reply-To: <452D6921.5010300@us.ibm.com>

Badari Pulavarty wrote:
> Martin J. Bligh wrote:
>> Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc1/2.6.19-rc1-mm1/
>>>
>>>
>>>
>>>
>>>   
>> fsx seems to fail now, across several different machines.
>>
>> http://test.kernel.org/functional/index.html
>>
>>
>> and drill down under "regression" on the failing ones.
>>
>> eg, see end of
>> http://test.kernel.org/abat/54516/debug/test.log.1 (i386)
>> and
>> http://test.kernel.org/abat/54503/debug/test.log.1 (x86_64)
>>
> 
> I am seeing fsx failures on 1k/2k ext3 filesystems, but not on 4k.
> Do you know the filesystem type & blocksize ?

Ok.  I've been poking at these results to try and get you these answers.
 In the process I noted that the benchmark was recently reviewed and
overhauled.  Looking at the changes it looks like we are now reporting
the results from some tests which are backgrounded for additional load,
which would not have previously been reported.  So this might not be a
new phenomenon.  We have some stable tests coming through now, so I
should be able to use them as a reference to be sure.

Here are the ones which are failing currently, note that the 139 at the
start is the exit status as reported by the shell, so SIGSEGV:

bl6-13: x86_64 ext3
-------------------
139 ./fsx-linux -l 500000 -r 4096 -t 2048 -w 2048 -Z -R -W -N 10000
test/junkfile
139 ./fsx-linux -N 10000 -o 128000 -A -l 500000 -r 512 -t 4096 -w 1024
-Z -R -W test/junkfile


elm3b239: x86_64 reiserfs
-------------------------
139 ./fsx-linux -N 10000 -o 8192 -A -l 500000 -r 1024 -t 2048 -w 2048 -Z
-R -W test/junkfile
139 ./fsx-linux -N 10000 -o 128000 -r 2048 -w 4096 -Z -R -W test/junkfile
139 ./fsx-linux -N 10000 -o 8192 -A -l 500000 -r 1024 -t 2048 -w 1024 -Z
-R -W test/junkfile

I have also seen the following style messages on 19-rc1-mm1:

short write: 0x15000 bytes instead of 0xf000

Note that this really does mean a _long_ write!

-apw

  reply	other threads:[~2006-10-16 15:57 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  7:09 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  7:20 ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10  7:45   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  8:03     ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10 13:14       ` RSS accounting (was: Re: 2.6.19-rc1-mm1) Peter Zijlstra
2006-10-10 16:13         ` Arjan van de Ven
2006-10-10 23:54           ` Eric W. Biederman
2006-10-11  8:47             ` Arjan van de Ven
2006-10-11 12:07               ` Eric W. Biederman
2006-10-11 13:55                 ` Arjan van de Ven
2006-10-11 17:15                   ` Chen, Kenneth W
2006-10-11 22:36                     ` Benjamin LaHaise
2006-10-10  7:31 ` 2.6.19-rc1-mm1 Miguel Ojeda
2006-10-10  8:10   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10  9:57     ` 2.6.19-rc1-mm1 Miguel Ojeda
2006-10-10 18:25       ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 12:19 ` 2.6.19-rc1-mm1 Theodore Tso
2006-10-10 12:26   ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-10 16:21   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 13:10 ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 14:04   ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11  5:35     ` 2.6.19-rc1-mm1 Neil Brown
2006-10-11 10:48       ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11 11:23         ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-11 13:08           ` _cpu_down deadlock [was Re: 2.6.19-rc1-mm1] Neil Brown
2006-10-11 13:32             ` Rusty Russell
2006-10-11 16:39             ` Andrew Morton
2006-10-11 23:46               ` Neil Brown
2006-10-12  6:51                 ` Arjan van de Ven
2006-10-12  7:53                   ` SPAM: " Neil Brown
2006-10-12  8:04                     ` Andrew Morton
2006-10-13  4:49                       ` Neil Brown
2006-10-10 15:47 ` BUG in filp_close() (was: Re: 2.6.19-rc1-mm1) Dave Kleikamp
2006-10-10 22:07   ` Dave Kleikamp
2006-10-10 22:14     ` Vadim Lobanov
2006-10-10 22:38     ` Vadim Lobanov
2006-10-10 16:09 ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 19:04   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 21:44     ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-10 21:52       ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-20 20:44         ` 2.6.19-rc1-mm1 Thomas Gleixner
2006-10-10 17:15 ` BUG() in copy_fdtable() with 64K pages (2.6.19-rc1-mm1) Olof Johansson
2006-10-10 19:34   ` Andrew Morton
2006-10-10 20:20   ` Linas Vepstas
2006-10-10 20:31     ` Vadim Lobanov
2006-10-10 23:05       ` Linas Vepstas
2006-10-10 18:09 ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 19:25   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 19:41     ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 23:10     ` 2.6.19-rc1-mm1 Paul Mackerras
2006-10-10 23:16       ` 2.6.19-rc1-mm1 Jeremy Fitzhardinge
2006-10-10 23:37       ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-10 22:17 ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11  6:56   ` 2.6.19-rc1-mm1 Arjan van de Ven
2006-10-11  3:13 ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11  4:01   ` 2.6.19-rc1-mm1 Andrew Morton
     [not found]     ` <1160578934.1447.1.camel@dyn9047017100.beaverton.ibm.com>
2006-10-11 16:56       ` 2.6.19-rc1-mm1 (ext4 problem ?) Andrew Morton
2006-10-11 17:08         ` Badari Pulavarty
2006-10-11 12:51   ` 2.6.19-rc1-mm1 Theodore Tso
2006-10-11 19:54 ` 2.6.19-rc1-mm1 Martin J. Bligh
2006-10-11 21:58   ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-16 15:56     ` Andy Whitcroft [this message]
2006-10-11 19:59 ` 2.6.19-rc1-mm1 Martin J. Bligh
2006-10-11 20:10   ` 2.6.19-rc1-mm1 Michal Piotrowski
2006-10-11 21:47   ` 2.6.19-rc1-mm1 Andrew Morton
2006-10-12 10:22     ` 2.6.19-rc1-mm1 Andy Whitcroft
2006-10-12 18:09     ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-12 18:52       ` 2.6.19-rc1-mm1 Vadim Lobanov
2006-10-12 19:01         ` 2.6.19-rc1-mm1 Badari Pulavarty
2006-10-11 21:19 ` 2.6.19-rc1-mm1 Michael Lothian
2006-10-12 12:18 ` 2.6.19-rc1-mm1 - locks when using "dd bs=1M" from card reader Helge Hafting
2006-10-12 18:29   ` Andrew Morton
2006-10-13 13:11     ` Helge Hafting
2006-10-13 16:29       ` Andrew Morton
2006-10-13 18:10         ` [linux-usb-devel] " Alan Stern
2006-10-18  9:31           ` Helge Hafting
2006-10-18 16:26             ` Alan Stern
2006-10-19 12:25               ` Helge Hafting
2006-10-19 18:40                 ` Alan Stern
2006-10-19 18:57                   ` Christopher "Monty" Montgomery
2006-10-20 11:44                   ` Helge Hafting
2006-10-20 15:55                     ` Alan Stern
2006-10-23  9:12                       ` Helge Hafting
2006-10-23 14:13                         ` Alan Stern
2006-10-23 20:36                       ` Christopher "Monty" Montgomery
2006-10-24 10:16                         ` Helge Hafting
2006-10-24 14:09                           ` Alan Stern
2006-10-12 18:37 ` 2.6.19-rc1-mm1 Valdis.Kletnieks

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=4533ABB3.1070104@shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@google.com \
    --cc=pbadari@us.ibm.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