> On 5 Sep 2015, at 17:11, Garrett Cooper <yaneurab...@gmail.com> wrote:
>> On Sep 5, 2015, at 08:50, Manfred Antar <n...@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.

Mark R V Murray

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to