**** BEGIN LOGGING AT Sat Jul 08 03:00:01 2017
Jul 08 09:33:45 <sicelo> i have annoying random reboots on my n900. nothing useful shown by syslog
Jul 08 09:35:12 <L29Ah> overclocking?
Jul 08 09:35:29 <sicelo> what is a bit strange is that the device time gets reset, hinting at a loose battery. however i can confirm that the battery is sitting snug in it's place. also, the reboot takes place with the device untouched, laying on flat table
Jul 08 09:35:35 <sicelo> no overclocking
Jul 08 09:35:54 <KotCzarny> you've got a virus :P
Jul 08 09:36:11 <L29Ah> the time thing is very strange
Jul 08 09:36:27 <KotCzarny> yeah, it suggests loose power
Jul 08 09:36:33 <L29Ah> how frequently do you see the resets?
Jul 08 09:37:14 <sicelo> very randomly. few minutes ago it rebooted, as well as about 8 hours ago
Jul 08 09:37:58 <L29Ah> i'd start logging the battery voltage every second or so
Jul 08 09:39:31 <sicelo> will do, but i don't think it's a problem with the battery itself (besides being loose somehow if that's the case)
Jul 08 09:41:48 <sicelo> anyone knows what relationship, if any, exists between KP53 and 2.6.28.10-cssu3 kernels?
Jul 08 09:54:27 <L29Ah> does n900 support voice calls over 3g?
Jul 08 09:54:55 <buZz> yes
Jul 08 09:56:13 <sicelo> is there a phone that doesn't?
Jul 08 09:58:18 <buZz> nokia 3310
Jul 08 09:59:00 <L29Ah> i remember i had to switch networks manually to be able to make calls when i was in .ua
Jul 08 09:59:03 <sicelo> haha, should of said 'a phone with 3g that doesn't support voice calls over 3g
Jul 08 09:59:27 <L29Ah> maybe they've messed something up on their side
Jul 08 10:00:15 <sicelo> what could you do on 3G? just Internet?
Jul 08 10:01:07 <L29Ah> yes
Jul 08 10:02:25 <sicelo> yes most of the problem must been on your provider's side, although N900's modem is not necessairly the best around :(
Jul 08 10:03:13 <sicelo> i'm facing opposite problem L29Ah - serious internet issues on 3g, so much that i've disabled it completely now
Jul 08 10:03:57 <buZz> sicelo: oooooo ;)
Jul 08 10:03:59 <L29Ah> works like a charm for me atm
Jul 08 10:04:23 <sicelo> the operator is at fault because i get the same problem on a 3g stick, but N900 is worse. at least the dongle and SGS4 eventually get through
Jul 08 10:06:00 <buZz> i wonder if you could just block the nonfunctioning cell towers
Jul 08 10:06:10 <buZz> (what this all sounds like)
Jul 08 10:08:59 <sicelo> 3.5G works fine. 3G absolutely not. i don't think it's cell tower problem because it is the same whether i remain in the same place or go somewhere else
Jul 08 10:10:41 <sicelo> i guess they are oversubscribing their equipment capabilities
Jul 08 10:11:01 <sicelo> wild guess .. not sure if it would really cause the issue
Jul 08 13:19:24 <DocScrutinizer05> sicelo: there's no difference between 3.5G and 3G. 3.5G is just 3G with turbo engaged, much like EDGE for 2G makes it 2.5G
Jul 08 13:20:46 <sicelo> yes, i am aware of that.
Jul 08 13:20:58 <DocScrutinizer05> technically it's just a channel bundling, when the base station offers to the phone to use more channels in parallel
Jul 08 13:23:32 <sicelo> i wish i knew why exactly i have the problems i have ... but t's all going to just be conjecture unless i get a listening, interested ear at the ISP
Jul 08 13:24:01 <DocScrutinizer05> L29Ah: of course N900 can do 3G voice cals
Jul 08 13:24:22 <sicelo> thankfully 2.5G serves most of my needs well 90% of the time
Jul 08 13:24:50 <xes> ...but... since operators are removing 2g and 3g channels to install 4g devices... i would not expect much from edge and 3.5g
Jul 08 13:25:04 <L29Ah> btw how do i check out the modem status?
Jul 08 13:25:13 <DocScrutinizer05> well, depends on where you are
Jul 08 13:25:15 <sicelo> yes xes. sucks
Jul 08 13:25:18 <L29Ah> like the used modulation and signal levels
Jul 08 13:25:52 <DocScrutinizer05> then there's also coexistence of LTE with UMTS and GSM on same band afaik
Jul 08 13:26:32 <DocScrutinizer05> L29Ah: there's an app "network monitor" or sth
Jul 08 13:26:47 <DocScrutinizer05> as good as it gets regarding service data
Jul 08 13:26:48 <Sicelo009N> cellnet-info i think ..
Jul 08 13:28:11 <DocScrutinizer05> Sicelo009N: your reboot problem sounds scary
Jul 08 13:28:36 <DocScrutinizer05> did you check the reboot reason logs?
Jul 08 13:29:02 <DocScrutinizer05> also make sure df -h isn't critical
Jul 08 13:30:18 <sicelo> i have 60% free rootfs, and nothing specific in syslog
Jul 08 13:31:56 <sicelo> i do think somehow my battery contcts are at fault as that's the only thing explaining the time resets
Jul 08 13:32:26 <DocScrutinizer05> not syslog, those dsme logs
Jul 08 13:32:38 <sicelo> where can i get them
Jul 08 13:33:53 <Sicelo009N>  /proc/bootreason currently has '32wd to' - watchtdog .. no idea what was hung, if that's what it means
Jul 08 13:34:25 <DocScrutinizer05>  /var/lib/dsme/stats/lifeguard_restarts
Jul 08 13:35:00 <DocScrutinizer05> 32vd TimeOut, yes
Jul 08 13:35:14 <DocScrutinizer05> watchdog timeout
Jul 08 13:36:18 <DocScrutinizer05> http://paste.ubuntu.com/25046492  I should clear that file
Jul 08 13:36:29 <sicelo> 4 lines should be safe to paste, from my lifeguard_restarts
Jul 08 13:37:00 <Sicelo009N> /usr/bin/ohm-session-agent: 1
Jul 08 13:37:02 <Sicelo009N> /usr/bin/camera-ui: 1
Jul 08 13:37:02 <Sicelo009N> /usr/bin/syncd: 1
Jul 08 13:37:02 <Sicelo009N> /usr/bin/hildon-status-menu: 2
Jul 08 13:39:01 <DocScrutinizer05> you might want to run a htop sort:cpu% via ssh/WLAN, this will stall with most busy app on top on a reboot
Jul 08 13:42:02 <DocScrutinizer05> syslog might not even catch the culprit. decent dmesg --follow (plus a few other options for getting all messages) will do a better job prolly
Jul 08 13:42:22 <DocScrutinizer05> alas messybox dmesg is fubar, like everything messybox
Jul 08 13:43:24 <L29Ah> /usr/bin/camera-ui: 97
Jul 08 13:43:28 <L29Ah> hmm
Jul 08 13:43:34 <DocScrutinizer05> you also may want to check mtdoops
Jul 08 13:43:42 <L29Ah> /sbin/mce --force-syslog: 1
Jul 08 13:43:48 <L29Ah> i wonder what are those numbers
Jul 08 13:43:57 <DocScrutinizer05> number of reboots?
Jul 08 13:44:09 <sicelo> yes i thout about mtdoops .. no idea how to read the info there however
Jul 08 13:44:21 <L29Ah> how does it correspond reboots with concrete binaries?
Jul 08 13:44:25 <DocScrutinizer05> ~pkg
Jul 08 13:44:26 <infobot> pkg is probably http://maemo.org/packages/
Jul 08 13:44:50 <DocScrutinizer05> L29Ah: task that caused reboot I guess
Jul 08 13:45:01 <L29Ah> how can a task cause a reboot?
Jul 08 13:45:09 <DocScrutinizer05> via watchdog timeout?
Jul 08 13:45:28 <KotCzarny> hogging resources?
Jul 08 13:45:33 <DocScrutinizer05> when the task stalls (busyloops, hangs) in a kernel syscall
Jul 08 13:45:45 <DocScrutinizer05> or whatever
Jul 08 13:45:51 <DocScrutinizer05> not entirely sure
Jul 08 13:45:56 <DocScrutinizer05> never looked into details#
Jul 08 13:48:49 <DocScrutinizer05> http://maemo.org/packages/view/sp-oops-extract/
Jul 08 13:50:09 <DocScrutinizer05> sp-oops-extract /dev/mtd2
Jul 08 13:51:35 <Sicelo009N> installing. is output human readable?
Jul 08 13:52:51 <DocScrutinizer05> sort of
Jul 08 13:52:59 <DocScrutinizer05> don't ask me what's >>[ 7497.347198] Kernel panic - not syncing: Fatal exception<<
Jul 08 13:53:30 <DocScrutinizer05> http://paste.ubuntu.com/25046580
Jul 08 13:53:34 <Sicelo009N> haha, i have a couple of those lines
Jul 08 13:55:42 <L29Ah> You don't have permission to access /packages/view/sp-oops-extract/ on this server.
Jul 08 13:55:49 <DocScrutinizer05> also timestamps are not really useful
Jul 08 13:56:10 <Sicelo009N>  /dev/mtd2 survives flashing? i see mention of cutetube, which i haven't installed since my reflash
Jul 08 13:56:12 <DocScrutinizer05> err wut? blacklisted?
Jul 08 13:56:53 <DocScrutinizer05> dev/mtd{1,2} survive flashing, yes
Jul 08 13:57:09 <DocScrutinizer05> so does dev/mtd4
Jul 08 13:57:10 <sicelo> ok
Jul 08 13:57:13 <DocScrutinizer05> afaik
Jul 08 13:57:47 <DocScrutinizer05> dev/mtd0 survices normal falshing, not coldflashing
Jul 08 13:59:58 <DocScrutinizer05> dev/mtd4 initfs always bugged me due to its complete uselessness
Jul 08 14:00:53 <DocScrutinizer05> Pali: couldn't we patch 0xffff to concat dev/mtd4 into dev/mtd3 kernel, to make it twice as large?
Jul 08 14:01:18 <Pali> DocScrutinizer05: no
Jul 08 14:01:29 <Pali> partition layout is hardcoded in NOLO
Jul 08 14:01:39 <DocScrutinizer05> I *guess* kernel itself doesn't mind at all how long it is and if it extends over "partition" borders
Jul 08 14:01:51 <DocScrutinizer05> WAAAH kill NOLO!!!
Jul 08 14:02:11 <DocScrutinizer05> friggin pile of shit
Jul 08 14:02:14 <Pali> but... in CAL is stored partition layout too
Jul 08 14:02:22 <DocScrutinizer05> o.O oooooh
Jul 08 14:02:39 <Pali> and IIRC NOLO first use partition layout from CAL and then fallback to hardcoded values
Jul 08 14:02:47 <DocScrutinizer05> makes sense
Jul 08 14:02:54 <Pali> I used this "hack" when debugged in qemu
Jul 08 14:03:02 <DocScrutinizer05> do you know a keyword to search for in CAL?
Jul 08 14:03:15 <Pali> so I was able to put larger zImage into nand
Jul 08 14:03:26 <DocScrutinizer05> exactly my plan :-)
Jul 08 14:03:27 <Pali> problem is: format of partition layout is undocumented
Jul 08 14:03:36 <DocScrutinizer05> :-S
Jul 08 14:03:50 <Pali> nokia released only tool called "qflasher" which prepares MTD dump for qemu
Jul 08 14:03:58 <Pali> and fill it also with CAL data
Jul 08 14:04:07 <DocScrutinizer05> oooooh
Jul 08 14:04:09 <Pali> and one parameter for qflasher is size of each partition
Jul 08 14:04:20 <Pali> tool is of course closed, i386 only
Jul 08 14:04:28 <DocScrutinizer05> F U NOKIA!!!!
Jul 08 14:04:29 <Pali> and probably lost...
Jul 08 14:04:39 <Pali> somewhere I have copy on my hdd
Jul 08 14:04:41 <DocScrutinizer05> err lost?
Jul 08 14:04:46 <DocScrutinizer05> please share!
Jul 08 14:04:49 <Pali> not available on internet anymore
Jul 08 14:08:42 <DocScrutinizer05> http://wstaw.org/m/2017/07/08/plasma-desktopGy8317.png  ;-D
Jul 08 14:10:25 <xes> maybe qflasher is the same of meego? http://www.mmnt.net/db/0/0/sower.yandex.ru/mirrors/meego/releases/1.2.0/repos/non-oss/source
Jul 08 14:12:45 <xes> non-oss... ops
Jul 08 14:14:21 <DocScrutinizer05> http://maemo.cloud-7.de/maemo5/dirsnapshot2.png
Jul 08 14:16:14 <DocScrutinizer05> xes: well, it still has a src.rpm, which stalls so far for me on opening it
Jul 08 14:17:02 <DocScrutinizer05> URL: ftp://sower.yandex.ru/mirrors/meego/releases/1.2.0/repos/non-oss/source/qflasher-21-1.1.src.rpm  The requested operation could not be completed   Connection to Server Refused
Jul 08 14:17:58 <DocScrutinizer05> rogue content?
Jul 08 14:19:40 <DocScrutinizer05> http://www.mmnt.net/db/0/0/sower.yandex.ru/mirrors/meego/releases/1.2.0/repos/non-oss/source/qflasher-21-1.1.src.rpm (synthesized URL)  Requested page not found.
Jul 08 14:19:59 <xes> DocScrutinizer05: yep for me too... but mmnt caches contents not always available. We should retry.. i think it is the first time i can see those files
Jul 08 14:21:29 <xes> Pali: maybe you already have those files? ^^
Jul 08 14:23:29 <Pali> I have these files: qflasher-21-1.2.i586.rpm qflasher-21-1.1.src.rpm qflasher-17-1.3.src.rpm 
Jul 08 14:23:44 <Pali> but *src* files contains only spec file and ELF binary
Jul 08 14:23:46 <Pali> no source code
Jul 08 14:23:55 <Pali> sources were never released
Jul 08 14:25:15 <DocScrutinizer05> o.O wow how nasty
Jul 08 14:28:37 <DocScrutinizer05> hmm?  >> Защита от вируса «WannaCry»: прямые ссылки на заплатки от Microsoft, скрипт для проверки локальной сети на уязвимость<< ?
Jul 08 14:32:33 <xes> ads?
Jul 08 14:42:04 <DocScrutinizer05> no idea, I just see WannaCry
Jul 08 16:21:03 <DocScrutinizer05> Pali: https://github.com/systemd/systemd/issues/6309
Jul 08 16:22:01 <KotCzarny> hehe, you are now officially marked as a troll by poetterheads
Jul 08 16:23:48 <Pali> poettering probably do not know about getpwnam() function
Jul 08 16:25:01 <Pali> for converting username to uid
Jul 08 16:26:05 <Pali> I bet that ticket would be locked and discussion about it forbidden
Jul 08 16:30:24 <DocScrutinizer05> I give a shit about what tags poetterheads give me ;-)
Jul 08 16:31:21 <DocScrutinizer05> Pali: feel free to comment on that ticket and mention getpwnam() function as the only "sytaxcheck" needed for the parameter value
Jul 08 16:34:30 <DocScrutinizer05> note: >>The getpwnam_r() and getpwuid_r() functions are thread-safe.<<
Jul 08 16:40:48 <DocScrutinizer05> but I guess poettering already does that, just he added a nonsensical syntax check for the username before, and - even worse - he makes systemd just ignore the whole parameter if that syntax check fails
Jul 08 18:48:48 <KotCzarny> doc, your ticket is already closed as 'fixed' ;)
Jul 08 19:04:41 <DocScrutinizer05> LOL
Jul 08 19:07:47 <Wizzup> well, in their defence, they made a PR with the fix
Jul 08 19:07:56 <Wizzup> the PR just hasn't been merged yet, so perhaps closing the issue is a bit weird
Jul 08 19:08:32 <L29Ah> i wonder if it will be silently merged w/o a word from lennart
Jul 08 19:09:01 <KotCzarny> or unmerged some time after ? ;)
Jul 08 19:09:15 <KotCzarny> or fixed the fix
Jul 08 19:09:25 <L29Ah> nah, he's not /that/ asshole
Jul 08 19:09:37 <KotCzarny> haha
Jul 08 19:09:53 <KotCzarny> that's what dead people say when someone stupid destroys whole civilisation
Jul 08 19:10:30 <L29Ah> he's a fulltime redhat employee, no?
Jul 08 19:11:03 <L29Ah> i guess this would be noticed by a few enterprise customers
Jul 08 19:20:47 <DocScrutinizer05> I already wonder how long until RH bosses will kick Lennart's arse
Jul 08 19:21:35 <sicelo> is he not a boss?
Jul 08 19:22:04 <DocScrutinizer05> I mean, the evil "how to achive world dominion" plan made up by RH a decade ago already is one thing, poor coding skills and bug handling is a whole different story
Jul 08 19:22:33 <DocScrutinizer05> Lennart is not RH boss afaik, not at all
Jul 08 19:26:57 <Wizzup> RH mostly doesn't like lennie.
Jul 08 19:27:18 <Wizzup> but surely we have better things to do with -our- time than worry about lennie
Jul 08 19:38:02 <sicelo> indeed
Jul 08 20:15:08 <DocScrutinizer05> I'm not worried about that person, rather about the general direction the linux world gets pushed to, and by whom and why
Jul 09 02:59:40 <MaceN8x0> well
Jul 09 02:59:53 <MaceN8x0> guess i got this old thing working
**** ENDING LOGGING AT Sun Jul 09 03:00:01 2017