From owner-freebsd-net@freebsd.org Thu Aug 23 07:16:38 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A03781083BF0 for ; Thu, 23 Aug 2018 07:16:38 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0B43E84839 for ; Thu, 23 Aug 2018 07:16:38 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C3D5D1083BEF; Thu, 23 Aug 2018 07:16:37 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 792AB1083BEC for ; Thu, 23 Aug 2018 07:16:37 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-ed1-x542.google.com (mail-ed1-x542.google.com [IPv6:2a00:1450:4864:20::542]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD03784838 for ; Thu, 23 Aug 2018 07:16:36 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: by mail-ed1-x542.google.com with SMTP id p52-v6so2910966eda.12 for ; Thu, 23 Aug 2018 00:16:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hbmg1uwWEYJ/fKAheiih9OKqMYag6boojOV97yLgRjU=; b=gVis64x32q7rS9hgUeAOsJDsxYbRRkPp1RI9mJ+7/Y0OmE0uLenIBxLwePWPsTFVfl n/G8lne3lpyMaMms2v5SLWkiiE1h5Z8TGVXOi2QiNqKAEJRIRMwpLqXIJQobsULfhAod 4YTgozKjhc1flZP49RjEX8KwvkD+oBUXNWEfmzVJwwD9asjHDajyjqlehZdKhGPW4X/H CeEpC/X8+HsjgNB0zM6ljF9guyO+oflON4nmV3eh2ZWl9XAeCWZp2vPYOBJKpR5KCsUH kx4hYA8zjayf98dDOy3MW2StpsUMO1cmxOKKeQXZpGntOQ5beruyEKADysQD4QO+b1S6 W2Ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=hbmg1uwWEYJ/fKAheiih9OKqMYag6boojOV97yLgRjU=; b=KqD1nxn1VUcR8ng1Iuh+FhZyRSswZTnEr0roGkIjfUh8KQ7eSWArRhuBcP1/twjEa9 eWd9RUO+eQh8lIKErRJIpRPlDJB9dVB52MBUVBZhseVWfGDtlygJ1o7OJVUD4+iG07Hv leWBH1epeYwd+uXV4kyfEzSEvclarik26z0JS7roUgOGnmUGKLrhVuQGYvlmkznxwsz0 phAEcYTlv6dYJoUQ5yhLv9tiVLRs2ZhR2TOFrBROjQqIo+neoCHiUkF2U4NdhkHOJG85 0mt25OWpdtoZ+uXF53aTOhqsDb/Dzgh9FPSLpYFvJDouc+fEFyx5VF432L1A6bUT2X0Z bQ5w== X-Gm-Message-State: AOUpUlFhhdLsW/Vbh9Dvrs3qf+mGssMs+x5yrs/KthgoHBLrctzYRTRu X92e9G1meUuwoWRomJ9HxX/jxXLk X-Google-Smtp-Source: AA+uWPxPKaiJMQ4D2RFh0vFMsJFPjnUNkawoU6HPF74a14u4P1f2xoA7hP2djvAUMVlICz1dkN4cTw== X-Received: by 2002:a50:8b65:: with SMTP id l92-v6mr20793991edl.44.1535008595704; Thu, 23 Aug 2018 00:16:35 -0700 (PDT) Received: from kloomba ([77.94.198.250]) by smtp.gmail.com with ESMTPSA id o12-v6sm3264705edo.0.2018.08.23.00.16.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Aug 2018 00:16:34 -0700 (PDT) Date: Thu, 23 Aug 2018 11:16:28 +0400 From: Roman Bogorodskiy To: Kevin Bowling Cc: net@freebsd.org Subject: Re: igb: device_attach: igb1 attach returned 6 Message-ID: <20180823071626.GA4446@kloomba> References: <20180819142106.GA1539@kloomba> <20180822090811.GA1691@kloomba> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2018 07:16:39 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I haven't used this hardware before, so I don't if it ever worked. I only tried 11.2 and it doesn't work. I've also tried Ubuntu 18.04 and it doesn't work as well. Ubuntu prints the following error: [ 343.053031] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.= 0-k [ 343.053032] igb: Copyright (c) 2007-2014 Intel Corporation. [ 343.415346] igb 0000:01:00.0: added PHC on eth0 [ 343.415349] igb 0000:01:00.0: Intel(R) Gigabit Ethernet Network Connecti= on [ 343.415352] igb 0000:01:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:12:c0:00:= e9:14 [ 343.415427] igb 0000:01:00.0: eth0: PBA No: 106100-000 [ 343.415430] igb 0000:01:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 t= x queue(s) [ 343.416422] igb 0000:01:00.0 enp1s0f0: renamed from eth0 [ 343.416827] igb: probe of 0000:01:00.1 failed with error -3 [ 343.485242] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready [ 343.777894] igb 0000:01:00.2: added PHC on eth0 [ 343.777897] igb 0000:01:00.2: Intel(R) Gigabit Ethernet Network Connecti= on [ 343.777900] igb 0000:01:00.2: eth0: (PCIe:5.0Gb/s:Width x4) 00:12:c0:00:= e9:16 [ 343.777974] igb 0000:01:00.2: eth0: PBA No: 106100-000 [ 343.777977] igb 0000:01:00.2: Using MSI-X interrupts. 4 rx queue(s), 4 t= x queue(s) [ 343.781905] igb 0000:01:00.2 enp1s0f2: renamed from eth0 [ 343.849424] IPv6: ADDRCONF(NETDEV_UP): enp1s0f2: link is not ready [ 344.139715] igb 0000:01:00.3: added PHC on eth0 [ 344.139718] igb 0000:01:00.3: Intel(R) Gigabit Ethernet Network Connecti= on [ 344.139722] igb 0000:01:00.3: eth0: (PCIe:5.0Gb/s:Width x4) 00:12:c0:00:= e9:17 [ 344.139797] igb 0000:01:00.3: eth0: PBA No: 106100-000 [ 344.139800] igb 0000:01:00.3: Using MSI-X interrupts. 4 rx queue(s), 4 t= x queue(s) [ 344.141054] igb 0000:01:00.3 enp1s0f3: renamed from eth0 [ 344.213393] IPv6: ADDRCONF(NETDEV_UP): enp1s0f3: link is not ready I googled for this error message and found the following patch: https://www.spinics.net/lists/netdev/msg515557.html I'm not sure if it addresses my problem, but it looks related. I haven't tried that yet though because I don't have a spare drive to install Linux and rebuild drivers there. Kevin Bowling wrote: > The phy code hasn't changed in any material way that I can see in a > long time. So I wonder if it's timing or some initialization issue. >=20 > e1000_get_hw_semaphore > e1000_put_hw_semaphore > e1000_read_phy_reg_i2c >=20 > This looks a bit funny, I think the hw sem should be held over the i2c > call. Is there a chance you can get the same log from the working > kernel? >=20 > Regards, > Kevin >=20 > On Wed, Aug 22, 2018 at 2:08 AM, Roman Bogorodskiy > wrote: > > Kevin Bowling wrote: > > > >> Roman, > >> > >> Interesting.. can you set DBG to 1 sys/dev/e1000/e1000_osdep.h Line > >> 109 so we can see closer what is failing to initialize? > > > > Hi Kevin, > > > > Here's a relevant bit of dmesg with debug enabled: > > > > igb1: port 0xe040-0xe05f= mem 0xf7800000-0xf79fffff,0xf7c08000-0xf7c0bfff irq 17 at device 0.1 on pc= i1 > > e1000_set_mac_type > > igb1: attach_pre capping queues at 8 > > e1000_set_mac_type > > e1000_init_mac_ops_generic > > e1000_init_phy_ops_generic > > e1000_init_nvm_ops_generic > > e1000_init_function_pointers_82575 > > e1000_init_mac_params_82575 > > e1000_read_sfp_data_byte > > e1000_read_sfp_data_byte > > e1000_init_nvm_params_82575 > > e1000_init_phy_params_82575 > > e1000_reset_mdicnfg_82580 > > e1000_sgmii_uses_mdio_82575 > > e1000_get_phy_id_82575 > > e1000_sgmii_uses_mdio_82575 > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 1 was unreadable > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 2 was unreadable > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 3 was unreadable > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 4 was unreadable > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 5 was unreadable > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 6 was unreadable > > e1000_read_phy_reg_sgmii_82575 > > e1000_acquire_phy_82575 > > e1000_acquire_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > e1000_read_phy_reg_i2c > > I2CCMD Error bit set > > e1000_release_phy_82575 > > e1000_release_swfw_sync > > e1000_get_hw_semaphore > > e1000_put_hw_semaphore > > PHY address 7 was unreadable > > PHY Initialization Error > > igb1: Setup of Shared code failed, error -2 > > igb1: IFDI_ATTACH_PRE failed 6 > > device_attach: igb1 attach returned 6 > > > > I've also attached a complete dmesg. > > > >> Regards, > >> Kevin > >> > >> On Sun, Aug 19, 2018 at 7:21 AM, Roman Bogorodskiy = wrote: > >> > Hi, > >> > > >> > I have a 4-port Intel I350 network card. When I plug sfp rj45 module= to > >> > one of the ports, devices fails to initialise, e.g. ifconfig(8) only > >> > shows three igb interfaces (expected to be four): > >> > > >> > igb0: flags=3D8802 metric 0 mtu 1500 > >> > options=3De505bb > >> > ether 00:12:c0:00:e9:14 > >> > media: Ethernet autoselect > >> > status: no carrier > >> > nd6 options=3D29 > >> > igb1: flags=3D8802 metric 0 mtu 1500 > >> > options=3De505bb > >> > ether 00:12:c0:00:e9:16 > >> > media: Ethernet autoselect > >> > status: no carrier > >> > nd6 options=3D29 > >> > igb2: flags=3D8802 metric 0 mtu 1500 > >> > options=3De505bb > >> > ether 00:12:c0:00:e9:17 > >> > media: Ethernet autoselect > >> > status: no carrier > >> > nd6 options=3D29 > >> > > >> > dmesg has the following: > >> > > >> > igb0: port 0xe060-0xe= 07f mem 0xf7a00000-0xf7bfffff,0xf7c0c000-0xf7c0ffff irq 16 at device 0.0 on= pci1 > >> > igb0: attach_pre capping queues at 8 > >> > igb0: using 1024 tx descriptors and 1024 rx descriptors > >> > igb0: msix_init qsets capped at 8 > >> > igb0: pxm cpus: 4 queue msgs: 9 admincnt: 1 > >> > igb0: using 4 rx queues 4 tx queues > >> > igb0: Using MSIX interrupts with 5 vectors > >> > igb0: allocated for 4 tx_queues > >> > igb0: allocated for 4 rx_queues > >> > igb0: Ethernet address: 00:12:c0:00:e9:14 > >> > igb0: netmap queues/slots: TX 4/1024, RX 4/1024 > >> > igb1: port 0xe040-0xe= 05f mem 0xf7800000-0xf79fffff,0xf7c08000-0xf7c0bfff irq 17 at device 0.1 on= pci1 > >> > igb1: attach_pre capping queues at 8 > >> > igb1: Setup of Shared code failed, error -2 > >> > igb1: IFDI_ATTACH_PRE failed 6 > >> > device_attach: igb1 attach returned 6 > >> > igb1: port 0xe020-0xe= 03f mem 0xf7600000-0xf77fffff,0xf7c04000-0xf7c07fff irq 18 at device 0.2 on= pci1 > >> > igb1: attach_pre capping queues at 8 > >> > igb1: using 1024 tx descriptors and 1024 rx descriptors > >> > igb1: msix_init qsets capped at 8 > >> > igb1: pxm cpus: 4 queue msgs: 9 admincnt: 1 > >> > igb1: using 4 rx queues 4 tx queues > >> > igb1: Using MSIX interrupts with 5 vectors > >> > igb1: allocated for 4 tx_queues > >> > igb1: allocated for 4 rx_queues > >> > igb1: Ethernet address: 00:12:c0:00:e9:16 > >> > igb1: netmap queues/slots: TX 4/1024, RX 4/1024 > >> > igb2: port 0xe000-0xe= 01f mem 0xf7400000-0xf75fffff,0xf7c00000-0xf7c03fff irq 19 at device 0.3 on= pci1 > >> > igb2: attach_pre capping queues at 8 > >> > igb2: using 1024 tx descriptors and 1024 rx descriptors > >> > igb2: msix_init qsets capped at 8 > >> > igb2: pxm cpus: 4 queue msgs: 9 admincnt: 1 > >> > igb2: using 4 rx queues 4 tx queues > >> > igb2: Using MSIX interrupts with 5 vectors > >> > igb2: allocated for 4 tx_queues > >> > igb2: allocated for 4 rx_queues > >> > igb2: Ethernet address: 00:12:c0:00:e9:17 > >> > igb2: netmap queues/slots: TX 4/1024, RX 4/1024 > >> > > >> > And in pciconf(8) it shows as: > >> > > >> > igb0@pci0:1:0:0: class=3D0x020000 card=3D0x00101b6d chip=3D0x= 15228086 rev=3D0x01 hdr=3D0x00 > >> > vendor =3D 'Intel Corporation' > >> > device =3D 'I350 Gigabit Fiber Network Connection' > >> > class =3D network > >> > subclass =3D ethernet > >> > none1@pci0:1:0:1: class=3D0x020000 card=3D0x00101b6d chip=3D0x= 15228086 rev=3D0x01 hdr=3D0x00 > >> > vendor =3D 'Intel Corporation' > >> > device =3D 'I350 Gigabit Fiber Network Connection' > >> > class =3D network > >> > subclass =3D ethernet > >> > igb1@pci0:1:0:2: class=3D0x020000 card=3D0x00101b6d chip=3D0x= 15228086 rev=3D0x01 hdr=3D0x00 > >> > vendor =3D 'Intel Corporation' > >> > device =3D 'I350 Gigabit Fiber Network Connection' > >> > class =3D network > >> > subclass =3D ethernet > >> > igb2@pci0:1:0:3: class=3D0x020000 card=3D0x00101b6d chip=3D0x= 15228086 rev=3D0x01 hdr=3D0x00 > >> > vendor =3D 'Intel Corporation' > >> > device =3D 'I350 Gigabit Fiber Network Connection' > >> > class =3D network > >> > subclass =3D ethernet > >> > > >> > Any suggestions what could be wrong with that? > >> > > >> > The host is FreeBSD 12.0-ALPHA1 amd64 @ r337885. I don't know how/if= it > >> > worked before, just plugged that in. > >> > > >> > Roman Bogorodskiy > > > > Roman Bogorodskiy Roman Bogorodskiy --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJbfl9KAAoJEMltX/4IwiJqfkcIALwf88fnFIl1cwVhpJ/gPzJ9 CXpy9JXTUXR9AAn892BurHt/MZKRUrPLGDrt7pHU7eI7DAmXvEbO6jq4VGEIQSZ6 9KG6MUKZY2hwB5CnCVVocx5nP2WcaOV4yjfXz39I+UzIiJ9pqrFsbnwDDm3KVevk K5v+Wnqy2Z1FD3hu6TtuufKeR0Ktob/fZ9QyfYsckCwDQCBgtAMEeYI7wfY8jdUq iMMvqnGPVOaeM7PXvGhZvO0gP+HQxqqJ2WENfsnZIblK0O7Tqe4cgUB4mO/XUG2N jPub//MZfUBkogeQgFy/GzzCotUgFT8om3SWW1O15IEYE5GVjUOVScZsguvFRWA= =ZQo0 -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--