Date: Sun, 30 Jul 2017 22:13:28 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Chris Rees <crees@bayofrum.net> Cc: Miroslav Lachman <000.fbsd@quip.cz>, ports@freebsd.org Subject: Re: Trying to get poudriere to start Message-ID: <77ac0738-b06c-deeb-6367-9a6c5be73180@digiware.nl> In-Reply-To: <95F080D1-1C83-44A7-8A07-F573AAD48B71@bayofrum.net> References: <3acd4049-6f55-449b-9867-b1474700324a@email.android.com> <c22639c0-fe0a-8fee-804d-b348bfd944cb@digiware.nl> <95F080D1-1C83-44A7-8A07-F573AAD48B71@bayofrum.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30-7-2017 19:59, Chris Rees wrote: > > > On 29 July 2017 20:01:42 BST, Willem Jan Withagen <wjw@digiware.nl> wrote: >> >> >> Op 29-7-2017 om 13:34 schreef Chris Rees: >>> >>> >>> On 29 Jul 2017 11:56, Willem Jan Withagen <wjw@digiware.nl> wrote: >>> >>> >>> >>> Op 28-7-2017 om 22:50 schreef Chris Rees: >>> >>> >>> >>> On 26 Jul 2017 23:59, Willem Jan Withagen <wjw@digiware.nl> >>> <mailto:wjw@digiware.nl> wrote: >>> >>> Op 27-7-2017 om 00:48 schreef Miroslav Lachman: >>> > Willem Jan Withagen wrote on 2017/07/26 23:24: >>> >> Hi, >>> >> >>> >> This has been working, but now the jail does not even >>> start.... >>> >> Any suggestions why the linux module is giving me >> trouble? >>> >> >>> >> > sudo poudriere bulk -vv -j ceph -p local net/ceph >>> >> kldload: an error occurred while loading module linux. >>> Please check >>> >> dmesg(8) for more details. >>> >> [00:00:00] ====>> Error: Required kernel module >> 'linux' >>> not found >>> >> >>> >> The parent system has linux stuff mounted in >>> /compat/linux/proc >>> >> >>> >> Running 12-CURRENT. >>> > >>> > Did you tried "kldload linux" in host system? Will >>> kldstat show you >>> > loaded kernel module "linux"? >>> > >>> Right, >>> I feel rather stupid... Because I do kknow how most of >>> this works. >>> So indeed this is all at the upper level: >>> >>> Looks like a incompatability.... >>> link_elf_obj: symbol freebsd32_exec_copyin_args undefined >>> linker_load_file: /boot/kernel/linux.ko - unsupported >> file >>> type >>> >>> But why.... >>> >>> [~] wjw@freetest.digiware.nl >>> <mailto:wjw@freetest.digiware.nl>> ls -asl >>> /boot/kernel/*linux* >>> 14 -r-xr-xr-x 1 root wheel 13232 Jul 19 12:55 >>> /boot/kernel/amr_linux.ko* >>> 47 -r-xr-xr-x 1 root wheel 47480 Jul 19 12:55 >>> /boot/kernel/geom_linux_lvm.ko* >>> 14 -r-xr-xr-x 1 root wheel 13312 Jul 19 12:55 >>> /boot/kernel/ipmi_linux.ko* >>> 771 -r-xr-xr-x 1 root wheel 659248 Jul 19 12:55 >>> /boot/kernel/linux.ko* >>> 643 -r-xr-xr-x 1 root wheel 590328 Jul 19 12:55 >>> /boot/kernel/linux64.ko* >>> 56 -r-xr-xr-x 1 root wheel 55936 Jul 19 12:55 >>> /boot/kernel/linux_common.ko* >>> 259 -r-xr-xr-x 1 root wheel 186336 Jul 19 12:55 >>> /boot/kernel/linuxkpi.ko* >>> 16 -r-xr-xr-x 1 root wheel 15120 Jul 19 12:55 >>> /boot/kernel/mfi_linux.ko* >>> 16 -r-xr-xr-x 1 root wheel 15448 Jul 19 12:55 >>> /boot/kernel/mrsas_linux.ko* >>> 102 -r-xr-xr-x 1 root wheel 103416 Jul 19 12:55 >>> /boot/kernel/systrace_linux.ko* >>> 112 -r-xr-xr-x 1 root wheel 113416 Jul 19 12:55 >>> /boot/kernel/systrace_linux32.ko* >>> >>> [~] wjw@freetest.digiware.nl >>> <mailto:wjw@freetest.digiware.nl>> file >> /boot/kernel/linux.ko >>> /boot/kernel/linux.ko: ELF 64-bit LSB relocatable, >> x86-64, >>> version 1 >>> (FreeBSD), not stripped >>> >>> Are the jail and host the same version? >>> >>> >>> Nope, >>> >>> But if I check the jail scripts, the modules are loaded outside >> of >>> the jail in the host. >>> So I would expect that not to mater. >>> >>> --WjW >>> >>> >>> Well, depends entirely on which modules are loaded! Are you loading >>> host modules? >>> >> >> This is the code I commented out: >> >> /usr/local/share/poudriere/common.sh: 1780 >> # if [ -z "${NOLINUX}" ]; then >> # if [ "${arch}" = "i386" -o "${arch}" = "amd64" ]; then >> # needfs="${needfs} linprocfs" >> # needkld="${needkld} linuxelf:linux" >> # if [ "${arch}" = "amd64" ] && \ >> # [ ${HOST_OSVERSION} -ge 1002507 ]; then >> # needkld="${needkld} linux64elf:linux64" >> # fi >> # fi >> # fi >> >> Which suggest that it is the host that is loading the modules. >> >> --WjW > > Long shot, but it's worth a try... Have you rebooted since installing that kernel 11 days ago? If you were running an old kernel that'll give the problem you're having. Rebooting was the first thing I did when I could not get it to work. The I checked that all components are of the same dat/time, and thus from the same compilation run. > Also, please check that > > # sysctl kern.bootfile Like this?? kern.bootfile: /boot/kernel/kernel > > is somewhere in /boot/kernel. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77ac0738-b06c-deeb-6367-9a6c5be73180>