From: linas@austin.ibm.com (Linas Vepstas)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ide dma_timer_expiry, then hard lockup
Date: Mon, 18 Jun 2007 16:22:38 -0500 [thread overview]
Message-ID: <20070618212238.GI5836@austin.ibm.com> (raw)
In-Reply-To: <20070618220441.3a3af8ca@the-village.bc.nu>
On Mon, Jun 18, 2007 at 10:04:41PM +0100, Alan Cox wrote:
>
> If you've got a nice repeatable problem
Very highly repeatable :-(
> 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.
Dohh, yes, of course. Completely forgot about that. (I assume you mean
CONFIG_ATA). Will report tommorrow.
--linas
next prev parent reply other threads:[~2007-06-18 21:22 UTC|newest]
Thread overview: 33+ 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-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-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-21 22:04 ` Alan Cox
2007-06-18 20:27 ` 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:04 ` Alan Cox
2007-06-18 21:22 ` Linas Vepstas [this message]
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
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=20070618212238.GI5836@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--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.