[lkml]   [2006]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.17-rc3-mm1
On Wed, 2006-05-03 at 06:48 -0700, Andrew Morton wrote:
> > Since a few -mm releases I am seeing processes stuck in a
> > nanosleep({0, 0}, NULL) syscall. Sometimes, they unfreeze after
> > several hours.
> Thanks. Yes, please test mainline first - it will probably occur there.
> And it's a nanosleep(zero) all the time? The obvious answer would be that
> a clock tick came in at the right time and we end up trying to sleep for -1
> units. But if that was the case, things wouldn't unsleep after just
> several hours.

I don't see how that should happen. The expiry time is stored in
absolute time format when nanosleep is started and compared against
current time in the softirq. We might miss one tick, but not more.

Benoit, can you please mail me .config and a boot log ?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-05-03 16:15    [W:0.042 / U:10.176 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site