mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis A. Montes" <lmontes@worldnet.att.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 filesystem corruption
Date: Sat, 9 Feb 2002 00:45:03 -0800	[thread overview]
Message-ID: <20020209004503.C662@penguin.montes2.org> (raw)
In-Reply-To: <200202030538.g135chu00602@penguin.montes2.org> <E16XMwN-0004UB-00@the-village.bc.nu>
In-Reply-To: <E16XMwN-0004UB-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Feb 03, 2002 at 05:44:19 -0800

On 2002.02.03 05:44 Alan Cox wrote:
> > this list to handle my SiS 735 chipset. It did seem more stable for a
> > while, until I decided to try and enable ultra dma 66 on my primary
> > drive. The two partitions that I had mounted got completely corrupted
> 
> How did you switch on UDMA66 ?
Well, when you mentioned this I remember a couple of things that I probably
shouldn't have done, that's why it took me so long to answer, I went back 
and
systematically tested different kernels on a test partition and taking 
note of
the hdparm's I used. I've still got a couple of kernels I want to test, so 
I
will post more complete results tomorrow. Still the answer seems to be that
2.4.5 is stable while 2.4.17 is not.
But to answer your question, I downloaded a utility from WD that switches 
the
drive from udma 33 to udma 66, and I then boot linux and type
hdparm -c 1 -d 1 -m 8
Last time before I wrote I also used -X66, but I'm not sure that's a good
idea ...

> 
> > hda: Western Digital Caviar WDC AC313000R (it is *not* in the udma
> > black list, should it be?)
> 
> There is certainly no evidence it should be

> 
> > hdb: Western Digital Caviar WDC AC23200L (this one is in the black
> > list, but is not being mounted, so it shouldn't matter, right?)
> 
> Unknown. But you can test that
> 
> > - Was there some change between 2.4.5 and 2.4.17 that could have
> >   introduced problems in the IDE layer? I really tried to test 2.4.5
> 
> For the SiS possibly.
> 
There is something in vanilla 2.4.17. Using the exact same .config and
filesystem as the one for 2.4.5 it crashes while 2.4.5 remains stable.
OTOH, I've finally managed to have an stable system for a week (I'm
actually using it right now) with 2.4.17. The difference is that
it's got the sis5513.c patch from Lionel Bouton that I found in
the lkml. I'm not using dma yet, though! The driver, as the previous
driver for this chipset, disables everything by default (but even
that didn't help for plain 2.4.17) That's what I'm going to test next,
using the above mentioned hdparm line.

  reply	other threads:[~2002-02-09  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03  5:38 Luis A. Montes
2002-02-03  6:01 ` Pierre Rousselet
2002-02-03 13:44 ` Alan Cox
2002-02-09  8:45   ` Luis A. Montes [this message]
2002-02-04 16:55 ` Denis Vlasenko
2002-02-09 19:06 Luis A. Montes

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=20020209004503.C662@penguin.montes2.org \
    --to=lmontes@worldnet.att.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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®