From: Jake Moilanen <moilanen@austin.ibm.com>
To: Leo Przybylski <leo@leosandbox.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: Blast and data miscompare
Date: Tue, 9 Nov 2004 09:34:00 -0600 [thread overview]
Message-ID: <20041109093400.34b49953@localhost> (raw)
In-Reply-To: <41847C52.8030702@leosandbox.org>
> I have tried searching on this issue, but found nothing. I heard from a
> kernel developer at work that a memory error was discovered recently in
> the linux 2.6 kernel that causes data miscompare errors in the generic
> scsi driver when executing blast tests.
>
> Does anyone know more about this???
Not sure if it's the same problem. But we were seeing a miscompare on
2.4 due to a incorrect COW happening, followed by a hardware hash hole
w/ PPC64.
To fix it we had to make sure that the PTE was cleared and the TLB's
flushed before the new PTE was established.
Martin, was this fixed on 2.6?
Thanks,
Jake
next prev parent reply other threads:[~2004-11-09 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 5:46 Blast and data miscompare Leo Przybylski
2004-11-09 15:34 ` Jake Moilanen [this message]
2004-11-09 15:43 ` Martin J. Bligh
2004-11-11 5:02 ` Paul Mackerras
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=20041109093400.34b49953@localhost \
--to=moilanen@austin.ibm.com \
--cc=leo@leosandbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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 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.