All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: dep <dennispowell@earthlink.net>
Cc: "Karnik, Rahul" <rakarnik@davidson.edu>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: VIA IDE bug with WD drive?
Date: Thu, 16 Nov 2000 12:06:37 +0100	[thread overview]
Message-ID: <20001116120637.C665@suse.cz> (raw)
In-Reply-To: <1DE3DA661DC2D31190030090273D1E6A0153FA97@pobox.davidson.edu> <00111519564300.04831@depoffice.localdomain>
In-Reply-To: <00111519564300.04831@depoffice.localdomain>; from dennispowell@earthlink.net on Wed, Nov 15, 2000 at 07:56:43PM -0500

On Wed, Nov 15, 2000 at 07:56:43PM -0500, dep wrote:
> On Wednesday 15 November 2000 19:30, Karnik, Rahul wrote:
> 
> | I get the following error if I try to enable DMA on my Abit KT7
> | motherboard with a VIA2C686 chipset:
> |
> | hdb: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest
> | } hdb: timeout waiting for DMA
> | hda: DMA disabled
> | hdb: DMA disabled
> | ide0: reset: success
> 
> i get the same thing, along with a crc error, over and over on a 
> 20-gig WD IDE drive. alternately puzzling and frightening. 
> apparently, wd uses some nonstandard goofball error checking thing 
> that just doesn't work with linux at present. it *seems* to do no 
> harm.

Ok, both of you, we can try to track this down.

1) Please try with 2.4.0-latest. 
2) Send me the complete dmesg.
3) Send me lspci -vvvxxx
4) Send me /proc/ide/via

I'll see what I can do about the driver.

-- 
Vojtech Pavlik
SuSE Labs
-
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/

      reply	other threads:[~2000-11-16 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16  0:30 VIA IDE bug with WD drive? Karnik, Rahul
2000-11-16  0:56 ` dep
2000-11-16 11:06   ` Vojtech Pavlik [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=20001116120637.C665@suse.cz \
    --to=vojtech@suse.cz \
    --cc=dennispowell@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rakarnik@davidson.edu \
    /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.