From nobody Fri Feb 03 14:17:19 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4P7d6F3Xfdz2pB7k for ; Fri, 3 Feb 2023 14:17:57 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4P7d6F0Ny1z4GX4 for ; Fri, 3 Feb 2023 14:17:57 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id hx15so15647105ejc.11 for ; Fri, 03 Feb 2023 06:17:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MfGfhdavec9GewEU4JSBpHsAzmOA5ti4jwEdnVQAKqE=; b=pNdNvsAbCkgWjFTzB5d7ebFujC6p3YIV0ji0TZqp7CZwjgYhNGA8oyhG2STNMaHY6G pVyteBWiwV2y7buUSIxzQVWkkw0JDNztCXCmvRGO3ZIrdwA/qCQCJ6NJYrQcKAR/pAPZ ArPz+qtv8eH0c3yqzdr8thsiexoIfcsSdX/HtDZI1Noa7UtVp85LRyXMMisqj480Z1ax cmJv1gozL8NKYZy+W9DdKoVfQkHbn2FxlheyHNXXFqx9KtlWnWivcslJPZTa7kvMpa9Q Y0en5W6hjQCSVoF0iIvDfjU7MI/YkgAwc9yhQeMuUcRRbGEYrpBYBlP1QTfDYKpWP+2U NaOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MfGfhdavec9GewEU4JSBpHsAzmOA5ti4jwEdnVQAKqE=; b=Eau9b3Dyljgy8Zg4vl/dh9QT3BpZ9Fl1cIlEIAPDkIXw/FJ04ERvM8dv+NqGQTVphg CKZqHdsRLWeiuoD3uo3XYOZJnZcOesaM+kLba/nuasDQsVQEH8BHJTCD+9/cQuTl5RcY yjmDGI1o8j4/Pbx7eZLxFVSR5RNNMoyTiuUfyXAQHq9hVLaPxqSNs4qd5OlTa5X3LY5A FvdoiDYAQkQHOiEEVzRhVvAb22XgogGOQD+89oOdSDT4ackFcu/zeFvVO8gFq2JLwbJG QMX6Fx7rt3g4unO8RpThABmxKl3ZKlwl6iyPSpxd86UTDOC3ZcSOvbO0bbgisBJ6zpw3 KylQ== X-Gm-Message-State: AO0yUKUsiTm5lJi12JUa9kUTplqhtq0/2Ai6Zn7sc+ExUdNJkto3bQsb 5tBMs3hwLYHG9g39LzVP9DJk6SN6i8klDbnY0YI6AV2CMmmXFg== X-Google-Smtp-Source: AK7set+NFIT5zZOL5hLRKsfxIiSS7bn+0mYCCjs5QkQIYBVAY9c/9eQ4NJoU6/ovanAvIW1AqS41/y3bjcDsqbh5Ln4= X-Received: by 2002:a17:907:cb25:b0:880:b580:d93 with SMTP id um37-20020a170907cb2500b00880b5800d93mr3111128ejc.276.1675433875645; Fri, 03 Feb 2023 06:17:55 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <09A3D05B-E269-437F-8ACB-A150EBCACF4E@dons.net.au> <128F6D81-D71B-4BC7-9143-8205E826088F@dons.net.au> <4E67D54E-CF0E-4A56-9B6B-51C359B7CEE2@dons.net.au> In-Reply-To: From: Mario Marietto Date: Fri, 3 Feb 2023 15:17:19 +0100 Message-ID: Subject: Re: devctl: Failed to detach pci0:1:0:0: Device busy / devctl: Failed to set pci0:1:0:0 driver to ppt: Device busy To: "Daniel O'Connor" Cc: freebsd-hackers Content-Type: multipart/alternative; boundary="00000000000000a96f05f3cc59f4" X-Rspamd-Queue-Id: 4P7d6F0Ny1z4GX4 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000000a96f05f3cc59f4 Content-Type: text/plain; charset="UTF-8" Very interesting behavior. I've added this new line in /etc/rc.conf : (until some minutes ago I didn't use it because I was using the intel driver,installed by the package : xf86-video-intel-2.99.917.916_2,1) kld_list="i915kms acpi_video" and this line in /boot/loader.conf : pptdevs="1/0/0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3 5/0/0" and boom. pptdevs worked again: # pciconf -l ppt0@pci0:1:0:0: class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1c02 subvendor=0x19da subdevice=0x2438 ppt1@pci0:1:0:1: class=0x040300 rev=0xa1 hdr=0x00 vendor=0x10de device=0x10f1 subvendor=0x19da subdevice=0x2438 ppt2@pci0:2:0:0: class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1e04 subvendor=0x19da subdevice=0x2503 ppt3@pci0:2:0:1: class=0x040300 rev=0xa1 hdr=0x00 vendor=0x10de device=0x10f7 subvendor=0x19da subdevice=0x2503 ppt4@pci0:2:0:2: class=0x0c0330 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1ad6 subvendor=0x19da subdevice=0x2503 ppt5@pci0:2:0:3: class=0x0c8000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1ad7 subvendor=0x19da subdevice=0x2503 So,maybe there is some incompatibility between the intel and the pptdevs driver ? take also in consideration that on xorg.cong I'm still using the intel driver : Section "Device" Identifier "Card0" Driver "intel" BusID "PCI:0:2:0" EndSection. It's a confusing situation. Il giorno ven 3 feb 2023 alle ore 14:27 Daniel O'Connor ha scritto: > > > > On 3 Feb 2023, at 23:52, Mario Marietto wrote: > > To put the pci addresses under ppt using the loader.conf always worked > for me. I would like to understand why it does not work anymore for some > months. Maybe some new feature and some obscure bug has been introduced > inside the bhyve source code. This is important to understand why I'm not > able to attach / detach the nVidia driver from the host to the guest os and > it lets me think that your consideration may be relevant in some way. > > It would have been more helpful if you had said up front that it used to > work for you.. > > Do you mean it used to work for these nvidia devices or something else, > or..? > > -- > Daniel O'Connor > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > > -- Mario. --00000000000000a96f05f3cc59f4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Very interesting= behavior. I've added this new line in /etc/rc.conf : (until some minut= es ago I didn't use it because I was using the intel driver,installed b= y the package : xf86-video-intel-2.99.917.916_2,1)

kld_list=3D"i915kms acpi_video"

and this line in /boot/loader.conf = :

<= /span>
pptdevs=3D"1/0= /0 1/0/1 2/0/0 2/0/1 2/0/2 2/0/3 5/0/0"

<= /div>
and boom. pptdevs worked aga= in:

# pciconf -l

ppt0@pci0:1:0:0: =C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x030000 rev=3D0xa1 hdr=3D0x00 = vendor=3D0x10de device=3D0x1c02 subvendor=3D0x19da subdevice=3D0x2438
ppt1@pci0:1:0:1: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0class=3D0x040300 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device= =3D0x10f1 subvendor=3D0x19da subdevice=3D0x2438
ppt2@pci0:2:0:0: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x03= 0000 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x1e04 subvendor=3D0x19= da subdevice=3D0x2503
ppt3@pci0:2:0:1: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x04= 0300 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x10f7 subvendor=3D0x19= da subdevice=3D0x2503
ppt4@pci0:2:0:2: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x0c= 0330 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x1ad6 subvendor=3D0x19= da subdevice=3D0x2503
ppt5@pci0:2:0:3: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0class=3D0x0c= 8000 rev=3D0xa1 hdr=3D0x00 vendor=3D0x10de device=3D0x1ad7 subvendor=3D0x19= da subdevice=3D0x2503

So,maybe there i= s some incompatibility between the intel and the pptdevs driver ? take also= in consideration that on xorg.cong I'm still using the intel driver :<= br>

Section "Device"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Identifier =C2=A0&quo= t;Card0"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Driver =C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0"intel"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0BusID =C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0"PCI:0:2:0"
EndSection.

It's a confusing situation.

Il g= iorno ven 3 feb 2023 alle ore 14:27 Daniel O'Connor <darius@dons.net.au> ha scri= tto:


> On 3 Feb 2023, at 23:52, Mario Marietto <marietto2008@gmail.com> wrote:
> To put the pci addresses under ppt using the loader.conf always worked= for me. I would like to understand why it does not work anymore for some m= onths. Maybe some new feature and some obscure bug has been introduced insi= de the bhyve source code. This is important to understand why I'm not a= ble to attach / detach the nVidia driver from the host to the guest os and = it lets me think that your consideration may be relevant in some way.

It would have been more helpful if you had said up front that it used to wo= rk for you..

Do you mean it used to work for these nvidia devices or something else, or.= .?

--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum



--
Mario.
=
--00000000000000a96f05f3cc59f4--