Bug 1829021
| Summary: | Error! Bad return status for module build on kernel: 5.6.6-200.fc31.x86_64 (x86_64) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | customercare |
| Component: | dkms | Assignee: | Simone Caronni <negativo17> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | mhjacks, negativo17 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | dkms-2.8.2-1.fc31 dkms-2.8.2-1.fc32 dkms-2.8.3-2.el8 dkms-2.8.3-2.el7 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-12 00:52:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Bootresult: Booting worked with 5.6.6 .. no idea what will not function as a result of this bug. This looks like it might be related to https://github.com/Bumblebee-Project/bbswitch/commit/0b11f33a9f71d8400a8baa7310d4fb9980ab560b, Do you agree? If that's the case the issue is with bbswitch and not with DKMS, and would best be fixed by a release in bbswitch. there is no bbswitch package(or it's not named that way) and we should keep track of it. DKMS seems the right place to do this, as it's involved. And, yes the bug looks like to be fixed inside bbswitch. FEDORA-2020-11149b8db4 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-11149b8db4 FEDORA-EPEL-2020-86a69a0d33 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 FEDORA-EPEL-2020-2a4c2c399e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e FEDORA-2020-bc1ecad001 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bc1ecad001 FEDORA-2020-bc1ecad001 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bc1ecad001` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bc1ecad001 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-11149b8db4 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-11149b8db4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-11149b8db4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-2a4c2c399e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-86a69a0d33 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-bc1ecad001 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-11149b8db4 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-bc1ecad001 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-2a4c2c399e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e FEDORA-EPEL-2020-86a69a0d33 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 FEDORA-EPEL-2020-2a4c2c399e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-86a69a0d33 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-2a4c2c399e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e FEDORA-EPEL-2020-86a69a0d33 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 FEDORA-EPEL-2020-86a69a0d33 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-86a69a0d33 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-2a4c2c399e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2a4c2c399e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2020-2a4c2c399e has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2020-86a69a0d33 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: While upgrading to FC31 the following kernel-BuildBug came up: Ausgeführtes Scriptlet: kernel-core-5.6.6-200.fc31.x86_64 6140/6140 dkms: running auto installation service for kernel 5.6.6-200.fc31.x86_64 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area.... make -j4 KERNELRELEASE=5.6.6-200.fc31.x86_64 KVERSION=5.6.6-200.fc31.x86_64....(bad exit status: 2) Error! Bad return status for module build on kernel: 5.6.6-200.fc31.x86_64 (x86_64) Consult /var/lib/dkms/bbswitch/0.8.0/build/make.log for more information. Done. dkms: running auto installation service for kernel 5.6.6-200.fc31.x86_64 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area.... make -j4 KERNELRELEASE=5.6.6-200.fc31.x86_64 KVERSION=5.6.6-200.fc31.x86_64....(bad exit status: 2) Error! Bad return status for module build on kernel: 5.6.6-200.fc31.x86_64 (x86_64) Consult /var/lib/dkms/bbswitch/0.8.0/build/make.log for more information. Done. The Laptop this upgrade was done on, has a bumblebee setup for a nvidia 3d-accelerator. As the buildlog show, it's not inside the nvidia part, so we reported it here. Version-Release number of selected component (if applicable): 5.6.6 How reproducible: As the nature of systemupgrades is .. not reproduceable. Additional Infos: DKMS make.log for bbswitch-0.8.0 for kernel 5.6.6-200.fc31.x86_64 (x86_64) Di 28. Apr 19:43:01 CEST 2020 make -C /lib/modules/5.6.6-200.fc31.x86_64/build M="$(pwd)" modules make[1]: Verzeichnis „/usr/src/kernels/5.6.6-200.fc31.x86_64“ wird betreten CC [M] /var/lib/dkms/bbswitch/0.8.0/build/bbswitch.o /var/lib/dkms/bbswitch/0.8.0/build/bbswitch.c: In Funktion »bbswitch_init«: /var/lib/dkms/bbswitch/0.8.0/build/bbswitch.c:460:63: Fehler: Übergabe des Arguments 4 von »proc_create« von inkompatiblem Zeigertyp [-Werror=incompatible-pointer-types] 460 | acpi_entry = proc_create("bbswitch", 0664, acpi_root_dir, &bbswitch_fops); | ^~~~~~~~~~~~~~ | | | struct file_operations * In Datei, eingebunden von ./include/acpi/acpi_bus.h:83, von ./include/linux/acpi.h:32, von /var/lib/dkms/bbswitch/0.8.0/build/bbswitch.c:32: ./include/linux/proc_fs.h:64:24: Anmerkung: »const struct proc_ops *« erwartet, aber Argument hat Typ »struct file_operations *« 64 | struct proc_dir_entry *proc_create(const char *name, umode_t mode, struct proc_dir_entry *parent, const struct proc_ops *proc_ops); | ^~~~~~~~~~~ cc1: Einige Warnungen werden als Fehler behandelt make[2]: *** [scripts/Makefile.build:268: /var/lib/dkms/bbswitch/0.8.0/build/bbswitch.o] Fehler 1 make[1]: *** [Makefile:1683: /var/lib/dkms/bbswitch/0.8.0/build] Fehler 2 make[1]: Verzeichnis „/usr/src/kernels/5.6.6-200.fc31.x86_64“ wird verlassen make: *** [Makefile:13: default] Fehler 2