sb0_ changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555_ has joined #m-labs
mauz555 has quit [Ping timeout: 245 seconds]
mauz555_ has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 245 seconds]
mauz555 has joined #m-labs
<_whitenotifier-6> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/fhtg7
<_whitenotifier-6> [m-labs/nmigen] whitequark d78e6c1 - hdl.mem: add DummyPort, for testing and verification.
<_whitenotifier-6> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/474004333?utm_source=github_status&utm_medium=notification
<_whitenotifier-6> [nmigen] Success. 81.45% (+0.08%) compared to ae3c583 - https://codecov.io/gh/m-labs/nmigen/commit/d78e6c155b6de72ab56f7cb123bc2b7cdb8f6b04
<_whitenotifier-6> [nmigen] Success. 100% of diff hit (target 81.36%) - https://codecov.io/gh/m-labs/nmigen/commit/d78e6c155b6de72ab56f7cb123bc2b7cdb8f6b04
<whitequark> rjo: ping
mauz555 has quit [Remote host closed the connection]
<key2> ping timeout
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
<_whitenotifier-6> [nmigen] whitequark opened issue #16: Support transparent ports with RE - https://git.io/fht2e
<_whitenotifier-6> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/fht2L
<_whitenotifier-6> [m-labs/nmigen] whitequark 031a9e2 - hdl.rec: use a helpful error on unknown field reference.
<_whitenotifier-6> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/474007256?utm_source=github_status&utm_medium=notification
<_whitenotifier-6> [nmigen] Success. 81.46% (+0.01%) compared to d78e6c1 - https://codecov.io/gh/m-labs/nmigen/commit/031a9e26160748bc426e6d2a0b687603e1345bff
<_whitenotifier-6> [nmigen] Success. 100% of diff hit (target 81.45%) - https://codecov.io/gh/m-labs/nmigen/commit/031a9e26160748bc426e6d2a0b687603e1345bff
<_whitenotifier-6> [m-labs/nmigen] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/fht2s
<_whitenotifier-6> [m-labs/nmigen] whitequark 3c07d8d - hdl.rec: include record name in error message.
<_whitenotifier-6> [nmigen] Success. The Travis CI build passed - https://travis-ci.org/m-labs/nmigen/builds/474007631?utm_source=github_status&utm_medium=notification
<_whitenotifier-6> [nmigen] Success. 81.48% (+0.01%) compared to 031a9e2 - https://codecov.io/gh/m-labs/nmigen/commit/3c07d8d52cef639dad501e86522db804796e0d6e
<_whitenotifier-6> [nmigen] Success. 100% of diff hit (target 81.46%) - https://codecov.io/gh/m-labs/nmigen/commit/3c07d8d52cef639dad501e86522db804796e0d6e
<_whitenotifier-6> [nmigen] The6P4C opened issue #17: Add a more user-friendly error message when the yosys binary can't be found - https://git.io/fht2R
<sb0> whitequark, rjo: OK to wipe the HDD on build.lab.m-labs.hk?
<whitequark> sb0: the old buildserver?
<sb0> whitequark: the new computer that was supposed to be used as a faster build machine, but which you never finished setting up
<whitequark> why do you want to wipe the HDD?
<whitequark> well, SSD
<whitequark> it doesn't have a HDD
<whitequark> you should at least back up /etc, because it has useful kernel and xen parameters
<whitequark> everything else is disposable i think
<sb0> whitequark: to use as an experimental nix build machine. if you have a better use for this computer then please do it. right now it's only collecting dust.
<whitequark> i'm pretty sure i configured it as a buildslave
<whitequark> if not, sure, i can do that
<whitequark> though you'll need to turn it on
<sb0> whitequark: can't we just replace the old machine completely?
<whitequark> sure
<sb0> iirc the buildslave didn't work
<whitequark> hm
<whitequark> i'm fairly sure i verified it, but if it didn't work, i can fix it
<whitequark> and/or migrate the old machine completely, yes
<whitequark> turn it on and ping me.
<sb0> there was just this artiq-quick builder, which was never finished, and CI didn't use it
<whitequark> oh, i remember that
<whitequark> but it's unrelated to the build machines
<whitequark> artiq-quick was not "quick" in the sense of fast
<whitequark> it is supposed to build people's pull requests when poked on IRC
<whitequark> i have provided instructions for this and iirc someone (hartytp?) used it
<whitequark> successfully, that is
<sb0> whitequark: it's on
<whitequark> ok, i'll take a look soon
<whitequark> do you have anything running on lab. that needs migrating?
<whitequark> oh. i remember now what was the problem with migrating the old machine.
<whitequark> the new one did not run xen, or rather, xen killed overclocking.
<whitequark> so i'll need to migrate the VMs to use kvm.
<whitequark> i think i started looking into kvm, but the tooling around it was kind of crap, so it never went anywhere.
<whitequark> but i can just run qemu -kvm instead of all the xml junk they added around
<sb0> whitequark: it's not stable with overclocking anyway
<sb0> I just disabled it
<sb0> running a few vivado instances concurrently systematically crashed the whole machine
<whitequark> sb0: why disable and not bump it down by 0.1 GHz?
<sb0> is there really a significant performance gain from this overclocking?
<sb0> and it conflicts with the VMs as you said
<whitequark> yes, actually, there is
<whitequark> i've spent a few days measuring it and it's nontrivial
<whitequark> iirc it was set up at 5 GHz when i put it in the lab
<whitequark> and 4.9 is about as far as it should go according to intel
<whitequark> so you only really need to knock it down one step
<whitequark> 5 GHz was stable in my experiments with one vivado process but i guess two pushed it enough
<whitequark> as for xen, there's no real difference between xen and kvm for our purposes. actually kvm might be slightly nicer.
<whitequark> it's mostly that i'm not used to libvirt but know xl
<whitequark> another problem with xen is that iirc it not only inhibits overclocking but it also inhibits turboboost
<whitequark> so if we put xen there it'll be even slower than it is right now
rohitksingh_work has joined #m-labs
<GitHub168> [smoltcp] jhwgh1968 commented on issue #266: I reviewed my code, and I think the case I was thinking of is already covered.... https://github.com/m-labs/smoltcp/pull/266#issuecomment-450711078
<GitHub43> [smoltcp] jhwgh1968 commented on issue #256: Since it didn't get linked to this issue, I have a phase 1 implementation in #266.... https://github.com/m-labs/smoltcp/issues/256#issuecomment-450711148
<GitHub43> [smoltcp] whitequark commented on pull request #266 2552d0b: This seems like a weird optimization, but since the RFC spells it out explicitly, I guess it's fine. https://github.com/m-labs/smoltcp/pull/266#discussion_r244628623
<GitHub31> [smoltcp] whitequark commented on issue #266: @m-labs-homu r+ https://github.com/m-labs/smoltcp/pull/266#issuecomment-450711180
<GitHub40> [smoltcp] m-labs-homu commented on issue #266: :pushpin: Commit 2552d0b has been approved by `whitequark`
<GitHub32> [smoltcp] whitequark commented on issue #266: @m-labs-homu r+ https://github.com/m-labs/smoltcp/pull/266#issuecomment-450711229
<GitHub67> [smoltcp] whitequark commented on issue #266: @m-labs-homu r+ https://github.com/m-labs/smoltcp/pull/266#issuecomment-450711180
<GitHub188> [smoltcp] m-labs-homu commented on issue #266: :bulb: This pull request was already approved, no need to approve it again. https://github.com/m-labs/smoltcp/pull/266#issuecomment-450711231
<GitHub182> [smoltcp] m-labs-homu commented on issue #266: :pushpin: Commit 2552d0b has been approved by `whitequark`
<GitHub139> [smoltcp] m-labs-homu pushed 1 new commit to auto: https://github.com/m-labs/smoltcp/commit/ed8dce015c45ee6e37c8d671f290a6d9b7fb49ac
<GitHub139> smoltcp/auto ed8dce0 jhwgh1968: Minimal Implementation of TCP Selective Acknowledgement...
<GitHub29> [smoltcp] m-labs-homu commented on issue #266: :hourglass: Testing commit 2552d0b414dc88d23db32150f02d84b807fdbe85 with merge ed8dce015c45ee6e37c8d671f290a6d9b7fb49ac... https://github.com/m-labs/smoltcp/pull/266#issuecomment-450711239
<travis-ci> m-labs/smoltcp#1191 (auto - ed8dce0 : jhwgh1968): The build passed.
<GitHub2> [smoltcp] m-labs-homu merged auto into master: https://github.com/m-labs/smoltcp/compare/556672f79811...ed8dce015c45
<GitHub140> [smoltcp] m-labs-homu commented on issue #266: :sunny: Test successful - [status-travis](https://travis-ci.org/m-labs/smoltcp/builds/474022451?utm_source=github_status&utm_medium=notification)
<GitHub131> [smoltcp] m-labs-homu closed pull request #266: Minimal Implementation of TCP Selective Acknowledgement (master...selective-ack-phase-1) https://github.com/m-labs/smoltcp/pull/266
_whitelogger has joined #m-labs
_whitelogger_ has joined #m-labs
_whitelogger_ has joined #m-labs
_whitelogger__ has joined #m-labs
_whitelogger__ has joined #m-labs
_whitelogger__ has joined #m-labs
_whitelogger___ has joined #m-labs
_whitelogger___ has joined #m-labs
_whitelogger___ has joined #m-labs
_whitelogger___ has joined #m-labs
_whitelogger____ has joined #m-labs
_whitelogger____ has joined #m-labs
_whitelogger____ has joined #m-labs
_whitelogger____ has joined #m-labs
_whitelogger____ has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh_work has quit [Read error: Connection reset by peer]
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has quit [Ping timeout: 250 seconds]
<GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/421ad9c9168e...48793b7ecf70
<GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/421ad9c9168e...48793b7ecf70
<GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/421ad9c9168e...48793b7ecf70
<GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/421ad9c9168e...48793b7ecf70
<GitHub-m-labs> [artiq] sbourdeauducq pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/421ad9c9168e...48793b7ecf70
<GitHub-m-labs> artiq/master 1e7ba32 Sebastien Bourdeauducq: nix: add development environment
<GitHub-m-labs> artiq/master 1e7ba32 Sebastien Bourdeauducq: nix: add development environment
<GitHub-m-labs> artiq/master 1e7ba32 Sebastien Bourdeauducq: nix: add development environment
<GitHub-m-labs> artiq/master e279980 Sebastien Bourdeauducq: nix: do not install development packages in user environment
<GitHub-m-labs> artiq/master 48793b7 Sebastien Bourdeauducq: nix: reorganize .nix files
<GitHub-m-labs> artiq/master e279980 Sebastien Bourdeauducq: nix: do not install development packages in user environment
<GitHub-m-labs> artiq/master 48793b7 Sebastien Bourdeauducq: nix: reorganize .nix files
<GitHub-m-labs> artiq/master 48793b7 Sebastien Bourdeauducq: nix: reorganize .nix files
<GitHub-m-labs> artiq/master 1e7ba32 Sebastien Bourdeauducq: nix: add development environment
<GitHub-m-labs> artiq/master e279980 Sebastien Bourdeauducq: nix: do not install development packages in user environment
<GitHub-m-labs> artiq/master e279980 Sebastien Bourdeauducq: nix: do not install development packages in user environment
<GitHub-m-labs> artiq/master 48793b7 Sebastien Bourdeauducq: nix: reorganize .nix files
<GitHub-m-labs> artiq/master 1e7ba32 Sebastien Bourdeauducq: nix: add development environment
<GitHub-m-labs> artiq/master 48793b7 Sebastien Bourdeauducq: nix: reorganize .nix files
<GitHub-m-labs> artiq/master e279980 Sebastien Bourdeauducq: nix: do not install development packages in user environment
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Okay, now it won't boot anymore, ``panic at src/libcore/result.rs:945:5cannot load RTM FPGA gateware: "Did not assert INIT in reaction to PROGRAM"``... https://github.com/m-labs/artiq/issues/1166#issuecomment-450739915
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Okay, now it won't boot anymore, ``panic at src/libcore/result.rs:945:5cannot load RTM FPGA gateware: "Did not assert INIT in reaction to PROGRAM"``... https://github.com/m-labs/artiq/issues/1166#issuecomment-450739915
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Okay, now it won't boot anymore, ``panic at src/libcore/result.rs:945:5cannot load RTM FPGA gateware: "Did not assert INIT in reaction to PROGRAM"``... https://github.com/m-labs/artiq/issues/1166#issuecomment-450739915
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Okay, now it won't boot anymore, ``panic at src/libcore/result.rs:945:5cannot load RTM FPGA gateware: "Did not assert INIT in reaction to PROGRAM"``... https://github.com/m-labs/artiq/issues/1166#issuecomment-450739915
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Okay, now it won't boot anymore, ``panic at src/libcore/result.rs:945:5cannot load RTM FPGA gateware: "Did not assert INIT in reaction to PROGRAM"``... https://github.com/m-labs/artiq/issues/1166#issuecomment-450739915
<bb-m-labs> build #2165 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2165
<bb-m-labs> build #2165 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2165
<bb-m-labs> build #2165 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2165
<bb-m-labs> build #2165 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2165
<bb-m-labs> build #2165 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2165
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Taking the RTM out of the crate and putting it back in again "fixed" the problem. You gotta love Sayma...... https://github.com/m-labs/artiq/issues/1166#issuecomment-450741155
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Taking the RTM out of the crate and putting it back in again "fixed" the problem. You gotta love Sayma...... https://github.com/m-labs/artiq/issues/1166#issuecomment-450741155
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Taking the RTM out of the crate and putting it back in again "fixed" the problem. You gotta love Sayma...... https://github.com/m-labs/artiq/issues/1166#issuecomment-450741155
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Taking the RTM out of the crate and putting it back in again "fixed" the problem. You gotta love Sayma...... https://github.com/m-labs/artiq/issues/1166#issuecomment-450741155
<GitHub-m-labs> [artiq] sbourdeauducq commented on issue #1166: Taking the RTM out of the crate and putting it back in again "fixed" the problem. You gotta love Sayma...... https://github.com/m-labs/artiq/issues/1166#issuecomment-450741155
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has quit [Ping timeout: 246 seconds]
rohitksingh has quit [Ping timeout: 246 seconds]
<bb-m-labs> build #2166 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2166
<bb-m-labs> build #2166 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2166
<bb-m-labs> build #2166 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2166
<bb-m-labs> build #2166 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2166
<bb-m-labs> build #2166 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2166
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
rohitksingh has joined #m-labs
<bb-m-labs> build #976 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/976
<bb-m-labs> build #976 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/976
<bb-m-labs> build #976 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/976
<bb-m-labs> build #976 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/976
<bb-m-labs> build #976 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/976
<bb-m-labs> build #2776 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2776
<bb-m-labs> build #2776 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2776
<bb-m-labs> build #2776 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2776
<bb-m-labs> build #2776 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2776
<bb-m-labs> build #2776 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2776
kuldeep has joined #m-labs
kuldeep has joined #m-labs
kuldeep has joined #m-labs
kuldeep has joined #m-labs
kuldeep has joined #m-labs
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] jordens commented on issue #1166: Cleaning this up and categorizing the historic and current issues observed/fixed, we have the following:... https://github.com/m-labs/artiq/issues/1166#issuecomment-450743254
<GitHub-m-labs> [artiq] hartytp commented on issue #1166: Thanks for looking into this @sbourdeauducq and @jordens. Glad to hear you can reproduce the issue. If there are any specific tests you'd like me to do then let me know. https://github.com/m-labs/artiq/issues/1166#issuecomment-450746661
<GitHub-m-labs> [artiq] hartytp commented on issue #1166: Thanks for looking into this @sbourdeauducq and @jordens. Glad to hear you can reproduce the issue. If there are any specific tests you'd like me to do then let me know. https://github.com/m-labs/artiq/issues/1166#issuecomment-450746661
<GitHub-m-labs> [artiq] hartytp commented on issue #1166: Thanks for looking into this @sbourdeauducq and @jordens. Glad to hear you can reproduce the issue. If there are any specific tests you'd like me to do then let me know. https://github.com/m-labs/artiq/issues/1166#issuecomment-450746661
<GitHub-m-labs> [artiq] hartytp commented on issue #1166: Thanks for looking into this @sbourdeauducq and @jordens. Glad to hear you can reproduce the issue. If there are any specific tests you'd like me to do then let me know. https://github.com/m-labs/artiq/issues/1166#issuecomment-450746661
<GitHub-m-labs> [artiq] hartytp commented on issue #1166: Thanks for looking into this @sbourdeauducq and @jordens. Glad to hear you can reproduce the issue. If there are any specific tests you'd like me to do then let me know. https://github.com/m-labs/artiq/issues/1166#issuecomment-450746661
kuldeep has quit [Read error: Connection reset by peer]
kuldeep has quit [Read error: Connection reset by peer]
kuldeep has quit [Read error: Connection reset by peer]
kuldeep has quit [Read error: Connection reset by peer]
kuldeep has quit [Read error: Connection reset by peer]
rohitksingh has quit [Remote host closed the connection]
rohitksingh has quit [Remote host closed the connection]
rohitksingh has quit [Remote host closed the connection]
rohitksingh has quit [Remote host closed the connection]
rohitksingh has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has quit [Ping timeout: 272 seconds]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has quit [Remote host closed the connection]
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has joined #m-labs
mauz555 has quit [Ping timeout: 244 seconds]
mauz555 has quit [Ping timeout: 244 seconds]
mauz555 has quit [Ping timeout: 244 seconds]
mauz555 has quit [Ping timeout: 244 seconds]
mauz555 has quit [Ping timeout: 244 seconds]