From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 23656C48BDF for ; Thu, 24 Jun 2021 07:07:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F2D4A613D3 for ; Thu, 24 Jun 2021 07:07:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229454AbhFXHJD (ORCPT ); Thu, 24 Jun 2021 03:09:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55924 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231435AbhFXHIA (ORCPT ); Thu, 24 Jun 2021 03:08:00 -0400 Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DBBD2C061766 for ; Thu, 24 Jun 2021 00:05:41 -0700 (PDT) Received: by mail-qv1-xf2e.google.com with SMTP id x6so2800826qvx.4 for ; Thu, 24 Jun 2021 00:05:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=uyb2tZAPltFwu0/3f+8N1Whypmr/BCkiRPdpo/+aATQ=; b=1k4BwsViMRanh9l3pCxYXbVk+Oyx377MNyaN+A7H1GoOF1uRYXQGng5Of4MMTa9UU3 vORjZS6xeUVPxvspcQ+l+7w1fTkM0/00RGXBi45WRT5KU/9WAV/KPULzqMKBijts9khK F/lF/vsX/G4rPWOQsLPLocaEyCyCWwzGBf8kLIPp+hHU3hyhLJl3VUbudhMPApe30AUw RCSulmDgTqH92L5VXwVSOkzK+czifbqwhrLaP/jTRp1bG/lKc1y127f3Ieh+WAUpA4nc IaehzvKKDdPzLdpQu/ioAXIcbwjbMwFLZwax+0y3VVLjhiGZ1wN5ESUfl8EJFlxVCzcG c9lQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=uyb2tZAPltFwu0/3f+8N1Whypmr/BCkiRPdpo/+aATQ=; b=Y5knHHReyOWV/zD2n7xd/cR8pJiJ7lov4/kb357QThzINvQPcKLCCgvjuVyKfMdU/1 QvKny34I/ftEhaPRQOADw5PAIYJVwl/00kI/o9mXHVzDHx1XoLT0fXTDd4aMighLkq5X t/roVvNruoUy9FvF8JAOk5KcetUXQKvmNFZbeZ62KOglr3KjKonOHca23+dTTDSP3Ro0 jr3+HHumZzE4pJ7QK2c1PtsPTXch3+vv79YAH9IW4SP/MgOBW4h0nfWwyruVqWOYhN1E 3sgiChGoELMdasq5Xil9DUhGm7hMPnzf+CSjwAk/GSQtPXMnrxZ33Z19SX1gs5o5d3sn mF0A== X-Gm-Message-State: AOAM532/eWBaZarjM3P4ef6kHhr+azA8iEYchyorBWb2b6vTq1sdUguX Bjz93GWwyoJth71nKchMd3q6d8I8C8ZSCuZ8Yzvtrg7sk74= X-Google-Smtp-Source: ABdhPJyGJSZUCvOO+Zj3YeyJ93PvQJ+8PxOIr1FJk6NHef4t2hFw140HmPxZ6bPSrcxq2Ngz0CZqAkTIcWAnx9n6EWM= X-Received: by 2002:a05:6214:a0f:: with SMTP id dw15mr4071409qvb.10.1624518340902; Thu, 24 Jun 2021 00:05:40 -0700 (PDT) MIME-Version: 1.0 References: <20210624082911.5d013e8c@canb.auug.org.au> In-Reply-To: From: Marcin Wojtas Date: Thu, 24 Jun 2021 09:05:28 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the net-next tree To: Naresh Kamboju Cc: Stephen Rothwell , David Miller , Networking , Linux Kernel Mailing List , Linux Next Mailing List , Nathan Chancellor , lkft-triage@lists.linaro.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi All, czw., 24 cze 2021 o 08:13 Naresh Kamboju napisa= =C5=82(a): > > Hi Marcin, > > On Thu, 24 Jun 2021 at 07:59, Nathan Chancellor wrote= : > > > > On Thu, Jun 24, 2021 at 12:46:48AM +0200, Marcin Wojtas wrote: > > > Hi Stephen, > > > > > > czw., 24 cze 2021 o 00:29 Stephen Rothwell nap= isa=C5=82(a): > > > > > > > > Hi all, > > > > > > > > Today's linux-next build (x86_64 modules_install) failed like this: > > > > > > > > depmod: ../tools/depmod.c:1792: depmod_report_cycles_from_root: Ass= ertion `is < stack_size' failed. > > LKFT test farm found this build error. > > Regressions found on mips: > > - build/gcc-9-malta_defconfig > - build/gcc-10-malta_defconfig > - build/gcc-8-malta_defconfig > > depmod: ERROR: Cycle detected: fwnode_mdio -> of_mdio -> fwnode_mdio > depmod: ERROR: Found 2 modules in dependency cycles! > make[1]: *** [/builds/linux/Makefile:1875: modules_install] Error 1 > > > > Thank you for letting us know. Not sure if related, but I just found > > > out that this code won't compile for the !CONFIG_FWNODE_MDIO. Below > > > one-liner fixes it: > > > > > > --- a/include/linux/fwnode_mdio.h > > > +++ b/include/linux/fwnode_mdio.h > > > @@ -40,7 +40,7 @@ static inline int fwnode_mdiobus_register(struct mi= i_bus *bus, > > > * This way, we don't have to keep compat bits around in driv= ers. > > > */ > > > > > > - return mdiobus_register(mdio); > > > + return mdiobus_register(bus); > > > } > > > #endif > > > > > > I'm curious if this is the case. Tomorrow I'll resubmit with above, s= o > > > I'd appreciate recheck. > > This proposed fix did not work. > > > Reverting all the patches in that series fixes the issue for me. > > Yes. > Reverting all the (6) patches in that series fixed this build problem. > > git log --oneline | head > 3752a7bfe73e Revert "Documentation: ACPI: DSD: describe additional MAC > configuration" > da53528ed548 Revert "net: mdiobus: Introduce fwnode_mdbiobus_register()" > 479b72ae8b68 Revert "net/fsl: switch to fwnode_mdiobus_register" > 92f85677aff4 Revert "net: mvmdio: add ACPI support" > 3d725ff0f271 Revert "net: mvpp2: enable using phylink with ACPI" > ffa8c267d44e Revert "net: mvpp2: remove unused 'has_phy' field" > d61c8b66c840 Add linux-next specific files for 20210623 > > steps to reproduce, config and build log located here in this link, > https://builds.tuxbuild.com/1uNjGjPUAI4XwwcwKFr5FUxkwzy/ > Thank you for your reports. I'm currently trying to reproduce and come back with a fix asap. Best regards, Marcin > > # TuxMake is a command line tool and Python library that provides > # portable and repeatable Linux kernel builds across a variety of > # architectures, toolchains, kernel configurations, and make targets. > # > # TuxMake supports the concept of runtimes. > # See https://docs.tuxmake.org/runtimes/, for that to work it requires > # that you install podman or docker on your system. > # > # To install tuxmake on your system globally: > # sudo pip3 install -U tuxmake > # > # See https://docs.tuxmake.org/ for complete documentation. > > > tuxmake --runtime podman --target-arch mips --toolchain gcc-10 > --kconfig malta_defconfig > > > - Naresh