Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Sep 2015 09:22:17 -0700
From:      Sean Bruno <sbruno@freebsd.org>
To:        Mark R V Murray <mark@grondar.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: em broken on current amd64
Message-ID:  <55EF0B39.30507@freebsd.org>
In-Reply-To: <A9598479-1AA1-4FDB-82BC-9918B647B49F@grondar.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> <A9598479-1AA1-4FDB-82BC-9918B647B49F@grondar.org>

next in thread | previous in thread | raw e-mail | index | archive | help

>>>
>>> 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.

sean



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55EF0B39.30507>