From: Vojtech Pavlik <vojtech@suse.cz>
To: Greg Ward <gward@python.net>
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 21:56:22 +0200 [thread overview]
Message-ID: <20010921215622.A1282@suse.cz> (raw)
In-Reply-To: <20010921134402.A975@gerg.ca> <20010921205356.A1104@suse.cz> <20010921150806.A2453@gerg.ca> <20010921154903.A621@gerg.ca>
In-Reply-To: <20010921154903.A621@gerg.ca>; from gward@python.net on Fri, Sep 21, 2001 at 03:49:03PM -0400
On Fri, Sep 21, 2001 at 03:49:03PM -0400, Greg Ward wrote:
> [Vojtech Pavlik]
> > Do you have the VIA IDE support enabled?
>
> [my response]
> > 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.
>
> Still no luck with this slightly tweaked kernel config.
>
> Here are the relevant config variables ("grep '=y' .config", copy lines
> from CONFIG_IDE to CONFIG_SCSI):
>
> CONFIG_IDE=y
> CONFIG_BLK_DEV_IDE=y
> CONFIG_BLK_DEV_IDEDISK=y
> CONFIG_IDEDISK_MULTI_MODE=y
> CONFIG_BLK_DEV_IDECD=y
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_IDEPCI_SHARE_IRQ=y
> CONFIG_BLK_DEV_IDEDMA_PCI=y
> CONFIG_BLK_DEV_ADMA=y
> CONFIG_IDEDMA_PCI_AUTO=y
> CONFIG_BLK_DEV_IDEDMA=y
> CONFIG_BLK_DEV_PDC202XX=y
> CONFIG_PDC202XX_BURST=y
> CONFIG_PDC202XX_FORCE=y
> CONFIG_BLK_DEV_VIA82CXXX=y
> CONFIG_IDEDMA_AUTO=y
> CONFIG_BLK_DEV_IDE_MODES=y
>
> Is there any point in upgrading to a kernel beyond 2.4.9? Or has the
> relevant code not been touched lately?
There were updates in 2.4.9-pre2 in the VIA driver, so it might be worth
trying. Also disabling CONFIG_IDEDMA_AUTO may work, but you'll get slow
performance. Afterwards, though, you can do hdparm -i /dev/hd* and cat
/proc/ide/via, which will tell us interesting information, which may
lead us further to solving the problem. Btw, what clock and multiplier
your CPU is?
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2001-09-21 19:57 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
2001-09-21 19:49 ` Greg Ward
2001-09-21 19:56 ` Vojtech Pavlik [this message]
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=20010921215622.A1282@suse.cz \
--to=vojtech@suse.cz \
--cc=bugs@linux-ide.org \
--cc=gward@python.net \
--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