public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ward <gward@python.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: bugs@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: "hde: timeout waiting for DMA": message gone, same behaviour
Date: Fri, 21 Sep 2001 15:08:06 -0400	[thread overview]
Message-ID: <20010921150806.A2453@gerg.ca> (raw)
In-Reply-To: <20010921134402.A975@gerg.ca> <20010921205356.A1104@suse.cz>
In-Reply-To: <20010921205356.A1104@suse.cz>; from vojtech@suse.cz on Fri, Sep 21, 2001 at 08:53:56PM +0200

[my ATA/100 problem]
> Under 2.4.9, the boot-time delay is not quite as long, but it's still
> there.  And it's not nearly as noisy.  However, the end-result is the
> same: DMA is disabled for this drive; it's a lot slower than an ATA/100
> drive ought to be; if I force DMA back on, the first access to the drive
> has another looong delay that results in the kernel turning DMA back
> off.  Grumble.
> 
> This is a brand-new drive and brand-new cable.  The motherboard's only
> about 9 months old.
> 
> So: is this in fact a kernel problem? or is it more likely to be a cable
> problem, a motherboard problem, or a hard drive problem?

On 21 September 2001, Vojtech Pavlik said:
> Do you have the VIA IDE support enabled?

I have tried it both ways, but I think only with 2.4.2.  I've only tried
one 2.4.9 build, and that was with CONFIG_BLK_DEV_VIA82CXXX=y.  I've
just done another build with slightly different config settings
(suggestion from Mark Hahn), but haven't tried it yet.  It still has
both the VIA and Promise (CONFIG_BLK_DEV_PDC202XX=y) support enabled.

I'll report back when I've tried this kernel build.

        Greg
-- 
Greg Ward - Linux weenie                                gward@python.net
http://starship.python.net/~gward/
If ignorance is bliss, why aren't there more happy people?

  reply	other threads:[~2001-09-21 19:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-21 17:44 "hde: timeout waiting for DMA": message gone, same behaviour Greg Ward
2001-09-21 18:53 ` Vojtech Pavlik
2001-09-21 19:08   ` Greg Ward [this message]
2001-09-21 19:49     ` Greg Ward
2001-09-21 19:56       ` Vojtech Pavlik
2001-09-21 20:43         ` Greg Ward
2001-09-22  8:04           ` Vojtech Pavlik
2001-09-22 10:53             ` David Grant
2001-09-22 13:40               ` Eyal Lebedinsky
2001-09-22 15:09               ` Greg Ward
2001-09-22 15:58                 ` Alan Cox
2001-09-25 20:23                   ` Maxwell Spangler
2001-09-26  2:02                     ` David Grant
2001-09-26  2:18                       ` Maxwell Spangler
2001-09-22 20:07                 ` David Grant
2001-09-24  8:35                   ` Vojtech Pavlik
2001-09-24 18:37                     ` Eric W. Biederman
2001-09-24 22:44                       ` Vojtech Pavlik
2001-09-25  0:15                         ` Kevin P. Fleming
2001-10-01 14:03 ` Greg Ward

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=20010921150806.A2453@gerg.ca \
    --to=gward@python.net \
    --cc=bugs@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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