I compiled 5.9.1 with:
# CONFIG_TRANSPARENT_HUGEPAGE is not set
And after setting the provider output source and attempting to bring up the external display I get a kernel crash.
The computer becomes unresponsive, so the best I can get is a photo, which is attached here:
I applied the patch and built the kernel. It boots correctly, and the xrandr provider gets added to the xrandr list. However when I use xrandr to change the resolution I get a hard Xorg crash. I think I will wait a bit until this patch hits mainline and report back.
I think you just need the one patch, but I’m not super familiar with it and Alex is on paternity leave so I can’t ask him at the moment.
Hello, I would like to report I have the same problem.
I am seeing the same error in the journal
even after applying the patch metioned and disabling the flag
My computer has a Ryzen 7 4800h CPU and an Nvidia RTX 2060 GPU, the distro is manjaro linux, kernel v5.9.8.
I have requested help in manjaro’s forum too but I am guessing the problem is distro-independent so I tought reporting here was relevant too.
Here is the full error message in the journal using the custom kernel.
Nov 18 16:55:28 legion5P kernel: ------------[ cut here ]------------
Nov 18 16:55:28 legion5P kernel: Unhandled error in __nv_drm_gem_user_memory_handle_vma_fault: -22
Nov 18 16:55:28 legion5P kernel: WARNING: CPU: 10 PID: 1320 at /storage/manjaro/makepkg/linux59-nvidia-455xx/src/NVIDIA-Linux-x86_64-455.45.01-no-compat32/kernel/nvidia-drm/nvidia-drm-gem-u>
Nov 18 16:55:28 legion5P kernel: Modules linked in: ccm rfcomm fuse cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel bluetooth hid_logitech_hidpp ecdh_generic ecc crc16 >
Nov 18 16:55:28 legion5P kernel: cec rc_core drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(POE) crypto_user ip_tables x_tables btrfs blake2b_generic libcrc32c crc32c_gen>
Nov 18 16:55:28 legion5P kernel: CPU: 10 PID: 1320 Comm: Xorg Tainted: P OE 5.9.8-2-MANJARO #1
Nov 18 16:55:28 legion5P kernel: Hardware name: LENOVO 82GU/LNVNB161216, BIOS FSCN09WW 06/28/2020
Nov 18 16:55:28 legion5P kernel: RIP: 0010:__nv_drm_gem_user_memory_handle_vma_fault+0x8c/0x90 [nvidia_drm]
Nov 18 16:55:28 legion5P kernel: Code: 41 bc 00 01 00 00 44 89 e0 41 5c c3 0f 0b 89 c2 48 c7 c6 80 d6 39 c0 48 c7 c7 cb d8 39 c0 c6 05 8d 7b 00 00 01 e8 31 e7 44 f8 <0f> 0b eb cc 0f 1f 44 0>
Nov 18 16:55:28 legion5P kernel: RSP: 0018:ffffb03900cdbb78 EFLAGS: 00010286
Nov 18 16:55:28 legion5P kernel: RAX: 0000000000000000 RBX: ffffb03900cdbbc8 RCX: 0000000000000000
Nov 18 16:55:28 legion5P kernel: RDX: 0000000000000001 RSI: ffffffffb918941a RDI: 00000000ffffffff
Nov 18 16:55:28 legion5P kernel: RBP: ffff9d8871649838 R08: 000000000000050c R09: 0000000000000001
Nov 18 16:55:28 legion5P kernel: R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000002
Nov 18 16:55:28 legion5P kernel: R13: 0000000000000000 R14: ffff9d8871649838 R15: ffffb03900cdbbc8
Nov 18 16:55:28 legion5P kernel: FS: 00007f338a83c540(0000) GS:ffff9d88af680000(0000) knlGS:0000000000000000
Nov 18 16:55:28 legion5P kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 18 16:55:28 legion5P kernel: CR2: 000055c3b6ac5850 CR3: 00000007c39c8000 CR4: 0000000000350ee0
Nov 18 16:55:28 legion5P kernel: Call Trace:
Nov 18 16:55:28 legion5P kernel: __do_fault+0x38/0xd0
Nov 18 16:55:28 legion5P kernel: handle_mm_fault+0x1496/0x1a40
Nov 18 16:55:28 legion5P kernel: __get_user_pages+0x25f/0x7c0
Nov 18 16:55:28 legion5P kernel: __gup_longterm_locked+0x61/0x1e0
Nov 18 16:55:28 legion5P kernel: os_lock_user_pages+0xa5/0x190 [nvidia]
Nov 18 16:55:28 legion5P kernel: _nv000635rm+0x7a/0xf0 [nvidia]
Nov 18 16:55:28 legion5P kernel: ? _nv000710rm+0x70c/0x880 [nvidia]
Nov 18 16:55:28 legion5P kernel: ? _raw_spin_unlock_irqrestore+0x20/0x40
Nov 18 16:55:28 legion5P kernel: ? rm_ioctl+0x54/0xb0 [nvidia]
Nov 18 16:55:28 legion5P kernel: ? nvidia_ioctl+0x5b7/0x900 [nvidia]
Nov 18 16:55:28 legion5P kernel: ? nvidia_frontend_unlocked_ioctl+0x37/0x50 [nvidia]
Nov 18 16:55:28 legion5P kernel: ? __x64_sys_ioctl+0x83/0xb0
Nov 18 16:55:28 legion5P kernel: ? do_syscall_64+0x33/0x40
Nov 18 16:55:28 legion5P kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Nov 18 16:55:28 legion5P kernel: ---[ end trace 3bb15a554f2c6903 ]---
Nov 18 16:55:28 legion5P kernel: Cannot map memory with base addr 0x7f3325736000 and size of 0x8ca pages
Disregard the previous message, I managed to fix the issue. I will briefly describe what I did,
In the previous message, I stated the unhandled error persisted with the patched kernel, I was wrong. When I built the kernel, I did not disable the
CONFIG_TRANSPARENT_HUGEPAGE flag. Therefore, enabling the flag and applying the patch mentioned by @aplattner fixed the
Unhandled error in __nv_drm_gem_user_memory_handle_vma_fault: -22.
However, doing so uncovered other errors.
Firstly, the error
AMD-Vi: Unable to read/write to IOMMU perf counter which needs a GRUB flag
Failed to get backlight or LED device 'backlight:acpi_video0': No such device also needs a GRUB flag
Fixing those revealed an nvidia-gpu i2c timeout error which needed another patch applied to the kernel.
After fixing this last one, my computer booted successfully and HDMI out was working correctly in hybrid mode!
Alright, I hope that is helpful. I tried to stick to the most relevant info here for brevity. I am documenting the full process and will share a link to it once I am done with the write up.
Great news! Looking forward to that write-up @carlosmorales777
I gave up after I ran a few tests on Windows and realised I could get at most 1h / 1h30 extra of battery in Hybrid graphics mode on my Legion 5 with a 60whr battery. This certainly wasn’t worth the extra complexity from having to handle two drivers in Linux, so I changed to Discrete Graphics in the BIOS.
With Discrete graphics I get around 4 hours of battery doing desktop stuff on both Windows and Linux.
How does your Legion 5P behave under Linux? Do you notice lower power consumption in Hybrid graphics mode? Do you get more out of your battery?
Also I appreciate you found a fix for this in Hybrid graphics mode, awesome.
In Discrete graphics mode, create the file /etc/X11/xorg.conf.d/21-nvidia-brightness.conf with the following:
Option “RegistryDwords” “EnableBrightnessControl=1;”
This will make backlight control work with just the nvidia card.
Can you tell us please more info about how you fix it, i have the lenovo legion 5 4800h +1660ti, and i cant get working the backlight in hybrid mode, and no external monitor. If you can explain with details all the comunity will apreciate it.
Which patch was that? Also, does anyone know if those patches were merged for 5.10 or do we have to wait until 5.11?
Apologies for the delay, I documented the process on this post on my personal blog
I hope it helps.
Sorry for the delay! Here is the post on my blog
Yes, thanks for sharing that. I was exploring the integrated video option thinking it was going to give me longer battery life. It turns out, the battery seems to lasts longer using the discrete card. Bear in mind, I don’t have hard data to back this claim. Once I solved the issues, I didn’t look more into it.
just for know, the lcd brightness didn’t work?, i currently have with discrete only for this reason, because in middle to dark rooms maximum brightness hurts my eyes.
Just for know2: How long last the battery with hybrid mode?, with discrete only last 3hr aprox.
Thanks for all!!!
Sorry, I haven’t check the 5.10 kernel, I’ll need to stay with version 5.9 for a few more days before moving to the newer version.
I could not fix the LCD brightness control with hybrid video.
The battery life seemed shorter using hybrid video too.
Sorry I can’t provide more info, I switched to discrete video too.
Thanks for reviving this thread guys.
So looks like there is no solution for the backlight control in Hybrid mode yet.
I ran a few tests with Hybrid mode on Windows, and the battery life difference is minimal, between 5 and 20% at most, and only when you’re idle. I suspect the NVIDIA card is not powered down properly even on Windows, and the AMD one is not as power efficient as we were lead to believe.
Still I’d like to run the same tests on Linux to see if there’s a difference, but I guess now we’ll have to wait…
Indeed, if the with screen at maximun brightness losse all the posibles beneficts of the non-nvidia save power, even drain more than nvidia with mid brightness level. And the fact of the maximum brightness hurts severely the eyes, actually there is no deal use this hybrid mode right now. If some one fix it, will be a deal breaker.
Did you guys run any battery tests in hybrid mode on Windows?
Like I said I get around 4 hours of battery in Linux, and in Windows I got at most 1 hour more, and this was not doing anything, just letting the computer sit there. Using the computer I got maybe 30 minutes more… so totally not worth it using Hybrid even in Windows.
I think it was finally fixed in 5.10, I do get an HDMI signal with that kernel version but that’s when only having the Nvidia GPU set (non-hybrid mode). I tried to make the HDMI output work with hybrid graphics but I’m getting a bit stuck. When I connect the HDMI monitor KDE detects it but does not activate it (activating it manually doesn’t change anything, the setting is reverted as soon as I open the system settings again) and changing the external display modes don’t do anything.
This seems weird since I configured Xorg as the Nvidia docs detail:
Identifier "X.org Configured"
Screen 0 "AMD"
Option "DRI" "3"
Option "TearFree" "true"
Option "IgnoreABI" "1"
I also tried the next commands once the HDMI monitor is plugged in:
xrandr --setprovideroutputsource 1 0
The screen flashes rapidly and the next error is given:
xrandr: Configure crtc 4 failed
But at least I can finally use an external monitor with just the Nvidia GPU (and some quick-switch scripts I made) thanks to the kernel fix!