From: Larry McVoy <lm@bitmover.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
Jens Axboe <axboe@suse.de>,
andre@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: [patch]: ide dma timeout retry in pio
Date: Mon, 28 May 2001 23:18:09 -0700 [thread overview]
Message-ID: <20010528231809.A29504@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10105281533400.25183-100000@coffee.psychology.mcmaster.ca> <E154UJT-0003XV-00@the-village.bc.nu>
In-Reply-To: <E154UJT-0003XV-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, May 28, 2001 at 10:12:31PM +0100
On Mon, May 28, 2001 at 10:12:31PM +0100, Alan Cox wrote:
> > really? do we know the nature of the DMA engine problem well enough?
> 3. Bad cabling
For what it is worth, in the recent postings I made about this topic, you
suggested that it was bad cabling, I swapped the cabling, same problem.
I swapped the mother board from Abit K7T to ASUS A7V and all cables worked
fine.
I really think there is a software problem in there with certain chipsets,
those from VIA seem to be problematic.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-05-28 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 18:34 [patch]: ide dma timeout retry in pio Jens Axboe
2001-05-28 19:39 ` Mark Hahn
2001-05-28 20:13 ` Christopher B. Liebman
2001-05-28 20:37 ` Jens Axboe
2001-05-28 22:15 ` Andre Hedrick
2001-05-28 22:26 ` Jens Axboe
2001-05-29 0:09 ` Andre Hedrick
2001-05-29 0:30 ` Jens Axboe
2001-05-28 21:12 ` Alan Cox
2001-05-28 22:11 ` James Turinsky
2001-05-29 6:18 ` Larry McVoy [this message]
2001-05-28 22:20 ` Alan Cox
2001-05-28 22:56 ` Meelis Roos
2001-05-29 7:11 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 21:09 Diefenbaugh, Paul S
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=20010528231809.A29504@work.bitmover.com \
--to=lm@bitmover.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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