From owner-freebsd-current@freebsd.org  Tue Sep  8 16:22:20 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA1F99CC4DB
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Tue,  8 Sep 2015 16:22:20 +0000 (UTC)
 (envelope-from sbruno@freebsd.org)
Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CE2A01DB0
 for <freebsd-current@freebsd.org>; Tue,  8 Sep 2015 16:22:20 +0000 (UTC)
 (envelope-from sbruno@freebsd.org)
Received: from [192.168.100.102] (unknown [50.136.155.142])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 (Authenticated sender: sbruno@ignoranthack.me)
 by mail.ignoranthack.me (Postfix) with ESMTPSA id 36482193A36;
 Tue,  8 Sep 2015 16:22:18 +0000 (UTC)
Subject: Re: em broken on current amd64
To: Mark R V Murray <mark@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>
Cc: freebsd-current@freebsd.org
From: Sean Bruno <sbruno@freebsd.org>
Message-ID: <55EF0B39.30507@freebsd.org>
Date: Tue, 8 Sep 2015 09:22:17 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <A9598479-1AA1-4FDB-82BC-9918B647B49F@grondar.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Sep 2015 16:22:21 -0000


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