From owner-freebsd-stable  Wed Oct 25  7:24:50 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from unto.eziba.com (unto.eziba.com [64.80.31.106])
	by hub.freebsd.org (Postfix) with ESMTP id 9BA3937B479
	for <freebsd-stable@FreeBSD.ORG>; Wed, 25 Oct 2000 07:24:47 -0700 (PDT)
Received: from avacet.com (thelonius.eziba.com [192.168.0.31])
	by unto.eziba.com (8.9.3/8.8.7) with ESMTP id KAA24188;
	Wed, 25 Oct 2000 10:27:07 -0400
Message-ID: <39F6ED29.6497A26A@avacet.com>
Date: Wed, 25 Oct 2000 10:24:41 -0400
From: Jay Sachs <jay@avacet.com>
X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: module_register/linker_file_sysinit messages
References: <20001024205317.A20261@staub.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Phil Staub wrote:
> 
> After a fresh install of 4.1R followed by building/installing a new
> kernel, I now get numerous messages of the following form upon boot:
> 
> module_register: module miibus/xmphy already exists!
> linker_file_sysinit "miibus.ko" failed to register! 17
> 
> Could someone point me to the meaning and resolution of this? It's not
> obvious from manpages, handbook or faq (or at least my searches came
> up empty). I also did a little poking around in the config files in
> /boot. The closest thing I could find was an entry in
> /boot/defaults/loader.conf that said:
> 
> miibus_load="NO"                # miibus support, needed for some drivers
> 
> Should this say "YES"? I'm running ed and xl drivers.
> 
> Thanks,
> Phil

As a possibly related "me-too", I get this console message as PPPoE
starts up. I have NETGRAPH, NETGRAPH_PPP and NETGRAPH_PPPOE options set
in the kernel config, but as soon as ppp makes the connection, I get an
equivalent message, but related to the negraph.ko module.  Things
function normally though. 

In sys/kern/kern_module.c, I see 

	/* temporary kludge until kernel `file' attachment registers modules */
	error = module_register(data, linker_kernel_file);
	if (error)
	    panic("module_register_init: register of module failed! %d",
error);
	mod = module_lookupbyname(data->name);
	if (mod == NULL)
	    panic("module_register_init: module STILL not found!");

If it's a hack, why not make it a friendlier hack and special-case a
return of EEXIST from module_register()? Either print a different
message, or no message at all, perhaps.

jay


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message