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: Some questions about new EH in libata
Date: Tue, 22 Aug 2006 14:10:00 +0900	[thread overview]
Message-ID: <44EA91A8.5090309@gmail.com> (raw)
In-Reply-To: <8202f4270608212154k787f63a1k15ed3dcfff0624c2@mail.gmail.com>

Fajun Chen wrote:
> Hi Folks,
> 
> I just upgraded to the libata with new EH and I have some questions
> about the new error handler:
> 1. In several occasions, I saw a port being disable, under what kind
> of conditions will new EH disable a port?

After EH fails to recover a device.  It usually takes three recovery 
trial failures.

> 2. For user space program, is there any way to checked the state of a
> port/drive? I noticed that dmesg has some printout but that could be
> wiped out by other traces or errors.

Hmmm... Not yet.

> 3. Does libata allow user space code to reset host/bus/drive or only
> libata itself has the privilege? I tried sg reset IOCTL interface on
> SATA Sil3124, it seems not working.

No, that doesn't work but issuing userscan forces libata to reset the 
channel.

> 4. How to reenable a port/drive after it's disabled without rebooting?
> Any API or command from user space?

You can use SCSI userscan interface.

Regards.

-- 
tejun

  reply	other threads:[~2006-08-22  5:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22  4:54 Some questions about new EH in libata Fajun Chen
2006-08-22  5:10 ` Tejun Heo [this message]
2006-08-22 15:40   ` Fajun Chen
2006-08-22 15:51     ` Tejun Heo
2006-08-29  0:51   ` Fajun Chen
2006-08-29  2:16     ` Tejun Heo
2006-08-29 15:51       ` Fajun Chen
2006-08-29 16:00         ` Tejun Heo

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=44EA91A8.5090309@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.