Re: [OS-BUILD PATCH] redhat: configs: disable CRYPTO_SM modules
From: Patrick Talbert on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1291#note_643742260 Acked-by: Patrick Talbert (via approve button) ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
❌ FAIL: Test report for kernel 5.13.8-200.fc34 (fedora-34)
Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.13.8-200.fc34 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=73289022 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: ppc64le: ❌ LTP aarch64: ❌ LTP All kernel binaries, config files, and logs are available for download here: https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/08/05/348187183 Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' __ Hardware testing We booted each kernel and ran the following tests: aarch64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng Host 2: ✅ Boot test ✅ Reboot test ✅ ACPI table test ❌ LTP ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon ppc64le: Host 1: ✅ Boot test ✅ Reboot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ Storage: swraid mdadm raid_module test 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: lvm device-mapper test - upstream 🚧 ✅ storage: software RAID testing Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ Reboot test ❌ LTP ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ⚡⚡⚡ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon s390x: Host 1: ✅ Boot test ✅ Reboot test ✅ LTP ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ✅ Boot test ✅ Reboot test ✅ Storage: swraid mdadm raid_module test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ⚡⚡⚡ stress: stress-ng x86_64: Host 1: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test ⚡⚡⚡ Reboot test ⚡⚡⚡ xfstests - ext4 ⚡⚡⚡ xfstests - xfs ⚡⚡⚡ xfstests - nfsv4.2 ⚡⚡⚡ Storage: swraid mdadm raid_module test 🚧 ⚡⚡⚡ xfstests - btrfs 🚧 ⚡⚡⚡ xfstests - cifsv3.11 🚧 ⚡⚡⚡ Storage blktests 🚧 ⚡⚡⚡ Storage block - filesystem fio test 🚧 ⚡⚡⚡ Storage block - queue scheduler test 🚧 ⚡⚡⚡ Storage nvme - tcp 🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream 🚧 ⚡⚡⚡ storage: software RAID testing 🚧 ⚡⚡⚡ stress: stress-ng Host 2: ✅ Boot test ✅ Reboot test ✅ ACPI table test ✅ LTP ✅ CIFS Connectathon ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ❌ xarray-idr-radixtree-test 🚧 ✅ NFS Connectathon Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this arc
Re: [OS-BUILD PATCH 0/0] [redhat] New configs in sound/soc
From: Patrick Talbert on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1220#note_643854955 Done. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCH 0/0] [redhat] New configs in sound/soc
From: Patrick Talbert on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1220#note_643898639 The problem now is that CONFIG_SND_SOC_INTEL_SOF_CS42L42_MACH selects all of the following: SND_SOC_CS42L42 SND_SOC_MAX98357A SND_SOC_DMIC SND_SOC_HDAC_HDMI SND_SOC_INTEL_HDA_DSP_COMMON SND_SOC_INTEL_SOF_MAXIM_COMMON This is a problem because redhat/configs/ark/generic/CONFIG_SND_SOC_CS42L42 explicitly disables that option and so there is a mismatch. The simple solution is to remove the redhat/configs/ark/generic/CONFIG_SND_SOC_CS42L42 file so I've pushed a new version. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCH 0/0] [redhat] New configs in sound/soc
From: Jaroslav Kysela on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1220#note_644226453 Thank you Patrick. I already realized that the ARK ALSA / SoundWire configs are really out of sync against RHEL 8.5 (missing SoundWire drivers and many Intel SOF driver related options). I tried to review all options one-by-one and the result is here: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1294 I appreciate any comments and I will try to fix build errors when CKI fails. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: fedpkg clone -a kernel failed
On Thu, 05 Aug 2021 02:33:57 -
"Sampson Fung" wrote:
> rpm -qa and dnf list installed return the same result.
Thanks for the info, looks like you are in business.
> Regarding the kernel.spec issue, I reported it as
> https://bugzilla.redhat.com/show_bug.cgi?id=1990129
>
> Change the below from 1 to 0 allow rpmbuild to finish building the
> kernel RPM packages.
>
> diff kernel.spec.dist kernel.spec.works
> 202c202
> < %define with_configchecks %{?_without_configchecks:0}
> %{?!_without_configchecks:1} ---
> > %define with_configchecks %{?_without_configchecks:0}
> > %{?!_without_configchecks:0}
It might get accepted, though the policy of the fedora kernel team has
been that anyone who builds their own kernels is on their own. It
makes sense because there are so many combinatorial possibilities.
But maybe it has changed.
> If I want to learn how to read kernel.spec, where should I start?
Well, the first thing is to understand the spec file organization.
https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Packagers_Guide/sect-Packagers_Guide-Creating_a_Basic_Spec_File.html
I'm not aware of any spec file documentation specific to the kernel. I
think it is institutional awareness within the fedora kernel team. You
can create a new thread here on the kernel list with something like
"can you point me to documentation of the kernel spec file" as the
subject, and maybe someone with more knowledge than me will give you
links to such documentation, if it exists.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Can you point me to documentation of the kernel spec file?
I am new to kernel building - I just managed to finishing building my first kernel with the help I can got here. I want to build with rpmbuild, Fedora's kernel source RPMs, and the contained kernel.spec under Fedora. I want to learn reading the kernel.spec file. Please help by pointing me where I can start reading! ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
