Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp4701400rdb; Tue, 12 Dec 2023 07:08:37 -0800 (PST) X-Google-Smtp-Source: AGHT+IHxrfOSGuioXMOEZWHv6vkTuhANKC5XHx6eccFGHMwgbLIAQzahXIzlP4qhRK9tjM4AEtSe X-Received: by 2002:a05:6a00:1744:b0:6cd:fe59:69d1 with SMTP id j4-20020a056a00174400b006cdfe5969d1mr3132889pfc.28.1702393717185; Tue, 12 Dec 2023 07:08:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702393717; cv=none; d=google.com; s=arc-20160816; b=C2nFjuNXy9a0pbuhnB1Cg9fW7ICJyzTP8rP6xxRZnwNQ1AXrQ7BMil1fj2b0kEPMBe pgJOtqoYi+etPTUx8IsogPFJUftjr6fz4PsXkrr2Z8tbvjPTVzew8qfWYHEhlPQrRRuE L2ViXNMc3nJJ7XBR2FDzc3bezT3m6sanrz+fN4aXHKgQrsv7eumzcgBdplkRNqNhhJUg tjJkMKPqYn/a9Ytx3r5/5vKLDdldHlok17nvivtMLeyjauswMeYVWfhntNRb0ewHLmJN 5N/l3w+WPN+1PXIacqgodYsCKsRo9tOM5K/P83ceN3nGgFyx5+NZtnOHR5Y6LO5brwMn yOSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=/ViUfK5Qr+atc+6M7L5mu3NaL5ELpYL5fC4EkoScI0k=; fh=nvrfxrRL6yTjdzjzuyW0esT4jBxKco3E79PlrLHTLZM=; b=IPDdC1npKk1blzH+gB9r+cV+aORx2y1UR6a4X0zJy2bBWQ+Bl+g3ob4jqLD8UB685p Nsc56W8WVRf+ds2tGKsyNgE6tjEUyTKFvEkD3iuT3yHdJVgzdT9MH/zPulb88ebA0UPC JxauqtWnsUDQwByD558AB4QYWdJ8siDpTxFMFoI8D6c4olVSynmOJqJAXTv2zjD5AsW5 GIyzSAriA1pI54ATTjP5M+kKtaQvxyDy/qkO2uCqgTbnazD9DxkuPepZEeEJTfKiwLNW 8Lmlt3Ndlh4ho5R7/56VIn+OOhdFuvmCQ2FCDfdPYVqCXOLoaAhAjVActe6svlsdjsfv fibg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@inria.fr header.s=dc header.b=oP6sHml1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=inria.fr Return-Path: Received: from morse.vger.email (morse.vger.email. [2620:137:e000::3:1]) by mx.google.com with ESMTPS id s7-20020a056a0008c700b006d09ceb6d1asi2299386pfu.173.2023.12.12.07.08.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Dec 2023 07:08:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1; Authentication-Results: mx.google.com; dkim=pass header.i=@inria.fr header.s=dc header.b=oP6sHml1; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=inria.fr Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by morse.vger.email (Postfix) with ESMTP id CBCC3802BD41; Tue, 12 Dec 2023 07:08:34 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at morse.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1376469AbjLLPIU (ORCPT + 99 others); Tue, 12 Dec 2023 10:08:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33578 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1376461AbjLLPIT (ORCPT ); Tue, 12 Dec 2023 10:08:19 -0500 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 87F8CAA for ; Tue, 12 Dec 2023 07:08:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=/ViUfK5Qr+atc+6M7L5mu3NaL5ELpYL5fC4EkoScI0k=; b=oP6sHml1sTlA4Bk/6Ezha0+OpcjEZiYoeDpglw1Ku8biOQCqDINVza8/ cmxCGzNo34i0rLmIATmFyiF1l/yV73LBcieC5jnFP4Q1CR7fFUJwxH+vF KpaoEwWrvpqam0xCCbT7sQ83EnGVTq0ayI9o9MtBEWMfszc2bG6PGkfil c=; Authentication-Results: mail3-relais-sop.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=julia.lawall@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr X-IronPort-AV: E=Sophos;i="6.04,270,1695679200"; d="scan'208";a="74197563" Received: from dt-lawall.paris.inria.fr ([128.93.67.65]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Dec 2023 16:08:24 +0100 Date: Tue, 12 Dec 2023 16:08:22 +0100 (CET) From: Julia Lawall To: Ivan Vecera cc: "David S. Miller" , linux-kernel@vger.kernel.org Subject: Re: Failed to start Raise network interfaces error In-Reply-To: <21977757-3a63-4586-ae03-e6630c1f009d@redhat.com> Message-ID: References: <21977757-3a63-4586-ae03-e6630c1f009d@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on morse.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (morse.vger.email [0.0.0.0]); Tue, 12 Dec 2023 07:08:35 -0800 (PST) On Tue, 12 Dec 2023, Ivan Vecera wrote: > On 10. 12. 23 23:28, Julia Lawall wrote: > > Hello, > > > > Starting with the commit: > > > > commit 9e479d64dc58f11792f638ea2e8eff3304edaabf > > Author: Ivan Vecera > > 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 problem is maybe with interface name... after this commit the interface > should contain port_name suffix. In your case the name should be > `enp24s0f0np0`. > > Could you please check it? Thanks for the feedback. But I'm not clear on how this would work. Does there have to be one name for kernels before this patch and another name for kernels starting with this patch? Or is the new name also acceptable for older kernels? thanks, julia