All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Fajun Chen <fajunchen@gmail.com>
Cc: linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Libata EH False Alarm (2.6.18-rc2)?
Date: Fri, 25 Aug 2006 23:54:23 +0900	[thread overview]
Message-ID: <44EF0F1F.3050109@gmail.com> (raw)
In-Reply-To: <8202f4270608250741l15047a96q544d38eebca8d57e@mail.gmail.com>

Fajun Chen wrote:
> Hi Tejun,
> 
> I tested your patch. No more EH alarms in dmesg during an overnight
> test.  One question I have is whether this fix will mask genuine
> failure.

No, you're experiencing a lot recoverable failures.  The reason can be 
anything - faulty drive, flakey cable, out-of-spec on-board trace, 
etc...  You probably want to solve the problem.

-- 
tejun

  reply	other threads:[~2006-08-25 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 19:42 Libata EH False Alarm (2.6.18-rc2)? Fajun Chen
2006-08-24 20:00 ` Tejun Heo
2006-08-24 20:05   ` Fajun Chen
2006-08-24 20:21     ` Tejun Heo
2006-08-24 20:24       ` Tejun Heo
2006-08-25 14:41         ` Fajun Chen
2006-08-25 14:54           ` Tejun Heo [this message]
2006-08-24 21:28       ` Fajun Chen

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=44EF0F1F.3050109@gmail.com \
    --to=htejun@gmail.com \
    --cc=fajunchen@gmail.com \
    --cc=jgarzik@pobox.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.