libera/#maemo-leste/ Sunday, 2021-12-26

rafael2kofono is ready to go production: https://github.com/rafael2k/ofono00:01
rafael2kFor people with pp, who want to test new ofono packages: http://173.255.215.196/pinephone/ofono-packaging/00:06
_inkyrafael2k: and thank you too for advices and ideas.01:12
_inkyi think eventually we have breakthroughs with pinephone support.01:12
_inkyand this is very important: people come to linux phones and operating systems via pinephone.01:12
_inkyso maemo will actually get more users via pinephone.01:13
_inkyi'll ask these couple of days if i need to update from -devel to get the updates you all made.01:14
tmlindhmm my bionic is all updated now, but not accelerated.. i have sgx-ddk-um-ti443x and xserver-xorg-video-omap installed, kernel module is initialized on boot..07:11
freemangordontmlind: check xorg.conf08:14
tmlindfreemangordon: don't seem to have one.. should it be under /etc/X11?08:14
freemangordonno, /usr/share/X11/xorg.conf.d08:15
tmlindok08:15
freemangordonthere should be 99-omap08:15
tmlindi have 99-omap.conf symlinked to 99-omap.conf.leste08:16
freemangordonyeah08:16
freemangordonthat's fine08:16
freemangordoncould you provide xorg log, from /tmp08:17
tmlindok08:17
tmlindfreemangordon: http://muru.com/Xorg.0.log08:20
tmlindnot much there for EE errors08:20
tmlindalso trying to run glxgears as user user fails08:21
tmlind/dev/dri is group readable/writable for video08:21
freemangordonglxgears?08:22
freemangordonyou should run es2_gears08:22
tmlindoh ok08:22
freemangordonOGL is not accelerated08:22
freemangordonbrb08:22
tmlindok es2gears works :)08:24
tmlindstellarium is not accelerated, let me recheck08:24
tmlindstarting stellarium as user produces: QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled08:25
tmlindi can start is as root but it's not accelerated08:25
tmlindfyi08:25
tmlindhmm es2tri triangle is only partially visible somehow08:28
freemangordondoes glmark2_es2 work?08:34
freemangordontmlind: actually, does your device boot to h-d?08:34
tmlindfreemangordon: yeah boots now to h-d, looks like stellarium tries to start with sgx with QT_QPA_PLATFORM=eglfs stellarium08:40
tmlindthen segfaults08:40
tmlindlet me check glmark2_es208:41
tmlindhmm can't find glmark2 package..08:42
freemangordonh-d is accelerated, right?08:42
freemangordonglmark2 shall be compiled, there is no package08:42
tmlindok, h-d looks a bit jerky, not sure if it's accelerated08:43
freemangordonhmm, weird08:43
tmlindi'm pretty sure h-d is accelerated, only jerky here and there08:43
freemangordonthat's weird, should be smooth08:43
freemangordonbut well, i have d4 here, not bionic08:44
tmlindshould be about the same08:44
freemangordonmaybe lets wait for Wizzup to share his experience08:44
freemangordonbut swiping h-d should be smooth08:45
freemangordonwell, non-accelerated h-d renders with 1-2 fps, so... :)08:45
tmlindyeah it's mostly smooth, sometimes starting a new app the animation is kind of jerky..08:45
freemangordonah08:46
freemangordonwell, for sure we have issues on omap, there is also tearing and the reported fps looks too high for what is really seens08:47
freemangordon*seen08:47
freemangordonbut otherwise is useful08:47
tmlindyup looks way better than earlier :)08:50
tmlindheh looks like gdb shows stellarium segfaults at ssl libcrypto somewhere..08:56
tmlindok got stellarium running with QT_QPA_PLATFORM=eglfs stellarium08:58
tmlindsorry with QT_QPA_PLATFORM=eglfs stellarium --home-planet=mars08:59
tmlindsome location lookup issue it seems :)08:59
tmlindabout 9 fps it seems08:59
freemangordon:)08:59
freemangordonhmm, shouldn;t it be faster?08:59
tmlindi'm seeing someting like 12 fps with wayland09:00
freemangordonah09:00
freemangordonwell, given that compositing is non-accelerated...09:00
freemangordonhmm, maybe I shall RE that part too09:00
freemangordonbtw, is it fullscreen?09:00
tmlindyeah it's full screen09:01
freemangordonhmm09:01
freemangordonshould be the same like WL09:01
freemangordonif not faster09:01
tmlindlet me check again on wl09:01
freemangordonwith 'mars'09:01
tmlinduh looks like i have some pvr issue with my wl setup right now, need to check the fps later09:07
tmlindswitching from stellarium to h-d window list hung xorg09:10
freemangordonhmm09:11
freemangordonsome oops?09:11
tmlindno, Xorg.0.log has many (EE) OMAP(0): ERROR: waitForBlitsCompleteOnDeviceMem: PVR2DQueryBlitsComplete failed with error code: -8 (Blit not complete)09:12
freemangordonthis should not result in a hang09:13
tmlindkeeps producing them about every 500 ms09:13
freemangordondmesg?09:13
freemangordonI would say there is HW recovery trigered09:13
tmlindno errors09:13
freemangordonweird09:13
tmlindwhat should i type to restart xorg?09:14
freemangordonnothing09:14
freemangordonI mean - you shoud restart the device09:14
tmlindkillall -9 Xorg at least got fb back09:16
freemangordonyeah09:16
freemangordonhmm, we even have tearing with modesetting without glamor09:17
freemangordonthis is omapdrm behaving I would say09:17
tmlindweird now it's behaving after a reboot09:23
freemangordonhmm?09:27
freemangordonyou mean there are no issues?09:27
tmlindcan't make QT_QPA_PLATFORM=eglfs stellarium --home-planet=mars hang after switching between app view and stellarium09:28
freemangordonit should not :)09:29
freemangordonI was hoping modesetting with glamor will hit > 50 fps on d409:45
freemangordonbut unfortunately it hits 50fps and that's it09:46
freemangordonand it suffers from the same tearing issue09:46
tmlindanyways a massive upgrade to get rid of all the old buggy legacy crap with the kernels and ddk-1.9 :)09:49
* tmlind goes to investigate fridge for the ham09:50
freemangordontmlind: any advice on how to deal with omapdrm tearing issue? I need upstream support, but I doubt Tomi will care about that09:50
Wizzuprafael2k: once I get home in ~8 hours I'll look at packaging this stuff, ty10:05
Wizzup08:56 < tmlind> heh looks like gdb shows stellarium segfaults at ssl libcrypto somewhere..10:06
Wizzupthis is openssl testing instructions (sigill)10:06
Wizzupfreemangordon: same for lima bug/video, will do that when I get back10:07
freemangordonok10:08
freemangordonno hurry10:08
Wizzup:)10:12
WizzupJust don't have the device here at the moment10:12
freemangordonyay, omapdrm BO patch is in -next :)10:14
tmlindfreemangordon: what's the omapdrm tearing issue?10:27
tmlindWizzup: i guess that openssl issue will get fixed upstream pretty fast10:29
freemangordontmlind: h-d swiping tears terribly10:31
freemangordonit is clearly visible in portrait10:31
freemangordonrotate you bionic in portrait and swipe10:31
freemangordon*your10:32
freemangordonthis happens with both omap and modesetting drivers10:32
freemangordonwith modesetting it happens even with no HW accel, though less visible because of low fps10:32
freemangordonI wonder if it is caused by omapdrm starting another flush while still there is a flush in progress10:33
freemangordonbut, it happens on hdmi too10:33
freemangordonhmm, actually lemme try again on hdmi10:33
freemangordonyep, there is tearing on HDMI as well10:40
tmlindok10:41
freemangordontmlind: hmm, if I lower the SGX frequency to 0x1f, tearing disappears on HDMI10:44
freemangordonI guess by the time the new frame is ready the old one has already been flushed or somesuch10:45
tmlindweird10:45
Wizzuptmlind: I don't think it is an issue, it's just it testing for instructions with sigill signal handler10:45
tmlinddoes reverting "drm/omap: Fix omap_gem_dma_sync_buffer() when we already have a dma_addr" make it better or worse by any chance?10:45
Wizzuptmlind: as in I don't think this is a bug, you just see it in gdb, but you can type 'c' for continue10:45
freemangordontmlind: lemme try10:46
tmlindso the test is to swipe the desktop background in portrait mode?10:47
freemangordonyes10:47
tmlindcan't seem to make it happen on my bionic10:47
freemangordonthe same happens in landscape, but is less visible10:47
freemangordoninstall marina theme10:47
tmlindi see a bit of flicker if i drag slowly10:48
freemangordonyep10:48
freemangordonhmm, wait10:48
freemangordontmlind: please install marina theme10:48
tmlindok10:48
freemangordonit has very sharp transition between backgrounds10:49
Wizzupmaybe just share the tearing test image10:49
* Wizzup bbiab10:50
freemangordonmarina is in the repos10:50
freemangordonand is cute, also :)10:51
tmlindyup with marina i see a variant of the black squares problem dragging the desktop slowly10:54
tmlindand also tearing between the desktop image borders10:55
freemangordonexactly10:55
freemangordonthis is what I mean10:55
freemangordonthis happens no matter driver/acceleration10:55
freemangordonthats why I think it is omapdrm10:55
tmlindi'm guessing the black artifacts problem gets worse with "drm/omap: Fix omap_gem_dma_sync_buffer() when we already have a dma_addr" reverted?10:56
tmlindthe tearing might get better..10:56
freemangordonreverting as we speak :)10:56
freemangordonI see no black artifacts though10:56
freemangordonsometimes I see some corrupted pixels (black) in the left top corner10:57
tmlindin portrait mode, slowly keep swiping to the left until you see tiny black rectangles at top right corner10:57
freemangordonok10:57
freemangordonnope10:57
tmlindtop left corner in landscape mode, top right corner in portrait mode10:57
tmlindor is it part of the background image pixmap?10:58
freemangordonnope10:58
freemangordonno10:58
tmlindmaybe it's part of the pixmap at the top right in portrait mode at the light blue area just before the dark blue border10:59
freemangordonI see nothing mis-rendered10:59
freemangordoncan;t see that here10:59
freemangordontmlind: sometimes bacground has some corruption, restart fixes that10:59
tmlindi see it on every 4th desktop10:59
freemangordonyep, that one :)11:00
freemangordonit is on top-left in portrait11:00
tmlindyup, so is that supposed to be there?11:00
freemangordonand lives just behind six bars11:00
freemangordonno11:00
freemangordonthis is deffinitely a corruption11:00
tmlindyeah that's the black tiles artifacts problem i also see with sway11:00
freemangordoncould you take a picture, to confirm we are talking about the same thing11:01
tmlindlet me consult my camera operator11:01
freemangordon:D11:02
freemangordontmlind: honestly, I don;t think this has anything to do with omapdrm11:03
freemangordonthis looks like a bug in pvr11:03
tmlindcould be11:03
freemangordonoh, lemme revert that patch11:04
freemangordonhmm, this patch looks to me like a reason for low fps :)11:08
tmlindok :)11:08
freemangordonlets see on the dvice though11:08
tmlindsee the black ants at top right corner here http://muru.com/m-l-ants.jpg11:08
freemangordonyes, exactly this11:09
freemangordonreboot fixes it usually11:09
freemangordonthis happens more often if your battery is low11:09
tmlindweird11:09
freemangordonbut I am almost sure this is either PVR or h-d/clutter bug11:10
tmlindso a variation of the ants problem i see on wayland is a bit larger black rectangles in the same location, top left corner for landscape mode11:10
freemangordonbecause this corruption is exactly behind and with the size of six squares icon11:10
freemangordoncould be11:11
freemangordonbut I almost never see that after a reboot11:11
freemangordononly if I play stopping/starting xorg/h-d11:11
tmlindwell m-l should revert "drm/omap: Fix omap_gem_dma_sync_buffer() when we already have a dma_addr" if it causes no other issues, wayland is unusable without that patch11:12
freemangordonthis should be fixed in wl though11:12
tmlindno idea how it should be fixed :(11:12
tmlindespecially if m-l also shows a similar issue on xorg11:13
freemangordonit should use sync11:13
freemangordonxorg uses "wait for blits"11:13
freemangordonbut WL can include sync objects in GL commands stream and wait for them, IIUC11:13
tmlindi don't think i've seen the ants with weston11:13
freemangordonugh, I should have fixed TS buttons udev rules before reboot :(11:14
freemangordonnow I have to wait device to autoconnect11:14
tmlindweird how the autoconnect stuff still takes few mins11:15
freemangordonnot on pinephone though11:15
tmlindweird11:15
freemangordonso it is something with d4 driver11:15
tmlindi wonder if adding iw dev wlan0 scan on start up would help11:15
freemangordonstill tears11:16
freemangordonlemme check fps11:17
freemangordonoh11:17
freemangordonwe hit 80 fps with ease11:17
tmlindnice11:17
tmlindmaybe check the stellarium on mars rate too?11:18
freemangordonis it in repos?11:18
tmlindyeah apt-get install stellarium11:18
tmlindtakes a while for the data files though11:19
freemangordonmaep renders with 45 fps though11:19
freemangordonthis is with 3-buffer11:19
tmlindneed to go for some family time now, ttyl11:19
freemangordonttyl11:19
freemangordonyay! I know why fps is too low - tmlind broke it :p11:20
freemangordontmlind: fps ~911:27
freemangordonbut, nothing moves, is that normal?11:28
freemangordonoh, ok, we hit 80 fps without 3-buffer11:33
freemangordonI think we shall disable it by default11:33
freemangordonat least on d4 it doesn;t seem we need 3-buffer11:47
rafael2kWizzup: tks11:51
rafael2kWizzup: ofono will be pretty easy11:51
rafael2kWizzup: kernel wise, I want some help with git, and also some suggestion if I should just add the line in rules to install kernel, initrd and dts to /boot, or may be use a postinst scrit...11:52
freemangordonwow, firefox renders as mad!11:57
freemangordonhmm, why there is no sound?12:02
rafael2kWizzup: dtbs are being installed in /usr/lib/linux-image-5.15.10/allwinner/ and I copied by hand to /boot/allwinner12:09
rafael2kWizzup: kernel and initrd are installed, but they dont get copied to ddefault locations specified in boot.txt12:11
Wizzupfreemangordon: what did you change?13:56
Wizzuprafael2k: ok13:56
freemangordonWizzup: reverted 6dd1aad1d0c4716944098b7b0f2abdd3a26cc0be.15:18
freemangordonwe must do that asap15:18
Wizzupfreemangordon: in kernel?15:25
Wizzupfreemangordon: asap as in. now?15:25
freemangordonyes, in kernel15:28
freemangordonasas as 'as soon as we can'15:28
freemangordonthis brings massive improvement on d4 and n900 (not tested)15:29
freemangordonand will allow us to not use 3-buffer15:29
freemangordonwhich will reduce memory usage15:29
freemangordonthis commit is the reason for 6ms delay in drmModePageFlip()15:31
bencohdon't we want to actually flush cache to memory during sync_buffer() ?15:56
Wizzupfreemangordon: ok16:16
Wizzupfreemangordon: ok so I'll make a trace of the fallback method, *without* EGL_BUFFER_PRESERVED set?16:39
Wizzupor with?16:39
Wizzupbecause I already have both16:39
freemangordonwithout17:07
freemangordonbencoh: I think this is done on the other side (GPU)17:09
bencohhmm ...17:09
freemangordonIIUC17:10
bencohso the gpu automatically forces a cache sync when pushing a frame to it?17:11
freemangordonI don;t really know when pvr driver flush caches17:12
bencohah17:12
freemangordonbut it does17:12
bencohso it happens on the cpu side17:12
bencohwait, something's wrong ... if it already takes place, why would it take 6ms?17:12
freemangordonah, yes, if you look at it like that17:12
bencohI mean, why would it take another 6ms?17:12
freemangordonbencoh: this commit in omapdrm17:13
freemangordonnot in pvr driver17:13
bencoharen't both used in our case?17:14
freemangordonyes, they are17:14
bencohI feel like I'm missing something17:14
freemangordonbut omapdrm is not the one to flush anything, as it renders nothing17:14
freemangordonmaybe I am missing something too17:14
bencohsure, but then why would flushing writes to buffer take 6ms?17:15
freemangordonI am not sure what dma_sync_single_for_device does17:15
bencoh(unless that sync-to-device does more than what I think it should do on our platform, and for some reason takes a lot of time)17:16
freemangordonthis is done for every page of our scanout buffer17:16
freemangordonand yes, maybe it does more17:17
bencohI guess you checked reverting that commit doesn't result in (more) tearing? :)17:18
freemangordonI don;t see how this commit may affect tearing17:18
freemangordonand yes, I checked :)17:18
freemangordonit affects fps only17:19
bencohwell, gpu fetching a non-fully-synced buffer sounds like tearing expected to me, hence me asking :)17:19
freemangordonthat's the point, gpu should fetch nothing here17:19
freemangordongpu has already rendered and we prepare the buffer for displaying17:20
bencohbut it's supposed to fetch later on17:20
bencohhmm17:20
freemangordonwhy is that?17:20
bencohwait, I might be the one missing something17:20
bencoh(I probably am)17:20
Wizzupfreemangordon: hm ok, but didn't enunez ask to have it on?17:21
bencohis that an input buffer to gpu, or an output buffer from gpu?17:21
Wizzupmaybe I will share both17:21
freemangordonWizzup: ok17:21
freemangordonbencoh: this is a back buffer (so output) we are preparing to flip to be front17:21
freemangordongpu == renderer, gpu != display controler17:22
freemangordonso, this buffer is output for gpu and input for display controller17:22
freemangordonand this is display controller (so CPU) doing sync17:23
freemangordonbut there is nothing to be synced, IIUC, as CPU does not render17:23
freemangordonI think this commit mitigates the issues tmlind has with WL as it adds a delay, during which GPU finishes rendering17:24
freemangordonbut not fully, as sometims GPU needs more than 6ms to render17:24
freemangordondoes this sound sane?17:24
freemangordonit is absolutely possible that I am talking nonsense here, but the net effect is that reverting that results in stable 80fps being hit on h-d swiping without any visible rendering artifacts, besides the tearing and ants, but they are there with and without that commit17:27
freemangordonand also removing that commit results in drmModePageFlip() behave according to specs17:28
freemangordon(didn;t check xorg logs though)17:28
Wizzupfreemangordon: ok so I will revert 6dd1aad1d0c4716944098b7b0f2abdd3a26cc0be for now in our -devel kernel17:51
tmlindack, that patch is a hack17:54
freemangordonWizzup: :mod:17:55
freemangordon:nod:17:55
freemangordonWizzup: shall I disable 3-buffer to be enabled by default in omap code?18:13
freemangordonI think this is the sane18:14
freemangordonthe other option is to disable it in config18:14
WizzupI would disable by default if we have no use for it18:15
freemangordonok, will disable and spin a new build18:15
Wizzupty18:16
Wizzupmaybe wait for kernel to complete18:16
freemangordonfor the build?18:16
freemangordonsure18:16
freemangordontmlind: can you recall any other hack patch that might be related to tearing?18:25
freemangordonhmm, I think I know what the possible fix for the corruption could be, in xorg18:28
freemangordonthere is pvr driver call that flushes GPU buffers to memory18:29
Wizzupgreat @ corruption18:30
freemangordonwell, I think this is of low prio18:32
Wizzupmhm18:32
tmlindfreemangordon: well are you seeing the same issues on n900? if not, it's somehow related to the tiler possibly18:35
freemangordonnever seen18:35
freemangordonIIRC18:35
freemangordonyeah, could be related to tiler18:35
freemangordonWizzup: ever seens something like http://muru.com/m-l-ants.jpg on n900?18:36
WizzupI do not recall at the moment, I only saw these problems on d4 windows18:37
freemangordonmhm18:37
Wizzupbut my n900 doesn't run for very long on X atm18:37
Wizzupbecause of the alloc problems18:37
freemangordonyeah, but this happens on startup only18:37
freemangordonwithout running any application18:37
Wizzupnever saw that on d4 either18:37
WizzupI only see it in overview windows18:38
freemangordonI am seeing it occasionally18:38
Wizzupcompose view18:38
freemangordoncould be related to compositing being done on CPU18:38
freemangordonmaybe those will disappear when I implement GPU compositing accel18:38
Wizzuphow does that work?18:39
freemangordonHW accel compositing?18:39
freemangordonUSSE code in pvr exa18:39
freemangordonbinary shaders IIUC18:39
Wizzupok18:42
freemangordoncould be a bug i nclutter as well18:42
freemangordonso, tomorrow will start implementing non-CMA buffers support18:43
freemangordonhopefully shouldn;t take much time18:44
tmlindi wonder what would happen with omapdrm .cpu_cache_flags = OMAP_BO_UNCACHED for omap4?18:45
tmlindjust as an experiment to see if the issues disappear18:45
tmlindinstead of OMAP_BO_WC18:46
freemangordontry it, I am curious as well18:46
tmlindyeah might be worth trying18:46
freemangordonWizzup: hmm, seems like kernel build is not progressing19:00
freemangordonoh, scratch that19:01
freemangordonI was looking at wrong xonsole outpit19:01
freemangordon*console19:01
Wizzupfreemangordon: it easily takes 2-3h19:02
Wizzupstill waiting on the solidrun server :(19:03
freemangordondepmod is being run, so it is @ end19:12
Wizzupgreat19:15
freemangordonhmm, now it doesn;t hit more than 56 fps with 2-buffer19:58
freemangordonweird19:58
freemangordonwell, ok, will reenable it by default and will fix one more issue20:04
Wizzupgreat20:06
freemangordontmlind: testing a fix for xorg error messages you were seeing, will let you know when it hits the repo20:11
freemangordonnon-fullscreen, landscape, glmark2 Score: 5620:18
Wizzupwith h-d running?20:19
freemangordonyes20:19
Wizzupnot bad :)20:20
freemangordongears run with 80fps20:20
freemangordonthis is vsynced20:20
Wizzupis that max screen refresh or something?20:20
Wizzuprighgt20:20
freemangordonyes20:20
freemangordoneven in tasknav small window ;)20:21
Wizzup:D20:21
freemangordonWizzup: it is in the repo, enjoy and report issues :)20:48
* Wizzup updates21:12
Wizzupfreemangordon: quite smooth indeed21:36
WizzupI guess I should brush off the pinetab as well once we have the other gfx bug fixed22:27

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!