Bug#981186: linux: Enable CMN-600 interconnect on arm64
Control: tags -1 moreinfo Hi Wookey, Le 2021-01-27 12:57, Wookey a écrit : > Source: linux > Version: Please enable ARM CMN-600 power management on arm64 > Severity: normal > Tags: patch > > Current arm hardware such as graviton2 (AWS arm64 hardware) has > 'Coherent Mesh Network' interconnect (between components in a > soc). It's important that support for this is built in the kernel so > it can be used. > > This requires CONFIG_ARM_CMN=y Does it really have to be built-in instead of being provided as a module? Last I checked, Fedora and Ubuntu provide it as a module. > This explains what the feature is: > https://www.arm.com/products/silicon-ip-system/corelink-interconnect/cmn-600 > Graviton2: > https://www.anandtech.com/show/15578/cloud-clash-amazon-graviton2-arm-against-intel-and-amd > > patch attached: > --- debian/config/arm64/config~ 2021-01-27 04:34:51.359552398 + > +++ debian/config/arm64/config2021-01-27 04:53:11.922998842 + > @@ -942,6 +942,7 @@ > CONFIG_ARM_CCI400_PMU=y > CONFIG_ARM_CCI5xx_PMU=y > CONFIG_ARM_CCN=y > +CONFIG_ARM_CMN=y > CONFIG_QCOM_L2_PMU=y > CONFIG_QCOM_L3_PMU=y > CONFIG_XGENE_PMU=y > --- debian/config/arm64/config~ 2021-01-27 04:34:51.359552398 + > +++ debian/config/arm64/config2021-01-27 04:53:11.922998842 + > @@ -942,6 +942,7 @@ > CONFIG_ARM_CCI400_PMU=y > CONFIG_ARM_CCI5xx_PMU=y > CONFIG_ARM_CCN=y > +CONFIG_ARM_CMN=y > CONFIG_QCOM_L2_PMU=y > CONFIG_QCOM_L3_PMU=y > CONFIG_XGENE_PMU=y Cheers, Vincent signature.asc Description: PGP signature
Processed: Re: Bug#981186: linux: Enable CMN-600 interconnect on arm64
Processing control commands: > tags -1 moreinfo Bug #981186 [src:linux] linux: Enable CMN-600 interconnect on arm64 Added tag(s) moreinfo. -- 981186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#981186: linux: Enable CMN-600 interconnect on arm64
Processing control commands: > tags -1 moreinfo Bug #981186 [src:linux] linux: Enable CMN-600 interconnect on arm64 Ignoring request to alter tags of bug #981186 to the same tags previously set -- 981186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#946791: io.weight cannot be enabled in recent Debian kernel package
Control: retitle -1 Please enable CONFIG_IOSCHED_BFQ=y On Thu, 26 Dec 2019 23:17:13 +0900 Ryutaroh Matsumoto wrote: > Source: linux > Followup-For: Bug #946791 > Control: tags -1 + patch > > Dear Maintainer, > > I reported that IOWeight config item in systemd has no effect > on recent Debian kernels. I found the root cause. > io.weight was changed to io.bfq.weight, and recent systemd sets > values of IOWeight to io.bfq.weight as > > https://github.com/systemd/systemd/commit/2dbc45aea747f25cc1c3848fded2ec0062f96bcf > > For io.bfq.weight to appear in cgroup v2 filesystem, the bfq kernel > module must be loaded. Addition of "bfq" to /etc/initramfs- tools/modules > solved this issue. Since the systemd needs bfq module to be loaded, > changing CONFIG_IOSCHED_BFQ=m to CONFIG_IOSCHED_BFQ=y in kernel config > seems suitable. > > If the Debian kernel team considers this issue to be handled by another > package, e.g. initramfs-tools or systemd, please reassign this. > If this issue is considered not being a bug, please close this. > Fwiw, the fedora kernel in F33 uses # grep CONFIG_IOSCHED_BFQ /boot/config-5.10.22-200.fc33.x86_64 CONFIG_IOSCHED_BFQ=y I think using CONFIG_IOSCHED_BFQ=y instead of loading it via initramfs- tools makes more sense (assuming it is safe to enable). Regards, Michael signature.asc Description: This is a digitally signed message part
Processed: Re: io.weight cannot be enabled in recent Debian kernel package
Processing control commands: > retitle -1 Please enable CONFIG_IOSCHED_BFQ=y Bug #946791 [linux] io.weight cannot be enabled in recent Debian kernel package Changed Bug title to 'Please enable CONFIG_IOSCHED_BFQ=y' from 'io.weight cannot be enabled in recent Debian kernel package'. -- 946791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#981186: linux: Enable CMN-600 interconnect on arm64
On 2021-03-17 14:52 +0100, Vincent Blut wrote: > Control: tags -1 moreinfo > > Hi Wookey, > > Le 2021-01-27 12:57, Wookey a écrit : > > Source: linux > > Version: Please enable ARM CMN-600 power management on arm64 > > Severity: normal > > Tags: patch > > > > Current arm hardware such as graviton2 (AWS arm64 hardware) has > > 'Coherent Mesh Network' interconnect (between components in a > > soc). It's important that support for this is built in the kernel so > > it can be used. > > > > This requires CONFIG_ARM_CMN=y > > Does it really have to be built-in instead of being provided as a module? > Last I > checked, Fedora and Ubuntu provide it as a module. No it should really be a module. Perf is driven from userspace so you never need to use it before modules can be loaded. I just did it like this because the other settings here are set as built-ins too and this seemed less disruptive. (If we make it a module we'll need to make sure it gets included in the right module package - I'm not sure if that need tweaking somewhere else in the build system) I see that CONFIG_THUNDERX2_PMU=y CONFIG_ARM_SMMU_V3_PMU=y are also set as builtins. That's probably wrong too. This should be a module (whic is the upstream default - I'm not sure why it's coming out as a built-in in the debian build): CONFIG_THUNDERX2_PMU=m I'm not sure about CONFIG_ARM_SMMU_V3_PMU=y as it's an architectureal feature. Best to leave it as a built-in for now. I also checked the state of the other perf configs with the arm kernel team and got feedback that we have all the ones that should sensibly be set set once CONFIG_ARM_CMN=m and CONFIG_THUNDERX2_PMU=m is added Upstream enables CONFIG_FSL_IMX8_DDR_PMU=m by default too. IMX8 hardware is available so we should probably turn this on too Do you want me to knock up a patch for this or is that enough info? Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#981186: linux: Enable CMN-600 interconnect on arm64
Le 2021-03-17 15:49, Wookey a écrit : > On 2021-03-17 14:52 +0100, Vincent Blut wrote: > > Control: tags -1 moreinfo > > > > Hi Wookey, > > > > Le 2021-01-27 12:57, Wookey a écrit : > > > Source: linux > > > Version: Please enable ARM CMN-600 power management on arm64 > > > Severity: normal > > > Tags: patch > > > > > > Current arm hardware such as graviton2 (AWS arm64 hardware) has > > > 'Coherent Mesh Network' interconnect (between components in a > > > soc). It's important that support for this is built in the kernel so > > > it can be used. > > > > > > This requires CONFIG_ARM_CMN=y > > > > Does it really have to be built-in instead of being provided as a module? > > Last I > > checked, Fedora and Ubuntu provide it as a module. > > No it should really be a module. Perf is driven from userspace so you > never need to use it before modules can be loaded. Agreed. > I just did it like this because the other settings here are set as > built-ins too and this seemed less disruptive. (If we make it a module > we'll need to make sure it gets included in the right module package - > I'm not sure if that need tweaking somewhere else in the build system) > > I see that > CONFIG_THUNDERX2_PMU=y > CONFIG_ARM_SMMU_V3_PMU=y > are also set as builtins. That's probably wrong too. It seems your arm64 kernel config deviates from the one we provide in Debian. CONFIG_THUNDERX2_PMU is compiled as a module while CONFIG_ARM_SMMU_V3_PMU is not set, at least in linux 5.10.19-1. > […] > I also checked the state of the other perf configs with the arm kernel team > and got feedback that we have all the ones that should sensibly be set set > once > CONFIG_ARM_CMN=m > and > CONFIG_THUNDERX2_PMU=m > is added This means updating the arm64 kernel config to only include ARM_CMN as a module. To me it is acceptable for Bullseye as this seems uncontroversial, but note that I can't speak for the kernel team. > Upstream enables > CONFIG_FSL_IMX8_DDR_PMU=m > by default too. IMX8 hardware is available so we should probably turn this on > too Contrary to Ubuntu, we do not provide support for the i.MX8M SoC family, so enabling this option in the arm64 kernel config is not an option, right? signature.asc Description: PGP signature
Bug#981186: linux: Enable CMN-600 interconnect on arm64
On 2021-03-17 19:43 +0100, Vincent Blut wrote: > Le 2021-03-17 15:49, Wookey a écrit : > > On 2021-03-17 14:52 +0100, Vincent Blut wrote: > > > Le 2021-01-27 12:57, Wookey a écrit : > > > > Version: Please enable ARM CMN-600 power management on arm64 > > > > > > > > This requires CONFIG_ARM_CMN=y > > > > > > Does it really have to be built-in instead of being provided as a module? > > > Last I > > > checked, Fedora and Ubuntu provide it as a module. > > > > No it should really be a module. Perf is driven from userspace so you > > never need to use it before modules can be loaded. > > Agreed. > > I see that > > CONFIG_THUNDERX2_PMU=y > > CONFIG_ARM_SMMU_V3_PMU=y > > are also set as builtins. That's probably wrong too. > > It seems your arm64 kernel config deviates from the one we provide in Debian. > CONFIG_THUNDERX2_PMU is compiled as a module while CONFIG_ARM_SMMU_V3_PMU is > not set, at least in linux 5.10.19-1. Hmm. I was looking at the (built, with CONFIG_ARM_CMN=y) sources for 5.10.9-1 and the (unbuilt) sources for 5.10.19-1. So yes, slightly different and the built version is not up to date any more. If we already have CONFIG_THUNDERX2_PMU=m already then that's great (Ah yes - that's the upstream default). Adding CONFIG_ARM_SMMU_V3_PMU=m would be good too. Adding it as a module should be pretty harmless then at least it's available? I'll set off a build now to check it works. > > […] > > > I also checked the state of the other perf configs with the arm kernel team > > and got feedback that we have all the ones that should sensibly be set set > > once > > CONFIG_ARM_CMN=m > > and > > CONFIG_THUNDERX2_PMU=m > > is added > > This means updating the arm64 kernel config to only include ARM_CMN as a > module. > To me it is acceptable for Bullseye as this seems uncontroversial, but note > that > I can't speak for the kernel team. Will you ask them, or should I? It seems like prodding someone would be good as this was filed back on 27th jan and there have been uploads since, so I guess no-one has noticed till now. > > Upstream enables > > CONFIG_FSL_IMX8_DDR_PMU=m > > by default too. IMX8 hardware is available so we should probably turn this > > on too > > Contrary to Ubuntu, we do not provide support for the i.MX8M SoC family, > so enabling this option in the arm64 kernel config is not an option, right? Ah OK. I didn't realise IMX8 was not enabled in the debian kernel (A subject for a different bug). In that case, no this is not appropriate. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#981186: linux: Enable CMN-600 interconnect on arm64
Le 2021-03-17 19:24, Wookey a écrit : > On 2021-03-17 19:43 +0100, Vincent Blut wrote: > > Le 2021-03-17 15:49, Wookey a écrit : > > > On 2021-03-17 14:52 +0100, Vincent Blut wrote: > > > > Le 2021-01-27 12:57, Wookey a écrit : > > > > > Version: Please enable ARM CMN-600 power management on arm64 > > > > > > > > > > This requires CONFIG_ARM_CMN=y > > > > > > > > Does it really have to be built-in instead of being provided as a > > > > module? Last I > > > > checked, Fedora and Ubuntu provide it as a module. > > > > > > No it should really be a module. Perf is driven from userspace so you > > > never need to use it before modules can be loaded. > > > > Agreed. > > > > I see that > > > CONFIG_THUNDERX2_PMU=y > > > CONFIG_ARM_SMMU_V3_PMU=y > > > are also set as builtins. That's probably wrong too. > > > > It seems your arm64 kernel config deviates from the one we provide in > > Debian. > > CONFIG_THUNDERX2_PMU is compiled as a module while CONFIG_ARM_SMMU_V3_PMU is > > not set, at least in linux 5.10.19-1. > > Hmm. I was looking at the (built, with CONFIG_ARM_CMN=y) sources for > 5.10.9-1 and the (unbuilt) sources for 5.10.19-1. So yes, slightly > different and the built version is not up to date any more. > > If we already have CONFIG_THUNDERX2_PMU=m already then that's great > (Ah yes - that's the upstream default). Adding > CONFIG_ARM_SMMU_V3_PMU=m would be good too. Adding it as a module > should be pretty harmless then at least it's available? I'll set off a > build now to check it works. Enabling ARM_SMMU_V3_PMU as a module should be harmless, indeed. > > > […] > > > > > I also checked the state of the other perf configs with the arm kernel > > > team > > > and got feedback that we have all the ones that should sensibly be set > > > set once > > > CONFIG_ARM_CMN=m > > > and > > > CONFIG_THUNDERX2_PMU=m > > > is added > > > > This means updating the arm64 kernel config to only include ARM_CMN as a > > module. > > To me it is acceptable for Bullseye as this seems uncontroversial, but note > > that > > I can't speak for the kernel team. > > Will you ask them, or should I? I can send merge requests to enable ARM_CMN and ARM_SMMU_V3_PMU if you wish. > It seems like prodding someone would be good as this was filed back on 27th > jan and there have been uploads since, so I guess no-one has noticed till now. I have been contributing for some time to help the kernel team, but I must admit I didn't notice this one (and probably many others). > > > Upstream enables > > > CONFIG_FSL_IMX8_DDR_PMU=m > > > by default too. IMX8 hardware is available so we should probably turn > > > this on too > > > Contrary to Ubuntu, we do not provide support for the i.MX8M SoC family, > > so enabling this option in the arm64 kernel config is not an option, right? > > Ah OK. I didn't realise IMX8 was not enabled in the debian kernel (A > subject for a different bug). In that case, no this is not > appropriate. I wanted to work on this a few months ago, but sadly I was unable to obtain a i.MX8 SBC. > Wookey > -- > Principal hats: Linaro, Debian, Wookware, ARM > http://wookware.org/ Cheers, Vincent signature.asc Description: PGP signature
Bug#942173: firmware-amd-graphics: seg fault with ati picasso grafic card and libqt5 software
tags 942173 moreinfo stop > Version: 20190717-2~bpo10+1 This should have seen quite some updates since, is this still reproducible? Sorry for the late reply, thank you for your report!
Processed: Re: firmware-amd-graphics: seg fault with ati picasso grafic card and libqt5 software
Processing commands for cont...@bugs.debian.org: > tags 942173 moreinfo Bug #942173 [firmware-amd-graphics] firmware-amd-graphics: seg fault with ati picasso grafic card and libqt5 software Added tag(s) moreinfo. > stop Stopping processing here. Please contact me if you need assistance. -- 942173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949973: firmware-realtek: kernel error caught
tags 949973 moreinfo stop > Version: 20190114-2 Can you still reproduce with newest testing? Sorry for the late reply and thank you for your report. -- maks
Processed: Re: firmware-realtek: kernel error caught
Processing commands for cont...@bugs.debian.org: > tags 949973 moreinfo Bug #949973 [firmware-realtek] firmware-realtek: kernel error caught Added tag(s) moreinfo. > stop Stopping processing here. Please contact me if you need assistance. -- 949973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ts
Processing commands for cont...@bugs.debian.org: > tags 984874 pending Bug #984874 [firmware-amd-graphics] Upgrading via apt-get results in module amdgpu 'possible missing firmware' errors Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 984874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
