**** BEGIN LOGGING AT Fri Jan 04 02:59:57 2019
Jan 04 07:30:09 <Herrie> Morning!
Jan 04 07:51:56 <Tofe> Morning!
Jan 04 09:13:41 <Herrie|Laptop> Morning
Jan 04 09:14:50 <Herrie|Laptop> New builder is start to take shape... Case, mainboard, CPU, cooler, memory, M.2 SSD all installed... Still waiting the results from DHL on the PSU... Might try to reuse my 650W Antec for the time being, seeing I don't have a power hungry video card ;)
Jan 04 10:18:54 <novaldex> Morning, Happy New Year all!
Jan 04 10:19:42 <nizovn> i just noticed we have linux-libc-headers 4.10, but our tissot kernel is 3.18. is it ok? i maybe have problem caused by this with OSE.
Jan 04 10:19:52 <nizovn> morning
Jan 04 10:19:57 <Herrie|Laptop> novaldex: Morning! Welcome back & Happy New Year!
Jan 04 10:20:26 <novaldex> Thanks Herrie|Laptop! Trust you had a good one?
Jan 04 10:20:41 <novaldex> I know i've been absent a bit, what did I miss?
Jan 04 10:20:58 <Herrie|Laptop> novaldex: Nothing too much ;)
Jan 04 10:21:05 <novaldex> that has to be a good thing ;)
Jan 04 10:21:08 <Herrie|Laptop> Server was down due to some size increase it seems
Jan 04 10:21:31 <novaldex> Milla? Yes i'm aware, but I only found out after ka6sox started work on it
Jan 04 10:21:43 <Herrie|Laptop> novaldex: It's sorted now anyway
Jan 04 10:21:58 <novaldex> the guys have been doing a fair few things over the holidays it seems, strengthening the infra
Jan 04 10:22:15 <Herrie|Laptop> That's good
Jan 04 10:22:22 <Herrie|Laptop> No update on the issues tracker?
Jan 04 10:22:29 <Herrie|Laptop> And the mailing list?
Jan 04 10:23:11 <novaldex> issues tracker is still being worked on, it became a question of where to bring it back
Jan 04 10:23:36 <novaldex> the mailing list I thought had been taken care of, it's not in our hands but OSUOSL's as they own/run it
Jan 04 10:23:46 <Herrie|Laptop> novaldex: I don't care where as long as it's accessible
Jan 04 10:23:59 <novaldex> ka6sox was supposed to be talking to one of the guys there to keep it going
Jan 04 10:24:32 <Herrie|Laptop> OK
Jan 04 10:24:45 <novaldex> yeah, that was our 'issue' as we couldn't bring it back somewhere that would be accessible at first, as it's pre-migration
Jan 04 10:25:09 <novaldex> i'll nudge them in a bit & see where they got to with it
Jan 04 10:25:29 <novaldex> reading back a bit did you guys need another package installed on one of the builders?
Jan 04 10:25:40 <Herrie|Laptop> novaldex: Yes it seems so
Jan 04 10:25:46 <Herrie|Laptop> At least that's what nizovn suggested
Jan 04 10:26:13 <Herrie|Laptop> See http://jenkins.nas-admin.org/job/webos-preware-feeds/lastBuild/consoleFull
Jan 04 10:28:30 <nizovn> ah yes, but i'm afraid it's not sufficient
Jan 04 10:28:39 <Herrie|Laptop> "Dec 24 16:05:05 <nizovn> Herrie: looks like we need to install intltool package on that server"
Jan 04 10:28:47 <nizovn> reviving this old infrastructure is a bit more difficult than i thought
Jan 04 10:29:06 * novaldex nods in agreement with nizovn
Jan 04 10:29:41 <novaldex> is it looking like just one or two missing packages?
Jan 04 10:30:50 <nizovn> just one "intltool" package
Jan 04 10:31:29 <novaldex> okay, let me put that on & at least you'll be a step closer
Jan 04 10:31:43 <novaldex> bonaire I take it is the one that needs it?
Jan 04 10:32:12 <nizovn> yes, seems so
Jan 04 10:48:49 <novaldex> okay, that's it installed now
Jan 04 10:49:11 <nizovn> thanks!
Jan 04 10:58:59 <Herrie|Laptop> novaldex: OK job running again, let's see where we get now
Jan 04 11:01:38 <novaldex> Herrie|Laptop: thanks..
Jan 04 11:02:16 <novaldex> I notice that builder could do with a few other updates, but decided against doing that right now, can save it for another time (it's probably not the only one)
Jan 04 11:03:06 <Herrie|Laptop> Seems we might need more: http://jenkins.nas-admin.org/job/webos-preware-feeds/31/console
Jan 04 11:20:05 <nizovn> i'm not familiar with autotools, but maybe we should just run autoupdate?
Jan 04 12:26:24 <Herrie|Laptop> nizovn: Neither am I
Jan 04 12:26:30 <Herrie|Laptop> I'll play around a bit when my new builder is ready
Jan 04 12:27:04 <bshah> anyone coming to FOSDEM btw?
Jan 04 12:34:24 <Herrie|Laptop> bshah: No plans yet, but Brussels isn't too far away from me, only few hrs by train
Jan 04 12:34:29 <Herrie|Laptop> So could get & make plans
Jan 04 12:35:24 <JaMa> fix for glog in thud was merged today, will trigger all unstable builds now (only old kernel should be failing now)
Jan 04 12:35:32 <bshah> Herrie|Laptop: *nod*
Jan 04 12:36:05 <Herrie|Laptop> bshah: But seeing it's on a weekend, might be a no go
Jan 04 12:36:07 <Herrie|Laptop> Need to check
Jan 04 12:36:11 <JaMa> Tofe: Herrie|Laptop: any luck with tissot backup?
Jan 04 12:36:36 <Herrie|Laptop> JaMa: I haven't tried anything yet, but got a Tissot with me here... So if you have some instructions on what to do, can try
Jan 04 12:37:03 <JaMa> sure, sec
Jan 04 12:38:13 <JaMa> 2019-01-02.log:01:51 <+JaMa> reflashing android 7,8,9 including persist partition didn't help with my touchscreen issue, last thing to try I can think of is if someone shares the backup (without system and userdata should be enough to make it smaller - my is around 140MB zip) with EDL https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 , then I can either confirm
Jan 04 12:38:19 <JaMa> that broken touchscreen
Jan 04 12:38:21 <JaMa> 2019-01-02.log:01:51 <+JaMa> calibration is somewhere in emmc, if it works I'll restore my backup again and then flash the internal partitions one by one to find out where it's stored, looks like TWRP itself is able to break the touchscreen, https://forum.xda-developers.com/mi-a1/help/touch-t3769226 so having your own backup of all partitions might be useful later as well
Jan 04 12:38:46 <JaMa> doesn't take long if you're in windows and have working EDL drivers
Jan 04 12:39:49 <JaMa> just run the command line tool, select partition_list.skip-systems-and-userdata.txt and dump it to some directory
Jan 04 12:40:49 <Herrie|Laptop> JaMa: Let me charge it a bit first and I'll have a look in a bit
Jan 04 12:41:17 <JaMa> thanks
Jan 04 14:32:23 <JaMa> novaldex: are the builders (bonaire) supposed to work fine now? the build I've triggered 2 hours ago seems to be stuck http://jenkins.nas-admin.org/view/luneos-unstable/job/luneos-unstable_mido/18/console
Jan 04 14:33:28 <novaldex> there isn't any reason why they shouldn't be working fine.. just checking
Jan 04 14:34:03 <JaMa> ok, will try to kill and restart that build
Jan 04 14:34:18 <novaldex> it's actively running
Jan 04 14:34:35 <novaldex> python3 seems to be using the most
Jan 04 14:34:48 <novaldex> ah, it's stopped now
Jan 04 14:35:14 <novaldex> not sure what it was actually doing, but the jenkins user had a few python3 instances running then
Jan 04 14:39:10 <JaMa> probably trying to comunicate with prserv which isn't running
Jan 04 14:42:23 <JaMa> I've started prserv on kaylee and now it works
Jan 04 15:17:00 <Herrie|Laptop> JaMa: Tissot doesn't want to charge it seems, need to check at home with another cable it seems
Jan 04 15:32:51 <JaMa> ok, thanks anyway
Jan 04 15:33:10 <JaMa> time to move OS to different SSD, bbl
Jan 04 23:37:12 <JaMa> damn Samsung SSD 860 EVO, seems like "Samsung explicitly states that queued TRIM is supported for Linux with
Jan 04 23:37:15 <JaMa> 860 PRO and 860 EVO.
Jan 04 23:37:20 <JaMa> " from Samsung explicitly states that queued TRIM is supported for Linux with
Jan 04 23:37:38 <JaMa> " https://github.com/torvalds/linux/commit/ca6bfcb2f6d9deab3924bf901e73622a94900473 isn't really true for all the drives
Jan 04 23:41:54 <elvispre> JaMa: What is the symptom? Are you running out of space when you shouldn't be or something?
Jan 04 23:43:34 <JaMa> "WRITE FPDMA QUEUED" commands fail and after a while (depending on how busy the drive is) result in sata port hard reset
Jan 04 23:44:24 <JaMa> which freezes the OS and in just 2 weeks managed to break ext4 a bit
Jan 04 23:44:51 <JaMa> I've blacklisted 860 in the libata again, lets see if it gets better, brb
Jan 05 00:20:53 <elvispre> JaMa: I guess you'll tell us if that worked in a fortnight :-)
Jan 05 00:22:12 <JaMa> it didn't :/ it's easy to reproduce with dd if=/dev/zero of=/dev/sdc bs=4096
Jan 05 00:22:25 <JaMa> even after re-extending the blacklist to cover 860 again
Jan 05 00:22:40 <JaMa> I wrote to the author of that commit, maybe he has some more clues
Jan 05 00:22:59 <elvispre> You get all the cool problems!
Jan 05 00:23:26 <JaMa> I can also try to disable NCQ completely, but lets first try this
Jan 05 00:23:49 <JaMa> elvispre: which reminds me, do you have few mins and tissot with you? :)
Jan 05 00:24:22 <elvispre> JaMa: Is this the backup partitions thing still?
Jan 05 00:24:25 <JaMa> yes
Jan 05 00:29:00 <elvispre> JaMa: It will take me a little while. I need to put a pyro LuneOS back onto my tissot and also work out how to get these EDL drivers onto my Windows machine.
Jan 05 00:29:07 <elvispre> Bear with me.
Jan 05 00:29:41 <JaMa> ok
Jan 05 00:30:09 <JaMa> you don't need the pyro for backup (if fastboot works for you it should be enough to put it into EDL mode)
Jan 05 00:30:24 <JaMa> I already had working EDL drivers in W10 (possibly from MiFlash)
Jan 05 00:32:06 <elvispre> JaMa: I have only ever used the flash_all.bat and that just uses fastboot from the android platform-tools
Jan 05 00:56:28 <elvispre> JaMa: So, can I just use one of the preconfigured partition lists?
Jan 05 00:56:43 <elvispre> persist-only, perhaps?
Jan 05 00:58:39 <elvispre> (After a bunch of fiddling about, I didn't seem to need to install EDL drivers after all. I already had a COM port.)
Jan 05 01:00:41 <elvispre> (And by no coincidence, I seem to have installed MiFlash back in July.)
Jan 05 01:13:25 <elvispre> Ah, JaMa requested partition_list.skip-systems-and-userdata.txt earlier. On its way...
Jan 05 01:21:39 * elvispre needs some sleep
**** ENDING LOGGING AT Sat Jan 05 02:59:56 2019