linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dong Liu <dliu.cn@gmail.com>
To: Carsten Emde <C.Emde@osadl.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: cpu stall and hyperthread
Date: Fri, 06 Jul 2012 12:03:37 -0400	[thread overview]
Message-ID: <4FF70C59.40801@gmail.com> (raw)
In-Reply-To: <4FF6CEA6.6080900@osadl.org>

On 7/6/12 7:40 AM, Carsten Emde wrote:
> Hi Dong,
>
>> I can quite reliably trigger this cpu stall error now. Just try to start
>> several KVM guests.
> Good. BTW, we do repeated long-term tests 14 times per day with a single
> kvm guest that runs on two cores and conducts a number of CPU
> benchmarks. (https://www.osadl.org/?id=931) - never had this problem. So
> it may be related to running more than a single kvm guest.
>

I'm using i7 860 with HT enabled. It has 8 logical cores. Maybe it has 
something to do with it.
>> [..]
>> Are there any way I can use to narrow down this error?
> cd /sys/kernel/debug/tracing/
> echo 0 >tracing_on
> echo 1 >events/enable
> echo function >current_tracer
> echo 14080 >buffer_size_kb
> echo 1 >tracing_on
> while true
> do
> if dmesg | tail -100 | grep -q "rcu_preempt detected stalls"
> then
> echo 0 >tracing_on
> break
> fi
> sleep 1
> done

I don't have /sys/kernel/debug/tracing/ directory. The kernel doc says 
turn on CONFIG_KPROBE_TRACING. But I could not find this config.


>
> Then start the kvm quests.
>
> Alternatively, you may use the kernel parameter ftrace_dump_on_oops.
>
I'll try that.

Thanks,

Dong

  reply	other threads:[~2012-07-06 16:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4FEBCDDE.60503@gmail.com>
2012-07-03 20:10 ` cpu stall and hyperthread Dong Liu
2012-07-04  1:13   ` Paul E. McKenney
2012-07-04 17:27     ` Dong Liu
2012-07-04 22:52   ` Carsten Emde
2012-07-05 18:41     ` Dong Liu
2012-07-05 22:48       ` Carsten Emde
2012-07-06  6:07         ` Dong Liu
2012-07-05 23:02       ` Carsten Emde
2012-07-06  6:04         ` Dong Liu
2012-07-05 18:48 ` Dong Liu
2012-07-06  6:20 ` Dong Liu
2012-07-06 11:40   ` Carsten Emde
2012-07-06 16:03     ` Dong Liu [this message]
2012-07-06 21:01       ` Carsten Emde
2012-07-09  4:33     ` Dong Liu
2012-07-09  6:53       ` Carsten Emde
2012-07-09 14:46         ` Dong Liu
2012-07-06 15:58   ` Dong Liu
2012-07-06 17:32   ` Dong Liu
2012-07-12 20:27 ` Dong Liu
2012-06-28  3:23 Dong Liu

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=4FF70C59.40801@gmail.com \
    --to=dliu.cn@gmail.com \
    --cc=C.Emde@osadl.org \
    --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).