public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.7 and runaway modprobe loop?
Date: Wed, 10 Apr 2002 16:51:48 +1000	[thread overview]
Message-ID: <4002.1018421508@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 09 Apr 2002 09:17:08 MST." <Pine.LNX.4.33L2.0204090912540.22258-100000@dragon.pdx.osdl.net>

On Tue, 9 Apr 2002 09:17:08 -0700 (PDT), 
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
>If I build/boot 2.5.7 with 64 GB support (with or without
>high_pte), I get:
>
>Freeing unused kernel memory: 448k freed
>INIT: version 2.78 booting
>kmod: runaway modprobe loop assumed and stopped
>kmod: runaway modprobe loop assumed and stopped
>kmod: runaway modprobe loop assumed and stopped
>kmod: runaway modprobe loop assumed and stopped
>kmod: runaway modprobe loop assumed and stopped
>
>If I build/boot it with 4 GB support, it boots fine.
>
>Fixes, suggestion?

If /var/log/ksymoops exists and is mounted rw when that message is
issued, look at 20020409.log to see what modprobe is asking for.
Otherwise add a printk to kernel/kmod::request_module() to print
module_name.  In either case, work out why it is going recursive.


  reply	other threads:[~2002-04-10  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 16:17 2.5.7 and runaway modprobe loop? Randy.Dunlap
2002-04-10  6:51 ` Keith Owens [this message]
2002-04-10 18:00   ` Randy.Dunlap
2002-04-10 23:27     ` Keith Owens

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=4002.1018421508@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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