Does anyone know what the jffs2_gcd_mtd4 process relates to? I've been having no end of problems with my n800 hanging/reseting repeatedly at boot and this command seems to be using up virually all CPU time (>97%) from the few times I've been able to get into anything and check. I'm a bit new to linux/maemo, so I've not really got a clue what it relates to and haven't been able to find out much through the site search or google.

My machine also seems to be running the battery flat when theoretically idle with the screen locked, but after a bit of research I suspect this is unrelated and might be the #978 metalayer-crawl bug. The 'fix' on the maemo.org bugzilla may as well be written in pingura chinese for all the sense it made to me (hey - I said I was new) but I've tried reformatting the SD card in case of file system was corrupted and will see how that goes - any suggestions are welcome either way, though.

As an aside, both these problems first started just after I'd installed minimo and although I suspect it's just coincidence, has anyone heard of a connection?

Just as a a further to this if anyone is remotely interested, reformatting the SD card seemed to help for a couple of days, but my n800 is now stuck in a constant "boot - display mostly frozen desktop for 30 seconds with 100%Cpu usage - reset - boot - etc" cycle so I effectively can't get into it any more. I'll reflash it later on when I get a chance.

I'd still be interested to hear any suggestions from people, though....

If you have 2.2006.51-6 or older firmware, reflash to newer 3.2007.10-7, there were some bugs fixed related to long running jffs2 garbage collector (the jffs2_gcd_mtd4) and reboots

Disabling lifeguard-reset will probably stop the automatic reboot until whatever process has completed... if it is the jffs garbage collector momentarily hogging CPU you may be able to re-enable lifeguard-reset after a couple of successful boots.

But uprading to the latest firmware is a very sensible suggestion from fanoush, as it fixed a lot of annoying stability bugs.

Thanks for the responses.

I was running the latest firmware as it happens - I re-flashed it the day I bought it.

As for disabling the lifeguard-reset, well, I have absolutely no idea how you would set about doing that, but I'll wander off and find out for future reference