Date: Thu, 31 Dec 2020 10:25:49 -0500 From: Mark Johnston <markj@freebsd.org> To: Neel Chauhan <neel@neelc.org> Cc: freebsd-hackers@freebsd.org, ambrisko@freebsd.org Subject: Re: Debugging a WIP PCI/ACPI patch: Bad tailq NEXT(0xffffffff81cde660->tqh_last) != NULL Message-ID: <X%2B3tfbxHGdiW1Kvt@raichu> In-Reply-To: <e73228a75b8f05c83214c62ed7e1ba68@neelc.org> References: <44528336fa9168966d121bf771e1e229@neelc.org> <X%2ByzpNIclmFYgbr7@raichu> <3c9ff844e527daacd04c51f48836b57d@neelc.org> <dbcc0e54eeb0080620ee4fb6d14845fc@neelc.org> <e73228a75b8f05c83214c62ed7e1ba68@neelc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 30, 2020 at 06:10:11PM -0800, Neel Chauhan wrote: > I have attached two files: > > * pcidump: A dump of `pciconf -lv` > * acpidump: A dump of `acpidump` > > Hope this can help. > > -Neel > > On 2020-12-30 14:36, Neel Chauhan wrote: > > Mark, thank you so much for your help! > > > > However, 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 > > > > What usually causes this? > > > > I'm no expert on PC hardware, my $DAYJOB is not related to hardware > > (I'm a C#/.NET developer for a living). > > > > I do however want my Spectre running FreeBSD and am willing to write > > patches (to some extent at least). Hi Neel, In the future please avoid posting to multiple threads on the same topic. I'm not sure what the problem is here. I cc'ed Doug, the author of the driver, to see if he can help. For context, the goal is to add support for a new device (ID 0x9a0b) to vmd(4), but vmd_bus_attach() fails with the aforementioned error. We found a minor bug already in that vmd_attach() does not call rman_fini() in error paths, but I don't know enough about vmd to usefully comment further.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X%2B3tfbxHGdiW1Kvt>