From: Brian Haley <brian.haley@hp.com>
To: mchan@broadcom.com
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Broadcom 5708 taking a few seconds to get link-up
Date: Fri, 08 Feb 2008 14:29:37 -0500 [thread overview]
Message-ID: <47ACADA1.1090809@hp.com> (raw)
Hi Michael,
I'm working on a system that has two on-board 5708's. We've noticed
that it takes about 3 seconds for the link to come up - is this
considered normal? I've tried this with the latest davem tree with
similar results to older kernels/drivers.
# uname -r
2.6.24
# ethtool -i eth3
driver: bnx2
version: 1.7.3
firmware-version: 1.9.3
bus-info: 0000:42:00.0
# lspci -v
42:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
Gigabit Ethernet (rev 11)
Subsystem: Hewlett-Packard Company Unknown device 7038
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 34
Memory at fa000000 (64-bit, non-prefetchable) [size=32M]
Capabilities: [40] PCI-X non-bridge device
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
# ip link set eth3 up; mii-tool eth3; sleep 1; mii-tool eth3; sleep 1;
mii-tool eth3; sleep 1; mii-tool eth3
eth3: no link
eth3: no link
eth3: no link
eth3: negotiated 100baseTx-FD, link ok
Other drivers I've tried - e1000 and tg3, get up in < 1 second. I'm
asking becuase any packet I try to transmit out this interface before
link-up never gets out.
Thanks for any info,
-Brian
next reply other threads:[~2008-02-08 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 19:29 Brian Haley [this message]
2008-02-08 19:42 ` Broadcom 5708 taking a few seconds to get link-up Michael Chan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47ACADA1.1090809@hp.com \
--to=brian.haley@hp.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.