From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: linux-kernel@vger.kernel.org
Subject: Impossible high cpu-time values for migration threads
Date: Thu, 17 Nov 2011 23:17:31 +0100 [thread overview]
Message-ID: <20111117221731.GA9229@x4.trippels.de> (raw)
Just saw this for the first time:
1 [|| 2.4%] Tasks: 63, 31 thr, 54 kthr; 1 running
2 [|| 1.7%] Load average: 0.03 0.06 0.36
3 [|| 1.0%] Uptime: 06:36:59
4 [|| 1.0%]
Mem[|||||||||||||||||||||||||||||||||| 1427/7977MB]
Mem:7977M used:1427M buffers:0M cache:2604M
Swp[| 0/2047MB]
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
11 root RT 0 0 0 0 S 0.0 0.0 5h38:27 migration/2
14 root RT 0 0 0 0 S 0.0 0.0 5h30:29 migration/3
1476 root 20 0 97672 38928 5024 S 1.0 0.5 4:49.06 /usr/bin/X -nolisten tcp :0 -auth /home/markus/.serverauth.1459
1281 markus 20 0 931M 317M 40592 S 0.0 4.0 4:19.17 firefox
1538 markus 20 0 200M 34544 18848 S 0.0 0.4 2:43.89 konsole -e /home/markus/start_screen
868 mpd 20 0 294M 20336 4868 S 0.0 0.2 2:04.88 mpd --no-daemon
...
As you can see the machine has an uptime of 06:36:59 and the two
migration threads both show greater than 5h30min cpu-time.
(Linux 3.2.0-rc2-00046-g317bfe8 on amd64)
--
Markus
reply other threads:[~2011-11-17 22:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111117221731.GA9229@x4.trippels.de \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®