On Mon, 2010-03-22 at 15:30 +0100, Kövesdi György wrote:
> > Where is the output of mjpg-streamer written to? It looks like it is
> > using ram disk or (slow) flash memory. Make sure it is on the hard disk.
> Sorry, i forgot to mention that there is a link:
> /data -> /mnt/xxx/
> which point to the HD.
>
OK, wanted to be sure that we are hunting a real bug. Did you check that
the files are actually written to that disk?
> > What is the rate of data being written? If, for some reason, the disk
> > (flash?) is too slow, you run out of memory due to the block layer
> > buffering.
> The measured maximum recorded rate is ~23 fps. My very first try was
> recording
> one picture in every 15 second, which is very slow, and it also leaded to
> crash in 3 days. Faster recording crashes sooner.
>
Sounds like a memory leak of the application. Or some (debug) log asking
too much memory. Maybe /var/log/messages is getting huge?
> ------------------
>
> I checked some out-of-memory situations, and found strange things. You can
> easily try it (i would like to hear if it works on your system or not):
> create
> a big directory (~50k...100k files) and give a simple 'ls' command:
>
> $ ls /my/big/directory
>
> No swap is in use, my physical memory is 32M.
> The 'ls' allocates very much memory, which leads to out-of-memory. AFAIK, the
> kernel calls the oom-killer, which should kill the biggest process ('ls' in
> this case).
I'm not sure that it kills the biggest process first.
> It happens, but the system hangs. Some seconds later the following
> message appears on the console:
>
> bcm47xx_wdtWatchdog will fire soon!!!
>
> This is the very last message, the system does not respond any more.
> I think this situation should be handled correctly.
>
What keeps the watchdog happy? It that still alive after the OOM-killer?
Bas.
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
