log☇︎
39500+ entries in 0.007s
asciilifeform: ^ subsequent
asciilifeform: 1048576 bytes (1.0 MB, 1.0 MiB) copied, 150.483 s, 7.0 kB/s
asciilifeform: ^ 1 run
asciilifeform: 0 bytes copied, 99.8535 s, 0.0 kB/s
asciilifeform: fwiw dd never stuck midway, only on opening tty.
asciilifeform: so far can't think of a third.
asciilifeform: i suspect an oddity with the linux tty subsystem. the Right Thing solution would be to find it. the alternative, ugly solution, is 1) 512 byte buffered reads 2) with timeout . ☟︎
asciilifeform: diana_coman: ok, finally managed to get a stuck dd
asciilifeform: aha
asciilifeform: and reads from buffered tty
asciilifeform: well the 1 obvious diff, is that it defaults to 512byte blocks
asciilifeform: it's not a constant rate, 7 is the empirical avg., and depends on environmental temp
asciilifeform: ( evidently the dc has pretty good cooling )
asciilifeform: not really, the nominal production is 7
asciilifeform: ^ dd
asciilifeform: 1048576 bytes (1.0 MB, 1.0 MiB) copied, 151.838 s, 6.9 kB/s <<
asciilifeform: eucrypt's test reliably hangs, however, ~every other run
asciilifeform: hm, over here dd ( with only 1 FG init'd ) is working correctly
asciilifeform: this box is running traditional gentoo, however, it more closely resembles primary s.mg machine than the test box
asciilifeform: ( fwiw i've dd's from dulap's FGs previously, with 0 signs of any problem )
asciilifeform: diana_coman: what was the exact process for dd hang ?
asciilifeform: not discovered culprit yet, literally 5min ago finished pressing & building ( used ave1's gcc , for completeness )
asciilifeform: dulap
asciilifeform: diana_coman: i've built eucrypt and replicated your hang
asciilifeform: there's liquishit kilometre deep in there nao
asciilifeform: i thought we had +v
asciilifeform: hey mod6 , why is #pizarro filling up with spamola ?
asciilifeform: the ameri-protestants 'improved' even on this, their heaven iirc is full of aborted foeti
asciilifeform: ( i recall a trilema article where mircea_popescu actually walked fleanode looking for signs of life, found ~0 )
asciilifeform: entirely possible.
asciilifeform: are we the only moderated chan left or wat
asciilifeform could not muster the fuck-giving to read the payload, has nfi what the thing wants ☟︎
asciilifeform: there's a dozen or so of these going, e.g. #linux-rockchip is filling up
asciilifeform: hunchback straightens -- in the grave.
asciilifeform: i dun think there is a cure for what ails these .
asciilifeform: mircea_popescu: spambot, spammed '9000' unmoderated chans
asciilifeform: afterwards can go to new tenant.
asciilifeform: mod6: recall, that one he asked to let be until expires
asciilifeform: ( how exactly this ties the hands of, e.g. , taiwanese fabs, i do not presume to know , but result is evident )
asciilifeform: they're actually named by name on usg 'export ban' list.
asciilifeform: i've turned up some hints that usg actually interferes with the ADC makers -- 'ohnoez, moscow could use fast ADC in radar set'
asciilifeform: i.e. are pressed shitboard , rather than hardwood.
asciilifeform: and they ~all do shenanigans with multiple slow ADCs masquerading as 1 fast one
asciilifeform: doubtful, all of the examples i've been able to peek into, are full of xilinx.
asciilifeform: ( in this context, 'sane' ~= sits on pcie bus, and ADC turnaround is fixed # of bus cycles, preferably 1. and documented i/o. )
asciilifeform wouldn't consider , say, 1btc , for a ~sane~ scope, to be unreasonable
asciilifeform: so if you want a 1G/s scope with os where you actually have some control of the timing ( for e.g. real time phase sampling ) you're 100% phuqed.
asciilifeform: ( these, for extra laughter, come with ~built in windows~ in the instrument itself ! )
asciilifeform: not the 250k agilent either.
asciilifeform: mircea_popescu: note, not in the i-dun-give-half-a-fuck-what-it-costs market, either
asciilifeform: sorta hilarious , this, 'here's pc with very spiffy 6G/s pcie bus, for 100$, but if you want to connect something useful to that, haha, what do you think this is, the fyootoor'
asciilifeform: 1000. whichever.
asciilifeform: not for 100 $, not for 100, not for 10,000.
asciilifeform: in other noose, since 1st time i asked the q in 2013, appears that there is ~to this day~ not such a thing as a 1Ghz oscilloscope with any linux support whatsoever.
asciilifeform: 1 scissor, 1 pant...
asciilifeform: ( tho perhaps, a FG with only 1 rng plugged in, could be a 'fuckgoat' )
asciilifeform: lol BingoBoingo , it's still plural, sorta like 'scissors'
asciilifeform: goodnight diana_coman
asciilifeform: ok , should suffice for test, i'ma report tomorrow .
asciilifeform: diana_coman: is http://btcbase.org/log/2018-07-31#1838330 an exact description of the test ? ☝︎
asciilifeform: i'ma test on dulap also, it has identical fg/cabling setup to primary s.mg box
asciilifeform: rather, ruled out as primary cause, could easily be the ultimate barf source in conjunction with 1 / 2
asciilifeform: ( kernel can be ruled out, both s.mg machines currently have afaik identical kernel )
asciilifeform: the possible suspects , so far -- 1) ttl dongles 2) hub 3) musl userland , somehow
asciilifeform: indeed
asciilifeform: ( the 2 constraints -- 1) ~not ever ftdi~ 2) no flashable chips plox )
asciilifeform: diana_coman: ftr i am still on the lookout for anything like a practicable replacement for pl2303
asciilifeform: diana_coman: i'm gonna try and replicate here in the torture room, with your proggy -- i have both cable types here
asciilifeform: BingoBoingo: 'blue' is theoretically same chip, but from a diff chinese seller ( fwiw asciilifeform's desk FG operates from a 'blue' )
asciilifeform: http://btcbase.org/log/2018-07-31#1838486 << i've only ever observed pl2303-specific headache when 3+ operating ( and even then , consisted of slow, rather than halted, signal ) ☝︎
asciilifeform: i was about to suggest, to swap both cables , see if these can be ruled out
asciilifeform: 'their poorly fitting bulletproof vests are beyond their expiration dates' << lolwat
asciilifeform: ( some usb2 hub chipsets behave dysfunctionally with pl2303 )
asciilifeform: btw also worth trying the item listed in 'Tip for Linux Users' at http://nosuchlabs.com/hardware.html .
asciilifeform: interesting
asciilifeform: diana_coman: does your boot-time sh init both dongles currently ?
asciilifeform: suggests oddity in pl2303 mod
asciilifeform: good % of unixland, by weight, consists of this.
asciilifeform: 'if i actually fix it, would have to admit that it was buggy'
asciilifeform: recall , similarly, koch's 'fix' for his mpi bug.
asciilifeform: afaik to this day no such provision in any unixlike.
asciilifeform: ( naturally the imbecile kernel doesn't actually test whether something is riding on the tty prior to opening, 'why would we' )
asciilifeform: mircea_popescu: happened to me '9000' times when testing FG, and earlier iron.
asciilifeform: btw if anyone wants to experimentally observe the zombie effect, can do it with ordinary gnu 'screen' -- when opened on a tty with blocking i/o, will routinely leave zombie turd instead of properly terminating, then hours later you find that tty is wedged, and discover 9 copies of 'screen' in process table.
asciilifeform: 'and for extra sport, i will also shit where you cannot clean'
asciilifeform: 'i will shit, you will clean'
asciilifeform: unix represents not merely bed-pissing, but just about ~ideological~ pant-shitting mentality.
asciilifeform: if diseased mind fails to produce impulse to visit toilet instead of filling own pants, then yes, work with.
asciilifeform: somewhere near the top of the list, right below 'gotta check EVERY system call for failure erry time in user coad'
asciilifeform: mircea_popescu: the astonishing bit isn't even that system5 unix had this nonsense, but that the linux derps faithfully re-created it.
asciilifeform: lol
asciilifeform: (~= 'for erry smart-arse, a threaded cock will be found' ) ☟︎
asciilifeform: 'на каждую хитрую жопу, всегда найдется свой болт с резьбой'(tm)(r)(proverb) ☟︎
asciilifeform: pretty great
asciilifeform: lol
asciilifeform: and ought to ring all of the alarm bells.
asciilifeform: a FG that produces , under normal conditions, 0 output for, say, 30 seconds, is indicative of dead iron.
asciilifeform: this being said, if you implement a timeout for the blocking reads, you will not have zombie problem.
asciilifeform: ( asciilifeform did not write the linux i/o subsystem ; nor the pl2303 kernel mod ; and will readily admit that they are sad. and if anyone has idea for some other means to connect a 115200 baud box to machine, that does not suffer from the weakness of these, i'm as always all ears )
asciilifeform: well not each time, but to see if the 'init breaks the dongle' hypothesis is troo.