Date: Wed, 2 Jul 2003 15:53:30 -0700
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Yet another SDET hang (73-mm3) ... yawn
Message-Id: <20030702155330.7d879299.akpm@digeo.com>
In-Reply-To: <570860000.1057184743@flay>
References: <570860000.1057184743@flay>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 819
Lines: 23

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> 2.5.73-mm3 + feral + highpte (ext2)
> 
> Seems to be all wedged up on io_schedule. Not sure if it was
> highpte that caused this or not, but I'd done one run on ext2
> and one on ext3 without it, and they worked fine.

highpte, or highpmd?

I assume the latter.  But either way, it would be an odd correlation.

It looks more like the block layer or device driver blew a fuse.  The usual
deal: make it repeatable, then try `elevator=deadline', then try a
different driver..

Oh, and write OpenSDET while you're at it.  grr.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/