public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PROBLEM_WITH_CPUACCT.SH_100_100_LTP_TESTSUITE]
Date: Wed, 22 Nov 2017 15:31:56 +0100	[thread overview]
Message-ID: <20171122143156.GE2389@rei.lan> (raw)
In-Reply-To: <CAPiF6ThOKV6egQ8nhxKoiUba1S8UzLP3h0LOB+HO8T9vc0vemg@mail.gmail.com>

Hi!
> I had run the test case ???./cpuacct.sh 100 100??? on my ARM board.
> 
> Afterward,  I have gotten a problem as bellow:
> 
> 
> 
> *1 TINFO: Creating 100 subgroups each with 100 processes*
> 
> *[69402.212655] imx2_wdt_interrupt: pretimer*
> 
> *[69402.212777] The following is the list of last 50 interrupts for each
> CPU*
> 
> *[69402.212868] [69402.145532]: irqnumber 1023 cpuid 0*
> 
> *[69402.212960] [69402.145727]: irqnumber 99 cpuid 0*
> 
> 
> 
> And my ARM board restarted immediately.

If that happens the odds are that you hardware/kernel is buggy.

> I think the test case had made my board run out of CPU power(CPU
> overloading ), so the watchdog timer has identified this problem and
> restarted the board.

There is no such thing CPU overload as far as I can tell. For small
system it may be the case that you are running out of memory but if
adding sleep to the loop fixes the problem that shouldn't be the case.

So all in all this looks like buggy kernel to me.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2017-11-22 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 17:18 [LTP] [PROBLEM_WITH_CPUACCT.SH_100_100_LTP_TESTSUITE] Na Nha
2017-11-22 14:31 ` Cyril Hrubis [this message]
2017-12-02 10:45   ` Na Nha
2017-12-04 13:36     ` Cyril Hrubis

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=20171122143156.GE2389@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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