From: root <root@ohlone.ucsc.edu>
To: linux-kernel@vger.kernel.org
Subject: net-pf-10, 2.6.1
Date: Fri, 30 Jan 2004 00:36:28 -0800 [thread overview]
Message-ID: <E1AmU8a-00005E-00@localhost> (raw)
Since compiling and installing 2.6.1, I, like many others, get these
repeated error messages:
----------------------------------------------------------------------
Jan 29 22:48:56 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 29 22:53:01 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 29 22:56:28 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 29 23:08:01 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 29 23:14:48 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 29 23:23:01 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 29 23:31:40 kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
----------------------------------------------------------------------
I do not have ipv6 support in my kernel-config:
# CONFIG_INET_IPCOMP is not set
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
The version of module-init-tools is 3.0-pre5-1 from Debian testing.
Is there any guidance about this little annoyance yet? Most of the
advice I've seen (on other lists) suggests putting the following in
modprobe.conf:
install net-pf-10 /bin/true
But this has made no difference for me.
There seems to be a correlation between the issue of the error-message
and regular exim runs:
Jan 29 22:53:01 ohlone /USR/SBIN/CRON[284]: (mail) CMD ( if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib
/exim/exim3 -q ; fi)
Jan 29 22:53:01 ohlone kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Jan 30 00:23:01 ohlone /USR/SBIN/CRON[311]: (mail) CMD ( if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi)
Jan 30 00:23:01 ohlone kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256
Almost all of the error messages from modprobe come exactly on the
heels of a call from cron to run exim. But why should exim spawn an
attempt to load this module? And why just with kernel 2.6.1?
Thanks for any advice,
Jim
next reply other threads:[~2004-01-30 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 8:36 root [this message]
2004-01-30 8:51 ` net-pf-10, 2.6.1 Russell King
2004-01-31 17:00 ` Greg Norris
[not found] ` <Pine.LNX.4.44.0401301532260.9270-100000@gaia.cela.pl>
2004-01-31 23:35 ` Jim McCloskey
2004-02-01 2:21 ` Steve Youngs
-- strict thread matches above, loose matches on Subject: below --
2004-02-01 9:28 Jim McCloskey
2004-02-01 9:46 ` Kiko Piris
2004-02-01 20:31 ` Jim McCloskey
2004-02-01 9:59 ` Russell King
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=E1AmU8a-00005E-00@localhost \
--to=root@ohlone.ucsc.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