Gilles, Stephan - I suspect a more simple build goof on my behalf, but I dont quite see it yet; these were the steps I used:
tar xvf ipipe-kernel-3.8.10.patch.tar.bz2 git clone git://git.xenomai.org/xenomai-2.6.git # using master git clone https://github.com/RobertCNelson/linux-dev.git cd linux-dev git checkout 3.8.10-bone15 -b tmp ./build_kernel.sh #... vanilla kernel builds fine.. # suspicious: I get some patching fuzz here but no rejects: ../xenomai-2.6/scripts/prepare-kernel.sh --linux=KERNEL --arch=arm --ipipe=../ipipe-kernel-3.8.10.patch cd KERNEL patch -p1 <../../post.patch # no fuzz cd .. tools/rebuild.sh # disable frequency scaling in menuconfig # xenomai kernel builds fine this time around, I get: ./xeno-regression-test -l "/usr/lib/xenomai/testsuite/dohell -m /tmp 100" -t 2 Started child 1921: /bin/bash /usr/xenomai/bin/xeno-test-run-wrapper ./xeno-regression-test -t 2 ++ echo 0 ++ /usr/xenomai/bin/arith Xenomai: native skin or CONFIG_XENO_OPT_PERVASIVE disabled. (modprobe xeno_native?) however: root@arm:/proc# cat /proc/ipipe/version 3 root@arm:/proc# cat /proc/xenomai/version 2.6.2.1 smoke, but no fire yet;) - Michael Am 04.05.2013 um 01:29 schrieb Gilles Chanteperdrix <[email protected]>: > On 05/03/2013 11:54 PM, Michael Haberler wrote: > >> I've built a 3.8.10 beaglebone kernel using Stephane's patch and >> xenomai-2.6 master ; only config changes from default config were: >> disable frequency scaling, and disable smp (but same symptoms as >> below without these changes) > > >> >> - kernel boots fine - 'sudo xeno-regression-test -l >> "/usr/lib/xenomai/testsuite/dohell -m /tmp 100" -t 2' aborts like so: >> http://static.mah.priv.at/public/regression.txt > > > I can not reproduce these issues, so, I must assume it is either > specific to beaglebone or 3.8.10. Could you try 3.8.0 to help narrow > down the issue? > > What arguments are passed to xenomai configure script? > >> - starting the >> linuxcnc latency-test (which basically starts two userland threads) >> hangs the board >> >> I'm a bit at wit's end - any suggestions? > > > Try: > - running a kernel with CONFIG_IPIPE_DEBUG_CONTEXT and > CONFIG_IPIPE_DEBUG_INTERNAL enabled; > - booting a kernel without CONFIG_IPIPE and CONFIG_XENOMAI, run: > > cat /proc/interrupts > > and check that all the interrupts controller you find > mentioned here have been changed following the instructions on this > page: > http://www.xenomai.org/index.php/I-pipe-core:ArmPorting#Interrupt_controller > > -- > Gilles. _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
