linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can't build IDE as modules in BK 2.5.69
Date: Tue, 13 May 2003 14:55:23 +1000	[thread overview]
Message-ID: <20030513073453.480DD2C240@lists.samba.org> (raw)
In-Reply-To: Your message of "Tue, 13 May 2003 13:44:12 +1000." <16064.27148.819310.962984@wombat.chubb.wattle.id.au>

In message <16064.27148.819310.962984@wombat.chubb.wattle.id.au> you write:
> 
> With the 2.5 bk linux as of 2003.05.13, and config options below,
> modutils seems to go into a seemingly infinite loop when trying to
> buld modules.dep on the resulting module set (and creates an extremely
> large modules.dep file -- 95M before the filesystem filled up)

Grrr... I thought that was fixed.  What version of depmod you using
(depmod -V).

Real problem is actual dependency loop in IDE modules, but depmod
should just report that and ignore the modules involved.

> WARNING: Module /lib/modules/2.5.69/kernel/drivers/scsi/ide-scsi.ko
> ignored, due to loop
> WARNING: Module /lib/modules/2.5.69/kernel/drivers/ide/pci/piix.ko
> ignored, due to loop
> WARNING: Module /lib/modules/2.5.69/kernel/drivers/ide/ide.ko ignored,
> due to loop
> WARNING: Module /lib/modules/2.5.69/kernel/drivers/ide/ide-taskfile.ko
> ignored, due to loop
> WARNING: Module /lib/modules/2.5.69/kernel/drivers/ide/ide-probe.ko
> ignored, due to loop

Thanks for the report,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2003-05-13  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  3:44 can't build IDE as modules in BK 2.5.69 Peter Chubb
2003-05-13  4:55 ` Rusty Russell [this message]
2003-05-13  5:45 ` Rusty Russell

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=20030513073453.480DD2C240@lists.samba.org \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@chubb.wattle.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).