Quote from: SLok on September 12, 2014, 02:45:35 AM

Quote from: lightfoot on September 12, 2014, 02:04:31 AM

Quote from: SLok on September 11, 2014, 02:17:01 PM

Do you also see messages like "sanity check, device is processing unknown work, device is missing queued job. device flushed (goes by too fast), failed to find work for queue results" in the bfgminer cmd window?

Interesting. When I first powered up I got a nice 700gh. After an hour I shut it down to switch power supplies, fired up, and saw some error messages and about 600gh speeds.

Shut it down, went back to previous supply, started up. Same.

This afternoon I shut it down, let it sit for 20 minutes to cool off, powered it up. 700gh, no errors I can see (I don't stare at it, just check every once in awhile). Solid as a rock.

One odd thing: I did notice the power supply high pitch frequency from the chokes was different. Maybe when the board is cycled hot it does a similar thing to what the old Singles did when they would power up more slowly. But letting it sit for a few mins seems to have restored it. Note it's been running for 6 hours now without a problem.

What are you seeing. Can you post the messages? Do they all do that, can you try shutting off the one that does for 15-20 mins? How does it hash?
C

posted this on bfl forum too, edited to today's findings;
"I'm getting errors on 1 of 2 monarchs, switched usb cables, ports, tried powered usb hub, un-powered, direct into pc. I noticed on powering the monarchs, one has a 1 red led going on/off/on/off etc. near the back usb, the other one with the errors has 2, one with the same on/off sequence, and one that blinks fast about 6 times, then goes off for a sec., then blinks fast again, etc.
errors are:
"sanity check, device is processing unknown work,
device is missing queued job. device flushed (goes by too fast)
failed to find work for queue results", then it hashes a couple of shares, and the same errors pop up again, and this repeats itself over and over, on the same monarch."

Later noticed they occur on bfl0 and bfl1, probably normal, I don't know if those messages in the command window are new for bfgminer 4.7.x and higher?

later

"Yeah, switching psu/usb/cables with the other one brings no difference, what does the fast blinking led next to the once-per-second flashing one on the error one mean? Even when it is only powered up and not hashing, it shows the same fast blinking of a second led. Doesn't look like I'm missing out on much hashrate though, it's running as it is specced, over 790-840GH for 2x 400GH rated units."

Actually a 400GH and a 425GH unit, and labelled so on the small fan's side. BFGminer reports couple of degrees above room temp, more shed temp, running about 22C. Odd thing is I found bfgminer shut down 2 times now. I'm kind of busy and don't have time to sit down with the miners and host and the bfgminer manuals to see what's to adapt, but I guess overclocking goes by fw like the sc's did?
And 5% and 4% hw errors btw, 0% and 0% rejected.

Just an FYI, the light below the blinking one (which indicates ASIC initialization when solid, hashing when blinking) is related to the FGPA. In the older code it was off, in the newer code it has the fast blink then off on a ~2 sec cycle. If the FPGA is erased, it lights dimly.

Have you seen the 4.2.0 custom build BFG on the BFL website? I know it doesn't seem anywhere near as prone to the sanity checks (unless you stop/start BFG without cycling power on the card) The FPGA buffers the work done and submits upon BFG restart and you get a mass of work not found. This buffer send seems to cause BFG to hiccup as I see an occasion 'failed to send queue' which goes away if I then cycle power on the card and restart BFG.