LKM 'pf': environment compile options mismatch - LKM '', kernel 'DEBUG,DIAGNOSTIC'

I have been using a xen service for a few weeks. I was using
PF and spamd. 
spamd was definitely working according to my logs.

Some upgrade was done by my Xen provider. I know nothing
about the domain0 
but I think it is running NetBSD.

I have:

# uname -mrsv
NetBSD 3.0 NetBSD 3.0 (XENU) #0: Mon Dec 19 01:30:48 UTC
2005  
buildsworks.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i
386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/
sys/arch/i386/compile/XENU 
i386

# ls -l /usr/lkm/pf.o
-r--r--r--  1 root  wheel  176613 Dec 18  2005 /usr/lkm/pf.o

When I attempt to load the module I get:

# /sbin/modload /usr/lkm/pf.o
modload: error initializing module: Program version wrong

And /var/log/messages has:

Jul 19 04:41:09 ca /netbsd: LKM 'pf': environment compile
options mismatch 
- LKM '', kernel 'DEBUG,DIAGNOSTIC'

Anyone else have this problem?

I tried using modload -f before, but I think it locked up my
system. I 
could not tell at that time because my console IP was
changed. And I don't 
want to try again just in case I can't recover.

- Jeremy C. Reed

ps. Please carbon-copy me on replies.

Hi Jeremy[1],


On Wed, Jul 19, 2006 at 07:00:10AM -0500, reedreedmedia.net wrote:
> Some upgrade was done by my Xen provider. I know
nothing about the domain0 
> but I think it is running NetBSD.

they probably updated the kernel You are running (might be
very 
much different from the one in Your /
It seems Your userland has gotten out of sync with the
kernel now,
ask them which exact kernel they are using - probably a
snapshot kernel?
or it might be the other way round - maybe they switch to a
stable xen3
kernel and You still (of course) have a -current userland.

> When I attempt to load the module I get:
> 
> # /sbin/modload /usr/lkm/pf.o
> modload: error initializing module: Program version
wrong
> 
> And /var/log/messages has:
> 
> Jul 19 04:41:09 ca /netbsd: LKM 'pf': environment
compile options mismatch 
> - LKM '', kernel 'DEBUG,DIAGNOSTIC'

seems more like a snapshot kernel to me, still only the
provider can 
put insight to this.

florian

[1] how come YOU are using pf? 

-- 

florian heigl			 http://deranfangvomen.de/
"ja, ja, ja, ja, ja, oh, oh, oh, oh scheise. oh. oh
fuck."
 -- the sound of a leased line multiplexer failing for the
second time 
    just after things looked ok again (via a workmate at the
phone)

Hi Jeremy[1],


On Wed, Jul 19, 2006 at 07:00:10AM -0500, reedreedmedia.net wrote:
> Some upgrade was done by my Xen provider. I know
nothing about the domain0 
> but I think it is running NetBSD.

they probably updated the kernel You are running (might be
very 
much different from the one in Your /
It seems Your userland has gotten out of sync with the
kernel now,
ask them which exact kernel they are using - probably a
snapshot kernel?
or it might be the other way round - maybe they switch to a
stable xen3
kernel and You still (of course) have a -current userland.

> When I attempt to load the module I get:
> 
> # /sbin/modload /usr/lkm/pf.o
> modload: error initializing module: Program version
wrong
> 
> And /var/log/messages has:
> 
> Jul 19 04:41:09 ca /netbsd: LKM 'pf': environment
compile options mismatch 
> - LKM '', kernel 'DEBUG,DIAGNOSTIC'

seems more like a snapshot kernel to me, still only the
provider can 
put insight to this.

florian

[1] how come YOU are using pf? 

-- 

florian heigl			 http://deranfangvomen.de/
"ja, ja, ja, ja, ja, oh, oh, oh, oh scheise. oh. oh
fuck."
 -- the sound of a leased line multiplexer failing for the
second time 
    just after things looked ok again (via a workmate at the
phone)

Hi Jeremy[1],


On Wed, Jul 19, 2006 at 07:00:10AM -0500, reedreedmedia.net wrote:
> Some upgrade was done by my Xen provider. I know
nothing about the domain0 
> but I think it is running NetBSD.

they probably updated the kernel You are running (might be
very 
much different from the one in Your /
It seems Your userland has gotten out of sync with the
kernel now,
ask them which exact kernel they are using - probably a
snapshot kernel?
or it might be the other way round - maybe they switch to a
stable xen3
kernel and You still (of course) have a -current userland.

> When I attempt to load the module I get:
> 
> # /sbin/modload /usr/lkm/pf.o
> modload: error initializing module: Program version
wrong
> 
> And /var/log/messages has:
> 
> Jul 19 04:41:09 ca /netbsd: LKM 'pf': environment
compile options mismatch 
> - LKM '', kernel 'DEBUG,DIAGNOSTIC'

seems more like a snapshot kernel to me, still only the
provider can 
put insight to this.

florian

[1] how come YOU are using pf? 

-- 

florian heigl			 http://deranfangvomen.de/
"ja, ja, ja, ja, ja, oh, oh, oh, oh scheise. oh. oh
fuck."
 -- the sound of a leased line multiplexer failing for the
second time 
    just after things looked ok again (via a workmate at the
phone)

Hi Jeremy[1],


On Wed, Jul 19, 2006 at 07:00:10AM -0500, reedreedmedia.net wrote:
> Some upgrade was done by my Xen provider. I know
nothing about the domain0 
> but I think it is running NetBSD.

they probably updated the kernel You are running (might be
very 
much different from the one in Your /
It seems Your userland has gotten out of sync with the
kernel now,
ask them which exact kernel they are using - probably a
snapshot kernel?
or it might be the other way round - maybe they switch to a
stable xen3
kernel and You still (of course) have a -current userland.

> When I attempt to load the module I get:
> 
> # /sbin/modload /usr/lkm/pf.o
> modload: error initializing module: Program version
wrong
> 
> And /var/log/messages has:
> 
> Jul 19 04:41:09 ca /netbsd: LKM 'pf': environment
compile options mismatch 
> - LKM '', kernel 'DEBUG,DIAGNOSTIC'

seems more like a snapshot kernel to me, still only the
provider can 
put insight to this.

florian

[1] how come YOU are using pf? 

-- 

florian heigl			 http://deranfangvomen.de/
"ja, ja, ja, ja, ja, oh, oh, oh, oh scheise. oh. oh
fuck."
 -- the sound of a leased line multiplexer failing for the
second time 
    just after things looked ok again (via a workmate at the
phone)