From: Nerijus Baliunas <nerijus@users.sourceforge.net>
To: maney@pobox.com, Marcelo Tosatti <marcelo@conectiva.com.br>,
Martin Maney <maney@two14.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Stephan von Krawczynski <skraw@ithnet.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-rc2 ext2 filesystem corruption
Date: Thu, 14 Aug 2003 01:58:02 +0300 (EEST) [thread overview]
Message-ID: <S271812AbTHMW6L/20030813225811Z+15085@vger.kernel.org> (raw)
In-Reply-To: <20030813181330.GA1122@furrr.two14.net>
On Wed, 13 Aug 2003 13:13:30 -0500 Martin Maney <maney@two14.net> wrote:
> At this point the outcome was pretty much a foregone conclusion, but
> yep, reverting to ".id" stopped the corruption for this test case. As
> Alan said, it "fixed" it only because that incorrect test happens to
> force the driver to use the lower DMA speed. I had been about to
> report on that when your request for the explicit test arrived, but in
> short it's that rc1 (and earlier) were disabling the "66" clock speed,
> while rc2 was, correctly, finding no reason not to enable it. The real
> bug, be it hardware or software, is that enabling the higher speed
> causes the corruption.
Do you have the latest Promise BIOS? If not, does it still happen with
the latest one?
Regards,
Nerijus
next prev parent reply other threads:[~2003-08-13 22:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 3:58 2.4.22-rc2 ext2 filesystem corruption Martin Maney
2003-08-12 10:18 ` Stephan von Krawczynski
2003-08-12 13:12 ` Marcelo Tosatti
2003-08-12 13:42 ` Martin Maney
2003-08-12 14:10 ` Marcelo Tosatti
2003-08-12 15:14 ` Martin Maney
2003-08-12 16:58 ` Marcelo Tosatti
2003-08-12 17:11 ` Alan Cox
2003-08-12 16:56 ` Martin Maney
2003-08-12 17:09 ` Marcelo Tosatti
2003-08-12 21:36 ` Martin Maney
2003-08-13 11:28 ` Alan Cox
2003-08-13 11:37 ` Stephan von Krawczynski
2003-08-13 14:55 ` Marcelo Tosatti
2003-08-13 18:13 ` Martin Maney
2003-08-13 19:40 ` Alan Cox
2003-08-16 6:35 ` Martin Maney
2003-08-17 0:09 ` Mike Fedyk
2003-08-13 22:58 ` Nerijus Baliunas [this message]
2003-08-12 6:20 Alex Davis
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=S271812AbTHMW6L/20030813225811Z+15085@vger.kernel.org \
--to=nerijus@users.sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maney@pobox.com \
--cc=maney@two14.net \
--cc=marcelo@conectiva.com.br \
--cc=skraw@ithnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).