<tmlind_>
Wizzup: did you get the tsc2005 idled? i'm kind of behind on mails and irc..
Wasmachineman_NL has joined #maemo-leste
<Wasmachineman_NL>
what is this I heard about a Maemo-Leste IRC :^)?
<Wizzup>
tmlind_: I ported it to the pm runtime framework, but it doesn't idle yet
<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 it
<Wizzup>
tmlind_: I'm not any further than what I wrote in my email, wondering if I need to look at suspending the irq or something
<uvos>
tmlind_: the problem isent ideling the interface persay
<Wizzup>
tmlind_: 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)
<Wizzup>
Wasmachineman_NL: yes, we're all here :)
<tmlind_>
Wizzup: ok weird
<uvos>
tmlind_: the stuff merged was about force ideling interfaces iirc
<uvos>
tmlind_: its about it blocking omap idle while not even open
<uvos>
ie just probed
<Wasmachineman_NL>
Wizzup even on stock Maemo my N900 crashes and reboots every once in a while lol
<tmlind_>
uvos: ok, do you have the commit id for that patch?
<Wasmachineman_NL>
(says the one who's had Android running on his Xperia X1 in 2010 lol)
<Wizzup>
tmlind_: if I blacklist omap3-isp, then the n900 panics usually right after everything is loaded/started
<Wasmachineman_NL>
omap3-isp sounds like something for the image processing sensor
<Wizzup>
(and the panic is in the idle code somewhere, same as the random boot problem)
<Wizzup>
Wasmachineman_NL: yes, iiuc
<uvos>
havin omap3-isp loaded is pretty optimistic no?
<Wasmachineman_NL>
why is the ISP being used in idle anyway?
<uvos>
what do we need it for
<Wizzup>
uvos: it's just in the defconfig I think
<Wizzup>
Wasmachineman_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 power
<tmlind_>
Wizzup: if isp is really needed, this might be related to the beagleboard timer issue
<Wasmachineman_NL>
Wizzup so when it's loaded it causes excessive idle power use
<Wasmachineman_NL>
got it.
<Wasmachineman_NL>
and when it's unloaded it freaks out the OS causing it to crash and burn
<Wasmachineman_NL>
or rather, reboot
<Wizzup>
tmlind_: how quickly does this manifest on the beagleboard?
<Wasmachineman_NL>
?
<tmlind_>
Wizzup: well beagleboard did not boot, sounds like this is something else actually
<Wizzup>
Wasmachineman_NL: there's various problems with the latest kernel for the n900 atm, this is just one of them
<Wizzup>
tmlind_: yes, the idle oops is the same as during boot
<Wizzup>
but if I don't block omap3isp later on, the system doesn't panic, but it also doesn't idle, so yeah...
<Wasmachineman_NL>
does liberachat webIRC support custom themes?
<Wizzup>
(it might still crash on boot)
<Wizzup>
Wasmachineman_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 easily
<Wasmachineman_NL>
that's where I came from :^)
<Wizzup>
I know
<Wasmachineman_NL>
might break out one of my Precisions and shitpost- I mean IRC from there
<tmlind_>
Wizzup: so do you need to do anything special on n900 to make it oops? or just let it sit idle?
<Wizzup>
tmlind_: 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 crash
<Wizzup>
It's not entirely reproducible, but happens frequently enough for me
<tmlind_>
Wizzup: ok i'll leave 5.15.2 kernel running idle for a while, i don't really have any modules loaded though
<Wizzup>
I don't think that causes trouble for me, oddly enough
<Wizzup>
I also have had that idle for a while in /bin/bash with just panel loaded
<Wizzup>
(and off mode enabled)
<Wizzup>
the emails in "Oops while booting 5.15.2 on Nokia N900" contain the traces, if they are of any us
<Wizzup>
use*
<tmlind_>
yeah ok
<tmlind_>
freemangordon: no idea about the 6ms flip :)
<Wizzup>
on the upside the droid3 hangs (that I had all the time on 5.11) are gone mostly it seems
<Wasmachineman_NL>
bit of a stupid question: are Kernel-Power or overclocking a thing with Maemo-Leste?
<uvos>
i run the droid at 1.4GHz
<uvos>
beond that no not really
<Wizzup>
uvos: jesus
<Wizzup>
:D
<Wizzup>
Wasmachineman_NL: power kernel is not a thing, mainline linux is more power than power kernel ever was
<Wizzup>
Wasmachineman_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 currently
<Wasmachineman_NL>
interesting.
<uvos>
i also ran the memory card interface at 50MB/s for a while - need to make that a nicer patch one of these days
<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 test
<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?
<tmlind_>
that sounds like memory problem.. maybe run memtester on that device?
<tmlind_>
uvos: sdhci-omap assuming you're already on v5.16-rc :)
<Wizzup>
tmlind_: 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 problem
<Wizzup>
tmlind_: so we have this in .config of the kernel that has this problem
<Wizzup>
but I guess u-boot also has it, but that should not be a problem according to that thread
<tmlind_>
i forgot the details, but i thought we got it all fixed up earlier
<Wizzup>
right, 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 A8
<Wizzup>
when I say applied I mean that it's in the .config as =y
<Wizzup>
so 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 cpu
<tmlind_>
yeah a9 errata are not applied for a8
<tmlind_>
Wizzup: so does your old working kernel say anything about the BPIALL workaround?
<Wizzup>
I tried to grep for that (BPIALL) and didn't find anything, so I'm not sure which commit or config you refer to
<tmlind_>
well i wonder if all the spectre-v2 patches somehow made the issue reappear
<Wizzup>
ah
<Wizzup>
5.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 se
<Wizzup>
I think the latter (65 something) is worked around in gcc/ld etc, so we should have that fixed in all modern userspace
<bencoh>
indeed
<Wizzup>
what I can try to do is pick all of spinals patches and config changes to 5.1 and apply them to 5.15
<bencoh>
the question is whether 5.15 includes a fix for the first one
<bencoh>
and whether it is enabled
<Wizzup>
yes to both @ 430973
<bencoh>
ah, alright :)
<Wizzup>
5.1 also has SLUB as allocator, not SLAB
<Wizzup>
to bad there's such a big difference hehe
<Wizzup>
sicelo: do you want to try apt dist-upgrade on beowulf-experimental ?
mrtux0 has joined #maemo-leste
Armen8 has joined #maemo-leste
<Wizzup>
sicelo: hm, wait, I am not sure if the old packages are being removed now as well, I'll have to check that
dsc_ has quit [Ping timeout: 256 seconds]
avoidr has quit [Ping timeout: 256 seconds]
* freemangordon
wonders what has happened with Tomi
Armen has quit [Ping timeout: 256 seconds]
mrtux has quit [Ping timeout: 256 seconds]
mrtux0 is now known as mrtux
Armen8 is now known as Armen
<Wizzup>
sicelo: yeah hold off for now
dsc_ has joined #maemo-leste
avoidr has joined #maemo-leste
<Wizzup>
sicelo: well whatever I did, I broke it atm, so I'll need to revert some stuff
akossh has joined #maemo-leste
<Wizzup>
I don't know why -experimental doesn't want to dist-upgrade to new pvr anymore, sigh
inky_ has joined #maemo-leste
akossh has quit [Remote host closed the connection]
pere has quit [Ping timeout: 256 seconds]
<_inky>
i 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.
<_inky>
i like hildon desktop so much. it is so underappreciated.
<_inky>
it is very useful when comparing to kde plasma or phosh. very.
<Wizzup>
mhm
<Wizzup>
we'll get there.
<Wizzup>
the keyboard addon will help loads I think
<uvos>
but, but we like our strange, rare, near obsolete nokia/motorola devices
<Wizzup>
why not both
<uvos>
well 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 tho
<Wizzup>
what situation?
<Wizzup>
I 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 ready
<uvos>
pp lagging in implemented features and stability compeard to mapphones.
<Wizzup>
either someone will come along, or we'll do it when mapphone is usable
<uvos>
i accidentaly "updated" h-d today and now gnome-contacts is broken again ;(
Daanct12 has joined #maemo-leste
<uvos>
Wizzup: btw what kind of power managament are you haveing on d4 atm with 5.15
Danct12 has quit [Ping timeout: 264 seconds]
mardy has quit [Quit: WeeChat 2.8]
<uvos>
im 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 lower
<Wizzup>
uvos: I'd have to check but it seems not too bad really
<Wizzup>
I think easily 20h with modem on
<Wizzup>
also haven't seen a lot of resets now
<Wizzup>
uvos: check @ PRs, will try to check later tonight
pere has joined #maemo-leste
Wikiwide has joined #maemo-leste
xmn has joined #maemo-leste
Wikiwide has quit [Ping timeout: 256 seconds]
xmn has quit [Quit: ZZZzzz…]
Wikiwide_ has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
<uvos>
the bug why hildon scrolling is Y2038 bug :P
<uvos>
*why hildon scrolling is terrible
<uvos>
in the launcher
<uvos>
it takes the time of the last 3 events adds them together and shoves that into a time_t and then devides
<uvos>
to get the mean time
<uvos>
that dident even work in 2010
Wikiwide_ has quit [Remote host closed the connection]
Wikiwide_ has joined #maemo-leste
pere has joined #maemo-leste
Wikiwide_ has quit [Remote host closed the connection]