lkml.org 
[lkml]   [2003]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Runaway cron task on 2.5.63/4 bk?
Kevin Brosius <cobra@compuserve.com> wrote:
>
> 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
>

Yes I've seen this four times over maybe three weeks. Three times on dual
CPU, once on a different UP machine.

In all cases, crond is stuck in a loop calling nanosleep with a tv_sec value
of a bit over 4,000,000 and a tv_nsec value of zero. nanosleep keeps
returning EINVAL immediately.

I'm not sure why crond is trying to sleep for so long. Maybe it has set an
alarm.

errr, OK. This returns -EINVAL:

#include <time.h>

main()
{
struct timespec req;
struct timespec rem;
int ret;

req.tv_sec = 5000000;
req.tv_nsec = 0;

ret = nanosleep(&req, &rem);
if (ret)
perror("nanosleep");
}

I shall take a look....

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.046 / U:0.568 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site