>>> 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
>> ?
> I did not report the failure to attach, and I am not seeing it as I don’t
> think I built a kernel that had that particular failure. I am having the
> “failure after 10-15 minutes” problem; this is on an em0 device.
> M

Hrm, that's odd.  That sounds like a hole where interrupts aren't being
reset for "reasons" that I cannot fathom.

What hardware (pciconf -lv) does your system actually have?  The em(4)
driver doesn't identify components which is frustrating.

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

Reply via email to