I just noticed that when i was hash-checking my torrents the problem appeared, but when i finished, its normal again, i really dont know WHEN it happens to me. But yesterday happened while i was using excel XD...lol (of course, torrents in background and other apps).

I want any answer, did it worked with the new flags? Thanks

edit: what i mean by "WHEN it happens to me" i mean when it happens and stays like that.....

I found that it always happened around the 3 hour mark no matter what I was doing

I had been without the issue a while, whithout doing anything else, lol.....meh..i want it to happen again to check some stuff on console, etc

Well, transmission crashed again, so i reboot with the flags posted (hpet tsc) and it got worse! LOL, they crashed like in a little while and i couldnt open anything again! D:

I have found, sadly, that my system is still not perfectly stable. My mouse movement problem is fixed with the kernel flags, and I needed no restarts for 3 days, but then I got the 10810 error again. It is getting really annoying. Itunes also gave me a division by 0 crash. I know it has to be some problem with multiple cores, but what?

After a few days of testing I cannot maintain a stable dual core system with any of the aforementioned flags. Looks like we're going to have to wait for either a patch or switch to Intel. For now I have reverted to using cpus=1 in my config.

---

MacBook Pro 15" | Mac OS X 10.6 • 2 GHz Intel Core Duo • 2 GB DDR2-667 • ATI Radeon Mobility X1600 128 MB • 100 GB Serial-ATA
Hackintosh | Mac OS X 10.5.6 • 3 GHz AMD Athlon 64 X2 6000+ • MSI K9N AM2 • 2 GB DDR2-667 • NVIDIA GeForce 8800 GT 512 MB • ALC888 Audio • 300 GB Serial-ATA
iPhone 3G • 8 GB

well mine crashes right now like in 3 days or something, dont know whats the breaking point, but i wont put cpus=1 lol...i dont want to lose my core =)! XD

I only have the problem that Firefox crashes rather often. Version 2 and 3.

---

2 Opteron systems: OSx86 10.5.8, Andy's 9.8.0 kernel, Asus A8N-SLI Premium, Opteron 185 o'clocked @ 2 x 2,95 GHz (2nd system 2.6 GHz), ATI Radeon HD2600XT 256MB Dual-Monitor 2x HP L2035, 4 GB RAM, Griffin FireWave as main audio device, Marvell + nForce LAN, Asus U3S6 USB3/SATA6 card, 5,5 TB harddisk, Firewire 800 card, Apple Remote + eHome IR receiver, 2x Wacom serial graphics tablet, Canon Pixma iP4700, Logitech Internet Navigator wireless keyboard/mouse combination.

My Audio stuff: M-Audio Transit USB (default audio), M-Audio ProFire 610, M-Audio ProFire Lightbridge (34 channels) using Creamware A16 ADAT converter • MIDI: M-Audio Midiman 4x MIDI interface • Behringer Audio Mixers: Xenyx 1002, Xenyx 1002FX, Xenyx 1202FX, Eurorack UB1002FX, Eurorack MX1804FX, Eurorack MX262A • FX devices: Lexicon MPX100 DSP, Behringer DSP-1000 Virtualizer, Behringer MiniFEX 800 DSP, Behringer Multicom Pro MDX4400 compressor • RETRO: MSSIAH midi/sequencer/synthesizer cardridge for the C64 (Dual-SID), Steinberg M.S.I. MIDI Interface for C64

meh it had been crashing more often, which "solutions" did you all used? Thanks

@pmcnano: Unfortunately it appears to be an AMD dual core issue that needs to be resolved at base code level. For stability, the only solution is to use cpus=1 :-\

---

MacBook Pro 15" | Mac OS X 10.6 • 2 GHz Intel Core Duo • 2 GB DDR2-667 • ATI Radeon Mobility X1600 128 MB • 100 GB Serial-ATA
Hackintosh | Mac OS X 10.5.6 • 3 GHz AMD Athlon 64 X2 6000+ • MSI K9N AM2 • 2 GB DDR2-667 • NVIDIA GeForce 8800 GT 512 MB • ALC888 Audio • 300 GB Serial-ATA
iPhone 3G • 8 GB