Livio has quit [Ping timeout: 268 seconds]
Pali has quit [Ping timeout: 252 seconds]
Daanct12 has joined #maemo-leste
<tmlind> Wizzup: thanks for the report, i'll be posting some rfc 8250_omap fixes today and might have a fix for that one too now, still have not seen it here somehow
<tmlind> seems similar to the one reported by freemangordon a few days ago
<tmlind> that driver clearly has other serious issues that have gone unnoticed..
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
joerg has quit [Ping timeout: 265 seconds]
joerg has joined #maemo-leste
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #maemo-leste
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
macros_ has quit [Ping timeout: 264 seconds]
macros_ has joined #maemo-leste
mardy has joined #maemo-leste
ceene has joined #maemo-leste
<freemangordon> Wizzup: ugh:
<freemangordon> Sep 27 22:28:50 localhost icd2 0.99[3483]: calling module 'libicd_network_wpasupplicant.so' link_up
<freemangordon> Sep 27 22:28:50 localhost icd2 0.99[3483]: libicd-network-wpasupplicant: wlan_bring_up: A1_23EC
<freemangordon> Sep 27 22:28:50 localhost icd2 0.99[3483]: libicd-network-wpasupplicant: Got network: (null), (null)
<freemangordon> Sep 27 22:28:50 localhost icd2 0.99[4388]: icd2 version 0.99 starting
rafael2k has joined #maemo-leste
rafael2k_ has joined #maemo-leste
Daanct12 has quit [Read error: Connection reset by peer]
Daaanct12 has joined #maemo-leste
rafael2k has quit [Ping timeout: 268 seconds]
<freemangordon> Wizzup: I think it is wrong to assume that network_id == iap_id without checking for ICD_NW_ATTR_IAPNAME here: https://github.com/maemo-leste/libicd-network-wpasupplicant/blob/master/src/wlan.c#L262
rafael2k_ is now known as rafael2k
n900 has quit [Ping timeout: 268 seconds]
crab has quit [Ping timeout: 268 seconds]
n900 has joined #maemo-leste
crab has joined #maemo-leste
<freemangordon> hmm, maybe there is another issue
RedW has quit [Ping timeout: 265 seconds]
pere has quit [Ping timeout: 265 seconds]
alex1216 has joined #maemo-leste
norayr has quit [Ping timeout: 250 seconds]
dev has quit [Ping timeout: 252 seconds]
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
pere has joined #maemo-leste
Livio has quit [Ping timeout: 246 seconds]
akossh has joined #maemo-leste
uvos has joined #maemo-leste
ceene has quit [Ping timeout: 260 seconds]
RedW has joined #maemo-leste
Daaanct12 has quit [Quit: Quitting]
RedW has quit [Ping timeout: 265 seconds]
ceene has joined #maemo-leste
<Wizzup> freemangordon: right
<Wizzup> tmlind: ok, ty
RedW has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Client Quit]
Pali has joined #maemo-leste
pere has quit [Ping timeout: 265 seconds]
ceene has quit [Ping timeout: 268 seconds]
pere has joined #maemo-leste
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste
ceene has joined #maemo-leste
<freemangordon> tmlind: oh, those fixes really look as what we need
<freemangordon> will test as soon as I have some spare time
ceene has quit [Ping timeout: 265 seconds]
norayr has left #maemo-leste [Error from remote client]
<tmlind> freemangordon: ok thanks, the first one hopefully fixes what you're seeing
<uvos> tmlind: Wizzup: freemangordon: applied and building on ci @uart patches
<tmlind> uvos: do you have it reproducable too?
<uvos> i can repoduce it
<uvos> sometimes
<uvos> its not reliable
<uvos> im not sure what makes the difference
<tmlind> hmm and are the messages appearing only in /var/log/messages on next reboot?
<freemangordon> I see it every time I issue sudo reboot/sudo poweroff from ssh session
<uvos> also console
<tmlind> or /var/log/syslog?
<tmlind> weird
<tmlind> no luck seeing it here with poweroff from ssh
<freemangordon> running leste?
<tmlind> nope, not seeing why that would make a difference though
<uvos> i clearly makes some kind of difference
<freemangordon> yes, it does
<uvos> the debian droid never sees it either
<tmlind> weird
<freemangordon> maybe timing issue
<tmlind> well let's hope the patch fixes it..
<freemangordon> uvos: does it happen if you issue sudo reboot from ssh session?
<freemangordon> here it is 100% reproducible
<tmlind> freemangordon: and you see it on the serial console as it happens, or on next boot in logs?
<uvos> freemangordon: not allways
<freemangordon> I see it on ssh console
<freemangordon> I have no serial here
<freemangordon> serial console that is
<uvos> tmlind: enableing serial makes it go away
<tmlind> ah ok
<uvos> tmlind: so dose enableing more traceing features in kconfig
<tmlind> heh
<uvos> not sure exactly which but my full debug options kernel dosent show it
<tmlind> ok
<tmlind> so i've seen flakey reboot occasionally where the device and does not reboot, maybe that's related as i don't think i've seen that with the pending 8250 fixes
<uvos> thats pretty mutch this
<tmlind> anybody else seen that one?
<uvos> when it happens the getty hangs
<uvos> and shutdown hangs
<tmlind> ok, and reboot hangs too?
<uvos> yes same thing
<tmlind> ok fingers crossed then
norayr has joined #maemo-leste
ceene has joined #maemo-leste
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
macros_2ndPC has joined #maemo-leste
macros_ has quit [Ping timeout: 246 seconds]
<freemangordon> uvos: you can't do 5.18.19.2-1 IIUC
<freemangordon> what you should do is 5.18.19-2 and force-push 5.18.19 tag
<freemangordon> Wizzup: correct? ^^^
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
<freemangordon> uvos: do you want me to release?
<uvos> freemangordon: i think it should work
<uvos> i just tagged it wrong sec
<freemangordon> ok
<uvos> yeah typo
<freemangordon> wait a bit
<freemangordon> I want to push battery low fix
<freemangordon> ok?
<buZz> omg yes please
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
<uvos> freemangordon: sure
<uvos> buZz: it wont solve your issue
<freemangordon> ok, will let you know when I am ready
<buZz> yesterday i pulled d4 from charger with 'fully charged' displayed, enabled wifi, started chromium, before page was loaded 'Battery empty at xxxxmV'
<buZz> and white led and powerdown \o
<freemangordon> buZz: yes, it will not fix your issue
<buZz> aw, sad
<uvos> buZz: that sounds like a bad battery
<freemangordon> your issue is bad battery
<buZz> ¯\_(ツ)_/¯
<buZz> it works fine if i make it ignore the 'battery empty'
<freemangordon> maybe try to reset the calibration
<uvos> callibration has nothing to do with it
<buZz> calibration wont change resistance
<uvos> itbuZz: maybe, but your symptoms suggests the battery spikeing down to 3.35v while at 4 ish volts
<uvos> thats bad
<uvos> that means its spikeing down below 2.8V when your battery is lower
<uvos> the omap/dram start missbehaveing at that voltage
<buZz> ¯\_(ツ)_/¯
<buZz> i'll fiddle around, maybe just a moving average over battery voltage
ceene has quit [Remote host closed the connection]
<freemangordon> uvos: pushed https://github.com/maemo-leste/droid4-linux/commit/d67cc2eba98cc3dca4739f9775303e46b1401870, please pull and tag as appropriate
<buZz> 'once every 30 seconds' might -totally- fix my issue :P
<uvos> no
<uvos> this isent whats powering off the device in your case
<buZz> its what is reporting the voltage
<uvos> upower polls voltage
<freemangordon> lets see
<buZz> then why is cpcap doing this at all?
<uvos> if its a whilte led during shutdown
<uvos> it was not the kernel
<buZz> if we arent using the interrupt, wouldnt it be better to not create it?
<uvos> its complicated
<freemangordon> uvos: actually it might help
<buZz> thats why i'm asking to clarify it ;)
<uvos> freemangordon: how so?
<freemangordon> as we may have the first 'low' irq at relatively ok voltage
<uvos> that dosent matter
<uvos> its not the kernel shutting down buzz device
<uvos> its mce
<uvos> and thats based on upower polling voltage_Now
<uvos> totaly unreladed to the machinery here
<freemangordon> yes, but it shits down on 'low' event and critical voltage
<buZz> where does the voltage come from? not cpcap?
<freemangordon> *shuts
<uvos> sure but if its spikeing below the kernel thresh of 3.1 or what was it v
<uvos> it will spike below mces of 3.35 even more
<buZz> 3.5v
<uvos> 3.35
<buZz> which is quite high imho
<freemangordon> buZz: it is the same here
<freemangordon> it is simply that those batteries are amost dead
<uvos> 3.35v
<buZz> 'cpcap_battery cpcap_battery.0: Battery low at 3461mV!
<uvos> cpcap fires the irq at 3.3v
<uvos> the kernel then mesures the voltage
<uvos> the 3.46 comes from that messurement
<buZz> but it -always- reports the voltage as 'low' ?
<freemangordon> it was triggered because a spike
<uvos> beacuse your battery is dead
<freemangordon> :nod:
<buZz> even without signalling with IRQ that its low?
<uvos> as in its internal resistance is really high
<buZz> whats the logic in that
<buZz> 3.46V isnt low
<freemangordon> buZz: wait
<freemangordon> there is a period between irq being triggered and voltage measured
<freemangordon> it is triggered @ < 3.3
<buZz> ah, and it -always- outputs 'cpcap_battery cpcap_battery.0: Battery low at 3461mV!' -regardless- if its low or not?
<freemangordon> but this is a spike caused by a temporal high load
<freemangordon> it *was*
<uvos> battery low here means that the low battery irq fired
<buZz> ah :)
<buZz> uvos: maybe put that in the text then? :D
<uvos> complain to tmlind
<uvos> its his text :P
<freemangordon> heh :)
<buZz> he's the only person with a texteditor eh
<freemangordon> yeah, this is misleading
<freemangordon> buZz: feel free to send a patch
<freemangordon> like "batter low irq triggered, current voltage xxxx"
<freemangordon> or somesuch
<buZz> where does the IRQ originate?
<freemangordon> cpcap
<buZz> so 'triggering low battery IRQ, voltage i see is xxxx' ?
<freemangordon> no, it is triggering the irq
<freemangordon> and irq handler measures the voltage
<buZz> ahh
<freemangordon> but it takes time for the handler to be called
<buZz> its only triggering to -itself-
<buZz> i wonder if IRQ would even be the best method for that
<freemangordon> and by the time of the measurement, the voltage is already different to the one that caused the irq to be triggered
<freemangordon> I can't explain it any better than that
<buZz> i follow
<freemangordon> uvos: it is still missing the tag
<uvos> freemangordon: sigh ok
<uvos> the tag its looking for is def there
<freemangordon> it is not
<freemangordon> I just pulled and there is no such tag
<uvos> git clone --depth 1 --branch maemo-kernel-5.18.19.2 git@github.com:maemo-leste/droid4-linux.git
<uvos> works here
<freemangordon> you should do "git push --tags"
<freemangordon> not, it searches for tag, not branch
<uvos> i cant do that, to many tags
<uvos> git push maemo tag maemo-kernel-5.18.19.2
<uvos> should have done the trick
norayr has left #maemo-leste [Error from remote client]
<uvos> --branch takes tags here
<uvos> i know thats counter intuative
<freemangordon> no idea, lemme pull, to see if it has appeared
<freemangordon> ok, now it appeared
<uvos> i dident change anything
<uvos> or push
<uvos> so wierd
<uvos> ill just kick it again and see
<freemangordon> I have no idea too
<freemangordon> ok
<freemangordon> maybe github was too slow, dunno
<freemangordon> yay, it seems the issue is fixed :D
norayr has joined #maemo-leste
<freemangordon> and device reboots/powers down way faster
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
norayr has joined #maemo-leste
<tmlind> freemangordon: ok maybe reply to the list with a tested-by then?
<freemangordon> sure
<freemangordon> I want to have it running for a while
noidea_ has quit [Remote host closed the connection]
rafael2k has quit [Ping timeout: 268 seconds]
alex1216 has quit [Quit: WeeChat 2.3]
<tmlind> yup
<tmlind> thanks
Livio has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
<uvos> freemangordon: github must have been to slow then
<uvos> wierd
<freemangordon> yeah
Livio has quit [Ping timeout: 265 seconds]
noidea_ has joined #maemo-leste
noidea_ has quit [Client Quit]
noidea_ has joined #maemo-leste
Twig has joined #maemo-leste
<freemangordon> tmlind: how to check if serial idles correctly?
<freemangordon> as I think I see increased idle current
<uvos> omapconf
<freemangordon> I guess I have to build that,right?
<uvos> i think we put it into the repos
<uvos> not sure tho
norayr has left #maemo-leste [Error from remote client]
<uvos> you can also read the register by hand ofc
<freemangordon> I'll just build the tool
<uvos> i dont know what it is of the top of my head
<uvos> if we dont have a omapconf package
<uvos> we should
<freemangordon> we don;t
<Wizzup> uvos: yeah I can make a pkg, but let's also have doc for it
<uvos> Wizzup: its fairly well documented by its help
<uvos> not sure what you want
<uvos> for details it quickly becomes "read the register manual"
<uvos> as its a tool that shows you registers
<freemangordon> ok, I compiled it, now what do I want from it?
<uvos> omapconf audio os_idle --log-all
<uvos> or so
<uvos> aproximate command
<uvos> check help
<freemangordon> I checked but there are too many options
<uvos> s/audio/audit
<uvos> my d4 is empty sorry
<uvos> its something very close to that
<uvos> also do sleep 20; omapconf .....
<uvos> so that its idle when it fires
<Wizzup> uvos: for our purposes maybe
dev has left #maemo-leste [Disconnected: closed]
<uvos> its "omapconf audit os_idle full_log"
<freemangordon> yep
<freemangordon> I have full og but not sure how to read that
<freemangordon> all I can see is that ABE clocks are running but they should be stopped
dev has joined #maemo-leste
<freemangordon> and I see abe_cm:clk:0030:0: failed to disable in dmesg
<freemangordon> anyway, have to run, ttyl
<tmlind> ok abe is mostly for audio etc, ttty
<tmlind> ttyl
<freemangordon> tmlind: do you want the log?
<freemangordon> tmlind: https://pastebin.com/65PkMSVp
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
<uvos> the abe issue
<uvos> we have allways had
<uvos> so thats not a regression
<uvos> otherwise log looks like your system is ideling ok
norayr has joined #maemo-leste
<tmlind> yeah it looks pretty good
<Wizzup> ret is also increasing for me
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 252 seconds]
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 244 seconds]
ceene has joined #maemo-leste
<freemangordon> 60 mA @ idle, is that ok?
<freemangordon> iirc it was 40
<buZz> quite sure 60mA @ idle is lower than many modern phones
<buZz> i was seeing 50-60 with screen off, gprs connected, my modified mosh open
ceene has quit [Remote host closed the connection]
<freemangordon> POWER_SUPPLY_CURRENT_AVG=32458
<freemangordon> oh, ok
<freemangordon> uvos: do we know the cause for that abe clock
<freemangordon> issue?
<buZz> 32! nice
<buZz> any idea how i should get rid of > Unknown media type in type 'font/ttf'
<buZz> shouldnt that mime type be defined by shared-mime-info ?
* buZz tried dpkg-reconfigure shared-mime-info
<buZz> tries*
<freemangordon> buZz: this is hildon thing
<buZz> but still, font/ttf shouldnt be a weird mime-type for apt, should it?
<freemangordon> I guess adding "font" there will fix it
<freemangordon> but still, this is just a warning anyways
<buZz> yeah i know, just annoying
<buZz> shall i PR 'font' into that?
<freemangordon> yep
<freemangordon> if it fixes the issue
<buZz> hmmm, is the src package of this in leste? then i could easily do it on my own system
<freemangordon> did you look ath the link ^^^
<buZz> yes
<freemangordon> this is libhildinmome package
<freemangordon> and yes, this is in leste
<buZz> i'll check myself then :P
<buZz> i ment the source package ;)
<freemangordon> yes, it is
<buZz> not all leste packages (that we have source of) have source in leste
<freemangordon> how's that?
<freemangordon> wtym 'leste package'
<buZz> like the kernel for instance
<freemangordon> sure we have source
<buZz> we -have- it , but 'apt-get source linux-image-omap' doesnt grab it
<freemangordon> weird]
<freemangordon> anyway, ttyl
<buZz> \o
<buZz> libhildonmime -does- have a src package , nice
<freemangordon> buZz: just clone the git repo
<freemangordon> it is exactly the same source
<freemangordon> but you'll be able to do PR
<buZz> right, but installing it is annoying from source
<buZz> i'll just try editting this source, building a pkg for my phone, and see if it removes the warnings
<buZz> and -then- do a PR if it does ;)
<freemangordon> buZz: cloning from git is 100% identical to source package in terms of building
<freemangordon> but ok, up to you
<buZz> freemangordon: sure, but a -mess- to install imho , apt-get source, edit, build, install updated pkg, makes it just superconvenient :)
Twig has quit [Remote host closed the connection]
norayr has left #maemo-leste [Error from remote client]
dev has left #maemo-leste [Disconnected: closed]
<uvos> freemangordon: no i never investigated it
<uvos> freemangordon: i have no idea
<uvos> d4 should get around 30 ish mA unter load
<uvos> or around 100mW
<uvos> *under idle ofc
<uvos> it its more, something regessed
<uvos> but its not visible in omapconf
<uvos> (could be more wakeups/s without idle being outright broken)
dev has joined #maemo-leste
mardy has quit [Quit: WeeChat 3.5]
Livio has quit [Ping timeout: 252 seconds]
<buZz> sadly, that warning is not fixed by just adding "font" on https://github.com/maemo-leste/libhildonmime/blob/master/libhildonmime/update-category-database.c#L41 (tested with dpkg-reconfigure hildon-update-category-database)
<buZz> oh maybe i should do the mime one first
<buZz> oh, no that actually is the mime one
<buZz> oh, thats from a seperate package! lol
<uvos> freemangordon: tmlind: indeed the new kernel has higher power consumption
<uvos> looks like ~30mW
<freemangordon> uvos: I am getting POWER_SUPPLY_CURRENT_AVG=32458
<freemangordon> which is near those 30mA you mentioned
<uvos> mW
<uvos> i have a cron job that logs power_avg every minute
<uvos> im geting around 30mW (thus around 10mA) more
noidea_ has quit [Ping timeout: 246 seconds]
akossh has quit [Quit: Leaving.]
<buZz> on a vanilla config?
<buZz> oh. 10mA more than 30mA ?
<buZz> freemangordon: yes it does!
<buZz> until the next missing mime mediatype, i bet ;)
norayr has joined #maemo-leste
noidea_ has joined #maemo-leste
uvos has quit [Ping timeout: 265 seconds]
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
dev has quit [Quit: Gateway shutdown]
sunshavi_ has quit [Ping timeout: 244 seconds]
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste