mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <Usama.Anjum@collabora.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Usama.Anjum@collabora.com
Subject: [Bug Report] Depmod is failing on allmodconfig for arm64 and x86_64
Date: Tue, 26 Nov 2024 18:25:44 +0500	[thread overview]
Message-ID: <91c041ac-5491-4c97-9afc-9eb11c8e686c@collabora.com> (raw)

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. 

[1] https://kcidb.kernelci.org/d/build/build?orgId=1&var-datasource=default&var-build_architecture=arm64&var-build_config_name=defconfig+allmodconfig&var-id=maestro:67427d2a923416c0c993033a
[2] https://kcidb.kernelci.org/d/build/build?orgId=1&var-datasource=default&var-build_architecture=x86_64&var-build_config_name=x86_64_defconfig%20allmodconfig&var-id=maestro:67427d2c923416c0c9930358&from=now-100y&to=now&timezone=browser&var-origin=$__all&var-test_path=&var-issue_presence=yes

-- 
BR,
Muhammad Usama Anjum

             reply	other threads:[~2024-11-26 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 13:25 Muhammad Usama Anjum [this message]
2024-11-27 12:26 ` Will Deacon
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=91c041ac-5491-4c97-9afc-9eb11c8e686c@collabora.com \
    --to=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®