linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linas Vepstas <linas@austin.ibm.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ide dma_timer_expiry, then hard lockup
Date: Tue, 19 Jun 2007 11:38:41 -0400	[thread overview]
Message-ID: <4677F881.6060200@rtr.ca> (raw)
In-Reply-To: <4677E726.1080602@ru.mvista.com>

Sergei Shtylyov wrote:
> Alan Cox wrote:
> 
>>>>> I can prepare a patch, but only with a lot of guidance. I can test 
>>>>> & debug, I'm highly motivated just right now ... 
> 
>>>> If you've got a nice repeatable problem please try using the libata
>>>> driver. That handles the error paths differently and doesn't try a FIFO
>>>> drain which might matter in this case I guess.
> 
>>>    FIFO drain for DMA commands?
> 
>> Welcome to the old IDE layer which I am so glad I left behind 8)
> 
>> ide_ata_error will try and do a PIO flush regardless of the command type
>> if DRQ_STAT is asserted. See ide_dma_intr -> ide_error -> ...
> 
>    Indeed... but the thing is we don't know what's asserted in this case 
> -- remember, it's reading the status register that locks everything up...

Exactly.  And IORDY shouldn't really apply there,
unless some nitwit standards person wrote it into a spec..

-ml

  reply	other threads:[~2007-06-19 15:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 17:57 [BUG] ide dma_timer_expiry, then hard lockup Linas Vepstas
2007-06-18 18:11 ` Stuart_Hayes
2007-06-19 14:07   ` Sergei Shtylyov
2007-06-19 15:05     ` Linas Vepstas
2007-06-19 16:10       ` Sergei Shtylyov
2007-06-19 16:48         ` Linas Vepstas
2007-06-19 18:43           ` Bartlomiej Zolnierkiewicz
2007-06-19 20:07             ` Sergei Shtylyov
2007-06-20 16:28               ` Linas Vepstas
2007-06-20 17:01                 ` Alan Cox
2007-06-21 17:58                   ` Sergei Shtylyov
2007-06-21 21:41                     ` Alan Cox
2007-06-21 19:47                   ` Linas Vepstas
2007-06-21 22:04                     ` Alan Cox
2007-06-18 20:27 ` Alan Cox
2007-06-18 20:46   ` Linas Vepstas
2007-06-18 21:04     ` Alan Cox
2007-06-18 21:22       ` Linas Vepstas
2007-06-19 14:56         ` bug in libata [was " Linas Vepstas
2007-06-19 14:10       ` Sergei Shtylyov
2007-06-19 14:19         ` Alan Cox
2007-06-19 14:24           ` Sergei Shtylyov
2007-06-19 15:38             ` Mark Lord [this message]
2007-06-19 15:51               ` Sergei Shtylyov
2007-06-19 16:17               ` Alan Cox
2007-06-19 16:32                 ` Sergei Shtylyov
2007-06-22 15:39 ` Sergei Shtylyov
2007-06-29 18:52   ` Sergei Shtylyov

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=4677F881.6060200@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linas@austin.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    /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;
as well as URLs for NNTP newsgroup(s).