Date: Thu, 02 Feb 2006 15:22:10 +0100 From: Michal Mertl <mime@traveller.cz> To: Scott Long <scottl@samsco.org> Cc: freebsd-current@freebsd.org Subject: Re: em(4) stops forwarding Message-ID: <1138890130.9192.3.camel@genius.i.cz> In-Reply-To: <43E203F9.9060307@samsco.org> References: <1138813174.1358.34.camel@genius.i.cz> <43E0FE09.50804@samsco.org> <1138875351.1807.12.camel@genius.i.cz> <43E203F9.9060307@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > Michal Mertl wrote: > > Scott Long wrote: > > > >>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: <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 > >>> > >> > >>What is sharing the interrupt? > > > > > > vgapci0, ipw0, ehci0, uhci0-2. I don't think vgapci0 and ipw0 are really > > using the interrupt when I use em0. > > > > > > Ouch. For now, edit /sys/dev/em/if_em.c and add the following line to > the top of the file: > > #define NO_EM_FASTINTR Do you know the reason of the problem? Wouldn't it be better if I used stock driver and got some information for you when it doesn't work? I use the machine as my workstation so it isn't such a big problem when it looses the network. > Also, does your kernel config include the apic device? Yes, it does. But I believe that the chipset doesn't have it and neither the CPU supports it. Michal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1138890130.9192.3.camel>