From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Ted Deppner <ted@psyber.com>
Cc: Jens Axboe <axboe@suse.de>, Martin Dalecki <martin@dalecki.de>,
Vojtech Pavlik <vojtech@suse.cz>,
linux-kernel@vger.kernel.org, vda@port.imtp.ilyichevsk.odessa.ua
Subject: Re: New IDE code and DMA failures
Date: Thu, 11 Apr 2002 17:27:29 +0100 [thread overview]
Message-ID: <2126B5B63EE@vcnet.vc.cvut.cz> (raw)
On 11 Apr 02 at 6:05, Ted Deppner wrote:
> On Thu, Apr 11, 2002 at 03:39:33PM -0200, Denis Vlasenko wrote:
> > I have a flaky IDE subsystem in one box. Reads work fine,
> > writes sometimes don't work and hang either IDE/block device
> >
> > Please inform me whenever you want me to test your patches.
>
> I've been testing 2.4.17 and 2.4.19-pre6 and see some similar issues. I
> have an Asus A7V w/ 1gig Athlon processor. Using the onboard Promise
> UDMA100 controller, I can read and write all day long to /dev/hde all by
> itself... However, after few minutes of any type of access to /dev/hdh,
> /dev/hde suddenly starts having DMA errors and switches to PIO. I'm on my
> third DMA66 cable (yet it fights tightly), and am still seeing the exact
> same issues. I don't believe my IDE subsystem to be flaky. hde is a WD
> drive, and hdh is a Maxtor.
What your /dev/hdg is? Using slave-alone on the A7V's Promise (and maybe
on other motherboards too) will corrupt your disk badly. Under Linux,
and also under Windows98. I did not tried other OSes...
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-04-11 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 16:27 Petr Vandrovec [this message]
2002-04-13 1:02 ` New IDE code and DMA failures Ted Deppner
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 17:39 Denis Vlasenko
2002-04-11 12:05 ` Martin Dalecki
2002-04-11 18:44 ` Denis Vlasenko
2002-04-11 12:52 ` Martin Dalecki
2002-04-11 19:17 ` Denis Vlasenko
2002-04-11 15:48 ` Vojtech Pavlik
2002-04-12 14:47 ` Denis Vlasenko
2002-04-11 13:05 ` Ted Deppner
2002-04-11 14:10 ` Oleg Drokin
2002-04-13 0:58 ` Ted Deppner
2002-04-13 7:07 ` Oleg Drokin
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=2126B5B63EE@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=ted@psyber.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.