From: Kevin Brosius <cobra@compuserve.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Runaway cron task on 2.5.63/4 bk?
Date: Sun, 09 Mar 2003 02:30:45 -0500 [thread overview]
Message-ID: <3E6AEDA5.D4C0FC83@compuserve.com> (raw)
Second attempt to send this after not seeing it post after about a day.
Anyone else have kernel posting problems?
I started seeing the cron task runaway, using 100% CPU continuously on a
single CPU with
2.5.63+bk and now with 2.5.64 (about two weeks now.) No other
apps/tasks seem to be affected, that I've noticed. It seems to take
upwards of 8 hours running the kernel for this to occur.
top shows:
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
594 root 25 0 1428 620 1364 R 49.9 0.1 195:23 cron
(This is a dual processor Athlon, so CPU0 is at 100% at the moment.)
This is repeatable. Leaving the box running overnight, or all day, and
the cron process is running 100% again after several hours. This does
not occur in prior 2.5 kernels, or in 2.4.19.
Any idea what's causing this? What additional info on the process would
be helpful? kernel .config file at
http://kevb.net/files/linux2564_config
--
Kevin
next reply other threads:[~2003-03-09 7:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 7:30 Kevin Brosius [this message]
2003-03-09 8:08 ` Runaway cron task on 2.5.63/4 bk? Andrew Morton
2003-03-09 8:17 ` Andrew Morton
2003-03-09 16:28 ` [PATCH] " Todd Mokros
2003-03-10 19:42 ` george anzinger
2003-03-10 19:49 ` Linus Torvalds
2003-03-10 22:21 ` george anzinger
2003-03-10 22:29 ` Andrew Morton
2003-03-10 22:46 ` george anzinger
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 23:05 Felipe Alfaro Solana
2003-03-10 23:33 ` Linus Torvalds
2003-03-11 10:20 ` george anzinger
2003-03-11 22:44 ` Andrew Morton
2003-03-11 23:02 ` Linus Torvalds
2003-03-11 23:09 ` Andrew Morton
2003-03-11 23:18 ` Linus Torvalds
2003-03-11 23:34 ` Andrew Morton
2003-03-11 23:46 ` george anzinger
2003-03-11 23:46 ` Linus Torvalds
2003-03-12 1:55 ` Jamie Lokier
2003-03-12 12:04 ` Denis Vlasenko
2003-03-11 23:35 ` george anzinger
2003-03-12 0:48 ` Matti Aarnio
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=3E6AEDA5.D4C0FC83@compuserve.com \
--to=cobra@compuserve.com \
--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