[doveman2]

I've been trying out some overclocks now that I seem to have got it stable at default

I tried

arm_freq=1000
core_freq=500
sdram_freq=600
over_voltage=6

but that hung after a small bit of linux boot text

arm_freq=1000
core_freq=500
sdram_freq=500
over_voltage=6

went further but it seemed to show a lot more linux boot text than usual and ultimately hung after mounting the USB stick

arm_freq=950
core_freq=450
sdram_freq=450
over_voltage=6

works OK, although I did get a phantom keypress loop almost straight away (in the shutdown menu).

I've got initial_turbo=30 set, which if I recall correctly is meant to prevent the overclock from kicking in for a while during boot but I might have misunderstood.

After booting and once the XBMC Home screen appears, the debug OSD shows the CPU is loaded (85%+) and the used RAM is changing rapidly for 27s before it stops and settles down to about 45%. This seems like a long time for it to stabilise and it's obviously going to be a bit laggy navigating during this time whilst the CPU is almost fully loaded already. Is this normal? I'm not doing any scans at startup or anything like that.

Log here http://pastebin.com/ff9jxa9w (I pressed some buttons to mark once it had settled, at 11:48:15, which means that XBMC must have loaded the Home screen around 11:47:48)

I uploaded the previous log, with Debugging disabled, here in case it's useful for comparison http://pastebin.com/DGf2xnri