libera/#maemo-leste/ Tuesday, 2021-11-30

uvosWizzup: here are the signalmaps for xt860 and xt875 parsed from dtb:01:10
uvoshttp://uvos.xyz/maserati/stockinfo/signalmaps/01:11
uvosunfortionaly for you the modem wakeup gpio mdm6600_usb_rwkup is not in the xt860 signalmap01:12
uvosthats a bit perplexing01:12
uvosthe other modem gpios are the same01:15
Wizzupuvos: thanks!01:24
Wizzupa lot of them look quite similar01:30
Wizzupto be expected of course01:30
Wizzupuvos: I don't think the resets happen so often that it we should not move the kernel to -devel, what do you think14:13
Wizzupfreemangordon: do you need me to keep my droid on 1.9 ddk any longer or shall I migrate it?14:13
freemangordonWizzup: I was just thinking about if you can gather any more useful info14:15
freemangordonbtw, with ddk 1.9, do you see the same tearing as win 1.17?14:16
freemangordonit is easily visible in portrait14:16
freemangordons/win/with14:17
Wizzuplet me check14:24
WizzupI don't think I see tearing with 1.17 in portrait mode14:25
Wizzupat least not when scrolling h-d14:25
Wizzupbut I didn't move to triple buffering yet14:25
Wizzupfreemangordon: ^14:26
uvosthere is tearing in 1.1714:27
uvosits extreamly obvious14:27
uvosits just the other way than you expect14:27
uvosbecause the display is scanned from left to right14:27
uvosWizzup: i think moveing it to devel is fine14:28
uvosdevel is not stable by definition14:29
Wizzupuvos: I only see stutters14:29
Wizzupno tearing14:29
WizzupI still have this:14:30
Wizzup# cat /etc/powervr.d/hildon-desktop.ini14:30
Wizzup[hildon-desktop]14:30
WizzupWSEGL_UseHWSync=014:30
Wizzup(probably not relevant, but eh)14:30
uvosi have that too14:32
uvosWizzup: http://uvos.xyz/maserati/tearingBackground.png14:33
uvosset that as your background14:33
uvosif you dont see tearing then (in portrait mode)  ill belive you :P14:33
bencoh:)14:34
Wizzupyeah ok there is some14:35
WizzupI guess I should try to set it on 1.19 as well then14:35
Wizzupfreemangordon: yes I also see tearing on 1.914:37
Wizzupuvos: did you try to run cloudgps btw?15:13
uvosWizzup: no15:44
uvosi wanted to15:45
uvosbut could not install it15:45
Wizzupshould be in the repo now15:46
Wizzuphttps://twitter.com/maemoleste/status/1465697460043464707 :)16:01
tmlind_nice :)16:09
tmlind_Wizzup: did you get the tsc2005 idled? i'm kind of behind on mails and irc..16:10
Wasmachineman_NLwhat is this I heard about a Maemo-Leste IRC :^)?16:10
Wizzuptmlind_: I ported it to the pm runtime framework, but it doesn't idle yet16:11
tmlind_ok. also, there should have been some better infrastructure merged to the input subsystem for idling devices earlier this year, sorry don't know the details, just recall seeing something about it16:11
Wizzuptmlind_: I'm not any further than what I wrote in my email, wondering if I need to look at suspending the irq or something16:11
uvostmlind_: the problem isent ideling the interface persay16:12
Wizzuptmlind_: the other problem I ran into with regards to idle tests (I have a list on the github issue) is that the n900 panics and resets quite often (like the boot problem)16:12
WizzupWasmachineman_NL: yes, we're all here :)16:12
tmlind_Wizzup: ok weird16:12
uvostmlind_: the stuff merged was about force ideling interfaces iirc16:12
uvostmlind_: its about it blocking omap idle while not even open16:12
uvosie just probed16:12
Wasmachineman_NLWizzup even on stock Maemo my N900 crashes and reboots every once in a while lol16:12
tmlind_uvos: ok, do you have the commit id for that patch?16:13
Wizzupthis is the tsc2005 one https://github.com/maemo-leste/droid4-linux/commit/d43f08d6b99d142a28a3dd97481ce3adec0e763816:13
uvostmlind_: not off hand16:13
uvostmlind_: i also just remember the discussion on the ml not if it was merged even16:13
WizzupWasmachineman_NL: mine doesn't really, after a long time of use, but I hope I can switch to leste in 2021q116:14
Wasmachineman_NLWizzup i'm impatiently awaiting the Pro1 M-L port16:14
tmlind_uvos: ok16:14
Wasmachineman_NLuntil then, still using my ye olde N900 I bought in early 201516:15
Wasmachineman_NLholy shit imagine this, 2015 is almost 7 years ago16:15
WizzupWasmachineman_NL: that's probably some time out still, we're focussing on droid4/n900/droid3/bionic atm16:15
Wasmachineman_NLI gathered16:15
Wizzupparazyd has my fx tec pro16:15
Wasmachineman_NLI was one of the first people to get a Pro1 and I hate it16:15
Wasmachineman_NLmostly because Android16:16
Wasmachineman_NLFUCK android.16:16
Wizzuptmlind_: in any case I think we're pretty close to idling on n900, the omap3-isp seems to block idle as well mostly16:16
Wizzuphere's the list https://github.com/maemo-leste/bugtracker/issues/545#issuecomment-98045878416:16
Wasmachineman_NL(says the one who's had Android running on his Xperia X1 in 2010 lol)16:16
Wizzuptmlind_: if I blacklist omap3-isp, then the n900 panics usually right after everything is loaded/started16:17
Wasmachineman_NLomap3-isp sounds like something for the image processing sensor16:17
Wizzup(and the panic is in the idle code somewhere, same as the random boot problem)16:17
WizzupWasmachineman_NL: yes, iiuc16:17
uvoshavin omap3-isp loaded is pretty optimistic no?16:17
Wasmachineman_NLwhy is the ISP being used in idle anyway?16:17
uvoswhat do we need it for16:17
Wizzupuvos: it's just in the defconfig I think16:17
WizzupWasmachineman_NL: well it's complicated, we don't use it now, but the module is loaded, and when it is loaded it should not block phone idle / use power16:18
tmlind_Wizzup: if isp is really needed, this might be related to the beagleboard timer issue16:18
Wasmachineman_NLWizzup so when it's loaded it causes excessive idle power use16:19
Wasmachineman_NLgot it.16:19
Wasmachineman_NLand when it's unloaded it freaks out the OS causing it to crash and burn16:19
Wasmachineman_NLor rather, reboot16:19
Wizzuptmlind_: how quickly does this manifest on the beagleboard?16:19
Wasmachineman_NL?16:19
tmlind_Wizzup: well beagleboard did not boot, sounds like this is something else actually16:19
WizzupWasmachineman_NL: there's various problems with the latest kernel for the n900 atm, this is just one of them16:19
Wizzuptmlind_: yes, the idle oops is the same as during boot16:20
Wizzupbut if I don't block omap3isp later on, the system doesn't panic, but it also doesn't idle, so yeah...16:20
Wasmachineman_NLdoes liberachat webIRC support custom themes?16:20
Wizzup(it might still crash on boot)16:20
WizzupWasmachineman_NL: sorry, don't know, you might want to get a better irc client anyway, I just linked it from the tweet for people to find us easily16:21
Wasmachineman_NLthat's where I came from :^)16:21
WizzupI know16:21
Wasmachineman_NLmight break out one of my Precisions and shitpost- I mean IRC from there16:21
tmlind_Wizzup: so do you need to do anything special on n900 to make it oops? or just let it sit idle?16:22
Wizzuptmlind_: for me just booting with the defconfig makes it oops every now and then. I can plug in my serial now and see how quickly/often I can make it crash16:24
WizzupIt's not entirely reproducible, but happens frequently enough for me16:24
tmlind_Wizzup: ok i'll leave 5.15.2 kernel running idle for a while, i don't really have any modules loaded though16:24
WizzupI don't think that causes trouble for me, oddly enough16:25
WizzupI also have had that idle for a while in /bin/bash with just panel loaded16:25
Wizzup(and off mode enabled)16:25
Wizzupthe emails in "Oops while booting 5.15.2 on Nokia N900" contain the traces, if they are of any us16:26
Wizzupuse*16:26
tmlind_yeah ok16:26
tmlind_freemangordon: no idea about the 6ms flip :)16:26
Wizzupon the upside the droid3 hangs (that I had all the time on 5.11) are gone mostly it seems16:27
Wasmachineman_NLbit of a stupid question: are Kernel-Power or overclocking a thing with Maemo-Leste?16:29
uvosi run the droid at 1.4GHz16:30
uvosbeond that no not really16:30
Wizzupuvos: jesus16:30
Wizzup:D16:30
WizzupWasmachineman_NL: power kernel is not a thing, mainline linux is more power than power kernel ever was16:30
WizzupWasmachineman_NL: currently we are trying to make everything work reliably, like the phone not resetting at night or in your pocket, once that is all going well, someone could look at overclocking, but not currently16:31
Wasmachineman_NLinteresting.16:31
uvosi also ran the memory card interface at 50MB/s for a while - need to make that a nicer patch one of these days16:31
tmlind_uvos: if you make a patch, please do it for the sdhci-omap.c, just update the dts to use sdhci compatible for your mmc to test16:34
tmlind_Wizzup: the omap3_l3_app_irq means there was some invalid access somewhere, in this case it looks like the read instruction was not valid?16:35
tmlind_that sounds like memory problem.. maybe run memtester on that device?16:36
tmlind_uvos: sdhci-omap assuming you're already on v5.16-rc :)16:36
Wizzuptmlind_: I think freemangordon had the same problems on his n900 wrt it not always booting, but he doesn't have the serial to confirm the problem16:37
Wizzuphttps://dpaste.com/8H8XKFN7G this one just happened while booting16:39
Wizzupsorry, raw here: https://dpaste.com/8H8XKFN7G.txt16:40
Wizzupthe 5.1 kernel does not suffer from this problem AFAICT16:40
Wizzupstill, I can run memtester if you'd like16:41
Wizzup(looks like the same as in my first email)16:42
Wizzuphappened 1 out of 4 times atm16:43
WizzupI assume we're not missing some errata in the config...16:43
Wizzupwe have ARM_ERRATA_430973 in 5.15, but not in 5.1, weird..16:45
tmlind_yeah a missing errata handling could explain something like that16:46
tmlind_or applying a wrong errata too i guess16:47
Wizzupa bunch are enabled looking at .config https://dpaste.com/8TPGCNKLA.txt - but this just omap2plus_defconfig16:51
Wizzupbtw: 5.1 did have 430973 applied, but only that one16:51
WizzupI guess I could disable all except 430973 but that might give problems for the droid4 and others, but just to see what happens16:55
WizzupI'm a bit doubtful this is the problem though, but can try16:55
tmlind_Wizzup: see also this old thread: https://linux-arm-kernel.infradead.narkive.com/Esh7UIgf/arm-errata-430973-on-multi-platform-kernels-was-omap3-n900-add-microphone-bias-voltages#post216:59
Wizzuptmlind_: so we have this in .config of the kernel that has this problem17:00
Wizzupbut I guess u-boot also has it, but that should not be a problem according to that thread17:01
tmlind_i forgot the details, but i thought we got it all fixed up earlier17:01
Wizzupright, it looks like both 5.1 and 5.15 have this applied and 5.1 doesn't seem to have the problem, but our build of that kernel *only* has 430973 applied, our 5.15 has 7 erratas applied, the majority for A9 and A15 and one for an older model, and just one for A817:02
Wizzupwhen I say applied I mean that it's in the .config as =y17:03
Wizzupso I can remove them from the .config and rebuild, but I would be a bit surprised if the errata's for A9 are applied on A8 cpu17:03
tmlind_yeah a9 errata are not applied for a817:04
tmlind_Wizzup: so does your old working kernel say anything about the BPIALL workaround?17:06
WizzupI tried to grep for that (BPIALL) and didn't find anything, so I'm not sure which commit or config you refer to17:07
tmlind_well i wonder if all the spectre-v2 patches somehow made the issue reappear17:09
Wizzupah17:09
Wizzup5.1 and 5.15 both do seem to have CPU_SPECTRE=y in their .config, but I don't think that enables spectre workarounds per se17:10
tmlind_yeah those patches are in v5.1 already17:11
tmlind_for reference, here's a better link to the old arm errata thread: https://lore.kernel.org/linux-omap/20150403183942.GV10805@atomide.com/17:16
tmlind_bbl17:17
Wizzupbye17:17
Wizzuphmm I wonder if we need HSI_CHAR in .config to fix the n900 dma problem in nokia-modem17:18
* Wizzup tries17:20
WizzupSo the 5.1 kernel is quite different in options, it's also build as thumb2 kernel whereas I don't think we build our 5.15 as thumb kernel17:23
Wizzupit even had SMP disabled17:24
bencohSMP shouldn't affect n900 much17:25
bencohwell, it might, but ...17:25
Wizzupprobably not, just looking at some obvious differences17:25
bencohthumb2 on the other hand ....17:25
Wizzupyeah17:25
bencohthere were two thumb2-related (iirc) errata for n90017:26
bencohand I think one of the fix belonged to kernelspace17:26
bencohso you should probably check it's enabled17:26
bencohah right, maemo.org is down :(17:27
WizzupI think we went over the erratas earlier, but maybe I missed something17:27
bencohjust in case: https://webcache.googleusercontent.com/search?q=cache:gDfkAwFC5P8J:https://wiki.maemo.org/Community_SSU/Thumb17:28
WizzupI think the latter (65 something) is worked around in gcc/ld etc, so we should have that fixed in all modern userspace17:35
bencohindeed17:35
Wizzupwhat I can try to do is pick all of spinals patches and config changes to 5.1 and apply them to 5.1517:35
bencohthe question is whether 5.15 includes a fix for the first one17:36
bencohand whether it is enabled17:36
Wizzupyes to both @ 43097317:36
bencohah, alright :)17:36
Wizzup5.1 also has SLUB as allocator, not SLAB17:38
Wizzupto bad there's such a big difference hehe17:38
Wizzupsicelo: do you want to try apt dist-upgrade on beowulf-experimental ?17:42
Wizzupsicelo: hm, wait, I am not sure if the old packages are being removed now as well, I'll have to check that17:43
* freemangordon wonders what has happened with Tomi17:44
Wizzupsicelo: yeah hold off for now17:45
Wizzupsicelo: well whatever I did, I broke it atm, so I'll need to revert some stuff17:58
WizzupI don't know why -experimental doesn't want to dist-upgrade to new pvr anymore, sigh19:21
_inkyi wish i could buy every maemo leste a pinephone. not only because i own one, seriously. but because pinephone is a device that attracts people to mobile linux. and maemo could have more share, therefore, more developers.22:29
_inkyi like hildon desktop so much. it is so underappreciated.22:29
_inkyit is very useful when comparing to kde plasma or phosh. very.22:29
Wizzupmhm22:31
Wizzupwe'll get there.22:31
Wizzupthe keyboard addon will help loads I think22:32
uvosbut, but we like our strange, rare, near obsolete nokia/motorola devices22:32
Wizzupwhy not both22:34
uvoswell i dont disagree that we should try and have the pp be supported as a first class citizen, not sure how to improve the situation tho22:36
Wizzupwhat situation?22:36
WizzupI spoke with tl lim in the very early days and he was up for doing a run with leste as well, but especially then we weren't ready22:36
uvospp lagging in implemented features and stability compeard to mapphones.22:37
Wizzupeither someone will come along, or we'll do it when mapphone is usable22:43
uvosspeaking of lagging in features22:44
uvoshttps://github.com/maemo-leste/leste-config/pull/26 <-> https://github.com/maemo-leste/libmatchbox2/pull/8 these 2 want review22:45
uvosi accidentaly "updated" h-d today and now gnome-contacts is broken again ;(22:46
uvosWizzup: btw what kind of power managament are you haveing on d4 atm with 5.1522:48
uvosim having a hard time getting under 200mW its probubly just something misbehaving on this unit as the bionic still idles fine at 90 ish or sometimes lower22:49
Wizzupuvos: I'd have to check but it seems not too bad really23:04
WizzupI think easily 20h with modem on23:04
Wizzupalso haven't seen a lot of resets now23:04
Wizzupuvos: check @ PRs, will try to check later tonight23:07

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