Skip to contentSkip to conversation

net-pf-10, 2.6.1

DISCUSSION root 5 participants 5 messages Jan 30, 2004 – Feb 1, 2004 1 message not in the archive

lore
Share & tools
lore

root

author
#0 lore 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

#1 lore raw
Quoted 5 lines · root

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

You want:

alias net-pf-10 off

Quoted 3 lines

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?

Because its trying to see if the kernel supports IPv6 by creating an IPv6 socket. Since the IPv6 module is not available, it correctly fails and uses IPv4 instead.

Signature · 4 lines
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core
#2 lore raw
In reply to root
Quoted 7 lines · root

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.

Did you run "update-modules" afterward?

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw

* Russell King ([email protected]) wrote:

  |>  On Fri, Jan 30, 2004 at 12:36:28AM -0800, jim wrote: 
  |>  > 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          
  |>                                    
  |>  You want:  
  |>                         
  |>    alias net-pf-10 off     

* Maciej Zenczykowski <[email protected]> wrote:

  |> try   
  |>              
  |> "alias net-pf-10 off" in /etc/modules.conf 

* Greg Norris wrote:

|> Did you run "update-modules" afterward?

Thank you all for helping. I'm sorry I didn't make clear initially that this (aliasing net-pf-10 to off) was the first thing I tried. I resorted to Google when it didn't work. I've tried it again but the error-messages continue. /lib/modules/modprobe.conf now has:

-rw-r--r-- 1 root root 7341 Jan 30 15:26 modprobe.conf

   alias net-pf-1  unix
   alias net-pf-2  ipv4
   alias net-pf-3  ax25
   alias net-pf-4  ipx
   alias net-pf-5  appletalk
   alias net-pf-6  netrom
   alias net-pf-7  bridge
   alias net-pf-8  atm
   alias net-pf-9  x25

alias net-pf-10 off
alias net-pf-11 rose
alias net-pf-12 decnet

and contains no other reference to net-pf-10. But still:

Jan 31 14:53:01 ohlone /USR/SBIN/CRON[1092]: (mail) CMD (  if [ -x /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then /usr/lib/exim/exim3 -q ; fi)
Jan 31 14:53:01 ohlone kernel: request_module: failed /sbin/modprobe -- net-pf-10. error = 256

for every time exim runs.

Others have reported the same effect, e.g:

http://linuxfromscratch.org/pipermail/lfs-hackers/2004-January/000297.html

This didn't happen in 2.6.0 (or earlier).

This is a very small problem indeed, of course. It's just weird ...

Jim

#5 lore raw
Quoted 1 line · Jim McCloskey

|> > install net-pf-10 /bin/true

This _is_ what you want in your modprobe.conf file. Or possibly `install net-pf-10-* /bin/true', but I'm pretty sure that Rusty has added some backward compatibility code so that either _should_ work.

The other thing that you need to do once you have updated modprobe.conf is to run `depmod' to regenerate the dependency files.

Signature · 4 lines
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|              Ashes to ashes, dust to dust.               |
|      The proof of the pudding, is under the crust.       |
|------------------------------<[email protected]>---|