From: Robert Hancock <hancockr@shaw.ca>
To: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Broadcom (bnx2) on PE1950/2950 failure
Date: Fri, 22 Jun 2007 16:56:57 -0600 [thread overview]
Message-ID: <467C53B9.3030102@shaw.ca> (raw)
In-Reply-To: <F1D642E5A91BC94D9504EC83AE19E6B0128A40@ecqcmtlmail3.quebec.int.ec.gc.ca>
Fortier,Vincent [Montreal] wrote:
> Here is the output of the dmesg with now the appropriate order:
> [root@urpdev1 /etc]# dmesg | grep -i eth
> [ 120.685696] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2
> v1.5.8.1 (May 7, 2007)
> [ 120.703846] eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X
> 64-bit 133MHz found at mem f8000000, IRQ 17, node addr 0019b9c8eedc
> [ 120.735350] eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X
> 64-bit 133MHz found at mem f4000000, IRQ 16, node addr 0019b9c8eede
> [ 120.921403] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network
> Connection
> [ 121.069025] e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network
> Connection
> [ 267.720475] bnx2: eth0: using MSI
> [ 270.832235] bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex, receive
> & transmit flow control ON
>
>
> But still, there is a problem with the second Broadcom port (eth1):
> [root@urpdev1 /etc]# mii-tool
> eth0: negotiated 100baseTx-FD flow-control, link ok
> SIOCGMIIPHY on 'eth1' failed: Resource temporarily unavailable
> eth2: negotiated 100baseTx-FD flow-control, link ok
> eth3: negotiated 100baseTx-FD flow-control, link ok
>
> I don't get it?
>
> Help appreciated.
Is that interface down? mii-tool probably doesn't work in that case..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-06-22 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.GUDTRJ+yqLKq4z8Xd89auM7cYdk@ifi.uio.no>
2007-06-21 23:53 ` Broadcom (bnx2) on PE1950/2950 failure Robert Hancock
2007-06-22 19:20 ` Fortier,Vincent [Montreal]
2007-06-22 22:56 ` Robert Hancock [this message]
2007-06-21 17:26 Fortier,Vincent [Montreal]
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=467C53B9.3030102@shaw.ca \
--to=hancockr@shaw.ca \
--cc=Vincent.Fortier1@EC.GC.CA \
--cc=linux-kernel@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.