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>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
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:
> >
> >> Ah, jumbo frames. Maybe you got lucky and some ethernet drivers
> >> default to accepting larger frames even if the MTU is 1500.
> >>
> >>
> >> -a
> >
> >
> > 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 bootet. That is
> > annoying. Lucckily, I can provide better informations since the box s now attached to
> > the network. Here we go:
> >
>
> I have a similar situation with my nick on a tower system.
>
> 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.
>
> I'm using a small startup script which actually does this:
>
> start_cmd="ifconfig ${refix_if} tso"
>
>
> > LAN:
> > re0@pci0:4:0:0: class=0x020000 card=0x502817aa chip=0x816810ec rev=0x10 hdr=0x00
> > vendor = 'Realtek Semiconductor Co., Ltd.'
> > device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
> > class = network
> > subclass = ethernet
> > bar [10] = type I/O Port, range 32, base 0x3000, size 256, enabled
> > bar [18] = type Memory, range 64, base 0xf1d04000, size 4096, enabled
> > bar [20] = type Memory, range 64, base 0xf1d00000, size 16384, enabled
> > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0
> > cap 05[50] = MSI supports 1 message, 64 bit
> > cap 10[70] = 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] = MSI-X supports 4 messages, enabled
> > Table in map 0x20[0x0], PBA in map 0x20[0x800]
> > cap 03[d0] = VPD
> > ecap 0001[100] = AER 2 0 fatal 0 non-fatal 1 corrected
> > ecap 0002[140] = VC 1 max VC0
> > ecap 0003[160] = Serial 1 01000000684ce000
> > ecap 0018[170] = LTR 1
> > ecap 001e[178] = unknown 1
> > PCI-e errors = Correctable Error Detected
> > Corrected = Receiver Error
> >
>
> re0@pci0:3:0:0: class=0x020000 card=0x11c01734 chip=0x816810ec rev=0x07
> hdr=0x00
> vendor = 'Realtek Semiconductor Co., Ltd.'
> device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
> class = network
> subclass = ethernet
> bar [10] = type I/O Port, range 32, base 0xd000, size 256, enabled
> bar [18] = type Prefetchable Memory, range 64, base 0xf2104000,
> size 4096, enabled
> bar [20] = type Prefetchable Memory, range 64, base 0xf2100000,
> size 16384, enabled
> cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0
> cap 05[50] = MSI supports 1 message, 64 bit
> cap 10[70] = 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] = MSI-X supports 4 messages, enabled
> Table in map 0x20[0x0], PBA in map 0x20[0x800]
> cap 03[d0] = VPD
> ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected
> ecap 0002[140] = VC 1 max VC0
> ecap 0003[160] = Serial 1 0100000004000001
> PCI-e errors = Correctable Error Detected
> Unsupported Request Detected
> Corrected = Advisory Non-Fatal Error
>
> it's similar hardware, same chip, different revision. I already reported
> this on net@ but no patch could really solve the issue.
>
Hello.
Well, it seems the same here with taht specific NIC. Changing ANYTHING, even already
enabled features, or bringing the NIC down and then up seem to solve this problem.
I guess, I file a PR to make this issue memorized.
Regards,
Oliver
[-- Attachment #2 --]
-----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-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140918104833.3a473d7e.ohartman>