Author

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

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
I doesnt actually crash and exit, the interface just stops responding. Also it stops submitting shares, I use the 50btc.com pool and when the miner hangs the drop in mhash/s is seen quickly in the pools API. And GPU-Z shows the gpus continue running the kernels.

What is the CGMINER GPU status and CGMINER pool status? Are your other network applications continue operating when you switch user?

Use cgminer API to read GPU and POOL status.

This happens after switching user:

Code:
08/16/12 14:49:06 0x12e4 INF refreshADLInfo(): min GPU utilization: 0%, max GPU temperature: 75C

...

08/16/12 14:49:21 0x12dc SVR monitorThread(): GPU mining activity: 0% is lower than threshold: 20%, timeout of 80 seconds has been reached, will restart miner process after: 15 seconds...

08/16/12 14:49:21 0x12dc SVR restartMiner(): killing miner process: 1164
I've no idea what creates that log ...
hero member
Activity: 626
Merit: 500
Mining since May 2011.
New version - 2.6.5, 15th August 2012

So far working great on Pi with multiple BFLs.

Well... I started having this issue: (Not bitching, just providing feedback)


I have two Pi, both configured identical except for hostname and IP. Both have two BFL Singles attached directly. I switched back to 2.5.0 on one of them and it has not crashed since, while on the other running 2.6.5 it has after 6-7 hours with the Comms error as shown above. I have also swapped which Pi was running 2.6.5 and this issue seems to follow it. (after 6+ hours) I have also swapped the BFL's around, it appears to be random as to which fails. Open for suggestions or let me know if there is a way I can help with configuring a log file or something that.
full member
Activity: 193
Merit: 100
I doesnt actually crash and exit, the interface just stops responding. Also it stops submitting shares, I use the 50btc.com pool and when the miner hangs the drop in mhash/s is seen quickly in the pools API. And GPU-Z shows the gpus continue running the kernels.

What is the CGMINER GPU status and CGMINER pool status? Are your other network applications continue operating when you switch user?

Use cgminer API to read GPU and POOL status.

This happens after switching user:

Code:
08/16/12 14:49:06 0x12e4 INF refreshADLInfo(): min GPU utilization: 0%, max GPU temperature: 75C

08/16/12 14:49:06 0x12e4 DBG adlPollingThread(): ADL H/W reading done, status: ADL_STATUS_CLOSED

08/16/12 14:49:10 0x0e28 INF listenForCommands(): new connection from: 127.0.0.1

08/16/12 14:49:11 0x0e28 SVR listenForCommands(): received invalid request

08/16/12 14:49:11 0x0e28 INF listenForCommands(): closing accepted connection.

08/16/12 14:49:11 0x0e28 INF listenForCommands(): new connection from: 127.0.0.1

08/16/12 14:49:12 0x0e28 DBG listenForCommands(): received 'status' command

08/16/12 14:49:12 0x0e28 DBG getWatchdogStatus(): status len: 927

08/16/12 14:49:12 0x0e28 INF listenForCommands(): closing accepted connection.

08/16/12 14:49:17 0x0e28 INF listenForCommands(): new connection from: 127.0.0.1

08/16/12 14:49:18 0x0e28 SVR listenForCommands(): received invalid request

08/16/12 14:49:18 0x0e28 INF listenForCommands(): closing accepted connection.

08/16/12 14:49:18 0x0e28 INF listenForCommands(): new connection from: 127.0.0.1

08/16/12 14:49:18 0x0e28 DBG listenForCommands(): received 'status' command

08/16/12 14:49:18 0x0e28 DBG getWatchdogStatus(): status len: 927

08/16/12 14:49:18 0x0e28 INF listenForCommands(): closing accepted connection.

08/16/12 14:49:21 0x12dc DBG monitorThread(): max gpu temperature (75C) stays below defined threshold (86C)

08/16/12 14:49:21 0x12dc DBG monitorThread(): all GPU fans appear to be functional

08/16/12 14:49:21 0x12dc SVR monitorThread(): GPU mining activity: 0% is lower than threshold: 20%, timeout of 80 seconds has been reached, will restart miner process after: 15 seconds...

08/16/12 14:49:21 0x12dc SVR restartMiner(): killing miner process: 1164
full member
Activity: 193
Merit: 100
CGMINER crashes when using Switch User on Windows. This is the only miner that does this, all other miners continue happily mining in the background.
When the crash happens, the mining kernel continues to run on the gpus but no shares are submitted, and the cgminer interface just hangs and doesnt respond.

I tried all versions back to 2.0.4, they all crash when switching user.

My machine:
Windows 7 x64
Catalyst 12.6, APP 2.7
Radeon 7950 and 5850

Does the cgminer actually crash or continues running in ALIVE state and not submitting shares?

If cgminer actually crashes, post WER details.

If cgminer process is still running, check GPU/PGA and pool statuses using ANUBIS or other API status display tools.


I doesnt actually crash and exit, the interface just stops responding. Also it stops submitting shares, I use the 50btc.com pool and when the miner hangs the drop in mhash/s is seen quickly in the pools API. And GPU-Z shows the gpus continue running the kernels.
hero member
Activity: 576
Merit: 500
Make your msdos window bigger by default.

still no luck, get the APPCRASH again
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
For some reason when I try to run cgminer with 2 GPUs and 4 BFLs it crashes. I have to run 2 separate instances, one with -S noauto for GPUs and other with all the BFLs. I can run 2 GPUs and 2 BFLs on same cgminer instance, but not all 6 at once. It happens on all versions of cgminer. Any idea why this is?

Not sure if this helps at all, but here is the windows log:
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   cgminer.exe
  Application Version:   0.0.0.0
  Application Timestamp:   502b065b
  Fault Module Name:   cgminer.exe
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   502b065b
  Exception Code:   c0000005
  Exception Offset:   0000a74d
  OS Version:   6.1.7601.2.1.0.256.4
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789
Make your msdos window bigger by default.
hero member
Activity: 576
Merit: 500
For some reason when I try to run cgminer with 2 GPUs and 4 BFLs it crashes. I have to run 2 separate instances, one with -S noauto for GPUs and other with all the BFLs. I can run 2 GPUs and 2 BFLs on same cgminer instance, but not all 6 at once. It happens on all versions of cgminer. Any idea why this is?

Not sure if this helps at all, but here is the windows log:
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   cgminer.exe
  Application Version:   0.0.0.0
  Application Timestamp:   502b065b
  Fault Module Name:   cgminer.exe
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   502b065b
  Exception Code:   c0000005
  Exception Offset:   0000a74d
  OS Version:   6.1.7601.2.1.0.256.4
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Quick question: Can someone tell me why the fan output on my 2nd card looks all wonky? Top card is a Gigabyte 7970, and bottom card is a Gigabyte 7770.


Not all GPUs support fanspeed monitoring by RPM; only the set percentage. You can see that from status line at the top. cgminer shouldn't be trying to show you the rpm below as it's completely invalid.
legendary
Activity: 952
Merit: 1000
Quick question: Can someone tell me why the fan output on my 2nd card looks all wonky? Top card is a Gigabyte 7970, and bottom card is a Gigabyte 7770.

hero member
Activity: 560
Merit: 500
I have found a bug that is reproducible. It seems cgminer always declares 1 ztex board dead after a while (1h or so). Interestingly enough this does not happen on my other rigs that are x86 based, and have also GPU's connected to them. Very weird indeed. Reproducible also in BFGMiner.

Also, if 1 board is declared dead and is kept connected to the computer, no more boards will be decalred dead. If I disconnect the dead board, soon another one will get sick and dead.

System setup:
CGMiner 2.6.4 running on Raspberry Pi
14-18 ztex 1.15x
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
On the 2.6.5 binary;
Seeing the same bug we had a while back again...  Undecided  (Well, may not be the same bug, but it's acting the same)

Intensity pegs to -10 when set to dynamic on a GPU with a display on it.
Hmm I think we had the discussion before, but are you sure the dynamic is set to the correct device?
Have only one GPU 6770, same thing there.
On LTC mining I have I=11, I change it to dynamic, it jumps to 9 for a second or two then falls to -10 and stays there.
full member
Activity: 193
Merit: 100
CGMINER crashes when using Switch User on Windows. This is the only miner that does this, all other miners continue happily mining in the background.
When the crash happens, the mining kernel continues to run on the gpus but no shares are submitted, and the cgminer interface just hangs and doesnt respond.

I tried all versions back to 2.0.4, they all crash when switching user.

My machine:
Windows 7 x64
Catalyst 12.6, APP 2.7
Radeon 7950 and 5850
legendary
Activity: 3583
Merit: 1094
Think for yourself
When using the load balance feature between 2 pools, I always have more accepted shares on pool 0 than pool 1. If I switch the pools on my .conf file I get the same result. Pool 0 always has a considerably higher amount of accepted shares than pool 1.

I have noticed a similar behavior too, but with me pool 3 gets almost all of the shares and pools 0, 1 and 2 get starved.
Sam
This is simply that one pool has rolltime and the others do not. It's such an efficient option that it's really a waste of resources to not use it on the one pool since the others have not moved out of the dark ages. But I guess I could add more black magic to cope with that....

I'm not worried about it, especially with the explanation's of the probable cause.
Thanks,
Sam
sr. member
Activity: 378
Merit: 250
Why is it so damn hot in here?
On the 2.6.5 binary;
Seeing the same bug we had a while back again...  Undecided  (Well, may not be the same bug, but it's acting the same)

Intensity pegs to -10 when set to dynamic on a GPU with a display on it.

Windows 7 x64, Catalyst 12.6, SDK 2.6, Two 5870s no crossfire.

Let me know if you need a debug dump or anything else.


Hmm I think we had the discussion before, but are you sure the dynamic is set to the correct device?

Yeah, we had this discussion before, I'll be damned if I can find it again though.  Worst search function ever.  The per device settings should be okay, I just moved my config file to the newer version and didn't touch anything else.  Let me try it with a clean config, be right back.

Edit: Seems to be working as expected with no config file.  Now I have to find out what is borked up in my old config file.  Sad
       At least I didn't go "OMG, I'm geeting less Mh/s with new version, you broke something!!!11!!"   Grin

Edit#2:  Okay, I spoke to soon, after running a few minutes, the display GPU pegs down to -10 still.  It doesn't happen right after starting.

Edit#3:  Okay, further "testing" shows that it it happening when my display GPU is set to dynamic, and the other GPU is set to a fixed intensity.  Also seeing a massive jump in CPU usage when it happens, using 50% CPU, one whole core when it goes to -10 I.  Going to let it run for a bit with both GPUs set to dynamic and see if it happens.

Edit#4:  After running with both GPUs set to dynamic, now the GPU with no monitor connected has pegged to -10 I.  Going to have to use the older version I have for the time being.  :/
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
On the 2.6.5 binary;
Seeing the same bug we had a while back again...  Undecided  (Well, may not be the same bug, but it's acting the same)

Intensity pegs to -10 when set to dynamic on a GPU with a display on it.

Windows 7 x64, Catalyst 12.6, SDK 2.6, Two 5870s no crossfire.

Let me know if you need a debug dump or anything else.


Hmm I think we had the discussion before, but are you sure the dynamic is set to the correct device?
sr. member
Activity: 378
Merit: 250
Why is it so damn hot in here?
On the 2.6.5 binary;
Seeing the same bug we had a while back again...  Undecided  (Well, may not be the same bug, but it's acting the same)

Intensity pegs to -10 when set to dynamic on a GPU with a display on it.

Windows 7 x64, Catalyst 12.6, SDK 2.6, Two 5870s no crossfire.

Let me know if you need a debug dump or anything else.

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Sorry if this is a dump question but, is it possible to undervolt my 7970 under Linux?!
No
legendary
Activity: 1204
Merit: 1000
฿itcoin: Currency of Resistance!
Sorry if this is a dump question but, is it possible to undervolt my 7970 under Linux?!

I mean, I set it up but I don't see any wattage drop at my kill-a-watt...  :-/

I'm using Ubuntu 12.04 64 bits, Catalyst 12.6 and CGMiner 2.6.5 binary...

Thanks!
Thiago
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
When using the load balance feature between 2 pools, I always have more accepted shares on pool 0 than pool 1. If I switch the pools on my .conf file I get the same result. Pool 0 always has a considerably higher amount of accepted shares than pool 1.

I have noticed a similar behavior too, but with me pool 3 gets almost all of the shares and pools 0, 1 and 2 get starved.
Sam
This is simply that one pool has rolltime and the others do not. It's such an efficient option that it's really a waste of resources to not use it on the one pool since the others have not moved out of the dark ages. But I guess I could add more black magic to cope with that....
sr. member
Activity: 271
Merit: 250
Both pools are difficulty 1 shares
Jump to: