[Kernel-packages] [Bug 2076545] Re: kworker consumes 100% CPU and machine is unusable after an Ethernet link down/up event
** Summary changed: - kworker consumes 100% and notebook unusable after an ethernet link down and link up event + kworker consumes 100% CPU and machine is unusable after an Ethernet link down/up event -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2076545 Title: kworker consumes 100% CPU and machine is unusable after an Ethernet link down/up event Status in linux-signed-hwe-6.8 package in Ubuntu: New Bug description: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new terminal takes minutes. Only reboot helps (even the reboot is problematic, I need to use sysreq keys to it "by force"), the fan of the computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.8.0-39.39~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39~22.04.1-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:02:52 2024 InstallationDate: Installed on 2022-09-23 (688 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2076545/+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 2076545] Re: kworker consumes 100% and notebook unusable after an ethernet link down and link up event
** Attachment added: "gziped full kernel log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2076545/+attachment/5804893/+files/kern.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2076545 Title: kworker consumes 100% and notebook unusable after an ethernet link down and link up event Status in linux-signed-hwe-6.8 package in Ubuntu: New Bug description: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new terminal takes minutes. Only reboot helps (even the reboot is problematic, I need to use sysreq keys to it "by force"), the fan of the computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.8.0-39.39~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39~22.04.1-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:02:52 2024 InstallationDate: Installed on 2022-09-23 (688 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2076545/+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 2076545] Re: kworker consumes 100% and notebook unusable after an ethernet link down and link up event
** Description changed: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new - terminal takes minutes. Only reboot helps, the fan of the computer - starts to spin wildly. Meanwhile in kernel log: + terminal takes minutes. Only reboot helps (even the reboot is + problematic, I need to use sysreq keys to it "by force"), the fan of the + computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.8.0-39.39~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39~22.04.1-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:02:52 2024 InstallationDate: Installed on 2022-09-23 (688 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2076545 Title: kworker consumes 100% and notebook unusable after an ethernet link down and link up event Status in linux-signed-hwe-6.8 package in Ubuntu: New Bug description: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new terminal takes minutes. Only reboot helps (even the reboot is problematic, I need to use sysreq keys to it "by force"), the fan of the computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.
[Kernel-packages] [Bug 2076545] Re: kworker consumes 100% and notebook unusable after an ethernet link down and link up event
** Attachment added: "More detailed kernel log about/around the event" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2076545/+attachment/5804862/+files/kernlog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2076545 Title: kworker consumes 100% and notebook unusable after an ethernet link down and link up event Status in linux-signed-hwe-6.8 package in Ubuntu: New Bug description: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new terminal takes minutes. Only reboot helps (even the reboot is problematic, I need to use sysreq keys to it "by force"), the fan of the computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.8.0-39.39~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39~22.04.1-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:02:52 2024 InstallationDate: Installed on 2022-09-23 (688 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.8/+bug/2076545/+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 2076545] [NEW] kworker consumes 100% and notebook unusable after an ethernet link down and link up event
Public bug reported: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new terminal takes minutes. Only reboot helps (even the reboot is problematic, I need to use sysreq keys to it "by force"), the fan of the computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.8.0-39.39~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39~22.04.1-generic 6.8.8 Uname: Linux 6.8.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:02:52 2024 InstallationDate: Installed on 2022-09-23 (688 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2076545 Title: kworker consumes 100% and notebook unusable after an ethernet link down and link up event Status in linux-signed-hwe-6.8 package in Ubuntu: New Bug description: I have got a somewhat unstable internet connection since years. So far it didn't caused extra problems, but since 1-2 days (I cannot tell exactly) I have a strange and annoying experience. I can even simulate this 100% by unplugging the ethernet cable and then plugging it back. At the time of the 'link up' event after the link down, kworker (I assume this is a kernel thread) starts to consume 100% of CPU, and the machine goes so slow, that I cannot even start a program, even opening a new terminal takes minutes. Only reboot helps (even the reboot is problematic, I need to use sysreq keys to it "by force"), the fan of the computer starts to spin wildly. Meanwhile in kernel log: Aug 11 14:40:04 rygel kernel: [19512.079303] e1000e :00:1f.6 enp0s31f6: NIC Link is Down Aug 11 14:40:31 rygel kernel: [19538.944490] workqueue: pm_runtime_work hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND Aug 11 14:40:48 rygel kernel: [19556.627377] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx Aug 11 14:40:48 rygel kernel: [19556.627408] BUG: scheduling while atomic: kworker/11:1/10842/0x0002 Another event like this: [ 352.735369] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 370.173051] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx [ 370.173085] BUG: scheduling while atomic: kworker/11:1/191/0x0002 Machine: Dell Inc. Latitude 5531/0FRYDD, BIOS 1.6.0 07/07/2022 Distribution: Ubuntu 22.04.4 LTS (64 bit x86) Kernel: Linux rygel 6.8.0-39-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jul 10 15:35:09 UTC 2 x86_64 x86_64 x86_64 GNU/Linu Network connection: wired ethernet (I don't use wifi), PCI info: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-39-generic 6.8.0-39.39~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-39.39~22.0
[Kernel-packages] [Bug 2060303] [NEW] ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU 0000:01:00.0: GPU has fallen off the bus."
Public bug reported: I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)). Yesterday, I had an ubuntu update, so I use driver 535 now, the previous one was 525. After some hours after going to have lunch, I found my notebook locked up, I could not use my keyboard, mouse, and the fan of the notebook was almost "screaming" already. I don't remember a single event like this before the upgrade (with 525, and older ones before). Now, it happened again after a hour or so, and seems to be a regular theme from now :( Which is - for sure - very problematic since I had to hard power-off the system losing all non-saved work and workflow all the time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 15:52:11 2024 InstallationDate: Installed on 2022-09-23 (560 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nvidia-graphics-drivers-535 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2060303 Title: ubuntu 22.04.4 lock up with nvidia driver, "NVRM: GPU :01:00.0: GPU has fallen off the bus." Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: I'm using Nvidia's driver on Ubuntu 22.04.4 without major issues since about a year (or so) on this DELL Latitude 5531 notebook (01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce MX550] (rev a1)). Yesterday, I had an ubuntu update, so I use driver 535 now, the previous one was 525. After some hours after going to have lunch, I found my notebook locked up, I could not use my keyboard, mouse, and the fan of the notebook was almost "screaming" already. I don't remember a single event like this before the upgrade (with 525, and older ones before). Now, it happened again after a hour or so, and seems to be a regular theme from now :( Which is - for sure - very problematic since I had to hard power-off the system losing all non-saved work and workflow all the time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-535 535.161.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 15:52:11 2024 InstallationDate: Installed on 2022-09-23 (560 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: nvidia-graphics-drivers-535 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2060303/+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 1888617] Re: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
It seems update 435.21-0ubuntu0.18.04.3 of nvidia-kernel-source-435 fixed the problem for me, at least! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1888617/+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 1888617] [NEW] nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build
Public bug reported: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIME | DRIVER_RENDER, ^~~~ DRIVER_PCI_DMA scripts/Makefile.build:273: recipe for target '/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o' failed make[2]: *** [/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.o] Error 1 make[2]: *** Waiting for unfinished jobs ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-uvm/uvm8_range_group_tree_test.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-utils.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-encoder.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-gem.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-connector.o ./tools/objtool/objtool check --module --retpoline --uaccess /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-crtc.o Makefile:1731: recipe for target '/var/lib/dkms/nvidia/435.21/build' failed make[1]: *** [/var/lib/dkms/nvidia/435.21/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-42-generic' Makefile:81: recipe for target 'modules' failed make: *** [modules] Error 2 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 PackageVersion: 435.21-0ubuntu0.18.04.2 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 DKMSKernelVersion: 5.4.0-42-generic Date: Wed Jul 22 08:08:55 2020 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-435:435.21-0ubuntu0.18.04.2:/var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? InstallationDate: Installed on 2020-01-06 (198 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 435.21-0ubuntu0.18.04.2 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: nvidia-graphics-drivers-435 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1888617 Title: nvidia-kernel-source-435 435.21-0ubuntu0.18.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: After a "usual" upgrade, my system did not give any sign of life on the monitor. I tried to boot an older kernel, it worked. Then I discovered, that the problem that nvidia drivers cannot be built against kernel linux-image-5.4.0-42-generic, which could be the problem. from /var/crash/nvidia-kernel-source-435.0.crash : /var/lib/dkms/nvidia/435.21/build/nvidia-drm/nvidia-drm-drv.c:662:44: error: ‘DRIVER_PRIME’ undeclared here (not in a function); did you mean ‘DRIVER_PCI_DMA’? .driver_features= DRIVER_GEM | DRIVER_PRIM
[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04
Lenovo ThinkPad L580: $ cat /sys/bus/serio/devices/serio1/firmware_id PNP: LEN2037 PNP0f13 $ dmesg | fgrep -i elan [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=8ee3c188-2063-45de-b270-2db3df928e18 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=1 [0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=8ee3c188-2063-45de-b270-2db3df928e18 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=1 [2.432975] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [2.449022] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [2.464414] psmouse serio1: elantech: Elan sample query result 00, 22, c8 [2.526860] input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input6 [2.545342] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input5 -- 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/1803600 Title: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 Status in linux package in Ubuntu: Confirmed Bug description: Confirmed affected laptops: ThinkPad: L480 L580 P72 P52 When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad stopped working. This means it is not recognized at all. This problem occured after the first boot in 18.10 `dmesg | grep -i elantech` shows the following errors: [3.409043] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [3.427372] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8 [3.464905] psmouse serio1: elantech: Trying to set up SMBus access [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [5.586505] elan_i2c 0-0015: failed to get resolution: -71 [5.586527] elan_i2c: probe of 0-0015 failed with error -71 uname: $ uname -a Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I found the following thread which solves the problem temporarly (and reports the same problem in Arch): https://bugs.archlinux.org/task/59714 Running the following command enables it again for the current session: sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol' dmesg afterwards: [ 569.522490] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [ 569.544584] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [ 569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8 Before running the fix: $ cat /sys/bus/serio/devices/serio1/protocol ETSMBus and after: $ cat /sys/bus/serio/devices/serio1/protocol ETPS/2 After reboot the command has to be run again, of course. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 15 20:59:36 2018 DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:506a] InstallationDate: Installed on 2018-08-06 (101 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LS001AGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago) dmi.bios.date: 02/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET37W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENO
[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)
@Kai-Heng Feng : Wow, it fixed the issue for me at least, on Lenovo Thinkpad L580. :) :) -- 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/1803600 Title: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480) Status in linux package in Ubuntu: Confirmed Bug description: When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad stopped working. This means it is not recognized at all. This problem occured after the first boot in 18.10 `dmesg | grep -i elantech` shows the following errors: [3.409043] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [3.427372] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8 [3.464905] psmouse serio1: elantech: Trying to set up SMBus access [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [5.586505] elan_i2c 0-0015: failed to get resolution: -71 [5.586527] elan_i2c: probe of 0-0015 failed with error -71 uname: $ uname -a Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I found the following thread which solves the problem temporarly (and reports the same problem in Arch): https://bugs.archlinux.org/task/59714 Running the following command enables it again for the current session: sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol' dmesg afterwards: [ 569.522490] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [ 569.544584] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [ 569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8 Before running the fix: $ cat /sys/bus/serio/devices/serio1/protocol ETSMBus and after: $ cat /sys/bus/serio/devices/serio1/protocol ETPS/2 After reboot the command has to be run again, of course. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 15 20:59:36 2018 DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:506a] InstallationDate: Installed on 2018-08-06 (101 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LS001AGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago) dmi.bios.date: 02/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET37W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bu
[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480)
I have Lenovo L580. And a similar issue. The install image written to the USB drive worked fine, but after installation touchpad simply did not work. I've tried everything suggested (utilizing some google searches ...), including kernel parameters, blacklisting various i2c hid modules, and all the combinations, but nothing. It's a fresh 18.10 install, I have no idea if it would work with previous versions, but I rather wouldn't downgrade, if this bug is expected to be fixed. In my case, I see this in dmesg: [2.418397] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [2.440307] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [2.456358] psmouse serio1: elantech: Elan sample query result 00, 22, c8 [2.471110] psmouse serio1: elantech: Trying to set up SMBus access [3.054187] elan_i2c 2-0015: 2-0015 supply vcc not found, using dummy regulator [3.066012] elan_i2c 2-0015: failed to get resolution: -71 [3.066039] elan_i2c: probe of 2-0015 failed with error -71 Interestingly, sometimes the four first lines lines (grep'ing all lines from dmesg containing strig 'elan'), and not the rest. But it can be, because I tried to disable/enable touchpad in BIOS to see there is a difference. -- 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/1803600 Title: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 (ThinkPad L480) Status in linux package in Ubuntu: Confirmed Bug description: When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad stopped working. This means it is not recognized at all. This problem occured after the first boot in 18.10 `dmesg | grep -i elantech` shows the following errors: [3.409043] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [3.427372] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8 [3.464905] psmouse serio1: elantech: Trying to set up SMBus access [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [5.586505] elan_i2c 0-0015: failed to get resolution: -71 [5.586527] elan_i2c: probe of 0-0015 failed with error -71 uname: $ uname -a Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I found the following thread which solves the problem temporarly (and reports the same problem in Arch): https://bugs.archlinux.org/task/59714 Running the following command enables it again for the current session: sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol' dmesg afterwards: [ 569.522490] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [ 569.544584] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [ 569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8 Before running the fix: $ cat /sys/bus/serio/devices/serio1/protocol ETSMBus and after: $ cat /sys/bus/serio/devices/serio1/protocol ETPS/2 After reboot the command has to be run again, of course. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 15 20:59:36 2018 DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:506a] InstallationDate: Installed on 2018-08-06 (101 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LS001AGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago) dmi.bios.date: 02/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET37W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS0
[Kernel-packages] [Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command
Removing the scsi_mod.use_blk_mq=1 from /etc/default/grub and the mentioned udev rule file, and regenerating initial ramdisk + reboot seems to do the trick, now everything works with default (cfq) I/O scheduler. Before this comment, and the problem: # cat /sys/block/sda/queue/scheduler [bfq] none # cat /sys/block/sdb/queue/scheduler [none] bfq After I removed the BFQ specific stuffs and everything worked again: # cat /sys/block/sda/queue/scheduler noop deadline [cfq] # cat /sys/block/sdb/queue/scheduler noop deadline [cfq] So, sorry about the noise, maybe it was my fault ... Interestingly, this setup of mine with BFQ worked in 17.10 on other machines with that kernel parameter and udev rule I mentioned in the previous comment. -- 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/1762450 Title: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've upgraded to 18.04. Since then, it's impossible to use thumb- drives. If I try, on the first write operation, that operation hangs. Trying to issue a 'sync' command that hangs too. After a while (some minutes or so?) I see the following in kernel log / dmesg (see later). It's not even possible to cleanly shut the computer down, as it also hangs then. kernel is: 4.15.0-15-generic Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -S /boot/vmlinuz-4.15.0-15-generic linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic $ dpkg -l linux-image-4.15.0-15-generic ii linux-image-4.15.0-15-generic4.15.0-15.16 amd64 Linux kernel image for version 4.15.0 on 64 bit x86 SMP dmesg: [ 110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd [ 111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00 [ 111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 111.083441] usb 6-1: Product: DataTraveler 2.0 [ 111.083444] usb 6-1: Manufacturer: Kingston [ 111.083447] usb 6-1: SerialNumber: 5B7402949950 [ 111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected [ 111.157882] scsi host6: usb-storage 6-1:1.0 [ 111.158826] usbcore: registered new interface driver usb-storage [ 111.174387] usbcore: registered new interface driver uas [ 112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 GiB) [ 112.443462] sd 6:0:0:0: [sdb] Write Protect is off [ 112.443464] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 112.443586] sd 6:0:0:0: [sdb] No Caching mode page found [ 112.443591] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 112.447045] sd 6:0:0:0: [sdb] Attached SCSI removable disk this was ok, the problem is from here: [ 363.231738] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 363.231745] Tainted: G OE4.15.0-15-generic #16-Ubuntu [ 363.231747] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.231750] fdisk D0 1798 1728 0x [ 363.231754] Call Trace: [ 363.231764] __schedule+0x297/0x8b0 [ 363.231768] ? fdatawait_one_bdev+0x20/0x20 [ 363.231771] schedule+0x2c/0x80 [ 363.231775] io_schedule+0x16/0x40 [ 363.231779] wait_on_page_bit_common+0xd8/0x160 [ 363.231782] ? page_cache_tree_insert+0xe0/0xe0 [ 363.231785] __filemap_fdatawait_range+0xfa/0x160 [ 363.231788] ? __filemap_fdatawrite_range+0xc1/0x100 [ 363.231791] ? __filemap_fdatawrite_range+0xcd/0x100 [ 363.231794] ? __sync_filesystem+0x60/0x60 [ 363.231797] filemap_fdatawait_keep_errors+0x1e/0x40 [ 363.231799] fdatawait_one_bdev+0x16/0x20 [ 363.231802] iterate_bdevs+0xb7/0x160 [ 363.231805] sys_sync+0x7e/0xb0 [ 363.231809] do_syscall_64+0x73/0x130 [ 363.231813] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 363.231816] RIP: 0033:0x7f2fcff17287 [ 363.231817] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 00a2 [ 363.231820] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287 [ 363.231821] RDX: RSI: 56096b766018 RDI: 56096b767400 [ 363.231823] RBP: 7fffbbea82d8 R08: 000a R09: 7472617020656854 [ 363.231824] R10: 0008 R11: 0202 R12: 56096a25b198 [ 363.231825] R13: R14: 56096a25b198 R15: [ 484.045928] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 484.045934] Tainted: G
[Kernel-packages] [Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command
Ok, I will investigate as soon as I have time. By the way, I am
wondering if using BFQ as I/O scheduler can be the problem, ie:
# cat /etc/udev/rules.d/60-schedulers.rules
## set noop scheduler for non-rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0",
ATTR{queue/scheduler}="noop"
## set bfq scheduler for rotating disks
ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="1",
ATTR{queue/scheduler}="bfq"
# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic
root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash
scsi_mod.use_blk_mq=1 vt.handoff=1
I guess, I try to remove BFQ specific stuffs as well to see if this
fixes the problem.
--
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/1762450
Title:
[18.04] writing on thumb drives causes hang for write op, shutdown and
'sync' command
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
I've upgraded to 18.04. Since then, it's impossible to use thumb-
drives. If I try, on the first write operation, that operation hangs.
Trying to issue a 'sync' command that hangs too. After a while (some
minutes or so?) I see the following in kernel log / dmesg (see later).
It's not even possible to cleanly shut the computer down, as it also
hangs then.
kernel is:
4.15.0-15-generic
Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ dpkg -S /boot/vmlinuz-4.15.0-15-generic
linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic
$ dpkg -l linux-image-4.15.0-15-generic
ii linux-image-4.15.0-15-generic4.15.0-15.16 amd64
Linux kernel image for version 4.15.0 on 64 bit x86 SMP
dmesg:
[ 110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd
[ 111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00
[ 111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 111.083441] usb 6-1: Product: DataTraveler 2.0
[ 111.083444] usb 6-1: Manufacturer: Kingston
[ 111.083447] usb 6-1: SerialNumber: 5B7402949950
[ 111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected
[ 111.157882] scsi host6: usb-storage 6-1:1.0
[ 111.158826] usbcore: registered new interface driver usb-storage
[ 111.174387] usbcore: registered new interface driver uas
[ 112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP
PQ: 0 ANSI: 0 CCS
[ 112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06
GB/1.92 GiB)
[ 112.443462] sd 6:0:0:0: [sdb] Write Protect is off
[ 112.443464] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 112.443586] sd 6:0:0:0: [sdb] No Caching mode page found
[ 112.443591] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 112.447045] sd 6:0:0:0: [sdb] Attached SCSI removable disk
this was ok, the problem is from here:
[ 363.231738] INFO: task fdisk:1798 blocked for more than 120 seconds.
[ 363.231745] Tainted: G OE4.15.0-15-generic #16-Ubuntu
[ 363.231747] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.231750] fdisk D0 1798 1728 0x
[ 363.231754] Call Trace:
[ 363.231764] __schedule+0x297/0x8b0
[ 363.231768] ? fdatawait_one_bdev+0x20/0x20
[ 363.231771] schedule+0x2c/0x80
[ 363.231775] io_schedule+0x16/0x40
[ 363.231779] wait_on_page_bit_common+0xd8/0x160
[ 363.231782] ? page_cache_tree_insert+0xe0/0xe0
[ 363.231785] __filemap_fdatawait_range+0xfa/0x160
[ 363.231788] ? __filemap_fdatawrite_range+0xc1/0x100
[ 363.231791] ? __filemap_fdatawrite_range+0xcd/0x100
[ 363.231794] ? __sync_filesystem+0x60/0x60
[ 363.231797] filemap_fdatawait_keep_errors+0x1e/0x40
[ 363.231799] fdatawait_one_bdev+0x16/0x20
[ 363.231802] iterate_bdevs+0xb7/0x160
[ 363.231805] sys_sync+0x7e/0xb0
[ 363.231809] do_syscall_64+0x73/0x130
[ 363.231813] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 363.231816] RIP: 0033:0x7f2fcff17287
[ 363.231817] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX:
00a2
[ 363.231820] RAX: ffda RBX: 56096b767400 RCX:
7f2fcff17287
[ 363.231821] RDX: RSI: 56096b766018 RDI:
56096b767400
[ 363.231823] RBP: 7fffbbea82d8 R08: 000a R09:
7472617020656854
[ 363.231824] R10: 0008 R11: 0202 R12:
56096a25b198
[ 363.231825] R13: R14: 56096a25b198 R15:
[ 484.045928] INFO: task fdisk:1798 blocked for more than 120 seconds.
[ 484.045934] Tainted: G OE4.15.0-15-generic #16-Ubuntu
[Kernel-packages] [Bug 1762450] Re: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command
[22596.884250] sysrq: SysRq : This sysrq operation is disabled. I got this, if I try to trigger those sysreq events by echoing t/m into that procfs file. I'm anyway curious how sysreq stuffs can be enabled/disabled, since I seldom use ALT-SYSREQ- combos as well, and many of them just reports the same as with this procfs trigger: operation is disabled. One thing though: If I attach the thumb drive, everything is fine, lsblk shows it, etc, I can remove it, lsblk does not show it, no problem. The problem seems to have after the first event when I try to write onto the device, then whatever I try even remove thumb drive physically, lsblk still shows it, all the "sync" commands (and anything which tries to write onto) stuck and cannot be killed. So even shutdown of system is problematic at this point. Now I've tried fdisk (btw, no partition on the thumb drive). Just displaying, everything is OK. However after the "w" command the problems begins. By checking the /proc entry for the PID of the fdisk, I see: # cat /proc/11283/status Name: fdisk Umask: 0022 State: D (disk sleep) [...] # cat /proc/11283/stat 11283 (fdisk) D 11084 11283 10324 34827 11283 4194560 673 0 4 0 0 1 0 0 20 0 1 0 2254524 21024768 877 18446744073709551615 94293651558400 94293651671008 140732927217664 0 0 0 0 0 0 1 0 0 17 1 0 0 16 0 0 94293653771504 94293653778500 94293676326912 140732927223610 140732927223625 140732927223625 140732927225836 0 Full output of status file: # cat /proc/11283/status Name: fdisk Umask: 0022 State: D (disk sleep) Tgid: 11283 Ngid: 0 Pid:11283 PPid: 11084 TracerPid: 0 Uid:0 0 0 0 Gid:0 0 0 0 FDSize: 256 Groups: 0 NStgid: 11283 NSpid: 11283 NSpgid: 11283 NSsid: 10324 VmPeak:21568 kB VmSize:20532 kB VmLck: 0 kB VmPin: 0 kB VmHWM: 4176 kB VmRSS: 3508 kB RssAnon: 372 kB RssFile:3136 kB RssShmem: 0 kB VmData: 284 kB VmStk: 132 kB VmExe: 112 kB VmLib: 3144 kB VmPTE:80 kB VmSwap:0 kB HugetlbPages: 0 kB CoreDumping:0 Threads:1 SigQ: 0/13289 SigPnd: ShdPnd: SigBlk: SigIgn: SigCgt: CapInh: CapPrm: 003f CapEff: 003f CapBnd: 003f CapAmb: NoNewPrivs: 0 Seccomp:0 Cpus_allowed: f Cpus_allowed_list: 0-3 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches:73 nonvoluntary_ctxt_switches: 0 -- 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/1762450 Title: [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command Status in linux package in Ubuntu: Confirmed Bug description: I've upgraded to 18.04. Since then, it's impossible to use thumb- drives. If I try, on the first write operation, that operation hangs. Trying to issue a 'sync' command that hangs too. After a while (some minutes or so?) I see the following in kernel log / dmesg (see later). It's not even possible to cleanly shut the computer down, as it also hangs then. kernel is: 4.15.0-15-generic Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -S /boot/vmlinuz-4.15.0-15-generic linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic $ dpkg -l linux-image-4.15.0-15-generic ii linux-image-4.15.0-15-generic4.15.0-15.16 amd64 Linux kernel image for version 4.15.0 on 64 bit x86 SMP dmesg: [ 110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd [ 111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00 [ 111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 111.083441] usb 6-1: Product: DataTraveler 2.0 [ 111.083444] usb 6-1: Manufacturer: Kingston [ 111.083447] usb 6-1: SerialNumber: 5B7402949950 [ 111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected [ 111.157882] scsi host6: usb-storage 6-1:1.0 [ 111.158826] usbcore: registered new interface driver usb-storage [ 111.174387] usbcore: registered new interface driver uas [ 112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 GiB) [ 112.443462] sd 6:0:0:0: [sdb]
[Kernel-packages] [Bug 1762450] [NEW] [18.04] writing on thumb drives causes hang for write op, shutdown and 'sync' command
Public bug reported: I've upgraded to 18.04. Since then, it's impossible to use thumb-drives. If I try, on the first write operation, that operation hangs. Trying to issue a 'sync' command that hangs too. After a while (some minutes or so?) I see the following in kernel log / dmesg (see later). It's not even possible to cleanly shut the computer down, as it also hangs then. kernel is: 4.15.0-15-generic Linux oxygene 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -S /boot/vmlinuz-4.15.0-15-generic linux-image-4.15.0-15-generic: /boot/vmlinuz-4.15.0-15-generic $ dpkg -l linux-image-4.15.0-15-generic ii linux-image-4.15.0-15-generic4.15.0-15.16 amd64 Linux kernel image for version 4.15.0 on 64 bit x86 SMP dmesg: [ 110.931501] usb 6-1: new high-speed USB device number 2 using xhci_hcd [ 111.083432] usb 6-1: New USB device found, idVendor=13fe, idProduct=1d00 [ 111.083438] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 111.083441] usb 6-1: Product: DataTraveler 2.0 [ 111.083444] usb 6-1: Manufacturer: Kingston [ 111.083447] usb 6-1: SerialNumber: 5B7402949950 [ 111.157729] usb-storage 6-1:1.0: USB Mass Storage device detected [ 111.157882] scsi host6: usb-storage 6-1:1.0 [ 111.158826] usbcore: registered new interface driver usb-storage [ 111.174387] usbcore: registered new interface driver uas [ 112.172295] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [ 112.203451] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 112.443337] sd 6:0:0:0: [sdb] 4030464 512-byte logical blocks: (2.06 GB/1.92 GiB) [ 112.443462] sd 6:0:0:0: [sdb] Write Protect is off [ 112.443464] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 112.443586] sd 6:0:0:0: [sdb] No Caching mode page found [ 112.443591] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 112.447045] sd 6:0:0:0: [sdb] Attached SCSI removable disk this was ok, the problem is from here: [ 363.231738] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 363.231745] Tainted: G OE4.15.0-15-generic #16-Ubuntu [ 363.231747] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.231750] fdisk D0 1798 1728 0x [ 363.231754] Call Trace: [ 363.231764] __schedule+0x297/0x8b0 [ 363.231768] ? fdatawait_one_bdev+0x20/0x20 [ 363.231771] schedule+0x2c/0x80 [ 363.231775] io_schedule+0x16/0x40 [ 363.231779] wait_on_page_bit_common+0xd8/0x160 [ 363.231782] ? page_cache_tree_insert+0xe0/0xe0 [ 363.231785] __filemap_fdatawait_range+0xfa/0x160 [ 363.231788] ? __filemap_fdatawrite_range+0xc1/0x100 [ 363.231791] ? __filemap_fdatawrite_range+0xcd/0x100 [ 363.231794] ? __sync_filesystem+0x60/0x60 [ 363.231797] filemap_fdatawait_keep_errors+0x1e/0x40 [ 363.231799] fdatawait_one_bdev+0x16/0x20 [ 363.231802] iterate_bdevs+0xb7/0x160 [ 363.231805] sys_sync+0x7e/0xb0 [ 363.231809] do_syscall_64+0x73/0x130 [ 363.231813] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 363.231816] RIP: 0033:0x7f2fcff17287 [ 363.231817] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 00a2 [ 363.231820] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287 [ 363.231821] RDX: RSI: 56096b766018 RDI: 56096b767400 [ 363.231823] RBP: 7fffbbea82d8 R08: 000a R09: 7472617020656854 [ 363.231824] R10: 0008 R11: 0202 R12: 56096a25b198 [ 363.231825] R13: R14: 56096a25b198 R15: [ 484.045928] INFO: task fdisk:1798 blocked for more than 120 seconds. [ 484.045934] Tainted: G OE4.15.0-15-generic #16-Ubuntu [ 484.045936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.045939] fdisk D0 1798 1728 0x [ 484.045942] Call Trace: [ 484.045950] __schedule+0x297/0x8b0 [ 484.045954] ? fdatawait_one_bdev+0x20/0x20 [ 484.045956] schedule+0x2c/0x80 [ 484.045959] io_schedule+0x16/0x40 [ 484.045962] wait_on_page_bit_common+0xd8/0x160 [ 484.045965] ? page_cache_tree_insert+0xe0/0xe0 [ 484.045967] __filemap_fdatawait_range+0xfa/0x160 [ 484.045970] ? __filemap_fdatawrite_range+0xc1/0x100 [ 484.045972] ? __filemap_fdatawrite_range+0xcd/0x100 [ 484.045975] ? __sync_filesystem+0x60/0x60 [ 484.045977] filemap_fdatawait_keep_errors+0x1e/0x40 [ 484.045979] fdatawait_one_bdev+0x16/0x20 [ 484.045981] iterate_bdevs+0xb7/0x160 [ 484.045984] sys_sync+0x7e/0xb0 [ 484.045987] do_syscall_64+0x73/0x130 [ 484.045990] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 484.045992] RIP: 0033:0x7f2fcff17287 [ 484.045994] RSP: 002b:7fffbbea61a8 EFLAGS: 0202 ORIG_RAX: 00a2 [ 484.045996] RAX: ffda RBX: 56096b767400 RCX: 7f2fcff17287 [ 484.045997] RDX: RSI: 56096b766018 RDI: 56096b
[Kernel-packages] [Bug 1373070] Re: full fix for disconnected path (paths)
Same problem with powerdns, I can't run it with apparmor profile, because it complains: operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/pdns_server" name="run/systemd/journal/dev- log" pid=17236 comm="pdns_server" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 I am not an expert, but I tried to put run/systemd/journal/dev-log into the profile, but it is not accepted as it does not start with / ... But this is what kernel log suggest, so what can I do otherwise? Note: I have: /usr/sbin/pdns_server flags=(complain,attach_disconnected) But still ... (now I have only complain mode). If I exclude pdns from systemd it works btw, and no wonder as it seems the problem somehow connected to systemd's journal, so it's better not to use systemd if possible since it renders apparmor unusable in my experience :( But for sure, I would be more than happy to have a better option, rather than deleting systemd's unit file each time after upgrade pdns ... Or so. this is up-to-date Ubuntu 16.04.3 LTS 64 bit, fresh install, but I have about a dozen of servers with this problem with different daemons as well, not only powerdns. -- 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/1373070 Title: full fix for disconnected path (paths) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: Confirmed Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+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 1629661] Re: Hissing sound in headphones
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Confirmed ** Description changed: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: lgb2128 F pulseaudio - /dev/snd/controlC0: lgb2128 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: lgb2128 F pulseaudio + /dev/snd/controlC0: lgb2128 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 2 14:24:21 2016 HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1 InstallationDate: Installed on 2015-07-10 (449 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-41-generic N/A - linux-backports-modules-4.4.0-41-generic N/A - linux-firmware1.157.4 + linux-restricted-modules-4.4.0-41-generic N/A + linux-backports-modules-4.4.0-41-generic N/A + linux-firmware1.157.4 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: FM2A88M Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Tags added: kernel-bug-exists-upstream -- 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/1629661 Title: Hissing sound in headphones Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lgb2128 F pulseaudio /dev/snd/controlC0: lgb2128 F pulseaudio Curren
[Kernel-packages] [Bug 1629661] Re: Hissing sound in headphones
Sorry about my English, so I meant that I didn't own the machine itself, so I have no experience just since I use that PC, and it's only two weeks or so. Also, I've just discovered that the annoying sound is there even right after switching the machine on, without any OS loaded too. -- 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/1629661 Title: Hissing sound in headphones Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lgb2128 F pulseaudio /dev/snd/controlC0: lgb2128 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 2 14:24:21 2016 HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1 InstallationDate: Installed on 2015-07-10 (449 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-41-generic N/A linux-backports-modules-4.4.0-41-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: FM2A88M Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629661/+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 1629661] Re: Hissing sound in headphones
$ uname -a Linux oxygene 4.8.0-040800-generic #201610022031 SMP Mon Oct 3 00:32:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux The really same. Moreover, this hissing sound can be heard with BIOS/etc too, without any OS, it's even more louder then. The issue started with this machine, I didn't have it with previous ubuntu versions ... -- 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/1629661 Title: Hissing sound in headphones Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lgb2128 F pulseaudio /dev/snd/controlC0: lgb2128 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 2 14:24:21 2016 HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1 InstallationDate: Installed on 2015-07-10 (449 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-41-generic N/A linux-backports-modules-4.4.0-41-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: FM2A88M Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629661/+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 1629661] Re: Hissing sound in headphones
Quite odd ... But it seems there is sometimes a louder hissing sound, but the other one is more frequent issue: a not so loud but annoying one. This second _seems_ to be cause (I have no idea about the reason!!) by an XBox 360 controller. If it's plugged to the USB port, the sound can be heard in sync with the blinking "circular green LED" on the controller. After it stops blinking, the sound remains. If I unplug from the USB port, the annoying noise is stopped. Maybe it's not even a software issue, but some kind of hardware, interference, or whatever? -- 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/1629661 Title: Hissing sound in headphones Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lgb2128 F pulseaudio /dev/snd/controlC0: lgb2128 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 2 14:24:21 2016 HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1 InstallationDate: Installed on 2015-07-10 (449 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-41-generic N/A linux-backports-modules-4.4.0-41-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: FM2A88M Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629661/+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 1629661] [NEW] Hissing sound in headphones
Public bug reported: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lgb2128 F pulseaudio /dev/snd/controlC0: lgb2128 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 2 14:24:21 2016 HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1 InstallationDate: Installed on 2015-07-10 (449 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic root=UUID=d203063e-78c0-425a-bee2-0e3ecb4ea74c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-41-generic N/A linux-backports-modules-4.4.0-41-generic N/A linux-firmware1.157.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: FM2A88M Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd01/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed third-party-packages xenial ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1629661/+attachment/4752825/+files/lspci-vnvn.log -- 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/1629661 Title: Hissing sound in headphones Status in linux package in Ubuntu: New Bug description: Ubuntu 16.04 on 64 bit produces hissing sound (just by my - far from being 'musical' - ear, it sounds like a sinus wave with frequency about 1KHz or so) on headphones. Interestingly, after boot this does not happen and usually can be hear only after the first application which makes any sound (but not always, sometimes it starts later). But if any time it starts, it remains, whatever I do, exiting the application (which makes the sound) even by killing pulseaudio process, etc. I've read a lot on this issue but usually - it seems - always notebook problems mentioned, however it's a desktop machine (Asrock FM2A88M extreme4+ motherboard, AMD A6-6400K CPU, integrated audio). It seems it uses snd_hda_intel kernel module though. I've tried advices mentioned by various resources throughout the net, disabling powersave problems, using hdajackretask from alsa-tools-gui, etc, but they didn't help. Ubuntu 4.4.0-36.55-generic 4.4.16 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-41-generic 4.4.0-41.61 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lgb2128 F pulseaudio /dev/snd/controlC0: lgb2128 F pulseaudio CurrentDesktop: Unity Date: Sun Oct 2 14:24:21 2016 HibernationDevice: RESUME=UUID=c92777cb-b700-4a8e-b937-1ed4983fecb1 InstallationDate: Installed on 2015-07-10 (449 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB
[Kernel-packages] [Bug 1615082] Re: kernel NULL pointer dereference on apparmor profile update
It's a problem that it's a production server, I cannot play too much with it :-/ It was a freshly installed 16.04LTS according to the operators who did the install. According to the logs, the problematic kernel was: Linux version 4.4.0-34-generic (buildd@lgw01-20) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 (Ubuntu 4.4.0-34.53-generic 4.4.15) It was installed with: Linux version 4.4.0-31-generic (buildd@lgw01-16) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 (Ubuntu 4.4.0- 31.50-generic 4.4.13) The -34- was already a kernel since upgrade packages. Now I have -36-, I haven't experienced with the bug yet since then at least. Additionaly, after the panic msg, every processes was stuck in 'D' state trying to do anything with apparmor (etc profile reload) including the postinst script of lxd which seems does that. After a reboot with -36- kernel, I could finish the upgrade with "dpkg --configure -a" though. If I again experience the bug, I'll try to test with latest upstream as you suggested (unfortunately, as I've told, I cannot "play" with this machine if it seems to be OK ...) -- 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/1615082 Title: kernel NULL pointer dereference on apparmor profile update Status in linux package in Ubuntu: Incomplete Bug description: I've used aa-logprof to find more things out to be added to my custom apache2 apparmor file. Since PHP created tons of files in /tmp in the form of /tmp/php* I've decided to add this: /tmp/php* rw, I'm not sure if it caused the problem, but after this /etc/init.d/apparmor reload froze and there was the following in the output of dmesg command: [13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" pid=23590 comm="apparmor_parser" [13838.920067] [ cut here ] [13838.920079] WARNING: CPU: 0 PID: 23590 at /build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 profile_cmp+0xed/0x180() [13838.920083] AppArmor WARN profile_cmp: ((!b)): [13838.920085] Modules linked in: [13838.920088] binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper [13838.920166] syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core pata_acpi fjes [13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 4.4.0-34-generic #53-Ubuntu [13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 10/30/2010 [13838.920195] 0086 88f44738 880128bffc00 813f11b3 [13838.920199] 880128bffc48 81cf08e8 880128bffc38 81081102 [13838.920204] 8800c8d7d400 000a [13838.920208] Call Trace: [13838.920218] [] dump_stack+0x63/0x90 [13838.920224] [] warn_slowpath_common+0x82/0xc0 [13838.920228] [] warn_slowpath_fmt+0x5c/0x80 [13838.920232] [] ? u32_swap+0x10/0x10 [13838.920236] [] profile_cmp+0xed/0x180 [13838.920239] [] aa_vec_unique+0x163/0x240 [13838.920244] [] __aa_labelset_update_subtree+0x687/0x820 [13838.920249] [] ? kzfree+0x2d/0x40 [13838.920254] [] aa_replace_profiles+0x59b/0xb70 [13838.920259] [] ? __kmalloc+0x22e/0x250 [13838.920263] [] policy_update+0x9f/0x1f0 [13838.920267] [] profile_replace+0x13/0x20 [13838.920272] [] __vfs_write+0x18/0x40 [13838.920275] [] vfs_write+0xa9/0x1a0 [13838.920279] [] ? do_sys_open+0x1bf/0x2a0 [13838.920282] [] SyS_write+0x55/0xc0 [13838.920288] [] entry_SYSCALL_64_fastpath+0x16/0x71 [13838.920291] ---[ end trace a19473a0fd8d9556 ]--- [13838.920305] BUG: unable to handle kernel NULL pointer dereference at 0038 [13838.920475] IP: [] profile_cmp+0x2f/0x180 [13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 [13838.920684] Oops: [#1] SMP [13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_
[Kernel-packages] [Bug 1615082] Re: kernel NULL pointer dereference on apparmor profile update
I've also attached some files, with full dmesg output, uname -a, lspci, version info, and the apparmor profile for apache2. ** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615082/+attachment/4724162/+files/bug-info.tgz -- 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/1615082 Title: kernel NULL pointer dereference on apparmor profile update Status in linux package in Ubuntu: New Bug description: I've used aa-logprof to find more things out to be added to my custom apache2 apparmor file. Since PHP created tons of files in /tmp in the form of /tmp/php* I've decided to add this: /tmp/php* rw, I'm not sure if it caused the problem, but after this /etc/init.d/apparmor reload froze and there was the following in the output of dmesg command: [13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" pid=23590 comm="apparmor_parser" [13838.920067] [ cut here ] [13838.920079] WARNING: CPU: 0 PID: 23590 at /build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 profile_cmp+0xed/0x180() [13838.920083] AppArmor WARN profile_cmp: ((!b)): [13838.920085] Modules linked in: [13838.920088] binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper [13838.920166] syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core pata_acpi fjes [13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 4.4.0-34-generic #53-Ubuntu [13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 10/30/2010 [13838.920195] 0086 88f44738 880128bffc00 813f11b3 [13838.920199] 880128bffc48 81cf08e8 880128bffc38 81081102 [13838.920204] 8800c8d7d400 000a [13838.920208] Call Trace: [13838.920218] [] dump_stack+0x63/0x90 [13838.920224] [] warn_slowpath_common+0x82/0xc0 [13838.920228] [] warn_slowpath_fmt+0x5c/0x80 [13838.920232] [] ? u32_swap+0x10/0x10 [13838.920236] [] profile_cmp+0xed/0x180 [13838.920239] [] aa_vec_unique+0x163/0x240 [13838.920244] [] __aa_labelset_update_subtree+0x687/0x820 [13838.920249] [] ? kzfree+0x2d/0x40 [13838.920254] [] aa_replace_profiles+0x59b/0xb70 [13838.920259] [] ? __kmalloc+0x22e/0x250 [13838.920263] [] policy_update+0x9f/0x1f0 [13838.920267] [] profile_replace+0x13/0x20 [13838.920272] [] __vfs_write+0x18/0x40 [13838.920275] [] vfs_write+0xa9/0x1a0 [13838.920279] [] ? do_sys_open+0x1bf/0x2a0 [13838.920282] [] SyS_write+0x55/0xc0 [13838.920288] [] entry_SYSCALL_64_fastpath+0x16/0x71 [13838.920291] ---[ end trace a19473a0fd8d9556 ]--- [13838.920305] BUG: unable to handle kernel NULL pointer dereference at 0038 [13838.920475] IP: [] profile_cmp+0x2f/0x180 [13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 [13838.920684] Oops: [#1] SMP [13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit [13838.922791] ttm drm_kms_helper syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core pata_acpi fjes [13838.923223] CPU: 0 PI
[Kernel-packages] [Bug 1615082] [NEW] kernel NULL pointer dereference on apparmor profile update
Public bug reported: I've used aa-logprof to find more things out to be added to my custom apache2 apparmor file. Since PHP created tons of files in /tmp in the form of /tmp/php* I've decided to add this: /tmp/php* rw, I'm not sure if it caused the problem, but after this /etc/init.d/apparmor reload froze and there was the following in the output of dmesg command: [13838.909880] audit: type=1400 audit(1471631019.426:1488): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/apache2" pid=23590 comm="apparmor_parser" [13838.920067] [ cut here ] [13838.920079] WARNING: CPU: 0 PID: 23590 at /build/linux-5vkMGy/linux-4.4.0/security/apparmor/label.c:142 profile_cmp+0xed/0x180() [13838.920083] AppArmor WARN profile_cmp: ((!b)): [13838.920085] Modules linked in: [13838.920088] binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper [13838.920166] syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core pata_acpi fjes [13838.920188] CPU: 0 PID: 23590 Comm: apparmor_parser Not tainted 4.4.0-34-generic #53-Ubuntu [13838.920192] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 10/30/2010 [13838.920195] 0086 88f44738 880128bffc00 813f11b3 [13838.920199] 880128bffc48 81cf08e8 880128bffc38 81081102 [13838.920204] 8800c8d7d400 000a [13838.920208] Call Trace: [13838.920218] [] dump_stack+0x63/0x90 [13838.920224] [] warn_slowpath_common+0x82/0xc0 [13838.920228] [] warn_slowpath_fmt+0x5c/0x80 [13838.920232] [] ? u32_swap+0x10/0x10 [13838.920236] [] profile_cmp+0xed/0x180 [13838.920239] [] aa_vec_unique+0x163/0x240 [13838.920244] [] __aa_labelset_update_subtree+0x687/0x820 [13838.920249] [] ? kzfree+0x2d/0x40 [13838.920254] [] aa_replace_profiles+0x59b/0xb70 [13838.920259] [] ? __kmalloc+0x22e/0x250 [13838.920263] [] policy_update+0x9f/0x1f0 [13838.920267] [] profile_replace+0x13/0x20 [13838.920272] [] __vfs_write+0x18/0x40 [13838.920275] [] vfs_write+0xa9/0x1a0 [13838.920279] [] ? do_sys_open+0x1bf/0x2a0 [13838.920282] [] SyS_write+0x55/0xc0 [13838.920288] [] entry_SYSCALL_64_fastpath+0x16/0x71 [13838.920291] ---[ end trace a19473a0fd8d9556 ]--- [13838.920305] BUG: unable to handle kernel NULL pointer dereference at 0038 [13838.920475] IP: [] profile_cmp+0x2f/0x180 [13838.920582] PGD 128a7d067 PUD 12a6be067 PMD 0 [13838.920684] Oops: [#1] SMP [13838.920755] Modules linked in: binfmt_misc nf_conntrack_ftp nf_conntrack_irc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_NFLOG nfnetlink_log nfnetlink xt_tcpudp xt_pkttype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables gpio_ich ipmi_devintf coretemp ipmi_ssif kvm dcdbas irqbypass i5000_edac serio_raw edac_core lpc_ich joydev input_leds i5k_amb ipmi_si 8250_fintek ipmi_msghandler shpchp mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure amdkfd amd_iommu_v2 radeon i2c_algo_bit [13838.922791] ttm drm_kms_helper syscopyarea sysfillrect sysimgblt hid_generic fb_sys_fops usbhid uas e1000e ptp hid usb_storage psmouse drm megaraid_sas bnx2 pps_core pata_acpi fjes [13838.923223] CPU: 0 PID: 23590 Comm: apparmor_parser Tainted: GW 4.4.0-34-generic #53-Ubuntu [13838.923369] Hardware name: Dell Inc. PowerEdge 1950/0DT097, BIOS 2.7.0 10/30/2010 [13838.923485] task: 880035b86400 ti: 880128bfc000 task.ti: 880128bfc000 [13838.923599] RIP: 0010:[] [] profile_cmp+0x2f/0x180 [13838.923734] RSP: 0018:880128bffcb0 EFLAGS: 00010086 [13838.923816] RAX: RBX: 8800c8d7d400 RCX: 0006 [13838.923916] RDX: RSI: RDI: 0009 [13838.924017] RBP: 880128bffcc0 R08: 000a R09: 0562 [1383
