hmmm. sounds promising

hehe sorry im not sure about the exact function, but it works for me and i thought i have to let u all know about that
if u find more infos about that i would really appreciate sharing them with us
although im not as interested in it as i would google around for it hrhr

Hmm interesting, this is what the osx86 wiki says:

"[use it]..."if you experience stutter like (shutter) syndrome; usualy on dual core processors"

Who knows...worth a try, I guess...

A general site that talked about unix kernels said that this flag is also found in other kernels, and is used to disable energy saving features...?

Gonna give this a go too, i had 24hrs problem free rebooted and then it came back again :-(

Unrelated, but a follow-up to that strange issue that I posted an hour ago here. I found out that my log wasn't showing anything before because it had "turned over". Anyway, I looked into my archived system logs and guess what I found as the culprit for the mystery:

In case you don't know, I've been trying to link this error message with the jerky mouse movement and the -10810 errors. So just to re-iterate, I was running torrents when this happened. This is also what I am doing when I get the mouse problems. I'm a little unsure about the 10810s though, however, I haven't seen them since the time I was experimenting with my memory timings. So I guess I'm not 100% cool with Leopard anymore. I thought running it for over 33 hours meant I was in the clear, but apparently not. There's also nothing I can do to prevent this except stop running torrents, and well, why should I have to do that? Bullshit.

I've found with transmission the higher the download speed the quicker this problem will come on.
also i have that error

Ugh. That makes sense since I was downloading 4 torrents at once. It's gotta be partially torrent related too because I've downloaded many many large files via web browser (FF and Saf) and it never happens when my speed goes high. For example, I've downloaded Ubuntu at my max ISP speed (700kB/s) as a test, and it was fine. Did this numerous times actually. This is really discouraging. I don't think it's limited to Transmission either because I had weird issues with BitRocket and TomatoTorrent in the past. I find it hard to believe that thousands of real mac users and/or the hundreds of Intel hackintosh users out there have problems with torrents like we do. What else could this be???

I did a google search and did see that a couple of real mac users seem to be having the problem but wether it was a different problem with same symptoms who knows.
For the moment I'm trying this

<key>Kernel Flags</key>
<string>idlehalt=0</string>

and as the memory thing seems to make some difference this makes sense.
Anyway let you know more tomorrow keeping my fingers crossed.

I'll give it a try too right now. I'll re-start the torrents after I reboot. That'll be the ultimate test for me to see if the system stays up despite torrents downloading.

disabling energy saving features of the cpu sounds pretty clear...
i bet if i try without that but disable the second core the mouse problem will be gone...
but i wont try coz i dont have the time to test that, more have another problem

btw...anyone knows how to fix the boot with inserted dvd only problem?
since i copied around my boot partitions (leo only for main and for tests) its occuring all the time
think the mbr or efi is damaged in any way... actually messing up with that at the moment,
would be cool if someone knows an open thread here for that