| *** masashi910 has joined #cip | 04:45 | |
| *** masashi910 has quit IRC | 06:52 | |
| *** masashi910 has joined #cip | 06:52 | |
| *** rajm has joined #cip | 07:01 | |
| *** helmut has quit IRC | 07:25 | |
| *** therisen has joined #cip | 07:43 | |
| wens | yay, severe performance regression in 4.19.x on x86 :( | 07:44 |
|---|---|---|
| wens | since 4.19.67 even, from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=46b306f3cd7b | 07:46 |
| szlin | does it affect 4.19 only? | 07:49 |
| wens | nooooo, it's also in 4.14, 4.9, and 4.4 | 07:51 |
| wens | it severely affects fork performance if CONFIG_VMAP_STACK=y | 07:51 |
| szlin | howa bout mainline? | 07:51 |
| wens | still need to test CONFIG_VMAP_STACK=n, but based on the fix: https://lore.kernel.org/patchwork/patch/1137341/ it should be ok | 07:52 |
| wens | szlin: I would say yes, but PTT doesn't run mainline kernel :p | 07:52 |
| wens | since the fix is still only in -next, mainline is likely to be affected | 07:53 |
| szlin | wens: I see, thanks. Maybe PTT can choose cip kernel in the future :p | 07:54 |
| wens | I'm using 4.19 for now, but we rarely update the kernel, as it's a pain to restart the machine | 07:55 |
| wens | anyway, that's my rant for the day | 08:12 |
| *** fujita3 has joined #cip | 08:51 | |
| wens | well, CONFIG_VMAP_STACK=n only fixes part of it. | 08:59 |
| *** pave1 has joined #cip | 08:59 | |
| *** pave1 has left #cip | 08:59 | |
| *** pave1 has joined #cip | 08:59 | |
| wens | other parts of the kernel use vmalloc and still get hit. things such as tty | 08:59 |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
| brlogger | Meeting started Thu Dec 12 09:00:02 2019 UTC and is due to finish in 60 minutes. The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 09:00 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | #topic rollcall | 09:00 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | please say hi if you're around | 09:00 |
| szlin | hi | 09:00 |
| wens | hi | 09:00 |
| pave1 | hi | 09:00 |
| patersonc | Hello | 09:00 |
| fujita3 | hi | 09:00 |
| masashi910 | #topic AI review | 09:00 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | 1. Test LTS (pre)releases directly - patersonc | 09:00 |
| *** kazu has joined #cip | 09:00 | |
| *** suzuki98 has joined #cip | 09:00 | |
| patersonc | For all of my actions - no update | 09:01 |
| patersonc | Sorry | 09:01 |
| suzuki98 | hi | 09:01 |
| masashi910 | ok, thanks | 09:01 |
| kazu | hi | 09:01 |
| masashi910 | 2. Create a way/process to run LTP only for release tests - patersonc | 09:01 |
| masashi910 | Chris-san, do you have updates? | 09:01 |
| patersonc | Nope | 09:02 |
| masashi910 | patersonc: ok, thanks | 09:02 |
| masashi910 | 3. Combine rootfilesystem with kselftest binary - Iwamatsu-san | 09:02 |
| masashi910 | Quote from Iwamatsu-san: "No 4 does not update." | 09:02 |
| masashi910 | Kudo's comment: "No 4 should be No 3". I will keep this AI as open | 09:02 |
| masashi910 | 4. Document a process on how to add tests to the CIP test setup - patersonc | 09:02 |
| patersonc | Nope | 09:02 |
| masashi910 | sure. | 09:02 |
| masashi910 | #topic kernel maintenance updates | 09:03 |
| *** brlogger changes topic to "kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:03 | |
| bwh | (hi) | 09:03 |
| masashi910 | == Quote from Iwamatsu-san == | 09:03 |
| masashi910 | I reviewed 4.4.202, and stable-rc on stable ML. | 09:03 |
| masashi910 | I send some comments for 4.19.y and other. | 09:03 |
| masashi910 | ==== | 09:03 |
| pave1 | I reviewed 4.19.88 and started reviewing 4.19.89. | 09:03 |
| masashi910 | pave1: thanks! | 09:04 |
| masashi910 | SZ-san, Wen-san, do you have updates? | 09:04 |
| wens | classify-failed-patches now includes more patches from the stable mailing list | 09:04 |
| wens | final step would be to include all the stable review series | 09:05 |
| wens | also, cip-kernel-sec has seen a few more CVEs | 09:05 |
| wens | will do another round of updates for cip-kernel-sec tomorrow. | 09:05 |
| bwh | I have been working on kernel-sec, including reviewing wens's changes. Also reviewed some y2038 patches upstream. | 09:05 |
| pave1 | Speaking of failed patches... I don't monitor that closely, | 09:06 |
| pave1 | but if there are changes that should be backported, I guess | 09:06 |
| pave1 | I can try to help...? | 09:06 |
| szlin | masashi910: none from me this week. | 09:07 |
| wens | pave1: I saw at least some ext4 patches, though I need to take a closer look | 09:08 |
| masashi910 | wens, bwh, szlin: thank you for your updates! | 09:09 |
| masashi910 | any other updates? | 09:09 |
| masashi910 | 3 | 09:09 |
| masashi910 | 2 | 09:09 |
| masashi910 | 1 | 09:09 |
| masashi910 | #topic Kernel testing | 09:09 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:09 | |
| masashi910 | patersonc: the floor is yours | 09:10 |
| patersonc | Hello | 09:10 |
| patersonc | This week I've seen a few build issues on the stable-rc branches for 4.4 and 4.19. | 09:10 |
| patersonc | Troublesome patches identified and reported to Greg. | 09:10 |
| patersonc | I've enabled arm, arm64 and x86 defconfig builds for the stable-rc testing. | 09:10 |
| patersonc | I've also been working on enabling the Siemens boards in our CI. | 09:10 |
| patersonc | Builds are working okay, but haven't got the x86 board booting yet. | 09:10 |
| patersonc | If anyone is x86 savvy can has a few minutes after the meeting I'd be glad for a few minutes of your time. | 09:10 |
| pave1 | Savvy, I don't know, but I guess I can try to help. | 09:11 |
| wens | I don't know why odd dts patches get backported, while the related dtsi patches get missed :( | 09:11 |
| patersonc | That's it from me. Any questions? | 09:11 |
| patersonc | wens: Indeed | 09:11 |
| pave1 | And sorry for -rt still being on old .yml versions, we can talk about that later, too. | 09:11 |
| patersonc | pave1: Thanks | 09:11 |
| pave1 | wens: Basically Sasha tries to backport _everything_ without checking closely if it is needed or not :-(. | 09:12 |
| masashi910 | patersonc: thanks for working with Greg. By installing the fix, the issues were all solved? | 09:12 |
| wens | pave1: is there a way to tell his bot to not select certain patches (by file path?) | 09:12 |
| szlin | wens: many ppl did that via email... | 09:13 |
| patersonc | masashi910: Issues resolved by dropping patches. | 09:13 |
| wens | szlin: I suppose that didn't work? | 09:13 |
| masashi910 | patersonc: thanks! | 09:13 |
| pave1 | wens: I believe we can take a trip to U.S.A. and take away his computer :-). | 09:13 |
| wens | lol | 09:13 |
| *** suzuki98 has quit IRC | 09:13 | |
| *** kazu has quit IRC | 09:13 | |
| wens | he'll just get a new one | 09:14 |
| pave1 | wens: I guess we can talk to Greg, explain that this causes problems for us, | 09:14 |
| *** kazu has joined #cip | 09:14 | |
| pave1 | wens: and try to get him to do more reasonable patch selection. | 09:14 |
| pave1 | wens: We are not only ones with this problems -- SuSE is not happy, either. | 09:14 |
| patersonc | I guess it's a problem for everyone, not just us | 09:14 |
| wens | for my platform at least, dts/dtsi patches go hand in hand with driver patches | 09:15 |
| patersonc | It just shows the value in us testing the stable release candidates | 09:15 |
| pave1 | wens: I tried to talk to Greg in person, but I guess I did not get the message accross. | 09:15 |
| *** suzuki15 has joined #cip | 09:15 | |
| pave1 | wens: If you want to exclude few .dts files, it should be enough to promise you'll do the stable marking for them. | 09:15 |
| wens | thanks, I'll discuss this with my co-maintainer and see what we can do | 09:15 |
| pave1 | wens: That should actually be quite easy to do. (And does not include forced entry into buildings :-) ) | 09:16 |
| masashi910 | thanks, folks, for working on difficult issues... | 09:16 |
| masashi910 | any other topics? | 09:17 |
| masashi910 | 3 | 09:17 |
| masashi910 | 2 | 09:17 |
| masashi910 | 1 | 09:17 |
| masashi910 | #topic CIP Core | 09:17 |
| *** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:17 | |
| masashi910 | kazu: the floor is yours | 09:17 |
| kazu | hello | 09:17 |
| kazu | I've started the review phase of the 1st package proposal given from Security WG (in cip-dev) | 09:17 |
| kazu | no feedback yet though | 09:17 |
| kazu | i guess some discussions will be needed for the packages | 09:18 |
| kazu | temporally set the due date to 23rd, but please ask me if you want to extend | 09:18 |
| kazu | and sorry for that no technical updates for a few weeks | 09:19 |
| kazu | that's all from me in this week | 09:19 |
| masashi910 | kazu: thank you | 09:19 |
| masashi910 | any other topics? | 09:19 |
| fujita3 | kazu: You may considering to have a meeting | 09:19 |
| kazu | fujita3 yes, sorry for long delay | 09:19 |
| fujita3 | okay | 09:20 |
| kazu | fujita3 i hope i can arrange in this year... | 09:20 |
| fujita3 | kazu: Agreed :-) | 09:20 |
| masashi910 | any other topics? | 09:21 |
| masashi910 | 3 | 09:21 |
| masashi910 | 2 | 09:21 |
| masashi910 | 1 | 09:21 |
| masashi910 | #topic Software update | 09:21 |
| *** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:21 | |
| masashi910 | suzuki: the floor is yours | 09:21 |
| suzuki15 | hi | 09:22 |
| suzuki15 | I have no update in this week, too. Sorry about that. | 09:22 |
| suzuki15 | I'll put a license file into our WG's demo script repository in a couple of days. | 09:22 |
| suzuki15 | That's it from me. | 09:22 |
| masashi910 | Suzuki-san, that's ok. thanks for your report. | 09:22 |
| masashi910 | any other topics? | 09:22 |
| masashi910 | 3 | 09:22 |
| masashi910 | 2 | 09:22 |
| masashi910 | 1 | 09:22 |
| masashi910 | #topic AOB | 09:23 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:23 | |
| masashi910 | 1. Proposed move from Mailman to Groups.io and kernel.org | 09:23 |
| masashi910 | Does any one opposite to move mail server to group.io? | 09:23 |
| patersonc | Nope. assuming that it handles patches okay. | 09:24 |
| masashi910 | patersonc: ok, thanks. | 09:24 |
| masashi910 | 3 | 09:24 |
| masashi910 | 2 | 09:24 |
| masashi910 | 1 | 09:24 |
| kazu | masashi910 i have no strong opinion about this if required features are supported :) | 09:25 |
| patersonc | masashi910: Others may have an opinion though? | 09:25 |
| masashi910 | patersonc: yes, so if there are objections, please speak up | 09:27 |
| masashi910 | currently Neal-san is planning to move if there are no objections. | 09:27 |
| szlin | I think everyone is agree with it? | 09:29 |
| masashi910 | szlin: thanks for your help. | 09:30 |
| masashi910 | So, at this moment, let me assume that the kernel team does not have objections. | 09:30 |
| masashi910 | ok, then let me move to the next | 09:30 |
| masashi910 | 2. When (Feb 27th-Thursday and 28th-Friday) do you prefer for F2F Kernel Team Meeting in Nurnberg during Embedded World 2020? - Doodle Poll | 09:30 |
| masashi910 | for this topic, I created a doodle poll. I will send out the link to that by email after this IRC meeting. | 09:31 |
| masashi910 | any other business? | 09:31 |
| masashi910 | 3 | 09:32 |
| masashi910 | 2 | 09:32 |
| masashi910 | 1 | 09:32 |
| masashi910 | #endmeeting | 09:32 |
| brlogger | Meeting ended Thu Dec 12 09:32:16 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:32 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-12-09.00.html | 09:32 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-12-09.00.txt | 09:32 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2019/12/cip.2019-12-12-09.00.log.html | 09:32 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:32 | |
| szlin | masashi910: thank you!! | 09:32 |
| pave1 | thank you! | 09:32 |
| wens | thanks | 09:32 |
| fujita3 | thank you! | 09:32 |
| masashi910 | thanks all! | 09:32 |
| kazu | masashi910 Thank you | 09:32 |
| pave1 | wens: 4.19 regression... | 09:32 |
| pave1 | wens: fortunately it is "only performance"... | 09:32 |
| suzuki15 | thank you! | 09:33 |
| wens | pave1: I'll send out an email about this to the stable ML later | 09:33 |
| *** suzuki15 has quit IRC | 09:33 | |
| bwh | I notice 4.19 is also missing commit 9a62d20027da, which looks really bad for x86-32 (so I wonder why it wasn't found earlier) | 09:33 |
| pave1 | wens: and unfortunately kpti is "new" (and forced to us by hw issues), so it might be hard. | 09:33 |
| pave1 | wens: If you could cc me at pavel@denx.de... | 09:33 |
| wens | sure | 09:33 |
| pave1 | bwh: I suspect I'm the last one running x86-32 :-). | 09:34 |
| wens | pave1: this server now runs with mitigations=off :) | 09:34 |
| bwh | $ git grep -l X86_32=y | 09:34 |
| bwh | 4.4.y-cip-rt/x86/siemens_i386-rt.config | 09:34 |
| bwh | 4.4.y-cip/x86/siemens_iot2000.config | 09:34 |
| patersonc | bwh: Currently we only build those configs. No testing | 09:35 |
| pave1 | bwh: But that hardware is 64-bit capable, right? | 09:35 |
| bwh | I don't think so | 09:35 |
| pave1 | bwh: aha, oops. | 09:35 |
| pave1 | bwh: that may be some fun in future, because not many people are running x86-32 on next / recent mainline. | 09:36 |
| pave1 | bwh: I do, but I suspect I'm the only one. | 09:37 |
| pave1 | bwh: Testing mainline on our x86-32 boards might be good idea to keep ammount of regressions low. | 09:38 |
| bwh | Might be worthwhile, yes | 09:38 |
| bwh | There are still Debian users that care about i386, but I think they mostly run stable | 09:38 |
| * patersonc waves for x86 help... | 09:39 | |
| pave1 | bwh: Yes, I suspect quite a lot of users run x86-32 on various distribution kernels. | 09:39 |
| pave1 | patersonc: Go ahead. | 09:39 |
| patersonc | Any suggestions as to what is going wrong here? https://lava.ciplatform.org/scheduler/job/8141 | 09:39 |
| patersonc | RFS isn't mounting | 09:39 |
| patersonc | It's using siemens_ipc227e_defconfig | 09:40 |
| patersonc | I don't know if it's a LAVA issue or a config issue | 09:40 |
| patersonc | Mentor have been using vmlinuz images, but it would make things a little easier for me if I can get bzImage working | 09:41 |
| pave1 | Do you have CONFIG_NFS and CONFIG_NFS_ROOT enabled? | 09:41 |
| pave1 | Let me take a look. | 09:41 |
| bwh | I don't see any "IP-Config" message | 09:41 |
| pave1 | exactly. | 09:41 |
| patersonc | Okay | 09:43 |
| patersonc | Here's a healthy job: https://lava.ciplatform.org/scheduler/job/8223 | 09:43 |
| patersonc | Using vmlinuz | 09:43 |
| patersonc | Which has Ip-Config | 09:43 |
| pave1 | CONFIG_IP_PNP_DHCP=y | 09:45 |
| pave1 | It seems to have dhcp enabled. | 09:45 |
| patersonc | Sorry, I need to afk for 15 mins | 09:47 |
| pave1 | I don't see driver for network card. | 09:47 |
| pave1 | I believe driver for network card needs to be enabled in kconfig. | 09:48 |
| *** toscalix has joined #cip | 09:51 | |
| bwh | Yeah, either you need IP_PNP, IP_PNP_DHCP, ROOT_NFS, and the net driver built-in *or* you must use an initramfs with nfsroot support | 09:52 |
| pave1 | Hmm. Bad Siemens. | 09:53 |
| pave1 | https://mall.industry.siemens.com/mall/en/WW/Catalog/Products/10255625#Technical specifications | 09:53 |
| pave1 | It explains that ethernet is 2x gigabit, but not what chip it uses. | 09:54 |
| pave1 | bwh: Yeah. I guess for our testing building driver in is easier. | 09:54 |
| patersonc | Back | 10:01 |
| pave1 | welcome :-) | 10:02 |
| pave1 | See above. | 10:02 |
| pave1 | .yml in -cip-rt: They did not make it, yet. They should make it during the next cycle. | 10:02 |
| pave1 | Would it help testing if I merge them early? | 10:02 |
| patersonc | pave1: It doesn't really matter tbh | 10:03 |
| patersonc | For now it can wait | 10:03 |
| pave1 | patersonc: Ok, good, easier for me :-). | 10:03 |
| patersonc | So it looks like the MAC isn't being set properly: https://lava.ciplatform.org/scheduler/job/8141#L198 | 10:05 |
| patersonc | Apparently this is an issue with the version of LAVA we're using | 10:05 |
| patersonc | But somehow it doesn't affect things when using vmlinuz | 10:05 |
| pave1 | Well, the MAC address - not sure what LAVA is trying to do there. | 10:06 |
| pave1 | But you really need driver for the ethernet, and you don't seem to have one. | 10:06 |
| pave1 | MAC may be secondary problem (or not). | 10:06 |
| patersonc | So how is NFS mounting for the vmlinuz case? | 10:07 |
| patersonc | Does vmlinuz have more things built in? | 10:07 |
| pave1 | Do you have a boot log where it works ok | 10:07 |
| pave1 | ? | 10:07 |
| patersonc | https://lava.ciplatform.org/scheduler/job/8223 | 10:07 |
| pave1 | Thanks, let me take a look. | 10:08 |
| pave1 | [ 3.327006] igb 0000:02:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 20:87:56:b6:21:d0 | 10:08 |
| pave1 | Can you enable CONFIG_IGB in kconfig? | 10:10 |
| pave1 | It is =m, but needs to be =y. | 10:10 |
| patersonc | Ah that's another point | 10:12 |
| patersonc | I haven't included the Kernel modules in LAVA | 10:12 |
| patersonc | s|I|the scripts | 10:12 |
| pave1 | You should not _need_ kernel modules for the boot test. And IGB will need to be built-in anyway due to nfsroot. | 10:14 |
| *** kazu has quit IRC | 10:15 | |
| patersonc | Okay | 10:16 |
| patersonc | I'll try a local build with CONFIG_IGB | 10:16 |
| pave1 | (y) | 10:17 |
| *** toscalix has quit IRC | 10:19 | |
| pave1 | (See you, if the boot problem persists, we can discuss over email). | 10:32 |
| patersonc | Thanks pavel | 10:33 |
| pave1 | You are welcome :_) | 10:38 |
| *** masashi910 has quit IRC | 10:38 | |
| *** rajm has quit IRC | 11:07 | |
| *** fujita3 has quit IRC | 11:12 | |
| *** rajm has joined #cip | 11:30 | |
| patersonc | I'm trying to test, but the internet d/l speed is crazy slow :( | 11:30 |
| *** pave1 has quit IRC | 11:39 | |
| *** masashi910 has joined #cip | 11:58 | |
| *** masashi910 has quit IRC | 13:14 | |
| *** tpollard has quit IRC | 13:18 | |
| *** tpollard has joined #cip | 13:19 | |
| *** tpollard has quit IRC | 14:00 | |
| *** helmut has joined #cip | 14:04 | |
| *** tpollard has joined #cip | 14:05 | |
| patersonc | Including CONFIG_IGB seems to work: https://lava.ciplatform.org/scheduler/job/8267 | 14:11 |
| patersonc | bwh: Are you around? | 14:50 |
| bwh | patersonc: yes | 14:50 |
| patersonc | bwh: I'm having a go at generating the .sources list for the cip-kernel-config repo | 14:53 |
| patersonc | How can I do it for just one config? | 14:53 |
| bwh | You should be able to give that filename as the target for make | 14:54 |
| patersonc | Okay | 14:55 |
| patersonc | it looks like it tries to go to a directory ../kernel | 14:56 |
| patersonc | Do I just hack the Makefile according to my setup? | 14:56 |
| bwh | you can put KSRC=... on the make command line | 14:56 |
| patersonc | Do I also need to set the crosscompiler and arch? | 14:58 |
| patersonc | I guess so | 15:00 |
| patersonc | Looks like it's compiling now | 15:01 |
| patersonc | Thanks bwh | 15:01 |
| bwh | The ARCH is automatically set based on the filename, and CROSS_COMPILE is set automatically based on the ARCH (but it might not guess right) | 15:04 |
| patersonc | Ah okay | 15:05 |
| *** therisen has quit IRC | 16:15 | |
| *** tpollard has quit IRC | 17:05 | |
| *** masashi910 has joined #cip | 22:32 | |
| *** rajm has quit IRC | 23:06 | |
| *** Guest68068 has quit IRC | 23:10 | |
| *** jward has joined #cip | 23:11 | |
| *** jward is now known as Guest3563 | 23:11 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!