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

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



On 19/11/2012 22:36, Kaya Saman wrote:

So Richard, what's your opinion on when this might get fixed or a
workaround found?

Crystal ball time :-)
I suspect that this can be worked around quite quickly. From a quick look at the tg3 driver source code I don't think that the BAR 2 registers are actually used on the model present in that version.
As a quick and dirty hack it might just be as simple as removing the BAR 2 entry from the assigned-addresses property. My Openboot/forth-foo is a little rusty but I'll see if I can find some time to work out a quick hack to try that.
If that works then I'd suspect that the correct way to handle this is to workaround the issue would be somewhere in the sparc platform setup code in the kernel. 



Basically I'm a bit in limbo now as the machine is built to the spec I
need bar the NICs.

Should I switch OS for now or do you think I should persist in debugging
until a solution is reached?
I rather suspect that the only way this will get fixed is if someone with the "broken" setup is willing to test.
If we can try a couple of the simple/hacky tests just to confirm my hypothesis that would be good. I'll try to find time to do that later tonight. 

Regards

Richard



Of course I would love to help out anyway that I could as I started with
Debian all the way back from Sarge and Etch days but on the other hand I
need a usable system too..... !humph!

Regards,

Kaya

On 11/19/2012 10:29 PM, Richard Mortimer wrote:



On 19/11/2012 17:34, Kaya Saman wrote:

On 11/19/2012 04:28 PM, Richard Mortimer wrote:
# dmesg | grep tg3
[   41.528377] tg3.c:v3.121 (November 2, 2011)
[   42.096605] tg3 0000:00:02.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware
update.sym0: No NVRAM, ID 7, Fast-80, LVD, parity checking
[   42.249670] tg3 0000:00:02.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware
update.
[   42.305863] tg3 0000:00:02.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware
update.
[   42.308810] tg3 0000:00:02.0: eth0: Tigon3 [partno(none) rev 2100]
(PCI:66MHz:64-bit) MAC address 00:14:4f:5d:1e:7e
[   42.446140] tg3 0000:00:02.0: eth0: attached PHY is 5704
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[   42.575463] tg3 0000:00:02.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[   42.679542] tg3 0000:00:02.0: eth0: dma_rwctrl[763f0000]
dma_mask[32-bit]
[   43.278806] tg3 0000:00:02.1: BAR 2: can't reserve [mem
0x7f700000000-0x7f70000ffff]
[   43.380653] tg3 0000:00:02.1: Cannot obtain PCI resources, aborting
[   43.741325] tg3: probe of 0000:00:02.1 failed with error -16


A bit more information for the bug report...

Looking at the prtconf output for your machine I suspect that the
problem is that the OBP assigned-addresses properties corresponding to
BAR (base address register) 2 are pointing to the same address. That
means that the 2nd device on that PCI bus fails to attach because the
PCI framework is saying that the address is already in use.



    Node 0xf00697a0
        .node:  f00697a0
        available:  81000000.00000000.00000300.00000000.0000fd00.
                    82000000.00000000.00100000.00000000.00100000.
                    82000000.00000000.00600000.00000000.bfa00000.
                    82000000.00000000.e0000000.00000000.20000000
        reg:  00000400.0ff00000.00000000.0000b000.
              00000400.0fc10000.00000000.00007020.
              000007f6.00000000.00000000.00000100.
              00000400.0ff80000.00000000.00010000
        ranges:
00000000.00000000.00000000.000007f6.00000000.00000000.01000000.
01000000.00000000.00000000.000007f6.01000000.00000000.01000000.
02000000.00000000.00000000.000007f7.00000000.00000001.00000000.
03000000.00000000.00000000.000007f7.00000000.00000001.00000000
        bus-range:  00000000.00000000
        #address-cells:  00000003
        #size-cells:  00000002

        Node 0xf00bea74
            .node:  f00bea74
            local-mac-address:  00144f5d.1e7e
            assigned-addresses:
               83001010.00000000.00200000.00000000.00200000.
               83001018.00000000.00000000.00000000.00010000
                                 ^^^^^^^^          ^^^^^^^^
** BAR 2 here. Start Address = 0x0, length 0x10000 **

            reg:
               00001000.00000000.00000000.00000000.00000000.
               03001010.00000000.00000000.00000000.00200000.
               03001018.00000000.00000000.00000000.00010000

        Node 0xf00c58d8
            .node:  f00c58d8
            local-mac-address:  00144f5d.1e7f
            assigned-addresses:
               83001110.00000000.00400000.00000000.00200000.
               83001118.00000000.00000000.00000000.00010000
                                 ^^^^^^^^          ^^^^^^^^
** BAR 2 here. Start Address = 0x0, length 0x10000 **
            reg:
               00001100.00000000.00000000.00000000.00000000.
               03001110.00000000.00000000.00000000.00200000.
               03001118.00000000.00000000.00000000.00010000






[   44.072115] tg3 0003:00:02.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware
update.
[   44.129861] tg3 0003:00:02.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware
update.
[   44.559842] tg3 0003:00:02.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware
update.
[   44.562363] tg3 0003:00:02.0: eth1: Tigon3 [partno(none) rev 2100]
(PCI:66MHz:64-bit) MAC address 00:14:4f:5d:1e:80
[   44.699696] tg3 0003:00:02.0: eth1: attached PHY is 5704
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[   44.829020] tg3 0003:00:02.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[   44.933095] tg3 0003:00:02.0: eth1: dma_rwctrl[763f0000]
dma_mask[32-bit]
[   45.125173] tg3 0003:00:02.1: BAR 2: can't reserve [mem
0x7c700000000-0x7c70000ffff]
[   45.227044] tg3 0003:00:02.1: Cannot obtain PCI resources, aborting
[   45.317544] tg3: probe of 0003:00:02.1 failed with error -16
[   57.680406] tg3 0000:00:02.0: eth0: No firmware running
[   59.335720] tg3 0000:00:02.0: eth0: Link is up at 100 Mbps, full
duplex
[   59.422695] tg3 0000:00:02.0: eth0: Flow control is off for TX and
off for RX
Reply to: