All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jordan Vrtanoski <jordan.vrtanoski@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: ClearFog GT 8K not initialising SFP-H10GB-CU1M transceiver on 5.4.150
Date: Tue, 16 Nov 2021 10:51:16 +0000	[thread overview]
Message-ID: <YZONJC7KhACsq+5m@shell.armlinux.org.uk> (raw)
In-Reply-To: <3AB36F18-250C-46F5-8135-94C79102B8A5@gmail.com>

On Tue, Nov 16, 2021 at 02:11:54PM +0400, Jordan Vrtanoski wrote:
> Hi,
> 
> I am trying to build kernel 5.4.150 for SolidRun ClearFog GT 8K. The kernel is stable and I had not experiance any stability issue. The only issue I am facing is with enabling the support for the SFP+ module. 
> 
> I am using SFP-H10GB-CU1M direct coper cable module. The module works on earlier version of the kernel 5.1.x (verified on the same hardware), however once the device is booted under 5.4.150, the transceiver is not recognised and the interface remains down. There are no error messages reported by the kernel.

The transceiver is recognised, but for some reason the link isn't coming
up - and from the debug kernel messages, there's no information pointing
to why not. At a guess, mvpp2 is not reporting that it has link for some
reason.

I don't think it's an issue with the module or the SFP layer - since
that is going into "link up" state and the TX_DISABLE signal is being
deasserted (not that they mean much for a DA cable.) So, I'd be thinking
that the problem is with the comphy or mvpp2 drivers.

mvpp2 doesn't have much in the way of debugging messages to help with
this, but phylink should at least be printing "mac link" messages in
both 5.1.x and 5.4.x kernels - but it doesn't appear to be. That
suggests enabling dynamic debug is not sufficient to get those messages
out... I'm afraid I've never used dynamic debug so can't help with that.
Maybe someone who knows now netdev_dbg() interacts with dynamic debug
can help with that. Strangely, you are getting the netdev_dbg() from
within phylink_sfp_module_insert(), so I don't really understand why
you aren't getting anything else from phylink.

It all seems rather odd.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-11-16 10:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 10:11 ClearFog GT 8K not initialising SFP-H10GB-CU1M transceiver on 5.4.150 Jordan Vrtanoski
2021-11-16 10:51 ` Russell King (Oracle) [this message]
2021-11-20 18:57   ` Jordan Vrtanoski
2021-11-20 19:41     ` Russell King (Oracle)
2021-11-21  5:37       ` Jordan Vrtanoski
2021-11-22 10:51         ` Jordan Vrtanoski
2021-11-22 13:15           ` Jordan Vrtanoski
2021-11-22 19:53           ` Russell King (Oracle)
2021-11-22 19:53             ` Russell King (Oracle)
2021-11-23 12:20             ` Greg KH
2021-11-23 12:20               ` Greg KH

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=YZONJC7KhACsq+5m@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=jordan.vrtanoski@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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.