From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 29497A0543 for ; Tue, 4 Oct 2022 08:50:04 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B3B5B40DDC; Tue, 4 Oct 2022 08:50:03 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id C7BCB40A87 for ; Tue, 4 Oct 2022 08:50:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664866201; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GHd/LaVqWDvoTmyavZxbm4q2XChmPNBwftGjtOTjeEw=; b=UV4caH/u3hn0PsBm1cfj/4YpBReqgrQPXgRx/d88Fm8Chhnp4n0IzA/ziW5cfKe1GARV/D GSu/VQD++GHDjnvs0goh55ecL+sUZg0N59I9tEfcMY02EfTJ9JC2D8CYEALkA4Xh0/BKDi 8uwp1hPU0hFEUk/IsDsKjsBzdrY/bTE= Received: from mail-pj1-f71.google.com (mail-pj1-f71.google.com [209.85.216.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-483-heLVihlvNWGoxwr-mAQ6XA-1; Tue, 04 Oct 2022 02:50:00 -0400 X-MC-Unique: heLVihlvNWGoxwr-mAQ6XA-1 Received: by mail-pj1-f71.google.com with SMTP id hk15-20020a17090b224f00b00205fa3483bdso11236395pjb.8 for ; Mon, 03 Oct 2022 23:49:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date; bh=GHd/LaVqWDvoTmyavZxbm4q2XChmPNBwftGjtOTjeEw=; b=kD1sHaTzYoygascT4nybmzUgBF4s9u7NUMWmh5/8yFdw1u8A4YmXTIFaeOB7ksU67u 1B0K0MjqYuRNWDmVfo1GZT0kbYwTOBTXFliv7l52bg5D64yB+3vpcn0ADAKelYRJ2Iw/ QnInocgZrfKH5KDkbwbO9Ysj8HPEbf+W8yN3ecLJQAe2Ke5zY2y7Lz7WOB48yPUiXORG K0LyRfczjUjPUZdPz9K5TrnxdA0tXBms0jhrKNz4U9x8Bq5Y4GhuCoyo+XtIOkajEcr7 +FJEwp9+o6lfFb9vgMWOPC8if/EoBGnyc0Xfzbv2D6Qz1GAXjht5FKoA5dDcLoQk8Av+ 0uiA== X-Gm-Message-State: ACrzQf3Y/VN40mfM23HTpJN50UXs++vcwF89BNQqddAaom1QCHapOP5m Pj2qgrhEQxyboiNVFnSwm9y6CnPDKmFXga2JOHO14krK09hYYBe1roe4nEMMUSAZWzG2xkeqSXP i8nED7saUpYhFBmNgd6Qt7A== X-Received: by 2002:a63:5b58:0:b0:452:2ba4:f86b with SMTP id l24-20020a635b58000000b004522ba4f86bmr4807841pgm.223.1664866199091; Mon, 03 Oct 2022 23:49:59 -0700 (PDT) X-Google-Smtp-Source: AMsMyM64UuFZJQlI3J6I/hsOafIcGp7VKexTw+Csm2DNuEl38EldC8Gxkh/NYTenJZgXTjJL/cuM7l6FEPfh4Ez9i1k= X-Received: by 2002:a63:5b58:0:b0:452:2ba4:f86b with SMTP id l24-20020a635b58000000b004522ba4f86bmr4807827pgm.223.1664866198870; Mon, 03 Oct 2022 23:49:58 -0700 (PDT) MIME-Version: 1.0 References: <5aed7250.25e2.1833a0110ef.Coremail.feng32@163.com> <20220916081059.5b9841a1@hermes.local> <1f974932.6f93.1835a928c39.Coremail.feng32@163.com> <20220920081625.2a307107@hermes.local> <5e2cb89b.6d5b.1835fe36090.Coremail.feng32@163.com> In-Reply-To: <5e2cb89b.6d5b.1835fe36090.Coremail.feng32@163.com> From: David Marchand Date: Tue, 4 Oct 2022 08:49:47 +0200 Message-ID: Subject: Re: Re: l2fwd: Requested device 0000:02:00.0 cannot be used (Ubuntu 22.04, DPDK 22.07, N5095, I225-V) To: F32 Cc: Stephen Hemminger , users@dpdk.org, "Guo, Junfeng" , simei , "Mah, Yock Gen" , samuel.taripin@intel.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Tue, Oct 4, 2022 at 8:33 AM F32 wrote: > > Thanks for the suggestion. > > I took half an hour to add debug logs layer by layer and finally I came t= o igc_init_phy_params_i225 in drivers/net/igc/base/igc_i225.c. > > There is a piece of code that looks like this in the function: > > > /* Verify phy id and set remaining function pointers */ > > switch (phy->id) { > > case I225_I_PHY_ID: > > case I226_LM_PHY_ID: > > phy->type =3D igc_phy_i225; > > phy->ops.set_d0_lplu_state =3D igc_set_d0_lplu_state_i225; > > phy->ops.set_d3_lplu_state =3D igc_set_d3_lplu_state_i225; > > /* TODO - complete with GPY PHY information */ > > break; > > default: > > ret_val =3D -IGC_ERR_PHY; > > goto out; > > } > > The supported I225 model is I225_I with PHY_ID 0x67C9DC00, but the adapte= rs on my Mini-PC are I225_V with PHY_ID 0x67C9DCC0. > After adding the case l2fwd is now working. A recent change in this area of the driver got merged in next-net-intel. c493e5ee25fe ("net/igc: remove unncessary PHY ID checking") Cc: igc maintainers and authors of the change > > BTW, I noticed that there are so many different cases (in different sourc= e files) which might generate the "Requested device xxx cannot be used" err= or. Introducing a standard error code may be hellpful for ordinary dpdk use= rs, but it requires lots of work. I don't see how this is feasible to standardize error codes that would help here. The less awful is to get debug log messages, which is the driver responsibi= lity. --=20 David Marchand