From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C97FBC433EF for ; Sun, 8 May 2022 16:39:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=P/i72D3Hoz3HD4EAGGIGx/Bq93MlW9+HWKtP41JsBhM=; b=ewYQY0szFlGOlg Jk9IuegtFbApeMKZ+LvJICKCQ1ssmbvQYqSEVcD5qlECopDS02SJZm5iRZyLbA0oD7DScKDBAiCUz /RF3Moyia1PRyvYONVPOoXfJOaBZtuv0McRAtMvaegOG9fW72jchtOXLWov0XYrt3JVYh7o6W6ESF Z1X3QRYvlTK72O1ID1gTq9G1mar2hGwmL5tG4qa/gkVg2VF4vgMOGDZOK3i8GHtRrlP1SifaMDpCM SC0l1kgTprLmsTx1SMbRcysboIQcWuoO2sD68W7uc1ptuxDHz9LiXssXnFsQJAcvmMTNtNNhI6BuM UWWNbgfNMfs1EabJmkiQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nnjvh-00AeWV-Mb; Sun, 08 May 2022 16:38:45 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nnjve-00AeW3-ED for linux-arm-kernel@lists.infradead.org; Sun, 08 May 2022 16:38:44 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B730561254; Sun, 8 May 2022 16:38:41 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CA57FC385A4; Sun, 8 May 2022 16:38:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1652027921; bh=86X6hLRDZInID5O+3zn6HJZJsGsAn4/7cprlgYWK/xg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=TetWQ6RmuaY9NpN9IKJRrJiQb41EqjFZ5DWaMfsolYYUvSbseujbQQSvJFLzW3CmF V2K/7wyv0eEAx0jp8KaPDTcRN75vGqlVATIVp3fbH4k7PpxAQttx3K9snYj5omzvXR oyhLn1A1G4s0Id5Zgrd1qPlfL4dr+iyKIqNAdC1/IMfqkfJMJ8Co6kaNjE6wsd/030 IB3RUfX6Fc2F0xHgNjH668EKriByMAwVve9EuUPtO8FS0NOuFaH5cj7G4UCnfDca/V /EkA2iWpFMbrswdYFOCafT8o0og5DHW/yMbmplaLV5k+R+km4Dy4P+6wlZ2pRccWdJ naphqujjsHrxw== Received: by pali.im (Postfix) id 5E5A67F7; Sun, 8 May 2022 18:38:38 +0200 (CEST) Date: Sun, 8 May 2022 18:38:38 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Giammarco lynx Cc: "Russell King (Oracle)" , linux-arm-kernel@lists.infradead.org Subject: Re: Question abount VSOL/CarlitoxxPro SFP Patch on Marvell Armada (MCBIN DS) Message-ID: <20220508163838.dfrghazb5id4x6x5@pali> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220508_093842_596399_AFC179A3 X-CRM114-Status: GOOD ( 20.05 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Monday 07 March 2022 21:12:45 Giammarco lynx wrote: > adding > > linux-arm-kernel@lists.infradead.org > > Il giorno lun 7 mar 2022 alle ore 21:09 Giammarco lynx > ha scritto: > > > > ok, doing in the way that you suggest, the link is bringing up. > > Here is the logs (without ifconfig eth3 up and module plugged): > > > > [ 3.035643] mvpp2 f4000000.ethernet eth3: Using firmware node mac > > address 00:51:82:11:22:03 > > [ 11.872410] sfp sfp-eth3: Host maximum power 2.0W > > [ 11.877149] sfp sfp-eth3: tx disable 1 -> 1 > > [ 11.877155] sfp sfp-eth3: SM: enter empty:detached:down event insert > > [ 11.877159] sfp sfp-eth3: SM: exit probe:detached:down > > [ 11.877410] sfp sfp-eth3: SM: enter probe:detached:down event dev_attach > > [ 11.877414] sfp sfp-eth3: SM: exit probe:down:down > > [ 12.180129] sfp sfp-eth3: SM: enter probe:down:down event timeout > > [ 12.187906] sfp sfp-eth3: Detected broken RTL8672/RTL9601C emulated EEPROM > > [ 12.194814] sfp sfp-eth3: Switching to reading EEPROM to one byte at a time > > [ 12.242005] sfp sfp-eth3: module OEM V2801F > > rev 1.0 sn 202101195032 dc 210119 > > [ 12.251800] mvpp2 f4000000.ethernet eth3: requesting link mode > > inband/1000base-x with support 0000000,00000200,00000440 > > [ 12.251804] mvpp2 f4000000.ethernet eth3: switched to > > inband/1000base-x link mode > > [ 12.259318] sfp sfp-eth3: SM: exit present:down:down > > [ 12.270123] sfp sfp-eth3: skipping hwmon device registration due to > > broken EEPROM > > [ 12.277636] sfp sfp-eth3: diagnostic EEPROM area cannot be read > > atomically to guarantee data coherency > > [ 35.174143] mvpp2 f4000000.ethernet eth3: configuring for > > inband/1000base-x link mode > > [ 35.182026] mvpp2 f4000000.ethernet eth3: major config 1000base-x > > [ 35.188158] mvpp2 f4000000.ethernet eth3: phylink_mac_config: > > mode=inband/1000base-x/Unknown/Unknown adv=0000000,00000200,00000440 > > pause=04 link=0 an=1 > > [ 35.202945] sfp sfp-eth3: SM: enter present:down:down event dev_up > > [ 35.209152] sfp sfp-eth3: tx disable 1 -> 0 > > [ 35.213387] sfp sfp-eth3: SM: exit present:up:wait > > [ 35.280129] sfp sfp-eth3: SM: enter present:up:wait event timeout > > [ 35.286253] sfp sfp-eth3: SM: exit present:up:link_up > > [ 56.097724] sfp sfp-eth3: los 0 -> 1 > > [ 56.101324] sfp sfp-eth3: SM: enter present:up:link_up event los_high > > [ 56.107792] sfp sfp-eth3: SM: exit present:up:link_up > > [ 56.112876] sfp sfp-eth3: mod-def0 1 -> 0 > > [ 56.116903] sfp sfp-eth3: tx-fault 0 -> 1 > > [ 56.120933] sfp sfp-eth3: SM: enter present:up:link_up event remove > > > > Then after "ifconfig eth3 up" i've removed and reinserted the SFP, > > this is the log: > > > > [ 56.127227] sfp sfp-eth3: module removed > > [ 56.131175] sfp sfp-eth3: tx disable 0 -> 1 > > [ 56.135432] sfp sfp-eth3: SM: exit empty:up:down > > [ 56.140067] sfp sfp-eth3: SM: enter empty:up:down event tx_fault > > [ 56.146103] sfp sfp-eth3: SM: exit empty:up:down > > [ 59.350731] sfp sfp-eth3: mod-def0 0 -> 1 > > [ 59.354757] sfp sfp-eth3: SM: enter empty:up:down event insert > > [ 59.360619] sfp sfp-eth3: SM: exit probe:up:down > > [ 59.680123] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 59.686185] sfp sfp-eth3: SM: exit probe:up:down > > [ 59.800122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 59.806179] sfp sfp-eth3: SM: exit probe:up:down > > [ 59.920122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 59.926179] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.040122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.046178] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.160123] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.166178] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.270122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.276177] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.380122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.386178] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.500122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.506177] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.620121] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.626176] sfp sfp-eth3: SM: exit probe:up:down > > [ 60.740122] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 60.746177] sfp sfp-eth3: please wait, module slow to respond > > [ 60.751982] sfp sfp-eth3: SM: exit probe:up:down > > [ 65.840198] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 65.846262] sfp sfp-eth3: SM: exit probe:up:down > > [ 70.870128] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 70.876192] sfp sfp-eth3: SM: exit probe:up:down > > [ 75.920133] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 75.926196] sfp sfp-eth3: SM: exit probe:up:down > > [ 80.896801] mvpp2 f4000000.ethernet eth3: mac link up > > [ 80.960124] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 80.966183] sfp sfp-eth3: SM: exit probe:up:down > > [ 81.330385] sfp sfp-eth3: los 1 -> 0 > > [ 81.333978] sfp sfp-eth3: tx-fault 1 -> 0 > > [ 81.338004] sfp sfp-eth3: SM: enter probe:up:down event tx_clear > > [ 81.344044] sfp sfp-eth3: SM: exit probe:up:down > > [ 81.348680] sfp sfp-eth3: SM: enter probe:up:down event los_low > > [ 81.354629] sfp sfp-eth3: SM: exit probe:up:down > > [ 86.000154] sfp sfp-eth3: SM: enter probe:up:down event timeout > > [ 86.013661] sfp sfp-eth3: Detected broken RTL8672/RTL9601C emulated EEPROM > > [ 86.020569] sfp sfp-eth3: Switching to reading EEPROM to one byte at a time > > [ 86.067758] sfp sfp-eth3: module OEM V2801F > > rev 1.0 sn 202101195032 dc 210119 > > [ 86.077555] mvpp2 f4000000.ethernet eth3: requesting link mode > > inband/1000base-x with support 0000000,00000200,00000440 > > [ 86.088390] sfp sfp-eth3: tx disable 1 -> 0 > > [ 86.092636] sfp sfp-eth3: SM: exit present:up:wait > > [ 86.097448] sfp sfp-eth3: skipping hwmon device registration due to > > broken EEPROM > > [ 86.104965] sfp sfp-eth3: diagnostic EEPROM area cannot be read > > atomically to guarantee data coherency > > [ 86.160128] sfp sfp-eth3: SM: enter present:up:wait event timeout > > [ 86.166252] sfp sfp-eth3: SM: exit present:up:link_up > > [ 86.171404] mvpp2 f4000000.ethernet eth3: Link is Up - 1Gbps/Full - > > flow control off > > [ 86.179193] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready > > > > In that way it goes up. So how can we avoid this behaviour? > > > > Thanks Hello! This looks like that your GPON ONT/ONU SFP module is incompatible with GPON OLT to which it is connected. All GPON ONT/ONU units must be fully configurable from OLT, including LAN part of ONU (link between SFP module and your CPU) and therefore it is up to the OLT when it says that LAN part is up. Mostly I saw these issues with GPON ONT/ONU modules from vendor A connected to GPON OLT from vendor B. Generally, you cannot do nothing :-( just replace SFP module by another one which would be from the same vendor as your ISP's OLT. Sometimes may help changing some settings in SFP module or on OLT side, but both changes can be done only via OMCI protocol and only from OLT management console / web interface. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel