Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Dec 2020 17:21:14 -0800
From:      Neel Chauhan <neel@neelc.org>
To:        Chuck Tuffli <ctuffli@gmail.com>
Cc:        freebsd-hackers@freebsd.org, FreeBSD-Current <freebsd-current@freebsd.org>
Subject:   Re: Intel TigerLake NVMe vmd: Adding Support & Debugging a Patch
Message-ID:  <3c55d6d50b1bcf1d45d4599502060f34@neelc.org>
In-Reply-To: <f3a548aa4f435f25983f9d6b2a010af0@neelc.org>
References:  <eeab20a1316335317d3ff8cbf68c1cf1@neelc.org> <CAKAYmMLn8rO-dJd%2BVYPguM9KmcXbkBiPnBu3bygRHBNpNn%2BS5w@mail.gmail.com> <f3a548aa4f435f25983f9d6b2a010af0@neelc.org>

next in thread | previous in thread | raw e-mail | index | archive | help
To extend, I am getting an issue with `pci_read_device()` where it 
returns a `vid` (PCI Vendor ID) of 0xffff.

This ends up returning "Cannot allocate dinfo!" from vmd.

Log (via grep): https://imgur.com/a/tAmmY7i

-Neel

On 2020-12-30 16:38, Neel Chauhan wrote:
> Hi Chuck,
> 
> On 2020-12-30 10:04, Chuck Tuffli wrote:
>> What is the output from
>> # pciconf -rb pci0:0:14:0 0x40:0x48
> 
> The output is:
> 
> 01 00 00 00 01 2e 68 02  00
> 
>> --chuck
> 
> I was also able to stop kernel panics by adding:
> 
> rman_fini(&sc->vmd_bus.rman);
> 
> In the fail: statement in vmd_attach().
> 
> But I still cannot detect the SSD.
> 
> -Neel
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3c55d6d50b1bcf1d45d4599502060f34>