Date: Fri, 05 Jun 2020 15:03:45 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com> Cc: "freebsd-arm" <freebsd-arm@freebsd.org>, "Marcin Wojtas" <mw@semihalf.com> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <cbf5773a03d3c67e133096a0f826274d@unrelenting.technology> In-Reply-To: <CAPv3WKcQFeMDs%2B7Pji5=8D_avua8TK_vHxGLofhoKZArXLyUpQ@mail.gmail.com> References: <CAPv3WKcQFeMDs%2B7Pji5=8D_avua8TK_vHxGLofhoKZArXLyUpQ@mail.gmail.com> <X6Vv06P26Vw5_LcsszpoJBBekBEtVOPLYn9JD5u7GmGzmpL19PqD21yZAb4Nm5-HpelPppbh8LAV7Cs5Amefzsx_kjJsy8LrmHH9mSRxuCY=@a9development.com> <8951311F-77F7-40B8-AEA0-F8CBCB1A05DE@yahoo.com> <4ad62e6669044f82e71a9d86fd493356@unrelenting.technology> <ShdSNL8XDgj0KtPR4v8nn1ohjVssrnoUQGwNL-gHOpylio7Eo5J_WjA2Ko9YjV5md64MeFz017Ts01KUnpJa3Xpw4y_PncL4e5cfUcotRWM=@a9development.com> <31D3FA64-8296-4CA5-92A2-F7FE7C4AE981@unrelenting.technology> <ZdPk7zJSE8UvoonkTixa2gV04ujgKfY93A71fz8cTB6ZPjt2uSCD5TdvFzDAEIR9Tu5LoGrcZLmXqgyrCmzh8OIB2JLc4gNKr6xF0pe931M=@a9development.com> <32d1c173d986884efb9b28932c0ead52@unrelenting.technology> <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> <a727f3c05b234218e053c53100b539f0@unrelenting.technology> <KwrTwABcfEzegUc4D8ZsCgFSxouYQIMOa9JoIbpe6d1HInlAX4G0OzdL_d_uug3gifKwFoh1C_EUd5MucQUgtvFy4T0qraW6riyZbje4Mw8=@a9development.com>
next in thread | previous in thread | raw e-mail | index | archive | help
June 5, 2020 3:01 PM, "Marcin Wojtas" <mw@semihalf.com> wrote:=0A=0A> pt.= , 5 cze 2020 o 13:46 Dan Kotowski <dan.kotowski@a9development.com>=0A> na= pisa=C5=82(a):=0A>> https://gist.github.com/agrajag9/749f504dcac741e902f8= 7c2ea03ae9ac=0A>> =0A>> From jnettlet:=0A>> =0A>> BEGIN QUOTE=0A>> the V1= silicon has a SATA errata. I have partially worked around the errata mov= ing some=0A>> configuration into the firmware, but I still need to sort o= ut the remaining bits. Sometimes just=0A>> unplugging and replugging your= SATA cable will help to reseat the connector and help. Also it is=0A>> v= ery sensitive to marginal SATA cables.=0A>> END QUOTE=0A>> =0A>> I played= around a bit and could create and destroy GPTs, make filesystems, read a= nd write to said=0A>> filesystems, and hot-plug even seems to work. But I= 'm not sure if jon's comment really explains the=0A>> AHCI error we're st= ill seeing:=0A>> =0A>> ```=0A>> (aprobe3:ahcich3:0:15:0): NOP FLUSHQUEUE.= ACB: 00 00 00 00 00 00 00 00 00 00 00 00=0A>> (aprobe3:ahcich3:0:15:0): = CAM status: Command timeout=0A>> (aprobe3:ahcich3:0:15:0): Error 5, Retri= es exhausted=0A>> ```=0A> =0A> I experienced this issue on a cuple of tar= gets (e.g. Zynq-MP or=0A> LS1046A). The port-multiplier quirk flag helped= - please try adding:=0A> ahci->quirks |=3D AHCI_Q_NOPMP;=0A=0A=0ABuild w= ith this + more ITS logging:=0Ahttps://send.firefox.com/download/cf66ed7f= 48160529/#LpeMjccv7iqze5hAx_6BrQ=0A=0AThe patch that lets AHCI attach:=0A= https://reviews.freebsd.org/D25145
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cbf5773a03d3c67e133096a0f826274d>