BitSyncom,

Can you share a word about invoicing and avalon name printed inside. It will be great if you share how you will process the other queue. I am curious how you will manage the shipment order. It will be based on Type of Payment, Order number, Date of payment received or what?

Thanks

+1
I am very happy with NGZ as well. But this time he will not be involved in shipping invoices and so on....
BitSyncom will take care of that and he is our contact person.

BitSyncom,

It is very important for me to sort out the invoicing in advance before shipment happens. I mailed you twice and opened a ticket and still no response. Please reply me when you can.

10X
Best

Thank you Kano!
I will find my way to hack around miner.php:)

Kano,
When mining with icarus + Stratum and diff> 1 following happens to stats

Utility is lowed by difficulty. What i mean is that when diff equals to one (getwork) utility shows 6.4. When Diff is equal to 8 (staratum) Utility shows 0.8. Same happens to HW erros i got about 16% of HW errors when mining with diff 8. Usually when i mine with get work they are about 2%.
I know that there is some kind of stats for shares below difficulty and proper calculations can be made. Can some sort of patch to be applied, so that cgminer counts U and HW errors  for every valid share like it was diff=1 (even share was below the target. And every share to be calculated with diff 1 when speaking of the stats) when mining with startum. Having this we will be able to see our stats like we used to when minig with diff=1 .
It is good to have because lancelot stats are messed up and all uf us are using U to measure the performance. Probably other FPGA folks can benefit from it also

As stated here in log term there will be almost zero variation in stats both ways

The problem is that we can apply some math and calculate proper U and HW errors but diff is not constant when using stratum. For instance i am mining 70% of the time with diff 8 but sometimes it drops to 4 and so on. Actually i do not know  how many shares at what diff i have submited to the pool so that i can hack miner.php to show stats like i like
What about it?

Or if you can provide some sorts of formula how to calculate utility (based on api stats) for all valid shares (Difficulty accepted and the ones below target + time since cgminer is up) will be great
10X

Dude,
If they can send them as demo units this mean no VAT:) But custom officers are very suspicious in my country so i personally prefer to pay 20% VAT on top just to be on a safe side.

About Invoicing...
The best option will be to name AVALON as "Computer Configuration" in the invoice

1. There are no additional taxes involved in my country when importing computers except VAT which can not be avoided
2. There will be no issues because it is crypto equipment named like "ordinary PC" and no additional customs check will be applied if it is double purpose or not. When speaking of Cryptography Import/Export rules, they are very strict in my country (and all over EU) and it may happen that some of the EU customers will not be able to get the unit at all from the customs
What about it BitSyncom?
Anyone to have something against naming our units as "Computer Configuration"? If we all agree on that it will be eraser for BitSyncom to handle invoices because all of them will be same for "Computer Configuration"?

Doc,
Was the ddos UDP? If it was UDP it is a big mess. Very hard to deal with. Good luck with finding new provider..We are waiting for you

Guy's,
I am complete newbie, so please excuse me in advance if this sounds stupid but…Is there any way to use PC RAM via USB at 115200 with FPGA and appropriate bitstream/miner combination?  As long RAM is the “bottle neck” for most FPGA boards now which are used for bitcoin mining. If yes MAX USB speed of some boards is  115200 only. Can this be a second bottle neck also? Probably yes but any comment is welcome
10X

Any update on avalon flash (will be good also 4/8/16 MB)/RAM(16/32/64/128) memory size (i guess there will be no HDD inside

The best will be flash > 4 and RAM >=64 personal opinion. With 8 Flash and 64 or 128 RAM we will be able to do whatever we like install php,web server, vpn or whatever comes handy
10X
PS: If i find a way to make proper cooling for asic unit and there is a hack (which will come with a time)  so that ASIC can be plugged in regular Linux PC i will take that route personally. But this option will not be available from day one though

+1
You memory is perfectly correct:)

I would like to have it with quick build instructions how to build it from cvs open-wrt

Marry Christmas Doc! Let the scala be with you
I wish to everybody lots health, luck and let the "luck" be with us 

Guy's,
Thank you very much! Have a nice holidays, merry Christmas and a happy new year!

If something else pops up i will let you know. gdb never lies:)

Best

Hi Kano,

Here is what happens

[New LWP 2833]
[New LWP 2832]
[New LWP 2831]

warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/bin/cgminer '.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000040be10 in __clone_available () at cgminer.c:3011
3011    cgminer.c: No such file or directory.
(gdb) bt
#0  0x000000000040be10 in __clone_available () at cgminer.c:3011
#1  0x000000000041e1b3 in main (argc=1, argv=0x7fffececa7b8) at cgminer.c:6859

(gdb) bt full
#0  0x000000000040be10 in __clone_available () at cgminer.c:3011
        work = 0x2424f70
        tmp = 0x40688f
        cloned = false
#1  0x000000000041e1b3 in main (argc=1, argv=0x7fffececa7b8) at cgminer.c:6859
        pool = 0x12b9290
        lagging = false
        ce = 0x1630e90
        ts = 1
        max_staged = 1
        cp = 0x12b9290
        work = 0x2420ed0
        pools_active = true
        handler = {__sigaction_handler = {sa_handler = 0x40b72a <sighandler>,
            sa_sigaction = 0x40b72a <sighandler>}, sa_mask = {__val = {
              0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x1}
        thr = 0x16325a8
        block = 0x12b7e30
        k = 31
        i = 1
        j = 1
        s = 0x12b7e10 "8332"

[57817.341874] cgminer[2450]: segfault at 260 ip 000000000040be10 sp 00007fffecec84c0 error 4 in cgminer[400000+57000]
[83170.561524] cgminer[32284]: segfault at 260 ip 000000000040be10 sp 00007fff6fb85250 error 4 in cgminer[400000+57000]
I hacked
static bool __clone_available(void)
{
        struct work *work, *tmp;
        bool cloned = false;

        mutex_lock(stgd_lock);
        if (!staged_rollable) {
                mutex_unlock(stgd_lock);
                goto out;
        }
        mutex_unlock(stgd_lock);
I do not know if it is OK but from what i can see there is race condition accessing staged_rollable or at least i think so
I will let you know if it crashesh again


You can see that bug happens at exact same location cgminer[400000+57000]  which makes me think that PC memory is OK.


I can send you core and cgminer binary if you need them.  Do you have any idea what might be wrong?

Thanks

PS this time we went little more further


[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/local/bin/cgminer.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000410ef4 in stage_work (work=0x326fc10) at cgminer.c:3584
3584            applog(LOG_DEBUG, "Pushing work from pool %d to hash queue", work->pool->pool_no);
(gdb) EBUG, "Pushing work from pool %d to hashEBUG, "Pushing work from pool %d to

Program terminated with signal 11, Segmentation fault.
#0  0x0000000000410ef4 in stage_work (work=0x326fc10) at cgminer.c:3584
3584            applog(LOG_DEBUG, "Pushing work from pool %d to hash queue", work->pool->pool_no);
(gdb) bt full
#0  0x0000000000410ef4 in stage_work (work=0x326fc10) at cgminer.c:3584
No locals.
#1  0x000000000040bebd in __clone_available () at cgminer.c:3021
        work_clone = 0x326fc10
        work = 0x32ad230
        tmp = 0x0
        cloned = false
#2  0x000000000041e1f3 in main (argc=1, argv=0x7fff030ba5c8) at cgminer.c:6869
        pool = 0x1f0a270
        lagging = false
        ce = 0x7fe030531120
        ts = 1
        max_staged = 1
        cp = 0x1f0a270
        work = 0x328f2e0
        pools_active = true
        handler = {__sigaction_handler = {sa_handler = 0x40b72a <sighandler>,
            sa_sigaction = 0x40b72a <sighandler>}, sa_mask = {__val = {
              0 <repeats 16 times>}}, sa_flags = 0, sa_restorer = 0x1}
        thr = 0x26fc698
        block = 0x1f08e10
        k = 31
        i = 1
        j = 1
        s = 0x1f08df0 "8332"
(gdb)
For me it seems that stage_work called from  __clone_available crashed
From the other hand

static void stage_work(struct work *work)
{
   applog(LOG_DEBUG, "Pushing work from pool %d to hash queue", work->pool->pool_no);
   work->work_block = work_block;

static unsigned int work_block; is a global and it has been never locked, so maybe a instance of test_work_current was trying to change it
work->work_block = ++work_block; and race conditions occurred?

I am not both c and threads expert, but as long as i know each global var shall be locked when changed. Maybe when read also but it depends on gcc os and whatever. Is that true? If yes we have a potential code that can cause core dumps because of it

I do not how to lock work->work_block = ++work_block; so i am running same version with staged_rollable locked and i do expect within a day or two same crash to appear
10X

Kano,

It might be memory. But my pc is running fine almost 5 mounts without a hang. If it is a memory i shall expect some random PC freezes also. Any way, as i told you i am not sure if core dump was generated from same version of cgminer. I am upgrading it frequently I shall wait for another crash and i will send the proper debug info

thank you very much!

Kano,
There might be version mismatch between core and executable
I will post correct info when it crashes again
I am not quite sure if that info is useful at all
Flowing your advise i got some gdb core info to share. cgminer 2.10.2 coredumps
[91932.126721] cgminer[2138]: segfault at 260 ip 000000000040be10 sp 00007fff4c6b48b0 error 4 in cgminer[400000+57000]

[New LWP 2680]
[New LWP 2731]
[New LWP 2618]

warning: Error reading shared library list entry at 0x780000003c

warning: Corrupted shared library list: 0x0 != 0x4830408b48d00148
Core was generated by `/usr/local/bin/cgminer xxxxxx.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000410ea1 in stage_thread (userdata=0x1c4a080) at cgminer.c:3576
3576    cgminer.c: No such file or directory.


line 3576   tq_freeze(mythr->q);


10X

Any recent kernel upgrade of the pool? If yes just go back to old one

You are talking about BFL Right?
They know their business and that is why i am sticking to them. However shit happens. But let us think positive. 

Dude (deathcode),
I wanna be the first one. Do not go before me pls
We are making jokes here, but there are a lot of people who are still spending money with BFL. That is complete misery at least for me..But the money are theirs anyway so they are free to do whatever they like

There will be batch 2 after they ship batch 1 as announced around 15th of January