From: Nebojsa Trpkovic <trxman@gmail.com>
To: cpufreq@lists.linux.org.uk
Subject: high "hi" usage and hang
Date: Tue, 15 Mar 2005 11:04:39 +0100 [thread overview]
Message-ID: <4236B337.6080703@gmail.com> (raw)
I've got my system very very slow in one moment, saw "98% hi" in top and
next moment system completely hanged. All hapened after turning on
powernow-k8 and trying to compile some large gentoo packages.
Is this cpufreq-related at all?
> Mar 15 10:49:55 master bad: scheduling while atomic!
> Mar 15 10:49:55 master
> Mar 15 10:49:55 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:49:55 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:49:55 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:49:55 master bad: scheduling while atomic!
> Mar 15 10:49:55 master
> Mar 15 10:49:55 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:49:55 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:49:55 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:49:55 master bad: scheduling while atomic!
> Mar 15 10:49:55 master
> Mar 15 10:49:55 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:49:55 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:49:55 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:27 master bad: scheduling while atomic!
> Mar 15 10:50:27 master
> Mar 15 10:50:27 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:27 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:27 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:27 master bad: scheduling while atomic!
> Mar 15 10:50:27 master
> Mar 15 10:50:27 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:27 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:27 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:27 master /usr/sbin/cron[14337]: (root) CMD (nice -n 19
> /root/skripte/rrd_update.pl)
> Mar 15 10:50:27 master /usr/sbin/cron[14339]: (root) CMD (test -x
> /usr/sbin/run-crons && /usr/sbin/run-crons )
> Mar 15 10:50:29 master bad: scheduling while atomic!
> Mar 15 10:50:29 master
> Mar 15 10:50:29 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:29 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:29 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:29 master su(pam_unix)[13662]: session closed for user root
> Mar 15 10:50:30 master bad: scheduling while atomic!
> Mar 15 10:50:30 master
> Mar 15 10:50:30 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:30 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:30 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:32 master bad: scheduling while atomic!
> Mar 15 10:50:32 master
> Mar 15 10:50:32 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:32 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:32 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:33 master bad: scheduling while atomic!
> Mar 15 10:50:33 master
> Mar 15 10:50:33 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:33 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:33 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:33 master bad: scheduling while atomic!
> Mar 15 10:50:33 master
> Mar 15 10:50:33 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:33 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:33 master <ffffffff804d51d3>{_sinittext+467}
> Mar 15 10:50:33 master bad: scheduling while atomic!
> Mar 15 10:50:33 master
> Mar 15 10:50:33 master Call Trace:<ffffffff8039ed5e>{schedule+94}
> <ffffffff8010d610>{default_idle+0}
> Mar 15 10:50:33 master <ffffffff8010d70b>{cpu_idle+107}
> <ffffffff804d58df>{start_kernel+495}
> Mar 15 10:50:33 master <ffffffff804d51d3>{_sinittext+467}
reply other threads:[~2005-03-15 10:04 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=4236B337.6080703@gmail.com \
--to=trxman@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
/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