From owner-freebsd-hackers@freebsd.org Thu Dec 31 15:25:53 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DD5B14C4E1B for ; Thu, 31 Dec 2020 15:25:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D6BnF5lQ6z4sj3; Thu, 31 Dec 2020 15:25:53 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk1-x734.google.com with SMTP id z11so16548850qkj.7; Thu, 31 Dec 2020 07:25:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=Wk+c0vmpOn9xcv6nPUam85/xZQd7bK7px+5r/0xdWjY=; b=I8FvYZ0nkY5ZcKxE5rB1cvAzp5nDkTHquahaz6C7/j9YJElyn9OERcX+WO0wNjacze nLLYj9xKNHfOrQvt0l8x3fNpbnqcFab3lzf0HwQ1ceNhJwhunSE4gkop4+jl1igndujR gt6b4pnSL2rBguSn/Y8xNMKIOAlo5ds1ReSvlWK0Skl96+EVOmQUSo7BIp2ejaEUwMQX MX8mg7dbmBKE0YSzriFrYd2+x9fMdBSB/19Q4azR2jQiMXGuNyko28IWwfylo2vfL1Y7 1OPNhwEmC8Uu339W3RMhGSFRbqEu4uYHWGWUbpnnqmGhTs/w5xgYXI23H2OussUmsWfw JL6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to; bh=Wk+c0vmpOn9xcv6nPUam85/xZQd7bK7px+5r/0xdWjY=; b=qg4TUvWVezjL8uP9WsVr5Biwfm+R4l7i7kxk/LXuIonshd3g8HISlRd/m90RSl0hff Og6075NbvBH9aOrvukSMx1fo//GlUAU1UfSOR9tkpk8WrrxnXOD0LR1lewYuDcYAZ7f6 c5Ms7voxn7wsq3WDe/Q9+0yriKtbrLyf+u0ApKEh6xxY88eIjcUqHB3e1CyTXU46PyOE nhfLM2Ly8MrzEylS/wdkEI8Gb8ZAvBZ+0wW1Fj4oL55zfWddH9dpJ7Y1VOBZTPnoaqx3 qAR+YUigkZYJXfH06dSMN+ckOuJEiHd1nJKdfKFZYZFNe3I/3QPRSziNZKdREME9m0pB lvpg== X-Gm-Message-State: AOAM530LcpzRYJZnwCwo1F7PQvrHWpKkuMlpTf4NXs7SvHCV0/GPDRuU WX5whqarqIHxm7bx/2EhFjNnW60UA+tzpQ== X-Google-Smtp-Source: ABdhPJxbgoIggkO0OJdJp87aET7CbGdPa192vcB2e96XqhWcpDGYf+genH7rntMgDVL2xM4JG1U23A== X-Received: by 2002:a05:620a:68e:: with SMTP id f14mr24113082qkh.460.1609428352676; Thu, 31 Dec 2020 07:25:52 -0800 (PST) Received: from raichu ([142.126.164.150]) by smtp.gmail.com with ESMTPSA id z30sm29555438qtc.15.2020.12.31.07.25.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 31 Dec 2020 07:25:51 -0800 (PST) Sender: Mark Johnston Date: Thu, 31 Dec 2020 10:25:49 -0500 From: Mark Johnston To: Neel Chauhan 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: References: <44528336fa9168966d121bf771e1e229@neelc.org> <3c9ff844e527daacd04c51f48836b57d@neelc.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4D6BnF5lQ6z4sj3 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Dec 2020 15:25:53 -0000 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.