IRC logs for #cip for Thursday, 2018-10-04

*** alicef has quit IRC04:14
*** alicef has joined #cip04:15
*** alicef has quit IRC04:16
*** alicef has joined #cip04:16
*** dl9pf has quit IRC04:37
*** dl9pf has joined #cip04:49
*** dl9pf has joined #cip04:49
*** wagi has quit IRC06:31
*** robertmarshall has joined #cip07:31
* robertmarshall runs a daily health on the iwg20m with an email to the list.07:39
*** robertmarshall is now known as rajm07:40
rajmunfortunately the BBB got left at home - let me see if I can find an appropriate cable for a spare board...07:41
*** Ystk has joined #cip07:47
* rajm runs a daily health on the BBB with an email to the list.07:56
*** patersonc has joined #cip07:58
*** wagi has joined #cip07:58
*** Tzongyen_Lin has joined #cip07:59
szlin#startmeeting08:00
szlin#roll call08:00
szlinplease say hi if you're around08:00
szlin._./08:00
gavinlaihi08:00
Tzongyen_Linhi08:00
bwhhi08:00
patersonchi08:00
wagihi (partial around, also on a telco in parallel)08:00
szlin#topic AI review08:01
rajmhi08:01
szlin- AI: Create a wiki page for collaboration (SZ Lin)08:01
szlin* https://wiki.linuxfoundation.org/civilinfrastructureplatform/linux-4.4.y08:01
szlinAny suggestions?08:01
patersoncWhen you say "ACK: SZ Lin...", is it for the patches listed above?08:02
szlinthat's right08:02
patersoncOkay08:03
szlinack the patch each by each08:03
iwamatsuHi08:03
szlinbecause some patches are not in CIP kernel maintenance scope08:03
szlinfeel free to provide any idea afterwards.08:04
szlin-AI: Discuss patchwork item in TSC meeting (Chris)08:04
szlin*Example: https://patchwork.kernel.org/project/linux-renesas-soc/list/08:04
patersoncI think the outcome of the discussion about patchwork was that no one saw any issues with using patchwork, or proposed any alternitives08:05
patersoncDoes anyone here have any other views?08:05
patersonciwamatsu? (as the main maintainer going forward...)08:05
szlinpatersonc: which one do you prefer? https://patchwork.ozlabs.org/ or https://patchwork.kernel.org/08:06
iwamatsupatersonc: patchwork makes it easy to understand the state of the patch, I think. I agree using pathcwork.08:07
patersoncI don't have a strong opinion, but kernel.org seems more 'legit', but only because I've never really heard of ozlabs until last week...08:07
patersonciwamatsu: Okay08:08
patersoncszlin: Either would be fine08:08
szlinAny objections?08:08
szlin#agreed CIP kernel maintenance team will use patchwork08:09
szlinpatersonc: do you need any assistence with this AI?08:10
patersoncOnly if someone is keen to set it up. If no one is then I'll pick it up.08:11
szlinanyone?08:12
patersoncI'll email kernel.org first and see if they'll take us. If not I'll try ozlabs.08:12
szlin#action patersonc will apply patchwork for CIP kernel maintenance team08:13
szlinpatersonc: thanks!08:13
patersoncNo worries08:13
szlin#topic kernel maintenance updates08:13
szlinMoxa UC-2100 dts was merged, I will check if we have any other in-house patches08:14
szlinhttps://www.lkml.org/lkml/2018/9/28/88008:14
szlinfurthermore, I've sent CVE-2018-10880 kernel patch for 4.4.y08:15
szlinhttps://www.spinics.net/lists/stable/msg260103.html08:15
patersoncGreat08:15
szlin=== 4.4.155 reviewing ===08:15
szlinI am taking my personal leave until next week, and thus I don't have any updates.08:15
wagiv4.4-rt update: Peter Z recommended to use ticket spinlocks for -rt instead of qspinlocks. I retested v4.4-rt with ticket spinlocks and the problem are gone.08:16
szlinwow...08:16
szlinwagi: do you find out the root cause?08:16
wagiit is still under investigation08:16
wagipretty nasty stuff08:17
szlinwagi: true.. thanks for your update08:17
bwhTicket spinlocks are what mainline uses, right?08:17
wagimainline uses qspinlocks these days08:17
bwhOh I see08:17
wagiqspinlocks scale easily up to hundreds of cpu08:18
wagiwhile ticket spinlocks is usuless for system with more then 16 cpus (if all cpus spin on the same lock, obviously)08:18
szlinsome references about kernel lock - http://events17.linuxfoundation.org/sites/events/files/slides/linuxcon-2014-locking-final.pdf08:19
szlinI'm not quite familiar with qspinlocks08:19
wagithe concept is 'easy' but the implementation is really really hard stuff08:20
*** mungaip has joined #cip08:20
wagianyway for 4.4-rt it is solved08:21
szlinwagi: that's interesting, I will take a look with it afterwards, thanks08:21
wagiI guess for 4.9 fixex could be backported08:21
wagibigeasy has done it for 4.9-rt08:21
wagithe problem is that there are quite a few dependencies (atomics API changes etc)08:22
wagiI shut up if no one has question now :)08:23
szlinwagi: do you have related URL with 4.9-rt?08:23
wagiIIRC bigeasy has not posted anything, still WIP08:24
wagiI suppose any fix will go via Greg KH's stable trees08:25
wagiI'll ask bigeasy what he's plan are08:25
szlinwagi: Please keep us posted on the status :)08:26
wagisure will do08:26
szlinany other points?08:26
szlin308:26
szlin208:26
szlin108:26
szlin#topic kernel testing08:26
rajmhi - there's a MR in for the change to b@d device types to get iwg20m - some discussion around whether using zImage directly is ok08:27
rajmI'm running daily tests on both BBB and iwg20m when in the office08:28
rajmstill having issues with uboot and lava-docker will discuss later08:28
rajmthanks08:28
szlinrajm: thanks for the updates.08:29
szlinany questions?08:29
szlin308:30
szlin208:30
patersonco/ Update from Renesas08:30
szlin108:30
patersoncWe were getting somewhere with the CIP LAVA master setup, but then the admin rebuilt the docker container from scratch rather than saved the instance before a reboot, so now we need to create all the user accounts and exchange passwords over the phone again.08:30
szlinpatersonc: thanks.08:31
szlinany other points?08:31
patersoncNope08:31
szlin#topic AOB08:31
szlinany points?08:32
bwhThe Debian kernel team had a meeting on Tuesday evening08:32
bwhWe agreed to use 4.19 for the buster release08:32
patersoncThanks bwh08:33
wagiIs 4.19 going to be a LTS?08:33
bwhyes08:33
patersoncI assume there are therefore no outstanding reasons for CIP not to use LTS v4.19 for the next SLTS?08:34
szlin#info Debian 10 (buster) selects 4.19 kernel08:34
patersoncIs this something the maintainers should take to the TSC (and maybe announce to the world at ELC?)08:34
*** toscalix has joined #cip08:34
iwamatsudebian kernel team meeting log: http://meetbot.debian.net/debian-kernel/2018/debian-kernel.2018-10-02-18.33.html08:34
szliniwamatsu: thank you for the link.08:35
toscalixthanks08:36
szlinpatersonc: yes, I think 4.19 might be the version of SLTS08:36
patersonc"Might"? Is there any reason it wouldn't be?08:37
szlinpatersonc: we need the official announcement08:37
toscalixthere won't be08:38
patersoncszlin: Good point08:38
patersoncSo assuming v4.19 _is_ an LTS, we will take it? If for some reason Greg doesn't use v4.19 afterall we'll have a rethink08:38
bwhright08:39
patersoncbwh: Is this basically the same view for Buster? Or will you use v4.19.y regardless?08:39
bwhWe want to use an LTS version08:40
patersoncOkay08:40
szlinthere is very little information about 4.1908:41
szlinany other points?08:42
szlin308:42
szlin208:42
szlin108:43
szlin#endmeeting08:43
szlinthanks all08:43
patersoncThanks08:43
Tzongyen_Linthanks08:43
*** Tzongyen_Lin has quit IRC08:43
bwhThanks08:43
iwamatsuthanks08:43
wagipatersonc: we still meet for the breakfast, right?08:44
szlinpatersonc: Typically, greg will post an announcement in his blog with stable kernel selection08:44
szline.g., http://www.kroah.com/log/blog/2017/09/06/4-dot-14-equals-equals-this-years-lts-kernel/08:44
patersoncwagi: Sure :) Monday before the maintainers meeting?08:44
patersoncszlin: yep - thanks.08:45
wagipatersonc: Nice. Yes, before the meeting08:45
patersoncOh one more point - I'm adding information about the iwg20m board to the cip wiki pages08:45
patersoncHow to build the BSP etc.08:45
patersonc(not really Kernel maintenance, but perhaps useful)08:46
patersoncIf anyone has any information on the other reference platforms it would be good to add it08:46
patersonchttps://wiki.linuxfoundation.org/civilinfrastructureplatform/cipreferencehardware08:46
toscalixpatersonc: nice08:47
patersoncI'm not very familiar with the other reference hardware - can anyone check I have the names correct?08:47
rajmyes thanks patersonc !08:48
patersoncIt's been on my todo list for over a year...08:49
*** Ystk has quit IRC09:08
*** Ystk has joined #cip13:17
rajmthanks bwh I've now merged https://gitlab.com/cip-project/cip-testing/board-at-desk-single-dev/merge_requests/63 - the iwg20m change13:45
*** Ystk has quit IRC13:55
*** rajm has quit IRC14:26
*** patersonc has quit IRC14:34
*** rajm has joined #cip14:41
*** patersonc has joined #cip14:50
*** dl9pf has quit IRC15:06
toscalixszlin: still around?15:11
toscalixbwh just sent the kernel config analysis15:12
szlintoscalix: yes, I'm here15:13
szlingot it, we will check it.15:17
szlinbwh: toscalix : thanks!15:17
toscalixit was the pending task missing from bwh as maintainer15:21
toscalixso we are done15:21
toscalixuntil the new maintainer request something15:22
toscalixrelated with the handover of the maintainer role15:22
toscalixnow... bwh changes hats15:22
toscalix:-)15:22
*** dl9pf has joined #cip15:24
*** dl9pf has joined #cip15:24
*** rajm has quit IRC15:44
patersoncWell done bwh :)16:02
*** patersonc has quit IRC16:09
*** toscalix has quit IRC17:05

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!