linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Ivan Vecera <ivecera@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: Failed to start Raise network interfaces error
Date: Tue, 12 Dec 2023 15:44:49 +0100 (CET)	[thread overview]
Message-ID: <492e8f8-c7af-7423-59e6-348ce5fca9b1@inria.fr> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2312102317350.3198@hadrien>



On Sun, 10 Dec 2023, Julia Lawall wrote:

> Hello,
>
> Starting with the commit:
>
> commit 9e479d64dc58f11792f638ea2e8eff3304edaabf
> Author: Ivan Vecera <ivecera@redhat.com>
> Date:   Fri Oct 13 19:07:51 2023 +0200
>
>     i40e: Add initial devlink support
>
> I am not able to boot normally.  The console shows the message
>
> Failed to start Raise network interfaces
>
> Searching for this message on th internet produces some old discussions
> that suggest to look at the file /etc/network/interfaces.  That file on my
> system contains:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> auto enp24s0f0
> iface enp24s0f0 inet dhcp
>
> -------------------------------
>
> The machine in question is part of a cluster, and may be set up in a
> specific way.  It actually does boot, in the sense that I get a
> login prompt, but it doesn't seem to be reachable from the outside.
>
> The above failure message is followed by a message about the inability to
> retrieve a file that is part of the local setup process.  I can find out
> more about what is supposed to be done with this file.
>
> Please let me know if there is any further information I can provide.

After some invetigation, it seems that the machine boots, but has no
access to the network.  And indeed, the information about the network for
this machine says:

eth0/enp24s0f0, Ethernet, configured rate: 10 Gbps, model: Intel Ethernet
Controller X710 for 10GbE SFP+, driver: i40e

All is fine on another machine in the same infrastructure that has a
different networking configuration:

eth0/eno1, Ethernet, configured rate: 25 Gbps, model: Mellanox
Technologies MT27710 Family [ConnectX-4 Lx], driver: mlx5_core, SR-IOV
enabled
eth1/eno2, Ethernet, configured rate: 25 Gbps, model: Mellanox
Technologies MT27710 Family [ConnectX-4 Lx], driver: mlx5_core, SR-IOV
enabled

thanks,
julia

  reply	other threads:[~2023-12-12 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 22:28 Failed to start Raise network interfaces error Julia Lawall
2023-12-12 14:44 ` Julia Lawall [this message]
2023-12-12 14:52 ` Ivan Vecera
2023-12-12 15:08   ` Julia Lawall
2023-12-12 15:45     ` Ivan Vecera
2023-12-12 15:48       ` Julia Lawall
2023-12-12 16:33       ` Julia Lawall
2023-12-12 16:44         ` Ivan Vecera
2023-12-12 16:53           ` Julia Lawall
2023-12-14 14:33           ` Julia Lawall
2023-12-14 14:47             ` Ivan Vecera
2023-12-14 14:50               ` Julia Lawall
2023-12-14 20:55           ` Lucas Nussbaum

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=492e8f8-c7af-7423-59e6-348ce5fca9b1@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=davem@davemloft.net \
    --cc=ivecera@redhat.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).