From: Ido Schimmel <idosch@mellanox.com>
To: Christoph Hellwig <hch@lst.de>
Cc: tj@kernel.org, xiaolong.ye@intel.com, mlxsw@mellanox.com,
michaelsh@mellanox.com, linux-ide@vger.kernel.org
Subject: Re: Regression due to "libata: implement SECURITY PROTOCOL IN/OUT"
Date: Sun, 27 Aug 2017 13:53:31 +0300 [thread overview]
Message-ID: <20170827105331.GA18386@shredder.mtl.com> (raw)
In-Reply-To: <20170827090546.GA16766@lst.de>
Hi Christoph,
On Sun, Aug 27, 2017 at 11:05:46AM +0200, Christoph Hellwig wrote:
> On Sat, Aug 26, 2017 at 08:15:37PM +0300, Ido Schimmel wrote:
> > On Thu, Aug 24, 2017 at 03:18:04PM +0300, Ido Schimmel wrote:
> > > On Thu, Aug 24, 2017 at 02:07:29PM +0200, Christoph Hellwig wrote:
> > > > What kind of device is this? Seems like we need to blacklist it
> > > > as it chokes when we tried to read the Identify Devіce Log.
> > >
> > > Is the below enough or do you need more info?
> >
> > Ping?
>
> Sorry, been a bit busy. Is this an actual SSD connected to a real
> controller, or a PCIe SSD that implements ahci itself?
Yes, it's an actual SSD. Not PCIe.
> Can you send the full dmesg output, plus lspci -v, plus the output of
> hdparm -i /dev/sdN for the device after a working boot?
dmesg from 4.12.8 kernel:
https://pastebin.com/HjMFqrP8
lspci -v from 4.12.8 kernel:
https://pastebin.com/UFnKVmg9
hdparm -i from 4.12.8 kernel:
https://pastebin.com/GdCVcj3G
dmesg from 4.13-rc6 kernel where the error is showed:
https://pastebin.com/uVLRsybx
Thank you for your time.
next prev parent reply other threads:[~2017-08-27 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 11:29 Regression due to "libata: implement SECURITY PROTOCOL IN/OUT" Ido Schimmel
2017-08-24 12:07 ` Christoph Hellwig
2017-08-24 12:18 ` Ido Schimmel
2017-08-26 17:15 ` Ido Schimmel
2017-08-27 9:05 ` Christoph Hellwig
2017-08-27 10:53 ` Ido Schimmel [this message]
2017-08-27 17:03 ` Christoph Hellwig
2017-08-27 18:25 ` Ido Schimmel
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=20170827105331.GA18386@shredder.mtl.com \
--to=idosch@mellanox.com \
--cc=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=tj@kernel.org \
--cc=xiaolong.ye@intel.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.