All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Georgi Chulkov <g.chulkov@jacobs-university.de>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Mark Lord <liml@rtr.ca>
Subject: Re: ATA device reset, shoud I be concerned?
Date: Mon, 21 Jan 2008 23:33:35 +0900	[thread overview]
Message-ID: <4794AD3F.40309@gmail.com> (raw)
In-Reply-To: <4794ACAF.70505@gmail.com>

Tejun Heo wrote:
> IMHO, losing media error information is much better than locking up a
> machine hard.  We can start white listing known good controllers but I'm
> skeptical how much benefit it will bring.

Just a data point, even ICHs lock up after PHY event if the wrong TF
register is accessed.  I just don't think tempting with TF regs after
timeout is worth the cost.

-- 
tejun

  reply	other threads:[~2008-01-21 14:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 22:19 ATA device reset, shoud I be concerned? Georgi Chulkov
2008-01-15 10:54 ` Andrew Morton
2008-01-15 11:35   ` Alan Cox
2008-01-21  7:56     ` Tejun Heo
2008-01-21 13:02       ` Alan Cox
2008-01-21 13:14         ` Tejun Heo
2008-01-21 14:14           ` Alan Cox
2008-01-21 14:31             ` Tejun Heo
2008-01-21 14:33               ` Tejun Heo [this message]
2008-01-21 16:44                 ` Alan Cox
2009-08-27  2:40                 ` Robert Hancock
2009-08-27  3:07                   ` Jeff Garzik
2009-08-27  8:37                   ` Alan Cox
2008-01-21 16:47               ` Alan Cox
2008-01-21 17:02                 ` Tejun Heo
2008-01-21 17:27                   ` Alan Cox
2008-01-22  0:31                     ` Tejun Heo
2008-01-22  1:31                   ` Bartlomiej Zolnierkiewicz
2008-01-22  1:36                     ` Tejun Heo
2008-01-22  2:08                       ` Tejun Heo
2008-01-22  1:39                     ` Alan Cox
2008-01-22 20:29   ` Georgi Chulkov

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=4794AD3F.40309@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=g.chulkov@jacobs-university.de \
    --cc=liml@rtr.ca \
    --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.