From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Alex Davis" <alex47794@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"John Ogness" <john.ogness@linutronix.de>,
linux-serial@vger.kernel.org
Subject: Re: [Regression] depmod fails on kernel 6.17.1 rc1
Date: Thu, 6 Nov 2025 18:15:57 +0200 [thread overview]
Message-ID: <aQzJveMYT6O3EHeK@smile.fi.intel.com> (raw)
In-Reply-To: <20251106160235.GBaQzGm8W2Gt_VMy-s@fat_crate.local>
On Thu, Nov 06, 2025 at 05:02:35PM +0100, Borislav Petkov wrote:
> Lemme add a whole bunch of relevant ppl to Cc.
Thanks!
> So I'm seeing this with an allmodconfig build too:
>
> depmod: ERROR: Cycle detected: 8250 -> 8250_base -> 8250
> depmod: ERROR: Found 2 modules in dependency cycles!
I'm surprised it took so long to people to start complaining.
So, some of those are modules? Can you share the
grep 8250 .config
part?
> make[6]: *** [scripts/Makefile.modinst:132: depmod] Error 1
> make[5]: *** [Makefile:1917: modules_install] Error 2
> make[4]: *** [Makefile:2140: run-command] Error 2
> make[3]: *** [debian/rules:66: binary-image] Error 2
> dpkg-buildpackage: error: make -f debian/rules binary subprocess returned exit status 2
> make[2]: *** [scripts/Makefile.package:126: bindeb-pkg] Error 2
> make[1]: *** [/home/amd/kernel/linux/Makefile:1643: bindeb-pkg] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
>
> That's 6.17.7
>
> On Sun, Oct 05, 2025 at 09:40:28PM -0400, Alex Davis wrote:
> > When running make modules_install on linux 6.17. with the attached
> > .config, I get the following error:
> >
> > DEPMOD /lib/modules/6.17.1-rc1
> > depmod: ERROR: Cycle detected: 8250 -> 8250_base -> 8250
> > depmod: ERROR: Cycle detected: serial_mctrl_gpio
> > depmod: ERROR: Found 2 modules in dependency cycles!
> > make[2]: *** [scripts/Makefile.modinst:132: depmod] Error 1
> > make[1]: *** [/spare/linux/linux-6.17/Makefile:1917: modules_install] Error 2
> > make: *** [Makefile:248: __sub-make] Error 2
> >
> > This also happens with 6.17; it does not happen with 6.16.x.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-06 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADiockCvM6v+d+UoFZpJSMoLAdpy99_h-hJdzUsdfaWGn3W7-g@mail.gmail.com>
2025-11-06 16:02 ` [Regression] depmod fails on kernel 6.17.1 rc1 Borislav Petkov
2025-11-06 16:15 ` Andy Shevchenko [this message]
2025-11-06 16:24 ` Borislav Petkov
2025-11-06 16:35 ` Ilpo Järvinen
2025-11-06 18:00 ` Ilpo Järvinen
2025-11-06 18:14 ` Andy Shevchenko
2025-11-07 8:17 ` Andy Shevchenko
2025-11-07 9:40 ` Ilpo Järvinen
2025-11-07 6:20 ` Jiri Slaby
2025-11-08 13:32 ` Borislav Petkov
2025-11-08 23:52 ` Stephen Rothwell
2025-11-09 0:49 ` Greg Kroah-Hartman
2025-11-09 6:34 ` Stephen Rothwell
2025-11-10 10:43 ` Ilpo Järvinen
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=aQzJveMYT6O3EHeK@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alex47794@gmail.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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