mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@aslab.com>
To: dan <lung@theuw.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Repeatable File Corruption (ECS K7S5A w/SIS735)
Date: Thu, 25 Oct 2001 23:35:37 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10110252331250.800-100000@master.linux-ide.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0110260205260.5131-100000@narboza.theuw.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-UNKNOWN, Size: 3053 bytes --]


On Fri, 26 Oct 2001 lung@theuw.net wrote:

> 
> I've received one report of someone using the same motherboard, but using
> SCSI and having no issues.  I think after a little testing, this will
> point directly at IDE.
> 
> I've made me test file available for more testing, but I think I can
> dig up an old SCSI drive tomorrow to test this myself.
> 
> 
> 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
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
> 
> 


Dan,

If I give you a patch and a test tool kit, will you run destructive data
tests?  If the low-level tool passes and the high-level fails we know it
is not in the driver.  If the low-level fails then it is in the chipset
setup code or the main loop.  If neither fail then it is random wrt the
driver or the block layer above and time to get worried.

Can you scratch a disk of content?

Regards,

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


  reply	other threads:[~2001-10-26  6:35 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
2001-10-26  6:08   ` lung
2001-10-26  6:35     ` Andre Hedrick [this message]
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.10110252331250.800-100000@master.linux-ide.org \
    --to=andre@aslab.com \
    --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®