From: tpo2@sourcepole.ch (Tomas Pospisek ML)
Subject: [sup-talk] CPU at 99%
Date: Fri, 31 Oct 2008 21:38:09 +0000 [thread overview]
Message-ID: <Lg3myPlb.1225489089.1213610.tpo2@192.168.3.7> (raw)
When I start Sup, it starts eating my CPU and won't stop. And it
doesn't seem to be doing anything either:
top - 22:34:10 up 19 days, 1:43, 14 users, load average: 1.12, 0.98,
0.64
Tasks: 169 total, 3 running, 166 sleeping, 0 stopped, 0 zombie
Cpu(s): 23.8%us, 27.6%sy, 0.0%ni, 47.9%id, 0.0%wa, 0.7%hi, 0.0%si,
0.0%st
Mem: 2054936k total, 2038152k used, 16784k free, 10264k buffers
Swap: 1951856k total, 683256k used, 1268600k free, 310932k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18228 tpo 20 0 185m 85m 3696 R 99 4.3 12:33.83 sup
Meanwhile my laptop is blowing hot air like a fumarole.
System is amd64 on Ubuntu Heron, Sup 0.6.
?
*t
next reply other threads:[~2008-10-31 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 21:38 Tomas Pospisek ML [this message]
2008-10-31 23:53 ` William Morgan
[not found] ` <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7>
2008-11-02 18:50 ` William Morgan
2008-11-03 20:45 ` Tomas Pospisek ML
2008-11-03 21:29 ` Tomas Pospisek ML
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=Lg3myPlb.1225489089.1213610.tpo2@192.168.3.7 \
--to=tpo2@sourcepole.ch \
/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