mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: alan@redhat.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Warn about taskfile?
Date: Wed, 30 Jul 2003 16:14:14 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10307301609580.19607-100000@master.linux-ide.org> (raw)
In-Reply-To: <20030730205935.GA238@elf.ucw.cz>


If your corruption is only under DMA you have a chipset or an ./arch/
problem.  If you have corruption under PIO, this could be a timing error.
If command mode of taskfile is at issue, you can not function period.

If this only happens on writes, you have a FIFO problem in the ASIC or
iotable for the scatter gather formation.

Taskfile is not broken, it is the only means to talk to an ATA/ATAPI/SATA
device.  How Taskfile is executed is dependent on the device attached.

So if this is the x86-64 issue you have to fix that arch.

-a

On Wed, 30 Jul 2003, Pavel Machek wrote:

> Hi!
> 
> I had some strange fs corruption, and andi suggested that it probably
> is TASKFILE-related. Perhaps this is good idea?
> 
> 								Pavel
> 
> --- clean/drivers/ide/Kconfig	2003-07-27 22:31:13.000000000 +0200
> +++ linux/drivers/ide/Kconfig	2003-07-30 22:56:50.000000000 +0200
> @@ -283,7 +283,8 @@
>  	---help---
>  	  Use new taskfile IO code.
>  
> -	  It is safe to say Y to this question, in most cases.
> +	  It is safe to say Y to this question, but you should attach
> +	  scratch monkey, first.
>  
>  comment "IDE chipset support/bugfixes"
>  	depends on BLK_DEV_IDE
> 
> -- 
> When do you have a heart between your knees?
> [Johanka's followup: and *two* hearts?]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


      parent reply	other threads:[~2003-07-30 23:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 20:59 Pavel Machek
2003-07-30 21:11 ` Alan Cox
2003-07-30 23:03   ` Pavel Machek
2003-07-30 23:12     ` Alan Cox
2003-07-30 23:31   ` Oliver Xymoron
2003-07-30 21:21 ` Robert Love
2003-07-30 21:25   ` Sean Estabrooks
2003-07-30 21:45 ` Bartlomiej Zolnierkiewicz
2003-07-30 22:43   ` Diego Calleja García
2003-07-30 22:55   ` Pavel Machek
2003-07-30 23:20     ` Bartlomiej Zolnierkiewicz
2003-07-31 10:28       ` Pavel Machek
2003-07-31 13:00         ` Andre Hedrick
2003-07-31 14:03           ` Pavel Machek
2003-07-30 23:17   ` Andre Hedrick
2003-07-30 23:14 ` Andre Hedrick [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=Pine.LNX.4.10.10307301609580.19607-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®