On Thursday 19 March 2009, maximilian attems wrote:
> copied over that file and saw still no sign of a trouble:
> mkinitramfs -v -o /tmp/foo | head -n 12

Here's the actual depmod command executed during a kernel build:
/sbin/depmod -ae -F System.map -b /home/fjp/projects/kernel/builds/amd64/debian/tmp 2.6.29-rc8-rjw
So, the (undocumented?) -r option is not there.

But even with the -r the commands I gave work for me to reproduce the
"broken" modules.dep file:
fjp@thorin:~$ apt-cache show module-init-tools | grep Version
Version: 3.7-pre9-1
fjp@thorin:~$ kvers=2.6.26.3
fjp@thorin:~$ mkdir -p /tmp/lib/modules
fjp@thorin:~$ cp -r /lib/modules/$kvers /tmp/lib/modules/
fjp@thorin:~$ rm /tmp/lib/modules/$kvers/modules.*
fjp@thorin:~$ sudo depmod -ae -F /boot/System.map-$kvers -b /tmp/ -r $kvers
fjp@thorin:~$ less /tmp/lib/modules/2.6.26.3/modules.dep
fjp@thorin:~$ grep ": .+" /tmp/lib/modules/2.6.26.3/modules.dep | head -n3
kernel/fs/cramfs/cramfs.ko: kernel/lib/zlib_inflate/zlib_inflate.ko
kernel/fs/hfs/hfs.ko: kernel/fs/nls/nls_base.ko
kernel/fs/nfs_common/nfs_acl.ko: kernel/net/sunrpc/sunrpc.ko

While for the original ("correct") modules.dep:
fjp@thorin:~$ grep ": .+" /lib/modules/2.6.26.3/modules.dep | head -n3
/lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/rpcsec_gss_spkm3.ko: /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko
/lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/rpcsec_gss_krb5.ko: /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko
/lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko: /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko

My hookscript does:
if [ -f /boot/initrd.img-$version ]; then
update-initramfs -u -k $version
else
update-initramfs -c -k $version
fi

Does 'update-initramfs -c' behave differently from mkinitramfs?

If I run update-initramfs (0.92o) with a "broken" modules.dep I get:
# update-initramfs -v -c -k 2.6.26.3 | head
update-initramfs: Generating /boot/initrd.img-2.6.26.3
Copying module directory kernel/drivers/ide
Copying module directory kernel/drivers/scsi
Copying module directory kernel/drivers/block
Copying module directory kernel/drivers/ata
Copying module directory kernel/drivers/mmc
Adding binary /usr/share/initramfs-tools/init
Adding binary /etc/initramfs-tools/initramfs.conf
Adding binary /usr/share/initramfs-tools/conf.d/uswsusp
Adding binary /etc/initramfs-tools/conf.d/resume
Adding binary /bin/busybox

# ls -l /boot/initrd.img-2.6.26.3*
-rw-r--r-- 1 root root 4139731 2009-03-19 18:42 /boot/initrd.img-2.6.26.3
-rw-r--r-- 1 root root 5537135 2008-08-22 02:58 /boot/initrd.img-2.6.26.3.sv



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thu, Mar 19, 2009 at 06:43:27PM +0100, Frans Pop wrote:
> fjp@thorin:~$ grep ": .+" /tmp/lib/modules/2.6.26.3/modules.dep | head -n3
> kernel/fs/cramfs/cramfs.ko: kernel/lib/zlib_inflate/zlib_inflate.ko
> kernel/fs/hfs/hfs.ko: kernel/fs/nls/nls_base.ko
> kernel/fs/nfs_common/nfs_acl.ko: kernel/net/sunrpc/sunrpc.ko
>
> While for the original ("correct") modules.dep:
> fjp@thorin:~$ grep ": .+" /lib/modules/2.6.26.3/modules.dep | head -n3
> /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/rpcsec_gss_spkm3.ko: /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko
> /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/rpcsec_gss_krb5.ko: /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko
> /lib/modules/2.6.26.3/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko: /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko

yep i see that difference too.

> My hookscript does:
> if [ -f /boot/initrd.img-$version ]; then
> update-initramfs -u -k $version
> else
> update-initramfs -c -k $version
> fi
>
> Does 'update-initramfs -c' behave differently from mkinitramfs?

no it is just the upperlayer call to mkinitramfs.

> If I run update-initramfs (0.92o) with a "broken" modules.dep I get:
> # update-initramfs -v -c -k 2.6.26.3 | head
> update-initramfs: Generating /boot/initrd.img-2.6.26.3
> Copying module directory kernel/drivers/ide
> Copying module directory kernel/drivers/scsi
> Copying module directory kernel/drivers/block
> Copying module directory kernel/drivers/ata
> Copying module directory kernel/drivers/mmc
> Adding binary /usr/share/initramfs-tools/init
> Adding binary /etc/initramfs-tools/initramfs.conf
> Adding binary /usr/share/initramfs-tools/conf.d/uswsusp
> Adding binary /etc/initramfs-tools/conf.d/resume
> Adding binary /bin/busybox

could you send the ouput of
sh -x mkinitramfs -o /tmp/foo 2.6.26.3





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Thursday 19 March 2009, maximilian attems wrote:
> On Thu, Mar 19, 2009 at 06:43:27PM +0100, Frans Pop wrote:
> could you send the ouput of
> sh -x mkinitramfs -o /tmp/foo 2.6.26.3

Attached.

Hmmm. I wonder if it is the old m-i-t's modprobe that is the problem when
you do:
modprobe --set-version=2.6.26.3 --ignore-install --show-depends <module>

Looks like that's it:
# modprobe -V
module-init-tools version 3.4
# modprobe --set-version=2.6.26.3 --ignore-install --show-depends nfs
WARNING: Could not open 'kernel/net/sunrpc/sunrpc.ko': No such file or
directory
WARNING: Could not open 'kernel/fs/nfs_common/nfs_acl.ko': No such file or
directory
WARNING: Could not open 'kernel/fs/lockd/lockd.ko': No such file or
directory
FATAL: Could not open 'kernel/fs/nfs/nfs.ko': No such file or directory

# modprobe -V
module-init-tools version 3.7-pre9
# modprobe --set-version=2.6.26.3 --ignore-install --show-depends nfs
WARNING: All config files need .conf: /etc/modprobe.d/pnp-hotplug, it will
be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/display_class, it
will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will
be ignored in a future release.
insmod /lib/modules/2.6.26.3/kernel/net/sunrpc/sunrpc.ko
insmod /lib/modules/2.6.26.3/kernel/fs/nfs_common/nfs_acl.ko
insmod /lib/modules/2.6.26.3/kernel/fs/lockd/lockd.ko
insmod /lib/modules/2.6.26.3/kernel/fs/nfs/nfs.ko

That would mean that m-i-t has created a backwards incompatibility problem
_with itself_ and that the problem actually is "installing a kernel, that
was built on a system with new m-i-t, on a system with old m-i-t".
Or, installing a kernel, built on a system running unstable or testing, on
a system running oldstable or stable. That sucks.

The next question is what to do about this? Cluebat m-i-t upstream? Maybe
it's worth taking this to debian-devel for discussion first so at least
more people are aware of the problem.