Date: Thu, 04 Jun 2020 16:38:51 +0000 From: greg@unrelenting.technology To: "Dan Kotowski" <dan.kotowski@a9development.com> Cc: "freebsd-arm" <freebsd-arm@freebsd.org> Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <5e1b4bfe845e62bbcd8b827fa37f2b98@unrelenting.technology> In-Reply-To: <ePx99n--NpqSdQxbdbM3B2qgpSXi0Gjvhspj566br-72pDug8bfXbCXAjnd68jPO2h1bWxkyPDpq5y2BzStbS38-MKkhwMzJI3uHhWcmP_g=@a9development.com> References: <ePx99n--NpqSdQxbdbM3B2qgpSXi0Gjvhspj566br-72pDug8bfXbCXAjnd68jPO2h1bWxkyPDpq5y2BzStbS38-MKkhwMzJI3uHhWcmP_g=@a9development.com> <49F29C72-F76C-46DA-920A-3148B4B0415A@unrelenting.technology> <664db38a87ea8803be72af9738534994@unrelenting.technology> <b5105ce888b7a91eff50ec9118a910a8@unrelenting.technology> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
June 4, 2020 2:40 PM, "Dan Kotowski" <dan.kotowski@a9development.com> wro= te:=0A=0A>> https://send.firefox.com/download/ae38fa35246497c1/#AVSGMsnrM= 0YB2MSL7rRJRQ=0A>> =0A>> - customized pcie driver=0A>> =0A>> - https://re= views.freebsd.org/D25121=0A>> - more interrupt debugging (stray interrupt= s, all GIC config writes)=0A> =0A> https://gist.github.com/agrajag9/484cd= d9c340a15f88be0fabbe2cf9b09=0A> =0A> With NVMe attached it no longer pani= cs, now it just hangs=0A> =0A> Loading mps still just loops=0A> =0A> And = anything attached via AHCI is still MIA=0A=0AOops, I've been adding some = debug prints to gicv2 not gicv3.=0A=0AOne thing I noticed is the interest= ing irq number the nvme admin queue gets..=0Ait's the same as gic_nirqs.= =0A=0Agic0: SPIs: 288, IDs: 65535=0Anvme0: attempting to allocate 17 MSI-= X vectors (33 supported)=0Anvme0: using IRQs 21-37 for MSI-X=0Aacpi0: all= ocating via sysres: res 0xfffffd0000726280, start 21 + count 1 - 1 =3D? e= nd 21=0Aintr_setup_irq(): irq 288 add handler error 0 on nvme0=0A=0Amaybe= that's just like.. the first ITS handled interrupt?=0A(funnily enough, N= etBSD lists MSIs as IRQs starting from 8192)=0A=0A=0AMore SATA debugging:= https://send.firefox.com/download/9de5357a2e58edd9/#s9ZaU_k2NHlO-tLdyGk5= iA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5e1b4bfe845e62bbcd8b827fa37f2b98>