Quote from: gentakin on June 02, 2011, 09:48:48 PM

Quote from: DiabloD3 on June 02, 2011, 09:30:26 PM

A dead giveaway of the bug is using -dd and seeing a ton of hardware check errors.

That's probably it!

Code:

[02.06.11 23:34:37] Added Barts (#1) (14 CU, local work size of 192)
[02.06.11 23:34:37] DEBUG: Enabling long poll support
[02.06.11 23:34:37] DEBUG: Enabling long poll support
[02.06.11 23:34:37] DEBUG: Enabling long poll support
[02.06.11 23:34:48] DEBUG: Attempt 1 found on Barts (#1)
[02.06.11 23:34:48] DEBUG: Invalid block found on Barts (#1), possible driver or hardware issue
[02.06.11 23:34:56] DEBUG: Attempt 2 found on Barts (#1)
[02.06.11 23:34:56] DEBUG: Invalid block found on Barts (#1), possible driver or hardware issue
[02.06.11 23:34:58] DEBUG: Attempt 3 found on Barts (#1)
[02.06.11 23:34:58] Block 1 found on Barts (#1)1
[02.06.11 23:35:15] DEBUG: Attempt 4 found on Barts (#1)
[02.06.11 23:35:15] Block 2 found on Barts (#1)6
[02.06.11 23:35:25] DEBUG: Attempt 5 found on Barts (#1)
[02.06.11 23:35:25] Block 3 found on Barts (#1),0
[02.06.11 23:35:26] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:35:26] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:35:26] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:36:13] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:36:13] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:36:13] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:36:15] DEBUG: Attempt 6 found on Barts (#1)
[02.06.11 23:36:16] Block 4 found on Barts (#1),4
[02.06.11 23:36:18] DEBUG: Attempt 7 found on Barts (#1)
[02.06.11 23:36:18] DEBUG: Invalid block found on Barts (#1), possible driver or hardware issue
[02.06.11 23:36:19] DEBUG: Attempt 8 found on Barts (#1)
[02.06.11 23:36:19] Block 5 found on Barts (#1),4
[02.06.11 23:36:29] DEBUG: Attempt 9 found on Barts (#1)
[02.06.11 23:36:29] DEBUG: Invalid block found on Barts (#1), possible driver or hardware issue
[02.06.11 23:36:50] DEBUG: Attempt 10 found on Barts (#1)
[02.06.11 23:36:50] Block 6 found on Barts (#1),9
[02.06.11 23:36:53] DEBUG: Attempt 11 found on Barts (#1)
[02.06.11 23:36:53] Block 7 found on Barts (#1),0
[02.06.11 23:36:53] DEBUG: Attempt 12 found on Barts (#1)
[02.06.11 23:36:53] Block 8 found on Barts (#1),0
[02.06.11 23:37:01] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:37:01] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:37:02] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:37:03] DEBUG: Attempt 13 found on Barts (#1)
[02.06.11 23:37:03] Block 9 found on Barts (#1),0
[02.06.11 23:37:25] DEBUG: Attempt 14 found on Barts (#1)
[02.06.11 23:37:25] DEBUG: Invalid block found on Barts (#1), possible driver or hardware issue
[02.06.11 23:37:37] DEBUG: Attempt 15 found on Barts (#1)
[02.06.11 23:37:38] Block 10 found on Barts (#1)8
[02.06.11 23:37:49] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:37:49] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:37:49] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:38:36] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:38:36] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:38:37] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:39:11] DEBUG: Attempt 16 found on Barts (#1)
[02.06.11 23:39:11] DEBUG: Invalid block found on Barts (#1), possible driver or hardware issue
[02.06.11 23:39:13] DEBUG: Attempt 17 found on Barts (#1)
[02.06.11 23:39:13] Block 11 found on Barts (#1)3
[02.06.11 23:39:23] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:39:24] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:39:25] DEBUG: Forcing getwork update due to nonce saturation
[02.06.11 23:39:30] DEBUG: Attempt 18 found on Barts (#1)
[02.06.11 23:39:30] Block 12 found on Barts (#1)4
[02.06.11 23:39:41] DEBUG: Attempt 19 found on Barts (#1)
[02.06.11 23:39:41] Block 13 found on Barts (#1)3
270047/269776 khash/sec | ghash: 82,0 | fps: 29,3^C

Now...

Code:

user@host:~/...../DiabloMiner$ git pull
Already up-to-date.

AFAIR, there were no updates since i cloned the repo from github yesterday. Even if there were, I just did a "mvn package" to recompile and still getting the hardware issue in my log. I hope I'm not doing it wrong.

Again, thanks for your support and fast miner.

Huh, interesting. You're getting them, yet the bug has been fixed, and I'm not aware of the bug ever showing on 2.4.

BTW, bfi_int with certain combinations of vector cause false positive hw errors, but otherwise do not touch the number of shares produced. At 270 mhash, you should be able to produce 50 shares in about 14 minutes.

If its the bug I'm thinking it is, then you will get 50 attempts, but not 50 shares. If its the bfi_int harmless driver bug, then you will get 50 shares, but way more than 50 attempts.