From owner-freebsd-current@FreeBSD.ORG  Wed Feb  1 16:59:41 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 139CA16A422
	for <freebsd-current@freebsd.org>; Wed,  1 Feb 2006 16:59:41 +0000 (GMT)
	(envelope-from mime@traveller.cz)
Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 84BB743D58
	for <freebsd-current@freebsd.org>; Wed,  1 Feb 2006 16:59:40 +0000 (GMT)
	(envelope-from mime@traveller.cz)
Received: from localhost.i.cz (ss.eunet.cz [193.85.228.13])
	by ss.eunet.cz (8.13.3/8.13.1) with ESMTP id k11GxcSv028787
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <freebsd-current@freebsd.org>; Wed, 1 Feb 2006 17:59:38 +0100 (CET)
	(envelope-from mime@traveller.cz)
From: Michal Mertl <mime@traveller.cz>
To: freebsd-current@freebsd.org
Content-Type: text/plain
Date: Wed, 01 Feb 2006 17:59:33 +0100
Message-Id: <1138813174.1358.34.camel@genius.i.cz>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Subject: em(4) stops forwarding
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2006 16:59:41 -0000

Hello,

I've been running CURRENT for long time and never experienced problem
with the built-in em(4) card before. Recently (I first noticed it on Jan
24) the card has stopped working several times. Nothing gets into the
log file. Carrier is still detected properly but no data is exchanged.
Ifconfig up/down doesn't help but kldunload/load does. When I run
tcpdump I don't see any packet coming in but I see some outgoing.

Can someone suggest what to look at when it happens the next time? I
have DDB compiled in. I will try to sniff the wire using another machine
next time to see if the card sends out anything.

The command 'pciconf -lv' says about the card this:
em0@pci2:1:0:   class=0x020000 card=0x05491014 chip=0x101e8086 rev=0x03
hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82540EP Gigabit Ethernet Controller (Mobile)'
    class    = network
    subclass = ethernet

The dmesg:
em0: <Intel(R) PRO/1000 Network Connection Version - 3.2.18> port
0x8000-0x803f mem 0xc0220000-0xc023ffff,0xc0200000-0xc020ffff irq 11 at
device 1.0 on pci2
em0: Ethernet address: 00:0d:60:cd:ae:e2
em0: [FAST]

The interrupt is shared since the machine is a notebook. I don't know if
it was just a coincidence but I think that it happened at the same time
as my USB mouse stopped working - the USB controller is on the same irq.

Michal