Date: Thu, 18 Sep 2014 10:48:33 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Guido Falsi <mad@madpilot.net> Cc: Kevin Oberman <rkoberman@gmail.com>, Adrian Chadd <adrian@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: 11.0-CURRENT and Lenovo ThinkPad E540: No LAN, no WiFI Message-ID: <20140918104833.3a473d7e.ohartman@zedat.fu-berlin.de> In-Reply-To: <541A9504.1010502@madpilot.net> References: <20140915233833.5bdd0725.ohartman@zedat.fu-berlin.de> <CAN6yY1vP-CCOy8aWp8m1z2ijkRH5pm-UeXKf9i-QKf4jesCKUA@mail.gmail.com> <CAJ-Vmomyd6yPWOdWO-GUe_ZxFpyE-FZbsdEVBGhcMUr64_o5gg@mail.gmail.com> <20140916131854.46acc5fb.ohartman@zedat.fu-berlin.de> <CAJ-Vmomkqzf%2BDZpg15gEyv5ZY3ePNu-0h4n1PqJX9uO8VpA5-g@mail.gmail.com> <20140918095851.6e743183.ohartman@zedat.fu-berlin.de> <541A9504.1010502@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/cMSIMgDXmMySkuIiJUqzZir
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Am Thu, 18 Sep 2014 10:17:08 +0200
Guido Falsi <mad@madpilot.net> schrieb:
> On 09/18/14 09:58, O. Hartmann wrote:
> > Am Tue, 16 Sep 2014 08:40:25 -0700
> > Adrian Chadd <adrian@freebsd.org> schrieb:
> >=20
> >> Ah, jumbo frames. Maybe you got lucky and some ethernet drivers
> >> default to accepting larger frames even if the MTU is 1500.
> >>
> >>
> >> -a
> >=20
> >=20
> > After all, I managed to get the NIC up and running. But the culprit is =
that I have to
> > take the NIC down and then up to make it working once the system has bo=
otet. That is
> > annoying. Lucckily, I can provide better informations since the box s n=
ow attached to
> > the network. Here we go:
> >=20
>=20
> I have a similar situation with my nick on a tower system.
>=20
> I need to change at least one flag on the card to have it working, I can
> also just set the flag to the value it already has.
>=20
> I'm using a small startup script which actually does this:
>=20
> start_cmd=3D"ifconfig ${refix_if} tso"
>=20
>=20
> > LAN:
> > re0@pci0:4:0:0: class=3D0x020000 card=3D0x502817aa chip=3D0x816810ec re=
v=3D0x10 hdr=3D0x00
> > vendor =3D 'Realtek Semiconductor Co., Ltd.'
> > device =3D 'RTL8111/8168B PCI Express Gigabit Ethernet controll=
er'
> > class =3D network
> > subclass =3D ethernet
> > bar [10] =3D type I/O Port, range 32, base 0x3000, size 256, enab=
led
> > bar [18] =3D type Memory, range 64, base 0xf1d04000, size 4096, e=
nabled
> > bar [20] =3D type Memory, range 64, base 0xf1d00000, size 16384, =
enabled
> > cap 01[40] =3D powerspec 3 supports D0 D1 D2 D3 current D0
> > cap 05[50] =3D MSI supports 1 message, 64 bit=20
> > cap 10[70] =3D PCI-Express 2 endpoint IRQ 1 max data 128(128) link =
x1(x1)
> > speed 2.5(2.5) ASPM disabled(L0s/L1)
> > cap 11[b0] =3D MSI-X supports 4 messages, enabled
> > Table in map 0x20[0x0], PBA in map 0x20[0x800]
> > cap 03[d0] =3D VPD
> > ecap 0001[100] =3D AER 2 0 fatal 0 non-fatal 1 corrected
> > ecap 0002[140] =3D VC 1 max VC0
> > ecap 0003[160] =3D Serial 1 01000000684ce000
> > ecap 0018[170] =3D LTR 1
> > ecap 001e[178] =3D unknown 1
> > PCI-e errors =3D Correctable Error Detected
> > Corrected =3D Receiver Error
> >
>=20
> re0@pci0:3:0:0: class=3D0x020000 card=3D0x11c01734 chip=3D0x816810ec rev=
=3D0x07
> hdr=3D0x00
> vendor =3D 'Realtek Semiconductor Co., Ltd.'
> device =3D 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
> class =3D network
> subclass =3D ethernet
> bar [10] =3D type I/O Port, range 32, base 0xd000, size 256, enabled
> bar [18] =3D type Prefetchable Memory, range 64, base 0xf2104000,
> size 4096, enabled
> bar [20] =3D type Prefetchable Memory, range 64, base 0xf2100000,
> size 16384, enabled
> cap 01[40] =3D powerspec 3 supports D0 D1 D2 D3 current D0
> cap 05[50] =3D MSI supports 1 message, 64 bit
> cap 10[70] =3D PCI-Express 2 endpoint IRQ 1 max data 128(128) link x1=
(x1)
> speed 2.5(2.5) ASPM disabled(L0s/L1)
> cap 11[b0] =3D MSI-X supports 4 messages, enabled
> Table in map 0x20[0x0], PBA in map 0x20[0x800]
> cap 03[d0] =3D VPD
> ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 1 corrected
> ecap 0002[140] =3D VC 1 max VC0
> ecap 0003[160] =3D Serial 1 0100000004000001
> PCI-e errors =3D Correctable Error Detected
> Unsupported Request Detected
> Corrected =3D Advisory Non-Fatal Error
>=20
> it's similar hardware, same chip, different revision. I already reported
> this on net@ but no patch could really solve the issue.
>=20
Hello.
Well, it seems the same here with taht specific NIC. Changing ANYTHING, eve=
n already
enabled features, or bringing the NIC down and then up seem to solve this p=
roblem.
I guess, I file a PR to make this issue memorized.
Regards,
Oliver
--Sig_/cMSIMgDXmMySkuIiJUqzZir
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJUGpxhAAoJEOgBcD7A/5N8ff4H/2IveS1fSLUXMN5S/ZSos6Jg
ZQN3FWd5RShlKSVhutKwDNmqAtQVIIS3ezm2sYnTs2JUjXk9tn6EerQzzHr4ox5v
NSI0QWSVRFP+YHBohOqcIn4yZV6CM9stv32ay2SEbpjCuwpBQ8mZA4rTWpb3KtpO
JILrbCDuvC93E7Ig1MzWWBD1Uxa20bb7bqoRV4gXAbcfKbNgjIpgR8SmuIwkxvv2
+mlTKQrURYEQUX/IgbK7csx/uG+C0oslFw1uWZTHyexbXFzYPOz9t7STxk2aNDKd
/XPdDAvq2/ccQ7R3czDrMRPRoOo4/MP3H3d1cmN0fPBmGTSolGTzCzBCVxfcGgU=
=p2V6
-----END PGP SIGNATURE-----
--Sig_/cMSIMgDXmMySkuIiJUqzZir--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140918104833.3a473d7e.ohartman>