All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <keith.busch@linux.intel.com>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Keith Busch <keith.busch@intel.com>,
	linux-block@vger.kernel.org, osandov@osandov.com,
	linux-nvme@lists.infradead.org, ming.lei@redhat.com
Subject: Re: blktests block/019 lead system hang
Date: Wed, 6 Jun 2018 08:28:57 -0600	[thread overview]
Message-ID: <20180606142857.GA19462@localhost.localdomain> (raw)
In-Reply-To: <1cbee034-d237-104d-bf5a-33e373821301@redhat.com>

On Wed, Jun 06, 2018 at 01:42:15PM +0800, Yi Zhang wrote:
> Here is the output, and I can see "HotPlug+ Surprise+" on SltCap

Thanks. That looks like a perfectly capable port. I even have the same
switch in one of my machines, but the test doesn't trigger fatal
firmware-first errors.

Might need to query something about the platform to know how it treats
link-downs before proceeding with the test (don't know off the top of
my head; will do some digging).

WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@linux.intel.com (Keith Busch)
Subject: blktests block/019 lead system hang
Date: Wed, 6 Jun 2018 08:28:57 -0600	[thread overview]
Message-ID: <20180606142857.GA19462@localhost.localdomain> (raw)
In-Reply-To: <1cbee034-d237-104d-bf5a-33e373821301@redhat.com>

On Wed, Jun 06, 2018@01:42:15PM +0800, Yi Zhang wrote:
> Here is the output, and I can see "HotPlug+ Surprise+" on SltCap

Thanks. That looks like a perfectly capable port. I even have the same
switch in one of my machines, but the test doesn't trigger fatal
firmware-first errors.

Might need to query something about the platform to know how it treats
link-downs before proceeding with the test (don't know off the top of
my head; will do some digging).

  reply	other threads:[~2018-06-06 14:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <838678680.4693215.1527664726174.JavaMail.zimbra@redhat.com>
2018-05-30  7:26 ` blktests block/019 lead system hang Yi Zhang
2018-05-30  7:26   ` Yi Zhang
2018-06-05 16:18   ` Keith Busch
2018-06-05 16:18     ` Keith Busch
2018-06-05 17:21     ` Keith Busch
2018-06-05 17:21       ` Keith Busch
2018-06-06  5:42       ` Yi Zhang
2018-06-06  5:42         ` Yi Zhang
2018-06-06 14:28         ` Keith Busch [this message]
2018-06-06 14:28           ` Keith Busch
2018-06-12 23:41     ` Austin.Bolen
2018-06-12 23:41       ` Austin.Bolen
2018-06-13 15:44       ` Keith Busch
2018-06-13 15:44         ` Keith Busch
2018-06-13 17:17         ` Austin.Bolen
2018-06-13 17:17           ` Austin.Bolen
2018-06-13 18:24         ` Austin.Bolen
2018-06-13 18:24           ` Austin.Bolen

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=20180606142857.GA19462@localhost.localdomain \
    --to=keith.busch@linux.intel.com \
    --cc=keith.busch@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.lei@redhat.com \
    --cc=osandov@osandov.com \
    --cc=yi.zhang@redhat.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 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.