On Mon, 8 Oct 2007, Bernd Schubert wrote:
> Hi,
>
> we have a system here were e.g. "sleep 1" will never finish. This is an
> issue of 2.6.23, on all older kernel versions it did work fine.
>
> Seems to hang in do_nanosleep()
>
> [ 153.775792] sleep S 0000000000000000 0 5372 5341
>
> [ 153.782385] ffff81007f0a9ea8 0000000000000082 0000000000000000
> 0000000000008efc
>
> [ 153.790635] ffff81007f0a9e48 ffffffff802447b4 ffff81007f0c3080
> 0000000300000000
>
> [ 153.798938] ffff81007f0c39c8 ffff81007f0c37c0 000000004001d908
> 0000000000000000
>
> [ 153.806991] Call Trace:
>
> [ 153.809937] [<ffffffff8048e4cd>] do_nanosleep+0x42/0x75
>
> [ 153.815727] [<0000000000000001>]
>
> [ 153.819383]
>
> [ 153.775792] sleep S 0000000000000000 0 5372 5341
>
>
>
> [ 330.669444] SysRq : Show Pending Timers
>
> [ 330.673552] Timer List Version: v0.3
>
> [ 330.677326] HRTIMER_MAX_CLOCK_BASES: 2
>
> [ 330.681282] now at 255011372633 nsecs
>
> [ 330.829981] active timers:
>
> [ 330.832859] #0: <ffff81007f0e3de8>, hrtimer_wakeup, S:01
>
> [ 330.838805] # expires at 260156346358 nsecs [in 5144973725 nsecs]
>
>
> [ 337.046189] now at 261387685432 nsecs
>
> [ 337.194966] active timers:
>
> [ 337.197834] #0: <ffff81007f0e3de8>, hrtimer_wakeup, S:01
>
> [ 337.203793] # expires at 260156346358 nsecs [in 18446744072478212542
> nsecs]
timer already expired ---------^^^^^^^^^^^^
(~1.2 seconds)
hmm, signedness problem (only in the display) ---------^^^^^^^^^^^^^^^^^^^
Can you please put a complete system description, your .config and a boot
log into bugzilla ?
Thanks,
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/
