Bug#567460: [Pkg-dkms-maint] Bug#567460: dkms: automatic module-build of the VirtualBox-Modules after kernel-update fails
Hello, as there is no response from you by now, I would like to ask, if I can do something to help you in investigating my problem?
Bug#567460: [Pkg-dkms-maint] Bug#567460: dkms: automatic module-build of the VirtualBox-Modules after kernel-update fails
According to the upstream bug I filed, the error seems to occur because of the order the modules are built. How can the order of compiling modules can be set? Could you look into it to support upstream!? Thanks!
Bug#567460: [Pkg-dkms-maint] Bug#567460: dkms: automatic module-build of the VirtualBox-Modules after kernel-update fails
Hello, after just updating my kernel, I searched for log-files again and I found one in /var/lib/dkms/vboxnetflt/kernel-2.6.32-7.slh.3-sidux-686-i686/log/make.log: DKMS make.log for vboxnetflt-3.1.4_BETA1 for kernel 2.6.32-7.slh.3-sidux-686 (i686) Do 4. Feb 00:00:25 CET 2010 make: Entering directory `/usr/src/linux-headers-2.6.32-7.slh.3-sidux-686' LD /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/built-in.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/linux/VBoxNetFlt-linux.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/VBoxNetFlt.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/SUPR0IdcClient.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/SUPR0IdcClientComponent.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/SUPR0IdcClient-linux.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/divdi3.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/moddi3.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/qdivrem.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/udivdi3.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/umoddi3.o LD [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.o Building modules, stage 2. MODPOST 1 modules WARNING: RTSemFastMutexDestroy [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTUuidCompareStr [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTR0Term [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSpinlockAcquire [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemEventCreate [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSpinlockDestroy [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTTimeNanoTS [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemFastMutexRelease [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTMemFree [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTLogRelDefaultInstance [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSpinlockCreate [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemFastMutexRequest [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTErrConvertToErrno [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTMemAllocZ [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemEventWait [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTErrConvertFromErrno [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemEventSignal [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTUuidFromStr [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemEventDestroy [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSpinlockRelease [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: SUPDrvLinuxIDC [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTR0Init [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! WARNING: RTSemFastMutexCreate [/var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko] undefined! CC /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.mod.o LD [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.ko make: Leaving directory `/usr/src/linux-headers-2.6.32-7.slh.3-sidux-686' This log is right after the automatic module build during the kernel update! The next one is right after rebooting and manually invoking /etc/init.d/vboxdrv setup DKMS make.log for vboxnetflt-3.1.4_BETA1 for kernel 2.6.32-7.slh.3-sidux-686 (i686) Do 4. Feb 00:17:45 CET 2010 make: Entering directory `/usr/src/linux-headers-2.6.32-7.slh.3-sidux-686' LD /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/built-in.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/linux/VBoxNetFlt-linux.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/VBoxNetFlt.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/SUPR0IdcClient.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/SUPR0IdcClientComponent.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/SUPR0IdcClient-linux.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/divdi3.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/moddi3.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/qdivrem.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/udivdi3.o CC [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/math/gcc/umoddi3.o LD [M] /var/lib/dkms/vboxnetflt/3.1.4_BETA1/build/vboxnetflt.o Building modules, stage 2. MODPOST 1 modules CC
Bug#567460: [Pkg-dkms-maint] Bug#567460: dkms: automatic module-build of the VirtualBox-Modules after kernel-update fails
For the first: I hope, it is the correct part of the correct log: /var/log/apt/term.log: Richte linux-headers-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ... Richte linux-image-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-7.slh.1-sidux-686 Running /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 Found kernel: /boot/vmlinuz-2.6.32-6.slh.4-sidux-686 Found kernel: /boot/vmlinuz-2.6.32-6.slh.3-sidux-686 Found kernel: /boot/vmlinuz-2.6.32-5.slh.2-sidux-686 Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 2.6.32-7.slh.1-sidux-686 /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-7.slh.1-sidux-686 /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-7.slh.1-sidux-686 /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 Richte linux-headers-2.6-sidux-686 ein (2.6.32-32) ... Richte linux-image-2.6-sidux-686 ein (2.6.32-32) ... For the second: I think the following should answer your question: my kernel-update-sequence: init 3 - update kernel - init 6 (boot into NEW kernel! - errors in dmesg - run /etc/init.d/vboxdrv setup If you need more information, I'll try to post it. Thanks! Dennis
Bug#567460: [Pkg-dkms-maint] Bug#567460: dkms: automatic module-build of the VirtualBox-Modules after kernel-update fails
For the first: I hope, it is the correct part of the correct log: /var/log/apt/term.log: Richte linux-headers-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ... Richte linux-image-2.6.32-7.slh.1-sidux-686 ein (2.6.32-32) ... Running depmod. Running update-initramfs. update-initramfs: Generating /boot/initrd.img-2.6.32-7.slh.1-sidux-686 Running /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 Found kernel: /boot/vmlinuz-2.6.32-6.slh.4-sidux-686 Found kernel: /boot/vmlinuz-2.6.32-6.slh.3-sidux-686 Found kernel: /boot/vmlinuz-2.6.32-5.slh.2-sidux-686 Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 2.6.32-7.slh.1-sidux-686 /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.32-7.slh.1-sidux-686 /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.32-7.slh.1-sidux-686 /boot/vmlinuz-2.6.32-7.slh.1-sidux-686 Richte linux-headers-2.6-sidux-686 ein (2.6.32-32) ... Richte linux-image-2.6-sidux-686 ein (2.6.32-32) ... For the second: I think the following should answer your question: my kernel-update-sequence: init 3 - update kernel - init 6 (boot into NEW kernel! - errors in dmesg - run /etc/init.d/vboxdrv setup If you need more information, I\'ll try to post it. Thanks! Dennis - A free e-mail service from TrashDevil.com http://www.Trashdevil.com - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567460: [Pkg-dkms-maint] Bug#567460: dkms: automatic module-build of the VirtualBox-Modules after kernel-update fails
This is two separate issues. For the first: Can you post the apt log to see if the kernel postinst.d hook was not getting ran? For the second, That depends on what that script is actually doing. And are you running it from the kernel you are supposed to be booted into? It could possibly be a bug in the script. On 01/29/2010 02:36 AM, Dennis Kadioglu wrote: Package: dkms Version: 2.1.1.1-1 Severity: important After every Kernel-Update I have to invoke /etc/init.d/vboxdrv setup because the modules built automatically by dkms during the Kernel-Update lead to the following errors in dmesg: vboxnetflt: no symbol version for RTSemFastMutexCreate vboxnetflt: Unknown symbol RTSemFastMutexCreate vboxnetflt: no symbol version for RTR0Init vboxnetflt: Unknown symbol RTR0Init vboxnetflt: no symbol version for SUPDrvLinuxIDC vboxnetflt: Unknown symbol SUPDrvLinuxIDC vboxnetflt: no symbol version for RTSpinlockRelease vboxnetflt: Unknown symbol RTSpinlockRelease vboxnetflt: no symbol version for RTSemEventDestroy vboxnetflt: Unknown symbol RTSemEventDestroy vboxnetflt: no symbol version for RTUuidFromStr vboxnetflt: Unknown symbol RTUuidFromStr vboxnetflt: no symbol version for RTSemEventSignal vboxnetflt: Unknown symbol RTSemEventSignal vboxnetflt: no symbol version for RTErrConvertFromErrno vboxnetflt: Unknown symbol RTErrConvertFromErrno vboxnetflt: no symbol version for RTSemEventWait vboxnetflt: Unknown symbol RTSemEventWait vboxnetflt: no symbol version for RTMemAllocZ vboxnetflt: Unknown symbol RTMemAllocZ vboxnetflt: no symbol version for RTErrConvertToErrno vboxnetflt: Unknown symbol RTErrConvertToErrno vboxnetflt: no symbol version for RTSemFastMutexRequest vboxnetflt: Unknown symbol RTSemFastMutexRequest vboxnetflt: no symbol version for RTSpinlockCreate vboxnetflt: Unknown symbol RTSpinlockCreate vboxnetflt: no symbol version for RTLogRelDefaultInstance vboxnetflt: Unknown symbol RTLogRelDefaultInstance vboxnetflt: no symbol version for RTMemFree vboxnetflt: Unknown symbol RTMemFree vboxnetflt: no symbol version for RTSemFastMutexRelease vboxnetflt: Unknown symbol RTSemFastMutexRelease vboxnetflt: no symbol version for RTTimeNanoTS vboxnetflt: Unknown symbol RTTimeNanoTS vboxnetflt: no symbol version for RTSpinlockDestroy vboxnetflt: Unknown symbol RTSpinlockDestroy vboxnetflt: no symbol version for RTSemEventCreate vboxnetflt: Unknown symbol RTSemEventCreate vboxnetflt: no symbol version for RTSpinlockAcquire vboxnetflt: Unknown symbol RTSpinlockAcquire vboxnetflt: no symbol version for RTR0Term vboxnetflt: Unknown symbol RTR0Term vboxnetflt: no symbol version for RTUuidCompareStr vboxnetflt: Unknown symbol RTUuidCompareStr vboxnetflt: no symbol version for RTSemFastMutexDestroy vboxnetflt: Unknown symbol RTSemFastMutexDestroy The Log-File vbox-install.log isn't written during automatic rebuild, the Log-File dkms-autoinstaller.log is always empty. DKMS doesn't show any error during automatic rebuild for the new kernel. I filed an upstream bug at virtualbox.org, too: http://www.virtualbox.org/ticket/5817 Thanks -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-7.slh.1-sidux-686 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dkms depends on: ii build-essential 11.4Informational list of build-essent ii dpkg-dev 1.15.5.6Debian package development tools ii gcc 4:4.4.2-3 The GNU C compiler ii make 3.81-7 An utility for Directing compilati ii module-init-tools3.12~pre1-1 tools for managing Linux kernel mo Versions of packages dkms recommends: pn fakerootnone (no description available) ii linux-headers-2.6.32-5.slh.2- 2.6.32-27 Header files for Linux 2.6.32-5.sl ii linux-headers-2.6.32-6.slh.3- 2.6.32-30 Header files for Linux 2.6.32-6.sl ii linux-headers-2.6.32-6.slh.4- 2.6.32-31 Header files for Linux 2.6.32-6.sl ii linux-headers-2.6.32-7.slh.1- 2.6.32-32 Header files for Linux 2.6.32-7.sl ii linux-image-2.6.32-5.slh.2-si 2.6.32-27 Linux 2.6.32 image on PPro/Celeron ii linux-image-2.6.32-6.slh.3-si 2.6.32-30 Linux 2.6.32 image on PPro/Celeron ii linux-image-2.6.32-6.slh.4-si 2.6.32-31 Linux 2.6.32 image on PPro/Celeron ii linux-image-2.6.32-7.slh.1-si 2.6.32-32 Linux 2.6.32 image on PPro/Celeron ii lsb-release 3.2-23 Linux Standard Base version report ii menu 2.1.43 generates programs menu for all me ii patch 2.6-2 Apply a diff file to an original ii sudo 1.7.2p1-1 Provide limited super user privile dkms suggests no packages. -- no debconf information ___ Pkg-dkms-maint
