Hi,
ext Kalle Valo wrote:
>> 3) Asterisk marks the application that caused the last wd timeout
>> operation? (so in this case, the spontanous reboot was caused by dsp_dld
>> or it at least seems so?)
>
> There is no way to know what cause hardware watchdog reboot. It can be
> a problem in kernel, or some userspace application taking all the CPU
> time.
Some process just taking all CPU doesn't cause HW watchdog reboot.
Some OOM-protected[1] process (such as Desktop) taking all memory
(e.g. due to a leak in an applet) so that kernel spends all time
just suffling memory pages can cause it though.
[1] OOM-protected = processes ignored by the kernel out of memory
killer. Applications (such as Browser) are not not OOM-protected.
If they use too much memory, kernel kills them to protect
rest of the system. (before this allocations are denied to
them, but this doesn't help if other processes in the system
need more memory too)
- Eero
_______________________________________________
maemo-developers mailing list
[email protected]
https://lists.maemo.org/mailman/listinfo/maemo-developers
