2011-08-22 02:50 <kristianpaul> wpwrak: what was the file you pusblished somwhere.. to update usb id list to qi-hardware related products?
2011-08-22 02:50 <kristianpaul> so lsusb is not just the ID and no description..
2011-08-22 02:53 <wpwrak> ah, lemme see ..
2011-08-22 02:55 <wpwrak> http://lists.en.qi-hardware.com/pipermail/discussion/2011-February/007210.html
2011-08-22 02:56 <kristianpaul> That one!, thanks
2011-08-22 04:11 <rjeffries> rejon how long will you stay in China?
2011-08-22 05:26 <qi-bot> The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-08212011-1734/
2011-08-22 06:32 <qi-bot> [commit] Xiangfu Liu: work around on python (master) http://qi-hw.com/p/openwrt-packages/0df4b6d
2011-08-22 06:42 <qi-bot> [commit] Xiangfu Liu: nanonote speedup powerup, thanks Bas (master) http://qi-hw.com/p/openwrt-packages/0ffd3d0
2011-08-22 07:13 <qi-bot> [commit] Xiangfu Liu: gmenu2x wallpaper only support .png (master) http://qi-hw.com/p/gmenu2x/46d6809
2011-08-22 07:24 <qi-bot> [commit] Xiangfu Liu: gmenu2x update (master) http://qi-hw.com/p/openwrt-packages/c609bba
2011-08-22 07:24 <qi-bot> [commit] Xiangfu Liu: 4th update to 2.61.2 (master) http://qi-hw.com/p/openwrt-packages/c4d594a
2011-08-22 08:20 <qi-bot> [commit] Xiangfu Liu: ben nanonote: forward patches to linux-3.1 (next) http://qi-hw.com/p/openwrt-xburst/2d22f1f
2011-08-22 08:52 <qi-bot> [commit] Xiangfu Liu: nanonote mtd.nn: disable kernel log when normal boot (master) http://qi-hw.com/p/openwrt-packages/d95cfe1
2011-08-22 09:35 <kyak> xiangfu: since you're modifying cmdline, how about adding "consoleblank=30"?
2011-08-22 09:36 <kyak> by default, it is 600 (i.e. 10 minutes)
2011-08-22 09:37 <xiangfu> kyak, yes. sure why not ;-)
2011-08-22 09:38 <qi-bot> [commit] Xiangfu Liu: change the console blank to 30 seconds, thanks kyak (master) http://qi-hw.com/p/openwrt-packages/70ce35e
2011-08-22 09:39 <xiangfu> kyak, ^ :) don't know this option before. thanks.
2011-08-22 09:40 <xiangfu> kyak, I use the workaround for now. hope I can get a new image recently two days.  
2011-08-22 09:41 <xiangfu> kyak, I pushed one branch 'next' which I already rebase on last openwrt svn trunk.
2011-08-22 09:42 <xiangfu> also I have committed my small work on linux 3.1 , just a start. we will jump to this recently , just after this release .
2011-08-22 09:58 <kyak> sounds great :)
2011-08-22 09:58 <kyak> and the changes i wanted are all inside
2011-08-22 09:59 <kyak> the problem is however, that ffmpeg is updated upstream and now some packages (like mocp) fail to build
2011-08-22 09:59 <kyak> https://dev.openwrt.org/changeset/28063
2011-08-22 09:59 <kyak> this is the changeset that causes trouble
2011-08-22 10:00 <kyak> perhaps we can override and revert it for this build
2011-08-22 10:00 <kyak> and then see how it goes on openwrt side
2011-08-22 10:01 <kyak> jow said he was going to talk to the committer :)
2011-08-22 10:53 <xiangfu> kyak, (mocp failed) yes. notice that so I have modify the feeds.conf to @28054 :)  http://fidelio.qi-hardware.com/~xiangfu/openwrt-xburst.full_system/feeds.conf  stop update upstream packages, :)
2011-08-22 10:53 <xiangfu> kyak, (jow said he was going to talk to the committer ) great.
2011-08-22 11:13 <wpwrak> kristianpaul: just catching up with some really old stuff ...  216.239.32.2: i can ping it but not connect to port 80. neither from home nor via a server in the US.
2011-08-22 11:16 <kristianpaul> he, okay :)
2011-08-22 11:17 <kristianpaul> i need to remenber was was the porpuse of my question, but first finish breadfast ;)
2011-08-22 11:18 <wpwrak> kristianpaul: and the .2 doesn't work because it's .21. can reach .21 without problems from home :)
2011-08-22 11:21 <kristianpaul> he ;)
2011-08-22 11:29 <qi-bot> [commit] Xiangfu Liu: nanonote: add 4th entry (master) http://qi-hw.com/p/gmenu2x/9dc513f
2011-08-22 11:30 <`antonio`> wpwrak, here's the video http://www.vimeo.com/27924004
2011-08-22 11:30 <qi-bot> [commit] Xiangfu Liu: gmenu2x update (master) http://qi-hw.com/p/openwrt-packages/58392ee
2011-08-22 11:31 <`antonio`> :) and here's the wiki if you want to know about the project http://theclashingrocks.org/wiki/doku.php?id=tcr
2011-08-22 11:31 <wpwrak> `antonio`: (video) ah yes, zedstar mentioned it. very nice ! i can't quite figure out what it shows, but it looks (and sounds) cool ;-)
2011-08-22 11:31 <wpwrak> `antonio`: btw, did you solve the duplicate ping response problem ?
2011-08-22 11:34 <`antonio`> i minimized it but didn't completely solve it yet 
2011-08-22 11:37 <wpwrak> `antonio`: what did you do ti minimize it ?
2011-08-22 11:37 <wpwrak> s/ti/to/
2011-08-22 11:41 <`antonio`> well changed the T_REASS_MS and T_ACK_MS on dirtpan.c and instead of having a real mesh i just connected each device to the coordinator
2011-08-22 11:41 <wpwrak> what does "real mesh" mean in this context ?
2011-08-22 11:41 <`antonio`> i'll work on it again this week and let you know how that goes
2011-08-22 11:42 <`antonio`> instead of having all devices connected to each other, i connect each device only to the coordinator 
2011-08-22 11:43 <wpwrak> hmm. strange. shouldn't make a difference if there's a connection to an IP you don't use.
2011-08-22 11:44 <`antonio`> I know, I will make some more experiments and let you know 
2011-08-22 11:44 <wpwrak> kewl :) thanks !
2011-08-22 11:45 <`antonio`> :)
2011-08-22 11:55 <qi-bot> [commit] Xiangfu Liu: nanonote: add python lua guile icons (master) http://qi-hw.com/p/gmenu2x/41e5f31
2011-08-22 11:56 <qi-bot> [commit] Xiangfu Liu: gmenu2x update (master) http://qi-hw.com/p/openwrt-packages/6baf30d
2011-08-22 13:31 <wpwrak> DocScrutinizer: by the way, if you like puzzles, here's a nice one (from milkymist rc3): http://downloads.qi-hardware.com/people/adam/m1/pic/rc3_0x77_ch1-TP36_ch2-NOR-pin34-DQ8_500ns.JPG.JPG
2011-08-22 13:35 <wpwrak> DocScrutinizer: CH1 shows a line that's normally pulled high with 10 kOhm and bypassed with 220 pF to ground. could be pulled low by an open collector, but we have reason to believe this isn't happening in this case.
2011-08-22 13:35 <wpwrak> DocScrutinizer: CH2 shows a quite unrelated line driven by a push-pull output. one thing they have in common is that they're on adjacent balls of the FPGA.
2011-08-22 13:37 <wpwrak> DocScrutinizer: when measuring the resistance between the two, we get about 10 kOhm in one direction, about 120 kOhm in the other. the 10 kOhm seems low and if i model this, i get roughly the right curve with similar values: http://downloads.qi-hardware.com/people/werner/m1/tmp/pin34.ps
2011-08-22 13:40 <wpwrak> DocScrutinizer: however, what kind of failure would really explain this ? (this is something we've only observed on two out of ~80 boards so far, and the other one may have a higher resistance between the two signals)
2011-08-22 13:48 <DocScrutinizer> sounds odd
2011-08-22 13:48 <wpwrak> DocScrutinizer: to say the least ;-)
2011-08-22 13:48 <DocScrutinizer> you considered clamping diodes when you did your measuring?
2011-08-22 13:49 <wpwrak> i thought of them but can't quite picture a credible failure scenario that involves them. they could explain any sneak current when measuring in-circuit and with power off, though.
2011-08-22 13:50 <DocScrutinizer> yes, sure they do, and it comes out as 10k on one meter, and as 307k on another, and yet another may tell it's 600R
2011-08-22 13:51 <wpwrak> ;-)
2011-08-22 13:51 <wpwrak> but then, when the system is powered, they shouldn't get in the way
2011-08-22 13:52 <DocScrutinizer> never probe outputs (or inputs) for resistance against ground or against another pin without proper voltage on clamping diodes
2011-08-22 13:52 <DocScrutinizer> yes
2011-08-22 13:52 <DocScrutinizer> exactly
2011-08-22 13:52 <wpwrak> i wonder if a diode test would yield more useful results. kinda tricky, though. some meters go up to relatively high voltages and i'm not sure adam has a good one.
2011-08-22 13:53 <wpwrak> if the system is powered, we can't really measure much resistance anyway. so it's an attempt to make do with what little we have
2011-08-22 13:53 <DocScrutinizer> unless your probing voltage is of wrong polarity (ground clamp diode kicks in, 0V7) or of higher voltage than VDD (VDD clamp diode kicks in, result random)
2011-08-22 13:54 <DocScrutinizer> another way to probe such things is with really good meter that has probing voltage <0.3V
2011-08-22 13:54 <DocScrutinizer> no non-linear component should spoil your results then - usually
2011-08-22 13:55 <DocScrutinizer> yet another way to probe is comparative probing between known good and DUT
2011-08-22 13:56 <DocScrutinizer> needs some experience to read the results of all those probings
2011-08-22 13:58 <DocScrutinizer> basically on a device without VDD applied, each pin is connected to each other pin via 2 diodes in series, no matter which is + and which -
2011-08-22 13:59 <DocScrutinizer> at least initially, until your meter has charged the PSU buffer capacitors ;-P
2011-08-22 13:59 <wpwrak> yeah ;-)
2011-08-22 13:59 <wpwrak> on DUTs, we got about 60/120 kOhm, compared to the 10/120 kOhm on the suspicious device
2011-08-22 13:59 <wpwrak> s/DUTs/good DUTs/
2011-08-22 13:59 <DocScrutinizer> I think we called this reverse alien powering a circuit
2011-08-22 14:00 <wpwrak> ;-))
2011-08-22 14:01 <DocScrutinizer> well, 60/120 vs 10/120 sounds like chip defect
2011-08-22 14:02 <wpwrak> interesting .. my fluke 8845A goes up to 10 V when measuring resistance (10 MOhm). the picotest m3500a goes up to 5 V. my handheld UT60G -230 mV
2011-08-22 14:02 <DocScrutinizer> or a short to some other pin you haven't considered
2011-08-22 14:03 <DocScrutinizer> yeah voltage on R test, a way underrated specifications detail of meters
2011-08-22 14:04 <wpwrak> there are no other paths that really seem to make sense. already this one (the adjacent but otherwise unrelated balls) was a lucky guess
2011-08-22 14:04 <DocScrutinizer> worst I've seen was some 40V, though on a electron valve heathkit device built for probing up to 100GR
2011-08-22 14:04 <DocScrutinizer> or 10GR, can't recall
2011-08-22 14:05 <DocScrutinizer> wpwrak: a soldering short rarely acts as diode
2011-08-22 14:05 <wpwrak> wow, 40 V not bad. 10 GOhm is even better, though :)
2011-08-22 14:06 <DocScrutinizer> so your reading had to be 10/10 rather than 10/120
2011-08-22 14:06 <wpwrak> yes, accidental creation of a PN barrier somehow seems improbable :)
2011-08-22 14:06 <DocScrutinizer> possible but unlikely, yes
2011-08-22 14:06 <DocScrutinizer> esp on TWO devices
2011-08-22 14:07 <DocScrutinizer> that's when I came up with silicon defect
2011-08-22 14:07 <wpwrak> of course, if we can do that just out of thin air, perhaps we should try our luck with cold fusion next ;-)
2011-08-22 14:08 <wpwrak> the boards had some light rework (addition of a 0402 component, replacement of another 0402 component, some wires) in the vicinity of those pads, including on traces leading to them
2011-08-22 14:08 <DocScrutinizer> OTOH on-chip defects that create shorts to a random PN structure nearby aren't uncommon
2011-08-22 14:08 <DocScrutinizer> often triggered by ESD
2011-08-22 14:09 <wpwrak> if a defect was caused by this rework, what are our chances to see anything useful on x-ray ? likewise, in case of ESD ?
2011-08-22 14:09 <DocScrutinizer> zero
2011-08-22 14:09 <wpwrak> sigh
2011-08-22 14:09 <DocScrutinizer> I'd guess
2011-08-22 14:09 <DocScrutinizer> I'd not bet a penny on it
2011-08-22 14:10 <wpwrak> on xray or on xray being useless ?
2011-08-22 14:10 <DocScrutinizer> you don't see silicon defects of that class in usual optical examination
2011-08-22 14:10 <DocScrutinizer> before sth shows up in xray even microscopy you need a severe burnout in the die
2011-08-22 14:11 <wolfspraul> the xray is an smt xray, not a foundry xray :-)
2011-08-22 14:11 <wpwrak> i was wondering is there could perhaps be a zone that looks abnormal, like lighter/darker than the rest or such
2011-08-22 14:11 <DocScrutinizer> a electromigration-alike defect is usually invisible unless you use electron microscopy I think
2011-08-22 14:11 <wpwrak> hmm
2011-08-22 14:12 <wpwrak> maybe we should just fire a few neutrinos at it and check how they get deflected :)
2011-08-22 14:12 <DocScrutinizer> let me put it this way: do your se the structures of a single transistor/diode on your xray? then you got chances to see the defect as well
2011-08-22 14:12 <wpwrak> anyone got the number of CERN ? it's about time they do something useful with their LHC :)
2011-08-22 14:13 <DocScrutinizer> hehe
2011-08-22 14:13 <wpwrak> (see transistors) i wouldn't count on that ;-) probably a few orders of magnitude too low-res
2011-08-22 14:13 <DocScrutinizer> yes, that's what I meant
2011-08-22 14:14 <wpwrak> are there other symptoms we could probe for that could reveal this sort of damage ? besides the "resistance"
2011-08-22 14:15 <DocScrutinizer> 1st approach: unsolder the chip and then probe again, without adjacent circuitry
2011-08-22 14:15 <wolfspraul> ma-tek could do it, but no way we will go in that direction http://www.ma-tek.com/
2011-08-22 14:16 <wpwrak> phew. that a ~450 balls FPGA.
2011-08-22 14:16 <wolfspraul> just replace the chip, and/or write off the board
2011-08-22 14:16 <DocScrutinizer> :shrug:
2011-08-22 14:17 <DocScrutinizer> anyway rework next to those pins smells like ESD damage
2011-08-22 14:17 <DocScrutinizer> symptoms are matching
2011-08-22 14:17 <DocScrutinizer> I've seen similar symptoms before
2011-08-22 14:18 <wpwrak> wolfspraul: let's see if we get the same on the other board. what troubles me is that 0x3c didn't show anything suspicious on the resistance test. 
2011-08-22 14:19 <wpwrak> wolfspraul: if he have this sort of failures, we need at least a way to detect them. even if it means the boards in question can't be salvaged.
2011-08-22 14:19 <wpwrak> s/he/we/
2011-08-22 14:20 <wolfspraul> I think Adam can smell them from 10m distance now.
2011-08-22 14:21 <wolfspraul> normally the decisions are made much faster and more radical, just replace/discard, all the way to happiness :-)
2011-08-22 14:21 <wpwrak> DocScrutinizer: yes, it all points in that direction. there are a few more things on those nets, but i can't really come up with a good theory how they would cause such effects. not without some very long failure chains. of course, if you assume triple- or quadruple failures even at different points, then anything is possible ;-)
2011-08-22 14:21 <wolfspraul> but of course it's good that we study a bit, a little knowledge never hurts. And Adam can learn a lot too I think.
2011-08-22 14:22 <wolfspraul> unless I feel there is something to be learnt for other boards, I feel pretty confident even I know how to 'fix' those boards :-) just throw away and replace with another one :-)
2011-08-22 14:22 <wpwrak> wolfspraul: naw, he can't smell these yet. he does occasionally see the boards go crazy, but even that comes and goes. maybe he catches all the afternoon boards but the morning boards are a bit colder and some escape. it's really weird.
2011-08-22 14:23 <wpwrak> wolfspraul: yes, if it's a defect in the chip, your fix is the only thing that's even remotely reliable ;-)
2011-08-22 14:24 <wolfspraul> I feel we've learnt 98% of what we can learn.
2011-08-22 14:25 <wolfspraul> I wouldn't want to take the chips to ma-tek, pay 20,000 USD, and finally have the final ultimate proof that it's an ESD damage because Adam touched the board in a certain way during some rework.
2011-08-22 14:25 <wolfspraul> that would be horrible waste
2011-08-22 14:25 <DocScrutinizer> I managed to "repair" such chips with a second OV treatment
2011-08-22 14:25 <wpwrak> wolfspraul: on 0x77, it seems we're pretty much exhausted our possibilities, yes
2011-08-22 14:25 <DocScrutinizer> ;-D
2011-08-22 14:26 <wpwrak> wolfspraul: 0x3c still bothers me, though. maybe it's TP36 plus something else than pin 34.
2011-08-22 14:26 <wolfspraul> let's see how the fix2b goes on other boards now
2011-08-22 14:27 <wolfspraul> I thought we had mostly exhausted what we can learn on 32/3c/77 etc. so far I haven't been proven wrong.
2011-08-22 14:27 <DocScrutinizer> I figured what component structure on the die might have been damaged initialy and with wild handwaving came up with a burn out the bug procedure that fused away another component thus "fixing" the short
2011-08-22 14:27 <wolfspraul> of course if there would be something it would be very significant, so it's good to have a little paranoia
2011-08-22 14:27 <DocScrutinizer> amazingly it actually worked on one of the three chips
2011-08-22 14:28 <DocScrutinizer> those were pretty simple chips though, where you actually could get even structure photos
2011-08-22 14:28 <DocScrutinizer> in the very early days of integrated circuits
2011-08-22 14:28 <wpwrak> wolfspraul: what i'm looking for is a non-statistical test for a defect there. so far, TP36-pin34 marks 0x77 as a clear outlier. but 0x3c proves that it doesn't show all the outliers. but if we could have a reasonably small set of pins to probe, that would help to catch damaged boards before they fail in the field.
2011-08-22 14:28 <DocScrutinizer> on sth like SN74xx series components
2011-08-22 14:29 <wpwrak> wolfspraul: also, the other NOR problems we've observed could be linked to this
2011-08-22 14:29 <wolfspraul> I don't think any of the boards made it very far
2011-08-22 14:29 <wolfspraul> I will look at that again, but not so worried
2011-08-22 14:29 <wolfspraul> we can also make the test a little stronger and catch them that way :-)
2011-08-22 14:29 <wolfspraul> it seems to fail quite early
2011-08-22 14:30 <DocScrutinizer> are you using JTAG boundary scan?
2011-08-22 14:30 <wpwrak> DocScrutinizer: the day wolfgang comes across some money, he'll hire you as the magic ESD healer for the fab ;-)
2011-08-22 14:30 <DocScrutinizer> lol, no thanks
2011-08-22 14:31 <wolfspraul> what drove me crazy before fix2b was boards failing on render cycle 2, 5, 9 etc. that meant even if we would have increase the render cycles to 20, 50, etc. we would have ignored something major (and driven up the fail rate sky high in the process)
2011-08-22 14:31 <wolfspraul> this is all far far better now, all under control
2011-08-22 14:32 <wpwrak> wolfspraul: yes, failures that late would be very bad
2011-08-22 14:32 <wolfspraul> I think tomorrow Adam should really move 80% or more of his time to fix2b and getting 30 full units ready for sales
2011-08-22 14:32 <DocScrutinizer> are you using JTAG boundary scan?
2011-08-22 14:32 <wolfspraul> after that day the time pressure goes away too
2011-08-22 14:32 <wpwrak> DocScrutinizer: (boundary scan) i don't think there's any test of that sort
2011-08-22 14:33 <DocScrutinizer> running "normal" programs and deciding go/no-go isn'T a proper QA
2011-08-22 14:34 <wpwrak> (atben/atusb production test has sort of a boundary scan ;-)
2011-08-22 14:35 <DocScrutinizer> proper QA consists of putting DUT into pathological operation modes to see how it reacts. The results of these operation modes are not like works/doesn't-work but more like "this error pattern is expected, so the board is ok" vs "duh it refuses to fail, so it might be defect"
2011-08-22 14:35 <wpwrak> (not that it actually caught anything - all three defects where outside the scope of these tests. but the tests are there, in all their cryptic beauty :)
2011-08-22 14:38 <wpwrak> wolfspraul: let's get the 0x3c signals and measure resistance on a few more pins on it then. that shouldn't take long. then adam can finish the fix2b and testing, and then we'll also see if more boards to decide to join the cluster.
2011-08-22 14:38 <DocScrutinizer> e.g you reduce VDD to a level where you expect a certain error to occur. If you got flaky output loads the error pattern will be different
2011-08-22 14:38 <wpwrak> DocScrutinizer: hmm, that seems tricky. lots and lots of undocumented behaviour.
2011-08-22 14:39 <DocScrutinizer> indeed it's undocumented, but you always do your own documentation on a known-good device anyway
2011-08-22 14:40 <DocScrutinizer> lots of QA are mere comparative tests between DUT and reference device
2011-08-22 14:40 <wolfspraul> agreed, some 3c pins and that's it
2011-08-22 14:40 <wpwrak> DocScrutinizer: what i do is pull up/down all pins, then set one to the opposite level. see if all the rest still reads as set. etc.
2011-08-22 14:40 <wolfspraul> DocScrutinizer: yes :-) comparative testing, lots and fast
2011-08-22 14:40 <DocScrutinizer> yup, when you also precisely log the VDD current etc then that's a good way
2011-08-22 14:41 <wolfspraul> and then even a dumb guy like me can make a thumb up/down decision :-)
2011-08-22 14:41 <wpwrak> DocScrutinizer: i skipped current this time (atben/atusb). too hard to pull it off (would have had to make a test rig, etc.)
2011-08-22 14:42 <DocScrutinizer> good way to follow and do more alike that
2011-08-22 14:42 <DocScrutinizer> yes, without a test rig you can not do decent QA
2011-08-22 14:42 <wolfspraul> calling it a day, n8
2011-08-22 14:42 <DocScrutinizer> that's the whole purpose of all those test pads after all
2011-08-22 14:42 <wpwrak> DocScrutinizer: (current test) of course, with my lab it would have been easy. maybe a simple passive board, but that would have been all. alas, tuxbrain wouldn't have had the instruments to make use of this ...
2011-08-22 14:43 <DocScrutinizer> night wolfspraul 
2011-08-22 14:43 <wpwrak> wolfspraul: untroubled dreams ! :)
2011-08-22 14:47 <wpwrak> hmm, i think i'll see if i can find some food. government sneaked in some public holiday today. the things that happen in election years under a government that sees blatant populism as its strongest card :-(
2011-08-22 14:48 <wpwrak> well, if all else fails, i can still live on crackers and cheese for a week or so ...
2011-08-22 14:52 <wpwrak> DocScrutinizer: thanks for your help ! so, no urgent xray session for adam :)
2011-08-22 14:54 <DocScrutinizer> yw
2011-08-22 14:55 <DocScrutinizer> time for 12648430    
2011-08-22 14:55 <DocScrutinizer> http://www.thehackernews.com/2011/08/nokia-website-hacked-by-pr0tect0r-aka.html
2011-08-22 14:58 <wpwrak> DocScrutinizer: have you been a bad boy ? ;-)
2011-08-22 14:58 <DocScrutinizer> nah
2011-08-22 15:21 <urandom__> why did he hack nokia? for fun?
2011-08-22 15:30 <wpwrak> urandom__: maybe to show solidarity with elop ? :)
2011-08-22 15:49 <urandom__> wpwrak well he doesn't write anything about solidarity in his message
2011-08-22 15:51 <larsc> probably he was just bored
2011-08-22 15:58 <urandom__> if he is bored he should do something productive and not hack other peoples websites just to show off how cool he is
2011-08-22 16:05 <DocScrutinizer> I appreciate he kicked develper.nokia.com webmins' butts, as that website had several issues with authentication etc before he came
2011-08-22 16:06 <DocScrutinizer> e.g it dropped a session-end cookie that made subsequent logins always fail
2011-08-22 16:09 <DocScrutinizer> doesn't show up if you use firefox with standard configuration for cookie management :-P
2011-08-22 16:11 <DocScrutinizer> for those users prefering a different browser and/or more sophisticated cookie management, it failed boldly
2011-08-22 16:17 <DocScrutinizer> I'd prefer he had found a way to snitch Nokia's root signing key used in OMAP3630 "TPM"
2011-08-22 16:19 <DocScrutinizer> but I guess iven if you find that file, it'd be secured with a passphrase that needs special treatment of Elop to get hold of it
2011-08-22 17:03 <wpwrak> DocScrutinizer: competent security ? don't count on it ;-)
2011-08-22 17:39 <roh> hm.. john wasnt seen here lately eh?
2011-08-22 17:39 <roh> .s
2011-08-22 17:39 <roh> meh
2011-08-22 17:40 <DocScrutinizer> hah
2011-08-22 17:40 <DocScrutinizer> just thought of you, while closing a 'mail.om.org: connection timed out' requester
2011-08-22 17:43 <wpwrak> roh: isn't it nice when people always think of you in their moments of distress ? you must feel like some superhero, better than superman ;-)
2011-08-22 17:48 <DocScrutinizer> well, I'm almost used to it. This warning requester poping up every 5 min, for the best part of last 2 weeks
2011-08-22 17:51 <DocScrutinizer> and each time I have to close it by clicking "OK", just to find it popping up 3min later again. Alas it's a modal requester which sucks big time
2011-08-22 17:53 <DocScrutinizer> ptobably I should stop polling of that account completely
2011-08-22 17:53 <DocScrutinizer> :-/
2011-08-22 18:12 <roh> meh
2011-08-22 18:12 <roh> tried re-setting the box again 2 times today but it doesnt look good. maybe we really need a human on the other end now to get it up again
2011-08-22 18:20 <roh> just entered a  verbose 'support-ticket'
2011-08-22 18:20 <roh> the will check the machine for visible damage now and if there is none run some tests
2011-08-22 19:29 <DocScrutinizer> roh: is it colocated?
2011-08-22 19:29 <DocScrutinizer> roh: ...or Hetzner hw?
2011-08-22 19:33 <wpwrak> rented, i think
2011-08-22 19:36 <DocScrutinizer> if it's rented then they shall damn replace it for a working iron there
2011-08-22 19:37 <DocScrutinizer> When I rent a car, I won't accept extended repair times in the garage. If we rented a server, that was meant to be a working one
2011-08-22 19:39 <DocScrutinizer> I thought they even guarantee a certain uptime percentage
2011-08-22 19:39 <DocScrutinizer> which should be better than 95%
2011-08-22 20:21 <qi-bot> The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-08222011-0827/
2011-08-22 20:49 <roh> DocScrutinizer: hetzner hw, really old one
2011-08-22 20:56 <DocScrutinizer> roh: I know a Hetzer service guy, if that can help in any way
2011-08-22 20:56 <DocScrutinizer> he offered to move the server on one of his boxes
2011-08-22 20:56 <DocScrutinizer> I said "thanks, but no thanks"
2011-08-22 20:57 <DocScrutinizer> maybe that was a bit unthought
2011-08-22 20:57 <jow_laptop> sounds offending somehow :)
2011-08-22 20:58 <jow_laptop> however hetzner is also the hoster that will write you a mail stating that they move your server across germany tomorrow ...
2011-08-22 20:58 <DocScrutinizer> Actually I said "ich glaub wir wollen da root rechte behalten"
2011-08-22 20:59 <jow_laptop> ah I see
2011-08-22 20:59 <roh> das eh.
2011-08-22 21:00 <DocScrutinizer> I can ask him to swap the friggin iron
2011-08-22 21:00 <roh> the hw seems just instable and crashing. i guess psu or mainboard are broken/caps burnt or so... i already added a support ticket
2011-08-22 21:00 <DocScrutinizer> gimme the ticket number, and I'll ping him to have an eye on it
2011-08-22 21:00 <roh> also we seem to have gotten some kind of filtering on the vm master ip from and to the outside, just the vm-subnet was working so i ignored it
2011-08-22 21:02 <roh> hm. no clue.. havent gotten the mail for it. need to ask gismo tomorrow.. maybe i should add myself to that list sometime
2011-08-22 21:03 <roh> the machine is #17402 if that helps somehow
2011-08-22 21:05 <DocScrutinizer> /queried him
2011-08-22 21:08 <DocScrutinizer> roh: anyway thanks for taking care