slep has quit [Remote host closed the connection]
<kona> hrm, and how to get like | and <> on the slide out keyboard in leste?
<kona> i tried touching the blue arrow and the ctrl key but that doesnt seem to do it maybe im doing it wrong https://leste.maemo.org/HowTo#How_do_I_show_the_special_keys_virtual_keyboard.3F_2
Wikiwide has quit [Ping timeout: 265 seconds]
lexik has quit [Ping timeout: 252 seconds]
lexik has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
joerg has quit [Ping timeout: 265 seconds]
joerg has joined #maemo-leste
SystemError has joined #maemo-leste
Oksana has joined #maemo-leste
Oksana has quit [Read error: Connection reset by peer]
Wikiwide has joined #maemo-leste
joerg has quit [Ping timeout: 244 seconds]
Daanct12 has joined #maemo-leste
joerg has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
SystemError has joined #maemo-leste
KREYREN has joined #maemo-leste
joerg has quit [Ping timeout: 248 seconds]
joerg has joined #maemo-leste
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
moparisthebest has quit [Ping timeout: 265 seconds]
SystemError has quit [Remote host closed the connection]
Pali has joined #maemo-leste
Livio has joined #maemo-leste
moparisthebest has joined #maemo-leste
akossh has joined #maemo-leste
akossh has quit [Ping timeout: 265 seconds]
Kryder has quit [Ping timeout: 248 seconds]
Kryder has joined #maemo-leste
Kryder has quit [Ping timeout: 245 seconds]
akossh has joined #maemo-leste
Kryder has joined #maemo-leste
akossh has quit [Ping timeout: 248 seconds]
akossh has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11> here are the very last msgs from boot log before the freeze:
<arno11> then, the next msg is related to the next boot
slep has joined #maemo-leste
<Wizzup> there might be more messages that do not get logged
<arno11> yes probably
<arno11> just before the last msgs, there is also iphbd starting
<arno11> anyway we must check swap stuff
<arno11> *first
uvos__ has quit [Remote host closed the connection]
pere has joined #maemo-leste
pere has quit [Ping timeout: 276 seconds]
Livio has quit [Ping timeout: 252 seconds]
arno11 has left #maemo-leste [#maemo-leste]
SystemError has joined #maemo-leste
Daanct12 has quit [Quit: WeeChat 4.3.5]
akossh has quit [Ping timeout: 265 seconds]
SystemError has quit [Ping timeout: 260 seconds]
SystemError has joined #maemo-leste
akossh has joined #maemo-leste
KREYREN has quit [Ping timeout: 260 seconds]
arno11 has joined #maemo-leste
<arno11> sicelo: Wizzup: it seems i'm able to boot fine now
<arno11> with last upgrade, i just removed pin entry and modest on boot
<arno11> why modest: just because i tried to boot with overclock earlier and i noticed that modest used lot of ressources during H-D loading
<arno11> and why overclock? : this way i'm able to run top/htop before the freeze
<arno11> and swap seems activated for a while (already 60MB used)
<sicelo> what did you modify to remove modest from boo
<sicelo> *boot
<arno11> i just moved /usr/bin/modest and modest.launch to /home temporary
<arno11> if it doesn't work for you, the only diff remaining with my install is the no blur transitions file.
pere has joined #maemo-leste
<arno11> Wizzup: when you have time, could you plz check if sysctl vm.page-cluster=8 on your n900 ?
<arno11> (just to check if vm custom stuff still works on boot)
SystemError has quit [Remote host closed the connection]
arno11 has left #maemo-leste [#maemo-leste]
SystemError has joined #maemo-leste
<Wizzup> arno11: what should I check exactly?
<kona> Wizzup: arno isn't here
arno11 has joined #maemo-leste
<kona> but i think they wanted to know if vm.page-cluster is set to 8
<arno11> yes exactly
<arno11> :)
<kona> i installed the 0804 image yesterday and it says 8 for me
<arno11> ah ok thanks
<arno11> so that's ok
<arno11> kona: and you're able to boot fine ? no freeze ?
<kona> i tried holding the blue button and ctrl on the hardware keyboard to bring up the special keys virtual kbd but i must not be doing it right because no dialogue.
<kona> i had one freeze or something that looked like a freeze.
<kona> right after activating zramtools
<kona> i.e. sudo apt install zram-tools && sudo reboot
<arno11> you should not activate zram stuff imo
<kona> it booted and showed the "welcome to maemo" but nothing was clickable and the power button didn't seem to do anything when held 10 seconds, so i removed the battery. put battery in, and it booted.
<kona> i also had a core from X
<kona> well, Xorg, i guess.
<arno11> ok yep
<arno11> the core from x is 'normal' lol
<kona> if it happens again, do you want the core?
<arno11> nope :) i just want to know if there is no freeze on boot without zram
<kona> ok, is there an easy way to disable zram?
<arno11> *on your device
<arno11> it is not activated by default
<kona> it isn't by default, but i installed zramtools and now it is.
<arno11> argh
<kona> /dev/zram0 partition 118.4M 113.4M 100
<kona> i can re-image, haven't really done much set up yet,.
<arno11> ok, maybe better, indeed
<arno11> bbiab
<kona> cool
<freemangordon> ok, my leste n900 hangs soon after h-d is started
<freemangordon> hard to say why, but it really seems OOM
<arno11> kona: btw for special char, you should click on blue arrow and then immediately on Ctrl
<arno11> freemangordon: ah
<freemangordon> so, 6.6 is really not ready for stable
<arno11> agree
<freemangordon> and we shall find why emmc swap does not work
<freemangordon> well, "does not work properly'
<arno11> yep
<freemangordon> now I removed SIM, to see if it make any difference
<arno11> ok, maybe we should check if every kernel commits are ok
<arno11> i removed modest on boot, which was using lot of ressources during H-D loading and was able to reboot fine
<Wizzup> freemangordon: emmc swa, not working is not the cause of the hang
<freemangordon> Wizzup: yes, I know
<Wizzup> also sd card swap seems genuinelly better
<Wizzup> it's faster than ever for me, my n900
<freemangordon> seems /swap is not activated early enough
<Wizzup> could be, not too hard to solve/identify
KREYREN has joined #maemo-leste
<Wizzup> I just didn't look yet
<freemangordon> hmm, seems like SGX lock, not OOM
<freemangordon> but yesterday it was working fine
<Wizzup> serial would tell
<freemangordon> I don;t have
<Wizzup> kinda sucks that only I have serial
<Wizzup> lol
<freemangordon> yeah
<freemangordon> lemme see if there is anything in syslog
<Wizzup> I can hook it up tonight or tomorrow
<freemangordon> no, it is not the swap
<freemangordon> I see "swap activated" message
<arno11> i bet on SGX
<arno11> i see swap using 60MB just before the freeze btw
<freemangordon> but why would SGX start freezing?
<arno11> iirc there are few changes in 6.6
<freemangordon> on d4 there is no issue
<freemangordon> ok, no idea what's going on, but yesterday it was booting fine
<freemangordon> hmm, the last I see is "WAKELINES TEST OK"
KREYREN has quit [Remote host closed the connection]
<freemangordon> hmm, no
<freemangordon> there is more
KREYREN has joined #maemo-leste
<kona> arno11: n900 seems to maybe be wedged on first boot
<kona> oh, yeah. hardware watchdog just reset it.
<freemangordon> Wizzup: yes, please, I don;t think I will be able to fix that without help
<kona> arno11: i've got it booted under freemantle presently in case you want me to retrieve any files.
<freemangordon> hmm, after removing SIM it boots
<Wizzup> from what I could tell the freeze was random for me, with or without sim
<arno11> same for me, totally random
<Wizzup> ok, tomorrow I will do the serial unit tests
<kona> i have no sim
<kona> just 512GB EVO Select TF card
<arno11> kona: ok
KREYREN has quit [Ping timeout: 260 seconds]
<kona> 2nd boot frozen too :O
arno11 has left #maemo-leste [#maemo-leste]
arno11 has joined #maemo-leste
<arno11> hm, weird, but could you try to reboot without modest guys ? 3rd reboot wihout issue
<arno11> (usually not possible)
<freemangordon> arno11: please...
<freemangordon> modest cannot hang the device
<arno11> it uses 100% cpu for a long time while HD is loading...
<freemangordon> so?
<freemangordon> that should not kause device hang
<freemangordon> *cause
<arno11> it's enough for freezing the device for 1 min (like trackers can do)
<freemangordon> no, I waited here at least 5 minutes
<freemangordon> also, that should happen *every* time, not sometimes
<arno11> yes !
<freemangordon> but it does not happen every time
<arno11> indeed
<freemangordon> trust me, this is not modest
<freemangordon> with 6.1 modest was using the same CPU, no?
<arno11> i'm not saying that's modest directly but it didn't use so much ressources previously iirc
uvos has joined #maemo-leste
<freemangordon> modest has not been changed for at least an year
<arno11> 2 years
<arno11> in fact
<freemangordon> so, if kernel upgrade is causing userspace to misbehave, I would say this is kernel issue, not userspace
<arno11> makes sense
<freemangordon> so, please, do not send PR to disable modest on n900 :)
wanderin900g has joined #maemo-leste
<arno11> :P
<freemangordon> lets just wait Wizzup to provide setial console output
<freemangordon> *serial
<arno11> yep
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 272 seconds]
wanderin900g has quit [Remote host closed the connection]
Juest has quit []
Juest has joined #maemo-leste
SystemError has quit [Remote host closed the connection]
<uvos> oom can easly hang the device permanently
<uvos> the kernel is _terrible_ in handling oom, allways has been
<freemangordon> uvos: but swap is enabled
<freemangordon> it is clearly visible in the logs
<uvos> how big is swap?
<freemangordon> 1G
<freemangordon> GiB
<uvos> hm ok
<arno11> i tried with smaller swap, same issue btw
<arno11> and even if there is
<arno11> oops
<freemangordon> 6.1 with smaller swap had no issues
<uvos> i wonder if we can run out of pined ram
SystemError has joined #maemo-leste
<freemangordon> I doubt, when device boots normally, there is about 100MiB free RAM
<freemangordon> and 30-40MiB swap used
<freemangordon> so I would bet on kernel oops/SGX freeze rather than on OOM
<uvos> sgx is obv pretty strange as d4 is perfetcly happy
<Wizzup> not the same hw
<uvos> i dont think there should be too manny code paths different there
<uvos> Wizzup: yeah but its very close
<Wizzup> in any case I'll just attach serial and hopefully we won't have to hypothesis
<Wizzup> hypothesize
SystemError has quit [Ping timeout: 260 seconds]
SystemError has joined #maemo-leste
Pali has quit [Quit: Pali]
d4dsc has left #maemo-leste [#maemo-leste]
uvos has quit [Remote host closed the connection]
arno11 has left #maemo-leste [#maemo-leste]
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
akossh has quit [Quit: Leaving.]