Date: Thu, 28 Apr 2011 14:31:12 -0700 From: Jack Vogel <jfvogel@gmail.com> To: Wiktor Niesiobedzki <bsd@vink.pl> Cc: freebsd-stable@freebsd.org Subject: Re: No data received with Intel Corporation Gigabit CT Desktop Adapter (82574L) Message-ID: <BANLkTikUdbND-0qWL-u9x3yd==SR5MBxbQ@mail.gmail.com> In-Reply-To: <BANLkTinSHNK6hkg_LU0K8BPqKqCf8wwipg@mail.gmail.com> References: <BANLkTim-ve2_du3JoZ7NmLLv4OU%2Bk9F-eQ@mail.gmail.com> <BANLkTi=t87a-L3WJY%2Be1G6Jy-w4PhgQz-Q@mail.gmail.com> <BANLkTinSHNK6hkg_LU0K8BPqKqCf8wwipg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, rebuild your kernel so the driver is not static, then you can load an= d unload the driver to see what happens. You only have one interface, no em1? Jack On Thu, Apr 28, 2011 at 2:17 PM, Wiktor Niesiobedzki <bsd@vink.pl> wrote: > Hi, > > I really don't know (I haven't done that intentionally). There is > nothing special in /var/log/messages: > kadlubek# grep -i msix /var/log/messages > Apr 28 21:37:03 kadlubek kernel: em0: Using MSIX interrupts with 0 vector= s > > Though sysctl suggests, that I haven't disabled MSIX: > kadlubek# sysctl -a | grep -i msix > hw.pci.enable_msix: 1 > > I've checked further pciconf output (now with -c option also) and there i= s: > em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 rev= =3D0x00 > hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' > class =3D network > subclass =3D ethernet > cap 01[c8] =3D powerspec 2 supports D0 D3 current D0 > cap 05[d0] =3D MSI supports 1 message, 64 bit > cap 10[e0] =3D PCI-Express 1 endpoint max data 128(256) link x1(x1) > cap 11[a0] =3D MSI-X supports 5 messages in map 0x1c enabled > > So it looks, like the card supports MSI-X and has them enabled. > > Though my PCI Express bridges report as: > pcib2@pci0:0:2:0: class=3D0x060400 card=3D0xc3231106 chip=3D0xa3641= 106 > rev=3D0x80 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'P4M900 PCI to PCI Bridge Controller' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x1(x1) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[98] =3D PCI Bridge card=3D0xc3231106 > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] =3D VC 1 max VC1 > ecap 0005[180] =3D unknown 1 > pcib3@pci0:0:3:0: class=3D0x060400 card=3D0xc3231106 chip=3D0xc3641= 106 > rev=3D0x80 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'P4M900 PCI to PCI Bridge Controller' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x1(x1) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[98] =3D PCI Bridge card=3D0xc3231106 > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] =3D VC 1 max VC1 > ecap 0005[180] =3D unknown 1 > > pcib5@pci0:128:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x287c1= 106 > rev=3D0x00 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'VT8251 Standard PCIe Root Port' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x0(x2) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit, vector masks > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[90] =3D PCI Bridge card=3D0x00000000 > ecap 0001[100] =3D AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0002[140] =3D VC 1 max VC1 > ecap 0005[180] =3D unknown 1 > pcib6@pci0:128:0:1: class=3D0x060400 card=3D0x00000004 chip=3D0x287d1= 106 > rev=3D0x00 hdr=3D0x01 > vendor =3D 'VIA Technologies, Inc.' > device =3D 'VT8251 Standard PCIe Root Port' > class =3D bridge > subclass =3D PCI-PCI > cap 10[40] =3D PCI-Express 1 root port max data 128(256) link x0(x1) > cap 01[68] =3D powerspec 2 supports D0 D3 current D0 > cap 05[70] =3D MSI supports 1 message, 64 bit, vector masks > cap 08[88] =3D HT MSI fixed address window disabled at 0xfee00000 > cap 0d[90] =3D PCI Bridge card=3D0x00000004 > > Though they mention that HT MSI windows is disabled. I'm not sure, > whether this matters. > > Cheers, > > Wiktor > > 2011/4/28 Jack Vogel <jfvogel@gmail.com>: > > Notice this: em0: Using MSIX interrupts with 0 vectors > > > > ZERO vectors are not a good sign :) You need to look at your system, yo= u > > have MSIX > > disabled or something? Maybe some message in /var/log/messages?? > > > > Jack > > > > > > On Thu, Apr 28, 2011 at 1:20 PM, Wiktor Niesiobedzki <bsd@vink.pl> > wrote: > >> > >> Hi, > >> > >> I've installed Intel Gigabit CT Desktop Adapter in my FreeBSD 8.2 box > >> and I can't see any incoming traffic on this card. Even ARP resolution > >> doesn't work. Though I see the outgoing traffic on the other end. > >> > >> Relevant info: > >> kadlubek# uname -a > >> FreeBSD kadlubek 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #20: Sat Feb 12 > >> 21:22:19 CET 2011 root@kadlubek:/usr/obj/usr/src/sys/KADLUB i386 > >> > >> kadlubek# dmesg | grep em0 > >> em0: <Intel(R) PRO/1000 Network Connection 7.1.9> port 0xdc00-0xdc1f > >> mem 0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff > >> irq 24 at device 0.0 on pci2 > >> em0: Using MSIX interrupts with 0 vectors > >> em0: [FILTER] > >> > >> kadlubek# ping 192.168.115.1 > >> PING 192.168.115.1 (192.168.115.1): 56 data bytes > >> ping: sendto: Host is down > >> ping: sendto: Host is down > >> > >> In mean time - tcpdump shows: > >> kadlubek# tcpdump -i em0 > >> 22:03:55.962118 ARP, Request who-has 192.168.115.1 tell > >> 192.168.115.220, length 28 > >> 22:03:56.967107 ARP, Request who-has 192.168.115.1 tell > >> 192.168.115.220, length 28 > >> 22:03:57.972094 ARP, Request who-has 192.168.115.1 tell > >> 192.168.115.220, length 28 > >> > >> I've checked the firewall rules, but there are none there: > >> kadlubek# pfctl -s rules > >> No ALTQ support in kernel > >> ALTQ related functions disabled > >> > >> pciconf -lv shows the card as: > >> em0@pci0:2:0:0: class=3D0x020000 card=3D0xa01f8086 chip=3D0x10d38086 r= ev=3D0x00 > >> hdr=3D0x00 > >> vendor =3D 'Intel Corporation' > >> device =3D 'Intel 82574L Gigabit Ethernet Controller (82574L)' > >> class =3D network > >> subclass =3D ethernet > >> > >> > >> kadlubek# sysctl dev.em.0 > >> dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.1.9 > >> dev.em.0.%driver: em > >> dev.em.0.%location: slot=3D0 function=3D0 handle=3D\_SB_.PCI0.NBPG.NPG= S > >> dev.em.0.%pnpinfo: vendor=3D0x8086 device=3D0x10d3 subvendor=3D0x8086 > >> subdevice=3D0xa01f class=3D0x020000 > >> dev.em.0.%parent: pci2 > >> dev.em.0.nvm: -1 > >> dev.em.0.debug: -1 > >> dev.em.0.rx_int_delay: 0 > >> dev.em.0.tx_int_delay: 66 > >> dev.em.0.rx_abs_int_delay: 66 > >> dev.em.0.tx_abs_int_delay: 66 > >> dev.em.0.rx_processing_limit: 100 > >> dev.em.0.flow_control: 3 > >> dev.em.0.link_irq: 0 > >> dev.em.0.mbuf_alloc_fail: 0 > >> dev.em.0.cluster_alloc_fail: 0 > >> dev.em.0.dropped: 0 > >> dev.em.0.tx_dma_fail: 0 > >> dev.em.0.rx_overruns: 0 > >> dev.em.0.watchdog_timeouts: 0 > >> dev.em.0.device_control: 1477444168 > >> dev.em.0.rx_control: 67141634 > >> dev.em.0.fc_high_water: 18432 > >> dev.em.0.fc_low_water: 16932 > >> dev.em.0.queue0.txd_head: 35 > >> dev.em.0.queue0.txd_tail: 35 > >> dev.em.0.queue0.tx_irq: 0 > >> dev.em.0.queue0.no_desc_avail: 0 > >> dev.em.0.queue0.rxd_head: 117 > >> dev.em.0.queue0.rxd_tail: 1023 > >> dev.em.0.queue0.rx_irq: 0 > >> dev.em.0.mac_stats.excess_coll: 0 > >> dev.em.0.mac_stats.single_coll: 0 > >> dev.em.0.mac_stats.multiple_coll: 0 > >> dev.em.0.mac_stats.late_coll: 0 > >> dev.em.0.mac_stats.collision_count: 0 > >> dev.em.0.mac_stats.symbol_errors: 0 > >> dev.em.0.mac_stats.sequence_errors: 0 > >> dev.em.0.mac_stats.defer_count: 0 > >> dev.em.0.mac_stats.missed_packets: 0 > >> dev.em.0.mac_stats.recv_no_buff: 0 > >> dev.em.0.mac_stats.recv_undersize: 0 > >> dev.em.0.mac_stats.recv_fragmented: 0 > >> dev.em.0.mac_stats.recv_oversize: 0 > >> dev.em.0.mac_stats.recv_jabber: 0 > >> dev.em.0.mac_stats.recv_errs: 0 > >> dev.em.0.mac_stats.crc_errs: 0 > >> dev.em.0.mac_stats.alignment_errs: 0 > >> dev.em.0.mac_stats.coll_ext_errs: 0 > >> dev.em.0.mac_stats.xon_recvd: 0 > >> dev.em.0.mac_stats.xon_txd: 0 > >> dev.em.0.mac_stats.xoff_recvd: 0 > >> dev.em.0.mac_stats.xoff_txd: 0 > >> dev.em.0.mac_stats.total_pkts_recvd: 117 > >> dev.em.0.mac_stats.good_pkts_recvd: 117 > >> dev.em.0.mac_stats.bcast_pkts_recvd: 41 > >> dev.em.0.mac_stats.mcast_pkts_recvd: 42 > >> dev.em.0.mac_stats.rx_frames_64: 71 > >> dev.em.0.mac_stats.rx_frames_65_127: 0 > >> dev.em.0.mac_stats.rx_frames_128_255: 35 > >> dev.em.0.mac_stats.rx_frames_256_511: 11 > >> dev.em.0.mac_stats.rx_frames_512_1023: 0 > >> dev.em.0.mac_stats.rx_frames_1024_1522: 0 > >> dev.em.0.mac_stats.good_octets_recvd: 15499 > >> dev.em.0.mac_stats.good_octets_txd: 2240 > >> dev.em.0.mac_stats.total_pkts_txd: 35 > >> dev.em.0.mac_stats.good_pkts_txd: 35 > >> dev.em.0.mac_stats.bcast_pkts_txd: 35 > >> dev.em.0.mac_stats.mcast_pkts_txd: 0 > >> dev.em.0.mac_stats.tx_frames_64: 35 > >> dev.em.0.mac_stats.tx_frames_65_127: 0 > >> dev.em.0.mac_stats.tx_frames_128_255: 0 > >> dev.em.0.mac_stats.tx_frames_256_511: 0 > >> dev.em.0.mac_stats.tx_frames_512_1023: 0 > >> dev.em.0.mac_stats.tx_frames_1024_1522: 0 > >> dev.em.0.mac_stats.tso_txd: 0 > >> dev.em.0.mac_stats.tso_ctx_fail: 0 > >> dev.em.0.interrupts.asserts: 2 > >> dev.em.0.interrupts.rx_pkt_timer: 0 > >> dev.em.0.interrupts.rx_abs_timer: 0 > >> dev.em.0.interrupts.tx_pkt_timer: 0 > >> dev.em.0.interrupts.tx_abs_timer: 0 > >> dev.em.0.interrupts.tx_queue_empty: 0 > >> dev.em.0.interrupts.tx_queue_min_thresh: 0 > >> dev.em.0.interrupts.rx_desc_min_thresh: 0 > >> dev.em.0.interrupts.rx_overrun: 0 > >> dev.em.0.wake: 0 > >> > >> kadlubek# sysctl dev.em.0.debug=3D1 > >> Interface is RUNNING and INACTIVE > >> em0: hw tdh =3D 35, hw tdt =3D 35 > >> em0: hw rdh =3D 118, hw rdt =3D 1023 > >> em0: Tx Queue Status =3D 1 > >> em0: TX descriptors avail =3D 989 > >> em0: Tx Descriptors avail failure =3D 0 > >> em0: RX discarded packets =3D 0 > >> em0: RX Next to Check =3D 0 > >> em0: RX Next to Refresh =3D 0 > >> > >> > >> I've tried booting linux on this box, and card is detected as follows: > >> [ 16.376557] e1000e: Intel(R) PRO/1000 Network Driver - 1.2.20-k2 > >> [ 16.376650] e1000e: Copyright(c) 1999 - 2011 Intel Corporation. > >> [ 16.376949] e1000e 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -= > > >> IRQ 24 > >> [ 16.377034] e1000e 0000:02:00.0: PCI: Disallowing DAC for device > >> [ 16.377152] e1000e 0000:02:00.0: setting latency timer to 64 > >> [ 16.377387] e1000e 0000:02:00.0: (unregistered net_device): Failed > >> to initialize MSI-X interrupts. Falling back to MSI interrupts. > >> [ 16.377511] e1000e 0000:02:00.0: (unregistered net_device): Failed > >> to initialize MSI interrupts. Falling back to legacy interrupts. > >> [ 16.377783] e1000e 0000:02:00.0: Disabling ASPM L0s > >> [ 16.505464] e1000e 0000:02:00.0: eth2: (PCI Express:2.5GB/s:Width > >> x1) 00:1b:21:9d:52:1b > >> [ 16.505571] e1000e 0000:02:00.0: eth2: Intel(R) PRO/1000 Network > >> Connection > >> [ 16.505668] e1000e 0000:02:00.0: eth2: MAC: 3, PHY: 8, PBA No: > >> E46981-005 > >> [ 85.821142] e1000e: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow > >> Control: Rx/Tx > >> [ 85.821162] e1000e 0000:02:00.0: eth2: 10/100 speed: disabling TSO > >> > >> > >> And works without a problem. > >> > >> I see, that 8-stable has 7.1.9 version of the driver, and current has > >> 7.2.2. Are there any patches for stable to update the driver to > >> version 7.2.2, so I can check, if this can help? Or maybe anyone has a > >> clue, how to make this card function in FreeBSD? > >> > >> Cheers, > >> > >> Wiktor Niesiob=EAdzki > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to " > freebsd-stable-unsubscribe@freebsd.org" > > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikUdbND-0qWL-u9x3yd==SR5MBxbQ>