current and nvidia-legacy340-kernel Question re 10-nvidia.conf file
by MDKDIO from LinuxQuestions.org on (#5BPJG)
Sorry if posted in the wrong place, but thought I'd rather make a new thread than post this in the "SBo scripts not building on current"...
I noticed that I have an error in my log file regarding nvidia:
Code:Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!The rest of the log entry:
Code:named[1187]: managed-keys-zone: Unable to fetch DNSKEY set '.': failure
kernel: [ 57.126702] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
kernel: [ 57.126806] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs
kernel: [ 57.786432] NVRM: Your system is not currently configured to drive a VGA console
kernel: [ 57.786434] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
kernel: [ 57.786435] NVRM: requires the use of a text-mode VGA console. Use of other console
kernel: [ 57.786435] NVRM: drivers including, but not limited to, vesafb, may result in
kernel: [ 57.786436] NVRM: corruption and stability problems, and is not supported.
kernel: [ 57.905770] ------------[ cut here ]------------
kernel: [ 57.905773] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!
kernel: [ 57.905783] WARNING: CPU: 5 PID: 1363 at mm/usercopy.c:75 usercopy_warn+0x7a/0x90
kernel: [ 57.905784] Modules linked in: cfg80211 8021q garp mrp stp llc efivarfs ipv6 nls_iso8859_1 nls_cp437 vfat fat snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio sn>
kernel: [ 57.905815] CPU: 5 PID: 1363 Comm: Xorg Tainted: P O 5.4.83 #1
kernel: [ 57.905816] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 2008 12/06/2019
kernel: [ 57.905818] RIP: 0010:usercopy_warn+0x7a/0x90
kernel: [ 57.905820] Code: bc 41 51 49 89 c0 49 89 f1 49 0f 45 d2 49 c7 c2 0b df 0a bc 48 89 f9 48 c7 c7 b8 ec 0b bc 4d 0f 45 d3 4c 89 d6 e8 54 12 e1 ff <0f> 0b 48 83 c4 18 c3 48 >
kernel: [ 57.905821] RSP: 0018:ffffbfc2410dfbc0 EFLAGS: 00010282
kernel: [ 57.905822] RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000006
kernel: [ 57.905823] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff9c790e956580
kernel: [ 57.905824] RBP: ffff9c78df3ede5b R08: 0000000000000001 R09: 00000000000003b1
kernel: [ 57.905824] R10: 0000000000013a84 R11: 0000000000000001 R12: ffff9c78df3ede58
kernel: [ 57.905825] R13: 0000000000000001 R14: ffff9c78df3ede58 R15: ffff9c78df3edea0
kernel: [ 57.905826] FS: 00007faf1c787900(0000) GS:ffff9c790e940000(0000) knlGS:0000000000000000
kernel: [ 57.905827] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: [ 57.905828] CR2: 00007faf17c1bf40 CR3: 0000000409568000 CR4: 0000000000340ee0
kernel: [ 57.905828] Call Trace:
kernel: [ 57.905833] __check_object_size+0x12e/0x13c
kernel: [ 57.905935] os_memcpy_to_user+0x27/0x50 [nvidia]
kernel: [ 57.906041] _nv001372rm+0xa5/0x260 [nvidia]
kernel: [ 57.906144] ? _nv004782rm+0x4eba/0x5500 [nvidia]
kernel: [ 57.906246] ? _nv004329rm+0xec/0xf0 [nvidia]
kernel: [ 57.906343] ? _nv004324rm+0xca/0x650 [nvidia]
kernel: [ 57.906446] ? _nv015124rm+0x576/0x5c0 [nvidia]
kernel: [ 57.906551] ? _nv000694rm+0x2e/0x60 [nvidia]
kernel: [ 57.906648] ? _nv000789rm+0x5f5/0x8b0 [nvidia]
kernel: [ 57.906744] ? rm_ioctl+0x73/0x100 [nvidia]
kernel: [ 57.906747] ? yield_to+0x120/0x150
kernel: [ 57.906843] ? nvidia_ioctl+0x15a/0x480 [nvidia]
kernel: [ 57.906939] ? nvidia_frontend_unlocked_ioctl+0x40/0x60 [nvidia]
kernel: [ 57.906941] ? do_vfs_ioctl+0x3c9/0x6b0
kernel: [ 57.906942] ? ksys_ioctl+0x5e/0x90
kernel: [ 57.906944] ? ksys_write+0x5f/0xe0
kernel: [ 57.906945] ? __x64_sys_ioctl+0x16/0x20
kernel: [ 57.906947] ? do_syscall_64+0x4c/0x170
kernel: [ 57.906949] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
---[ end trace bfe24f2a7bccbc94 ]---
And searching the net, I found this was/is an old bug, sorted with a patch.
I see no patch included when I use the slackbuild in ponce repo for current.
(I did see a patched been removed in January, listed as no longer needed...).
Question:
In nvidia-legacy340-kernel.SlackBuild there's these lines:
Code:mkdir -p $PKG/usr/share/X11/xorg.conf.d/
cat $CWD/10-nvidia.conf > $PKG/usr/share/X11/xorg.conf.d/10-nvidia.confIF I am understanding this correct, there should be a 10-nvidia.conf file located in /usr/share/X11/xorg.conf.d/ folder?
In my case, that file doesn't exist. However, the xorg.conf located in
/etc/X11/xorg.conf do have the correct lines:
Code:Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection(Reason could be that I had used the NVIDIA-Linux-x86_64-340.108.run
for installing the driver prior to using the slackbuild).
Any thoughts?
I noticed that I have an error in my log file regarding nvidia:
Code:Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!The rest of the log entry:
Code:named[1187]: managed-keys-zone: Unable to fetch DNSKEY set '.': failure
kernel: [ 57.126702] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
kernel: [ 57.126806] caller _nv000788rm+0xe4/0x1c0 [nvidia] mapping multiple BARs
kernel: [ 57.786432] NVRM: Your system is not currently configured to drive a VGA console
kernel: [ 57.786434] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
kernel: [ 57.786435] NVRM: requires the use of a text-mode VGA console. Use of other console
kernel: [ 57.786435] NVRM: drivers including, but not limited to, vesafb, may result in
kernel: [ 57.786436] NVRM: corruption and stability problems, and is not supported.
kernel: [ 57.905770] ------------[ cut here ]------------
kernel: [ 57.905773] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!
kernel: [ 57.905783] WARNING: CPU: 5 PID: 1363 at mm/usercopy.c:75 usercopy_warn+0x7a/0x90
kernel: [ 57.905784] Modules linked in: cfg80211 8021q garp mrp stp llc efivarfs ipv6 nls_iso8859_1 nls_cp437 vfat fat snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio sn>
kernel: [ 57.905815] CPU: 5 PID: 1363 Comm: Xorg Tainted: P O 5.4.83 #1
kernel: [ 57.905816] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 2008 12/06/2019
kernel: [ 57.905818] RIP: 0010:usercopy_warn+0x7a/0x90
kernel: [ 57.905820] Code: bc 41 51 49 89 c0 49 89 f1 49 0f 45 d2 49 c7 c2 0b df 0a bc 48 89 f9 48 c7 c7 b8 ec 0b bc 4d 0f 45 d3 4c 89 d6 e8 54 12 e1 ff <0f> 0b 48 83 c4 18 c3 48 >
kernel: [ 57.905821] RSP: 0018:ffffbfc2410dfbc0 EFLAGS: 00010282
kernel: [ 57.905822] RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000006
kernel: [ 57.905823] RDX: 0000000000000007 RSI: 0000000000000092 RDI: ffff9c790e956580
kernel: [ 57.905824] RBP: ffff9c78df3ede5b R08: 0000000000000001 R09: 00000000000003b1
kernel: [ 57.905824] R10: 0000000000013a84 R11: 0000000000000001 R12: ffff9c78df3ede58
kernel: [ 57.905825] R13: 0000000000000001 R14: ffff9c78df3ede58 R15: ffff9c78df3edea0
kernel: [ 57.905826] FS: 00007faf1c787900(0000) GS:ffff9c790e940000(0000) knlGS:0000000000000000
kernel: [ 57.905827] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: [ 57.905828] CR2: 00007faf17c1bf40 CR3: 0000000409568000 CR4: 0000000000340ee0
kernel: [ 57.905828] Call Trace:
kernel: [ 57.905833] __check_object_size+0x12e/0x13c
kernel: [ 57.905935] os_memcpy_to_user+0x27/0x50 [nvidia]
kernel: [ 57.906041] _nv001372rm+0xa5/0x260 [nvidia]
kernel: [ 57.906144] ? _nv004782rm+0x4eba/0x5500 [nvidia]
kernel: [ 57.906246] ? _nv004329rm+0xec/0xf0 [nvidia]
kernel: [ 57.906343] ? _nv004324rm+0xca/0x650 [nvidia]
kernel: [ 57.906446] ? _nv015124rm+0x576/0x5c0 [nvidia]
kernel: [ 57.906551] ? _nv000694rm+0x2e/0x60 [nvidia]
kernel: [ 57.906648] ? _nv000789rm+0x5f5/0x8b0 [nvidia]
kernel: [ 57.906744] ? rm_ioctl+0x73/0x100 [nvidia]
kernel: [ 57.906747] ? yield_to+0x120/0x150
kernel: [ 57.906843] ? nvidia_ioctl+0x15a/0x480 [nvidia]
kernel: [ 57.906939] ? nvidia_frontend_unlocked_ioctl+0x40/0x60 [nvidia]
kernel: [ 57.906941] ? do_vfs_ioctl+0x3c9/0x6b0
kernel: [ 57.906942] ? ksys_ioctl+0x5e/0x90
kernel: [ 57.906944] ? ksys_write+0x5f/0xe0
kernel: [ 57.906945] ? __x64_sys_ioctl+0x16/0x20
kernel: [ 57.906947] ? do_syscall_64+0x4c/0x170
kernel: [ 57.906949] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
---[ end trace bfe24f2a7bccbc94 ]---
And searching the net, I found this was/is an old bug, sorted with a patch.
I see no patch included when I use the slackbuild in ponce repo for current.
(I did see a patched been removed in January, listed as no longer needed...).
Question:
In nvidia-legacy340-kernel.SlackBuild there's these lines:
Code:mkdir -p $PKG/usr/share/X11/xorg.conf.d/
cat $CWD/10-nvidia.conf > $PKG/usr/share/X11/xorg.conf.d/10-nvidia.confIF I am understanding this correct, there should be a 10-nvidia.conf file located in /usr/share/X11/xorg.conf.d/ folder?
In my case, that file doesn't exist. However, the xorg.conf located in
/etc/X11/xorg.conf do have the correct lines:
Code:Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection(Reason could be that I had used the NVIDIA-Linux-x86_64-340.108.run
for installing the driver prior to using the slackbuild).
Any thoughts?