Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 May 2020 01:46:46 +0000
From:      myfreeweb <greg@unrelenting.technology>
To:        Warner Losh <imp@bsdimp.com>, Dan Kotowski <dan.kotowski@a9development.com>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: FreeBSD on Layerscape/QorIQ LX2160X
Message-ID:  <6E6E4F0C-F85B-428B-B221-C5F704677076@unrelenting.technology>
In-Reply-To: <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com>
References:  <SBSqkdZA-3beqJyVy2tMuk5GRmV22DVVnz_8sNDhYCNOjNPe1wgoiSCoOitGhtlBspk-Gk2MKFv4sUyJKy58mKOBpXrGtZoRQKqmDvB1xIg=@a9development.com> <LqTdXCGMiTFwSobCq9LtV5QVLOZ42AiBDUTC9UrdM67cUlD_I8Y7no-8F7d_vs3VDJwIFJLgHTSZVrbkIXXeZ_-hcU0FxfWj0dr-GvhKXHA=@a9development.com> <b04385d558850dc1dfa60fc398c9ac6c@unrelenting.technology> <CAPv3WKdyOzegfK4NJjKzXQTp9jGV9VkDRWxY%2BhDudzWQKkRfEQ@mail.gmail.com> <3e81db774e0fc1a3c2251c89b7629e1b@unrelenting.technology> <86119565e5927716a9feebabcb611871@unrelenting.technology> <f801aa134da12d1b4a34b87dbc180b4a@unrelenting.technology> <37858865a8ebddd3fe1e3a228a19ef62@unrelenting.technology> <7066da0bc417ed047dc27b4741c90e81@unrelenting.technology> <xoiJF1ZUP3-rgbxC8ZmJGQNpsJSyK4zsAXhbLl8Ml96Da1lBPGwPqn0ANf7q-GgthPAWePSR9QDCM5vKysd_3e2aGtp-0egUXu6AW3bhLDg=@a9development.com> <CANCZdfqbd_u35toFYKr4LKkCBwnRhutM5knjnVcGR018Jfo1Vw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On May 23, 2020 1:25:48 AM UTC, Warner Losh <imp@bsdimp=2Ecom> wrote:
>On Fri, May 22, 2020 at 7:07 PM Dan Kotowski <dan=2Ekotowski@a9developmen=
t=2Ecom>
>wrote:
>
>> > > > > I spent some time looking at that NetBSD Layerscape code - I
>> couldn't figure out how to add it
>> > > > > trivially to the current HEAD on my own, so I'm looking forward=
 to
>> seeing how we're going to yeet
>> > > > > that in for testing=2E=2E=2E
>> > > > > Something like this:
>> > > > >
>> https://github=2Ecom/myfreeweb/freebsd/commit/6cbdafbc310b9a0fa4d046f71=
979aa01302e8b0b
>> > > > >
>> https://send=2Efirefox=2Ecom/download/ec0419c6d3fa856e/#QOMHO8pBq1dP1K2=
_4P4CBw
>> > > >
>> > > > https://gist=2Egithub=2Ecom/agrajag9/b214aa837d0ed6bb14139770ff58=
35ff
>> > > > Line 404: panic: Misaligned access from kernel space!
>> > > > oops, I actually have to care about the`bytes` parameter=2E=2E
>> > > > at least I got the ACPI-walking on the first try :)
>> > > >
>> https://send=2Efirefox=2Ecom/download/6406af63fee41a8a/#FnEEayn7igQ_eTG=
s0Wq0uw
>> > >
>> > > https://gist=2Egithub=2Ecom/agrajag9/b47d63484fa51eed535d8a43625a52=
76
>> >
>> > hmmm=2E there's now a pcib2: <PCI-PCI bridge> at device 0=2E0 on pci1
>> >
>> > and it actually does allocate memory, after the root fails to:
>> >
>> > pcib1: rman_reserve_resource: start=3D0x670000000, end=3D0x67003ffff,
>> count=3D0x40000
>> > pcib1: pci_host_generic_core_alloc_resource FAIL: type=3D3, rid=3D28,
>> start=3D0000000670000000, end=3D000000067003ffff, count=3D0000000000040=
000,
>> flags=3D4800
>> > pcib2: allocated memory range (0x70040000-0x7007ffff) for rid 1c of
>> pci1:1:0:0
>> >
>> > iiiinteresting=2E Try to kldload mpr/mps/whatever? Also insert the nv=
me
>> drive
>>
>> https://gist=2Egithub=2Ecom/agrajag9/226018f25c9c5dd9c5dec4d5ea1b767d
>>
>> It just kept looping like that for about 5min before I killed it=2E But=
 it
>> definitely reads the firmware version correctly - it's been on a shelf =
for
>> a while=2E But I'm thinking maybe the card isn't initializing right - t=
here's
>> none of the usual output during POST - so I'm going to dig up that PCI
>> power cable and the RX480 tomorrow and try those=2E
>>
>> As for NVMe, it panics before I get to a shell=2E
>>
>
>Where?

You can see that in the gist: "NVME polled command failed to complete with=
in 1s"

Same as before (with straight ECAM)=2E

Looks like straight ECAM *is* supposed to work, after all (with limitation=
s on bifurcation or something, I've heard)=2E The code I'm porting from Net=
BSD does use that same ECAM space when touching non-0 busses=2E

Whoops, I might've been working on increasing features instead of fixing b=
ugs=2E=2E :D

It's odd that what's failing is just polling I/O with the devices, and aft=
er successful reads=2E Does that smell like cache issues or something?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6E6E4F0C-F85B-428B-B221-C5F704677076>