Am Thu, 18 Sep 2014 10:17:08 +0200 Guido Falsi <mad_at_madpilot.net> schrieb: > On 09/18/14 09:58, O. Hartmann wrote: > > Am Tue, 16 Sep 2014 08:40:25 -0700 > > Adrian Chadd <adrian_at_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_at_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_at_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_at_ 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
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:52 UTC