[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
changing dev_err to dev_err_once like suggested in comment 35 worked for me, thank you! probably this hides the cause but at least I'm no longer being hit with tons of messages in syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 149987] Re: CONFIG_MODULE_FORCE_UNLOAD is not set
I also need to force remove a module. It is unacceptable to have to reboot when I know for sure that removing the module will not affect the system stability. It is also difficult to keep rebuilding kernel just to have this feature. Please reconsider. Thanks. ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/149987 Title: CONFIG_MODULE_FORCE_UNLOAD is not set Status in linux package in Ubuntu: Confirmed Status in linux-source-2.6.20 package in Ubuntu: Won't Fix Bug description: Binary package hint: kernel-image-2.6.20-15-generic-di In some time I need run rmmod -f some_module, but this is not work becase in kernel config CONFIG_MODULE_FORCE_UNLOAD is not set... May be enabling this in future version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/149987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
>Kai-Heng Feng (kaihengfeng) wrote on 2019-12-11: #4 > Can you please run `sudo update-initramfs -u -k all` and see if the issue still happens? yes this persists even after that. I have a nvidia card but I want to blacklist it. even blacklisted, the systemd-udevd /lib/udev/rules.d/71-nvidia.rules attempt to run the rules forever. moving /lib/udev/rules.d/71-nvidia.rules away from udev rules search path fixes that, but that's not the correct solution. why does systemd- udev insist repeating instead of failing after first try? 18.04 lts here. drivers nvidia-driver-390 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
also other people complained https://www.reddit.com/r/VFIO/comments/90tg4h/after_loading_vfiopci_instead_of_nvidia_my_dmesg/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in systemd package in Ubuntu: Expired Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734172] Re: Upgrade ZFS to 0.7.3
@ comment #9, it has landed into proposed, not into main! this means xenial won't get 0.7 via hwe... :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1734172 Title: Upgrade ZFS to 0.7.3 Status in zfs-linux package in Ubuntu: In Progress Bug description: ZFS v0.7 is out, current version is 0.7.3: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.3 . It is desired to have the latest stable version at least in LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.6.5.11-1ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 Date: Thu Nov 23 19:03:47 2017 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2017-05-20 (187 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1734172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734172] Re: Upgrade ZFS to 0.7.3
this is really worrying. we chose ubuntu for native zfs but it is such a dissapointment to not provide at least a ppa with updated zfs 0.7 for xenial. if next LTS comes without 0.7 we will switch back to centos that has almost immediate release packages after official release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1734172 Title: Upgrade ZFS to 0.7.3 Status in zfs-linux package in Ubuntu: In Progress Bug description: ZFS v0.7 is out, current version is 0.7.3: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.7.3 . It is desired to have the latest stable version at least in LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: zfsutils-linux 0.6.5.11-1ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 Date: Thu Nov 23 19:03:47 2017 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: zfs-linux UpgradeStatus: Upgraded to bionic on 2017-05-20 (187 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1734172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
seeing this on xenial after this sequence of operations: lxc stop run2 lxc delete run2 lxc copy run1 run2 lxc start run2 <- hangs here, with later dmesg [337766.146479] unregister_netdevice: waiting for lo to become free. Usage count = 1 [337772.435786] INFO: task lxd:20665 blocked for more than 120 seconds. [337772.435856] Tainted: P OE 4.4.0-47-generic #68-Ubuntu [337772.435922] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [337772.436002] lxd D 88006b6cbcb8 0 20665 1 0x0004 [337772.436006] 88006b6cbcb8 821d0560 880235aa8000 8801b57d2580 [337772.436009] 88006b6cc000 81ef5f24 8801b57d2580 [337772.436010] 81ef5f28 88006b6cbcd0 81830f15 81ef5f20 [337772.436012] Call Trace: [337772.436020] [] schedule+0x35/0x80 [337772.436022] [] schedule_preempt_disabled+0xe/0x10 [337772.436024] [] __mutex_lock_slowpath+0xb9/0x130 [337772.436026] [] mutex_lock+0x1f/0x30 [337772.436029] [] copy_net_ns+0x6e/0x120 [337772.436033] [] create_new_namespaces+0x11b/0x1d0 [337772.436035] [] copy_namespaces+0x6d/0xa0 [337772.436038] [] copy_process+0x905/0x1b70 [337772.436040] [] _do_fork+0x80/0x360 [337772.436044] [] ? SyS_access+0x1e8/0x230 [337772.436046] [] SyS_clone+0x19/0x20 [337772.436048] [] entry_SYSCALL_64_fastpath+0x16/0x71 fwiw, at the time of stop, run2 had an additional IP address on dev lo, and at the time of copy, run1 also was running and had an additional ip address on dev lo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-lts-utopic package in Ubuntu: Confirmed Status in linux-lts-xenial package in Ubuntu: Confirmed Status in linux source package in Trusty: Fix Released Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Confirmed Status in linux source package in Vivid: Fix Released Bug description: SRU Justification: [Impact] Users of kernels that utilize NFS may see the following messages when shutting down and starting containers: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] Setup multiple containers in parallel to mount and NFS share, create some traffic and shutdown. Eventually you will see the kernel message. Dave's script here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24 [Fix] commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream -- I currently running trusty latest patches and i get on these hardware and software: Ubuntu 3.13.0-43.72-generic 3.13.11.11 processor : 7 vendor_id : GenuineIntel cpu family: 6 model : 77 model name: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz stepping : 8 microcode : 0x11d cpu MHz : 2400.000 cache size: 1024 KB physical id : 0 siblings : 8 core id : 7 cpu cores : 8 apicid: 14 initial apicid: 14 fpu : yes fpu_exception : yes cpuid level : 11 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms bogomips : 4799.48 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: somehow reproducable the subjected error, and lxc is working still but not more managable until a reboot. managable means every command hangs. I saw there are alot of bugs but they seams to relate to older version and are closed, so i decided to file a new one? I run alot of machine with trusty an lxc containers but only these kind of machines produces these errors, all other don't show these odd behavior. thx in advance meno To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
