Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Sep 2006 12:52:36 +0200
From:      "Ulrich Spoerlein" <uspoerlein@gmail.com>
To:        "Martin Nilsson" <martin@gneto.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2
Message-ID:  <7ad7ddd90609270352i450d2345va1b10513c5978bce@mail.gmail.com>
In-Reply-To: <451A1375.5080202@gneto.com>
References:  <451A1375.5080202@gneto.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 9/27/06, Martin Nilsson <martin@gneto.com> wrote:
>
> mailbox# uname -a
> FreeBSD mailbox 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Fri Sep 22
> 00:31:29 CEST 2006
> root@mailbox:/usr/obj-local/usr/src/sys/SMP  amd64
>
> I get tons of these:
> em0: watchdog timeout -- resetting
> em0: link state changed to DOWN
> em0: link state changed to UP
>
> mailbox# pciconf -lv
> em0@pci13:0:0:  class=0x020000 card=0x108c15d9 chip=0x108c8086 rev=0x03
> hdr=0x00
>      vendor   = 'Intel Corporation'
>      device   = 'PRO/1000 PM'
>      class    = network
>      subclass = ethernet
> em1@pci14:0:0:  class=0x020000 card=0x109a15d9 chip=0x109a8086 rev=0x00
> hdr=0x00
>      vendor   = 'Intel Corporation'
>      class    = network
>      subclass = ethernet
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>          options=b<RXCSUM,TXCSUM,VLAN_MTU>
>          inet6 fe80::230:48ff:fe89:c958%em0 prefixlen 64 scopeid 0x1
>          inet 192.168.10.2 netmask 0xffffff00 broadcast 192.168.10.255
>          ether 00:30:48:89:c9:58
>          media: Ethernet autoselect (1000baseTX <full-duplex>)
>          status: active


We have several SMP systems with onboard em0/em1 Interfaces running on a
RELENG_6 snapshot taken at 2006-09-20 00:00+0. They are not in production
yet, so the load is not that much. However I haven't seen any watchdog
timeouts on them. Only annoyance is, that the em(4) interfaces take too long
for the interface to come up, ie, the system will boot, run ifconfig, the
interface still has no link so syslogd/ntpdate/ntpd will complain about 'no
route to host'. A 'sleep 5' fixes that problem, though I'd like to avoid
such hacks.

Anyway, here's the data:

em0@pci3:2:0:   class=0x020000 card=0x117a8086 chip=0x10798086 rev=0x03
hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82546EB Dual Port Gigabit Ethernet Controller'
    class    = network
    subclass = ethernet
em1@pci3:2:1:   class=0x020000 card=0x117a8086 chip=0x10798086 rev=0x03
hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82546EB Dual Port Gigabit Ethernet Controller'
    class    = network
    subclass = ethernet

em0: <Intel(R) PRO/1000 Network Connection Version - 6.1.4> port
0x3040-0x307f mem 0xd8320000-0xd833ffff irq 54 at device 2.0 on pci3
em0: Ethernet address: XXXXXXXXXX
em0: [FAST]
em1: <Intel(R) PRO/1000 Network Connection Version - 6.1.4> port
0x3080-0x30bf mem 0xd8340000-0xd835ffff irq 55 at device 2.1 on pci3
em1: Ethernet address: XXXXXXXXXX
em1: [FAST]
em0: link state changed to UP

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet 1.2.3.4 netmask 0xffffff00 broadcast 1.2.3.4
        ether XXXXXXXXX
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

Hope this helps to narrow down the problem.
Uli



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7ad7ddd90609270352i450d2345va1b10513c5978bce>