Date: Sat, 7 Apr 2012 16:22:07 -0700 From: Jack Vogel <jfvogel@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: jfv@freebsd.org, jhb@freebsd.org, net@freebsd.org Subject: Re: 82574L hangs (with r233708 e1000 driver). Message-ID: <CAFOYbc=hFg_jvohPVQrp4M%2BXQztoO6b-9Pop=PrVn6VxP6oaHQ@mail.gmail.com> In-Reply-To: <20120407133715.GU2358@deviant.kiev.zoral.com.ua> References: <20120407133715.GU2358@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Make sure you have any firmware up to the latest available, if that doesn't help let me know and I'll check internally to see if there are any outstanding issues in shared code, that will be after the weekend. Jack On Sat, Apr 7, 2012 at 6:37 AM, Konstantin Belousov <kostikbel@gmail.com>wrote: > I bought Intel Atom motherboard DN2800MT, which has integrated if_em > LOM, reported by pciconf as > em0@pci0:1:0:0: class=0x020000 card=0x20128086 chip=0x10d38086 rev=0x00 > hdr=0x00 > 82574L Gigabit Network Connection > It seems that any non-trivial network activity on the interface causes > reliable interface hang, which can be temporary cured by ifconfig down/up. > This happens both with outdated stable/9 sys/dev/e1000 and with driver > from HEAD merged into stable/9. I currently use the copy of dev/e1000 > at rev. r233708. Disabling MSI-X makes the hand to occur slightly less > often. > > I can reproduce the hang in approximately a minute by scp'ing large > file from other machine to /dev/null on the DN2800MT. This makes the > board completely unusable for me. > > The driver reports itself as > em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x2000-0x201f mem > 0xc0400000-0xc041ffff,0xc0000000-0xc03fffff,0xc0420000-0xc0423fff irq 16 at > device 0.0 on pci1 > em0: attempting to allocate 3 MSI-X vectors (5 supported) > msi: routing MSI-X IRQ 258 to local APIC 0 vector 60 > msi: routing MSI-X IRQ 259 to local APIC 0 vector 61 > msi: routing MSI-X IRQ 260 to local APIC 0 vector 62 > em0: using IRQs 258-260 for MSI-X > em0: Using MSIX interrupts with 3 vectors > em0: bpf attached > em0: Ethernet address: 00:22:4d:7a:47:f6 > em0: Link is up 1000 Mbps Full Duplex > > The board is connected to ProCurve switch, there is no link flaps. > > When hang occur, dmesg output of # sysctl dev.em.0.debug=1 > dev.em.0.debug: Interface is RUNNING and ACTIVE > em0: hw tdh = 357, hw tdt = 357 > em0: hw rdh = 323, hw rdt = 273 > em0: Tx Queue Status = 0 > em0: TX descriptors avail = 1024 > em0: Tx Descriptors avail failure = 0 > em0: RX discarded packets = 0 > em0: RX Next to Check = 274 > em0: RX Next to Refresh = 273 > > and # sysctl dev.em.0 > dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.3.2 > dev.em.0.%driver: em > dev.em.0.%location: slot=0 function=0 handle=\_SB_.PCI0.RP01.PXSX > dev.em.0.%pnpinfo: vendor=0x8086 device=0x10d3 subvendor=0x8086 > subdevice=0x2012 class=0x020000 > dev.em.0.%parent: pci1 > dev.em.0.nvm: -1 > dev.em.0.debug: -1 > dev.em.0.fc: 3 > 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.eee_control: 0 > 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: 1074790984 > 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: 400 > dev.em.0.queue0.txd_tail: 400 > dev.em.0.queue0.tx_irq: 1835 > dev.em.0.queue0.no_desc_avail: 0 > dev.em.0.queue0.rxd_head: 331 > dev.em.0.queue0.rxd_tail: 273 > dev.em.0.queue0.rx_irq: 1392 > 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: 6475 > dev.em.0.mac_stats.good_pkts_recvd: 6475 > dev.em.0.mac_stats.bcast_pkts_recvd: 3 > dev.em.0.mac_stats.mcast_pkts_recvd: 1 > dev.em.0.mac_stats.rx_frames_64: 4 > dev.em.0.mac_stats.rx_frames_65_127: 220 > dev.em.0.mac_stats.rx_frames_128_255: 12 > dev.em.0.mac_stats.rx_frames_256_511: 17 > dev.em.0.mac_stats.rx_frames_512_1023: 907 > dev.em.0.mac_stats.rx_frames_1024_1522: 5315 > dev.em.0.mac_stats.good_octets_recvd: 8963959 > dev.em.0.mac_stats.good_octets_txd: 331463 > dev.em.0.mac_stats.total_pkts_txd: 4297 > dev.em.0.mac_stats.good_pkts_txd: 4297 > dev.em.0.mac_stats.bcast_pkts_txd: 4 > dev.em.0.mac_stats.mcast_pkts_txd: 0 > dev.em.0.mac_stats.tx_frames_64: 4 > dev.em.0.mac_stats.tx_frames_65_127: 4146 > dev.em.0.mac_stats.tx_frames_128_255: 122 > dev.em.0.mac_stats.tx_frames_256_511: 18 > dev.em.0.mac_stats.tx_frames_512_1023: 1 > dev.em.0.mac_stats.tx_frames_1024_1522: 6 > dev.em.0.mac_stats.tso_txd: 0 > dev.em.0.mac_stats.tso_ctx_fail: 0 > dev.em.0.interrupts.asserts: 3 > 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 > # > > Any help ? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFOYbc=hFg_jvohPVQrp4M%2BXQztoO6b-9Pop=PrVn6VxP6oaHQ>