For the records: overclocking does not seem to be the culprit, as I am getting spontaneous reboots in certain moments still, with conky showing me 250 MHz. Loading the bleeding edge drivers sometimes leads to my N900 giving up, from time to time. Getting the N900 to access my home WiFi when coming back from 3G/3.5G to the home-office always requires a restart frenzy (sometimes I just give up).

I have not been able to return to my home WiFi to be encrypted yet, which gives me a headache (There is some equipment in the WDS setup that disallows WEP, and WPA/2 does not work at all yet with my N900).

I do realize that a WDS, comprised out of several APs might not be the preferred terrain for the N900, but unfortunately, that's how things are here.

So I am struggling on with my spontaneous reboots.

Thread revival time: Overclocking is definitely not the culprit here (unless your N900 is used and was heavily overclocked before). Prolonged overclocking CAN be the culprit of spontaneous CPU damage if the overclocking is taxing enough on the CPU's electronics to damage it, BUT, I for one, have never overclocked the N900 and I have a nice history with spontaneous reboots. Well, nice in that spontaneous reboots just love me, and my N900 was and still is plagued with them since a LOOOOONG time ago.

I find R&D mode turned on, with watchdogs and lifeguard reset flags turned on to disable those 'features', helps tremendously with spontaneous reboots (if you're willing to occasionally have something crash in the background, that would normally cause a spontaneous reboot by something killing something else, and wait with bated breath to see if it'll restart on its own, or if you'll have to manually shut down the device.) But, for example, just yesterday morning my N900 had either hildon-desktop or x.org or something crash, and not everything restarted. (I suspect it was x.org that crashed because for a moment I saw the kernel's framebuffer console - which normally gets covered - assuming it's enabled in the first place - when x.org starts during boot.)

Some of the stuff restarted, and I got my current window re-displayed. But keyboard input crashed and didn't come back, as did whatever part of hildon lets you switch windows. ANYWAY, the virtual keyboard remained working and I had the chance to finish a PM I was writing on here, before shutting the device off.

So R&D mode can alleviate some of the problems (if you edit /sbin/preinit to disable the keyboard flickering when screen is locked, to keep battery consumption the same) of spontaneous reboots, although, honestly, it depends on the exact nature of the spontaneous reboots.

Worth a try, at any rate.

I'm in rd-mode with the watchdogs and dsme reboots disabled and I have no problems. (I never had many problem with spontaneous reboot but I prefer to not have the phone rebooting if I kill some process too rapidly.)

Modify sleep_ind 1 to sleep_ind 0 in /etc/pmconfig to avoid keyboard flickering (no need to mess with /sbin/preinit)

*Shrug* That works too. I change it in /sbin/preinit to keep my modified-system-files minimal (less restoring time after a reflash) - and more importantly because that's where I originally figured out how to disable it. (Since I was messing in /sbin/preinit to get my boot-shell script to launch as early as possible.)