From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/9] ia64: VIRT_CPU_ACCOUNTING (accurate cpu time accounting)
Date: Wed, 07 Nov 2007 09:46:01 +0000 [thread overview]
Message-ID: <47318959.2080306@jp.fujitsu.com> (raw)
In-Reply-To: <4714BDC7.1070702@jp.fujitsu.com>
> I did run the kernel some more today and noticed some odd "hangs".
> Some processes seemed to get stuck for many seconds and then
> continued again. Didn't have time to try and track what was
> happening. Have you seem snything like this?
>
I've encountered the similar phenomenon several times. I have
not investigated it very much, but I guess it is related to the
problem reported at
http://marc.info/?l=linux-kernel&m\x119303432628668&w=2
The 'wa' field of 'top' command showed that one of cpus is under
100% iowait when I encountered the problem.
Thanks,
Kenji Kaneshige
next prev parent reply other threads:[~2007-11-07 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:33 [PATCH 1/9] ia64: VIRT_CPU_ACCOUNTING (accurate cpu time accounting) Hidetoshi Seto
2007-11-01 20:29 ` Tony Luck
2007-11-02 3:15 ` Hidetoshi Seto
2007-11-07 6:59 ` Luck, Tony
2007-11-07 9:46 ` Kenji Kaneshige [this message]
2007-11-19 4:34 ` Simon Horman
2007-11-19 5:17 ` Hidetoshi Seto
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=47318959.2080306@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-ia64@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