Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

depmod is failing even though build was successful #912

Open
musamaanjum opened this issue Nov 26, 2024 · 1 comment
Open

depmod is failing even though build was successful #912

musamaanjum opened this issue Nov 26, 2024 · 1 comment
Assignees
@musamaanjum

Comments

@musamaanjum
Copy link
Contributor

musamaanjum commented Nov 26, 2024 •
edited
Loading

The depmod is failing on 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 may be an issue with the upstream code.
@musamaanjum musamaanjum self-assigned this Nov 26, 2024
@musamaanjum musamaanjum converted this from a draft issue Nov 26, 2024
@musamaanjum musamaanjum changed the title kselftests build failures are poluting kernel build results depmod is failing even though build was successful Nov 26, 2024
@musamaanjum
Copy link
Contributor Author

Reported: https://lore.kernel.org/all/[email protected]

cc: @laura-nao JFYI the failure is also present on x86 in allmodconfig.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@musamaanjum musamaanjum

Labels
None yet
Projects
KernelCI results data evaluation
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@musamaanjum