Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uninstalling / disabling #145

Closed
devedse opened this issue Mar 16, 2024 · 2 comments
Closed

Uninstalling / disabling #145

devedse opened this issue Mar 16, 2024 · 2 comments

Comments

@devedse
Copy link

devedse commented Mar 16, 2024

Hello everyone,

Pardon me for maybe being a noob in DKMS modules, but for testing purposes on my machine I'd like to completely disable the sr-iov module. (From what I read is that I don't actually need this for hardware acceleration inside LXC containers).

So I'm looking for a guide to either completely uninstall it, or maybe a simpler version, to temporarily disable it.
(I can try some things myself but I want to know if for example modifying the boot parameters is good enough to disable it or if I should also uninstall the DKMS module)

@devedse
Copy link
Author

devedse commented Mar 19, 2024

Copied from another post (#137 (comment)):

brussig-tud

Just dkms remove'ing the module will be enough to disable virtual functions temporarily. I did not have to do anything else to get rid of the memory leak, which pretty much proves that the i915-sriov driver is the culprit. You can always just dkms install it again later on if you need virtual functions back.

devedse

So I don't need to remove this from grub?:
intel_iommu=on i915.enable_guc=3 i915.max_vfs=7

And also don't need to remove this file:
/etc/sysfs.conf

brussig-tud

@devedse The "vanilla" i915 driver will ignore the max_vfs kernel boot parameter, and the sysfs entry will just silently fail if the driver does not provide the endpoints, so yeah, you can leave them in place.

I don't remember whether just not creating VFs via sysfs was enough to fix the memory leak, or if you also had to set max_vfs=0, or if you had to completely disable GuC scheduling altogether (which should also cause this driver to not leak memory). You can try narrowing it down further like this, but removing the DKMS module will surely prove or disprove the hypothesis that this driver is causing your memory leak and you can leave the other things there in case you need them later.

@devedse devedse closed this as completed Mar 19, 2024
@devedse
Copy link
Author

devedse commented Mar 20, 2024

Apparently after the dkms remove you also need to reinstall the kernel since the "i915.ko" module has been removed.

I did this as follows:

dpkg --search /usr/lib/modules/<kernel version directory>

apt-get --reinstall install proxmox-kernel-6.5.13-1-pve-signed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant