Hi :) i use latest nvidia drivers on my gentoo linux with latest gentoo-kernel with Nvidia GTX 1060 card. i had X86_KERNEL_IBT enabled in the kernel, the warning states that the driver might not load, but it did.. i saw it on lsmod, and X worked, so ignored the warning. i tried to convert video files to x265 using ffmpeg with nvenc encoder, this is the command that i execute: ffmpeg -threads 9 -hwaccel cuda -nostdin -i "$file" -c:v libx265 -crf 20 -preset slow "$file.mkv" so i use cuda with nvenc, now when the X86_KERNEL_IBT was enabled, ffmpeg told me that my graphics card doesn't have the minimal requirements for nvenc. and i believed him for a while. today I tried to remove that from the kernel, and ffmpeg works perfectly and very fast with hardware acceleration. so maybe to fix the documentation that there are also known issues with nvenc encoders ? this is my emerge --info: https://bpa.st/PYVQ Reproducible: Always
Repost emerge --info? Be useful to know what CPU you have. Please don't use paste services given these expire, should either attach or inline a post. The primary reasons I left that warning is because: 1. I don't have a cpu that can use IBT to test (tigerlake or newer, I only have a skylake) 2. there's still *tons* of build warnings from the kernel's objtool when building against a kernel with IBT enabled, unsure if it's an indicator of issues or if it can be ignored, e.g.: nvidia.o: warning: objtool: _nv016993rm+0x2c: missing int3 after ret 3. there's been confusion as to which versions are *really* fixed (if any) given changelogs may have mixed things up with USE=kernel-open's fixes, which is fine because it's using modern gcc, but nvidia been typically using a old gcc for its blob which does not support this tl;dr I'd like someone that actually has IBT in-use (not just the option enabled) to confirm which branches are still broken or not (nvidia-drivers:0/390 obviously would so no need to know for that one though) I did leave the warning vague saying that it can be ignored meanwhile though.
(In reply to Ionen Wolkens from comment #1) > I did leave the warning vague saying that it can be ignored meanwhile though. Well, guess I could put more emphasis on the "If" and "may", and reword a bit given cpu may not support IBT and then it doesn't matter. Alternatively suppose could try to skip the warning if the cpu can't use it, albeit I don't overly want to do cpu detection (uncertain if it's even the machine it'll be ran on too).
(In reply to Ionen Wolkens from comment #2) > (In reply to Ionen Wolkens from comment #1) > > I did leave the warning vague saying that it can be ignored meanwhile though. > Well, guess I could put more emphasis on the "If" and "may", and reword a > bit given cpu may not support IBT and then it doesn't matter. Oh wait, I already did that for >390, well still missing the CPU bit.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8b1535336edc4a2aee3574611f665716588e6b31 commit 8b1535336edc4a2aee3574611f665716588e6b31 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2023-08-06 02:20:31 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2023-08-06 04:27:45 +0000 x11-drivers/nvidia-drivers: adjust IBT warning again Hoping to be able to remove this from 535 branch at least, but I have no way to really confirm so leaving it there for now. Last time I removed this warning I just got someone on IRC with issues who wondered why the ebuild didn't warn about this but that was with an older version. This aside, do disable warning with USE=kernel-open, pretty sure that should always be fine. Having a bug open to track this should be useful anyhow. Bug: https://bugs.gentoo.org/911142 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> x11-drivers/nvidia-drivers/nvidia-drivers-390.157.ebuild | 7 +++++-- x11-drivers/nvidia-drivers/nvidia-drivers-470.199.02.ebuild | 8 +++++--- x11-drivers/nvidia-drivers/nvidia-drivers-525.125.06.ebuild | 10 ++++++---- x11-drivers/nvidia-drivers/nvidia-drivers-525.47.35.ebuild | 10 ++++++---- x11-drivers/nvidia-drivers/nvidia-drivers-535.86.05.ebuild | 10 ++++++---- 5 files changed, 28 insertions(+), 17 deletions(-)
Created attachment 867197 [details] emerge --info i attached emerge info Video Card: 01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] (rev a1) CPU: 13th Gen Intel(R) Core(TM) i3-13100F and as i mentioned before, it would be nice if it was clearer that even if the module load it can still cause problems with IBT
(In reply to Kfir Ozer from comment #5) > and as i mentioned before, it would be nice if it was clearer that even if > the module load it can still cause problems with IBT Oh sorry, I glanced over that too quickly and misunderstood. That sounds surprising though, and is also all kind of annoying given IBT is default in recent kernels. Guess I can add a note for that anyhow, albeit guess it means I can't remove the warning altogether.
(In reply to Ionen Wolkens from comment #6) > (In reply to Kfir Ozer from comment #5) > > and as i mentioned before, it would be nice if it was clearer that even if > > the module load it can still cause problems with IBT > Oh sorry, I glanced over that too quickly and misunderstood. That sounds > surprising though, and is also all kind of annoying given IBT is default in > recent kernels. > > Guess I can add a note for that anyhow, albeit guess it means I can't remove > the warning altogether. glad we're clear now :) ahhmm.. there has been new nvidia drivers and new kernels since then. i have two gentoo machines, the one that i described, and a 13th Gen Intel(R) Core(TM) i7-13700KF and NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] (rev a1). on both of them i'll enable IBT and see if the problem still occurs, i'll update the status, and if so i would also do a bug report for ffmpeg so the error message will be clearer.
(In reply to Kfir Ozer from comment #7) > on both of them i'll enable IBT and see if the problem still occurs Thanks, I'll update the warning for now either way so people can suspect it if they run into other issues (harmless to have).
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d5c0621072a1e7c017cd31fe5b547a5fffb5282f commit d5c0621072a1e7c017cd31fe5b547a5fffb5282f Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2023-08-06 09:54:29 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2023-08-06 10:06:04 +0000 x11-drivers/nvidia-drivers: adjust IBT warning yet again Sounds it may cause more issues than just failing to load modules (cuda/nvenc notably). Can't confirm myself, but let's stay on the safe side for now. 0/390 branch gets a different message given it should most likely do fail to load, and CUDA/NVENC are no longer usable with it using in-tree packages anyway. Eventually this may end up better suited for the wiki than the ebuild. Does not help that this is noisy for everyone when using prebuilt gentoo-kernel-bin even if their CPU does not support it. Bug: https://bugs.gentoo.org/911142 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> x11-drivers/nvidia-drivers/nvidia-drivers-390.157.ebuild | 7 ++++--- x11-drivers/nvidia-drivers/nvidia-drivers-470.199.02.ebuild | 7 ++++--- x11-drivers/nvidia-drivers/nvidia-drivers-525.125.06.ebuild | 7 ++++--- x11-drivers/nvidia-drivers/nvidia-drivers-525.47.35.ebuild | 7 ++++--- x11-drivers/nvidia-drivers/nvidia-drivers-535.86.05.ebuild | 7 ++++--- 5 files changed, 20 insertions(+), 15 deletions(-)
in the last couple of months i played with two different gentoo servers, one with gtx3060 and one with gtx1060 and IBT doesn't give me any issues anymore. plex, ffmpeg.... everything works as it should.
(In reply to Kfir Ozer from comment #10) > in the last couple of months i played with two different gentoo servers, one > with gtx3060 and one with gtx1060 and IBT doesn't give me any issues > anymore. plex, ffmpeg.... everything works as it should. What drivers version was that? Due time to cleanup this warning, albeit I'd leave it in the versions older than the one you used.
Unfortunately i didn't not mark first version that i saw working properly, but i can safely say that the latest ~amd64 version was the one i played with the most with different boot params, nvidia-drm, psi and so on so just to be on the same side tag the latest version 545.29.06-r1
Alright thanks, guess I'll remove the warning from 545 and 550 then (550 is an unkeyworded beta but is afaik due to become the next production branch and thus replace stable 535).
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1d546d3a975eef7683c69882f6af50bb816ba417 commit 1d546d3a975eef7683c69882f6af50bb816ba417 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2024-01-31 10:19:28 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2024-01-31 10:24:19 +0000 x11-drivers/nvidia-drivers: remove IBT warning in 545+ Hopefully for good this time, albeit will be left forever in 390 (definitely broken) and 470 too given status is incertain. 525+535 will eventually be dropped either way (far sooner than 390+470 anyway), so let's just leave them alone to be safe. Closes: https://bugs.gentoo.org/911142 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> x11-drivers/nvidia-drivers/nvidia-drivers-545.29.06-r1.ebuild | 6 ------ x11-drivers/nvidia-drivers/nvidia-drivers-550.40.07.ebuild | 6 ------ 2 files changed, 12 deletions(-)
