Re: kvm fpu warning on 4.14.89

2019-04-05 Thread cagnulein via Xenomai
Thank you, on Monday morning I will fire it up! :) R. Il ven 5 apr 2019, 20:29 Jan Kiszka ha scritto: > On 05.04.19 15:27, Jan Kiszka wrote: > > On 05.04.19 11:42, Jan Kiszka wrote: > >> On 05.04.19 10:44, cagnulein wrote: > >>> Hi, yes I double checked the patch and it's applied correctly. >

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread Jan Kiszka via Xenomai
On 05.04.19 15:27, Jan Kiszka wrote: On 05.04.19 11:42, Jan Kiszka wrote: On 05.04.19 10:44, cagnulein wrote: Hi, yes I double checked the patch and it's applied correctly. Here you can find my config. CONFIG_DEBUG_STACKOVERFLOW is disabled. I can't get the uart on this system, is there any

Re: Checkpatch errors

2019-04-05 Thread Jan Kiszka via Xenomai
On 05.04.19 16:05, Roman Stratiienko wrote: > Hello Jan, > > Let me share some of checkpatch findings after recent update: > > > Commit 67549038b677 ("rtnet: e1000e: Account for timer API changes") >

Checkpatch errors

2019-04-05 Thread Roman Stratiienko via Xenomai
Hello Jan, Let me share some of checkpatch findings after recent update: Commit 67549038b677 ("rtnet: e1000e: Account for timer API changes") WARNING:

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread Jan Kiszka via Xenomai
On 04.04.19 21:05, Jan Kiszka wrote: > On 21.03.19 09:01, Jan Kiszka wrote: >> On 21.03.19 08:04, cagnulein wrote: >>> I've got a similar issue even with the 4.9.146 with a kvm guest on and >>> latency >>> on too. It's quite deterministic. Any idea? >>> >> >> I didn't trigger your trace yet, but

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread Jan Kiszka via Xenomai
On 05.04.19 11:42, Jan Kiszka wrote: > On 05.04.19 10:44, cagnulein wrote: >> Hi, yes I double checked the patch and it's applied correctly. >> Here you can find my config. >> >> CONFIG_DEBUG_STACKOVERFLOW is disabled. >> >> I can't get the uart on this system, is there any other way to catch log

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread cagnulein via Xenomai
I'll give it a shot, I will let you know on Monday. Thanks and good weekend R. Il ven 5 apr 2019, 11:42 Jan Kiszka ha scritto: > On 05.04.19 10:44, cagnulein wrote: > > Hi, yes I double checked the patch and it's applied correctly. > > Here you can find my config. > > > >

[RFC][PATCH] ci: Pull kernels from git and enhance coverage

2019-04-05 Thread Jan Kiszka via Xenomai
From: Jan Kiszka This switches to cloning the ipipe tree, rather than downloading patches. It allows to test also unreleased ipipe revisions. The test matrix is enhanced by - 4.19-arm - 4.14.78-arm64 - 4.14.y-x86 - 4.4.y-x86 - 4.4.y-arm The 4.1-arm build is dropped because that kernel is

[PATCH] rtnet: igb: Account for timer API changes

2019-04-05 Thread Jan Kiszka via Xenomai
From: Jan Kiszka init_timer was removed in 4.15. Signed-off-by: Jan Kiszka --- kernel/drivers/net/drivers/igb/igb_main.c | 22 ++ 1 file changed, 22 insertions(+) diff --git a/kernel/drivers/net/drivers/igb/igb_main.c b/kernel/drivers/net/drivers/igb/igb_main.c index

Re: EMSGSIZE whith send on RTcan socket

2019-04-05 Thread Jan Kiszka via Xenomai
On 05.04.19 11:31, Johannes Holtz via Xenomai wrote: > Hi, > > While sending a multitude of SDOs via RTcan I get some EMSGSIZE errors. There > is > no obvious pattern to the occurrences and most of the messages are sent OK. I > checked the parameters that I use and each frame is send with the

EMSGSIZE whith send on RTcan socket

2019-04-05 Thread Johannes Holtz via Xenomai
Hi, While sending a multitude of SDOs via RTcan I get some EMSGSIZE errors. There is no obvious pattern to the occurrences and most of the messages are sent OK. I checked the parameters that I use and each frame is send with the same size ( sizeof(can_frame_t) ) and each frame has a dlc of 8.

[PATCH] rtnet: e1000: Convert timers to delay-work

2019-04-05 Thread Jan Kiszka via Xenomai
From: Jan Kiszka Like in upstream. Also avoids breakage on newer kernels that removed init_timer. Signed-off-by: Jan Kiszka --- kernel/drivers/net/drivers/e1000/e1000.h | 7 ++- kernel/drivers/net/drivers/e1000/e1000_main.c | 91 ++- 2 files changed, 50

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread cagnulein via Xenomai
ust > discovered a compilation issue on that kernel version). > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux > -- next part -- A non-text attachment was scrubbed... Name: config.4.14.89 Type: application/octet-stream Size: 173380 bytes Desc: not available URL: <http://xenomai.org/pipermail/xenomai/attachments/20190405/228690c4/attachment.obj>

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread Jan Kiszka via Xenomai
On 05.04.19 08:20, cagnulein wrote: > Hi Jan, thanks for your patch. > I've just tried but I have the same issue: I start a kvm guest (windows 10 > iot > 2019) and it works, but when I start a latency test the whole system hangs > completely. > > Could i give you more info in some way? OK...

Re: kvm fpu warning on 4.14.89

2019-04-05 Thread cagnulein via Xenomai
Hi Jan, thanks for your patch. I've just tried but I have the same issue: I start a kvm guest (windows 10 iot 2019) and it works, but when I start a latency test the whole system hangs completely. Could i give you more info in some way? R. Il gio 4 apr 2019, 21:05 Jan Kiszka ha scritto: > On