From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Yet another SDET hang (73-mm3) ... yawn
Date: Wed, 02 Jul 2003 15:57:13 -0700 [thread overview]
Message-ID: <575880000.1057186633@flay> (raw)
In-Reply-To: <20030702155330.7d879299.akpm@digeo.com>
--On Wednesday, July 02, 2003 15:53:30 -0700 Andrew Morton <akpm@digeo.com> wrote:
> "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.
The former, I think. I turned on "3rd level pagetables in high memory". Presumably that's still just highpte.
larry:~/linux/2.5.73-mm3# grep HIGH .config
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
CONFIG_HIGHMEM=y
CONFIG_HIGHPTE=y
# CONFIG_DEBUG_HIGHMEM is not set
But yes, it's probably coincidence.
> 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..
Yeah, I'll beat her some more later.
> Oh, and write OpenSDET while you're at it. grr.
Use reaim7. But maybe I should write open-16-way-hardware with a
subtext of race-conditions-we-find? ;-)
M.
next prev parent reply other threads:[~2003-07-02 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 22:25 Yet another SDET hang (73-mm3) ... yawn Martin J. Bligh
2003-07-02 22:53 ` Andrew Morton
2003-07-02 22:57 ` Martin J. Bligh [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-03 15:30 Benjamin Stuhl
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=575880000.1057186633@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.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.