linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Fuchs <mfuchs@ma-fu.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: 3.12.6-rt9 on AM335x (armv7)
Date: Wed, 01 Jan 2014 17:37:28 +0100	[thread overview]
Message-ID: <52C44448.3030405@ma-fu.de> (raw)

Hi,

I did a setup with 3.12.6-rt9 kernel on a Beaglebone board
with an TI AM335x CPU running at fixed 720MHz. The kernel uses the 
omap2plus_defconfig configuration that comes with this kernel with 
additional CONFIG_PREEMPT_RT_FULL switched on.

I am observing some strange max. latencies when comparing with kernel 
3.2.45-rt66. The results of a similiar system can be found on the OSADL lab
site (https://www.osadl.org/Latency-plot-of-system-in-rack-7-slot.qa-latencyplot-r7s5.0.html).

With "cyclictest -p99 -m -n -i200 -h400 -q -l10000000" I get
...
# Min Latencies: 00013
# Avg Latencies: 00062
# Max Latencies: 04664
...

Also the latency does not differ much from that when doing a flood ping against 
the system as simple stress.

3.2.45-rt66 comes with a max. latency of 118us! So I expect something to be wrong with 3.12.6-rt9
at least on armv7 or especially this device (max. lat. 4664us).

I also noticed an issue with the on-chip ethernet when CONFIG_PREEMPT_RT_FULL is
switched on with this kernel:

I also noticed that the 3.12.6-rt9 with enabled 
[    2.817024] net eth0: initializing cpsw version 1.12 (0)
[    2.825269] net eth0: phy found : id is : 0x7c0f1
[    2.830713] libphy: PHY 4a101000.mdio:01 not found
[    2.835777] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   12.846394] Waiting up to 110 more seconds for network.
[   22.846147] Waiting up to 100 more seconds for network.
...

Finally networking is fine. But I need to wait for 110 seconds :-)

Prior testing with 3.12.6-rt9 I did the same test with 3.12.5-rt7. Same results.
But without CONFIG_PREEMPT_RT_FULL I do not get this bringup delay. I could not do this 
test with rt9 because it does not build without CONFIG_PREEMPT_RT_FULL!

Any ideas?

Matthias

             reply	other threads:[~2014-01-01 16:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 16:37 Matthias Fuchs [this message]
2014-01-06 19:48 ` 3.12.6-rt9 on AM335x (armv7) Matthias Fuchs
2014-01-07  8:38   ` Tim Sander
2014-01-07 21:20     ` Matthias Fuchs
2014-01-07 22:58       ` Tim Sander
2014-01-07 23:46         ` Pavel Vasilyev
2014-01-08  8:08           ` Matthias Fuchs
2014-01-08  8:06         ` Matthias Fuchs
2014-02-07 16:07           ` Sebastian Andrzej Siewior

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=52C44448.3030405@ma-fu.de \
    --to=mfuchs@ma-fu.de \
    --cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).