LKML Archive on
help / color / mirror / Atom feed
From: Mike Fedyk <>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: David =?unknown-8bit?Q?G=F3mez?= <>,
	Linux-kernel <>
Subject: Re: IDE DMA errors [was: Some ext2 errors]
Date: Sun, 7 Oct 2001 17:32:37 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> <>
In-Reply-To: <>

On Sun, Oct 07, 2001 at 11:39:04PM +0100, Riley Williams wrote:
> Hi Mike.

Hey Riley,

>  >>> As far as I can tell, it's a problem with the PSU in the computer
>  >>> in question, as I can swap ANYTHING else in there, motherboard
>  >>> included, without the problem going away on that drive, but as
>  >>> soon as I swap the PSU, the problems vanish - even if I put a PSU
>  >>> with a lower rating in its place.
>  > It may not be your MB or drive, but an interaction between them.
>  > I.E. Your bios could've told the linux driver to use a higher
>  > dma level than the drive likes.
> Always possible, but I'd consider it unlikely that using the SAME
> motherboard and drive, but with a different PSU would have any affect
> whatsoever if such was the reason.
> I would presume that the old PSU was just too noisy for that
> particular drive, and a new PSU is rather quieter in that regard.

But we don't know what is happening with David's system.

To rule out some possible causes David, you should run these tests:
memtest86 (
badblocks -s /dev/hda (read only hard drive test, newer versions have a -p
option for safe write mode tests too)

>  > Try running "hdparm -d0 /dev/hda" (since your drive is hda in
>  > this case...) And see if the problem goes away. If it does, then
>  > try Multimode dma, if (-X34) you get errors, try single mode
>  > (probably -X31), if you get no errors there, try UDMA mode 2
>  > (-X66, also make sure you have a 80 line ide cable) and see if
>  > any of the problems come back.
> Unfortunately, none of that is relevant in my case...see below...

But maybe for david...  David, try the tests above with read only badblocks...

>  >>>> Yeah. If you can't figure out hdparm, leave it alone.
>  >>> Who says hdparm has anything to do with it?
>  >> He says, it seems he has very deep knowledge of hdparm 'secrets'.
>  > Again, sorry for being presumptuous. I've only been able to cause
>  > this with hdparm. Maybe I'm just not using new enough hardware...
> The system in question is my network printserver, which has a 386sx/16
> processor and a very definitely 40 line cable with no support for
> anything else. The hard drive is an antique Maxtor 800M one, and I
> have no problem assuring you that it's not possible to buy that model
> new, and hasn't been for some years now...

It would probably recognize a 2gb drive, which you could easily raid 1 for
your server, assuming that there are two ide connectors on that old 386 MB.

This just adds another possible test...  Buying a new power supply.

David, let us know what you find...


> Best wishes from Riley.

  reply	other threads:[~2001-10-08  0:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06 15:15 Some ext2 errors davidge
2001-10-06 19:13 ` Mike Fedyk
2001-10-06 23:05   ` Riley Williams
2001-10-07 13:15     ` David Gómez 
2001-10-07 18:02       ` IDE DMA errors [was: Some ext2 errors] Mike Fedyk
2001-10-07 22:39         ` Riley Williams
2001-10-08  0:32           ` Mike Fedyk [this message]
2001-10-08  0:51             ` David Gómez 
2001-10-08 11:19             ` Riley Williams
2001-10-08 18:24               ` David Gómez 

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --cc=rhw@MemAlpha.CX \
    --subject='Re: IDE DMA errors [was: Some ext2 errors]' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).