From: Jens Axboe <axboe@suse.de>
To: Nathan Black <NBlack@md.aacisd.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bolck Device problem or Compaq Smart array 2 problem? kernel -2.4 .0+
Date: Mon, 29 Jan 2001 17:38:15 +0100 [thread overview]
Message-ID: <20010129173815.C23061@suse.de> (raw)
In-Reply-To: <8FED3D71D1D2D411992A009027711D671859@md>
In-Reply-To: <8FED3D71D1D2D411992A009027711D671859@md>; from NBlack@md.aacisd.com on Mon, Jan 29, 2001 at 11:06:15AM -0500
On Mon, Jan 29 2001, Nathan Black wrote:
> Here are my results.
>
> 2.2.18- works fine. 24 MBytes/sec at 100+ gigabytes (16GB looped many times
> ( lseek64(FD,SEEK_SET,0) )).
>
> 2.4.0 release SMP and Uniprocessor with NMI on- Kernel oops. I can reproduce
> if necessary( oops at about 700 MB) sometimes more, sometime less. (In
> BDFLUSH if I recall)
>
> 2.4.0 release UniProcessor NMI off- Works like the 2.2.18
>
> 2.4.1-pre10 & 11- Works but system becomes unusable(requires reboot) after
> completing.
Unusable how? Does it hang or oops? Does nmi and up/smp make any
differences in 2.4.1-preXX?
I did some fixes for cpq after the blk merge in 2.4.1-pre, and got
reports that it works. However, I don't have the necessary hardware
to test myself.
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 16:06 Bolck Device problem or Compaq Smart array 2 problem? kernel -2.4 .0+ Nathan Black
2001-01-29 16:38 ` Jens Axboe [this message]
2001-01-29 16:39 ` Dr. Michael Weller
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 16:44 Nathan Black
2001-01-29 16:51 ` Jens Axboe
2001-01-29 16:47 Nathan Black
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=20010129173815.C23061@suse.de \
--to=axboe@suse.de \
--cc=NBlack@md.aacisd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.