Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 525. (Read 5805546 times)

Of course, despite being credited to Kano, this was debugged by me, and actually originally fixed in BFGMiner 2.6.3:

Thank you 

2.6.4
An Xubuntu 11.04 x86_64 executable is in my github downloads called cgminer-2.6.4a
https://github.com/kanoi/cgminer/downloads

For anyone who didn't realise, it's just the executable file to put in place of 'cgminer'
Nothing else needs changing
First get and extract the full binary release from ckolivas and then copy my file in place of 'cgminer'

No Problems so far on my GPU, BFL or 2xIcarus

The same configure options as cvolivas' binary version
In case anyone was wondering:
CFLAGS="-O2 -W -Wall" ./configure --enable-icarus --enable-bitforce --enable-ztex --enable-modminer --enable-scrypt

I have also added a WinXP cgminer-2.6.4a.exe

This ONLY has BFL + ICA (as below) thus it doesn't need a computer with OpenCL on it
CFLAGS="-O2 -W -Wall" ./configure --enable-icarus --enable-bitforce

You will most likely also need the windowsdlls.zip file there in my downloads since some of my *.dll might be slightly different to ckolivas

FYI: I've deleted all the other 2.6.* executables due to the known bugs in them

And now for something completely different...

New release - 2.6.4, 7th August 2012

Bugfixes, mainly for the crash. I couldn't stand knowing the latest release has a showstopper bug in it.

Human readable changelog

The crash in libcurl was tracked down with the help of Kano. Interestingly this bug was always there but because previous versions queued so much extra, the number of "curls" in existence never dropped low enough to hit the bug.
The scrypt code was updated - now ALL results from a GPU are checked to see if they're valid and if not, instead of being submitted where they are guaranteed to be rejected, they register as hardware errors. This will make tuning your scrypt parameters easier as HW error count will rise if you've set the parameters too high.
A few more tweaks to the BFL code to make it more robust, especially on windows.
Updated miner.php
More information from the API.

Full changelog
- Convert the serial autodetect functions to use int instead of char to
enumerate devices.
- Make the serial open timeout for BFL generically 1 second on windows.
- Deuglify windows autodetect code for BFL.
- There is no point zeroing temperature in BFL if we fail to get a response, and
we should register it as a HW error, suggesting throttling.
- Update SCRYPT README with information about HW errors.
- Use the scrypt CPU code to confirm results from OCL code, and mark failures as
HW errors, making it easier to tune scrypt parameters.
- We may as well leave one curl still available per pool instead of reaping the
last one.
- Need to recheck the pool->curls count on regaining the pool lock after the
pthread conditional wait returns.
- Display reaped debug message outside mutex lock to avoid recursive locking.
- Add specific information when ADL detects error -10 saying the device is not
enabled.
- api.c update API start message and include port number
- miner.php ignore arg when readonly
- miner.php allow pool inputs: delete, addpool, poolpriority

Then I think you got that one dud commit which has since been fixed which caused massive damage. 8897e0657507072448f4e951ce1caadca15b4b30 was the dud commit and it was fixed by 3dd1658e1f3410dfdf00b267593a3cbe7041c645. Check git log to see what you're up to.

I am building from git.  I discovered this problem 12/6/12 9:00 pm EST and was building then.  All the Ubuntu machines are made the same way.  The four cards in the two misbehaving computers are: 3 5870's, 1 6850.

None of what you describe seems related to the other bug discussed here. You appear to have stumbled on something completely different, but what, I haven't got the faintest, unless you happened to be building from git and picked a bad commit to build from.

I was unaware of the reports in this thread.  But have discovered problems with 2.6.3 myself.

I upgraded my 12 computers to 2.6.3 yesterday.  Two of the computers would not mine correctly.  The screen would show only one card out of two with a non-zero hash rate but no shares were generated plus the graphics cards were not loaded as shown with the aticonfig command.  When I reverted to version 2.5.0 they resumed working.

The other computers didn't have any issues.

10 of my machines run Ubuntu 11.04, ati driver 11.6, SDK 2.5.  2 machines run Windows 7.  The failing computers were running Ubuntu 11.04.

That bug is looking pretty consistent now. Thanks for the reports. I guess the spotfire period is not over yet for 2.6.x. I will put up a "stable" vs "development" link on the front page since it's still not up to 2.5 stability till I can sort it out.

I get this on any of my bfl rigs running newest cgminer. Sometimes theres not even a error, I just see my desktop and no cgminer window.

with the previous version no problems.
I prefer to use something workable.

If you guys install DrMingw, you'll get a Debug button on crashes that will dump a stack trace, which is usually much more useful than Windows's crash info.

windows 7 x64
driver 12.06
SDK 2.7
cgminer 2.6.3 - crash every 5 - 6 hours
-------------------------------------------------------------------------------
Log Name:      Application
Source:        Application Error
Date:          06.08.2012 00:18:45
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MINER
Description:
Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x501e265c
Faulting module name: libcurl-4.dll, version: 0.0.0.0, time stamp: 0x4f460f95
Exception code: 0xc0000005
Fault offset: 0x000147d8
Faulting process id: 0x4f0
Faulting application start time: 0x01cd7344c2481a40
Faulting application path: D:\mining\cgminer\cgminer.exe
Faulting module path: D:\mining\cgminer\libcurl-4.dll
Report Id: 234bd240-df43-11e1-8745-001d60c3d47b
-------------------------------------------------------------------------------

back to cgminer 2.6.2

Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x501e265c
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b60
Exception code: 0xc0000005
Fault offset: 0x00052c39
Faulting process id: 0x210
Faulting application start time: 0x01cd737050196b5f
Faulting application path: C:\Users\1\Desktop\cgminer-2.6.3-win32\cgminer.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

edit: Running on win7 32bit, no bfl's, just gpu's, 58xx series.

I'm using W7 x64 and having no issues with scrypt on what is my initial run with it. 24 hours and going now.

So I've tried setting up scrypt in CGminer but regardless of what pool I use it hangs on Longpoll activated.  

http://imgur.com/LumIV

Am I missing something?

I've tried this on 2 of my systems and it's the same.

Here is my log as well from the crash from one of my rigs:

Log Name:      Application
Source:        Application Error
Date:          8/6/2012 3:43:22 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      spklsf4
Description:
Faulting application name: cgminer.exe, version: 0.0.0.0, time stamp: 0x501e265c
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000005
Fault offset: 0x0002dfe4
Faulting process id: 0x107c
Faulting application start time: 0x01cd73311a165c2a
Faulting application path: C:\Users\jensen\Desktop\cgminer-2.6.3-win32\cgminer.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll

I found this in the event log, too (from the 2.6.3 crash):

It happened on my BFL rig last night, same error as before, it had uptime of about 1.5 days before.  Now all 13 of my rigs have done this, back on 2.5 and everything is stable.

I had this happen as well on a 2.6.3 test rig, Win 7 x64: (Was running 2.5.0 prior without issue.)