linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Samsung SSD 1.92TB PM863 Enterprise 2.5" SATA3 errors withc stable 4.4.34
Date: Wed, 14 Dec 2016 13:22:01 +0100	[thread overview]
Message-ID: <20161214122201.GB6279@linux-x5ow.site> (raw)
In-Reply-To: <CACaajQsKcHJsaUvNo_YTf6UNYR4F2Vi0E6pMUmB1zLpAQg=4ug@mail.gmail.com>

On Wed, Dec 14, 2016 at 03:07:48PM +0300, Vasiliy Tolstov wrote:
> Hi! I have stable problems with all Samsung SSD drivers like PM863 and
> EVO 850 Pro.
> 
> Time after time scsi bus reset link with messages:
> [ 2477.973617] ata1: exception Emask 0x50 SAct 0x0 SErr 0x4090800
> action 0xe frozen
> [ 2477.975036] ata1: irq_stat 0x00400040, connection status changed
> [ 2477.976396] ata1: SError: { HostInt PHYRdyChg 10B8B DevExch }

Random shot in the dark, have you tried changing the cable?
HostInt: HBA Internal error
PHYRdyChg: PhyRdy signal changed state 
10B8B: 10b to 8b decoding error occurred
DevExch: Device presence has changed

This could indicate a problem with the cabling and/or connectors.

Byte,
	Johannes

-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  reply	other threads:[~2016-12-14 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 12:07 Samsung SSD 1.92TB PM863 Enterprise 2.5" SATA3 errors withc stable 4.4.34 Vasiliy Tolstov
2016-12-14 12:22 ` Johannes Thumshirn [this message]
2016-12-14 20:19   ` Vasiliy Tolstov
2016-12-14 12:48 ` Greg KH
2016-12-14 20:20   ` Vasiliy Tolstov

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=20161214122201.GB6279@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=v.tolstov@selfip.ru \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).