v4.19.50-cip3-rt2

cip-dev Pavel Machek 6 participants 18 messages Jul 23, 2019 – Jul 29, 2019

Share & tools

Pavel Machek

author

2019-07-23 12:40 UTC #0 lore raw

Hi!

4.19.50-cip3-rt2 should be available at kernel.org. It performs well on socfpga (Altera-Terasic-Deo-NanoAltera); but not so well on iwg20m (r8a7743-iwg20d-q7) board.

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt

And their content should be identical. I attempted to tag it in a way consistent with previous releases, and I attempted to sign a tag.

Best regards,
Pavel

Signature · 9 lines

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190723/e2d816ca/attachment.sig>

Jan Kiszka

2019-07-23 13:53 UTC #1 lore raw

Quoted 6 lines · Pavel Machek

Hi!
4.19.50-cip3-rt2 should be available at kernel.org. It performs well on socfpga (Altera-Terasic-Deo-NanoAltera); but not so well on iwg20m (r8a7743-iwg20d-q7) board.

Thanks!

Quoted 8 lines

Trees are available at
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt
And their content should be identical. I attempted to tag it in a way consistent with previous releases, and I attempted to sign a tag.

...but you didn't push the tag yet? Or is this WiP?

Jan

Signature · 2 lines

Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Pavel Machek

author

2019-07-23 21:06 UTC #2 lore raw

Hi!

Quoted 10 lines

Quoted 8 lines
Trees are available at
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt
And their content should be identical. I attempted to tag it in a way consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?

Sorry, I forgot I need to push the tag. It should be fixed now.

Best regards,
Pavel

Signature · 9 lines

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190723/9d168c33/attachment.sig>

Zoran S

2019-07-24 03:45 UTC #3 lore raw

I finally was able to make the viable .config... For the previous rt-kernel for BBB.

root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux

It was very tough and rough... But I have it! Now I need to abandon this effort, since I have another immediate things to do!

Well...

Zoran
_______

Quoted 25 lines · Pavel Machek

Hi!
Quoted 10 lines
Quoted 8 lines
Trees are available at
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt-rebase
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt
And their content should be identical. I attempted to tag it in a way consistent with previous releases, and I attempted to sign a tag.
...but you didn't push the tag yet? Or is this WiP?
Sorry, I forgot I need to push the tag. It should be fixed now.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

Pavel Machek

author

2019-07-24 11:53 UTC #4 lore raw

Hi!

Quoted 9 lines

I finally was able to make the viable .config... For the previous rt-kernel for BBB.
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
It was very tough and rough... But I have it! Now I need to abandon this effort, since I have another immediate things to do!

No problem. You should be able to use same .config with the new kernel...

Best regards,
Pavel

Signature · 9 lines

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190724/6b99cda7/attachment-0001.sig>

Zoran S

2019-07-24 13:00 UTC #5 lore raw

Quoted 2 lines

No problem. You should be able to use same .config with the new kernel...

U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some problems to do rt-tests (connecting BBB target to my VM).

Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill publish the results) . Then I need to leave it for the time been.

Zoran
_______

Quoted 21 lines · Pavel Machek

Hi!
Quoted 9 lines
I finally was able to make the viable .config... For the previous rt-kernel for BBB.
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
It was very tough and rough... But I have it! Now I need to abandon this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new kernel...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Zoran S

2019-07-24 16:06 UTC #6 lore raw

(limitations): I could NOT connect with ETH to target (something is wrongly set with my local.conf for YOCTO rootfs)...

Here is my approximate recipe for rootfs I am using for the test (initramfs) for your inspection (it is thud, local.conf moved to warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf

More or/and less, here are results after approximately 63 minutes of running rt-tests:

root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned about MAX over > 900 ns!

On 4.4 RT kernel I had some much better # such as: Min: 19 Act:
44 Avg: 42 Max: 81

I need to do more... No time anymore now!

Best Regards,
Zoran
_______

Quoted 35 lines · Zoran S

Quoted 3 lines
No problem. You should be able to use same .config with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some problems to do rt-tests (connecting BBB target to my VM).
Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill publish the results) . Then I need to leave it for the time been.
Zoran
_______
Quoted 21 lines · Pavel Machek
Hi!
Quoted 9 lines
I finally was able to make the viable .config... For the previous rt-kernel for BBB.
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
It was very tough and rough... But I have it! Now I need to abandon this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new kernel...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

daniel.sangorrin at toshiba.co.jp

2019-07-25 00:22 UTC #7 lore raw

Hello Zoran

Quoted 3 lines

From: cip-dev-bounces at lists.cip-project.org <cip-dev- (limitations): I could NOT connect with ETH to target (something is wrongly set with my local.conf for YOCTO rootfs)...

Why don't you use ISAR CIP Core?
https://gitlab.com/cip-project/cip-core/isar-cip-core

Thanks,
Daniel

Quoted 79 lines

Here is my approximate recipe for rootfs I am using for the test (initramfs) for your inspection (it is thud, local.conf moved to warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf
More or/and less, here are results after approximately 63 minutes of running rt-tests:
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90
MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned about MAX over > 900 ns!
On 4.4 RT kernel I had some much better # such as: Min: 19 Act:
44 Avg: 42 Max: 81
I need to do more... No time anymore now!
Best Regards,
Zoran
_______
Quoted 7 lines · Zoran S
Quoted 3 lines
No problem. You should be able to use same .config with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some problems to do rt-tests (connecting BBB target to my VM).
Quoted 28 lines
Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill publish the results) . Then I need to leave it for the time been.
Zoran
_______
Quoted 21 lines · Pavel Machek
Hi!
Quoted 9 lines
I finally was able to make the viable .config... For the previous rt-kernel for BBB.
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
It was very tough and rough... But I have it! Now I need to abandon this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new kernel...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

Zoran S

2019-07-25 06:44 UTC #8 lore raw

Quoted 2 lines

Why don't you use ISAR CIP Core?
https://gitlab.com/cip-project/cip-core/isar-cip-core

With all due respect (and I do really respect prominent CIP founders), I need to make this problem solved solely by myself...

But, anyway, thank you for the advise! :-)

Zoran
_______

Quoted 92 lines · On Thu, Jul 25, 2019 at 2:22 AM <[email protected]> wrote:

Hello Zoran
Quoted 3 lines
From: cip-dev-bounces at lists.cip-project.org <cip-dev- (limitations): I could NOT connect with ETH to target (something is wrongly set with my local.conf for YOCTO rootfs)...
Why don't you use ISAR CIP Core?
https://gitlab.com/cip-project/cip-core/isar-cip-core
Thanks,
Daniel
Quoted 79 lines
Here is my approximate recipe for rootfs I am using for the test (initramfs) for your inspection (it is thud, local.conf moved to warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf
More or/and less, here are results after approximately 63 minutes of running rt-tests:
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90
MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned about MAX over > 900 ns!
On 4.4 RT kernel I had some much better # such as: Min: 19 Act:
44 Avg: 42 Max: 81
I need to do more... No time anymore now!
Best Regards,
Zoran
_______
Quoted 7 lines · Zoran S
Quoted 3 lines
No problem. You should be able to use same .config with the new kernel...
U R targeting 4.19.50-cip3-rt2... I do agree 100%, but I have some problems to do rt-tests (connecting BBB target to my VM).
Quoted 28 lines
Please, stay tuned. I'll resolve these problems ASAP (if ?, then Ill publish the results) . Then I need to leave it for the time been.
Zoran
_______
Quoted 21 lines · Pavel Machek
Hi!
Quoted 9 lines
I finally was able to make the viable .config... For the previous rt-kernel for BBB.
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
It was very tough and rough... But I have it! Now I need to abandon this effort, since I have another immediate things to do!
No problem. You should be able to use same .config with the new kernel...
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

Pavel Machek

author

2019-07-26 21:05 UTC #9 lore raw

In reply to Zoran S

Quoted 11 lines · Zoran S

(limitations): I could NOT connect with ETH to target (something is wrongly set with my local.conf for YOCTO rootfs)...
Here is my approximate recipe for rootfs I am using for the test (initramfs) for your inspection (it is thud, local.conf moved to warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf
More or/and less, here are results after approximately 63 minutes of running rt-tests:

Quoted 15 lines

root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90

Your log is corrupted, see?

If it was real, it would be

Max: 905
Max: 90

But you have

Max:  905
Max:  90

Notice the whitespace.

Quoted 2 lines

MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned about MAX over > 900 ns!

It is usec, not nsec, AFAICT.

Best regards,
Pavel

Signature · 9 lines

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190726/fc1ed8b0/attachment.sig>

Zoran S

2019-07-27 02:19 UTC #10 lore raw

Quoted 1 line

Your log is corrupted, see?

You are correct, I should write that these are preliminary WTH/ad-hoc results (I need to fix/rerun these in the correct setup, I know).

Quoted 1 line

It is usec, not nsec, AFAICT.

Again, correct. I wrote nsec instead usec, having in mind INTEL technology per asm instruction. INTEL illusions/delusions in my brain. I am trying to catch up on armv7, A8 and A9, since these gadgets started ruling the embedded industry.

Thank you,
Zoran
_______

Quoted 54 lines · Pavel Machek

Quoted 11 lines · Zoran S
(limitations): I could NOT connect with ETH to target (something is wrongly set with my local.conf for YOCTO rootfs)...
Here is my approximate recipe for rootfs I am using for the test (initramfs) for your inspection (it is thud, local.conf moved to warrior):
https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-warrior/local.conf
More or/and less, here are results after approximately 63 minutes of running rt-tests:
Quoted 15 lines
root at beaglebone:~# uname -a
Linux beaglebone 4.19.13-cip1-rt1 #1 PREEMPT RT Tue Jul 23 12:18:18 GMT 2019 armv7l GNU/Linux
_______
policy: fifo: loadavg: 291.28 287.63 267.78 21/486 30014
policy: fifo: loadavg: 186.97 215.90 243.41 5/458 22788
policy: fifo: loadavg: 248.16 243.95 244.63 194/486 8800
policy: fifo: loadavg: 283.55 240.50 243.74 9/318 2383
T: 0 (13903) P:80 I:1000 C:3942593 Min: 19 Act: 52 Avg: 45 Max: 93
T: 0 (13903) P:80 I:1000 C:3785664 Min: 19 Act: 44 Avg: 45 Max: 935
T: 0 (13903) P:80 I:1000 C:3716107 Min: 19 Act: 60 Avg: 45 Max: 936
policy: fifo: loadavg: 222.11 176.72 90.66 5/213 21249
T: 0 (13903) P:80 I:1000 C:2213895 Min: 19 Act: 38 Avg: 46 Max: 905
T: 0 (13903) P:80 I:1000 C: 181403 Min: 21 Act: 49 Avg: 45 Max: 90
T: 0 (13903) P:80 I:1000 C: 181320 Min: 21 Act: 29 Avg: 45 Max: 90
Your log is corrupted, see?
If it was real, it would be
Max: 905
Max: 90
But you have
Max:  905
Max:  90
Notice the whitespace.
Quoted 2 lines
MIN 19 ns, MAX 936 ns (3x over 900 ns)... I would be really concerned about MAX over > 900 ns!
It is usec, not nsec, AFAICT.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Pavel Machek

author

2019-07-23 21:12 UTC #11 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

In reply to Pavel Machek

Hi!

v4.4.185-cip35-rt24 should be available at kernel.org.

Daniel says:

# in the v4.4-rt is still a problem with f01f17d3705b ("mm,
# vmstat: make quiet_vmstat lighter"). It is needed to boot on x86_64
# but it breaks on NVIDIA's boards, e.g. Jetson. Unfortunately, I don't
# have a NVIDIA board in my lab to figure out what is missing. So I
# suspect there is a still a problem hidden in the current v4.4-rt tree.

I did nothing to solve that problem. If someone uses NVIDIA boards, let me know.

Trees are available at

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt-rebase

https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt

And their content should be identical. It should be tagged and tag should be signed.

Best regards,
Pavel

Signature · 9 lines

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190723/c22183e0/attachment.sig>

Daniel Wagner

2019-07-25 08:50 UTC #12 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

Hi,

Quoted 11 lines · Pavel Machek

v4.4.185-cip35-rt24 should be available at kernel.org.

Daniel says:

# in the v4.4-rt is still a problem with f01f17d3705b ("mm,
# vmstat: make quiet_vmstat lighter"). It is needed to boot on x86_64
# but it breaks on NVIDIA's boards, e.g. Jetson. Unfortunately, I don't
# have a NVIDIA board in my lab to figure out what is missing. So I
# suspect there is a still a problem hidden in the current v4.4-rt tree.

I did nothing to solve that problem. If someone uses NVIDIA boards, let me know.

I still try to get hands on a NVIDIA board. They are not terrible expensive but I still don't want to buy it myself :)

So if someone is willing to lend me a board, I can't try to reproduce it.

Thanks,
Daniel

Jan Kiszka

2019-07-25 09:06 UTC #13 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

Quoted 12 lines · Daniel Wagner

Hi,

Quoted 9 lines · Pavel Machek

v4.4.185-cip35-rt24 should be available at kernel.org.

Daniel says:

# in the v4.4-rt is still a problem with f01f17d3705b ("mm,
# vmstat: make quiet_vmstat lighter"). It is needed to boot on x86_64
# but it breaks on NVIDIA's boards, e.g. Jetson. Unfortunately, I don't
# have a NVIDIA board in my lab to figure out what is missing. So I
# suspect there is a still a problem hidden in the current v4.4-rt tree.

Quoted 7 lines

Quoted 2 lines
I did nothing to solve that problem. If someone uses NVIDIA boards, let me know.
I still try to get hands on a NVIDIA board. They are not terrible expensive but I still don't want to buy it myself :)
So if someone is willing to lend me a board, I can't try to reproduce it.

Which one do you need? I have a TK1 in reach, Ralf should have a TX1 with the potential of remote access.

Jan

Signature · 2 lines

Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Daniel Wagner

2019-07-25 09:12 UTC #14 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

Hi Jan,

Quoted 4 lines · Jan Kiszka

Quoted 1 line
So if someone is willing to lend me a board, I can't try to reproduce it.
Which one do you need? I have a TK1 in reach, Ralf should have a TX1 with the potential of remote access.

It should be reproducable on a TK1:

https://lore.kernel.org/stable/f32de22f-c928-2eaa-ee3f-d2b26c184dd4 at nvidia.com/

So if I could get hands on one of those, it would really help.

Remote access is also good, if the uplink from the board is reasonable fast. I finally got a fast uplink (400MBit/s) :)

Thanks,
Daniel

Ralf Ramsauer

2019-07-25 11:42 UTC #15 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

Hi,

Quoted 9 lines · Daniel Wagner

Hi Jan,
Quoted 6 lines · Jan Kiszka
Quoted 2 lines
So if someone is willing to lend me a board, I can't try to reproduce it.
Which one do you need? I have a TK1 in reach, Ralf should have a TX1 with the
potential of remote access.

Yep, he does.

Quoted 7 lines

It should be reproducable on a TK1:
https://lore.kernel.org/stable/f32de22f-c928-2eaa-ee3f-d2b26c184dd4 at nvidia.com/
So if I could get hands on one of those, it would really help.

You can either get your hands dirty on your own, or you simply give me a .config together with a commit hash and a short description what I should test. The latter is probably the easier choice, if the test isn't that complex.

Quoted 3 lines

Remote access is also good, if the uplink from the board is reasonable fast. I finally got a fast uplink (400MBit/s) :)

Come on, 400Mbit/s... But it should be fast enough to tease our 1GBit/s DFN network ;-)

Ralf

Quoted 3 lines

Thanks,
Daniel

Daniel Wagner

2019-07-26 17:27 UTC #16 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

In reply to Daniel Wagner

Hi,

Quoted 1 line

It should be reproducable on a TK1:

Today I got from Jan the TK1 for testing. After the usual WTF with u-boot and kernel configs, I am able to reproduce it. Let's see what's going wrong.

Thanks,
Daniel

Daniel Wagner

2019-07-29 10:23 UTC #17 lore raw

[cip-dev] [ANNOUNCE] v4.4.185-cip35-rt24

Quoted 1 line

Let's see what's going wrong.

Identified the problem. It was a missing dependency 587198ba5206 ("vmstat: Remove BUG_ON from vmstat_update").

Need to run a few more tests before sending Greg an updated series for stable v4.4.