public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4 ate my filesystem on rw-mount, getting closer
Date: Sun, 14 Jan 2001 23:32:08 +0100	[thread overview]
Message-ID: <20010114233208.A2487@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.30.0101141636350.6714-301000@svea.tellus> <Pine.LNX.4.30.0101141848330.7031-100000@svea.tellus>
In-Reply-To: <Pine.LNX.4.30.0101141848330.7031-100000@svea.tellus>; from tori@tellus.mine.nu on Sun, Jan 14, 2001 at 06:59:57PM +0100

On Sun, Jan 14, 2001 at 06:59:57PM +0100, Tobias Ringstrom wrote:
> 
> I should also add that the 3.11 driver seems to make things better, but
> not yet perfect.  My intuition tells me that I get CRC errors much sooner
> with 2.1e than with 3.11.
> 
> Has the timings changed from 2.1e to 3.11, and would it be easy to modify
> 3.11 to get extra safe/paranoid, but less high performance, timings?

If you use 'idebus=40' or 'idebus=50', the driver will add an extra
margin to the timings, trying to compensate for the 40 or 50 MHz PCI bus
it will be tricked to think it's working with.

This could add a data point, yes.

> Some extra data:
> * B seems to work in 2 with udma2
> * A seems to work in 2 with udma1, but not with udma2.

UDMA1 is 22.2 MB/sec, UDMA2 is 33.3. UDMA0 is 16.6.

Could you (if didn't already) send me the lspci -vvxxx after the -X65
(UDMA1) command, together with the one before? That also could tell
something.

> I wouldn't say it's rock solid, and I would not trust my data to any of
> these combinations, but at least it not break immmediately (i.e. for less
> than 1 GB written).

Actually, the CRC messages are safe and only mean a data transfer is
retried. That is, only if it doesn't fail every time. They happen on
many boards and drives using UDMA even under normal correct operation :(

> The worst combination is 2.4.0 with VIA 2.1e and A in 1.  Going from 2.1e
> to 3.11 helps, but it is still very bad.
> 
> I'd really like to be more precise, but there are too many combinations to
> try to try them all, and sometimes it fails right away, and sometimes
> after several hundred megabytes.

If 'fails after several hundred megabytes' only means a single CRC error
which is recovered from correctly, then that actually means 'working and
probably would work perfect with a shorter cable'.

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-14 22:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  9:15 2.4 ate my filesystem on rw-mount Tobias Ringstrom
2001-01-12 10:22 ` Alan Cox
2001-01-12 17:23   ` Martin Laberge
2001-01-12 19:51     ` Vojtech Pavlik
2001-01-12 19:49 ` Vojtech Pavlik
2001-01-13  8:12   ` Tobias Ringstrom
2001-01-13 14:35     ` Vojtech Pavlik
2001-01-13 16:20       ` Tobias Ringstrom
2001-01-13 22:36         ` 2.4 ate my filesystem on rw-mount, getting closer Tobias Ringstrom
2001-01-14  8:44           ` Vojtech Pavlik
2001-01-14  8:45             ` Tobias Ringstrom
2001-01-14  9:48               ` Vojtech Pavlik
2001-01-14 16:37                 ` Tobias Ringstrom
2001-01-14 17:59                   ` Tobias Ringstrom
2001-01-14 22:32                     ` Vojtech Pavlik [this message]
2001-01-23 21:39                       ` 2.4 ate my filesystem on rw-mount, summary Tobias Ringstrom

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=20010114233208.A2487@suse.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tori@tellus.mine.nu \
    /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