From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 18:29:25 2006 Return-Path: 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 4AAF016A420 for ; Wed, 1 Feb 2006 18:29:25 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E409643D45 for ; Wed, 1 Feb 2006 18:29:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k11ITKka034282; Wed, 1 Feb 2006 11:29:21 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43E0FE09.50804@samsco.org> Date: Wed, 01 Feb 2006 11:29:29 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michal Mertl References: <1138813174.1358.34.camel@genius.i.cz> In-Reply-To: <1138813174.1358.34.camel@genius.i.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 18:29:25 -0000 Michal Mertl wrote: > 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: 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 > What is sharing the interrupt? Scott