Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 07 Sep 2012 14:46:39 +0200
From:      Harald Schmalzbauer <h.schmalzbauer@omnilan.de>
To:        Jack Vogel <jfvogel@gmail.com>
Cc:        stable@freebsd.org
Subject:   Re: intel 82579 nic support?
Message-ID:  <5049ECAF.3020709@omnilan.de>
In-Reply-To: <CAFOYbcmS1jG0e5jxV0GoD7YoV9=OwJxXdY1EO6yZVmAGZm=A%2BA@mail.gmail.com>
References:  <50491E26.1010106@omnilan.de> <CAFOYbcmS1jG0e5jxV0GoD7YoV9=OwJxXdY1EO6yZVmAGZm=A%2BA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig276C8CD127D49CE4676D9926
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

 schrieb Jack Vogel am 07.09.2012 00:27 (localtime):
> 82579 is not a NIC, its a PHY, and it you look at the current code you
> will see the support
> is in there. So the real question is what the actual NIC is, how about
> a pciconf -lv?
>
> Next, how are you trying "to pass through the device into my FreeBSD
> VM", what is
> the virtualization environment.
>
> Widely spread, uh ya, but not virtualized, so tell me more about the
> environment.

Thanks for your reply. I didn't know that this phy is officially
supported, so I haven't provided any info.
But I'm happy you asked for:

PassThrough is done as PCI dev, with VT-d and DMA support (have been
using that for SAS controllers many times and FreeBSD sees the devices
like without vmware in between on the same maschine)
According to VMware, the phy is 82579LM
With "if_em" in the kernel and the 82579 configured as PCI-passthrough I
get these lines at boot time:
em2: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x7000-0x701f mem
0xd6720000-0xd673ffff,0xd6702000-0xd6702fff irq 18 at device 0.0 on pci6
em2: Memory Access and/or Bus Master bits were not set!
em2: Using an MSI interrupt
em2: Setup of Shared code failed
device_attach: em2 attach returned 6
(em0+1 are virtual-HW devices, em2 thy physical PCI-passthrough)

Now if I kldload "if_igb", it seems to also try to attach to the 82579
(at least kernel prints these lines (again)):
em2: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x7000-0x701f mem
0xd6720000-0xd673ffff,0xd6702000-0xd6702fff irq 18 at device 0.0 on pci6
em2: Memory Access and/or Bus Master bits were not set!
em2: Using an MSI interrupt
em2: Setup of Shared code failed
device_attach: em2 attach returned 6

Disabling MSI (MSIX) hasn't changed anythin.

Here's the pciconf:
em1@pci0:5:0:0:    class=3D0x020000 card=3D0x07d015ad chip=3D0x10d38086
rev=3D0x00 hdr=3D0x00
    vendor     =3D 'Intel Corporation'
    device     =3D '82574L Gigabit Network Connection'
    class      =3D network
    subclass   =3D ethernet
none1@pci0:6:0:0:    class=3D0x020000 card=3D0x35788086 chip=3D0x15028086=

rev=3D0x05 hdr=3D0x00
    vendor     =3D 'Intel Corporation'
    device     =3D '82579LM Gigabit Network Connection'
    class      =3D network
    subclass   =3D ethernet

Thanks you for your attention!

-Harry


--------------enig276C8CD127D49CE4676D9926
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iEYEARECAAYFAlBJ7LoACgkQLDqVQ9VXb8gqnwCeM9uVXSTCM0oQu2O2dDvOkwTC
zUIAn0Hp/KSdrZYU4rgLfEaK4HP7ASHS
=hW6Q
-----END PGP SIGNATURE-----

--------------enig276C8CD127D49CE4676D9926--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5049ECAF.3020709>