New update - core0 3000 stable stock volts, but core1 will fail, max is 2900 at stock HT - so bump in voltage, now added 0.05v, at 1.344v idle/1.338v load at 3000/3000/2700/2800 testing for another 24 hours or so. No fail yet, just ran 2 benches and EVEREST stability test 30 mins. +1 hr gone now...




Quote Originally Posted by justapost View Post
Umm, that's why I run and asked for "i2cdetect 0" first.
That does only detect the addresses where chips live and does not test the chips. I'd not run sensors-detect with a phenom mounted. I tested all other boards i have here with an X2 cpu. The system only froze on the Sapphire board,not on the M3A(770) the GBT780G and the M2A-VM (690G).
Yeah, I know what it does but like I said it never worked. Installed latest lm-sensors manually (2.10.1) and then ran i2cdetect 0, never gave any feedback, failed and then second time froze my system. Rebooted and then ran it again, no output. Then ran i2cdetect -l and it again froze my system. No idea if its broken but none of these commands nor sensors-detect does anything odd in Ubuntu, I had tried it once before a few days back.

The guide on lm-sensors mentions clearly that its not safe to run:
WARNING

This program can confuse your I2C bus, cause data loss and worse!
So I'm a bit weary of trying it again, I don't want a screwed up system again like so many times before.
Running "i2cdump 0" with the i2c-piix4 and the i2c-dev module loaded did never freeze a system but it makes the smbus/i2c chip unusable till i restart the system (cold start). It does not interfer with the it87 module which is used for the sensor-chips on all of my boards.
I wonder if "i2cdump 0" also shows a chip at 0x2e, whom is responsible for the freezing.
Will try in Ubuntu and check - just give me some hours to test stability first.
Thanks, that is from the SB600 docs i guess?
Yes
Yeah but it can be that with 1.55V the bad clocker at stock whould have been stable and the better clocker are causing the freezes now because they do not like those hight voltages.
I didn't understand what you said there
For the p-states amd says the multis and dividers must be equal for all cores.
We know that this is no requirement but I'm not so sure if it will not cause problems 24/7 longterm.
I'm perfectly fine with it since AMD themslves demo'd and allowed us to clock cores individually in their own public software: AOD.
If it was problematic, they wouldn't do that. Anything causing them headaches, they always remove, even if its something rare.
My last 9850BE also had a bad third core and the fourth also was no good clocker. Cores one and two ran 3GHz at ~1.325V.
Looks like mine and yours are similar. Mine is on 3000 1.344v/1.338v idle/load stable now for about an hour. Load, it can do 3055 on all cores at that voltage stable, but idling I'm still testing