[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Sun Fire V210 NIC's don't work





On 15/11/2012 08:35, Michael Leicht wrote:
How about looking into OBP Config? Something like "test net" ?
I was going to suggest trying using "watch-net-all". It relies on there being traffic on the connected networks but can be useful. See
http://people.ee.ethz.ch/~ballisti/computer_topics/docs/U10svc/HTML/files/c0406.htm

More comments below...


I once had a similar Problem with a "hardcoded IP" (?) in OBP. Have you tried resseting your OBP and NVRAM?
My Blade 1500 silver shoudl have the same NIC and works just great, the missing Firmware Messages appeared but never had any Problem with them so i just ignored them.. ;)

Am 14.11.2012 um 19:38 schrieb Kaya Saman <kayasaman@gmail.com>:

On 11/14/2012 06:25 PM, Richard Mortimer wrote:
On 14/11/2012 17:58, Kaya Saman wrote:
On 11/14/2012 05:52 PM, Frans van Berckel wrote:
On Wed, 2012-11-14 at 17:14 +0000, Kaya Saman wrote:

...snip...

I can't ping anywhere from the eth1 interface :-(

In addition I tried eth2 as the server has 4 NICs... it doesn't even get
recognized by the system??

Can you provide a few more bits of information.

1 - output from "prtconf -pv"  That will give an OBP view of the system. I checked in DaveM's git tree and there isn't a sample from the v210 in there
https://git.kernel.org/?p=linux/kernel/git/davem/prtconfs.git;a=tree

It would be good to push a copy of that to DaveM if you are agreeable.

2 - output from "ifconfig -a"

3 - output from "lspci"

Regards

Richard

Hi Richard,

# lspci
0000:00:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
0000:00:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
0001:00:06.0 Non-VGA unclassified device: ALi Corporation M7101 Power Management Controller [PMU]
0001:00:07.0 ISA bridge: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
0001:00:0a.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
0001:00:0d.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
0002:00:02.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter (rev 01)
0002:00:02.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter (rev 01)
0003:00:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet
0003:00:02.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet

That is good. All 4 devices show up on the PCI bus.


# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:14:4f:5d:1e:7e
          inet addr:192.168.1.116  Bcast:192.168.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11450 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6220 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1000502 (977.0 KiB)  TX bytes:516835 (504.7 KiB)
          Interrupt:6
Matching HWaddr to the local-mac-address properties in the prtconf output that is the device listed at node 0xf00bea74 I think that you have previously confirmed that this is connected to net0 (known as "net" in the OBP aliases)

        net: '/pci@1f,700000/network@2'

and from your dmesg output you posted earlier that matches too

[   83.749175] tg3 0000:00:02.0: eth0: No firmware running



eth1      Link encap:Ethernet  HWaddr 00:14:4f:5d:1e:80
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:31

This HWaddr matches node 0xf00b0d34 which is net2.

        net2: '/pci@1d,700000/network@2'

So I think you need to do your tests connected to the net2 port.

[   45.499671] tg3 0003:00:02.0: eth1: dma_rwctrl[763f0000] dma_mask[32-bit]


Additionally it looks like the 2nd network device on each PCI bus is not getting
attached properly.

Does

dmesg | grep tg3
or
dmesg | grep 0003:00:02

produce anything relating to the other ports?

Regards

Richard

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9542 (9.3 KiB)  TX bytes:9542 (9.3 KiB)



I have attached the prtconf file:


Regards,


Kaya
<prtconf.txt>




Reply to: