From: Doug McNaught <doug@wireboard.com>
To: James Brents <James@nistix.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE DMA problems on 2.4.0 with vt82c686a driver
Date: 11 Jan 2001 10:12:54 -0500 [thread overview]
Message-ID: <m34rz6rukp.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <3A5DB638.1050809@nistix.com>
In-Reply-To: James Brents's message of "Thu, 11 Jan 2001 07:33:44 -0600"
James Brents <James@nistix.com> writes:
> Hello,
> Since this looks like either a chipset, drive, or driver problem, I am
> submitting this.
>
> I have recently started using DMA mode on my harddisk. However, I occasionally
> (not often/constant, but sometimes) get CRC errors:
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
You might try testing with a different drive if you can get hold of
one--if that works OK, that'll narrow it down to either a drive or
drive-chipset interaction. The above error message could very well
mean that you're starting to lose the drive, so keep backups!
-Doug
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-11 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 13:33 IDE DMA problems on 2.4.0 with vt82c686a driver James Brents
2001-01-11 14:38 ` dep
2001-01-11 14:49 ` Alan Cox
2001-01-11 13:09 ` [PATCH] dgrs.c: kmalloc release on failure Arnaldo Carvalho de Melo
2001-01-11 14:21 ` Arnaldo Carvalho de Melo
2001-01-12 4:19 ` IDE DMA problems on 2.4.0 with vt82c686a driver John O'Donnell
2001-01-12 5:23 ` Andre Hedrick
2001-01-12 8:05 ` Vojtech Pavlik
2001-01-11 14:41 ` Mark Hahn
2001-01-12 8:12 ` Vojtech Pavlik
2001-01-11 15:12 ` Doug McNaught [this message]
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=m34rz6rukp.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=James@nistix.com \
--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 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.