Date: Sun, 8 Apr 2012 08:09:38 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Jason Wolfe <nitroboost@gmail.com> Cc: jfv@freebsd.org, jhb@freebsd.org, net@freebsd.org Subject: Re: 82574L hangs (with r233708 e1000 driver). Message-ID: <20120408050938.GZ2358@deviant.kiev.zoral.com.ua> In-Reply-To: <CAAAm0r2t5aKctSA7_1KLagm8_FtSZ%2BZKKV_1n9H-sfo=ndCQrA@mail.gmail.com> References: <20120407133715.GU2358@deviant.kiev.zoral.com.ua> <CAAAm0r2t5aKctSA7_1KLagm8_FtSZ%2BZKKV_1n9H-sfo=ndCQrA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--f9wPAG0p55LdzBq3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 07, 2012 at 03:06:38PM -0700, Jason Wolfe wrote: > 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=3D0x020000 card=3D0x20128086 chip=3D0x10d38086 re= v=3D0x00 hdr=3D0x00 > > 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 me= m 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=3D1 > > dev.em.0.debug: Interface is RUNNING and ACTIVE > > em0: hw tdh =3D 357, hw tdt =3D 357 > > em0: hw rdh =3D 323, hw rdt =3D 273 > > em0: Tx Queue Status =3D 0 > > em0: TX descriptors avail =3D 1024 > > em0: Tx Descriptors avail failure =3D 0 > > em0: RX discarded packets =3D 0 > > em0: RX Next to Check =3D 274 > > em0: RX Next to Refresh =3D 273 > > > > [..snip..] > > Any help ? >=20 > Konstantin, >=20 > It doesn't appear to be the exact issue I was seeing, but here is a > patch that did resolve issues with my 82574L buffers filling and > requiring a down/up to recover. It was the result of the 'Intel > 82574L interface wedging - em7.3.2/8.2-STABLE' if you'd like to peruse > that. Yes, I (re)read the thread when I first encountered the issue. The r233708 that I specifically mentioned above should be the commit of the patch you have attached. Anyway, thank you for help. --f9wPAG0p55LdzBq3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk+BHZEACgkQC3+MBN1Mb4gUnwCgpy2G+VhstvuUutdqyat3FoIF 02gAoIILG75t4JqBQqZQuTDuoVI1kQFN =GJIm -----END PGP SIGNATURE----- --f9wPAG0p55LdzBq3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120408050938.GZ2358>