Re: I-pipe 4.4.x-cip

Hi Jan, On Thu, Dec 20, 2018 at 05:32:37PM +0100, Jan Kiszka wrote: > Hi all, > > just a quick note that I started a 4.4-cip based I-pipe tree: > > https://gitlab.denx.de/Xenomai/ipipe/tree/ipipe-4.4.y-cip > > So far it's just a merge of ipipe-4.4.y @ipipe-core-4.4.166-x86-12 with the > CIP

Re: Stack dump on ipipe 4.9.135-7 x86_64

On Fri, 2018-12-21 at 16:11 +0100, Mauro Salvini via Xenomai wrote: > On Fri, 2018-12-21 at 14:51 +0100, Henning Schild wrote: > > Am Thu, 20 Dec 2018 10:10:29 +0100 > > schrieb Jan Kiszka : > > > > > On 20.12.18 09:28, Mauro Salvini via Xenomai wrote: > > > > Hi all, > > > > > > > > I'm testing

Re: Stack dump on ipipe 4.9.135-7 x86_64

1.357244] [] ? xnclock_tick+0x1a9/0x2c0 [ 191.357261] [] ? xnintr_core_clock_handler+0x2fa/0x310 [ 191.357264] [] ? dispatch_irq_head+0x8a/0x120 [ 191.357267] [] ? __ipipe_handle_irq+0x85/0x1b0 [ 191.357270] [] ? apic_timer_interrupt+0x89/0xb0 [ 191.357273] [] ? crc_array+0x1e/0x1e [crc32c_intel] [ 191.357275] [] ? crc32c_pcl_intel_update+0x53/0x60 [crc32c_intel] [ 191.357278] [] ? jbd2_journal_commit_transaction+0x9e0/0x1850 [jbd2] [ 191.357281] [] ? __switch_to_asm+0x40/0x70 [ 191.357284] [] ? try_to_del_timer_sync+0x4f/0x80 [ 191.357287] [] ? kjournald2+0xe2/0x290 [jbd2] [ 191.357289] [] ? wake_up_atomic_t+0x30/0x30 [ 191.357292] [] ? commit_timeout+0x10/0x10 [jbd2] [ 191.357295] [] ? kthread+0xf5/0x110 [ 191.357298] [] ? __switch_to_asm+0x40/0x70 [ 191.357300] [] ? kthread_park+0x60/0x60 [ 191.357303] [] ? ret_from_fork+0x55/0x60 [ 191.357306] ---[ end trace 4ff3f5c62c8143d3 ]--- -- next part -- A non-text attachment was scrubbed... Name: config Type: text/x-mpsub Size: 186495 bytes Desc: not available URL: <http://xenomai.org/pipermail/xenomai/attachments/20181221/8180c64e/attachment.bin>

Re: Stack dump on ipipe 4.9.135-7 x86_64

Am Thu, 20 Dec 2018 10:10:29 +0100 schrieb Jan Kiszka : > On 20.12.18 09:28, Mauro Salvini via Xenomai wrote: > > Hi all, > > > > I'm testing Xenomai 3 on an Intel Braswell board (Atom x5-E8000). > > I'm using ipipe kernel at last commit from [1], branch ipipe-4.9.y, > > 64bit build on a Debian

[PATCH] cobalt/x86: fix condition in eager fpu code for kernels < 4.14

From: Henning Schild We should mark the current task as not owning the fpu anymore if it does actually own the fpu, not if the fpu itself is active. Fixes cb52e6c7438fa Reported-by: Mauro Salvini Signed-off-by: Henning Schild --- kernel/cobalt/arch/x86/thread.c | 2 +- 1 file changed, 1

[I-PIPE] ipipe-core-4.14.89-x86-2 released

Download URL: https://xenomai.org/downloads/ipipe/v4.x/x86/ipipe-core-4.14.89-x86-2.patch Repository: https://git.xenomai.org/ipipe-x86 Release tag: ipipe-core-4.14.89-x86-2

RE: Cobalt Preemption of kernel update_fast_timekeeper can cause deadlocks

n Firmenbuchgericht/ Court of registry: Handelsgericht Wien Firmenbuchnummer/ Company registration: FN 61833 g DVR: 0605077 UID-Nr.: ATU14756806 Thank You ____ -- next part -- An embedded and charset-unspecified text was scrubbed... Name: cobalt_preload_helper.c URL: <http://xenomai.org/pipermail/xenomai/attachments/20181221/fefe0671/attachment.c>

Re: ipipe-arm64 kernel issue

On Thu, Dec 13, 2018 at 6:20 PM Steve Pavao via Xenomai wrote: > > > > On Dec 12, 2018, at 5:21 AM, Philippe Gerum wrote: > > > > On 12/11/18 10:25 PM, Steve Pavao via Xenomai wrote: > >> I have 2 different, basic apps that oops in a very similar way on > >> ipipe-arm64 running on R Pi 3B. One

Re: RTnet tests in smokey

On Fri, Dec 14, 2018 at 5:54 PM Jan Kiszka via Xenomai wrote: > > Hi all, > > while debugging that list corruption in Rtnet I noticed that the related > smokey tests are in a rather improvable state. First of all, they are > never working automatically unless the rtnet core is built into the >