public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@free.fr>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] 2.4.17-rc1, IDE : SIS735/SIS5513 unusable ?
Date: Sat, 22 Dec 2001 01:54:08 +0100	[thread overview]
Message-ID: <3C23D9B0.3010109@free.fr> (raw)

Short :

SIS735 IDE subsystem unreliable -> system unusable.

Long :

I recently purchased an ECS K7S5AL mb built around the SIS735 chipset. 
The system built around this mb worked perfectly for one week before 
failing to boot with root fs mount errors. Subsequent tries to reinstall 
  the OS failed : either during the RedHat 7.2 install (fs error) or on 
the first boot after install (root fs mount error).

I trust all other components of the system (except the RAM and PSU which 
I purchased recently too) as they were heavily used in a previous one 
without a glitch.

I saw one other bugreport on lklm from one person with several SIS735 
mbs all failing on IDE DMA transfers and hints in the following thread 
that the init code for the SIS5513 is not complete for the SIS735 and 
might lead to the kind of problem I encountered (stable operation for a 
while followed by an unusable IDE subsystem).

I'm now on the way of heavy testing (Clean install on a drive in a 
separate system, master of the drive, move in the not-so-cooperative mb 
and several iterations of test-screwup-master_recopy-test-... ). I'll 
test different BIOS revisions, ide kernel parameters while searching for 
the SIS735 technical specs and then attempts at kernel hacking.

I noticed Andre by private mail and posted a bugreport on sis support 
web site asking them to supply appropriate init code to him. Is there 
something else I can do (specific sis e-mail contacts for technical 
papers for example, preliminary patch to test) ?

Lionel


                 reply	other threads:[~2001-12-22  0:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C23D9B0.3010109@free.fr \
    --to=lionel.bouton@free.fr \
    --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