Date: Mon, 7 Sep 2015 16:44:19 -0700 From: Sean Bruno <sbruno@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: em broken on current amd64 Message-ID: <55EE2153.1050704@freebsd.org> In-Reply-To: <63EACBE5-F82A-47D9-BA9A-E95D0E6AE80D@FreeBSD.org> References: <1B3BC636-6765-4478-AAE0-122E6904276E@pozo.com> <70759B1C-6685-4EF9-BC65-52590ABD398E@gmail.com> <63EACBE5-F82A-47D9-BA9A-E95D0E6AE80D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/07/15 14:10, Mark R V Murray wrote: > >> On 5 Sep 2015, at 17:11, Garrett Cooper <yaneurabeya@gmail.com> >> wrote: >> >> >>> On Sep 5, 2015, at 08:50, Manfred Antar <null@pozo.com> wrote: >>> >>> 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. >>> >>> boot messages: >>> >>> 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 >>> device_attach: em0 attach returned 5 >> >> Tijl said the same. The offending commit's r287467. Cheers, > > I’m also seeing breakage with the em0 device; this isn’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: > > 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 > > Fixing it is as easy as … > > # ifconfig em0 down ; service ipfw restart ; ifconfig em0 up > > :-) > > I’m running CURRENT, r287538. This last worked of me a month or so > ago at my previous build. > > M > Just so I'm clear, the original problem reported was a failure to attach (you were among several folks reporting breakage). Is that fixed ? sean -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJV7iFPXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kFn4H/Rsjq9GqgTHUZHvw4e7DkM8y nWftg4CM3RCMDnLPHxrFSXIUgq8a7jrtbEcft7YlA0ko56uqJs1SWgbXT2Ug4Mb7 0zNPR/Qy4ihGcwrfDew/JrSKGNG/T7BmNKFY7ANd90fcTeTf6qKIkhUj6bfj+m6/ OfAfQiegI9A5db7xbohhuG4RfXOx2yOz9ONkBpROuwBm7YvYk4hP4yIpGl+ANZ9V YtjhaEw2v7ehu8SpZ6Zg8XbbtfJ9k814WXxdx7FOcfiSeVPxTa4unwavzjhYWhy0 Z33DAyB8tsrzXfPMu9QZaU9XHUV1fROJ88B2MA0CvTnavhSjd+cCPVnTTnFX/bI= =A76q -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55EE2153.1050704>