/srv/irclogs.ubuntu.com/2018/09/16/#ubuntu-x.txt

KitsuWhooaalkisg: I tested a https://www.asus.com/us/Graphics-Cards/A9250TD128M/overview/ and it worked out of the box, so I doubt ATi cards are affected05:25
alkisgKitsuWhooa: nice... do you think those horizontal lines in vbox were related? I haven't tested if pageflip off fixes vbox as well..05:26
KitsuWhooaThose go away by switching ttys, the ones on nvidia hardware don't05:27
alkisgAnd the one in tnt2 causes a segfault... those all might be bad codepaths, forced by a "central" bug somewhere...05:38
alkisgE.g. uninitialized resolution variable => may cause either corruption or segfault later on...05:38
alkisgThe corruption can be fixed by xrandr -s other-resolution; xrandr -s original-resolution05:39
KitsuWhooawhich is why a gdb backtrace would be useful05:39
alkisgSure; I'll set up the tnt2 system within the week05:40
KitsuWhooaYeah, I was just mentioning it05:40
KitsuWhooaApologies if it sounded a bit harsh05:40
alkisgNo no I very much appreciate all your input and help in this05:41
KitsuWhooaturns out I found a TNT206:38
KitsuWhooaand also what identifies itself as "NV10GL Quadro"06:43
KitsuWhooa01:00.0 VGA compatible controller: NVIDIA Corporation NV5 [Riva TNT2 Model 64 / Model 64 Pro] (rev 15)07:02
KitsuWhooaYup, X crashes right after the login screen07:04
alkisgKitsuWhooa: do you have epoptes working in your ltsp setup? Could you run this at the login screen, before login, and see if it's still crashing or not? xrandr -s 640x480; xrandr -s original-resolution07:11
KitsuWhooaI don't have LTSP set up on epoptes, but I do have a shell07:11
KitsuWhooatwo of them07:11
alkisgOK, you'd need to export DISPLAY and XAUTHORITY for xrandr to work07:11
KitsuWhooawould I need to rebuild the squashfs image to add epoptes?07:12
alkisgYes07:12
KitsuWhooaAny way to rebuild the image without keeping the old one around during build?07:12
KitsuWhooanot enough disk space :p07:12
alkisgltsp-update-image --no-backup -c /07:13
KitsuWhooaexcellent, thank you07:13
alkisg...stop nbd-server first so that it's not in use07:13
KitsuWhooaAlso, I think I found a mate bug07:13
KitsuWhooahttps://tasossah.com/s/3d40462bc831.jpg07:13
KitsuWhooaI don't even know what I did to make those two network indicators show up07:14
alkisgIt goes away if you kill/rerun nm-applet, or on next login07:14
alkisgIt's some race condition somewhere, I haven't pinpointed it07:14
KitsuWhooaSo, I need both epoptes and epoptes-client on the server?07:15
alkisgYes. apt install epoptes should be enough, it installs epoptes-client as well07:15
KitsuWhooaah07:15
KitsuWhooaokay07:15
KitsuWhooaRight, after being distracted for a bit08:04
KitsuWhooaI can't seem to be able to find the nouveau debug symbol package08:04
KitsuWhooaAh, they're on a separate repo08:11
KitsuWhooaalkisg: that did in fact make it not crash08:43
KitsuWhooaI have to say though, the TNT2 is really slow at 1680x105008:45
KitsuWhooaand I got epoptes set up too, really cool 08:45
alkisgKitsuWhooa: it sounds like it's something in xorg initialization that goes wrong, and gets correctly initialized with xrandr09:05
KitsuWhooaEeeeyup09:22
KitsuWhooaI'll try with gdb now and see if I can find anything interesting09:22
KitsuWhooaAlso, wakeonlan works and it got me more excited than it should have :p09:23
KitsuWhooas/and/to/09:23
KitsuWhooaalkisg: I ran startx, I attached gdb, and then after a while epoptes said my client went offline and killed my remote terminal09:41
KitsuWhooaany idea why?09:41
KitsuWhooa(X was in a frozen state)09:41
KitsuWhooanetwork never died either09:42
alkisgKitsuWhooa: how much ram does that client have?09:51
alkisgoom?09:51
KitsuWhooaI checked dmesg, not oom09:51
KitsuWhooait has 3x256 DDR109:51
alkisgStrange09:52
alkisgWhen the client is logged off, do you see it in epoptes as a blue icon?09:52
alkisg(fat client)09:52
KitsuWhooayeah09:52
KitsuWhooaand I can even spawn a shell09:52
alkisgBtw epoptes is supposed to reconnect after a minute of inactivity, did it?09:53
alkisgThe remote terminal was "root", not "user", right?09:54
KitsuWhooayup09:54
KitsuWhooait did not reconnect, no09:54
alkisg(root epoptes-client runs from systemd as root, while user runs from /etc/xdg/autostart as the user)09:54
KitsuWhooaand I checked that the network was still functioning09:54
alkisgThat's rather strange, if you have a vt on the client it would be interesting to rerun epoptes-client as root, make it crash again, and see the stderr there09:55
KitsuWhooaI do yeah09:55
KitsuWhooalet me try again09:55
KitsuWhooaI have two vts and the remote shell09:56
KitsuWhooaI ran startx on the vt and attached gdb through the epoptes root shell09:56
alkisg(btw to open another vt if needed, it's openvt bash)09:57
KitsuWhooaI have two09:57
KitsuWhooabut I will, thanks09:57
alkisge.g. if you want to attach gdb from a vt, so that it is more "stable"09:57
alkisgexport $(/usr/share/epoptes-client/get-display) => gives you access to xorg btw09:58
KitsuWhooaI wanted the gdb session remotely so that it's more comfortable for me to work as I will be using my desktop keyboard09:58
alkisg(DISPLAY/XAUTHORITY)09:58
alkisgYeah, I know the feeling :D09:58
alkisgI don't know why epoptes would do that though09:58
alkisgAh maybe systemctl status epoptes-client would show the stderr09:58
KitsuWhooaservice vboxadd stop09:58
KitsuWhooa...oops09:58
alkisgOr journalctl something, for the previous crash09:59
KitsuWhooaI'll check, yeah09:59
KitsuWhooais it python?09:59
KitsuWhooaI'm used to seeing segfaults in dmesg, but if it's python it probably won't be a segfault09:59
alkisgepoptes-client is mostly shell + socat10:00
alkisgA couple of python scripts are ran externally, as child processes10:00
KitsuWhooahttps://tasossah.com/s/1ecf05d7e48b.jpg10:01
KitsuWhooamight need to recompile nouveau without optimisations 10:01
KitsuWhooabut nouveau_present_flip_exec definitely has to do with double/triple buffering10:02
KitsuWhooaalkisg: 13:24:22 ltsp162 epoptes-client[1561]: Could not detect or access the active display10:40
KitsuWhooa13:36:34 ltsp162 epoptes-client[1561]: 2018/09/16 13:36:34 socat[1561] E waitpid(): child 1629 exited on signal 310:40
KitsuWhooaformer makes sense because X is frozen, not sure why socat died 12 minutes later though10:41
alkisgNot detecting the display shouldn't crash epoptes though10:43
KitsuWhooaalkisg: I traced the segfault down a bit16:44
KitsuWhooaIt's an X issue16:44
KitsuWhooaexaGetPixmapDriverPrivate() returns a 0 pointer16:45
alkisgKitsuWhooa: is this enough info for a bug report?19:40
KitsuWhooaPossibly, but I'm going to look more into it tomorrow. X 1.19 also has the same issue, so it happened some time before it.19:41
alkisgGreat!19:42
KitsuWhooaI tried disabling acceleration and it still crashed, which is a bit odd19:42
KitsuWhooabecause the above gets called due to acceleration19:42
alkisgNoAccel was the first thing I tried yeah19:42
KitsuWhooaI also tried setting AccelMethod or whatever it is to none19:42
KitsuWhooaand that didn't help either19:42
* alkisg has studied vga internals back in 1990, but has no idea about xorg internals :(19:43
KitsuWhooaI don't know much about it either to be honest.19:46
KitsuWhooaI will however say that this whole thing helped me uncover two kernel bugs that affect my desktop, that I'll need to look into/report at some point19:47

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!