[opensuse-factory] Leap 42.3 and drm-kmp-default packages
Hello, I have a system upgraded with zypper dup from Leap 42.2 to 42.3 sometimes in May. Since then I usually updated it to new released snapshots. I just noticed it has several drm-kmp-default packages installed, most for kernels which are no longer installed: user@linux:/lib/modules> rpm -qa |grep drm-kmp-default |sort drm-kmp-default-4.9.30_k4.4.70_1-1.2.x86_64 drm-kmp-default-4.9.30_k4.4.71_1-1.6.x86_64 drm-kmp-default-4.9.31_k4.4.72_1-1.1.x86_64 drm-kmp-default-4.9.33_k4.4.72_1-1.1.x86_64 drm-kmp-default-4.9.33_k4.4.73_1-2.1.x86_64 drm-kmp-default-4.9.33_k4.4.74_19-2.2.x86_64 drm-kmp-default-4.9.33_k4.4.75_1-3.1.x86_64 user@linux:/lib/modules> rpm -qa |grep kernel-default |sort kernel-default-4.4.74-1.1.x86_64 kernel-default-4.4.75-1.1.x86_64 user@linux:/lib/modules> du -sh * 12M 4.4.70-1-default 12M 4.4.71-1-default 12M 4.4.72-1-default 12M 4.4.73-1-default 12M 4.4.74-19-default 200M 4.4.74-1-default 212M 4.4.75-1-default The content of these packages resides in the /lib/modules/<kernel-version> directory. I guess after the related kernel was removed they are not needed anymore. Should they be uninstalled by the purge-kernels.service? Regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
16.07.2017 09:28, dieter пишет:
Hello,
I have a system upgraded with zypper dup from Leap 42.2 to 42.3 sometimes in May. Since then I usually updated it to new released snapshots.
I just noticed it has several drm-kmp-default packages installed, most for kernels which are no longer installed: user@linux:/lib/modules> rpm -qa |grep drm-kmp-default |sort drm-kmp-default-4.9.30_k4.4.70_1-1.2.x86_64 drm-kmp-default-4.9.30_k4.4.71_1-1.6.x86_64 drm-kmp-default-4.9.31_k4.4.72_1-1.1.x86_64 drm-kmp-default-4.9.33_k4.4.72_1-1.1.x86_64 drm-kmp-default-4.9.33_k4.4.73_1-2.1.x86_64 drm-kmp-default-4.9.33_k4.4.74_19-2.2.x86_64 drm-kmp-default-4.9.33_k4.4.75_1-3.1.x86_64
user@linux:/lib/modules> rpm -qa |grep kernel-default |sort kernel-default-4.4.74-1.1.x86_64 kernel-default-4.4.75-1.1.x86_64
user@linux:/lib/modules> du -sh * 12M 4.4.70-1-default 12M 4.4.71-1-default 12M 4.4.72-1-default 12M 4.4.73-1-default 12M 4.4.74-19-default 200M 4.4.74-1-default 212M 4.4.75-1-default
The content of these packages resides in the /lib/modules/<kernel-version> directory. I guess after the related kernel was removed they are not needed anymore. Should they be uninstalled by the purge-kernels.service?
In general KMP is supposed to be upward compatible, so KMP built for 4.4.70 should still run under 4.4.75. So blindly removing them is wrong as well. I'm not even sure what the right decision matrix would be - keep last 2 KMP for each kernel version? Keep the oldest common KMP and the newest one? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 16 Jul 2017 09:55:26 +0300 Andrei Borzenkov wrote:
The content of these packages resides in the /lib/modules/<kernel-version> directory. I guess after the related kernel was removed they are not needed anymore. Should they be uninstalled by the purge-kernels.service?
In general KMP is supposed to be upward compatible, so KMP built for 4.4.70 should still run under 4.4.75. So blindly removing them is wrong as well. I'm not even sure what the right decision matrix would be - keep last 2 KMP for each kernel version? Keep the oldest common KMP and the newest one?
But e.g. drm-kmp-default-4.9.33_k4.4.74_19 contains only files under /lib/modules/4.4.74-19-default/updates/drivers/gpu/drm: rpm -ql drm-kmp-default-4.9.33_k4.4.74_19 /lib/modules/4.4.74-19-default /lib/modules/4.4.74-19-default/updates /lib/modules/4.4.74-19-default/updates/drivers /lib/modules/4.4.74-19-default/updates/drivers/gpu /lib/modules/4.4.74-19-default/updates/drivers/gpu/drm ... My understanding is that modules located in another kernel-version directory would not be considered by depmod and they would also not be loaded by modprobe automatically, even if they are compatible, maybe except the full pathname would be supplied. If modules from other kernel versions can be loaded this seems quite confusing to me. E.g. on this system I have 6 versions of amdgpu.ko updates installed: user@linux:/lib/modules> find . -name amdgpu.ko |grep t/updates/ ./4.4.73-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.74-19-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.75-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.72-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.70-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.71-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko I assume by default the one from the directory of the currently running kernel is used. But if there is not yet one for this kernel (e.g. there was a kernel update but the related KMP was not provided yet) - which one would be used? Regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 16 Jul 2017 10:03:22 +0200, dieter wrote:
On Sun, 16 Jul 2017 09:55:26 +0300 Andrei Borzenkov wrote:
The content of these packages resides in the /lib/modules/<kernel-version> directory. I guess after the related kernel was removed they are not needed anymore. Should they be uninstalled by the purge-kernels.service?
In general KMP is supposed to be upward compatible, so KMP built for 4.4.70 should still run under 4.4.75. So blindly removing them is wrong as well. I'm not even sure what the right decision matrix would be - keep last 2 KMP for each kernel version? Keep the oldest common KMP and the newest one?
But e.g. drm-kmp-default-4.9.33_k4.4.74_19 contains only files under /lib/modules/4.4.74-19-default/updates/drivers/gpu/drm:
rpm -ql drm-kmp-default-4.9.33_k4.4.74_19 /lib/modules/4.4.74-19-default /lib/modules/4.4.74-19-default/updates /lib/modules/4.4.74-19-default/updates/drivers /lib/modules/4.4.74-19-default/updates/drivers/gpu /lib/modules/4.4.74-19-default/updates/drivers/gpu/drm ...
My understanding is that modules located in another kernel-version directory would not be considered by depmod and they would also not be loaded by modprobe automatically, even if they are compatible, maybe except the full pathname would be supplied.
If modules from other kernel versions can be loaded this seems quite confusing to me.
E.g. on this system I have 6 versions of amdgpu.ko updates installed: user@linux:/lib/modules> find . -name amdgpu.ko |grep t/updates/ ./4.4.73-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.74-19-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.75-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.72-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.70-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko ./4.4.71-1-default/updates/drivers/gpu/drm/amd/amdgpu/amdgpu.ko
I assume by default the one from the directory of the currently running kernel is used. But if there is not yet one for this kernel (e.g. there was a kernel update but the related KMP was not provided yet) - which one would be used?
The KMP usually creates weak-update links if available. It works only when the kABI is compatible. For Leap, once after the release, the kABI is fixed, thus usually no multi-version is needed for KMP. And, I thought we disabled the multi-version for KMP since it caused problems. Michal? Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dne 17.7.2017 v 08:35 Takashi Iwai napsal(a):
On Sun, 16 Jul 2017 10:03:22 +0200, The KMP usually creates weak-update links if available. It works only when the kABI is compatible. For Leap, once after the release, the kABI is fixed, thus usually no multi-version is needed for KMP.
And, I thought we disabled the multi-version for KMP since it caused problems. Michal?
The plan is to change this with Tumbleweed / SLE 15 / Leap 15.0. But thanks for the reminder, I should commit the change finally :D. Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
dieter -
Michal Marek -
Takashi Iwai