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 ?
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
