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: Thu, 21 Jun 2007 17:53:25 -0600 [thread overview]
Message-ID: <467B0F75.5020900@shaw.ca> (raw)
In-Reply-To: <fa.GUDTRJ+yqLKq4z8Xd89auM7cYdk@ifi.uio.no>
Fortier,Vincent [Montreal] wrote:
> Here is part of the dmesg:
> [root@localhost /root]# dmesg | grep -i eth
> [ 119.196375] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2
> v1.5.8.1 (May 7, 2007)
> [ 119.215023] eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X
> 64-bit 133MHz found at mem f8000000, IRQ 17, node addr 0019b9c8eedc
> [ 119.246853] eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X
> 64-bit 133MHz found at mem f4000000, IRQ 16, node addr 0019b9c8eede
> [ 119.458598] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network
> Connection
> [ 119.654095] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network
> Connection
> [ 266.513144] bnx2: eth3: using MSI
> [ 269.638237] bnx2: eth3 NIC Link is Up, 1000 Mbps full duplex, receive
> & transmit flow control ON
> [ 290.242533] eth3: no IPv6 routers present
>
> As you can notice it tried to use eth0 & eth1 for both broadcom adapters
> but it did not worked properly since e1000 used them instead and finally
> bnx2 got eth3 working using MSI ?
Huh? eth0 and eth1 are the e1000 adapters, eth3 (and presumably eth2)
are the bnx2 adapters..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-06-21 23:54 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 ` Robert Hancock [this message]
2007-06-22 19:20 ` Broadcom (bnx2) on PE1950/2950 failure Fortier,Vincent [Montreal]
2007-06-22 22:56 ` Robert Hancock
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=467B0F75.5020900@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.