Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1281563

Re: libata-core: devslp fails on ATP mSATA

From Andreas Werner <andreas.werner@men.de>
Newsgroups linux.kernel
Subject Re: libata-core: devslp fails on ATP mSATA
Date 2015-12-02 10:50 +0100
Message-ID <qBccV-5qs-3@gated-at.bofh.it> (permalink)
References <qAVON-3v2-7@gated-at.bofh.it> <qAVON-3v2-5@gated-at.bofh.it> <qAYtk-5dB-21@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Dec 01, 2015 at 02:04:10PM -0500, Tejun Heo wrote:
> On Tue, Dec 01, 2015 at 11:17:15AM -0500, Tejun Heo wrote:
> > So, I suppose this is a fallout from 9faa643855df ("libata: use
> > READ_LOG_DMA_EXT").  The description just says "we should try use it"
> > but is there any benefit from using NCQ variant of read log page?  I
> > mean, it's used during config and error handling, so it's not like
> > queueing is gonna help anything.  It ends up issuing NCQ commands on
> > controllers which don't support NCQ and causes failures on devices
> > which lie about supporting the feature.
> 
> Hmmm... so, the controller locks up on READ_LOG_EXT issued as pio?
> That's just weird.  I suppose you can blacklist the controller so that
> any attempt to read the log page fails without actually issuing the
> command.
> 
> Thanks.
> 
> -- 
> tejun

Hi,
yes since i am using 3.14 where the READ_LOG_DMA_EXT is not it, it
seems that the controller locks up even on READ_LOG_EXT as PIO.

I have checked the current ERRATA sheet of the CPU but there
are no issues regarding this problem.

Test on a Freescale T4240 show the same behaviour as on P1013/P1022.
It seems that some FSL Cpus are affected.
I have asked my FAE at Freescale if he has some information about
that kind of issue.

Blacklisting the controller would be a solution yes, but I just
wanna wait the answer from the FAE to be sure we really have a
problem.

What kind of identifier can I use for blacklisting? The driver name
from the host driver? (fsl-sata) I did not find any register
in the sata controller to read out an ID.

Regards
Andy


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: libata-core: devslp fails on ATP mSATA Tejun Heo <tj@kernel.org> - 2015-12-01 17:20 +0100
  Re: libata-core: devslp fails on ATP mSATA Tejun Heo <tj@kernel.org> - 2015-12-01 20:10 +0100
    Re: libata-core: devslp fails on ATP mSATA Andreas Werner <andreas.werner@men.de> - 2015-12-02 10:50 +0100
      Re: libata-core: devslp fails on ATP mSATA Tejun Heo <tj@kernel.org> - 2015-12-02 17:50 +0100
        Re: libata-core: devslp fails on ATP mSATA Andreas Werner <andreas.werner@men.de> - 2015-12-03 10:50 +0100
          Re: libata-core: devslp fails on ATP mSATA Tejun Heo <tj@kernel.org> - 2015-12-03 16:20 +0100
            Re: libata-core: devslp fails on ATP mSATA Andreas Werner <andreas.werner@men.de> - 2015-12-03 17:10 +0100

csiph-web