From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jeremyhu@uclink4.berkeley.edu (Jeremy Huddleston),
linux-kernel@vger.kernel.org
Subject: Re: Problem with module versioning in 2.4.0
Date: Thu, 11 Jan 2001 11:37:14 +1100 [thread overview]
Message-ID: <7595.979173434@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 11 Jan 2001 00:17:41 -0000." <E14GVR1-0001J9-00@the-village.bc.nu>
On Thu, 11 Jan 2001 00:17:41 +0000 (GMT),
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>jeremyhu wrote
>> See below for my origional problem. It seems the problem lies in the
>> module versioning option.
>
>Not quite
Probably is.
>> When the system boots, I am spammed with the following line:
>> insmod: /lib/modules/2.4.0/kernel/net/unix/unix.o: insmod net-pf-1
>> failed
>
>What happens is this
>
>kernel needs unix sockets
>kernel invokes modprobe
>modprobe opens a unix socket
> kernel needs unix sockets
> kernel invokes modprobe
> .....
kmod.c has code to catch that recursive case and abort it. The problem
is not the loop per se, it is caused by that insmod unix.o failing on
every attempt. That is almost certainly caused by bad symbol versions.
See http://www.tux.org/lkml/#s8-8.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-11 0:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 23:26 Jeremy Huddleston
2001-01-11 0:17 ` Alan Cox
2001-01-11 0:28 ` Jeremy Huddleston
2001-01-11 0:29 ` Alan Cox
2001-01-11 0:54 ` Mike A. Harris
2001-01-11 0:37 ` Keith Owens [this message]
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=7595.979173434@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeremyhu@uclink4.berkeley.edu \
--cc=linux-kernel@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
Powered by JetHome