mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: maney@pobox.com
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stephan von Krawczynski <skraw@ithnet.com>
Subject: Re: 2.4.22-rc2 ext2 filesystem corruption
Date: 13 Aug 2003 20:40:13 +0100	[thread overview]
Message-ID: <1060803612.9130.37.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <20030813181330.GA1122@furrr.two14.net>

On Mer, 2003-08-13 at 19:13, Martin Maney 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. 

Ok

> I suppose the obvious bandaid would be to add a config option or yet
> another /proc/something kluge to let Promise chips be throttled on
> purpose, rather than fortuitously.  For my own use, I think I'm just
> going to reconfigure to avoid the Promise controller on this machine. 

I think the real thing is to find the bug. I guess pdc202xx_old.c needs
an audit at this point.

> I do have one casual question, if someone should have the answer.  The
> driver only talks about a 66MHz high speed; does that mean that the
> 20265 never gets run at its full speed under Linux, or is it just old
> terminology from back when UDMA66 was the top speed?

The latter. 


  reply	other threads:[~2003-08-13 19:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12  3:58 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 [this message]
2003-08-16  6:35                   ` Martin Maney
2003-08-17  0:09                     ` Mike Fedyk
2003-08-13 22:58                 ` Nerijus Baliunas
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=1060803612.9130.37.camel@dhcp23.swansea.linux.org.uk \
    --to=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

all inboxes | Powered by JetHome®