I have a secondary suse 9.0-box where the following "modprobe :can't locate module xp0" occures.

I'm suspecting this resulting in another problem we have regarding creating "lock-files" on a NFS-mounted filesystem:
"Locking failed on survey.linesLocking failed on survey.lines"


cut from boot.msg-file:

Master Resource Control: previous runlevel: N, switching to runlevel: 5
<notice>start services (simrad.server random isdn)
Initializing random number generatordone
<notice>exit status of (simrad.server random isdn) is (0 0 0)
<notice>start services (cfloor.server)
<notice>exit status of (cfloor.server) is (0)
<notice>start services (network)
Setting up network interfaces:
lo modprobe: modprobe: Can't locate module xp0

done
modprobe: modprobe: Can't locate module xp0

<notice>exit status of (network) is (0)
<notice>start services (syslog)
Starting syslog services<notice>startproc: execve (/sbin/syslogd) [ /sbin/syslogd ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=21 INIT_VERSION=sysvinit-
2.82 REDIRECT=/dev/tty1 AUTOBOOT=YES COLUMNS=148 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=51 HOME=/ SHLVL=2 BOOT_IMAGE=Lin
ux splash=silent sscripts=43 _=/sbin/startproc DAEMON=/sbin/syslogd ]
modprobe: modprobe: Can't locate module xp0

modprobe: modprobe: Can't locate module xp0

<notice>startproc: execve (/sbin/klogd) [ /sbin/klogd -c 1 -2 ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=21 INIT_VERSION=sysvinit-2.82 REDIRECT=/dev/t
ty1 AUTOBOOT=YES COLUMNS=148 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=51 HOME=/ SHLVL=2 BOOT_IMAGE=Linux splash=silent ssc
ripts=43 _=/sbin/startproc DAEMON=/sbin/klogd ]
done

The loading works fine when booting in safemode

ppl.
problem solved and it had nothing to do with xp0..
it was a easy fix.. the nfslockdaemon was not starting/running on boot.

as soon as that was started at boot, the problem was no more.