Date: Sat, 12 Sep 2015 21:45:04 +0100 From: Mark R V Murray <markm@FreeBSD.org> To: Mark Robert Vaughan Murray <markm@FreeBSD.org> Cc: Sean Bruno <sbruno@freebsd.org>, freebsd-current@freebsd.org Subject: Re: em broken on current amd64 Message-ID: <2B045997-23A9-4B83-B34B-B9E4C06EF2C5@FreeBSD.org> In-Reply-To: <5CEDDA5F-7858-4A7D-BB45-CB902F53A83B@FreeBSD.org> References: <1B3BC636-6765-4478-AAE0-122E6904276E@pozo.com> <70759B1C-6685-4EF9-BC65-52590ABD398E@gmail.com> <63EACBE5-F82A-47D9-BA9A-E95D0E6AE80D@FreeBSD.org> <55EE2153.1050704@freebsd.org> <A9598479-1AA1-4FDB-82BC-9918B647B49F@grondar.org> <55EF0B39.30507@freebsd.org> <5CEDDA5F-7858-4A7D-BB45-CB902F53A83B@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 8 Sep 2015, at 19:02, Mark R V Murray <markm@FreeBSD.org> wrote: >=20 >=20 >> On 8 Sep 2015, at 17:22, Sean Bruno <sbruno@freebsd.org> wrote: >>=20 >>=20 >>>>>=20 >>>>> I=E2=80=99m also seeing breakage with the em0 device; this isn=E2=80= =99t a kernel >>>>> hang, it is a failure to move data after about 10-15 minutes. The >>>>> symptom is that my WAN ethernet no longer moves traffic, no pings, >>>>> nothing. Booting looks normal: >>>>>=20 >>>>> em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port >>>>> 0x30c0-0x30df mem 0x50300000-0x5031ffff,0x50324000-0x50324fff irq >>>>> 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: = Ethernet >>>>> address: 00:16:76:d3:e1:5b em0: netmap queues/slots: TX 1/1024, RX >>>>> 1/1024 >>>>>=20 >>>>> Fixing it is as easy as =E2=80=A6 >>>>>=20 >>>>> # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up >>>>>=20 >>>>> :-) >>>>>=20 >>>>> I=E2=80=99m running CURRENT, r287538. This last worked of me a = month or so >>>>> ago at my previous build. >>>>>=20 >>>>> M >>>>>=20 >>>>=20 >>>>=20 >>>> Just so I'm clear, the original problem reported was a failure to >>>> attach (you were among several folks reporting breakage). Is that = fixed >>>> ? >>>=20 >>> I did not report the failure to attach, and I am not seeing it as I = don=E2=80=99t >>> think I built a kernel that had that particular failure. I am having = the >>> =E2=80=9Cfailure after 10-15 minutes=E2=80=9D problem; this is on an = em0 device. >>>=20 >>> M >>>=20 >>=20 >>=20 >> Hrm, that's odd. That sounds like a hole where interrupts aren't = being >> reset for "reasons" that I cannot fathom. >>=20 >> What hardware (pciconf -lv) does your system actually have? The = em(4) >> driver doesn't identify components which is frustrating. >=20 > pciconf -lv output below: >=20 > hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x514d8086 = chip=3D0x29a08086 rev=3D0x02 hdr=3D0x00 > vendor =3D 'Intel Corporation' > device =3D '82P965/G965 Memory Controller Hub' > class =3D bridge > subclass =3D HOST-PCI I just caught this, on today=E2=80=99s build: em0: Watchdog timeout Queue[0]-- resetting Interface is RUNNING and ACTIVE em0: TX Queue 0 ------ em0: hw tdh =3D 127, hw tdt =3D 139 em0: Tx Queue Status =3D -2147483648 em0: TX descriptors avail =3D 1012 em0: Tx Descriptors avail failure =3D 0 em0: RX Queue 0 ------ em0: hw rdh =3D 0, hw rdt =3D 1023 em0: RX discarded packets =3D 0 em0: RX Next to Check =3D 0 em0: RX Next to Refresh =3D 1023 [graveyard] /usr/ports 09:42 pm # uname -a FreeBSD graveyard.grondar.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 = r287705: Sat Sep 12 15:07:54 BST 2015 = root@graveyard.grondar.org:/b/obj/usr/src/sys/G_AMD64_GATE amd64 M --=20 Mark R V Murray
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2B045997-23A9-4B83-B34B-B9E4C06EF2C5>