All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eva Rachel Retuya <eraretuya@gmail.com>
To: outreachy-kernel@googlegroups.com
Subject: depmod: modules in dependency cycles
Date: Thu, 29 Oct 2015 17:40:10 +0800	[thread overview]
Message-ID: <20151029094006.GA15647@Socrates-Mint> (raw)

Hi,

After successfully finishing a few patches and rebasing my branch to
obtain the latest updates, I have run into this problem that keeps me
from updating my kernel and therefore won't let me test patch/es I
intend to send.

A snippet of my "failed" installation can be found here:
http://pastebin.com/8WzV1Ayn

I'd like to ask for help as to how to resolve this issue. My searches so
far did not yield enough information for me to successfully solve this
on my own. What I am doing lately was to boot to my stable kernel
(3.16.0-38), copy its config to .config as directed from the tutorial. Compile the kernel and install (sudo make modules_install install). The end result are as indicated on the pastebin link. Even booting from my last-known working "latest" kernel (rc5) yields the same result.

I reviewed the config and the lustre components were selected as
modules. It worked without a hitch before so I'm puzzled as to why the
said modules are in dependency cycles now. I also did "make clean" and
recompiled from scratch, still no dice.

Thank you in advance,
Eva


             reply	other threads:[~2015-10-29  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  9:40 Eva Rachel Retuya [this message]
2015-10-29 14:41 ` [Outreachy kernel] depmod: modules in dependency cycles Julia Lawall
2015-10-30  6:41   ` Eva Rachel Retuya
2015-10-30  6:59     ` Sudip Mukherjee
2015-10-30 14:49       ` Eva Rachel Retuya
     [not found]     ` <alpine.DEB.2.02.1510300745180.2253@localhost6.localdomain6>
2015-10-30 14:47       ` Eva Rachel Retuya
2015-10-30 15:10         ` Julia Lawall

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=20151029094006.GA15647@Socrates-Mint \
    --to=eraretuya@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.