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

[-ck]

New version: 3.7.2, 5th November 2013

In the interests of not leaving a relatively unstable release out there, here's a pure bugfix release.


Human readable changelog:

- Fix for crashes on startup and hotplug.
- Fix for hangs doing no further work after a block change.
- Fix yet again scrypt showing a block solve with every highish diff share.
- Try to find a compromise between the various ends of the windows+AMU timeout issue spectrum.
- Write errors will cause a device failure, allowing cgminer to attempt to hotplug them again.
- Icarus based devices will hopefully align on the display with others.
- Fix for short periods of no/idled work on avalon devices due to async restarts with block changes.
- Fix for diff shown on big endian machines
- Fix for building with curses disabled.
- Other low level clean ups.


Full changelog:

- Clean up completely on avalon shutdown.
- Use cgsem timed waits in avalon driver to not miss any queued wake ups to
account for async messages coming during a flush work.
- Statline before is too long on icarus that doesn't have monitoring.
- Different windows+usb combinations respond with varying levels of reliability
wrt timeouts so use a nominal extra 40ms before cancelling transfers that fail
to time out on their own.
- Do all hotplug_process under the write mining_thr_lock
- Fix for opt_worktime on big endian machines.
- Correct set_blockdiff for big endian machines.
- Make sure cgpu exists in the restart threads loop in cases of hotplug etc.
- Treat usb write timeout errors as unrecoverable.
- Transfer errors are filtered out in usbutils now so no need to look for them
in NODEV checks.
- Remove now unused entries from struct cg_usb_device
- Do not double up with checking for end of timeout measurements in usb
read/write.
- Do get_work in fill_queue without holding other locks.
- Initialise usb after all the locks and conditionals are initialised.
- Use only a trylock in flush queue to prevent deadlocks.
- Add a wr_trylock wrapper for pthread rw lock write trylock.
- Scale diff for scrypt when testing for block solves.
- Fix for non curses build.

[jmc1517]

No, there are too many changes post 3.5.1 that everything else depends on. In the same way new versions come out for other reasons and need bugfixes, the solution is to fix the current  behaviour, not go to the old behaviour.

EDIT: What's interesting is that the pattern is the same every time in your logs. One device disappears and then another has timeouts forever more. However it also seems to keep hashing fine based on the fact that your summary shows the hashrate is the same for AMU0 as the rest.

EDIT2: Here're the next tests (note this is specifically for your issue now since last report aigeezer's was working)
http://ck.kolivas.org/apps/cgminer/temp/cgminer-lt.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-nt.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer-et.exe

Appreciate your dedication to this, I'll stick with it for as long as you want to keep testing, but quite willing to stick with the older version if you want to spend your time more productively!

So, latest test results. Nothing to very hopeful, at least to my untrained eye:
Started cgminer-lt @10:21, zombie at 11:01. Test ended
Started cgminer-nt @11:06, zombie at 12:07. Test ended

Started cgminer-et at 12:11. First zombie AMU29 appeared at 12:18 just as I started uploading to Flickr aagin (coincidence?). The offending AMU was replugged at 12:22 and started working again as AMU 34.

Two AMU LEDs came on full and 2 zombies appeared in the display at 12:25, AMU 14&16, but AMU 16 started working again. Tis behaviour is new, perhaps?  It was removed from the table and reappeared as AMU 35. AMU 14 was still reported as zombie, but there was no corresponding "NO_DEVICE" in the logfile for either of these two. Strange?

I tried re-plugging AMU 14 @12:30 but it did not get recognised again (LED came back full on and the zombie remained in the display table). Test ended...

Edit to add logfile links:
 https://dl.dropboxusercontent.com/u/44240170/logfile-lt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-nt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-et.txt

Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

[-ck]

So, latest test results. Nothing to very hopeful, at least to my untrained eye:
Started cgminer-lt @10:21, zombie at 11:01. Test ended
Started cgminer-nt @11:06, zombie at 12:07. Test ended

Started cgminer-et at 12:11. First zombie AMU29 appeared at 12:18 just as I started uploading to Flickr aagin (coincidence?). The offending AMU was replugged at 12:22 and started working again as AMU 34.

Two AMU LEDs came on full and 2 zombies appeared in the display at 12:25, AMU 14&16, but AMU 16 started working again. Tis behaviour is new, perhaps?  It was removed from the table and reappeared as AMU 35. AMU 14 was still reported as zombie, but there was no corresponding "NO_DEVICE" in the logfile for either of these two. Strange?

I tried re-plugging AMU 14 @12:30 but it did not get recognised again (LED came back full on and the zombie remained in the display table). Test ended...

Edit to add logfile links:
 https://dl.dropboxusercontent.com/u/44240170/logfile-lt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-nt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-et.txt

Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

Thanks for that. 3.7.1 is closest to -et in behaviour.

[whiteEAGLE]

Does sgminer run with Nanofury NF1 USB-sticks?

If yes - how can i get it to work?

[-ck]

Does sgminer run with Nanofury NF1 USB-sticks?

If yes - how can i get it to work?

No

[whiteEAGLE]

is this planed to add?

[aigeezer]

So, latest test results. Nothing to very hopeful, at least to my untrained eye:
Started cgminer-lt @10:21, zombie at 11:01. Test ended
Started cgminer-nt @11:06, zombie at 12:07. Test ended

Started cgminer-et at 12:11. First zombie AMU29 appeared at 12:18 just as I started uploading to Flickr aagin (coincidence?). The offending AMU was replugged at 12:22 and started working again as AMU 34.

Two AMU LEDs came on full and 2 zombies appeared in the display at 12:25, AMU 14&16, but AMU 16 started working again. Tis behaviour is new, perhaps?  It was removed from the table and reappeared as AMU 35. AMU 14 was still reported as zombie, but there was no corresponding "NO_DEVICE" in the logfile for either of these two. Strange?

I tried re-plugging AMU 14 @12:30 but it did not get recognised again (LED came back full on and the zombie remained in the display table). Test ended...

Edit to add logfile links:
 https://dl.dropboxusercontent.com/u/44240170/logfile-lt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-nt.txt
 https://dl.dropboxusercontent.com/u/44240170/logfile-et.txt

Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

Thanks for that. 3.7.1 is closest to -et in behaviour.

3.7.1 froze on startup for me and did not respond to the Q command. I tried it twice, then reverted to 3.7.0 which seems to be running fine. Prior to that, 3.7.0 had run without error for 24 hours before I tried the update to 3.7.1.

[jmc1517]

So, latest test results.
Edit: Just noticed the 3.7.1 release.  I'll give it a try. You never know!
 

Thanks for that. 3.7.1 is closest to -et in behaviour.

3.7.1 doesn't start up for me - it just hangs and doesn't turn off any of the AMU LEDs.  No screen display.  I've tried both zip and 7z archives, running cgminer with my usual conf file, and also cgminer-nogpu.  No dice.  Tried a few times, then back to 3.5.1 which started up ok.  I guess it's not just me, seeing the previous post from aigeezer.
 

[-ck]

Shit shit shit, last minute breakage 

pretend you didn't see 3.7.1

[-ck]

3.7.2 uploading as we speak/type. Besides, even numbers always sound more stable.

EDIT: And it's up.

[aigeezer]

3.7.2 uploading as we speak/type. Besides, even numbers always sound more stable.

EDIT: And it's up.

It's off to a good start for me (Windows zip version).

[P_Shep]

Getting this compile error:

cgminer-driver-knc-spi-fpga.o: In function `knc_process_response.constprop.6':
driver-knc-spi-fpga.c:(.text+0xf54): undefined reference to `WEXITSTATUS'
cgminer-driver-knc-spi-fpga.o: In function `knc_scanwork':
driver-knc-spi-fpga.c:(.text+0x1700): undefined reference to `WEXITSTATUS'

[-ck]

Getting this compile error:

cgminer-driver-knc-spi-fpga.o: In function `knc_process_response.constprop.6':
driver-knc-spi-fpga.c:(.text+0xf54): undefined reference to `WEXITSTATUS'
cgminer-driver-knc-spi-fpga.o: In function `knc_scanwork':
driver-knc-spi-fpga.c:(.text+0x1700): undefined reference to `WEXITSTATUS'

The KfC sauce is meant to only cook on this architecture: arm-angstrom-linux-gnueabi
There is no point trying to compile it for anything else since the hardware only exists on a beaglebone. What are you trying to compile it for?

[P_Shep]

Getting this compile error:

cgminer-driver-knc-spi-fpga.o: In function `knc_process_response.constprop.6':
driver-knc-spi-fpga.c:(.text+0xf54): undefined reference to `WEXITSTATUS'
cgminer-driver-knc-spi-fpga.o: In function `knc_scanwork':
driver-knc-spi-fpga.c:(.text+0x1700): undefined reference to `WEXITSTATUS'

The KfC sauce is meant to only cook on this architecture: arm-angstrom-linux-gnueabi
There is no point trying to compile it for anything else since the hardware only exists on a beaglebone. What are you trying to compile it for?

Ah, ok, I just enabled everything. Complies fine without.
And thanks for adding the '--with-system-libusb'

[jmc1517]

Downloaded and started running cgminer-3.7.2

After about 40 minutes, 2 AMU LEDs (27/28) came on solid, but by the time I had checked the display only 1 was showing as zombie, then both LEDs went out and no zombies remained in the display. Yay!  Both AMUs had re-initialised as AMU 34/35.  This looks very promising

[Jeffrey]

Hi,

Maybe a weird question, but is there a limit on the amount of Block Erupters cgminer is able to run? I'm asking this because I'm trying to set 98 up, (2x49port hubs) and it doesn't work.

When I connect hub 1 (with 49 BE's) it's fine. When I disconnect 1 and connect hub 2, it's fine. (so it's not a power issue, both are powered by an ATX supply with 30a on 5v) When I connect both of them at the same time, cgminer tells me it can't find any device and it's waiting for a hotplug.

When connect 1 full and a couple on the 2nd hub, it works. cgminer crashes on hotplug, so I have to close it, add more, and restart it. This works until I have 59. 59 is fine, 60 gives this error. I've tried putting the 60th in different usb ports (also on the laptop host itself), also other sticks, but it just won't accept  60 or more.

This is the behavior on cgminer 3.6.4, 3.7.0 and 3.7.2 (and often, 3.7.2 crashes after 1 or 2 minutes regardless of how many I've attached)

Using windows 7 64bit

Any advise?

[SpAcEDeViL]

CGMiner 3.6.6. Crash Raspberry Pi with Raspbian after 20 min, or 2 h or 6h... random system freeze.

Only restart with power off.

[chadtn]

CGMiner 3.6.6. Crash Raspberry Pi with Raspbian after 20 min, or 2 h or 6h... random system freeze.

Only restart with power off.

I did an update & upgrade yesterday in anticipation of my K16's showing up.  As soon as I popped them in my Raspberry Pi running Raspbian Wheezy started crashing constantly any time I tried to hash.  zipiju posted the following on www.projectklondike.com and it fixed my problem instantly:

Raspberry Pi is locking up when running CGMiner

If your RPi is freezing randomly after some time (could be minutes, could be hours or days) with error like Oops: PREEMPT ARM, CPU0 Not tainted printed out over HDMI, and with locked up ethernet and USB interfaces, you have to add following option to the /boot/cmdline.txt file on SD card:

slub_debug=FP
Make sure you do not add that option to the new line if some other options are already present in that file. Always paste it behind all other options delimited with space. Also, before editing, make sure your /boot partition is mounted by issuing this command:

mount | grep boot
It should print out something like this when it is mounted:

/dev/mmcblk0p1 on /boot type vfat (rw,noatime)
If it is not mounted, that command returns nothing. To mount /boot partition, just do:

mount /boot
Freezing is caused by some bug probably in Kernel itself, as you can read on http://www.raspberrypi.org/phpBB3/viewtopic.php?t=55370&p=421883:

"We recently changed the kernel memory allocator to SLUB for increased performance (incidentally also allowing this sort of debugging) which meant that this bug, which has probably always been there, has crawled into the open." by jdb.

To this date, this bug is still present in Master and Next branches of RPi firmware/kernel (https://github.com/raspberrypi/firmware) - up to a Kernel version 3.10.15 and maybe even latter.

Chad

[-ck]

Yay finally a night's sleep after a release without showstopper bugs.

[SpAcEDeViL]

Hy,

i have

Code:

Linux raspberrypi 3.10.18+ #577 Tue Nov 5 12:33:36 GMT 2013 armv6l GNU/Linux

Code:

Oct 18 2013 16:07:43
Copyright (c) 2012 Broadcom
version dbda126981820ea5681263042435388dddf65131 (tainted) (release)
root@raspberrypi:~#

Last kern.log before crash:

Code:

Nov  5 21:19:00 raspberrypi kernel: [   10.741945] bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100k)
Nov  5 21:19:00 raspberrypi kernel: [   10.836278] bcm2708_spi bcm2708_spi.0: master is unqueued, this is deprecated
Nov  5 21:19:00 raspberrypi kernel: [   10.846583] bcm2708_spi bcm2708_spi.0: SPI Controller at 0x20204000 (irq 80)
Nov  5 21:19:00 raspberrypi kernel: [   12.340492] usbcore: registered new interface driver rtl8192cu
Nov  5 21:19:00 raspberrypi kernel: [   18.815515] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Nov  5 21:19:00 raspberrypi kernel: [   19.255702] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Nov  5 21:19:00 raspberrypi kernel: [   20.328267] i2c /dev entries driver
Nov  5 21:19:00 raspberrypi kernel: [   25.039911] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov  5 21:19:00 raspberrypi kernel: [   28.192313] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Nov  5 21:19:02 raspberrypi kernel: [   50.173568] Adding 102396k swap on /var/swap.  Priority:-1 extents:2 across:507900k SS
Nov  5 21:25:37 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.
Nov  5 21:25:37 raspberrypi kernel: [    0.000000] Booting Linux on physical CPU 0x0

Now i have install cgminer 3.7.2
And reboot it with slub_debug=FP in my cmdline.txt

Code:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait slub_debug=FP

i hope the system runs now...