From: Nathan Black <NBlack@md.aacisd.com>
To: "'Jens Axboe'" <axboe@suse.de>
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 11:44:06 -0500 [thread overview]
Message-ID: <8FED3D71D1D2D411992A009027711D67185B@md> (raw)
It comes back with a command prompt. trying a "simple command... ps, ls
it does not return. The hard disks(hardware raid) light up. But it seems
like noone is home.
It doesn't oops in the 2.4.1-pre11 or 10.
That is a good thing.
-----Original Message-----
From: Jens Axboe [mailto:axboe@suse.de]
Sent: Monday, January 29, 2001 11:38 AM
To: Nathan Black
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bolck Device problem or Compaq Smart array 2 problem?
kernel -2.4 .0+
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 reply other threads:[~2001-01-29 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 16:44 Nathan Black [this message]
2001-01-29 16:51 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-01-29 16:47 Nathan Black
2001-01-29 16:06 Nathan Black
2001-01-29 16:38 ` Jens Axboe
2001-01-29 16:39 ` Dr. Michael Weller
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=8FED3D71D1D2D411992A009027711D67185B@md \
--to=nblack@md.aacisd.com \
--cc=axboe@suse.de \
--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 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®