From: Andre Hedrick <andre@aslab.com>
To: Daniela Engert <dani@ngrt.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dan <lung@theuw.net>
Subject: Re: Repeatable File Corruption (ECS K7S5A w/SIS735)
Date: Thu, 25 Oct 2001 23:02:02 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10110252300580.800-100000@master.linux-ide.org> (raw)
In-Reply-To: <20011026045736.77F08106D0@mail.medav.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-UNKNOWN, Size: 2068 bytes --]
Daniela,
I just love it when you bust my crops, dear ;-)
How about some init code to resolve the problem?
Cheers,
On Fri, 26 Oct 2001, Daniela Engert wrote:
> On Thu, 25 Oct 2001 22:21:47 -0400 (EDT), dan wrote:
>
> > It is repeatable and verified on other boards of the same model. This
> >just started happening when I upgraded the system. The following is a
> >link to the ECS K7S5A board in question, the SIS735 chipset, and a
>
> > hda: ST36421A, ATA DISK drive
> > hdb: QUANTUM FIREBALLP LM10.2, ATA DISK drive
> > hdc: IC35L060AVER07-0, ATA DISK drive
>
> >The problem only went away when I replaced the motherboard. I also
> >haven't had any file corruption issues running Windows2000 on the same
> >hardware with the same files. I moved all of the hardware in the original
> >system to a new motherboard (ASUS A7A266) and the problem went away.
>
> >I have CC'd the IDE chipset maintainer because I can only assume it might
> >be related.
>
> It very likely is. The current Linux SiS IDE driver doesn't initialize
> the the EIDE controller in the SiS735 (and most likely all other
> ATA/100 capable members, too) correctly.
>
> The SiS735 IDE cycle timing registers have a layout that is different
> from the older predecessors!
>
> >From my experiences, drivers taking this not into account *do* actually
> work most of the time even if the timing of the layer 0 communication
> protocol is wrong, but fail mysteriously sometimes. Andre needs to
> update the SiS5513 code.
>
> Ciao,
> Dani
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Daniela Engert, systems engineer at MEDAV GmbH
> Gräfenberger Str. 34, 91080 Uttenreuth, Germany
> Phone ++49-9131-583-348, Fax ++49-9131-583-11
>
>
Andre Hedrick
CTO ASL, Inc.
Linux ATA Development
-----------------------------------------------------------------------------
ASL, Inc. Tel: (510) 857-0055 x103
38875 Cherry Street Fax: (510) 857-0010
Newark, CA 94560 Web: www.aslab.com
next prev parent reply other threads:[~2001-10-26 6:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 2:21 dan
2001-10-26 2:26 ` Andre Hedrick
2001-10-26 3:56 ` lung
2001-10-26 5:53 ` Daniela Engert
2001-10-26 6:02 ` Andre Hedrick [this message]
2001-10-26 6:08 ` lung
2001-10-26 6:35 ` Andre Hedrick
2001-10-26 6:41 ` lung
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=Pine.LNX.4.10.10110252300580.800-100000@master.linux-ide.org \
--to=andre@aslab.com \
--cc=dani@ngrt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lung@theuw.net \
/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®