Re: [Xenomai] beaglebone: arm: xeno-test gives segmentation fault - test dlopen failed
On Thu, Jun 28, 2018 at 9:06 PM Henning Schild wrote: > > Hi, > > could you please try v3.0.7 (733a32b71f77dfb3e7a64039d0692e6c9d5d1cfe) How to clone 3.0.7 as a git repo (not the tar)? > this is a tag not a branch. Or use branch "stable/v3.0.x". Ok, will try with stable on Beaglebone. But as I see stable also contains the same dlopen fixes. > The commit from "next" you mentioned does not exist anymore, one of the > pleasures of using git ... do not use "next" unless you really have to! > I guess, arm64 support is present only on "next" branch. Since we want to maintain single kernel for all (x86, arm, arm64) we choose next branch. And AFAIK, next branch should always contain all the patches from previous stable branch. > If you are not using dlopen just drop "--enable-dlopen-libs" from your > configure options. > Yes, I did not use this, but still I get dlopen error on ARM - beaglebone. I just used: # ./configure --enable-smp Also, on x86, it works if I just use: # ./configure But same dlopen error if I use: # ./configure --enable-dlopen-libs And, I wanted to know how to disable this config from xenomai-3 - configure.ac CONFIG_XENO_LIBS_DLOPEN > Henning > > Am Wed, 27 Jun 2018 18:51:03 +0530 > schrieb Pintu Kumar : > > > Hi, > > > > Sorry, but both the below patches are already applied to my > > xenomai-next repo: build: link dlopen libs with "nodelete" > > smokey/dlopen: fix testcase > > > > Still I am facing dlopen issue. > > Is there any other patches I am missing? > > > > > > Thanks, > > Pintu > > > > On Wed, Jun 27, 2018 at 6:47 PM Pintu Kumar > > wrote: > > > > > > Hi, > > > > > > One doubt, how do we clone 3.0.7 ? > > > Is it part of the following branches? > > > remotes/origin/next > > > remotes/origin/stable/v3.0.x > > > > > > I could not find any branch with the name 3.0.7. > > > > > > Is all 3 patches important, or only this is fine: > > > build: link dlopen libs with "nodelete" > > > smokey/dlopen: fix testcase > > > > > > Sorry, but can you list down all 3 commits. > > > > > > > > > Thanks, > > > Pintu > > > > > > > > > > > > Thanks, > > > Pintu > > > On Wed, Jun 27, 2018 at 6:30 PM Pintu Kumar > > > wrote: > > > > > > > > Dear Henning, > > > > > > > > Thanks so much for your reply. > > > > I am actually using xenomai-next branch. > > > > With last commit as: > > > > commit ffb68112e2342a62a1f70916a35a3d68e875b12c > > > > Author: Philippe Gerum > > > > Date: Mon May 21 12:54:59 2018 +0200 > > > > > > > > scripts/prepare-kernel.sh: drop left overs from obsolete ports > > > > > > > > Anyways, I will check with your reference commits. > > > > > > > > Thanks, > > > > Pintu > > > > On Wed, Jun 27, 2018 at 6:07 PM Henning Schild > > > > wrote: > > > > > > > > > > Hi Pintu, > > > > > > > > > > i guess you might be using v3.0.6. There are a couple of > > > > > commits on top of that > > > > > https://gitlab.denx.de/Xenomai/xenomai/commit/aa008686091484c88cbb809bc190133a98769a30 > > > > > and 2 parents > > > > > All three are in v3.0.7, which hopefully solves your problem. > > > > > > > > > > regards, > > > > > Henning > > > > > > > > > > Am Wed, 27 Jun 2018 16:11:43 +0530 > > > > > schrieb Pintu Kumar : > > > > > > > > > > > Dear Henning, > > > > > > > > > > > > I saw your commit regarding dlopen here: > > > > > > https://xenomai.org/pipermail/xenomai/2018-February/038351.html > > > > > > > > > > > > We are facing dlopen error with xeno-test on arm (beagle > > > > > > bone) and arm64 (hikey) boards. > > > > > > Segmentation fault > > > > > > /usr/xenomai/bin/smokey: test dlopen failed: Unknown error -1 > > > > > > > > > > > > Do you have any clue regarding this issue. > > > > > > Earlier xeno-test worked for us, but after this commit > > > > > > xeno-test is failing. > > > > > > > > > > > > Currently we dont need dlopen test. > > > > > > So, please let us know how to disable dlopen test to pass the > > > > > > xeno-test report. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > Pintu > > > > > > > > > > > > > > > > > > > > > > > > On Tue, Jun 26, 2018 at 11:07 PM Pintu Kumar > > > > > > wrote: > > > > > > > > > > > > > > One more thing, > > > > > > > On x86 xeno-test works fine even with dlopen. > > > > > > > > > > > > > > This problem is seen only of arm and arm64 boards. > > > > > > > > > > > > > > Thanks, > > > > > > > Pintu > > > > > > > On Tue, Jun 26, 2018 at 10:16 PM Pintu Kumar > > > > > > > wrote: > > > > > > > > > > > > > > > > Ok Greg thanks a lot. > > > > > > > > > > > > > > > > Yes, I can recompile it, but for now I want to get rid of > > > > > > > > this dlopen to pass rest of xeno-test. > > > > > > > > Please let me know how to disable it from configure.ac > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Pintu > > > > > > > > On Tue, Jun 26, 2018 at 8:57 PM Greg Gallagher > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > I'll take a look at this tonight. I'll confirm if > > > > > > > > > this test is crashing on
Re: [Xenomai] Assertion current-magic 0 failed
On 06/28/2018 05:28 PM, Stéphane Reichert wrote: > Hi, > > I am testing the new version 3.0.7 on our system (iMX 6 on 4.1.46 kernel), > and I would like to know > if anybody else encountered this error : > > threadobj.c:1344: threadobj_prologue: Assertion `current->magic == 0' > failed. > > I compile the kernel with --enable-pshared --enable > registry --enable-debug=full. > > Here is a backtrace I get on the debug signal callback: > > # Mode switch (reason: triggered fault), aborting. Backtrace: > Retrieve backtrace... > ./tests_integration_lib_ipc(Unable to handle kernel NULL pointer dereference > at virtual address 0004 > 4x180)[0[x01020206000]08l0e0r0+ > ]]/ l*ipbd=39180831/libc.so.,6 (*+p0txe2=50105000)0[00, > *ppte=0x76ca3150 > > /lib/libcopperplate.so.0(syncobj_lIonctke+r0nxa8l4 error: Oops: 17 [#1] > PREEMPT SMP ARM > l0x76Meo1dau7lee8s] > i/nlkiebd/in:libcopper pcltarte.so.0(syncluster_fin > dcocbmj+0x34)[0x76e18eec] > /lib/li buaslbc_hfe_mayc.mso.0(al u_serialchemy_bind > _uosbbj_efc_te+c0mx98)[0x76e 3ge_1ccd0c] > nlib/libalchemy.so. 0u(_rett_hheerap_bind+0x30 libcomposite)[0x76e411c 4c]o > f/irgofost/libs/lib_ iwplc1.2sxox(init_local_data+0x6 0w)l[c0oxr7e6f1085c] > /roo mac80211t/libs/li bc_figp8c0.2s1o1(rt_shm_open+ 0rxf7k0i)l[l0x76f10bfc] > /tests _filnetxecgarnation_lib_ip wlcore_sdioc[0x12d68] > dc/il_ihbd/rlci_biamlchemy. suos.b0m(i+s0cx_ai4m4x8)[0x76e43 4c4i8_]h > ]r/clib/libcoppe udc_corerplate.so. 0c(a+n0_xd8e3v14)[0x76e1a314 > It looks like there are two backtraces, one generated from the app in userland, a second one by the kernel, none of them is readable as they intermingle. -- Philippe. ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
Re: [Xenomai] beaglebone: arm: xeno-test gives segmentation fault - test dlopen failed
Hi, could you please try v3.0.7 (733a32b71f77dfb3e7a64039d0692e6c9d5d1cfe) this is a tag not a branch. Or use branch "stable/v3.0.x". The commit from "next" you mentioned does not exist anymore, one of the pleasures of using git ... do not use "next" unless you really have to! If you are not using dlopen just drop "--enable-dlopen-libs" from your configure options. Henning Am Wed, 27 Jun 2018 18:51:03 +0530 schrieb Pintu Kumar : > Hi, > > Sorry, but both the below patches are already applied to my > xenomai-next repo: build: link dlopen libs with "nodelete" > smokey/dlopen: fix testcase > > Still I am facing dlopen issue. > Is there any other patches I am missing? > > > Thanks, > Pintu > > On Wed, Jun 27, 2018 at 6:47 PM Pintu Kumar > wrote: > > > > Hi, > > > > One doubt, how do we clone 3.0.7 ? > > Is it part of the following branches? > > remotes/origin/next > > remotes/origin/stable/v3.0.x > > > > I could not find any branch with the name 3.0.7. > > > > Is all 3 patches important, or only this is fine: > > build: link dlopen libs with "nodelete" > > smokey/dlopen: fix testcase > > > > Sorry, but can you list down all 3 commits. > > > > > > Thanks, > > Pintu > > > > > > > > Thanks, > > Pintu > > On Wed, Jun 27, 2018 at 6:30 PM Pintu Kumar > > wrote: > > > > > > Dear Henning, > > > > > > Thanks so much for your reply. > > > I am actually using xenomai-next branch. > > > With last commit as: > > > commit ffb68112e2342a62a1f70916a35a3d68e875b12c > > > Author: Philippe Gerum > > > Date: Mon May 21 12:54:59 2018 +0200 > > > > > > scripts/prepare-kernel.sh: drop left overs from obsolete ports > > > > > > Anyways, I will check with your reference commits. > > > > > > Thanks, > > > Pintu > > > On Wed, Jun 27, 2018 at 6:07 PM Henning Schild > > > wrote: > > > > > > > > Hi Pintu, > > > > > > > > i guess you might be using v3.0.6. There are a couple of > > > > commits on top of that > > > > https://gitlab.denx.de/Xenomai/xenomai/commit/aa008686091484c88cbb809bc190133a98769a30 > > > > and 2 parents > > > > All three are in v3.0.7, which hopefully solves your problem. > > > > > > > > regards, > > > > Henning > > > > > > > > Am Wed, 27 Jun 2018 16:11:43 +0530 > > > > schrieb Pintu Kumar : > > > > > > > > > Dear Henning, > > > > > > > > > > I saw your commit regarding dlopen here: > > > > > https://xenomai.org/pipermail/xenomai/2018-February/038351.html > > > > > > > > > > We are facing dlopen error with xeno-test on arm (beagle > > > > > bone) and arm64 (hikey) boards. > > > > > Segmentation fault > > > > > /usr/xenomai/bin/smokey: test dlopen failed: Unknown error -1 > > > > > > > > > > Do you have any clue regarding this issue. > > > > > Earlier xeno-test worked for us, but after this commit > > > > > xeno-test is failing. > > > > > > > > > > Currently we dont need dlopen test. > > > > > So, please let us know how to disable dlopen test to pass the > > > > > xeno-test report. > > > > > > > > > > > > > > > Thanks, > > > > > Pintu > > > > > > > > > > > > > > > > > > > > On Tue, Jun 26, 2018 at 11:07 PM Pintu Kumar > > > > > wrote: > > > > > > > > > > > > One more thing, > > > > > > On x86 xeno-test works fine even with dlopen. > > > > > > > > > > > > This problem is seen only of arm and arm64 boards. > > > > > > > > > > > > Thanks, > > > > > > Pintu > > > > > > On Tue, Jun 26, 2018 at 10:16 PM Pintu Kumar > > > > > > wrote: > > > > > > > > > > > > > > Ok Greg thanks a lot. > > > > > > > > > > > > > > Yes, I can recompile it, but for now I want to get rid of > > > > > > > this dlopen to pass rest of xeno-test. > > > > > > > Please let me know how to disable it from configure.ac > > > > > > > > > > > > > > Thanks, > > > > > > > Pintu > > > > > > > On Tue, Jun 26, 2018 at 8:57 PM Greg Gallagher > > > > > > > wrote: > > > > > > > > > > > > > > > > Hi, > > > > > > > > I'll take a look at this tonight. I'll confirm if > > > > > > > > this test is crashing on all platforms or just BB. To > > > > > > > > disable I believe you'll have to recompile the tests. > > > > > > > > > > > > > > > > -Greg > > > > > > > > > > > > > > > > On Tue, Jun 26, 2018 at 10:43 AM, Pintu Kumar > > > > > > > > wrote: > > > > > > > > > Dear Greg, > > > > > > > > > > > > > > > > > > Please let me know how to disable "dlopen" test in > > > > > > > > > xenomai-next. > > > > > > > > > > > > > > > > > > I even tried, without dlopen parameter > > > > > > > > > during ./configure but still I get the same issue. > > > > > > > > > # ./configure --enable-smp > > > > > > > > > > > > > > > > > > We did not face this issue earlier on xenomai-3 > > > > > > > > > stable branch. So, I am planning to disable it right > > > > > > > > > now. Please help! > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Pintu > > > > > > > > > > > > > > > > > > On Tue, Jun 26, 2018 at 12:52 PM Pintu Kumar > > > > > > > > > wrote: > > > > > > > > >> > > > > > > > > >> Hi, > > > > > > > > >> I am using
[Xenomai] Assertion current-magic 0 failed
Hi, I am testing the new version 3.0.7 on our system (iMX 6 on 4.1.46 kernel), and I would like to know if anybody else encountered this error : threadobj.c:1344: threadobj_prologue: Assertion `current->magic == 0' failed. I compile the kernel with --enable-pshared --enable registry --enable-debug=full. Here is a backtrace I get on the debug signal callback: # Mode switch (reason: triggered fault), aborting. Backtrace: Retrieve backtrace... ./tests_integration_lib_ipc(Unable to handle kernel NULL pointer dereference at virtual address 0004 4x180)[0[x01020206000]08l0e0r0+ ]]/ l*ipbd=39180831/libc.so.,6 (*+p0txe2=50105000)0[00, *ppte=0x76ca3150 /lib/libcopperplate.so.0(syncobj_lIonctke+r0nxa8l4 error: Oops: 17 [#1] PREEMPT SMP ARM l0x76Meo1dau7lee8s] i/nlkiebd/in:libcopper pcltarte.so.0(syncluster_fin dcocbmj+0x34)[0x76e18eec] /lib/li buaslbc_hfe_mayc.mso.0(al u_serialchemy_bind _uosbbj_efc_te+c0mx98)[0x76e 3ge_1ccd0c] nlib/libalchemy.so. 0u(_rett_hheerap_bind+0x30 libcomposite)[0x76e411c 4c]o f/irgofost/libs/lib_ iwplc1.2sxox(init_local_data+0x6 0w)l[c0oxr7e6f1085c] /roo mac80211t/libs/li bc_figp8c0.2s1o1(rt_shm_open+ 0rxf7k0i)l[l0x76f10bfc] /tests _filnetxecgarnation_lib_ip wlcore_sdioc[0x12d68] dc/il_ihbd/rlci_biamlchemy. suos.b0m(i+s0cx_ai4m4x8)[0x76e43 4c4i8_]h ]r/clib/libcoppe udc_corerplate.so. 0c(a+n0_xd8e3v14)[0x76e1a314 Ulib/libcobalt.so.2(+0x1058c)[0x76df558cC]P : 1 PID: 296 Comm: Reception task Not tainted 4.1.46-ipipe #6 Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree) task: a885dd80 ti: a97fa000 task.ti: a97fa000 PC is at cobalt_signal_send+0xf8/0x1f8 LR is at 0x18 pc : [<800acedc>]lr : [<0018>]psr: a0080093 sp : a97fbf00 ip : a94ff948 fp : 8095f680 r10: ab70e6e0 r9 : 0124 r8 : 8088c880 r7 : 0001 r6 : r5 : 0080 r4 : a94ff4d8 r3 : 0017 r2 : r1 : c08f9000 r0 : c09e5800 Flags: NzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user Control: 10c53c7d Table: 38ec804a DAC: 0015 Process Reception task (pid: 296, stack limit = 0xa97fa220) Stack: (0xa97fbf00 to 0xa97fc000) bf00: 0018 c08f9000 c09e5800 800ad534 c09e5800 0018 0001 bf20: 8088c880 808945fc 0018 800ad788 c09e9008 0022 a97fbfb0 800ad71c bf40: 808945fc 0001 ab70e6e0 800ae248 762bce38 a97fbfb0 808945fc 20080013 bf60: 0001 ab70d6e0 8095f680 8088b6e0 ab70e6e0 8008a14c 8095f680 a97fbfb0 bf80: 8088b6e0 8088da20 0404 762bce14 762bce38 000f0042 8000f028 bfa0: a97fa000 0002 762718cc 8000ef84 1040 0124 0018 0124 bfc0: 762bce14 762bce38 000f0042 76f23594 0001e030 76271c74 762718cc bfe0: 0018 76271870 000122ac 76df5148 20080010 1040 8473a46f c307ae3a [<800acedc>] (cobalt_signal_send) from [<800ad534>] (__cobalt_kill+0x190/0x1b0) [<800ad534>] (__cobalt_kill) from [<800ad788>] (CoBaLt_kill+0x6c/0xcc) [<800ad788>] (CoBaLt_kill) from [<800ae248>] (ipipe_syscall_hook+0xfc/0x270) [<800ae248>] (ipipe_syscall_hook) from [<8008a14c>] (__ipipe_notify_syscall+0xa8/0x1a4) [<8008a14c>] (__ipipe_notify_syscall) from [<8000ef84>] (pipeline_syscall+0x8/0x24) Code: e5813084 e583c000 e8bd8070 e59421b0 (e592c004) ---[ end trace fcd211fc12a8e500 ]--- tests_integration_lib_ipc: threadobj.c:1344: threadobj_prologue: Assertion `current->magic == 0' failed. [2]+ Aborted./tests_integration_lib_ipc --session=rct cha # Best regards Stephane ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
[Xenomai] BUG: unable to handle kernel paging request at 00007ffccbd27e10 using rtnet -xenomai-3.0.5
Hi, I am using rtnet with xenomai-3.0.5 and soem ethercat code to communicate with EK1818 Ethercat coupler , I am getting the following message in my syslog and I am not able to get slave information. Jun 28 19:01:41 texsonics kernel: [ 2173.562482] BUG: unable to handle kernel paging request at 7ffccbd27e10 Jun 28 19:01:41 texsonics kernel: [ 2173.562518] IP: [] strncmp+0xc/0x50 Jun 28 19:01:41 texsonics kernel: [ 2173.562541] PGD 6d0f7067 Jun 28 19:01:41 texsonics kernel: [ 2173.562552] PUD 8484c067 Jun 28 19:01:41 texsonics kernel: [ 2173.562563] PMD 6d263067 Jun 28 19:01:41 texsonics kernel: [ 2173.562569] PTE 800099010867 Jun 28 19:01:41 texsonics kernel: [ 2173.562581] Jun 28 19:01:41 texsonics kernel: [ 2173.562589] Oops: 0001 [#1] SMP Jun 28 19:01:41 texsonics kernel: [ 2173.562601] Modules linked in: tdma(E) rtmac(E) rtcfg(E) rtcap(E) rt_loopback(E) rtudp(E) rtpacket(E) rtipv4(E) nls_utf8(E) isofs(E) uas(E) usb_storage(E) bnep(E) rfcomm(E) snd_hda_codec_hdmi(E) snd_hda_codec_realtek(E) intel_rapl(E) snd_hda_codec_generic(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) i915(E) coretemp(E) kvm_intel(E) snd_hda_intel(E) kvm(E) snd_hda_codec(E) snd_hda_core(E) drm_kms_helper(E) joydev(E) input_leds(E) snd_hwdep(E) drm(E) snd_pcm(E) snd_seq_midi(E) snd_seq_midi_event(E) snd_rawmidi(E) snd_seq(E) irqbypass(E) snd_seq_device(E) snd_timer(E) hci_uart(E) i2c_algo_bit(E) btbcm(E) btqca(E) btintel(E) fb_sys_fops(E) snd(E) bluetooth(E) syscopyarea(E) crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) aesni_intel(E) soundcore(E) rt_e1000e(E) sysfillrect(E) eeepc_wmi(E) Jun 28 19:01:41 texsonics kernel: [ 2173.562924] asus_wmi(E) sparse_keymap(E) aes_x86_64(E) sysimgblt(E) mxm_wmi(E) lrw(E) gf128mul(E) glue_helper(E) rtnet(E) acpi_als(E) serio_raw(E) ablk_helper(E) cryptd(E) intel_lpss_acpi(E) kfifo_buf(E) pinctrl_sunrisepoint(E) intel_lpss(E) shpchp(E) i2c_hid(E) video(E) industrialio(E) wmi(E) mei_me(E) mei(E) pinctrl_intel(E) mac_hid(E) parport_pc(E) ppdev(E) lp(E) parport(E) hid_generic(E) usbhid(E) hid(E) psmouse(E) e1000e(E) ptp(E) pps_core(E) ahci(E) libahci(E) fjes(E) Jun 28 19:01:41 texsonics kernel: [ 2173.563124] CPU: 0 PID: 2858 Comm: slave Tainted: GE 4.9.38-xenomai-3.0.5 #1 Jun 28 19:01:41 texsonics kernel: [ 2173.563152] Hardware name: System manufacturer System Product Name/H110M-D, BIOS 3601 12/12/2017 Jun 28 19:01:41 texsonics kernel: [ 2173.563182] I-pipe domain: Linux Jun 28 19:01:41 texsonics kernel: [ 2173.563195] task: 93b6c4866740 task.stack: bb53c1eb4000 Jun 28 19:01:41 texsonics kernel: [ 2173.563216] RIP: 0010:[] [] strncmp+0xc/0x50 Jun 28 19:01:41 texsonics kernel: [ 2173.563244] RSP: 0018:bb53c1eb7d58 EFLAGS: 00010202 Jun 28 19:01:41 texsonics kernel: [ 2173.563264] RAX: bb53c0917040 RBX: c0358780 RCX: 0072 Jun 28 19:01:41 texsonics kernel: [ 2173.563288] RDX: 0010 RSI: 7ffccbd27e10 RDI: 93b6c48c4004 Jun 28 19:01:41 texsonics kernel: [ 2173.563313] RBP: bb53c1eb7d58 R08: 0010 R09: 0008 Jun 28 19:01:41 texsonics kernel: [ 2173.563338] R10: 0001 R11: R12: 93b6c48c4000 Jun 28 19:01:41 texsonics kernel: [ 2173.563362] R13: 7ffccbd27e10 R14: 7ffccbd27e10 R15: aa19d3f0 Jun 28 19:01:41 texsonics kernel: [ 2173.563387] FS: 7fb983c68780() GS:93b77220() knlGS: Jun 28 19:01:41 texsonics kernel: [ 2173.563415] CS: 0010 DS: ES: CR0: 8005003b Jun 28 19:01:41 texsonics kernel: [ 2173.563435] CR2: 7ffccbd27e10 CR3: 80b92000 CR4: 003406f0 Jun 28 19:01:41 texsonics kernel: [ 2173.563460] Stack: Jun 28 19:01:41 texsonics kernel: [ 2173.563469] bb53c1eb7d80 c0352152 7ffccbd27e10 Jun 28 19:01:41 texsonics kernel: [ 2173.563500] 00054888 bb53c1eb7da8 c0352673 93b6d8682200 Jun 28 19:01:41 texsonics kernel: [ 2173.563532] 40180021 93b6c4866740 bb53c1eb7de0 c0355494 Jun 28 19:01:41 texsonics kernel: [ 2173.563564] Call Trace: Jun 28 19:01:41 texsonics kernel: [ 2173.563577] [] __rtdev_get_by_name+0x32/0x60 [rtnet] Jun 28 19:01:41 texsonics kernel: [ 2173.563602] [] rtdev_get_by_name+0x53/0xc0 [rtnet] Jun 28 19:01:41 texsonics kernel: [ 2173.563626] [] rt_socket_if_ioctl+0x34/0x240 [rtnet] Jun 28 19:01:41 texsonics kernel: [ 2173.563651] [] ? CoBaLt_fcntl+0x20/0x20 Jun 28 19:01:41 texsonics kernel: [ 2173.563671] [] rt_packet_ioctl+0x154/0x310 [rtpacket] Jun 28 19:01:41 texsonics kernel: [ 2173.563695] [] ? CoBaLt_fcntl+0x20/0x20 Jun 28 19:01:41 texsonics kernel: [ 2173.563715] [] rtdm_fd_ioctl+0xe1/0x210 Jun 28 19:01:41 texsonics kernel: [ 2173.563736] [] ? xnthread_switch_fpu+0x2d/0x40 Jun 28 19:01:41 texsonics kernel: [ 2173.563758] [] ? CoBaLt_fcntl+0x20/0x20 Jun 28 19:01:41 texsonics kernel: [ 2173.563778] [] CoBaLt_ioctl+0x10/0x20
Re: [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e)
On 06/28/2018 12:40 PM, Pintu Kumar wrote: >> FWIW, all of my rtnet fixes that went in since 3.0.6 have been tested on >> x86 exclusively. > > For us, even the xeno-test/net_udp fails on both x86/arm. > I also verified the udp test (loopback) that exists on rtnet repo: > https://git.code.sf.net/p/rtnet/code > Under: examples/generic/ > > Then, I also developed a common rtnet udp server/client using posix skin. > When I build and verify it on normal kernel it works fine. > But when I build it with Xenomai posix skin, I get the kernel oops on > both x86/arm. > > Now it fails with xenomai-3/next (latest) and with Kernel 4.9, on x86. > Earlier (1.5 months ago), I remember, rtnet loopback worked on x86_64 > with 3.0.6, with "nosmap". > If I run the same on Virtual Box Ubuntu 32-bit with same Kernel 4.9, it > works. > > So, I wonder, normally how do you verify rtnet sample application. Sorry, I don't maintain rtnet. > Please share the test applications and the steps you follow. > Run the smokey test suite over real x86 hw and a real ethernet interface, not the loopback. These were the tests conditions for the changes addressing the smap issue. I have no bandwidth to invest in rtnet at the moment, so you may want to confront and debug the issue directly. I'm sure that any proposal for a fix once the bug is spotted would be welcome, reviewed and commented on this list. -- Philippe. ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
Re: [Xenomai] Kernel oops during rtnet loopback usage on x86_64 (e1000e)
> FWIW, all of my rtnet fixes that went in since 3.0.6 have been tested on > x86 exclusively. For us, even the xeno-test/net_udp fails on both x86/arm. I also verified the udp test (loopback) that exists on rtnet repo: https://git.code.sf.net/p/rtnet/code Under: examples/generic/ Then, I also developed a common rtnet udp server/client using posix skin. When I build and verify it on normal kernel it works fine. But when I build it with Xenomai posix skin, I get the kernel oops on both x86/arm. Now it fails with xenomai-3/next (latest) and with Kernel 4.9, on x86. Earlier (1.5 months ago), I remember, rtnet loopback worked on x86_64 with 3.0.6, with "nosmap". If I run the same on Virtual Box Ubuntu 32-bit with same Kernel 4.9, it works. So, I wonder, normally how do you verify rtnet sample application. Please share the test applications and the steps you follow. Thanks, Pintu On Wed, Jun 27, 2018 at 11:40 PM Philippe Gerum wrote: > > On 06/27/2018 07:29 PM, Pintu Kumar wrote: > > On Wed, Jun 27, 2018 at 10:47 PM Greg Gallagher > > wrote: > >> > >> I don't think Beaglebone is supported currently in RTNet. > >> > > > > But I am just checking loopback interface with 127.0.0.1 > > I hope that should work on all boards and arch, even without > > installing the net driver. > > > > You must be the first and only user giving any feedback about rtnet over > ARM if my memory serves me well. So either all others have been hiding > behind for all these years, or you may be the only specimen of that species. > > FWIW, all of my rtnet fixes that went in since 3.0.6 have been tested on > x86 exclusively. > > -- > Philippe. ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
Re: [Xenomai] Some Problem with build sam5d36 IMAGE
On 06/28/2018 03:31 AM, 10年 wrote: > ./prepare-kernel.sh --arch=arm > --adeos=/usr/src/linux/ipipe-core-4.14.36-arm-1.patch > --linux=/usr/src/linux/linux-4.14.36 > make menuconfig and I load file in > /usr/src/linux/linux-4.14.36/arch/arm/configs/sama5_defconfig --and save in > /usr/src/linux/linux-4.14.36/.config > > make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- bzImage modules > > That's all I do, while building, some errors coming that : > > > AS arch/arm/xenomai/switch.o > CC arch/arm/xenomai/syscall.o > In file included from arch/arm/xenomai/include/asm/xenomai/syscall.h:29:0, > from arch/arm/xenomai/syscall.c:22: > ./include/asm-generic/xenomai/syscall.h: In function 'cobalt_copy_from_user': > ./include/asm-generic/xenomai/syscall.h:49:3: error: implicit declaration of > function '__copy_from_user_inatomic' [-Werror=implicit-function-declaration] >__xn_copy_from_user(dst, src, size)) ? -EFAULT : 0; >^ > ./include/asm-generic/xenomai/syscall.h: In function 'cobalt_copy_to_user': > ./include/asm-generic/xenomai/syscall.h:56:3: error: implicit declaration of > function '__copy_to_user_inatomic' [-Werror=implicit-function-declaration] >__xn_copy_to_user(dst, src, size)) ? -EFAULT : 0; >^ > cc1: some warnings being treated as errors > scripts/Makefile.build:328: recipe for target 'arch/arm/xenomai/syscall.o' > failed > make[1]: *** [arch/arm/xenomai/syscall.o] Error 1 > Makefile:1040: recipe for target 'arch/arm/xenomai' failed > make: *** [arch/arm/xenomai] Error 2 > > > > > Can any body help me ? > Support for kernel 4.14 was introduced in Xenomai 3.0.7. -- Philippe. ___ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
