Re: em(4) stops forwarding

Michal Mertl wrote:

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.


The problem is that the drivers that are sharing the interrupt,
particularly the USB ones, can spend a very very long time waiting on
locks to service the interrupt. During that time, the interrupt pin is
masked and the all interrupts from all shared devices don't get
delivered. So even though the if_em driver has a very fast interrupt
handler, it still has to wait on the USB drivers. During that wait, a
burst of network traffic might come into the card, filling its buffers
and triggering an overflow. This would be especially likely to happen
while the kernel is flushing out filesystem i/o. In theory the
interrupt service latency shouldn't be any different whether the if_em
driver is fast or not, but there might be coincidental timing issues
that I don't understand. That's why I'd like you to set the #ifdef in
the driver to revert it back to it's classic behaviour and see if the
problem persists. If it doesn't, then I'll have to rethink some of the
changes that I made to it.

Scott


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


_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: USB Mass Storage Device
    ... chanses are your usb function ... controller driver isn't working properly (If my memory serves me right ... The card has to be inserted before. ...
    (microsoft.public.windowsce.platbuilder)
  • USB Interrupt pipe time out problem
    ... We experience a mind boggling problem during development of a USB ... passing data at 200 Hz over an interrupt pipe. ... Capturing the data is done through a thread in a stream driver ...
    (microsoft.public.windowsce.platbuilder)
  • Re: aAttention MSVPs. USB 2.0 Drivers not recognised - XP is defective !
    ... my USB setup is as follows: ... OpenHCI Controller ... but nothing has changed either thru the PCI Card or the mobo. ... The O/S will still not update the Mass Storage device to a different driver. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: freeze problem on normal boot
    ... You have to look at the PMQ import log to see if the driver for the card is ... It turns out that if I remove the graphics card sitting in the PCI-Express ... Re the USB mouse, I added in the MS USB Intellimouse coponent (maybe it ... "Sean Liming " wrote: ...
    (microsoft.public.windowsxp.embedded)
  • Re: USB mass storage issue
    ... driver is primarilly designed for use with non-removable storage (such ... So If you are replacing the SD/MMC card then ... USB host driver configures and searches for the device during the boot ...
    (microsoft.public.windowsce.platbuilder)