Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Apr 2020 15:30:37 -0600
From:      Scott Long <scottl@samsco.org>
To:        Miroslav Lachman <000.fbsd@quip.cz>
Cc:        Kurt Jaeger <pi@freebsd.org>, Warner Losh <imp@bsdimp.com>, FreeBSD-Current <freebsd-current@freebsd.org>
Subject:   Re: PCIe NVME drives not detected on Dell R6515
Message-ID:  <90C35FEF-690C-4D04-A0D8-D3E5A448C744@samsco.org>
In-Reply-To: <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz>
References:  <bc00d2f4-d281-e125-3333-65f38da20817@quip.cz> <0F8BCB8C-DE60-4A34-A4D8-F1BB4B9F906A@samsco.org> <CANCZdfprct8pELBaev=Ub3sXb_JRx9xovUhzxDpSwY2rXfMtrg@mail.gmail.com> <9EF043C1-FF8F-4997-B59A-EC3BF7D1CEEE@samsco.org> <31E8B2BE-BED2-4084-868D-32C48CB3CD6E@samsco.org> <573f5fab-1ef6-151f-18ca-58d3a4a89c72@quip.cz> <07B6763F-C23B-4B7C-B76A-26267AC35453@samsco.org> <fe25f330-979c-a1ea-6ca6-fce80e869f04@quip.cz> <20200417194431.GD39563@home.opsec.eu> <148dcdf7-f185-f14f-52ee-d4df3a2a1dc7@quip.cz> <8D8E1F62-AB66-47E1-8444-3D66F8EADA74@samsco.org> <c7fe1d15-a2f7-5aee-466e-a5444340c267@quip.cz> <F8D7C4AF-90D5-4997-B4C3-F7EDF4C787EE@samsco.org> <015c7aa8-9385-4219-1bf1-0137f65ed80d@quip.cz>

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


> On Apr 17, 2020, at 3:07 PM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:
>=20
> Scott Long wrote on 04/17/2020 23:04:
>>> On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:
>>>=20
>>> Scott Long wrote on 04/17/2020 22:17:
>>>>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd@quip.cz> =
wrote:
>>>>>=20
>>>>> Kurt Jaeger wrote on 04/17/2020 21:44:
>>>>>> Hi!
>>>>>>>> pciconf -lBc pcib12
>>>>>>>> pciconf -lBc pcib13
>>>>>>>=20
>>>>>>> Printscreen attached.
>>>>>> Attachments are stripped from the list -- can you put them =
somewhere
>>>>>> online ?
>>>>>=20
>>>>> Here it is https://ibb.co/c1dZrTf
>>>>>=20
>>>>> Miroslav Lachman
>>>>>=20
>>>> Ok, the bridges know about their downstream bus numbers, but I see =
nothing that suggests that they=E2=80=99re being probed.  The next step =
would be bootverbose, but that=E2=80=99s going to be a lot of output to =
collect in screen captures.
>>>=20
>>> Over 3000 lines long but I finally managed to make SOL work so I =
have it as text!
>>>=20
>>> https://pastebin.pl/view/90fdaafb
>>>=20
>> This helped a lot, thanks.  It looks like these PCIe buses are marked =
as being hotplug, and for some reason we=E2=80=99re not probing them.  =
At this point, I=E2=80=99d need to feed you some kernel patches that =
will dump out more info, but you=E2=80=99d have to compile them and get =
them onto your boot media.  Is that a possibility?
>=20
> Currently I have all machines on 11.3 (where I can rebuild kernel =
without problem)
> If CURRENT is required I would need to setup some CURRENT VM in =
VirtualBox.
>=20
> Can you send me some link to documentation who should I create new ISO =
after rebuild?
>=20

I don=E2=80=99t know of any docs for doing custom releases, and it looks =
like it=E2=80=99s harder than it used to be to insert custom patches.  =
That said, I recommend doing the following on your 11.x build system:

1.  Do a clean `make buildworld` with an up-to-date tree
2.  change into the `release` directory that you just did the buildworld =
from
3.  `sudo make release NOPORTS=3D NODOC=3D CHROOTDIR=3D/usr/tmp/release =
SRCBRANCH=3D"base/stable/11@rHEAD=E2=80=9D`

You can set CHROOTDIR to whatever you want that has a few GB of space, =
but remember where you=E2=80=99ve set it for later steps.  This will =
build a release with stock sources.  Let it complete, both to prepare =
for the next step and to ensure that it works.  It=E2=80=99ll take an =
hour or two depending on your machine speed

4.  Take the patch that I=E2=80=99ll send you shortly and apply it to =
$CHROOTDIR/usr/src
5.  `sudo make memstick NOPORTS=3D NODOC=3D SRC_UPDATE_SKIP=3D =
CHROOTDIR=3D/usr/tmp/release`

Scott






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90C35FEF-690C-4D04-A0D8-D3E5A448C744>