00:25 imirkin: ajax: it would seem that way. i haven't personally confirmed anything.
15:21 karolherbst: anybody with a dlink router? :D my advise: burn that shit :D
15:24 Tomin: karolherbst: with original firmware? they are crap as usual (I've used DIR-615 and DIR-655)
15:24 karolherbst: well yeah, of course with the Dlink firmware
15:24 karolherbst: but the software is so broken…
15:25 karolherbst: Tomin: https://pierrekim.github.io/blog/2016-09-28-dlink-dwr-932b-lte-routers-vulnerabilities.html
15:26 Tom^: i think ive broken atleast 4 DIR-615
15:26 karolherbst: Tom^: ohh, I am sure you made them more secure in the end
15:27 Tom^: they all sort of burn up after a while if you have to much computers plugged in. :p
15:27 karolherbst: :D
15:27 Tom^: then i bought asus RT-N66U , havent had a issue since.
15:28 Tomin: I usually just put OpenWRT (or DD-WRT) if I can and nowadays just try to avoid anything that is not supported by OpenWRT
15:29 Tom^: karolherbst: also dear lord those are some serious vulnerabilities haha
15:31 karolherbst: :D
15:31 karolherbst: Tom^: remote "update" for the firmware
15:31 karolherbst: that's the best
15:31 karolherbst: so before you even put your own firmware on, the old one may be already backdoored and is backdooring the new one as well!
15:31 karolherbst: profit
15:32 karolherbst: that's even dumber than what lenovo did… I thought lenovo deserved place 1 for the most stupid backdoor ever, but here we go, Dlink made it
15:40 Tomin: even if there weren't any security problems, the D-Link user interface is already a good reason to avoid them. It's horrible, after every change the router must be rebooted...
15:41 karolherbst: yeah well, how can you trust such a router at all?
15:41 karolherbst: even the firmware you uploaded could be modified
15:43 Tom^: karolherbst: well now, how can we even trust gcc?
15:44 karolherbst: that's a good question indeed
15:45 karolherbst: because the backdoor might be hidden inside the binary and just adds the backdoor to every gcc on compile
15:45 Tom^: precisely
15:46 Tom^: which is why we need to compile clang with msvc and then compile gcc with clang
15:46 Tom^: !
15:46 Tom^: oh wait that will make clang to phone home. to microsoft
15:46 Tom^: and yep, that is a fact. xD
15:47 karolherbst: well yeah
15:47 Tom^: https://www.infoq.com/news/2016/06/visual-cpp-telemetry
15:52 Tom^: better to just do the 5 stages of grief fast, accept it and continue on like nothing is happening. ignorance is bliss
15:52 Tom^: ;)
16:34 siro__: imirkin_: is DRI3 stable on nouveau and modesetting ?
16:34 imirkin_: not sure what you mean by 'stable' - it won't crash or anything
16:35 imirkin_: (or at least i'm not aware of any such things)
16:35 imirkin_: however afaik some kde stuff misrenders greatly with it
16:36 siro__: I've got lot's of system hangs with DRI3 enabled while running nine
16:37 imirkin_: unexpected.
16:37 siro__: every time the process crashes (due to an assert) the kernel module dies,too
16:37 imirkin_: are you doing threaded command submission?
16:38 siro__: no i don't think so
16:38 imirkin_: nouveau + multithreading = no
16:38 imirkin_: iirc st/nine does something funky with threads
16:38 imirkin_: and perhaps that blows up in our faces with DRI3
16:38 siro__: it only has one pipe_contex
16:39 imirkin_: irrelevant
16:39 imirkin_: could multiple threads be calling into nouveau code at the same time?
16:39 imirkin_: *any* nouveau code, not just context functions
16:40 siro__: no, nine locks a mutex for each d3d9 interface call
16:40 imirkin_: and what is the "thread_submit" thing i've heard about?
16:41 siro__: ah, that's for presenting
16:41 imirkin_: which doesn't call into nouveau?
16:42 siro__: I don't know
16:42 imirkin_: can you disable it and see if that helps?
16:42 siro__: it uses xcb and friends to present it
16:42 imirkin_: (or is it off by default?)
16:43 siro__: atm it's not possible to disable it
16:43 imirkin_: ah ok. iirc it was an option
16:43 imirkin_: either that changed, or i'm misremembering
16:43 siro__: I thought about adding a dummy interface to run wine tests headless
16:43 imirkin_: what assert do you get btw?
16:44 siro__: I don't know, my system freezes
16:44 siro__: can't do anything
16:45 imirkin_: how do you know you get one?
16:47 siro__: good point. I guess there's one
16:47 siro__: I used llvmpipe first and found a few
16:47 siro__: at the same spot nouveau freezed my system, so I guess there's another one
16:48 imirkin_: usually an assert will end the program gracefully
16:48 siro__: that doesn't show up in llvmpipe
16:48 siro__: yes, it does on llvmpipe
16:48 imirkin_: a hang tends to be due to resource mismanagement