ivsc-driver module should not try to build when CONFIG_GPIOLIB_IRQCHIP is disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ivsc-driver (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Confirmed
|
Undecided
|
Unassigned | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Won't Fix
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU justification:
[Impact]
This is encountered on linux kernel derivatives with fewer configuration options enabled.
First time seen on jammy:linux-
During build, it fails with the following error:
...
Building module:
cleaning build area...
make -j1 KERNELRELEASE=
Error! Bad return status for module build on kernel: 5.15.0-1030-kvm (x86_64)
Consult /var/lib/
E: ivsc-driver/
========== /var/lib/
DKMS make.log for ivsc-driver-
Wed Mar 8 23:41:46 UTC 2023
make -C /lib/modules/
make[1]: Entering directory '/usr/src/
CC [M] /var/lib/
LD [M] /var/lib/
CC [M] /var/lib/
LD [M] /var/lib/
CC [M] /var/lib/
/var/lib/
/var/lib/
268 | irq = irq_find_
| ^
/var/lib/
/var/lib/
441 | girq = &ljca_gpio->gc.irq;
| ^
make[2]: *** [scripts/
make[1]: *** [Makefile:1906: /var/lib/
make[1]: Leaving directory '/usr/src/
make: *** [Makefile:43: all] Error 2
=======
./ivsc-
autopkgtest [23:42:00]: test dkms-autopkgtest: -------
autopkgtest [23:42:00]: test dkms-autopkgtest: - - - - - - - - - - results - - - - - - - - - -
dkms-autopkgtest FAIL non-zero exit status 1
autopkgtest [23:42:00]: @@@@@@@
dkms-autopkgtest FAIL non-zero exit status 1
=======
./ipu6-
autopkgtest [23:42:45]: test dkms-autopkgtest: -------
autopkgtest [23:42:46]: test dkms-autopkgtest: - - - - - - - - - - results - - - - - - - - - -
dkms-autopkgtest FAIL non-zero exit status 1
autopkgtest [23:42:46]: @@@@@@@
because CONFIG_
[Fix]
Add a rule to avoid building ivsc-driver when CONFIG_
[Test Plan]
Install a new version of jammy:linux-kvm (1029 for example).
apt install ivsc-driver will fail as described above.
After the fix, it will not be built at all.
Once the package is in proposed, a new adt is triggered against proposed for jammy:linux-kvm.
[Where problems could occur]
Low possibility of new issues.
[Note]
This fix is not scalable in the sense that if configuration name changes, the module has to be changed as well.
tags: | added: sru-20230227 |
Changed in ivsc-driver (Ubuntu): | |
status: | Fix Released → New |
Proposed fix is attached
Tested on linux-kvm-1029 jammy-kvm: ~/ivsc- driver$ sudo dpkg -i intel-vsc- dkms_0~ git202211241536 .70d95269- 0ubuntu0. 22.04.2_ amd64.deb dkms_0~ git202211241536 .70d95269- 0ubuntu0. 22.04.2_ amd64.deb ... 536.70d95269- 0ubuntu0. 22.04.2) ... 536.70d95269- 0ubuntu0. 22.04.2) ... 0~git2022112415 36.70d95269- 0ubuntu0. 22.04.2 DKMS files... dkms/ivsc- driver/ 0~git2022112415 36.70d95269- 0ubuntu0. 22.04.2/ 5.15.0- 1029-kvm/ x86_64/ dkms.conf for module ivsc-driver includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch.
ubuntu@
Selecting previously unselected package intel-vsc-dkms.
(Reading database ... 142281 files and directories currently installed.)
Preparing to unpack intel-vsc-
Unpacking intel-vsc-dkms (0~git202211241
Setting up intel-vsc-dkms (0~git202211241
Loading new ivsc-driver-
Building for 5.15.0-1029-kvm
Building initial module for 5.15.0-1029-kvm
Error! The /var/lib/
This indicates that it should not be built.
Skipped.