Processed: Re: Processed: Re: Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
Processing control commands:
> reassign -1 virtualbox-guest-dkms 6.0.10-dfsg-4
Bug #934483 {Done: Gianfranco Costamagna }
[src:linux] virtualbox-guest-dkms: Doesn't build with latest kernel in unstable
5.2.0-2-686-pae
Bug reassigned from package 'src:linux' to 'virtualbox-guest-dkms'.
No longer marked as found in versions linux/5.2.9-1.
No longer marked as fixed in versions virtualbox/6.0.10-dfsg-5.
Bug #934483 {Done: Gianfranco Costamagna }
[virtualbox-guest-dkms] virtualbox-guest-dkms: Doesn't build with latest kernel
in unstable 5.2.0-2-686-pae
Marked as found in versions virtualbox/6.0.10-dfsg-4.
--
934483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#934483: Processed: Re: Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
Control: reassign -1 virtualbox-guest-dkms 6.0.10-dfsg-4 On Tue, 2019-08-20 at 14:03 +, Debian Bug Tracking System wrote: > Processing control commands: > > > reassign -1 src:linux No, this is not our problem to fix. In answer to your question, which *wasn't* cc'd to debian-kernel: > Ben, do you have any clue? should the code include > instead? Yes I think so. I don't know how it ever worked before. Ben. -- Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
Processing control commands: > reassign -1 src:linux Bug #934483 [virtualbox-guest-dkms] virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae Bug reassigned from package 'virtualbox-guest-dkms' to 'src:linux'. No longer marked as found in versions virtualbox/6.0.10-dfsg-4. Ignoring request to alter fixed versions of bug #934483 to the same values previously set > affects -1 virtualbox-guest-dkms Bug #934483 [src:linux] virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae Added indication that 934483 affects virtualbox-guest-dkms > found -1 5.2.9-1 Bug #934483 [src:linux] virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae Marked as found in versions linux/5.2.9-1. -- 934483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
control: reassign -1 src:linux control: affects -1 virtualbox-guest-dkms control: found -1 5.2.9-1 On Mon, 19 Aug 2019 19:02:52 +0200 Raphael Hertzog wrote: > On Sun, 11 Aug 2019, Christian Marillat wrote: > > But bevare fixind the include file path (drm/ttm/ttm_page_alloc.h) doesn't > > work at all the virtualbox doesn't start. > Hello, for some reasons, the directory "include/drm" is not correctly used from Makefile in -common and this leads to a build failure gcc-8 -Wp,-MD,/virtualbox-guest-6.0.10/vboxvideo/.vbox_hgsmi.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/8/include -I/usr/src/linux-headers-5.2.0-2-common/arch/x86/include -I./arch/x86/include/generated -I/usr/src/linux-headers-5.2.0-2-common/include -I./include -I/usr/src/linux-headers-5.2.0-2-common/arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I/usr/src/linux-headers-5.2.0-2-common/include/uapi -I./include/generated/uapi -include /usr/src/linux-headers-5.2.0-2-common/include/linux/kconfig.h -include /usr/src/linux-headers-5.2.0-2-common/include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -O2 --param=allow-store-data-races=0 -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=/usr/src/linux-headers-5.2.0-2-common/= -Wno-packed-not-aligned -I/usr/src/linux-headers-5.2.0-2-common/include -I/virtualbox-guest-6.0.10/vboxvideo/ -Iinclude/drm -D__KERNEL__ -DMODULE -DRT_WITHOUT_PRAGMA_ONCE -DRT_ARCH_AMD64 -DMODULE -DKBUILD_BASENAME='"vbox_hgsmi"' -DKBUILD_MODNAME='"vboxvideo"' -c -o /virtualbox-guest-6.0.10/vboxvideo/vbox_hgsmi.o /virtualbox-guest-6.0.10/vboxvideo/vbox_hgsmi.c /virtualbox-guest-6.0.10/vboxvideo/vbox_ttm.c:31:10: fatal error: ttm/ttm_page_alloc.h: No such file or directory #include ^~ this works: diff -rup /Makefile /usr/src/linux-headers-5.2.0-2-common/Makefile --- /Makefile 2019-08-20 13:53:45.407304601 + +++ /usr/src/linux-headers-5.2.0-2-common/Makefile 2019-08-20 13:58:16.887902668 + @@ -450,6 +450,7 @@ LINUXINCLUDE:= \ -I$(objtree)/arch/$(SRCARCH)/include/generated \ $(if $(filter .,$(srctree)),,-I$(srctree)/include) \ -I$(objtree)/include \ + -I$(srctree)/include/drm \ $(USERINCLUDE) KBUILD_AFLAGS := -D__ASSEMBLY__ -fno-PIE but for sure it might be not a real solution, just a workaround I can't understand yet... Ben, do you have any clue? should the code include instead? I admit I'm lost in this bug... G.
Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
On Sun, 11 Aug 2019, Christian Marillat wrote: > But bevare fixind the include file path (drm/ttm/ttm_page_alloc.h) doesn't > work at all the virtualbox doesn't start. I fixed the path, the build went through. I rebooted my VM and it worked. What exactly was the failure that you had? Did you have some error message in the kernel logs? However on the gdm3 login screen, after I have input my login/password, the picture stays fixed and I have to resize the window or force a VT switch to get it working again... In the kernel log I see this: > [drm] Error -12 pinnning new fb, out of video mem? And as you mentionned in your other mail, if I increase the allocated memory for video to 32 Mb (I had 16), this problem goes away. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
On 19 août 2019 17:18, Raphael Hertzog wrote: > Hi, > > On Thu, 15 Aug 2019, Darsey Litzenberger wrote: >> I haven't gotten around to testing, but it looks like maybe all that needs >> to be done is to disable building some of these modules after a certain >> kernel version. > > At least I can confirm that if you disable "vboxvideo" from the > dkms configuration (in dkms.conf and Makefile in the > /usr/src/virtualbox-guest-6.0.10/ directory), then the DKMS build > works. Works for me too. But memory assigned to video in virtualbox need to be increased, 10MB isn't enough. Christian
Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
Hi, On Thu, 15 Aug 2019, Darsey Litzenberger wrote: > I haven't gotten around to testing, but it looks like maybe all that needs > to be done is to disable building some of these modules after a certain > kernel version. At least I can confirm that if you disable "vboxvideo" from the dkms configuration (in dkms.conf and Makefile in the /usr/src/virtualbox-guest-6.0.10/ directory), then the DKMS build works. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Bug#934483: virtualbox-guest-dkms: Doesn't build with latest kernel in unstable 5.2.0-2-686-pae
On Sun, Aug 11, 2019 at 03:14:16PM +0200, Christian Marillat wrote: Dear Maintainer, /var/lib/dkms/virtualbox-guest/6.0.10/build/vboxvideo/vbox_ttm.c:31:10: fatal error: ttm/ttm_page_alloc.h: No such file or directory #include ^~ compilation terminated. But bevare fixind the include file path (drm/ttm/ttm_page_alloc.h) doesn't work at all the virtualbox doesn't start. Do all of these modules even need to be built using dkms anymore? It looks like some of them have been mainlined (though I haven't compared the code): It looks like virtualbox-guest-dkms builds 3 modules: # cd /var/lib/dkms/virtualbox-guest # find . -name \*.ko ./6.0.10/5.0.0-trunk-amd64/x86_64/module/vboxguest.ko ./6.0.10/5.0.0-trunk-amd64/x86_64/module/vboxsf.ko ./6.0.10/5.0.0-trunk-amd64/x86_64/module/vboxvideo.ko Out of those three modules, it seems like only vboxsf.ko still needs to be built on recent kernels: root@syra:/lib/modules# find . -name vboxguest.ko -o -name vboxsf.ko -o -name vboxvideo.ko ./5.0.0-trunk-amd64/kernel/drivers/staging/vboxvideo/vboxvideo.ko ./5.0.0-trunk-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko ./5.0.0-trunk-amd64/updates/dkms/vboxguest.ko ./5.0.0-trunk-amd64/updates/dkms/vboxsf.ko ./5.0.0-trunk-amd64/updates/dkms/vboxvideo.ko ./4.19.0-5-amd64/kernel/drivers/staging/vboxvideo/vboxvideo.ko ./4.19.0-5-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko ./5.2.0-2-amd64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko ./5.2.0-2-amd64/kernel/drivers/virt/vboxguest/vboxguest.ko (split for readability) I haven't gotten around to testing, but it looks like maybe all that needs to be done is to disable building some of these modules after a certain kernel version.
