From: Will Deacon <will@kernel.org>
To: Muhammad Usama Anjum <Usama.Anjum@collabora.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bug Report] Depmod is failing on allmodconfig for arm64 and x86_64
Date: Wed, 27 Nov 2024 12:26:03 +0000 [thread overview]
Message-ID: <20241127122602.GA2530@willie-the-truck> (raw)
In-Reply-To: <91c041ac-5491-4c97-9afc-9eb11c8e686c@collabora.com>
On Tue, Nov 26, 2024 at 06:25:44PM +0500, Muhammad Usama Anjum wrote:
> Hi,
>
> The depmod is failing on 9f16d5e6f2206 (mainline) arm64 and x86_64 because of:
> ```
> depmod: ERROR: Cycle detected: libphy
>
> depmod: ERROR: Cycle detected: lan969x_switch -> sparx5_switch -> lan969x_switch
> depmod: ERROR: Cycle detected: ptp
> depmod: ERROR: Cycle detected: stp
> depmod: ERROR: Cycle detected: ipv6
> depmod: ERROR: Cycle detected: bridge
> depmod: ERROR: Found 2 modules in dependency cycles!
> make[2]: *** [scripts/Makefile.modinst:132: depmod] Error 1
> make[1]: *** [/tmp/kci/linux/Makefile:1844: modules_install] Error 2
> make: *** [Makefile:224: __sub-make] Error 2
> ```
>
> This issue wasn't present until c66fbc6c3df9.
$ git show c66fbc6c3df9
commit c66fbc6c3df9ccefbb896695cfc4db279d517ff1
Merge: f103749785a7 1037d186edfc
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed Nov 20 14:56:02 2024 -0800
Merge tag 'for-linus' of https://github.com/openrisc/linux
Pull OpenRISC update from Stafford Horne:
"A single fixup from me: Fix bug with earlycon being broken due to
removal of early_ioremap"
* tag 'for-linus' of https://github.com/openrisc/linux:
openrisc: Implement fixmap to fix earlycon
Are you sure?
Will
next prev parent reply other threads:[~2024-11-27 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 13:25 Muhammad Usama Anjum
2024-11-27 12:26 ` Will Deacon [this message]
2024-11-27 12:47 ` Muhammad Usama Anjum
2024-12-02 16:26 ` Calvin Owens
2024-12-03 12:48 ` Daniel Machon
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=20241127122602.GA2530@willie-the-truck \
--to=will@kernel.org \
--cc=Usama.Anjum@collabora.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
all inboxes | Powered by JetHome®