From: "U.Mutlu" <um@mutluit.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: Diagnosing network module for missing link establishment (cxgb3, Chelsio T320)
Date: Fri, 29 Jun 2018 16:45:36 +0200 [thread overview]
Message-ID: <5B364610.8090401@mutluit.com> (raw)
In-Reply-To: <20180629133304.GD11285@lunn.ch>
Andrew Lunn wrote on 06/29/2018 03:33 PM:
>> Kernel: 3.16.0-4-amd64 (Debian v8 stock kernel)
>
> This is very old. Please at least try the current version of Debian,
> "Stretch".
>
> Andrew
>
I had the same idea and attached the card to another machine with a recent kernel:
# uname -a
Linux c5 4.14.1-my1a #1 SMP Wed Nov 22 11:20:35 CET 2017 x86_64 GNU/Linux
But the version of the cxgb3.ko is the same, and the same effect happens: no
link establishment.
So, what should I do get it working?
I could also re-compile the cxgb3 driver with enabled diagnostic settings, if
it has any such (haven't studied yet).
Is there an easier method to find the reason, and hopefully get it establish a
link?
Btw, to encirle the problem, I'm simply attaching the fibre cable
from port 1 to port 2 on the same card. Is doing so ok?
Thx
# dmesg | grep "Chelsio\|cxgb\|eth[0-9]"
[ 0.670473] cxgb3: Chelsio T3 Network Driver - version 1.1.5-ko
[ 0.691397] alx 0000:04:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet
[d0:50:99:0e:89:04]
[ 1.044840] cxgb3 0000:01:00.0: Port 0 using 4 queue sets.
[ 1.044883] cxgb3 0000:01:00.0: Port 1 using 4 queue sets.
[ 1.044924] cxgb3 0000:01:00.0 eth1: Chelsio T320 10GBASE-R RNIC (rev 3)
PCI Express x8 MSI-X
[ 1.044964] cxgb3: eth1: 128MB CM, 256MB PMTX, 256MB PMRX, S/N: PT37080022
[ 1.044999] cxgb3 0000:01:00.0 eth2: Chelsio T320 10GBASE-R RNIC (rev 3)
PCI Express x8 MSI-X
[ 1.728291] cxgb3 0000:01:00.0 eth6: renamed from eth1
[ 1.748264] systemd-udevd[368]: renamed network interface eth1 to eth6
[ 1.748351] cxgb3 0000:01:00.0 eth7: renamed from eth2
[ 1.777472] alx 0000:04:00.0 eth3: renamed from eth0
[ 1.777522] systemd-udevd[378]: renamed network interface eth2 to eth7
[ 1.789052] systemd-udevd[372]: renamed network interface eth0 to eth3
[ 31.248196] alx 0000:04:00.0 eth3: NIC Up: 1 Gbps Full
next prev parent reply other threads:[~2018-06-29 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 23:17 Diagnosing network module for missing link establishment (cxgb3, Chelsio T320) U.Mutlu
2018-06-29 13:33 ` Andrew Lunn
2018-06-29 14:45 ` U.Mutlu [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-28 9:33 U.Mutlu
2018-06-28 16:07 ` Lucas De Marchi
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=5B364610.8090401@mutluit.com \
--to=um@mutluit.com \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.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.