public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "M.H.VanLeeuwen" <vanl@megsinet.net>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does kernel require IDE enabled in BIOS to access HD, FS errors?
Date: Mon, 09 Jul 2001 22:41:38 -0500	[thread overview]
Message-ID: <3B4A7972.F0CFBACE@megsinet.net> (raw)
In-Reply-To: <3B492324.E36B86AF@linux-ide.org>

Andre,

I had a chance to play a little more today, here is what I've come up with:

a. w/ hdc disable in BIOS, changing the PIO mode to 0 or 1 seems to allow the
   system to run error free.  PIO mode 3 still has silent FS corruption issues.

b. w/ hdc enabled in BIOS, the PIO mode doesn't seem to matter. (except for speed;)

c. CONFIG_IDEDMA_PCI_AUTO affects the number of interrupts needed to complete
   each block xfer.  With it enabled the number of IRQ's per second ~600.
   With it disabled ~2/block or 5000-6000 per second.  I thought from the dmesg
   output that DMA was disabled and this option should have no affect.

   > CMD646: IDE controller on PCI bus 00 dev 10
   > CMD646: chipset revision 1
   > CMD646: not 100% native mode: will probe irqs later
   > CMD646: chipset revision 0x01, MultiWord DMA Limited, IRQ workaround enabled
   > CMD646: simplex device:  DMA disabled
   > ide0: CMD646 Bus-Master DMA disabled (BIOS)
   > CMD646: simplex device:  DMA disabled
   > ide1: CMD646 Bus-Master DMA disabled (BIOS)

d. CONFIG_IDEDMA_PCI_AUTO does not seem to affect the outcome of "a" or "b" above.

Martin

andre@linux-ide.org wrote:
> 
> Martin, you have an old beast that there are problems in how the chipset
> was deployed.
> How are you confirming the corruption against the various layers in the
> kernel?
> If you would like patches & tests to verify I will send them to you.
> 
> Cheers
> 
> --
> Andre Hedrick
> Linux ATA Development
> ASL Kernel Development
> -----------------------------------------------------------------------------
> ASL, Inc.                                     Toll free: 1-877-ASL-3535
> 1757 Houret Court                             Fax: 1-408-941-2071
> Milpitas, CA 95035                            Web: www.aslab.com

  parent reply	other threads:[~2001-07-10  3:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09  3:21 Does kernel require IDE enabled in BIOS to access HD, FS errors? andre
2001-07-09 12:30 ` M.H.VanLeeuwen
2001-07-10  3:41 ` M.H.VanLeeuwen [this message]
2001-07-10  6:37   ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2001-07-08 14:41 Adam Kropelin
2001-07-07  5:25 M.H.VanLeeuwen
2001-07-07 13:18 ` Jim Roland
2001-07-07 13:47   ` M.H.VanLeeuwen
2001-07-07 20:42     ` Jim Roland
2001-07-07 20:50       ` Rik van Riel

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=3B4A7972.F0CFBACE@megsinet.net \
    --to=vanl@megsinet.net \
    --cc=andre@linux-ide.org \
    --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