Nikolaus Rath:
> > Do you mean all stopped at the similar function, ie. block I/O?
>
> Since the system becomes totally inaccessible, I have no idea what these
> processes are up to. What I mean is that I get kernel messages of the for=
> m
>
> Jul 10 14:11:38 beta kernel: [25560.688091] INFO: task cron:2278 blocked
> for more than 120 seconds.
> Jul 10 14:11:38 beta kernel: [25560.688100] "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [...]
The snipped part is important.
If the stack trace shows something like this,
io_schedule+0x3a/0x60
sync_buffer+0x38/0x40
__wait_on_bit+0x4d/0x70
out_of_line_wait_on_bit+0xab/0xc0
__wait_on_buffer+0x2e/0x30
squashfs_read_data+0x30b/0x720 [squashfs]
:::
then it means the process blocks in block I/O.
J. R. Okajima
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
