public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Mynarik <mynarikj@phoenix.inf.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6,2.4] HPT366 (on Abit BP6) + Seagate 7000.7 + DMA = kernel halted
Date: Thu, 15 Jan 2004 17:29:27 +0100	[thread overview]
Message-ID: <1074184167.27869.19.camel@narsil> (raw)
In-Reply-To: <1074178780.1400.34.camel@hostmaster.org>

On Thu, 2004-01-15 at 15:59, Thomas Zehetbauer wrote:
> Must be a problem with the harddisk; I do also have a Abit BP6 board
> with two WD800JB which work fine on the HPT366 controller. Maybe you
> should try to connect them to one of the PIIX4 IDE channels. Btw: I do
> have CONFIG_IDEDMA_PCI_AUTO enabled so I do not even need to use hdparm
> to enable DMA.
> 

It supports my idea that linux kernel driver miss some 'special'
initialization for Seagate disk. But I need to try HighPoint's own
driver first, hopefully during weekend.

I also know that's not problem of AUTO DMA, I tried it and it didn't
change anything. During boot driver reports that my disk can do only
PIO.

However I am myself not so sure if I should use the HPT366 or the PIIX4
> controller as I got better cache read throughput (hdparm -T) with the
> PIIX4 controller and could avoid sharing an interrupt. Maybe someone
> here is willing to share some piece of advice?
> 

The problem with faster controller is a bit funny. I suppose that the
HPT366 controller is there because of its ability to run UDMA66, so that
it should be faster.

Anyway, thanks for your comments.

Pogo

-- 
Jan Mynarik <mynarikj@phoenix.inf.upol.cz>


      reply	other threads:[~2004-01-15 16:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 18:11 [2.6,2.4] HPT366 (on Abit BP6) + Seagate 7000.7 + DMA = kernel halted Jan Mynarik
2004-01-15 14:59 ` Thomas Zehetbauer
2004-01-15 16:29   ` Jan Mynarik [this message]

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=1074184167.27869.19.camel@narsil \
    --to=mynarikj@phoenix.inf.upol.cz \
    --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