On Tue, Nov 23, 2010 at 03:16:57PM +0100, Toni Mueller wrote:
> Hi,
>
> On Thu, 18.11.2010 at 16:38:55 +0100, Manuel Guesdon
> <[email protected]> wrote:
> > Is there a way to get detailed em(4) device errors without having to
> > recompile kernel with EM_DEBUG ?
> > I try to find in-errors reason(s) but netstat only gives errors as a sum of
> > dropped_pkts + stats.rxerrc + stats.crcerrs + sc->stats.algnerrc +... as far
> > as I can see :-(
>
> I'm having a similar problem. On one 4x em(4) machine, I get a lot of
> input errors and, much more serious, intermittend packet loss, but only
> on one interface out of two with similar traffic levels (~1-4kpps per
> direction).
>
> After reading the latest em(4) threads, I also found this very strange
> thing, which must have been automatically configured:
>
> # ifconfig em3
> em3:
> flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
> lladdr 00:30:48:94:0b:21
> priority: 0
> media: Ethernet autoselect (1000baseT full-duplex,master)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> status: active
>
>
> I'm unsure about how to remove this feature from this (physical)
> interface, and the machine uses none of carp, pfsync or sasync.
> The hardware for this interface is
I would rather investigate why the PROMISC and ALLMULTI flags are set
on this interface.
-Otto
>
> em3 at pci5 dev 0 function 0 "Intel PRO/1000MT (82573L)" rev 0x00: apic 2 int
> 17 (irq 11), address 00:30:48:94:0b:21
>
> as detected by OpenBSD 4.8-stable (i386).
>
> The ability to selectively enable or disable debugging for individual
> devices at runtime would be a great feature, from a sysadmin's
> perspective.
>
>
> --
> Kind regards,
> --Toni++
