All of lore.kernel.org
 help / color / mirror / Atom feed
From: maney@two14.net (Martin Maney)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: maney@pobox.com, 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: Sat, 16 Aug 2003 01:35:12 -0500	[thread overview]
Message-ID: <20030816063512.GA1075@furrr.two14.net> (raw)
In-Reply-To: <1060803612.9130.37.camel@dhcp23.swansea.linux.org.uk>

On Wed, Aug 13, 2003 at 08:40:13PM +0100, Alan Cox wrote:
> I think the real thing is to find the bug. I guess pdc202xx_old.c needs
> an audit at this point.

I've got no problem with that, of course.  I guess I was thinking
pessimistic thoughts about finding a fix for this for .22

> > 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. 

So what I'm seeing is a failure at 100MHz operation.  Is there any way
to put the Promise into 66MHz mode (other than using a drive that runs
no faster)?  Because at this point I don't have any practical way to
rule out the possibility that the cable/drive are what's marginal at
100MHz; aside from the Promise, I don't have anything faster than a
UDMA66 card (which works fine with them).

I also managed to find a useful non-broken link on ASUS's web site and
found that they had snuck out a BIOS update later than the latest I had
previously known of, and it did include a minor change in the Promise
BIOS (from 2.01 build 19 to build 35).  Made no difference, though: the
50MB copy still failed as usual with 22-rc2.

-- 
The Internet discourages reflection and deep thought. It
encourages just glossing over, as quick as possible. The
Internet is a terrific way to look up facts and a terrible
way to get a story.  -- Clifford Stoll
                                          

  reply	other threads:[~2003-08-16  6:35 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 [this message]
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=20030816063512.GA1075@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 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.