From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: xenomai <xenomai@xenomai.org>
Subject: [Xenomai] Xenomai 3.0.3 is broken in my system (was Regarding Xenomai and RTNET)
Date: Mon, 03 Oct 2016 18:12:12 +0200 [thread overview]
Message-ID: <2990549.hKSmcVRoDB@indiana> (raw)
Hi,
I have been making some tests and I have arrived to the conclusion that the PC
that I would like to install Xenomai and RTNET doesn't like it.
It's a PC with a motherboard Gigabyte Q170M-D3H-CF. I'm running 4.1.18 with
xenomai 3.0.3. AFAIK, the xenomai tests works. However, when I try to run
RTNET, I got crashes:
BUG: unable to handle kernel paging request at 00007f47ea0ef878
IP: [<ffffffffa0231580>] rt_udp_ioctl+0x50/0x74 [rtudp]
PGD 458887067 PUD 4590a1067 PMD 45921f067 PTE 8000000438863867
Oops: 0001 [#1] PREEMPT SMP
Modules linked in: rt_igb rt_loopback rtcfg rtudp rtipv4 rtmac rtpacket rtnet
e100 mii ctr ccm binfmt_misc nfsd
CPU: 4 PID: 6773 Comm: LWRJointPositio Not tainted 4.1.18-xenomai-3.0.3 #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Q170M-D3H-
CF, BIOS F1 10/13/2015
task: ffff880459a26010 ti: ffff880459a38000 task.ti: ffff880459a38000
RIP: 0010:[<ffffffffa0231580>] [<ffffffffa0231580>] rt_udp_ioctl+0x50/0x74
[rtudp]
RSP: 0018:ffff880459a3be08 EFLAGS: 00010246
RAX: 00007f47ea0ef870 RBX: ffff880458d59400 RCX: ffff880458d59440
RDX: 0000000000000000 RSI: 0000000040100022 RDI: ffff880458d59400
RBP: 0000000000000003 R08: ffff880460297420 R09: 000000000000004e
R10: 00000000000000dc R11: ffff880459a3bdc0 R12: ffff880459a26010
R13: ffffc90001f05008 R14: 0000000040100022 R15: ffffffff81b85ec0
FS: 00007f47ea0f0700(0000) GS:ffff880460200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f47ea0ef878 CR3: 000000045890c000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
I-pipe domain Linux
Stack:
ffffffffa0231535 ffffffff8116fb70 ffff880459a265c0 00007f47ea0ef870
ffff8804599975d0 0000000000000010 ffff880459a3beb8 ffff880459a3be48
0000000000000002 ffff880459a26010 00007f47ea0ef870 ffff880459a26010
Call Trace:
[<ffffffffa0231535>] ? rt_udp_ioctl+0x5/0x74 [rtudp]
[<ffffffff8116fb70>] ? rtdm_fd_ioctl+0x100/0x270
[<ffffffff81174b40>] ? CoBaLt_fcntl+0x20/0x20
[<ffffffff81174b40>] ? CoBaLt_fcntl+0x20/0x20
[<ffffffff81174b50>] ? CoBaLt_ioctl+0x10/0x20
[<ffffffff81174b45>] ? CoBaLt_ioctl+0x5/0x20
[<ffffffff8118450a>] ? ipipe_syscall_hook+0x11a/0x360
[<ffffffff81108da7>] ? __ipipe_notify_syscall+0xe7/0x1d0
[<ffffffff81107185>] ? __ipipe_restore_root_nosync+0x5/0x30
[<ffffffff8158fb34>] ? pipeline_syscall+0x9/0x16
Code: 23 00 10 40 75 15 8b 50 08 48 8b 30 48 89 cf 48 83 c4 08 e9 a3 fd ff ff
0f 1f 00 48 89 c2 48 83 c4 08 e9 5
RIP [<ffffffffa0231580>] rt_udp_ioctl+0x50/0x74 [rtudp]
RSP <ffff880459a3be08>
CR2: 00007f47ea0ef878
---[ end trace 085d23e71de3ae4b ]---
The funny (or ugly thing) is that, same kernel (I'm using debian packages) and
almost the same Xenomai (compiled in each machine but with the same configure
options) works in another similar box, with the same network cards (rt_igb).
My application doesn't crash.
I also have tested another network card (rt_e1000_new) with the same core
dump.
So, any idea how can I find some light in this? I don't know if it's a rtnet
issue of a combination of kernel and hardware issue.
Best regards,
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20161003/916f72c2/attachment.sig>
next reply other threads:[~2016-10-03 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 16:12 Leopold Palomo-Avellaneda [this message]
2016-10-04 15:36 ` [Xenomai] Xenomai 3.0.3 is broken in my system (was Regarding Xenomai and RTNET) Leopold Palomo-Avellaneda
2016-10-05 10:39 ` Jan Kiszka
2016-10-05 12:42 ` Leopold Palomo-Avellaneda
2016-10-05 12:45 ` Jan Kiszka
2016-10-05 13:00 ` Leopold Palomo-Avellaneda
2016-10-05 13:12 ` Jan Kiszka
2016-10-06 9:51 ` [Xenomai] About SMAP (was Re: Xenomai 3.0.3 is broken in my system) Leopold Palomo-Avellaneda
2016-10-06 11:50 ` Jan Kiszka
2016-10-06 17:24 ` Leopold Palomo-Avellaneda
2016-10-06 17:30 ` Philippe Gerum
2016-10-06 17:44 ` Leopold Palomo-Avellaneda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2990549.hKSmcVRoDB@indiana \
--to=leo@alaxarxa.net \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.