On 25.03.22 14:01, Paal Tamas wrote: > > > Jan Kiszka <jan.kis...@siemens.com> írta: > > On 25.03.22 13:26, Paal Tamas via Xenomai wrote: > > Dear All, > > I am using xenomai_3.2.1 with kernel 5.10-dovetail on x86_64 platform. > I compile the kernel to 64bit, but I need to have the userspace as 32bit. So > I configured the userspace compilation the following way: > > ./configure --with-core=cobalt --enable-smp --enable-pshared > --host=i686-linux CFLAGS="-m32 -D_FILE_OFFSET_BITS=64" LDFLAGS=-m32 > host_alias=i686-linux > > I tried to start RTNET, but I get "Inappropriate ioctl for device" > errors. I reported this issue in another thread. > > The problem seems to be not RTNET realted, since xeno-test fails with > the same error: desktop:/usr/xenomai/bin$ sudo ./xeno-test > > Started child 2202: /bin/bash /usr/xenomai/bin/xeno-test-run-wrapper > ./xeno-test > > ++ echo 0 > > ++ testdir=/usr/xenomai/bin > > ++ which systemctl > > ++ systemctl is-active --quiet systemd-timesyncd > > ++ timesyncd_was_running=true > > ++ systemctl stop systemd-timesyncd > > ++ /usr/xenomai/bin/smokey --run random_alloc_rounds=64 > pattern_check_rounds=64 > > arith OK > > bufp skipped (no kernel support) > > cpu_affinity skipped (no kernel support) > > fpu_stress OK > > gdb OK > > iddp skipped (no kernel support) > > leaks OK > > memory_coreheap OK > > memory_heapmem OK > > memory_tlsf OK > > setup.c:96, ioctl(fd, IOC_RT_IFINFO, &cmd): Inappropriate ioctl for > device > > /usr/xenomai/bin/smokey: test net_packet_dgram failed: Inappropriate > ioctl for device > > + start_timesyncd > > + true > > + systemctl start systemd-timesyncd > > + timesyncd_was_running=false > > child 2202 returned: exited with status 1 > > What am I doing wrong? > > Nothing, known issue in principle: > https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues/21 > > Jan > > -- > Siemens AG, Technology > Competence Center Embedded Linux > > Jan, >
The citation settings of your email client are misconfigured. > > > Thank you for the fast response! > > Do you have any guess when this "mixed system" will work? > There are multiple issues to be debugged and patched. Someone has to sit down and do at least the debugging work. And we need that image for the test lab so that the result is validated during regular runs. So far none of those to-dos have a schedule yet. Jan -- Siemens AG, Technology Competence Center Embedded Linux
