From: maney@two14.net (Martin Maney)
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org,
Stephan von Krawczynski <skraw@ithnet.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.22-rc2 ext2 filesystem corruption
Date: Tue, 12 Aug 2003 16:36:45 -0500 [thread overview]
Message-ID: <20030812213645.GA1079@furrr.two14.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0308121408450.10045-100000@logos.cnet>
On Tue, Aug 12, 2003 at 02:09:53PM -0300, Marcelo Tosatti wrote:
> Well, rc2 had a Promise change. I'm not sure if it could be the cause, but
> lets check.
> Please try -rc2 with the following patch unpplied (patch -R):
Oops, I overlooked the change. Tried it with a relatively
stripped-down 22-rc2 build (slimmed the vmlinuz down by about 100K),
but that made no difference. I popped a CMD648-based card in, disabled
the on-board Promise chip, and it booted right up and works fine with
22-rc2. So if the .id -> .present is the only change that affected the
Promise driver (I did some looking for obvious, but gave up after
realizing that unless the change actually had a /* borks Promise IDE
controllers*/ in it I wouldn't be likely to recognize it), then I guess
that's it.
> # [PATCH] PATCH: Promise cable
> #
> # The old driver used to check .id was NULL to detect drive absent
> # (which is wrong but generally worked) with the IDE changes it always
> # got it wrong. This fixes it to test .present instead.
> #
> # Without this fix it mistakenly assumes that the empty drive slot
> # cannot do UDMA66/100/133
Does this really mean that the Promise has been running at only 33MHz
all along, and that with this fix it stopped choking the speed and
that's the cause of the problem? I know that back when I first setup
this drive on the Promise (over a year ago - I'm pretty sure I was
runnign 2.2.latest back then and had to jumper the drive to get around
the 64K cylinders problem) I know I saw transfer speeds greater than
33MB reported by hdparm -T.
Okay, for completeness I should back out that change and retest it with
the Promise, and I'll try to remember to throw a quick throughput test
in just to see what it's been doing to me. ;-)
BTW, yes, I am (and have been) using an 80-pin cable with this drive.
--
Faced with the choice between changing one's mind and proving there is
no need to do so, almost everyone gets busy on the proof. -- JKG
next prev parent reply other threads:[~2003-08-12 21:38 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20030812213645.GA1079@furrr.two14.net \
--to=maney@two14.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maney@pobox.com \
--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