The frame checksum error count looks a little high to me.  Its not 
"critically" bad, but you might want to double check your connections 
and your gear.  Its a sign that packets are being corrupted -- usually 
in-flight, but it could also be occurring elsewhere.  With some NICs, 
certain bugs can trigger fcs_errors -- I'm not sure this is the case 
here or not.

The other, probably more obvious thing, to check, is to make sure that 
both sides are in agreement about the link duplex.  In certain 
situations, a misconfigured link duplex setting can cause fcs errors.  
(Although, I *think* I would expect to see them at the peer, rather than 
here, since this NIC appears to be configured for full duplex.  But I 
wouldn't rule out bugs where the driver *thinks* the hardware is full 
duplex, but the hardware is really running in half-duplex.  Maybe 
Masa-san can check into that.)

    -- Garrett

Piotr Jasiukajtis wrote:
> Well, I created simple script in /etc/init.d/ so it seems to be working
> now, but:
>
>   
>> netstat -I sfe0 -in
>>     
> Name  Mtu  Net/Dest      Address        Ipkts  Ierrs Opkts  Oerrs Collis
> Queue 
> sfe0  1500 192.168.0.0   192.168.0.3    880    55    0      0     0
> 0     
>
>   
>> kstat sfe
>>     
> module: sfe                             instance: 0     
> name:   mac                             class:    net
>         adv_cap_1000fdx                 0
>         adv_cap_1000hdx                 0
>         adv_cap_100fdx                  1
>         adv_cap_100hdx                  0
>         adv_cap_100T4                   0
>         adv_cap_10fdx                   1
>         adv_cap_10hdx                   1
>         adv_cap_asmpause                1
>         adv_cap_autoneg                 0
>         adv_cap_pause                   1
>         adv_rem_fault                   0
>         align_errors                    0
>         brdcstrcv                       46
>         brdcstxmt                       48
>         cap_1000fdx                     0
>         cap_1000hdx                     0
>         cap_100fdx                      1
>         cap_100hdx                      1
>         cap_100T4                       0
>         cap_10fdx                       1
>         cap_10hdx                       1
>         cap_asmpause                    1
>         cap_autoneg                     0
>         cap_pause                       1
>         cap_rem_fault                   0
>         carrier_errors                  0
>         collisions                      0
>         crtime                          34,090248325
>         defer_xmts                      0
>         ex_collisions                   0
>         fcs_errors                      16
>         first_collisions                0
>         ierrors                         101
>         ifspeed                         100000000
>         ipackets                        1204
>         ipackets64                      1204
>         jabber_errors                   0
>         link_asmpause                   0
>         link_autoneg                    0
>         link_duplex                     2
>         link_pause                      0
>         link_state                      1
>         link_up                         1
>         lp_cap_1000fdx                  0
>         lp_cap_1000hdx                  0
>         lp_cap_100fdx                   0
>         lp_cap_100hdx                   0
>         lp_cap_100T4                    0
>         lp_cap_10fdx                    0
>         lp_cap_10hdx                    0
>         lp_cap_asmpause                 0
>         lp_cap_autoneg                  0
>         lp_cap_pause                    0
>         lp_rem_fault                    0
>         macrcv_errors                   0
>         macxmt_errors                   0
>         multi_collisions                0
>         multircv                        7
>         multixmt                        0
>         norcvbuf                        0
>         noxmtbuf                        0
>         obytes                          0
>         obytes64                        0
>         oerrors                         0
>         oflo                            0
>         opackets                        0
>         opackets64                      0
>         promisc                         0
>         rbytes                          309079
>         rbytes64                        309079
>         runt_errors                     58
>         snaptime                        432,045809824
>         sqe_errors                      0
>         toolong_errors                  27
>         tx_late_collisions              0
>         uflo                            0
>         unknowns                        0
>         xcvr_addr                       1
>         xcvr_id                         4294967295
>         xcvr_inuse                      4
>
> module: sfe                             instance: 0     
> name:   sfe0                            class:    net
>         brdcstrcv                       46
>         brdcstxmt                       48
>         collisions                      0
>         crtime                          34,103830488
>         ierrors                         101
>         ifspeed                         100000000
>         ipackets                        1204
>         ipackets64                      1204
>         link_duplex                     2
>         link_state                      1
>         multircv                        7
>         multixmt                        0
>         norcvbuf                        0
>         noxmtbuf                        0
>         obytes                          0
>         obytes64                        0
>         oerrors                         0
>         opackets                        0
>         opackets64                      0
>         rbytes                          309079
>         rbytes64                        309079
>         snaptime                        432,05588841
>         unknowns                        94
>
> Any idea?
> :/
>
>
> Dnia 02-03-2008, N o godzinie 13:59 +0100, Piotr Jasiukajtis pisze:
>   
>> Hello,
>>
>> It looks like there is a bug in sfe driver. It has problem with 
>> auto negotiation:
>>
>> Mar  2 12:40:39 devhost1 sfe: [ID 831844 kern.info] sfe0:
>> auto-negotiation started
>> Mar  2 12:40:39 devhost1 sfe: [ID 490553 kern.info] sfe0:
>> auto-negotiation failed: remote fault
>> Mar  2 12:40:39 devhost1 sfe: [ID 831844 kern.info] sfe0:
>> auto-negotiation started
>> Mar  2 12:40:39 devhost1 sfe: [ID 490553 kern.info] sfe0:
>> auto-negotiation failed: remote fault
>> Mar  2 12:40:39 devhost1 sfe: [ID 831844 kern.info] sfe0:
>> auto-negotiation started
>> Mar  2 12:40:40 devhost1 sfe: [ID 490553 kern.info] sfe0:
>> auto-negotiation failed: remote fault
>>
>>
>>
>>
>> # ifconfig sfe0 up
>> # ifconfig sfe0
>> sfe0: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 2
>>         inet 192.168.0.3 netmask ffffff00 broadcast 192.168.0.255
>>         ether 0:b:6a:63:a4:fb 
>>
>> # dladm show-dev
>> LINK            STATE  SPEED    DUPLEX
>> sfe0            down   100Mb    unknown
>> elxl0           unknown 0Mb     half
>>
>> # dladm show-link
>> LINK        CLASS    MTU    STATE    OVER
>> sfe0        phys     1500   down     --
>> elxl0       phys     1500   unknown  --
>>
>> # /usr/X11/bin/scanpci 
>>
>> pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x1039 device 0x0746
>>  Silicon Integrated Systems [SiS] 746 Host
>>
>> pci bus 0x0000 cardnum 0x01 function 0x00: vendor 0x1039 device 0x0002
>>  Silicon Integrated Systems [SiS] SG86C202
>>
>> pci bus 0x0000 cardnum 0x02 function 0x00: vendor 0x1039 device 0x0008
>>  Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
>>
>> pci bus 0x0000 cardnum 0x02 function 0x05: vendor 0x1039 device 0x5513
>>  Silicon Integrated Systems [SiS] 5513 [IDE]
>>
>> pci bus 0x0000 cardnum 0x02 function 0x07: vendor 0x1039 device 0x7012
>>  Silicon Integrated Systems [SiS] AC'97 Sound Controller
>>
>> pci bus 0x0000 cardnum 0x03 function 0x00: vendor 0x1039 device 0x7001
>>  Silicon Integrated Systems [SiS] USB 1.0 Controller
>>
>> pci bus 0x0000 cardnum 0x03 function 0x01: vendor 0x1039 device 0x7001
>>  Silicon Integrated Systems [SiS] USB 1.0 Controller
>>
>> pci bus 0x0000 cardnum 0x03 function 0x02: vendor 0x1039 device 0x7002
>>  Silicon Integrated Systems [SiS] USB 2.0 Controller
>>
>> pci bus 0x0000 cardnum 0x04 function 0x00: vendor 0x1039 device 0x0900
>>  Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet
>>
>> pci bus 0x0000 cardnum 0x0b function 0x00: vendor 0x1102 device 0x0002
>>  Creative Labs SB Live! EMU10k1
>>
>> pci bus 0x0000 cardnum 0x0b function 0x01: vendor 0x1102 device 0x7002
>>  Creative Labs SB Live! Game Port
>>
>> pci bus 0x0000 cardnum 0x0c function 0x00: vendor 0x10b7 device 0x9055
>>  3Com Corporation 3c905B 100BaseTX [Cyclone]
>>
>> pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4153
>>  ATI Technologies Inc RV350 AS [Radeon 9550]
>>
>> pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x4173
>>  ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)
>>
>>
>> # uname -srv
>> SunOS 5.11 snv_83
>>
>>
>>
>> This is workaround:
>> ndd -set /dev/sfe0 adv_autoneg_cap 0
>>
>> But the problem repeats after reboot. That is, I need to set it
>> manually.
>>
>> I added this to the /etc/system, but it doesn't work:
>>
>> set sfe0:adv_autoneg_cap=0
>> set sfe0:adv_100hdx_cap=0
>> set sfe0:adv_100fdx_cap=1
>>
>>
>> Any idea?
>>
>>     

_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to