Date: Tue, 8 Sep 2015 08:26:00 +0100 From: Mark R V Murray <mark@grondar.org> To: Sean Bruno <sbruno@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: em broken on current amd64 Message-ID: <A9598479-1AA1-4FDB-82BC-9918B647B49F@grondar.org> In-Reply-To: <55EE2153.1050704@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>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 8 Sep 2015, at 00:44, Sean Bruno <sbruno@freebsd.org> wrote: >=20 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 >=20 >=20 > On 09/07/15 14:10, Mark R V Murray wrote: >>=20 >>> On 5 Sep 2015, at 17:11, Garrett Cooper <yaneurabeya@gmail.com> >>> wrote: >>>=20 >>>=20 >>>> On Sep 5, 2015, at 08:50, Manfred Antar <null@pozo.com> wrote: >>>>=20 >>>> Recent changes to em have broken current on amd64. Booting >>>> kernel will hang when trying to load em0, then will continue >>>> booting without the driver loading (No Network) This is on a HP >>>> SFF 8000 with em0 embedded on the motherboard. >>>>=20 >>>> boot messages: >>>>=20 >>>> em0: <Intel(R) PRO/1000 Network Connection 7.5.2> port >>>> 0x3100-0x311f mem 0xf3100000-0xf311ffff,0xf3125000-0xf3125fff >>>> irq 19 at device 25.0 on pci0 em0: attempting to allocate 1 MSI >>>> vectors (1 supported) em0: using IRQ 265 for MSI em0: Using an >>>> MSI interrupt em0: The EEPROM Checksum Is Not Valid=20 >>>> device_attach: em0 attach returned 5 >>>=20 >>> Tijl said the same. The offending commit's r287467. Cheers, >>=20 >> I=E2=80=99m also seeing breakage with the em0 device; this isn=E2=80=99= t 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 > ? 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. M --=20 Mark R V Murray
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A9598479-1AA1-4FDB-82BC-9918B647B49F>