[Ubuntu-x-swat] [Bug 1801898] Re: Only one of two external (displayport) displays is working without hotplug
I think this bug can be closed. Some upstream update (not sure which) made it work as it should. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801898 Title: Only one of two external (displayport) displays is working without hotplug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801898/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache
** Description changed:
[Impact]
- A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
+ A new fix has been merged to NVIDIA libglvnd repo at
https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e
We need to include it in bionic.
It would be ok to just include this fix even without updating to the latest
glvnd version.
This change fixes a crash seen in some GLX apps while calling
glXGetProcAddress.
+ Source Package :
+ https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
- Source Package :
https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2
+ Can we get this fix merged in current LTS 18.04 as "-updates"
+
+ [Test app]
+
+ To reproduce this failure: Install python-pyglet on 18.04 ubuntu.
+ And run a small test app with this piece of code.
+ void *handle = dlopen("libGLX.so.0", 2);
+ glXGetProcAddressARB = (GLXextFuncPtr (*)(const GLubyte*))dlsym(handle,
"glXGetProcAddressARB");
+ glXGetProcAddressARB("glXAllocateMemoryMESA");
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1816004
Title:
GLVND: AARCH64 : Fix address passed to clear cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1816004] [NEW] GLVND: AARCH64 : Fix address passed to clear cache
Public bug reported: [Impact] A new fix has been merged to NVIDIA libglvnd repo at https://github.com/NVIDIA/libglvnd/pull/171/commits/9948df636708e2915e5c2daa61b318e6252bc02e We need to include it in bionic. It would be ok to just include this fix even without updating to the latest glvnd version. This change fixes a crash seen in some GLX apps while calling glXGetProcAddress. Source Package : https://launchpad.net/ubuntu/+source/libglvnd/1.0.0-2ubuntu2.2 ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Package changed: vulkan (Ubuntu) => libglvnd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to vulkan in Ubuntu. https://bugs.launchpad.net/bugs/1816004 Title: GLVND: AARCH64 : Fix address passed to clear cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1816004/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815957] [NEW] SynPS/2 Synaptics TouchPad: Read error 19
Public bug reported: Hi Ubuntu 18.04 went into standby mode with the mouse plugged in. Then I've removed the mouse. A few hours later I wanted to continue work (without mouse) and woke up my PC from standby mode. Unfortunately the touchpad did not work. So I put Ubuntu back into standby mode, plugged in a mouse and woke it up again. Both Touchpad and mouse worked perfectly again. Regards, Ettore Atalan ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1815957/+attachment/5238744/+files/syslog -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1815957 Title: SynPS/2 Synaptics TouchPad: Read error 19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1815957/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815947] Re: video
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815947 Title: video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815947/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815947] [NEW] video
Public bug reported: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: /dev/sda1: clean, 323551/19144704 files, 17190727/76570112 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 14 19:14:04 2019 DistUpgraded: 2018-06-22 23:29:57,626 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce GTS 250] [10b0:0401] NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G92 [GeForce GTS 250] [1043:82fb] InstallationDate: Installed on 2018-06-17 (242 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=sl PATH=(custom, no user) LANG=sl_SI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=0bbe53b3-055a-45b3-9588-a717e2462ba9 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-22 (236 days ago) dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 0703 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision0703:bd08/09/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Feb 13 18:46:13 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: [drm] Failed to open DRM device for (null): -22 open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815947 Title: video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815947/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815172]
Just correcting a wrong comment (#2) I made: > It happens on both 32bit and 64bit installations. I asked the school that reported the issue on 64bit to check again, and they said they have a 32bit installation after all. So the problem has only been reported in 32bit installations; I don't know if it happened on 64bit. And btw everything is fixed now, thanks again to all. :) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed. ** Tags removed: verification-needed-bionic ** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815125] Re: constant video freezes in firefox with x-x-v-amdgpu 18.1.0
I've tested it on a 'vega 8 mobile' laptop with glxgears. Without the fix the session would freeze periodically, after installing the update and restarting gnome-shell things work fine. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1815125 Title: constant video freezes in firefox with x-x-v-amdgpu 18.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1815125/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Description changed: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu - ExtraDebuggingInterest: No + ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815858] Re: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build
Hello. I'm sorry for writing post by post, but I forget to write, that - in my case - architecture is i386/i686. There is also one more issue: I've made a mistake during writing my post, in the last 'Makefile/make[1]' informations (see exceptions from a build log): of course, there should be "recipe for target 'module' failed". Best regards. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1815858 Title: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1815858/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815858] Re: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1815858 Title: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1815858/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1815858] Re: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build
Hello. It seems, that I'm experiencing exactly the same problem. During kernel update process to v4.4.0-143.169 (from '-proposed') there was an error message about some issues with 'nvidia' module etc. '/var/lib/dkms/nvidia-304/304.135/build/make.log' file contains a full build process informations. Here are some examples (I can paste it somewhere): [ NVIDIA Build log examples ] In file included from ./arch/x86/include/asm/preempt.h:5:0, from include/linux/preempt.h:59, from include/linux/spinlock.h:50, from include/linux/seqlock.h:35, from include/linux/time.h:5, from include/uapi/linux/timex.h:56, from include/linux/timex.h:56, from include/linux/sched.h:19, from include/linux/utsname.h:5, from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:40, from /var/lib/dkms/nvidia-304/304.135/build/nv.c:13: include/linux/percpu-refcount.h: In function ‘percpu_ref_get_many’: ./arch/x86/include/asm/percpu.h:130:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] ((val) == 1 || (val) == -1)) ? \ ^ (...) include/linux/percpu-refcount.h: In function ‘percpu_ref_get_many’: ./arch/x86/include/asm/percpu.h:130:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] ((val) == 1 || (val) == -1)) ? \ ^ (...) include/linux/percpu-defs.h:394:11: note: in expansion of macro ‘this_cpu_add_1’ case 1: stem##1(variable, __VA_ARGS__);break; \ ^ (...) include/linux/percpu-refcount.h:276:3: note: in expansion of macro ‘this_cpu_sub’ this_cpu_sub(*percpu_count, nr); ^ (...) include/linux/compiler.h:165:40: note: in definition of macro ‘likely’ # define likely(x) __builtin_expect(!!(x), 1) ^ (...) In file included from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:82:0, from /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:15: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ (...) make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.135/build] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! Makefile:257: commands for 'module' object failed make[1]: *** [module] Error 1 makefile:59: commands for 'module' object failed make: *** [module] Error 2 ● NOTE: There is more definitions of, mentioned above, 'macros'. For example: ‘__pcpu_size_call’, ‘this_cpu_add’, ‘percpu_add_op’, ‘this_cpu_add_4’ etc. Generally, they all are repeated in build log. [ END of NVIDIA Build log example ] That's is only an example (whole build log contains about ~1500 lines). Most interesting and strange part is that I'm not using 'nvidia' or 'nouveau' module, but I still can log to system via LightDM! Why is that? Shouldn't there be some graphics issues? Here are some more informations about 'nvidia' module (NOTE: I'm logged in and using v4.4.0-143-generic kernel - on which 'nvidia' module failed to build): [~]$ modinfo nvidia modinfo: ERROR: Module nvidia not found. [~]$ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='nvidia_304' modprobe: ERROR: could not insert 'nvidia_304': Unknown symbol in module, or unknown parameter (see dmesg) [~]$ sudo modprobe nvidia_304 modprobe: FATAL: Module nvidia_304 not found in directory /lib/modules/4.4.0-143-generic (NOTE: dmesg(1) is empty - there is no informations about 'nvidia' issues). [~]$ lsmod |grep nvidia [~]$ lsmod |grep nouveau By the way: there were some problems with graphics when monitor blacked out (there should 'light-locker' show up), because of - for example - no mouse movements or no reaction from user side and after resume colors were bright, fonts thiner etc. If it's about X.org logs, there is something like this in '/var/log/Xorg.0.log' file: (II) LoadModule: "nvidia" (II) Loading /usr/lib/i386-linux-gnu/xorg/extra-modules/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 (...) (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your (EE) NVIDIA: system's kernel log for additional error messages. (II) UnloadModule: "nvidia" (II) Unloading nvidia (EE) Failed to load module "nvidia" (module-specific error, 0) (II) LoadModule: "nouveau" (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so Now, some technical informations about versions etc.: ✗ Linux kernel: v4.4.0-143-generic ✗ Description: Ubuntu 16.04.5 LTS Release: 16.04 ✗ nvidia-304 304.135-0ubuntu0.16.04.2 ✗ nvidia-304-updates 304.135-0ubuntu0.16.04.2 ✗ xserver-xorg-video-nouveau 1:1.0.12-1build2 ✗ lspci(8) info: 00:10.0
