pere has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
doc|home is now known as doc
zmatt has quit [Ping timeout: 252 seconds]
Wikiwide has quit [Ping timeout: 250 seconds]
Wikiwide has joined #maemo-leste
zmatt has joined #maemo-leste
L29Ah has joined #maemo-leste
Pali has quit [Ping timeout: 240 seconds]
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
macros_ has joined #maemo-leste
macros__ has quit [Ping timeout: 252 seconds]
joerg has quit [Ping timeout: 245 seconds]
joerg has joined #maemo-leste
alex1216 has joined #maemo-leste
<sicelo> kexecboot starts on droid 4 without a battery in the device. Wonder what's missing to allow an OS to start too
Wikiwide has quit [Ping timeout: 245 seconds]
<freemangordon> Wizzup: booting with non-cma buffers patch :)
<freemangordon> first try that is
wunderw has joined #maemo-leste
wunderw has left #maemo-leste [#maemo-leste]
<Wizzup> freemangordon: great
Pali has joined #maemo-leste
<freemangordon> Wizzup: seems to wokr
<freemangordon> *work
<freemangordon> Wizzup: do you have old n900 image around? with old kernel/pvr?
<freemangordon> I need to know what FPS achieve that when swiping hildon-dekstop
<freemangordon> also, gears fps
<freemangordon> also, what is bpp of Xorg
<Wizzup> freemangordon: I can dd some old(er) image
<Wizzup> freemangordon: pretty sure we're on 24bit regardless
<freemangordon> ok
<freemangordon> but I would like to have fps
<freemangordon> because current seems a bit low to me
<Wizzup> ok
<Wizzup> wunderw - still around?
<Wizzup> or is that maybe wunderwungiel[m]
<Wizzup> I wonder what the latest image is that still worked
<Wizzup> maybe maemo-leste-1.0-armhf-n900-20211031.img.xz
<Wizzup> dd'ing
<freemangordon> Wizzup: how do you want to test the patch? I think it would be easier to give you .patch file,no?
<Wizzup> yes
<freemangordon> ok
<freemangordon> Wizzup: final test and will provide you the patches
<Wizzup> ok
<freemangordon> hmm...
<freemangordon> maybe it doesn't work
<freemangordon> I cannot open any application
<freemangordon> or, it is something else
<Wizzup> freemangordon: do you want test with or without clutter
<freemangordon> anyway, I'll provide the patches to you
<freemangordon> shoudl not matter
<freemangordon> Wizzup: sent over the email
<freemangordon> hmm, I don;t see any memory allocation errors, so it must be something else
<freemangordon> Wizzup: you have to patch both kernel and omap driver
<Wizzup> ok
<freemangordon> what?!?
<freemangordon> died loading invoked application: '/usr/bin/controlpanel.launch: cannot dynamically load position-independent executable'
<freemangordon> why we hit that again?
<Wizzup> glibc stuff?
<freemangordon> hmm
<freemangordon> oh
<freemangordon> I guess I have new glibc on that device
<freemangordon> yeah 2.31-4
xmn has quit [Quit: ZZZzzz…]
<freemangordon> ok, I think I have to flash an image
<freemangordon> not sure I can revert
<freemangordon> lets try though
meldrian is now known as derBass
<freemangordon> Wizzup: but wait, how hildon-desktop starts then?
<freemangordon> maybe we didn;t fix all the applications
<freemangordon> yeah, looks like that
<Wizzup> weird, I don't have this problem
<Wizzup> are you sure you're up to date/
<freemangordon> I installed libc from chimaera back then
<Wizzup> freemangordon: what is clutter fps again
<Wizzup> env
<freemangordon> CLUTTER_SHOW_FPS=1
<Wizzup> max fps I get is 49
<Wizzup> but most is lower than that
<Wizzup> between 25-35
<freemangordon> yeah, max is what I wanted to know
<freemangordon> here we hit max 40
<freemangordon> I know why is that, but this should be fixed in the kernel
<freemangordon> the p[oint is now omap driver waits for rendering to complete before queuing page flip
<Wizzup> ok
<freemangordon> this is again that missing fence
<Wizzup> freemangordon: so I should also disable cma now?
<Wizzup> in .config
<freemangordon> no, you cannot
<freemangordon> just lower the value to 16MB
<Wizzup> ok
<Wizzup> building kernel
<Wizzup> freemangordon: so apply your xf86-video-omap on top of your triple buffering commit?
<freemangordon> yes
<Wizzup> ok
inky_ has quit [Read error: Connection reset by peer]
<Wizzup> freemangordon: I get like 18 fps
<freemangordon> go to launcher
<freemangordon> then back
<Wizzup> wait
<Wizzup> forgot omap ddx
dreamer has quit [Remote host closed the connection]
<freemangordon> Wizzup: hmm?
<Wizzup> sec
<Wizzup> freemangordon: well I forgot to dpkg -i the ddx I built
<freemangordon> ah
<Wizzup> freemangordon: but now with the new ddx it basically crashed almost right away
<freemangordon> weird
<Wizzup> with:
<Wizzup> [ 138.991149] cma: cma_alloc: reserved: alloc failed, req-size: 375 pages, ret: -16
<Wizzup> maybe I installed the wrong ddx?
<Wizzup> hmm
<freemangordon> see, maybe my patch does not work
<freemangordon> but yeah, you must have the correct ddx
<Wizzup> I think I have
<Wizzup> let me try once more
<Wizzup> but it's weird since it seemed fine before
<freemangordon> here it goes locale generation, will take a while it seems :(
<freemangordon> but at least I think I will be able to downgrade
<sicelo> Wizzup: did sre's patch for acx565akm help?
<Wizzup> the panel? yes, I replied that on ml
<sicelo> oh nice. for some reason i don't get all the messages anymore. but nice if that helps
<freemangordon> Wizzup: any progress?
<Wizzup> checking
<Wizzup> max fps is like 6
<Wizzup> 26
alex1216 has quit [Ping timeout: 256 seconds]
<Wizzup> no crash this time at least
<Wizzup> well not yet
<freemangordon> enter and exit the launcher
<freemangordon> and check fps then
<Wizzup> yes I did that
<freemangordon> still 26?
<Wizzup> X crashes again
<freemangordon> hmm
<Wizzup> [ 131.519] (WW) OMAP(0): WARNING: get vblank counter failed: Invalid argument
<Wizzup> [ 131.521] (WW) OMAP(0): WARNING: flip queue failed: Invalid argument
<Wizzup> [ 639.147] (EE)
<Wizzup> [ 639.153] (EE) Backtrace:
<Wizzup> [ 639.243] (EE)
<Wizzup> [ 639.244] (EE) Segmentation fault at address 0x10
<Wizzup> [ 116.882995] omapdrm omapdrm.0: Failed to setup plane gfx
<Wizzup> [ 639.150726] cma: cma_alloc: reserved: alloc failed, req-size: 375 pages, ret: -16
<Wizzup> [ 539.129241] omapdrm omapdrm.0: Failed to setup plane gfx
<freemangordon> ugh
alex1216 has joined #maemo-leste
<freemangordon> well, not sure what's going on
<freemangordon> trying to bring my n900 back
<Wizzup> you don't get this on n900?
<Wizzup> ah ok
<freemangordon> no, but I didn;t have most of the things runnung
<Wizzup> yeah it usually happens for me when I start apps
<freemangordon> hmm , maybe 16MiB is too small
<freemangordon> could you try with 32?
<Wizzup> could be, but I also got this even with 64MiB some times, but that was before your patch
<Wizzup> sure
<freemangordon> yeah, now the patch should change the thing
<Wizzup> building kernel
alex1216 has quit [Ping timeout: 250 seconds]
<Wizzup> trying now
<freemangordon> oh,ok, seems I will have to dd
<freemangordon> but what?
<Wizzup> you mean what iamge?
<freemangordon> mhm
<freemangordon> will flash latest
<Wizzup> ok, you just need to fix mime and hope other stuff wasn't broken
<Wizzup> but for kernel you will need to do some more stuff I guess
<freemangordon> hmm yeah, other stuff
<Wizzup> with 32MB I got the same failure with just h-d scrolling
joerg has quit [Remote host closed the connection]
<freemangordon> ok, lemme dd and boot and test
<freemangordon> I wonder why it continues to use CMA
joerg has joined #maemo-leste
<Wizzup> mhm
inky_ has joined #maemo-leste
<Wizzup> anything you want me to check
<freemangordon> no
<freemangordon> maybe my patch is inclomplete
<freemangordon> *incomplete
<freemangordon> but I need to boot here to verify
<freemangordon> ugh, that one tears like hell
<freemangordon> I guess that's why it is so fast
<freemangordon> Wizzup: I shall upgrade to -experimental and then put my kernel, right?
<Wizzup> freemangordon: yes
<freemangordon> ok
<Wizzup> freemangordon: -devel might be ok too
<freemangordon> ok
<Wizzup> freemangordon: make sure to have the right libs
<Wizzup> I haven't set up the n900 meta yet
<Wizzup> freemangordon: as in ti343x
<freemangordon> yeah
<Wizzup> I still need to try dtb boot
<Wizzup> (without appended I mean)
<freemangordon> mhm
<Wizzup> shouldn't be too hard
<freemangordon> Wizzup: what is the kernel package name/version?
<freemangordon> or, we don;t have one yet?
<Wizzup> freemangordon: add droid4 component and insall linux-image-droid4 iirc
<Wizzup> or linux-droid4-image
<Wizzup> let me check
<freemangordon> ah, ok
<Wizzup> linux-image-droid4
<freemangordon> ok
inky_ has quit [Ping timeout: 256 seconds]
alex1216 has joined #maemo-leste
alex1216 has quit [Ping timeout: 240 seconds]
alex1216 has joined #maemo-leste
<freemangordon> Wizzup: how many applications to open?
<freemangordon> Wizzup: also, any clue why wifi does not work?
<Wizzup> freemangordon: wifi should work with our tree
<Wizzup> freemangordon: xterm, cpa, and just click around is enough
<freemangordon> hmm, cannot repro here
<freemangordon> but, with *my* tree
<Wizzup> freemangordon: I took your patch and applied it on top of this https://github.com/maemo-leste/droid4-linux/commits/wip/n900/maemo-5.15-cleaned-up
<Wizzup> and then also decrease cma from 64 to 32
<freemangordon> I opened xterm, cpa, clock, pdf,qalendar
<Wizzup> hmmm
<freemangordon> and that's with xorg from the repo
<freemangordon> lemme check cma size
<Wizzup> let me update the n900 I have
<Wizzup> I maybe forgot to dist-upgrade it
<Wizzup> although I don't think it matters
<Wizzup> 52 packages can be upgraded. Run 'apt list --upgradable' to see them.
<Wizzup> The following NEW packages will be installed: ti-omap3-sgx xserver-xorg-video-pvrsgx
<freemangordon> 65536K cma-reserved
<Wizzup> oof
<Wizzup> 64MB then
<freemangordon> mhm
<freemangordon> lemme reduce that
<Wizzup> it helps but you still run into it
<freemangordon> mhm
<freemangordon> yep, got that with 16mb
<Wizzup> ok
<freemangordon> hmm, maybe I shall take https://github.com/maemo-leste/xf86-video-omap/blob/master/src/omap_dri2.c#L237 into account
<freemangordon> pfff
vectis_ has joined #maemo-leste
<freemangordon> Wizzup: hmm, I think we shall do some calculations first
<freemangordon> like, if we want to do page flipping, what is the needed CMA per application
<freemangordon> maybe we shall not use page flipping on n900
<freemangordon> and instead do blits, the same way Nokia did it
<freemangordon> I guess they had reason to do it like that
<freemangordon> so, each application is 2-buffered in clutter - if we want to flip, those buffers must be CMA allocated
<freemangordon> so we have ~2MiB per application for those buffers
<freemangordon> and 1MiB for the 3rd buffer
<freemangordon> thus, we need 2xnum_apps+1 MiB CMA just for the buffers, IIUC
<freemangordon> hmm, what the? even after Xorg crashed, CMA free is still 0?!?
<freemangordon> looks like someone leaks cma memory
derBass is now known as meldrian
<Wizzup> freemangordon: I think so too @ memory leak
Blikje has quit [Ping timeout: 240 seconds]
<Wizzup> freemangordon: does cma show you what allocs what
<freemangordon> I don't think so
<freemangordon> in proc/meminfo there is something about it
<freemangordon> but I don;t know what it means
<freemangordon> like, what cmafree is
<freemangordon> hmm, with 24MB CMA I have now 13 apps open
<freemangordon> 8 of them are xterm, vbut still
<freemangordon> Wizzup: could you try with 32MB, to see if you can trigger the crash?
mepy has joined #maemo-leste
<freemangordon> Wizzup: with 24MiB CMA I can start 11 xterms (one of them running htop)+settings+calendar+calculator+pdf+ham
<freemangordon> I don;t think it makes sense to torture the device anymore than that :)
<sicelo> fmg the exorcist :-p
alex1216 has quit [Ping timeout: 252 seconds]
alex1216 has joined #maemo-leste
inky_ has joined #maemo-leste
<Wizzup> freemangordon: I had the crash with 32MB almost right after boot
<Wizzup> freemangordon: well, we still don't want X to crash if it runs out of vram
<freemangordon> Wizzup: agree (crash), but why it is not crashing for me?
<freemangordon> Wizzup: hmm compaction is disabled in the kernel you use, right?
xmn has joined #maemo-leste
<Wizzup> freemangordon: yes
<freemangordon> that might explain it
<Wizzup> maybe try to disable it
<Wizzup> we don't want it on
<freemangordon> yes, but who is going to compact CMA?
<freemangordon> but ok
<Wizzup> this kernel feature is new
<Wizzup> like 5.9 new or something
<Wizzup> clearly it worked before as well
<freemangordon> did it? I remember having hard times allocating CMA memory back then
<freemangordon> to the point I was fixing some drivers to have private CMA pool
<freemangordon> omapfb especially ;)
<freemangordon> Wizzup: also, what do you think is the correct way to handle vram OOM?
<freemangordon> shall we fix the kernel to pass __GFP_NOFAIL (or whatever the flag is)?
<freemangordon> kernel == omapdrm
<freemangordon> Wizzup: it is CONFIG_COMPACTION, right?
<Wizzup> freemangordon: yes
<freemangordon> I don't think we can disable that
<Wizzup> freemangordon: maybe killing the X window
<freemangordon> we cannot disable compaction, IIUC without it there is no way CMA to work
<Wizzup> it is new since 5.9
<Wizzup> so unless CMA never worked
<Wizzup> let me re-check
<freemangordon> found in Linux kernels: 3.7–3.19, 4.0–4.20, 5.0–5.15, 5.16-rc+HEAD
<Wizzup> freemangordon: maybe we enable it but revert facdaa917c4d5a376d09d25865f5a863f906234a
<freemangordon> I see
<freemangordon> lemme read that huge commi message
<Wizzup> freemangordon: no nee
<Wizzup> tl;dr is the guy measured some jvm improvements when he wakes up the system twice a second
<Wizzup> and he's ignored all our of emails so far
<Wizzup> or might be on a very long vacation
<Wizzup> this kills off mode
<Wizzup> and also is a pm nightmare
<Wizzup> the commit doesn't provide a way to stop the wake ups or even tweak the interval
<Wizzup> freemangordon: I'll revert that commit and re-enable the config
<Wizzup> and test
<freemangordon> Wizzup: just re-enable compaction and test
<freemangordon> to see if this is the one that leads to almost instant crashes on you device
<freemangordon> we'll think about PM if we know this is the problematic feature
<Wizzup> freemangordon: no, I'm going to revert that commit in any case
<Wizzup> we don't want it
<Wizzup> and I already reverted it anyway
<freemangordon> Wizzup: wait a second
<freemangordon> ah, ok :)
<freemangordon> wouldn;t it be easier to just replace HPAGE_FRAG_CHECK_INTERVAL_MSEC with some tunable?
<freemangordon> like 30s or something
<freemangordon> as this looks like a useful feature to me
<Wizzup> maybe, but they did not respond to any of my emails so I'm not particularly interested in working with them
<freemangordon> am I in CC? I think I saw 2 mails so far?
<freemangordon> I'll ping tomorrow
<freemangordon> we may ask tmlind to pester them too
<freemangordon> also, gta04 guys should be bitten by that one too
<freemangordon> basically, this is every baterry-operated device
<freemangordon> *battery
<freemangordon> Wizzup: how often is n900 woken-up without this?
<freemangordon> who the hell thought that "static const int HPAGE_FRAG_CHECK_INTERVAL_MSEC = 500;" is a good idea?
<Wizzup> freemangordon: not very often at all wrt wakeup
<Wizzup> freemangordon: tmlind also asked
<freemangordon> yeah, I know
<Wizzup> freemangordon: like less than 0.5 wakeups/s
<Wizzup> when I did some measurements
<Wizzup> sometimes way less because it stays in off mode for 30+ seconds
<freemangordon> ok, so waking up once every 30 seconds should not affect PM, right?
<freemangordon> but yeah, maybe we don;t really need that
<freemangordon> so, setting the tunable to 0 shall disable that feature, iiuc
<freemangordon> but right, lets simply revert until we have a better solution
<Wizzup> freemangordon: no, setting that via sysctl does not stop wakeups
<Wizzup> freemangordon: I treid my hand at reverting it, if this doesn't work I'll try to use it as is and then see if the bug still occurs
<freemangordon> yes, I see that setting it to 0 does not stop wakeups, I meant that setting ti to zero should stop wakeups :)
<freemangordon> sorry for not being clear
<freemangordon> the patch to stop wakeups for 0 seems like one-liner though
<Wizzup> maybe
<Wizzup> don't think it will be a one liner since you need to change the interval probably disable the old timer
<Wizzup> but fwiw yes, I don't see crashes now
<freemangordon> good
<Wizzup> so I suggest we do a careful revert of that commit
<Wizzup> (it conflicts in ~6 places)
<Wizzup> and also another commit uses that sysctl
<Wizzup> either that or we really up that interval value
<Wizzup> but I think really upping that value probably defeats the point in the measurements this guy did
<freemangordon> I think it is easier to just increase the wakeup interval to 60 seconds or something
<Wizzup> k
<Wizzup> I'll do that and try
<freemangordon> ttyl
<Wizzup> I'll make it two mins
<freemangordon> ok
<Wizzup> btw I still don't see like 40fps I think
<Wizzup> but I will try again once this new kernel hits
<Wizzup> maybe cma makes a diff
<Wizzup> err compaction
<Wizzup> freemangordon: ok so with these patches I will start with omap-linux
<Wizzup> agreed?
<Wizzup> freemangordon: I pushed to wip/n900/maemo-5.15-cleaned-up and confirmed that with much higher interval we are ok with off mode
sicelo has quit [Quit: Bye!]
alex1216 has quit [Quit: WeeChat 2.3]
sicelo has joined #maemo-leste
sicelo has joined #maemo-leste
sicelo has quit [Changing host]
<freemangordon> Wizzup: yep, I am fine. I will have to create formal patches in xorg omap and linux trees
<freemangordon> but not now
Blikje has joined #maemo-leste
dreamer has joined #maemo-leste
dreamer has quit [Remote host closed the connection]
<Wizzup> freemangordon: sure
dreamer has joined #maemo-leste
avoidr has quit [Quit: leaving]
avoidr has joined #maemo-leste
<Wizzup> ,3ot@(none):/# grep ^core_pwrdm /sys/kernel/debug/pm_debug/count | cut -d',' -f2,
<Wizzup> OFF:351,RET:7
<Wizzup> root@(none):/# uptime 05:35:42 up 3:35, 0 users, load average: 0.00, 0.00, 0.00
<Wizzup> not bad, right?
<Wizzup> (that's with just busybox sh)
<lel> James-Hanson opened an issue: https://github.com/maemo-leste/bugtracker/issues/599 (Hildon fails to load theme on newer Droid 4 images)