All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [RFT] hpt366: reset DMA state machine on timeouts
Date: Sat, 23 Jun 2007 22:10:34 +0400	[thread overview]
Message-ID: <467D621A.80406@ru.mvista.com> (raw)
In-Reply-To: <20070622163646.GG8840@austin.ibm.com>

Hello.

Linas Vepstas wrote:

>>>>Reset HPT36x's DMA state machine on a DMA timeout the way it's done for 
>>>>HPT370.
>>>>drivers/ide/pci/hpt366.c |   24 +++++++++++++++++++++++-

>>>This worked great!  

>>   I hope you meant those messages were preceeded by DMA timeouts 
>>   (otherwise this code wouldn't come into action).

> Oops, I was wrong ... 

> Scads of 
> Jun 21 20:22:30 localhost kernel: [  434.574301] hdc: task_out_intr:
> status=0x50 { DriveReady SeekComplete }
> Jun 21 20:22:30 localhost kernel: [  434.574318] ide: failed opcode was:
> unknown

>>>from it (I put in a printk to verify this).

>>   You mean into my ide_dma_timeout() method?

> Ooops, I lied. I have so many printk's in there, that I got confused.
> No, in fact, it looks like I did NOT see your handler run. 

    Now I'm confused too -- did you get any DMA timeouts this time?

> --linas

MBR, Sergei

  reply	other threads:[~2007-06-23 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 17:54 [RFT] hpt366: reset DMA state machine on timeouts Sergei Shtylyov
2007-06-21 19:31 ` Linas Vepstas
2007-06-22 15:13 ` Linas Vepstas
2007-06-22 15:32   ` Sergei Shtylyov
2007-06-22 16:36     ` Linas Vepstas
2007-06-23 18:10       ` Sergei Shtylyov [this message]
2007-06-25 21:44         ` Linas Vepstas
2007-06-26 13:57           ` Sergei Shtylyov
2007-06-22 15:54   ` Alan Cox
2007-06-22 16:03     ` Linas Vepstas
2007-06-22 16:33       ` Alan Cox

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=467D621A.80406@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linas@austin.ibm.com \
    --cc=linux-ide@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.