LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: David =?unknown-8bit?Q?G=F3mez?= <davidge@jazzfree.com>
Cc: Riley Williams <rhw@MemAlpha.CX>,
	Linux-kernel <linux-kernel@vger.kernel.org>
Subject: IDE DMA errors [was: Some ext2 errors]
Date: Sun, 7 Oct 2001 11:02:12 -0700	[thread overview]
Message-ID: <20011007110212.A22412@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110062358590.25149-100000@infradead.org> <Pine.LNX.4.33.0110071510190.878-100000@fargo>
In-Reply-To: <Pine.LNX.4.33.0110071510190.878-100000@fargo>

On Sun, Oct 07, 2001 at 03:15:33PM +0200, David G?mez wrote:
> On Sun, 7 Oct 2001, Riley Williams wrote:
> 
> > I see this regularly on one of my systems, and hdparm has never even
> > been insatalled on that system. If I put the drive in a different
> > system, the drive reports clean, but whatever drive I put in here
> > regularly reports that problem.
> 
> Yes, i also have seen this error also when not using hdparm, so it's not
> the cause of this ext2 errors.
>

Oh, sorry, I blamed before I had facts... my bad.

> >
> > 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.
> 
> If i see this error show more times i'll try to replace the PSU. First i
> think is has some relation with my VIA chipset, but if you tell me you
> have changed even your motherboard... ;)
>

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.

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. 

> >  > 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...

Mike

  reply	other threads:[~2001-10-07 18:02 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       ` Mike Fedyk [this message]
2001-10-07 22:39         ` IDE DMA errors [was: Some ext2 errors] Riley Williams
2001-10-08  0:32           ` Mike Fedyk
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:
  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=20011007110212.A22412@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=davidge@jazzfree.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rhw@MemAlpha.CX \
    --subject='Re: IDE DMA errors [was: Some ext2 errors]' \
    /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

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).