Quote from: kerney666 on April 22, 2019, 11:49:18 AM

Quote from: carlosmonaco on April 22, 2019, 10:34:35 AM

When I was looking how to decrease consumption I found two things really weird.

One of my rig is reporting a huge diference between reported hashrate and pool hashrate . ( No hw error etc..)
https://imgur.com/a/In6q2S4
There is no error and there is 2 kh/s between pool hashrate and reported hashrate.

Miner vs poolside testing is a b*tch, and I dedicated the last section of the CN_MAX_YOUR_VEGA.txt guide in the 0.4.4 release to it. That said, your numbers are way off, this should happen in <= 0.07% of all cases _if you were running at a static diff_. Since you aren't, it's really difficult to reason about if this is a "normal outlier" that happens every 100th run, or that it more or less proves that something clearly is off.

Drilling deeper and looking at each gpu, two of your cards look a little fishy at 1480 h/s poolside, but we have way too little data to assert anything on a per-gpu basis. So, please run a xmrig-proxy test as decribed in the guide for e.g. 50k shares total and you should have the data you need - it might be that those two cards are not doing great at the current clocks and/or timing mods, and it should be clearly visible with that higher amount of shares. We're doing tons and tons of testing ourselves to make sure we hit the poolside hashrate, I'd love to get more user data here, but it must be from runs that I know I can trust from a statistical standpoint.

Quote from: carlosmonaco on April 22, 2019, 10:34:35 AM

The second thing is even weird:

This is my PPT for my Vega 64:
https://imgur.com/a/NTuNGjT

P0->p6 core are disable and P0->P2 mem too and for the last state I use 875mV but when I check HWinfo when mining voltage is still around 895 mV.

Look like it use the higher voltage of disable state when running.

So I try to change my PPT by using 820mV for all state except the last one for core and mem.
I keep the exact same P7 core and P3 mem but my card is reporting dead almost one min after starting to mine.

Any explanation ?

Newer drivers often seem to lock P7 core+P3 mem during load to not be too aggressive with switching p-states.

For the PPT itself, this is an artform. Don't be fooled by the view in ODNT. The only thing that exists is a single vdd lookup table which is _shared_ by core and mem states. ODNT fools you into believing that you can separate voltage settings for e.g. core P4 from mem P3, which isn't true unless you do some serious PPT tweaking. I'm not 100% it's possible even then.

To simplify your tests, I'd either (1) use the same target voltage for ALL core and mem states in your PPT or (2) make sure all core and mem states have increasing voltage levels in respective series and also that core P4 voltage == mem P3 voltage and that it matches your target.

I'm not 100% sure what happens in your tests. Maybe mem P3 is rather grabbed from core P4, so in your first test you get 900 mV (~= 895 mV), and in your second test you get 820 mV which is way too low to handle sustained pressure?

Thanks so much for the answer , for the bad pool hashrate I just reinstalled 18.6.1 drivers , now seems to be ok . Didn't know what happens.

For the PPT , I checked all my rig ( all running at 895 mV for the good one ) even when I set up 850 mV Core P7 And Mem P3.
When I try to lower voltage for CORE P4 and above I get a crash everytime ( vega 56 and vega 64).
Two ideas : I just lost silicon lotery for all card or my PPT are really bad.

Running drivers 18.6.1
Soc Clock : 1107 ( VEga 64 and 56)
I cannot use mem timing , too much increase in heat and consumption.
I will try to test other PPT.