Date: Tue, 8 Sep 2015 06:31:04 +0200 From: olli hauer <ohauer@gmx.de> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: em broken on current amd64 Message-ID: <55EE6488.3020509@gmx.de> 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
On 2015-09-07 23: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.
>
Not sure if this is a current issue.
Some days ago I build a 10.2 system with an on-board em0 to test my new assigned IPv6 (only) connectivity and seeing similar symptoms.
Haven't measured the time but the system stops forwarding packages on the em0 until I bring it down and up again (sometime additional restart pf)
# uname
FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
# ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether f8:b1:56:d7:a9:c4
inet6 fe80::fab1:56ff:fed7:a9c4%em0 prefixlen 64 scopeid 0x1
inet6 2001:9xx:1xxx::2 prefixlen 64
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
# dmesg | grep em0
em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xf040-0xf05f mem 0xfb300000-0xfb31ffff,0xfb328000-0xfb328fff irq 20 at device 25.0 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: f8:b1:56:d7:a9:c4
ahciem0: <AHCI enclosure management bridge> on ahci0
ses0 at ahciem0 bus 0 scbus1 target 0 lun 0
--
olli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55EE6488.3020509>