From owner-freebsd-current@freebsd.org Tue Feb 23 15:31:46 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CC1CAB1CD6; Tue, 23 Feb 2016 15:31:46 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 480ED18EC; Tue, 23 Feb 2016 15:31:46 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id e185so164211820vkb.1; Tue, 23 Feb 2016 07:31:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r2EAANXTKNfU2J4a+9+7c0EipIdasK+EQP1oEAg39+A=; b=mqrqsviQaHGbmw41Mx8g/eBkNxh2+7irO7mexsqTMKG3n/+w7Biyda2wc/LHU672B9 2/wjcGySo8fTf7JPd+0d6HZGOD/p0yHxwfYp+uyxkM/1ApRh4vr0pSOc1/9LQSPCMk5M hqK2oVgVRzAi9qPTYhAbmd+Xu34KWCQnEmRCIww86qZhjofssQ3U+so91YqOmTHt3oZ6 ztLbN7Zn1IO+KDT8J99J1rqpH8d9hhWy658d1H0App4QM2Rj2xVX0mAdGwu+DnEwsLaY OYqWCo33JK+ssEqs8JTc9gDYGyrfH+gLVqnyflRIG7jxrtt4IqL8p7iVJpHECdO7nJhk pLWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=r2EAANXTKNfU2J4a+9+7c0EipIdasK+EQP1oEAg39+A=; b=JX/Dd30HDPRXJyNyMgoGFKPaeJ+L1f035gdoF//wtXraVhhcwHNk830lZQ92GRynYN VBZDESmKapn10yvnjNJ8LwGxm1Ce0lH0EUYnio/R9I4K1oBH7lfZKJ7ok/atCAE47lKm MZfajwofMc04qYebMOk+ueMys7xxMDoyFkGc04wTCmvk1MFW/B79X3XPU4f8cR/f/WEO Sa3gFLsWtIAiII3+LzEDWlZjGI4pvRUNdj67eWA0uxbb1GddPr7yRsFBOP2cY3WFLLti MqoO63kqo3Xwk1Ll4FcDEeSRlKFpQxT6Ebzm1nzcmT86XsvplYcsA3TQnrs/krzjlWGp skTQ== X-Gm-Message-State: AG10YOS0i28PBRX9Iu/mgO1fO82DxtblEn4HaI59jDZxdR7iRN3jFu/Ybq6I0leMcZDgZLsmjuAzzVnZxIMfHg== MIME-Version: 1.0 X-Received: by 10.31.47.88 with SMTP id v85mr28833311vkv.118.1456241504762; Tue, 23 Feb 2016 07:31:44 -0800 (PST) Received: by 10.31.194.194 with HTTP; Tue, 23 Feb 2016 07:31:44 -0800 (PST) In-Reply-To: References: Date: Tue, 23 Feb 2016 10:31:44 -0500 Message-ID: Subject: Re: sr-iov issues, reset_hw() failed with error -100 From: Ultima To: Eric Joyner Cc: freebsd-current@freebsd.org, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2016 15:31:46 -0000 Upgraded to r295920 and used generic kernel. Then rebooted and checked bios thoroughly. I found 3, yes 3 different areas in the bios for enabling sr-iov (some screen shots below). 2 are for vt-d(Forgot to take a screenshot of the 2nt, all were enabled) and one for sr-iov(was disabled). Unfortunately with generic kernel, and all these options enabled, adding only 2vf's resulted in the same behavior as above. Little bit of good news, when removing the vf's and ifconfig ix1 down/up the interface's functionality is restored. I also tested this on MYKERNEL r295920, sr-iov option in bios likely played a role in this. If you have any ideas, I'm willing to test them. Thanks! =] VT-d screen: https://puu.sh/niyiq/4fee92e4a3.jpgn PCI advanced options: https://puu.sh/niyjg/88e71e48d9.jpgn Ultima On Mon, Feb 22, 2016 at 9:46 PM, Ultima wrote: > I forgot to mention my kernel conf.... I'm not sure if it would cause this > issue, but I'll test again with GENERIC. > > --- /usr/src/sys/amd64/conf/GENERIC 2016-02-22 21:05:37.152953000 -0500 > +++ /root/MYKERNEL-11-CURRENT-AMD64 2015-12-28 19:18:22.893391452 -0500 > @@ -91,6 +91,12 @@ > options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > options MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones > > +### VIMAGE ### > +options VIMAGE > + > +### ROUTE TABLES ### > +options ROUTETABLES=2 > + > # Make an SMP-capable kernel by default > options SMP # Symmetric MultiProcessor Kernel > > The interface is just dead after creating the vf's earlier. Recreating > with only 2, its still dead. > > Running out of ideas, decided to try a tcpdump... > > # dhclient ix1 > DHCPREQUEST on ix1 to 255.255.255.255 port 67 > DHCPREQUEST on ix1 to 255.255.255.255 port 67 > DHCPREQUEST on ix1 to 255.255.255.255 port 67 > DHCPDISCOVER on ix1 to 255.255.255.255 port 67 interval 7 > DHCPDISCOVER on ix1 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on ix1 to 255.255.255.255 port 67 interval 14 > > # tcpdump -i ix1 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on ix1, link-type EN10MB (Ethernet), capture size 262144 bytes > 21:41:13.234688 IP 192.168.1.145.bootpc > 255.255.255.255.bootps: > BOOTP/DHCP, Request from -Hidden- (oui Unknown), length 300 > 21:41:16.236671 IP 192.168.1.145.bootpc > 255.255.255.255.bootps: > BOOTP/DHCP, Request from -Hidden- (oui Unknown), length 300 > 21:41:23.243242 IP 192.168.1.145.bootpc > 255.255.255.255.bootps: > BOOTP/DHCP, Request from -Hidden- (oui Unknown), length 300 > 21:41:38.261015 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from -Hidden- (oui Unknown), length 300 > 21:41:45.284752 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from -Hidden- (oui Unknown), length 300 > 21:41:58.292223 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from -Hidden- (oui Unknown), length 300 > > I don't think this is that helpful tho. =/ > tcpdump on the other end, the packets are never received. > > I'v already double checked VT-d, but I'll make it tripple! =] I can't > reset the system right now, but ill send an update when possible with only > 2 vf's and unmodified generic. > > Ultima > > On Mon, Feb 22, 2016 at 8:52 PM, Eric Joyner wrote: > >> I don't really have any ideas on the error -100. Error -100 means there >> was a mailbox error, so something failed in the initial communications >> setup between the PF and VF, but I don't know what exactly went wrong. >> >> I'm grasping at straws, but try using a smaller number of VFs initially, >> like 2? And check to see if VT-d is enabled in your BIOS? (Though I >> would've expected iovctl to fail). >> >> - Eric >> >> >> On Mon, Feb 22, 2016 at 12:01 PM Ultima wrote: >> >>> After reboot... >>> >>> ifconfig ix1 up >>> >>> dhclient ix1 >>> DHCPDISCOVER on ix1 to 255.255.255.255 port 67 interval 4 >>> DHCPOFFER from 192.168.1.1 >>> DHCPREQUEST on ix1 to 255.255.255.255 port 67 >>> DHCPACK from 192.168.1.1 >>> bound to 192.168.1.145 -- renewal in 21600 seconds. >>> >>> ix0 down >>> ping 192.168.1.1 >>> PING 192.168.1.1 (192.168.1.1): 56 data bytes >>> 64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.149 ms >>> 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.171 ms >>> 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.167 ms >>> >>> iovctl -Cf /etc/iovctl.conf >>> >>> ping 192.168.1.1 >>> PING 192.168.1.1 (192.168.1.1): 56 data bytes >>> ^C >>> --- 192.168.1.1 ping statistics --- >>> 29 packets transmitted, 0 packets received, 100.0% packet loss >>> ifconfig ix1 up >>> ping 192.168.1.1 >>> PING 192.168.1.1 (192.168.1.1): 56 data bytes >>> ^C >>> --- 192.168.1.1 ping statistics --- >>> 12 packets transmitted, 0 packets received, 100.0% packet loss >>> >>> ix1 is no longer usable until a restart... >>> >>> iovctl -Dd ix1 >>> ifconfig ix1 up >>> ping 192.168.1.1 >>> PING 192.168.1.1 (192.168.1.1): 56 data bytes >>> ^C >>> --- 192.168.1.1 ping statistics --- >>> 9 packets transmitted, 0 packets received, 100.0% packet loss >>> >>> >>> >>> Is there anything else that maybe useful? >>> >>> here is my ifconfig at the end (after ifconfig ix0 up) >>> >>> >>> ix0: flags=8943 metric 0 >>> mtu 1500 >>> >>> options=e400b9 >>> ether -Hidden- >>> inet 192.168.1.8 netmask 0xffffff00 broadcast 192.168.1.255 >>> inet 192.168.1.9 netmask 0xffffff00 broadcast 192.168.1.255 >>> nd6 options=29 >>> media: Ethernet autoselect (10Gbase-T ) >>> status: active >>> ix1: flags=8843 metric 0 mtu 1500 >>> >>> options=e407bb >>> ether -Hidden- >>> inet 192.168.1.145 netmask 0xffffff00 broadcast 192.168.1.255 >>> nd6 options=29 >>> media: Ethernet autoselect (10Gbase-T ) >>> status: active >>> lo0: flags=8049 metric 0 mtu 16384 >>> options=600003 >>> inet6 ::1 prefixlen 128 >>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 >>> inet 127.0.0.1 netmask 0xff000000 >>> nd6 options=21 >>> groups: lo >>> bridge0: flags=8843 metric 0 mtu >>> 1500 >>> ether -Hidden- >>> nd6 options=9 >>> groups: bridge >>> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >>> maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 >>> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >>> member: ix0 flags=143 >>> ifmaxaddr 0 port 1 priority 128 path cost 2000 >>> member: epair0a flags=143 >>> ifmaxaddr 0 port 5 priority 128 path cost 2000 >>> epair0a: flags=8943 >>> metric 0 mtu 1500 >>> options=8 >>> ether -Hidden- >>> inet6 fe80::ff:70ff:fe00:50a%epair0a prefixlen 64 scopeid 0x5 >>> nd6 options=21 >>> media: Ethernet 10Gbase-T (10Gbase-T ) >>> status: active >>> groups: epair >>> >>> On Mon, Feb 22, 2016 at 1:51 PM, Eric Joyner wrote: >>> >>>> Did you do an ifconfig up on ix1 before loading the VF driver? >>>> >>>> On Sat, Feb 20, 2016 at 11:57 AM Ultima wrote: >>>> >>>>> Decided to do some testing with iovctl to see how sr-iov is coming >>>>> along. >>>>> Currently when adding the vf's there are a couple errors, and the >>>>> network >>>>> no longer function after iovctl is started. My guess is the reset_hw() >>>>> call >>>>> that is failing. Any ideas why this call would fail? I tested this on >>>>> both >>>>> ports, ix1 is detached and unused for this test, however inserting a >>>>> cable >>>>> results in an unusable port. iovctl -Dd ix1 removes the vf's, however >>>>> functionality is still not restored without a system restart. >>>>> >>>>> FreeBSD S1 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r295736: Wed Feb 17 >>>>> 21:17:28 EST 2016 root@S1:/usr/obj/usr/src/sys/MYKERNEL amd64 >>>>> >>>>> /boot/loader.conf >>>>> hw.ix.num_queues="4" >>>>> >>>>> /etc/iovctl.conf >>>>> PF { >>>>> device : ix1; >>>>> num_vfs : 31; >>>>> } >>>>> >>>>> DEFAULT { >>>>> passthrough : true; >>>>> } >>>>> VF-0 { >>>>> passthrough : false; >>>>> } >>>>> VF-1 { >>>>> passthrough : false; >>>>> } >>>>> >>>>> # iovctl -C -f /etc/iovctl.conf >>>>> >>>>> dmesg >>>>> ixv0: >>>> 1.4.6-k> at device 0.129 on pci12 >>>>> ixv0: Using MSIX interrupts with 2 vectors >>>>> ixv0: ixgbe_reset_hw() failed with error -100 >>>>> device_attach: ixv0 attach returned 5 >>>>> ixv0: >>>> 1.4.6-k> at device 0.131 on pci12 >>>>> ixv0: Using MSIX interrupts with 2 vectors >>>>> ixv0: ixgbe_reset_hw() failed with error -100 >>>>> device_attach: ixv0 attach returned 5 >>>>> pci12: at device 0.133 (no driver attached) >>>>> pci12: at device 0.135 (no driver attached) >>>>> pci12: at device 0.137 (no driver attached) >>>>> pci12: at device 0.139 (no driver attached) >>>>> pci12: at device 0.141 (no driver attached) >>>>> pci12: at device 0.143 (no driver attached) >>>>> pci12: at device 0.145 (no driver attached) >>>>> pci12: at device 0.147 (no driver attached) >>>>> pci12: at device 0.149 (no driver attached) >>>>> pci12: at device 0.151 (no driver attached) >>>>> pci12: at device 0.153 (no driver attached) >>>>> pci12: at device 0.155 (no driver attached) >>>>> pci12: at device 0.157 (no driver attached) >>>>> pci12: at device 0.159 (no driver attached) >>>>> pci12: at device 0.161 (no driver attached) >>>>> pci12: at device 0.163 (no driver attached) >>>>> pci12: at device 0.165 (no driver attached) >>>>> pci12: at device 0.167 (no driver attached) >>>>> pci12: at device 0.169 (no driver attached) >>>>> pci12: at device 0.171 (no driver attached) >>>>> pci12: at device 0.173 (no driver attached) >>>>> pci12: at device 0.175 (no driver attached) >>>>> pci12: at device 0.177 (no driver attached) >>>>> pci12: at device 0.179 (no driver attached) >>>>> pci12: at device 0.181 (no driver attached) >>>>> pci12: at device 0.183 (no driver attached) >>>>> pci12: at device 0.185 (no driver attached) >>>>> pci12: at device 0.187 (no driver attached) >>>>> pci12: at device 0.189 (no driver attached) >>>>> >>>>> pciconf -lv >>>>> ix1@pci0:129:0:1: class=0x020000 card=0x00001458 chip=0x15288086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'Ethernet Controller 10-Gigabit X540-AT2' >>>>> class = network >>>>> subclass = ethernet >>>>> none155@pci0:129:0:129: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> none156@pci0:129:0:131: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt0@pci0:129:0:133: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt1@pci0:129:0:135: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt2@pci0:129:0:137: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt3@pci0:129:0:139: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt4@pci0:129:0:141: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt5@pci0:129:0:143: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt6@pci0:129:0:145: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt7@pci0:129:0:147: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt8@pci0:129:0:149: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt9@pci0:129:0:151: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt10@pci0:129:0:153: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt11@pci0:129:0:155: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt12@pci0:129:0:157: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt13@pci0:129:0:159: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt14@pci0:129:0:161: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt15@pci0:129:0:163: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt16@pci0:129:0:165: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt17@pci0:129:0:167: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt18@pci0:129:0:169: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt19@pci0:129:0:171: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt20@pci0:129:0:173: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt21@pci0:129:0:175: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt22@pci0:129:0:177: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt23@pci0:129:0:179: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt24@pci0:129:0:181: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt25@pci0:129:0:183: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt26@pci0:129:0:185: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt27@pci0:129:0:187: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> ppt28@pci0:129:0:189: class=0x020000 card=0x00001458 chip=0x15158086 >>>>> rev=0x01 hdr=0x00 >>>>> vendor = 'Intel Corporation' >>>>> device = 'X540 Ethernet Controller Virtual Function' >>>>> class = network >>>>> subclass = ethernet >>>>> >>>>> Ultima >>>>> _______________________________________________ >>>>> 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" >>>>> >>>> >>> >