OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[-ck]

They all seemed to come back up when I replugged them. I was hoping you found a way to catch it and stop calling the device when it thought I was out of memory and clean the memory out.

I'm going to run it for a few hours and see what happens. I hope nothings going bad  ....

The idea is that it isn't supposed to run out of memory instead.

[-ck]

just saw this right now at kncminers homepage:

All,
 
We have our source code here for those of you who are intrested, We will most likely open up a public github when our engineers have time, but until then you can download the source code from the links below
www.kncminer.com/userfiles/file/cgminer_knc.zip
www.kncminer.com/userfiles/file/cgminer_knc.tgz
 
These links will also be availble under our Support page
 
Thanks
 
KnCMiner Team

That's nice to see their sauce at last. Furthermore, KFC have finally decided to engage us (well just me) and are sending me a unit. Unfortunately for KFC users, I am currently being paid by other manufacturers to work on their drivers, so modifying the KFC driver will go lower priority than those other manufacturers, but I will get around to it eventually. [sic]

[-ck]

New version: 3.6.4 - 18th October 2013

Thank you for your patience through this rough ride of changes in 3.6. Hopefully we're close to a stable release on all OSes now. There are actually some other bugfixes in this one besides more libusb massaging.


Human readable changelog:

- Found the source of the memory leak on windows AND the source of the too many files open error on OSX. Both have been rectified, and fully asynchronous transfers are used on all OSes.
- Fixed numerous causes of problems on shutdown.
- Fixed some BFLSC parameters not being read properly.
- Fixed the problem of lost communications and lots of errors on devices on shutdown and possibly unsuccessful shutdown/reset.
- Fixed a bug where  bogus work was being generated at extreme hashrates.
- Decreased the overhead in generating more work for queued devices (eg BFLSC).
- Fixes to klondike driver



Full changelog:

- Fixing the memory leak for remaining semaphores means we can go back to using
async transfers on other OSes with our own timeout management again.
- Use the forcelog function on shutdown to cope with indeterminate console lock
states due to killing of threads.
- Add a forcelog variant of applog which invalidates any console lock to force
output.
- Send pthread_cancel to failed completion_timeout that has timed out.
- Simplify queued hashtable by storing unqueued work separately in a single
pointer.
- bflsc use getinfo chip parallelization if it is present
- bflsc - fix brackets so [Chips] isn't always null
- Remove unused variables.
- Use cgcompletion timeouts for the unreliable shutdown functions on kill_work.
- Fix cgcompletion return code and free on successful completion.
- Provide a cg_completion_timeout helper function for unreliable functions that
takes arbitrary functions and parameters and reliably returns.
- Perform sync transfers on shutdown to allow final transfers to complete.
- Destroy cgsems used after transfers to not leave open files on osx.
- klondike rewrite work control
- allow __work_complete() access
- miner.h allow devices to tv_stamp work

[btc_uzr]

just saw this right now at kncminers homepage:

All,
 
We have our source code here for those of you who are intrested, We will most likely open up a public github when our engineers have time, but until then you can download the source code from the links below
www.kncminer.com/userfiles/file/cgminer_knc.zip
www.kncminer.com/userfiles/file/cgminer_knc.tgz
 
These links will also be availble under our Support page
 
Thanks
 
KnCMiner Team

That's nice to see their sauce at last. Furthermore, KFC have finally decided to engage us (well just me) and are sending me a unit. Unfortunately for KFC users, I am currently being paid by other manufacturers to work on their drivers, so modifying the KFC driver will go lower priority than those other manufacturers, but I will get around to it eventually. [sic]

In hope it pushes the priority a little I'd like to mention that buyers of KFC's 'ultimate boxes' will donate for improvements made on KFC sauce  

[techman05]

I'll try 3.6.4 when I get home. Good you found the problem. Just makes me wish I could direct update from my phone right now.

[Prelude]

I just upgraded my Windows machines from 3.1.1 to 3.6.4 and was wondering if it's possible to have each accepted share show as "1" instead of the share's actual value? I've been checking the readme but can't find anything.

Thanks for your great work, ckolivas.

[Karin]

3.6.4 works great on Macs again, thank you!

There are two minor bugs, but they don't affect mining.  The first one occurs during building, where I must now explicitly use "--disable-adl" whereas I didn't need to in 3.6.3.  ADL isn't used on the Mac, so it's no loss, but since it is a non-default option it's a caveat Mac users will need to remember if they want to successfully build it for 3.6.4.  Here is readout from make:

Code:

In file included from ./sha2.h:36,
                 from cgminer.c:52:
./miner.h:127:30: error: ADL_SDK/adl_sdk.h: No such file or directory
In file included from ./sha2.h:36,
                 from cgminer.c:52:
./miner.h:288: error: expected specifier-qualifier-list before ‘ADLTemperature’
cgminer.c: In function ‘write_config’:
cgminer.c:4393: error: ‘struct gpu_adl’ has no member named ‘overtemp’
cgminer.c:4396: error: ‘struct gpu_adl’ has no member named ‘targettemp’
make[2]: *** [cgminer-cgminer.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Again, using "--disable-adl" solves it.  The other bug(?) occurs when quitting cgminer, the following messages are output.

Code:

[2013-10-18 11:27:04] Received kill message
[2013-10-18 11:27:05] AMU0: Comms error (rerr=-4 amt=0)
[2013-10-18 11:27:05] Thread 2 failure, exiting
[2013-10-18 11:27:05] Failed to read errno=0 in usbutils.c usb_resource_thread():3737
[2013-10-18 11:27:05] Shutdown signal received.

The "usbutils.c" error (4th line down) I think is atypical.  Neither of these affect usability of the program.  Thanks for the great update!

[m3ta]

Raspberry Pi still crashes after some minutes.
Nothing in logs, just a complete freeze.

[Karin]

Unofficial Mac binaries for 3.6.4 now posted.

cgminer for Mac OS X 3.6.4 (direct download link)
http://spaceman.ca/cgminer (website)

[streetuff]

Raspberry Pi still crashes after some minutes.
Nothing in logs, just a complete freeze.

hmmm. got 27 block errupters running on raspi with 3.6.4.... works pretty nice here!

-> http://imgur.com/a/j5vTt

[-ck]

Raspberry Pi still crashes after some minutes.
Nothing in logs, just a complete freeze.

hmmm. got 27 block errupters running on raspi with 3.6.4.... works pretty nice here!

-> http://imgur.com/a/j5vTt

Sweet

[-ck]

3.6.4 works great on Macs again, thank you!

There are two minor bugs, but they don't affect mining.  The first one occurs during building, where I must now explicitly use "--disable-adl" whereas I didn't need to in 3.6.3.  ADL isn't used on the Mac, so it's no loss, but since it is a non-default option it's a caveat Mac users will need to remember if they want to successfully build it for 3.6.4.  Here is readout from make:

Code:

In file included from ./sha2.h:36,
                 from cgminer.c:52:
./miner.h:127:30: error: ADL_SDK/adl_sdk.h: No such file or directory
In file included from ./sha2.h:36,
                 from cgminer.c:52:
./miner.h:288: error: expected specifier-qualifier-list before ‘ADLTemperature’
cgminer.c: In function ‘write_config’:
cgminer.c:4393: error: ‘struct gpu_adl’ has no member named ‘overtemp’
cgminer.c:4396: error: ‘struct gpu_adl’ has no member named ‘targettemp’
make[2]: *** [cgminer-cgminer.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Again, using "--disable-adl" solves it.  The other bug(?) occurs when quitting cgminer, the following messages are output.

Code:

[2013-10-18 11:27:04] Received kill message
[2013-10-18 11:27:05] AMU0: Comms error (rerr=-4 amt=0)
[2013-10-18 11:27:05] Thread 2 failure, exiting
[2013-10-18 11:27:05] Failed to read errno=0 in usbutils.c usb_resource_thread():3737
[2013-10-18 11:27:05] Shutdown signal received.

The "usbutils.c" error (4th line down) I think is atypical.  Neither of these affect usability of the program.  Thanks for the great update!

Great, thanks for confirming testing and providing builds. The failed to read message is fine on shutdown. The reason is macosx doesn't support unnamed semaphores and I built a custom structure and set of functions to imitate them on OSX. During shut down the structures are being torn down so don't work at some stage and that's what you're seeing.
See:
http://ck-hack.blogspot.com/2013/09/unnamed-semaphores-and-pososx.html

Not sure about the ADL issue. Weird since I didn't really touch that code between .3 and .4 (Try 'autoreconf -fi' first if you're building from git)

[-ck]

That's nice to see their sauce at last. Furthermore, KFC have finally decided to engage us (well just me) and are sending me a unit. Unfortunately for KFC users, I am currently being paid by other manufacturers to work on their drivers, so modifying the KFC driver will go lower priority than those other manufacturers, but I will get around to it eventually. [sic]

In hope it pushes the priority a little I'd like to mention that buyers of KFC's 'ultimate boxes' will donate for improvements made on KFC sauce  

That's a good point, but bear in mind I'm being paid professional rates from the other manufacturers in the still-in-design phase who will then be supplying me with prototypes and finally real hardware which really puts to shame the "offer hardware and code after the fact" approach.

[dlasher]

That's a good point, but bear in mind I'm being paid professional rates from the other manufacturers in the still-in-design phase who will then be supplying me with prototypes and finally real hardware which really puts to shame the "offer hardware and code after the fact" approach.

\em crossing fingers that's Cointerra.

[-ck]

That's a good point, but bear in mind I'm being paid professional rates from the other manufacturers in the still-in-design phase who will then be supplying me with prototypes and finally real hardware which really puts to shame the "offer hardware and code after the fact" approach.

\em crossing fingers that's Cointerra.

From another thread:

For what it's worth, CoinTerra have been talking to me about their MCU protocol and I have been working on a preliminary driver model for them, so they have most definitely not disappeared. I suspect they're approaching the communication via forum aspect differently to other manufacturers.

[Askit2]

I notice 3.6.4 came out while I slept. I have some logging that I did on 3.6.3 because having cron kill cgminer off every 20 minutes seemed excessive even for a raspberry pi.

First I have 509 lines of cgminer trying to figure out what device its talking to. All 509 lines precede probing for an alive pool. I have 9 devices.
Each check goes like this

Code:

[2013-10-18 01:49:04] RES: thread starting
 [2013-10-18 01:49:04] BFL looking for BFL 0403:6014 but found 046d:c52b instead
 [2013-10-18 01:49:04] BFL looking for and found BFL 0403:6014
 [2013-10-18 01:49:04] USB lock BitForce 1-17
 [2013-10-18 01:49:04] RES: BitForce (1:17) lock=1
 [2013-10-18 01:49:04] USB res lock BitForce 1-17
 [2013-10-18 01:49:04] RES: BitForce (1:17) lock ok=1
 [2013-10-18 01:49:04] USB init, iManufacturer mismatch - BFL device 1:17
 [2013-10-18 01:49:04] USB free BFL
 [2013-10-18 01:49:04] USB unlock BitForce 1-17
 [2013-10-18 01:49:04] BFL looking for and found BFL 0403:6014
 [2013-10-18 01:49:04] RES: BitForce (1:17) lock=0
 [2013-10-18 01:49:04] USB res unlock BitForce 1-17
AFTER OTHER DEVICES
 [2013-10-18 01:49:04] USB scan devices: checking for ICA devices
 [2013-10-18 01:49:05] ICA looking for ICA 067b:2303 but found 046d:c52b instead
 [2013-10-18 01:49:05] ICA looking for AMU 10c4:ea60 but found 046d:c52b instead
 [2013-10-18 01:49:05] ICA looking for BLT 0403:6001 but found 046d:c52b instead
 [2013-10-18 01:49:05] ICA looking for LLT 0403:6001 but found 046d:c52b instead
 [2013-10-18 01:49:05] ICA looking for CMR 0403:6014 but found 046d:c52b instead
 [2013-10-18 01:49:05] ICA looking for CMR 0403:8350 but found 046d:c52b instead
 [2013-10-18 01:49:05] ICA looking for ICA 067b:2303 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for AMU 10c4:ea60 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for BLT 0403:6001 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for LLT 0403:6001 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for and found CMR 0403:6014
 [2013-10-18 01:49:05] USB lock Icarus 1-17
 [2013-10-18 01:49:05] RES: Icarus (1:17) lock=1
 [2013-10-18 01:49:05] USB res lock Icarus 1-17
 [2013-10-18 01:49:05] RES: Icarus (1:17) lock ok=1
 [2013-10-18 01:49:05] USB init, iProduct mismatch - CMR device 1:17
 [2013-10-18 01:49:05] USB free CMR
 [2013-10-18 01:49:05] USB unlock Icarus 1-17
 [2013-10-18 01:49:05] RES: Icarus (1:17) lock=0
 [2013-10-18 01:49:05] USB res unlock Icarus 1-17
 [2013-10-18 01:49:05] ICA looking for ICA 067b:2303 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for AMU 10c4:ea60 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for BLT 0403:6001 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for LLT 0403:6001 but found 0403:6014 instead
 [2013-10-18 01:49:05] ICA looking for and found CMR 0403:6014

As I see it that means the device ID didn't match up to the expected id. The non matching ones should be a keyboard or one of 4 hubs.
Next we have some accepted work like this.

Code:

 [2013-10-18 01:49:14] Pool 2 difficulty changed to 32
 [2013-10-18 01:49:14] Generated stratum merkle 186092d356a918ff818a07453ffd0b684ad7cd65610ee4a3c6ffc7db2227c8df
 [2013-10-18 01:49:14] Generated stratum header 000000024e7c1f74032837b38c00b7498cae4ad8394627eaa08cc8c20000000a00000000186092d356a918ff818a07453ffd0b684ad7cd65610ee4a3c6ffc7db2227c8df5260e7e519100ab6000000000000008000000000000000000000000000000000000000000000000000000000000000
 [2013-10-18 01:49:14] Work job_id 2765-2e nonce2 0 ntime 5260e7e5
 [2013-10-18 01:49:14] Generated target 00000000000000000000000000000000000000000000000000f8ff0700000000

This goes on for a while from that first share to the first part I don't understand. I have left some data before to try to help you find the error its unlikely the error is here.

Code:

[2013-10-18 01:49:15] Pool 0 stratum+tcp://us3.eclipsemc.com:3333 alive
 [2013-10-18 01:49:15] Pushing sem post to thread 0
 [2013-10-18 01:49:15] Pushing sem post to thread 1
 [2013-10-18 01:49:15] Pushing sem post to thread 2
 [2013-10-18 01:49:15] Pushing sem post to thread 3
 [2013-10-18 01:49:15] Pushing sem post to thread 4
 [2013-10-18 01:49:15] Pushing sem post to thread 5
 [2013-10-18 01:49:15] BAJ3: reset got err 0
 [2013-10-18 01:49:15] BAJ2: reset got err 0
 [2013-10-18 01:49:15] BAJ1: reset got err 0
 [2013-10-18 01:49:15] BAJ: cgid 3 SetLatency got err 0
 [2013-10-18 01:49:15] BAJ4: reset got err 0
 [2013-10-18 01:49:15] Pushing sem post to thread 6
 [2013-10-18 01:49:15] BAJ: cgid 2 SetLatency got err 0
 [2013-10-18 01:49:15] BAJ3: setdata got err 0
 [2013-10-18 01:49:15] BAJ5: reset got err 0
 [2013-10-18 01:49:15] BAJ0: reset got err 0
 [2013-10-18 01:49:15] BAJ: cgid 1 SetLatency got err 0
 [2013-10-18 01:49:15] BAJ2: setdata got err 0
 [2013-10-18 01:49:15] BAJ: cgid 4 SetLatency got err 0
 [2013-10-18 01:49:15] Pushing sem post to thread 7
 [2013-10-18 01:49:15] BAJ3: setbaud got err 0
 [2013-10-18 01:49:15] BAJ: cgid 0 SetLatency got err 0
 [2013-10-18 01:49:15] BAJ4: setdata got err 0
 [2013-10-18 01:49:15] BAJ2: setbaud got err 0
 [2013-10-18 01:49:15] BAJ6: reset got err 0
 [2013-10-18 01:49:15] BAJ1: setdata got err 0
 [2013-10-18 01:49:15] BAJ: cgid 5 SetLatency got err 0
 [2013-10-18 01:49:15] Pushing sem post to thread 8
 [2013-10-18 01:49:15] BAJ0: setdata got err 0
 [2013-10-18 01:49:15] BAJ2: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ: cgid 6 SetLatency got err 0
 [2013-10-18 01:49:15] BAJ3: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ1: setbaud got err 0
 [2013-10-18 01:49:15] BAJ4: setbaud got err 0
 [2013-10-18 01:49:15] BAJ5: setdata got err 0
 [2013-10-18 01:49:15] BAJ7: reset got err 0
 [2013-10-18 01:49:15] BAJ2: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ5: setbaud got err 0
 [2013-10-18 01:49:15] BAJ1: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ4: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ6: setdata got err 0
 [2013-10-18 01:49:15] BAJ3: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ0: setbaud got err 0
 [2013-10-18 01:49:15] BAJ8: reset got err 0
 [2013-10-18 01:49:15] BAJ1: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ4: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ5: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ2: purgetx got err 0
 [2013-10-18 01:49:15] BAJ: cgid 7 SetLatency got err 0
 [2013-10-18 01:49:15] BAJ3: purgetx got err 0
 [2013-10-18 01:49:15] BAJ6: setbaud got err 0
 [2013-10-18 01:49:15] BAJ0: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ4: purgetx got err 0
 [2013-10-18 01:49:15] BAJ3: purgerx got err 0
 [2013-10-18 01:49:15] BAJ5: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ7: setdata got err 0
 [2013-10-18 01:49:15] BAJ1: purgetx got err 0
 [2013-10-18 01:49:15] BAJ: cgid 8 SetLatency got err 0
 [2013-10-18 01:49:15] Selecting pool 0 for work
 [2013-10-18 01:49:15] BAJ2: purgerx got err 0
 [2013-10-18 01:49:15] BAJ6: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ0: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ5: purgetx got err 0
 [2013-10-18 01:49:15] BAJ7: setbaud got err 0
 [2013-10-18 01:49:15] BAJ4: purgerx got err 0
 [2013-10-18 01:49:15] BAJ0: purgetx got err 0
 [2013-10-18 01:49:15] BAJ6: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ8: setdata got err 0
 [2013-10-18 01:49:15] BAJ1: purgerx got err 0
 [2013-10-18 01:49:15] BAJ7: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ8: setbaud got err 0
 [2013-10-18 01:49:15] BAJ5: purgerx got err 0
 [2013-10-18 01:49:15] BAJ6: purgetx got err 0
 [2013-10-18 01:49:15] BAJ0: purgerx got err 0
 [2013-10-18 01:49:15] Generated stratum merkle ffae7d20ce43dafa4dd3018685311102faf42702696b3324be6619aae5bff61d
 [2013-10-18 01:49:15] BAJ7: setmodemctrl got err 0
 [2013-10-18 01:49:15] BAJ8: setflowctrl got err 0
 [2013-10-18 01:49:15] BAJ6: purgerx got err 0

That will be unlikely to have more then things I don't understand. I assume by err 0 there is no error. Then this happens.

Code:

 [2013-10-18 01:49:54] Generated stratum work
 [2013-10-18 01:49:54] Pushing work from pool 0 to hash queue
 [2013-10-18 01:49:54] BAJ 4 usb read err:(1) **UNKNOWN**
 [2013-10-18 01:49:54] USB release BAJ4
 [2013-10-18 01:49:54] USB uninit BAJ4
 [2013-10-18 01:49:54] USB free BAS
 [2013-10-18 01:49:54] USB unlock BitForceSC 1-25
 [2013-10-18 01:49:54] RES: BitForceSC (1:25) lock=0
 [2013-10-18 01:49:54] USB res unlock BitForceSC 1-25
 [2013-10-18 01:49:54] BAJ4: RequestQueJobStatus failed (err=1 amt=0)
 [2013-10-18 01:49:54] BAJ 4 failure, disabling!
 [2013-10-18 01:49:54] Popping work from get queue to get work

 [2013-10-18 01:49:56] Pushing work from pool 0 to hash queue
 [2013-10-18 01:49:56] BAJ 5 usb read err:(1) **UNKNOWN**
 [2013-10-18 01:49:56] USB release BAJ5
 [2013-10-18 01:49:56] USB uninit BAJ5
 [2013-10-18 01:49:56] USB free BAS
 [2013-10-18 01:49:56] USB unlock BitForceSC 1-23
 [2013-10-18 01:49:56] RES: BitForceSC (1:23) lock=0
 [2013-10-18 01:49:56] USB res unlock BitForceSC 1-23
 [2013-10-18 01:49:56] BAJ5: QueJobStatus failed (err=1 amt=0)
 [2013-10-18 01:49:56] BAJ 5 failure, disabling!
 [2013-10-18 01:49:56] Thread 5 being disabled
 [2013-10-18 01:49:56] Waiting on sem in miner thread
 [2013-10-18 01:49:57] [thread 3: 4294967296 hashes, 3522589.9 khash/sec]

 [2013-10-18 01:49:57] BFL looking for and found BFL 0403:6014
 [2013-10-18 01:49:57] USB lock BitForce 1-25
 [2013-10-18 01:49:57] RES: BitForce (1:25) lock=1
 [2013-10-18 01:49:57] USB res lock BitForce 1-25
 [2013-10-18 01:49:57] RES: BitForce (1:25) lock ok=1

 [2013-10-18 01:49:57] Share below target
 [2013-10-18 01:49:57] USB init, iManufacturer mismatch - BFL device 1:25
 [2013-10-18 01:49:57] USB free BFL
 [2013-10-18 01:49:57] USB unlock BitForce 1-25
 [2013-10-18 01:49:57] RES: BitForce (1:25) lock=0
 [2013-10-18 01:49:57] USB res unlock BitForce 1-25
 [2013-10-18 01:49:57] BFL looking for and found BFL 0403:6014
 [2013-10-18 01:49:57] USB lock BitForce 1-23
 [2013-10-18 01:49:57] RES: BitForce (1:23) lock=1
 [2013-10-18 01:49:57] USB res lock BitForce 1-23
 [2013-10-18 01:49:57] RES: BitForce (1:23) lock ok=1
 [2013-10-18 01:49:57] BAJ0: Changed scan sleep time to 666

 [2013-10-18 01:49:57] Pushing work from pool 2 to hash queue
 [2013-10-18 01:49:57] USB init, iManufacturer mismatch - BFL device 1:23
 [2013-10-18 01:49:57] USB free BFL
 [2013-10-18 01:49:57] USB unlock BitForce 1-23
 [2013-10-18 01:49:57] RES: BitForce (1:23) lock=0
 [2013-10-18 01:49:57] USB res unlock BitForce 1-23
 [2013-10-18 01:49:57] BFL looking for and found BFL 0403:6014
 [2013-10-18 01:49:57] BFL looking for and found BFL 0403:6014

 [2013-10-18 01:49:58] BAS looking for and found BAS 0403:6014
 [2013-10-18 01:49:58] USB lock BitForceSC 1-25
 [2013-10-18 01:49:58] RES: BitForceSC (1:25) lock=1
 [2013-10-18 01:49:58] USB res lock BitForceSC 1-25
 [2013-10-18 01:49:58] RES: BitForceSC (1:25) lock ok=1
 [2013-10-18 01:49:58] Popping work from get queue to get work

 [2013-10-18 01:49:58] USB init - BAS device 1:25 usbver=0200 prod='BitFORCE SHA256 SC' manuf='Butterfly Labs' serial='FTWNQPY4'
 [2013-10-18 01:49:58] BAS0: reset got err 0
 [2013-10-18 01:49:58] BAS: cgid 0 SetLatency got err 0
 [2013-10-18 01:49:58] BAS0: setdata got err 0
 [2013-10-18 01:49:58] BAS0: setbaud got err 0
 [2013-10-18 01:49:58] BAS0: setflowctrl got err 0
 [2013-10-18 01:49:58] BAS0: setmodemctrl got err 0
 [2013-10-18 01:49:58] BAS0: purgetx got err 0
 [2013-10-18 01:49:58] BAS0: purgerx got err 0
 [2013-10-18 01:49:58] BitForceSC detect (1:25) found an FPGA 'ERR:INVALID DATA
' ignoring
 [2013-10-18 01:49:58] USB uninit BAS0
 [2013-10-18 01:49:58] USB free BAS
 [2013-10-18 01:49:58] USB unlock BitForceSC 1-25
 [2013-10-18 01:49:58] RES: BitForceSC (1:25) lock=0
 [2013-10-18 01:49:58] USB res unlock BitForceSC 1-25
 [2013-10-18 01:49:58] BAS looking for and found BAS 0403:6014
 [2013-10-18 01:49:58] USB lock BitForceSC 1-23
 [2013-10-18 01:49:58] RES: BitForceSC (1:23) lock=1
 [2013-10-18 01:49:58] USB res lock BitForceSC 1-23
 [2013-10-18 01:49:58] RES: BitForceSC (1:23) lock ok=1
 [2013-10-18 01:49:58] Popping work from get queue to get work

 [2013-10-18 01:49:58] USB init - BAS device 1:23 usbver=0200 prod='BitFORCE SHA256 SC' manuf='Butterfly Labs' serial='FTWNQQ5S'
 [2013-10-18 01:49:58] Share below target
 [2013-10-18 01:49:58]  Proof: 0000000073bc6872d8111f9ac9ed169759bdfe2343ae45fc58691f3b28fab2f6
Target: 0000000007fff800000000000000000000000000000000000000000000000000
TrgVal? no (false positive; hash > target)
 [2013-10-18 01:49:58] BAS0: reset got err 0
 [2013-10-18 01:49:58] Share below target
 [2013-10-18 01:49:58]  Proof: 00000000ff731b4bdf51b449e1d596e4ab2c6e43cd4fb1c41cf17b21dfe04f58
Target: 0000000007fff800000000000000000000000000000000000000000000000000
TrgVal? no (false positive; hash > target)
 [2013-10-18 01:49:58] BAS: cgid 0 SetLatency got err 0
 [2013-10-18 01:49:58] Share below target
 [2013-10-18 01:49:58] BAS0: setdata got err 0
 [2013-10-18 01:49:58]  Proof: 00000000e1b7da4d6ad9554414722d135f3a11776877eb5fcf6a24e9ae875d38
Target: 0000000007fff800000000000000000000000000000000000000000000000000
TrgVal? no (false positive; hash > target)
 [2013-10-18 01:49:58] Share below target
 [2013-10-18 01:49:58] BAS0: setbaud got err 0
 [2013-10-18 01:49:58] BAS0: setflowctrl got err 0
 [2013-10-18 01:49:58]  Proof: 00000000f4411d882d9c6c52bbdd4fafe8c7ec67aad7d862998c02b262b959f2
Target: 0000000007fff800000000000000000000000000000000000000000000000000
TrgVal? no (false positive; hash > target)
 [2013-10-18 01:49:58] BAS0: setmodemctrl got err 0
 [2013-10-18 01:49:58] Share below target
 [2013-10-18 01:49:58] BAS0: purgetx got err 0
 [2013-10-18 01:49:58] BAS0: purgerx got err 0
 [2013-10-18 01:49:58]  Proof: 00000000500cf65acce179fd5ba4df54e97460f9a42c20a079269d8dcde15f50

 [2013-10-18 01:49:58] Share below target
 [2013-10-18 01:49:59] BAS 0 usb read err:(1) **UNKNOWN**
 [2013-10-18 01:49:59] USB release BAS0
 [2013-10-18 01:49:59] USB uninit BAS0
 [2013-10-18 01:49:59] USB free BAS
 [2013-10-18 01:49:59] USB unlock BitForceSC 1-23
 [2013-10-18 01:49:59] RES: BitForceSC (1:23) lock=0
 [2013-10-18 01:49:59] USB res unlock BitForceSC 1-23
 [2013-10-18 01:49:59] BitForceSC detect (1:23) get details returned nothing (0:1)
 [2013-10-18 01:49:59] BitForceSC detect (1:23) send details request failed (0:-4)
 [2013-10-18 01:49:59] BitForceSC detect (1:23) send details request failed (0:-4)
 [2013-10-18 01:49:59] USB unlock BitForceSC 1-23
 [2013-10-18 01:49:59] RES: BitForceSC (1:23) lock=0
 [2013-10-18 01:49:59] USB res unlock BitForceSC 1-23
 [2013-10-18 01:49:59] FAIL: USB get_lock not found (1:23)
 [2013-10-18 01:49:59] BAS looking for and found BAS 0403:6014
 [2013-10-18 01:49:59] FAIL: USB remove not already in use (1:23)
 [2013-10-18 01:49:59] BAS looking for and found BAS 0403:6014
 [2013-10-18 01:49:59] BAS looking for BAS 0403:6014 but found 05e3:0612 instead
 [2013-10-18 01:49:59] BAS looking for and found BAS 0403:6014
 [2013-10-18 01:49:59] BAS looking for BAS 0403:6014 but found 05e3:0612 instead
 [2013-10-18 01:49:59] BAS looking for BAS 0403:6014 but found 0424:ec00 instead
 [2013-10-18 01:49:59] BAS looking for BAS 0403:6014 but found 0424:9512 instead
 [2013-10-18 01:49:59] BAS looking for BAS 0403:6014 but found 1d6b:0002 instead
 [2013-10-18 01:49:59] USB scan devices: checking for AVA devices
 [2013-10-18 01:49:59] [thread 3: 4294967296 hashes, 3887604.4 khash/sec]
 [2013-10-18 01:49:59] Popping work from get queue to get work

As errors still happen on 3.6.4 built from git I don't think the bug is smashed. Though it seems I can now restart every 30 minutes instead of 20 so it is a bit better.

[-ck]

I notice 3.6.4 came out while I slept. I have some logging that I did on 3.6.3 because having cron kill cgminer off every 20 minutes seemed excessive even for a raspberry pi.

First I have 509 lines of cgminer trying to figure out what device its talking to. All 509 lines precede probing for an alive pool. I have 9 devices.
Each check goes like this


As I see it that means the device ID didn't match up to the expected id. The non matching ones should be a keyboard or one of 4 hubs.
Next we have some accepted work like this.

That will be unlikely to have more then things I don't understand. I assume by err 0 there is no error. Then this happens.

Code:

 [2013-10-18 01:49:54] BAJ 4 usb read err:(1) **UNKNOWN**

 [2013-10-18 01:49:56] BAJ 5 usb read err:(1) **UNKNOWN**

 [2013-10-18 01:49:59] BAS 0 usb read err:(1) **UNKNOWN**

As errors still happen on 3.6.4 built from git I don't think the bug is smashed. Though it seems I can now restart every 30 minutes instead of 20 so it is a bit better.

1. Normal for lots of looking for new devices to occur. The more usb things you have plugged in and the more drivers you compile in, the more looking will occur.

2. All looks fine.

3. Error 1 is a failed transfer - I plan to add more informational output than just unknown in the future. There is no way to recover from that and it suggests a communication problem. Meaning... I'm not sure this is a code problem?

[-ck]

No errors in the new version for me 

Great

Well after this frantic pace of development, I'm going to take a little breather and concentrate on some other areas. I think the code is quite stable but needs a lot more people testing it, so I will leave the "stable version for windows/osx" recommendation at 3.5.1. There will be some downtime on my server this weekend so grab your downloads now even if you don't plan to move to the new version immediately.

[mdude77]

No errors in the new version for me 

Great

Well after this frantic pace of development, I'm going to take a little breather and concentrate on some other areas. I think the code is quite stable but needs a lot more people testing it, so I will leave the "stable version for windows/osx" recommendation at 3.5.1. There will be some downtime on my server this weekend so grab your downloads now even if you don't plan to move to the new version immediately.

3.6.4 is stable for me so far too.  At least more than any of the 3.5 series was.  Hopefully the winsock error is gone too.

M

[pazor]

cgminer 3.6.x does not support ztex fpgas anymore ?