[Kernel-packages] [Bug 2025230] Re: linux-headers-6.2.0-24-generic missing in ubuntu 23.04
** Changed in: linux-meta (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2025230 Title: linux-headers-6.2.0-24-generic missing in ubuntu 23.04 Status in linux-meta package in Ubuntu: Fix Released Bug description: The latest linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 linux-image-generic-hwe-22.04 versions cannot be installed on ubuntu 23.04 because the linux-headers-6.2.0-24-generic package is missing. The latest available version is linux-headers-6.2.0-23-generic Source: https://packages.ubuntu.com/search?keywords=linux-headers-6.2.0-=names=lunar=all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025230/+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 2025230] [NEW] linux-headers-6.2.0-24-generic missing in ubuntu 23.04
Public bug reported: The latest linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 linux-image-generic-hwe-22.04 versions cannot be installed on ubuntu 23.04 because the linux-headers-6.2.0-24-generic package is missing. The latest available version is linux-headers-6.2.0-23-generic Source: https://packages.ubuntu.com/search?keywords=linux-headers-6.2.0-=names=lunar=all ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2025230 Title: linux-headers-6.2.0-24-generic missing in ubuntu 23.04 Status in linux-meta package in Ubuntu: New Bug description: The latest linux-generic-hwe-22.04 linux-headers-generic-hwe-22.04 linux-image-generic-hwe-22.04 versions cannot be installed on ubuntu 23.04 because the linux-headers-6.2.0-24-generic package is missing. The latest available version is linux-headers-6.2.0-23-generic Source: https://packages.ubuntu.com/search?keywords=linux-headers-6.2.0-=names=lunar=all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025230/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
I now tested with newer kernels: The regression is still present in 5.15.0-33-generic from the hwe-edge package for Ubuntu 20.04. I also tested kernels from the Ubuntu Mainline Kernel Archive. It works with 5.13.0-051300-generic and fails with 5.14.0-051400-generic and also still with 5.18.3-051803-generic. So this is consistent with my hypothesis about which commit is the problem. Is there a chance to get this resolved? If I can be of any further help, e.g., by testing more kernel versions, please let me know! -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2
[Kernel-packages] [Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
I have now tested whether the issue is still resolved and it luckily is. So both after installing a version of amdgpu-pro and also after uninstalling this proprietary driver again, unlocking the system works again. Once the stable version of Ubuntu 22.04 is published, I will upgrade and try again. At this point, I don’t want to try a pre-release version to avoid having my only personal computer become inoperable. Also, I have yet to find a way to restore the resolution during the boot process. Specifically, the default resolution is used during the cryptsetup decryption stage and before (when only the mainboard manufacturer logo is shown). The BIOS configuration seems to be in order and is set to use the primary PCIe slot to which my monitor is connected. It’s not terrible that this is so, but I’d like to fix it. My internet searches have been unsuccessful though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+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 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
Yes, I believe having installed a proprietary driver could’ve caused this. I didn’t realize this at the time of installing the driver, but I think the file name "amdgpu-pro-21.20-1271047-ubuntu-20.04" clearly indicates that this is in fact AMD’s proprietary driver. Curiously, the issue didn’t happen immediately after installing this driver and rebooting. I used the computer for at least two sessions after this and everything was seemingly fine. In any case, things are mostly in order now. I have yet to test if my initially reported issue of locking the computer crashing the driver is still resolved. I will get back with an updated report on this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+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 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
After the things I did in https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.13/+bug/1964711/comments/7, I am now facing a worse problem. My computer no longer recognizes my display correctly. Since the boot screen, the resolution is the minimum available (1024x768). I think my system no longer selects the correct driver for my graphics card. Running "sudo lshw -c video" yields the following: ``` *-display UNCLAIMED description: VGA compatible controller product: Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:03:00.0 version: ca width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:4000-4fff memory:5000-501f ioport:3000(size=256) memory:5030-5037 memory:c-d ``` Running "lsmod | grep amd" prints nothing (it used to before) and "dkms status amdgpu" also prints nothing. I tried uninstalling the drivers I installed and also tried installing drivers from different source. I tried to look for issues in my BIOS settings. All to no avail. If I don’t find a solution to this, I will resort to completely re-installing Ubuntu 20.04. I have luckily completed a full backup before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+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 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked
I’ve done the following things now: Unsuccessful: Upgrade from Ubuntu 20.04 to 21.04. This did not solve the issue. Successful: Manually uninstall and install the latest amdgpu package from https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified- linux-21-20. Specifically, I downloaded amdgpu- pro-21.20-1271047-ubuntu-20.04.tar.xz and installed it via the amdgpu- install binary. This seems to have solved the issue. I reckon there is a good chance that it was rather uninstalling and reinstalling the driver than installing a specific version of it, but that I can’t tell with certainty. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down the power button. The attached monitor does not receive a signal from the computer during these attempts. This started to happen several weeks ago and worked without a problem before then. Due to the nature of this issue, I can neither report any errors occurring nor can I observe any other out of the ordinary things from happening. Thus, I don’t know which package is causing the issue. Also, this issue happens every time I leave the computer unattended for a longer time and lock it. However, locking it and triggering an input immediately after does produce the lock screen, so the lock screen seems to work in principle. Description: Ubuntu 20.04.4 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+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 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
This is a kernel regression and now almost three months old. Could somebody please have a look? -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116,
[Kernel-packages] [Bug 1947718] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534264/+files/ProcInterrupts.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio
[Kernel-packages] [Bug 1947718] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534263/+files/ProcCpuinfoMinimal.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root
[Kernel-packages] [Bug 1947718] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534266/+files/UdevDb.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19
[Kernel-packages] [Bug 1947718] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534267/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU ---
[Kernel-packages] [Bug 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
Status set to "Confirmed" as requested by the bot after uploading logs (although I did upload them when creating the issue as well...). -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19
[Kernel-packages] [Bug 1947718] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534261/+files/Lsusb-v.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19
[Kernel-packages] [Bug 1947718] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534260/+files/Lspci-vt.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19
[Kernel-packages] [Bug 1947718] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534265/+files/ProcModules.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1
[Kernel-packages] [Bug 1947718] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534262/+files/ProcCpuinfo.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1
[Kernel-packages] [Bug 1947718] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1947718/+attachment/5534259/+files/Lspci.txt -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42
[Kernel-packages] [Bug 1947718] Re: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
apport information ** Tags added: apport-collected ** Description changed: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Oct 19 04:42 seq + crw-rw 1 root audio 116, 33 Oct 19 04:42 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' + CasperMD5CheckResult: skip
[Kernel-packages] [Bug 1947718] [NEW] overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732
Public bug reported: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the following command: mkdir /tmp/test /tmp/test/upper /tmp/test/work unshare -m -U -r mount -t overlay none / -o lowerdir=/,upperdir=/tmp/test/upper,workdir=/tmp/test/work On an older kernel, this works and outputs nothing. On the affected kernels, it outputs mount: /: wrong fs type, bad option, bad superblock on none, missing codepage or helper program, or other error. I strongly suspect that this is due to commit "ovl: prevent private clone if bind mount is not allowed" (https://github.com/torvalds/linux/commit/427215d85e8d1476da1a86b8d67aceb485eb3631), which is supposed to fix CVE-2021-3732 and was backported to the affected Ubuntu kernels. This would likely mean that also all other supported Ubuntu versions are affected and also upstream kernel (but I did not test this). My testing indicates that the mount problem exists whenever I want to use a directory as lowerdir that has some mountpoints below. For example, using / or /dev as lowerdir does not work, but lowerdir=/dev/shm works even on the affected kernels. Of course I can understand the problem of CVE-2021-3732, but the current fix is clearly a regression for legitimate behavior. My use case is that I want to create a container for sandboxing purposes where I want to mount overlays inside a user+mount namespace over the whole visible filesystem hierarchy. (Note that in this use case, I iterate over all mount points and create an overlay mount for each existing mount point, I do not expect a single overlay mount to have meaningful cross-mountpoint behavior. So my use case is not affected by the security problem. But for this I still need to be able to create overlay mounts for all mount points, including non-leave mountpoints.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-89-generic 5.4.0-89.100 ProcVersionSignature: User Name 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 19 04:42 seq crw-rw 1 root audio 116, 33 Oct 19 04:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: skip CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Oct 19 12:15:01 2021 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-89-generic N/A linux-backports-modules-5.4.0-89-generic N/A linux-firmware1.187.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-5.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.14.0-0-g155821a1990b-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.2:cvnQEMU:ct1:cvrpc-i440fx-5.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-5.2 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1947718 Title: overlay: permission regression in 5.4.0.89.93 due to fix for CVE-2021-3732 Status in linux package in Ubuntu: New Bug description: Since kernel 5.4.0-89.100 on Focal and 4.15.0-159.167 on Bionic I can no longer mount an overlay filesystem over directories like / in a user namespace. With kernel versions 5.4.0-88.99 and 4.15.0-158.166, respectively, this still works. An easy way to test this is the
[Kernel-packages] [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Thanks!
>> I noticed that in the list of affected packages in the bug metadata
>> Bionic is not mentioned. Will the fix also be backported there?
>
> It depends on which kernel you are talking about. The bionic GA kernel
> (4.15) was not affected based on my testing. If you are seeing problems
> with it, please let me know.
4.15 was not affected indeed.
> The bionic HWE kernel is derived from the kernel source in focal, so
> that kernel does not need to be fixed separately from the focal kernel.
Ok, just wanted to make sure this is the case.
Everything is fine for me now.
--
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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification
[Impact]
The backports to fix CVE-2020-16120 introduced a regression for
overlay mounts within user namespaces. Files with ownership outside of
the user namespace can no longer be accessed, even if allowed by both
DAC and MAC.
This issue is fixed by the following upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b6650dab404c701d7fe08a108b746542a934da84
This commit relaxes the check to remove O_NOATIME from the open flags
for the file in the lower filesystem when the overlay filesystem
mounter is not privileged with respect to the underlying inode, rather
than failing the open as happens now.
[Test Case]
The attached lp1900141.sh script reproduces the issue.
[Where problems could occur]
For the most part this patch restores previous behavior of allowing
access to these files while keeping the enhanced permission checks
towards the lower filesystem to help prevent unauthorized access to
file data in the lower filesystem. The one difference in behavior is
that files in the lower filesystem may no longer be opened with the
O_NOATIME flag, potentially causing atime updates for these files
which were not happening before. If any software expects O_NOATIME
behavior in this situation then it could cause problems for that
software. However, the correct behavior is that only the inode owner
or a process with CAP_FOWNER towards the inode owner is allowed to
open with O_NOATIME (as documented in open(2)).
---
We use unprivileged user namespaces with overlay mounts for
containers. After recently upgrading our Focal kernels to 5.4.0-51.56
this breaks, one cannot access files through the overlay mount in the
container anymore. This is very likely caused by some of the patches
that were added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay
of /usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52
but is broken on kernel 5.4.0-51.56, no matter whether on Bionic or
Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches
that according to the changelogs were applied in the same revision but
only to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name
[Kernel-packages] [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Thanks!
I tested it on a Focal machine and the -proposed kernel works. However,
I don't have a Groovy machine here, is it necessary for me to test this?
I noticed that in the list of affected packages in the bug metadata
Bionic is not mentioned. Will the fix also be backported there?
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Committed
Bug description:
SRU Justification
[Impact]
The backports to fix CVE-2020-16120 introduced a regression for
overlay mounts within user namespaces. Files with ownership outside of
the user namespace can no longer be accessed, even if allowed by both
DAC and MAC.
This issue is fixed by the following upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b6650dab404c701d7fe08a108b746542a934da84
This commit relaxes the check to remove O_NOATIME from the open flags
for the file in the lower filesystem when the overlay filesystem
mounter is not privileged with respect to the underlying inode, rather
than failing the open as happens now.
[Test Case]
The attached lp1900141.sh script reproduces the issue.
[Where problems could occur]
For the most part this patch restores previous behavior of allowing
access to these files while keeping the enhanced permission checks
towards the lower filesystem to help prevent unauthorized access to
file data in the lower filesystem. The one difference in behavior is
that files in the lower filesystem may no longer be opened with the
O_NOATIME flag, potentially causing atime updates for these files
which were not happening before. If any software expects O_NOATIME
behavior in this situation then it could cause problems for that
software. However, the correct behavior is that only the inode owner
or a process with CAP_FOWNER towards the inode owner is allowed to
open with O_NOATIME (as documented in open(2)).
---
We use unprivileged user namespaces with overlay mounts for
containers. After recently upgrading our Focal kernels to 5.4.0-51.56
this breaks, one cannot access files through the overlay mount in the
container anymore. This is very likely caused by some of the patches
that were added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay
of /usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52
but is broken on kernel 5.4.0-51.56, no matter whether on Bionic or
Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches
that according to the changelogs were applied in the same revision but
only to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
AplayDevices:
[Kernel-packages] [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
I noticed that the changelog of the kernel package 5.4.0-50.55~18.04.1
for Bionic now also includes the two additional patches, and indeed I
can confirm that on Bionic with kernel 5.4.0-54-generic the regression
was now also introduced.
Is there an update whether it will be possible to solve this regression?
It breaks our container runtime unfortunately.
--
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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
Status in linux package in Ubuntu:
In Progress
Bug description:
We use unprivileged user namespaces with overlay mounts for
containers. After recently upgrading our Focal kernels to 5.4.0-51.56
this breaks, one cannot access files through the overlay mount in the
container anymore. This is very likely caused by some of the patches
that were added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay
of /usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52
but is broken on kernel 5.4.0-51.56, no matter whether on Bionic or
Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches
that according to the changelogs were applied in the same revision but
only to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
Date: Fri Oct 16 13:02:32 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic
root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.4.0-51-generic N/A
linux-backports-modules-5.4.0-51-generic N/A
linux-firmware1.187.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org
dmi.chassis.type: 1
[Kernel-packages] [Bug 1894334] Re: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel
Updated my BIOS to V2.13 It didn't resolve this bug. I'm still stuck on Kernel 5.4.0-42 If you need additional Information, please get in touch with me. Because I don't know what you need or how to gather that info. -- 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/1894334 Title: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel Status in linux package in Ubuntu: Confirmed Bug description: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-28T17:00:58.663417 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894334/+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 1900141] [NEW] overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
Public bug reported:
We use unprivileged user namespaces with overlay mounts for containers.
After recently upgrading our Focal kernels to 5.4.0-51.56 this breaks,
one cannot access files through the overlay mount in the container
anymore. This is very likely caused by some of the patches that were
added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay of
/usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52 but
is broken on kernel 5.4.0-51.56, no matter whether on Bionic or Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches that
according to the changelogs were applied in the same revision but only
to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
Date: Fri Oct 16 13:02:32 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic
root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.4.0-51-generic N/A
linux-backports-modules-5.4.0-51-generic N/A
linux-firmware1.187.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-5.0
dmi.modalias:
dmi:bvnSeaBIOS:bvrrel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-5.0:cvnQEMU:ct1:cvrpc-i440fx-5.0:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-5.0
dmi.sys.vendor: QEMU
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug focal
--
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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
Status in linux package in Ubuntu:
Confirmed
Bug description:
We use unprivileged user namespaces with overlay mounts
[Kernel-packages] [Bug 1894334] [NEW] GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel
Public bug reported: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.5:bd08/31/2012:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-01-28T17:00:58.663417 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- 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/1894334 Title: GK104 [Geforce GTX 760 GTK] won't work for me with latest Kernel Status in linux package in Ubuntu: Confirmed Bug description: When migrating from the Kernel 5.4.0-42-lowlatency to 5.4.0-45-lowlatency my Graphic card stopped working properly. My second Monitor went dark. even little things like moving the mouse was just a slide show. When using Grub to load with the previus Kernel (5.4.0-42-lowlatency) my Graphics card worked just fine again. My Bios version is "heavily outdated" as I was told. I'll try to update it to V2.13 soon, maybe that helps run newer Kernel in the future. My Hardware: Mainboard: Z77A-G43 the command "sudo dmidecode -s bios-version" returned: "V2.5" Graphic card: Geforce GTX 760 GTK Driver package: NVIDIA driver metapackage nvidia-driver-435 UbuntuStudio 20.04.1 LTS Kernel 5.4.0-45-lowlatency PS: Thanks for your awesome Work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Sep 4 20:51:16 2020 InstallationDate: Installed on 2020-01-26 (222 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: MSI MS-7758 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=58aefce8-42fe-4333-81ae-31d2c867846e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-21 (75 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1883239] Re: Kernel modules missing in 5.4.0-37
Same for me. I was also missing linux-generic. That explains it, thank you! -- 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/1883239 Title: Kernel modules missing in 5.4.0-37 Status in linux package in Ubuntu: Invalid Bug description: I recently updated my Ubuntu 20.04 to the latest kernel (5.4.0-37) but upon reboot my Dell XPS lost a few peripherals, like the wifi, and the possibility to use the Dell WD-15 docking station for LAN or external monitors; USB hub functionality was working though. After some inspection, I've found that several kernel modules are missing for that specific kernel version: $ find /usr/lib/modules -iname ath10k /usr/lib/modules/5.4.0-28-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-31-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-33-generic/kernel/drivers/net/wireless/ath/ath10k And lspci shows the wireless card twice (one more time at the top) and that the following modules and drivers are not loaded for the proper devices: - i915 - processor_thermal_device - intel_pch_thermal - intel_lpss_pci - mei_me - snd_hda_intel - nouveau (but not the nvidia, which I'm using) - ath10k_pci - rtsx_pci Restarting with the previous kernel version (5.4.0-33) works without any issue. I'll attach both lspci outputs, but you can easily review the diff here: https://www.diffchecker.com/mVCbTzSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+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 1883239] Re: Kernel modules missing in 5.4.0-37
I believe I was hit by the same bug. I'm using Ubuntu 20.04 on a ThinkPad X1 Carbon 4th. Manually installing the missing linux-modules- extra for 5.4.0-37 brings networking back, but I still had problems getting the system to detect external monitors. That is why I stay on 5.4.0-33 for the moment. However, even on 5.4.0-33, the detection of external monitors sometimes fails. That means that aspect could be a false alarm (on my system). What I can confirm is that for me networking is definitely broken because of the missing linux-modules-extra, which were automatically installed for 5.4.0.33 but were missing in 5.4.0.37. After manually installing the package, networking works as before. -- 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/1883239 Title: Kernel modules missing in 5.4.0-37 Status in linux package in Ubuntu: Confirmed Bug description: I recently updated my Ubuntu 20.04 to the latest kernel (5.4.0-37) but upon reboot my Dell XPS lost a few peripherals, like the wifi, and the possibility to use the Dell WD-15 docking station for LAN or external monitors; USB hub functionality was working though. After some inspection, I've found that several kernel modules are missing for that specific kernel version: $ find /usr/lib/modules -iname ath10k /usr/lib/modules/5.4.0-28-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-31-generic/kernel/drivers/net/wireless/ath/ath10k /usr/lib/modules/5.4.0-33-generic/kernel/drivers/net/wireless/ath/ath10k And lspci shows the wireless card twice (one more time at the top) and that the following modules and drivers are not loaded for the proper devices: - i915 - processor_thermal_device - intel_pch_thermal - intel_lpss_pci - mei_me - snd_hda_intel - nouveau (but not the nvidia, which I'm using) - ath10k_pci - rtsx_pci Restarting with the previous kernel version (5.4.0-33) works without any issue. I'll attach both lspci outputs, but you can easily review the diff here: https://www.diffchecker.com/mVCbTzSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883239/+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 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
** Description changed: - I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: + I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272G5DYEB. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 -- 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/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I just checked back with my Nvidia machine and instead of "amdgpu" it saying that "modeset" is doing the EDID'ing (both with open source and proprietary driver) and no 1080p 144 Hz: [18.782] (II) modeset(G0): EDID for output DP-1-1 [18.782] (II) modeset(G0): Printing probed modes for output DP-1-1 [18.782] (II) modeset(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [18.782] (II) modeset(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [18.782] (II) modeset(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [18.782] (II) modeset(G0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e) [18.782] (II) modeset(G0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Where do I have to file the bug report in this case? I saw that there is a thing called modesetting that is part of the kernel. Do I have to file a report for the kernel? -- 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/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272G5DYEB. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
The drm-tip kernel didn't help the case. Did I understand this correctly that you have identified the driver to be the problem? If so I have to delegate this two 3 different drivers with which I have this problem: the already linked amd driver, but also the proprietary and open source nvidia drivers that I both tested with unsuccessfully. Can you point me to the right places here? -- 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/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
Doesn't seem to be that there is much EDID communication going on. ** Attachment added: "sys-edid.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1879402/+attachment/5374122/+files/sys-edid.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/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I just went into Windows using a cmd-tool called DumbEDID which gave me information I upload here (note that there are two monitors present and the MSI is working fine in Ubuntu, I'm referring to the philips at the bottom of the log). There is some information that is actually transported like the native resolution, physical size, monitor model and some frequencies. I'm wondering if I can use this information now to create a modeline in Ubuntu. ** Attachment added: "The information for the concerning monitor is at the bottom. The top shows information about another monitor that is working fine." https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1879402/+attachment/5373993/+files/edid.txt -- 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/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel:
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I tried 3 different Displayport cables without success. In Ubuntu get- edid tells me that there is no EDID information provided. As the monitor is working properly in Windows I think that Windows is just doing a better job at coming up with a 1080p modeline on its own. So in my mind the thing to do now is trying out different modelines until one with the proper resolution is actually working but I have no idea how to come up with more modelines other than using cvt 1920 1080. -- 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/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log
[Kernel-packages] [Bug 172937] Re: SQUASHFS error while booting from live cd
Update regarding my previous comment:
After resetting the VM (in the Hyper-V connection -> "Action" ->
"Reset") the VM rebooted, showed the login screen for the first time and
I could login. But right after the login the screen was stuck again -
there was no menu bar with the program launch icons on the left (a.k.a.
"dock"), the bar on the top was empty except for the three indicators in
the top right corner (network, sound, power), right click on the
background didn't do anything and there was just the time being
displayed in the center. Nothing happened for at least 15 minutes.
Then after resetting *again* and logging in a second time, finally the
typical welcome screen of Ubuntu appeared ("What's new in Ubuntu", the
program launch bar on the left etc.) and I could properly use the
system.
--
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/172937
Title:
SQUASHFS error while booting from live cd
Status in linux package in Ubuntu:
Won't Fix
Status in linux package in Fedora:
Won't Fix
Status in linux package in Mandriva:
Invalid
Bug description:
Some users have reported being unable to boot from the Ubuntu LiveCD,
due to SquasFS errors like this:
[ 135.292409] SQUASHFS error: sb_bread failed reading block 0x9d7f3
[ 135.292411] SQUASHFS error: Unable to read fragment cache block [275faa28]
[ 135.292413] SQUASHFS error: Unable to read page, block 275faa28, size 23a7
These errors can be due to a variety of reasons:
* bad media (solution: try burning the iso image to a new disc)
* a bad dvd drive (solution: if possible, try using a different cd/dvd
drive)
* bad memory modules (solution: use memtest86+ to check your memory)
* a corrupted iso image (solution: run an md5 checksum, and if they don't
match, download the iso image again)
* an optical drive connected via SATA instead of PATA and running in
Enhanced mode (solution: change the IDE configuration to "compatible" in the
BIOS)
This is all described in more detail here:
https://help.ubuntu.com/community/SquashfsErrors
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+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 172937] Re: SQUASHFS error while booting from live cd
I just installed Ubuntu 18.04 in a new Hyper-V VM (host is Windows 10 Pro). Fresh virtual disk (25 GB), 2 virtual CPUs, 4 GB RAM. I used the ISO file to boot and install. The installation went fine until the forced reboot at the end of the installation. After the reboot a lot of these "SQUASHFS error: ..." messages appear: - SQUASHFS error: Unable to read metadata cache entry [...] - SQUASHFS error: read_indexes: reading block [...:...] And at the end the screen is stuck as can be seen in the attached screenshot. ** Attachment added: "2020-01-15 ubuntu vm.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+attachment/5320576/+files/2020-01-15%20ubuntu%20vm.png -- 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/172937 Title: SQUASHFS error while booting from live cd Status in linux package in Ubuntu: Won't Fix Status in linux package in Fedora: Won't Fix Status in linux package in Mandriva: Invalid Bug description: Some users have reported being unable to boot from the Ubuntu LiveCD, due to SquasFS errors like this: [ 135.292409] SQUASHFS error: sb_bread failed reading block 0x9d7f3 [ 135.292411] SQUASHFS error: Unable to read fragment cache block [275faa28] [ 135.292413] SQUASHFS error: Unable to read page, block 275faa28, size 23a7 These errors can be due to a variety of reasons: * bad media (solution: try burning the iso image to a new disc) * a bad dvd drive (solution: if possible, try using a different cd/dvd drive) * bad memory modules (solution: use memtest86+ to check your memory) * a corrupted iso image (solution: run an md5 checksum, and if they don't match, download the iso image again) * an optical drive connected via SATA instead of PATA and running in Enhanced mode (solution: change the IDE configuration to "compatible" in the BIOS) This is all described in more detail here: https://help.ubuntu.com/community/SquashfsErrors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+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 1811226] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228266/+files/UdevDb.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228267/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228265/+files/ProcModules.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228260/+files/CurrentDmesg.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228261/+files/Lspci.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228262/+files/ProcCpuinfoMinimal.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] Re: ipvsadm --ops causes CPU soft lockup on traffic
apport information ** Tags added: apport-collected bionic ** Description changed: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel- ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jan 10 11:37 seq + crw-rw 1 root audio 116, 33 Jan 10 11:37 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 18.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + PciMultimedia: + + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro + ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.2 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' + Tags: bionic + Uname: Linux 4.15.0-43-generic x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-2.12 + dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-2.12 + dmi.sys.vendor: QEMU ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228259/+files/CRDA.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001
[Kernel-packages] [Bug 1811226] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228264/+files/ProcInterrupts.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1811226/+attachment/5228263/+files/ProcEnviron.txt -- 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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: Confirmed Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 11:37 seq crw-rw 1 root audio 116, 33 Jan 10 11:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=27723a0b-84b7-4d41-ac73-d96bb9bc770a ro ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.12 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.12 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1811226] [NEW] ipvsadm --ops causes CPU soft lockup on traffic
Public bug reported: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel- ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1811226/+attachment/5228243/+files/version.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/1811226 Title: ipvsadm --ops causes CPU soft lockup on traffic Status in linux package in Ubuntu: New Bug description: Using IPVS with One-Packet Scheduling on UDP causes CPU soft lockup on traffic. Steps to reproduce: 1. Install ipvsadm and netcat-openbsd 2. Execute `ipvsadm -a -u 127.0.0.1:1234 -s rr --ops && ipvsadm -A -u 127.0.0.1:1234 -r 127.0.0.1:1235 -m -w 1` 3. Execute `nc -l -k -u 1235` to actually have a listening service 4. In another terminal, generate traffic `while sleep 0.01; do date | nc -u -w 0 127.0.0.1 1234; done` In only takes several packets (around 100 in my tests) to cause the soft lockup to appear. Even with lower packet rates (sleep 1 for example), the bug occurs. This problem is already fixed in the current 4.20 vanilla kernel but is present in the 4.15 vanilla kernel (tested packages from the kernel-ppa). So basically, this would be a backport. Ubuntu release: Ubuntu 18.04.1 LTS Kernel version: Ubuntu 4.15.0-43.46-generic 4.15.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811226/+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 1793458] Re: Overlayfs in user namespace leaks directory content of inaccessible directories
Tyler, thanks for the clarification. I have tested it with 4.15.0-42-generic from bionic-proposed and can confirm it is fixed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1793458 Title: Overlayfs in user namespace leaks directory content of inaccessible directories Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: Summary: With a combination of overlayfs and user namespaces, regular users can see the content of directories that would otherwise be inaccessible to them because of directory permissions (e.g., all users can see content of "/root"). Details: For the exploit it is necessary to create user and mount namespaces and mount an overlayfs inside it. Ubuntu allows this for regular users. The lower dir of the overlay would be "/", and the upper dir an attacker-controlled temporary directory. If the attacker wants to see the content of "/root", they would create a directory "root" in the upper dir of the overlay. Overlays seems to get confused about the permissions, and instead of applying the restrictive permissions of "root" from the lower dir, it applies more relaxed restrictions of "root" from the upper dir, granting the attacker the possibility to list the directory contents of "/root". To reproduce, simply run the attached script as regular user. It will show the content of "/root", on my system the output is this: ``` /bin/ls: cannot access '/root/.cache': Permission denied /bin/ls: cannot access '/root/.bashrc': Permission denied /bin/ls: cannot access '/root/snap': Permission denied /bin/ls: cannot access '/root/.gnupg': Permission denied /bin/ls: cannot access '/root/.aptitude': Permission denied /bin/ls: cannot access '/root/.bash_history': Permission denied /bin/ls: cannot access '/root/.profile': Permission denied /bin/ls: cannot access '/root/.hplip': Permission denied total 8 drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 . drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 .. d? ? ? ? ?? .aptitude -? ? ? ? ?? .bash_history -? ? ? ? ?? .bashrc d? ? ? ? ?? .cache d? ? ? ? ?? .gnupg d? ? ? ? ?? .hplip -? ? ? ? ?? .profile d? ? ? ? ?? snap ``` The script also has some comments that explain the necessary steps in more details. I tested on Ubuntu 18.04 with Linux 4.15.0-34-generic, but the bug probably affects all Ubuntu versions of the last years. Other distributions and the vanilla kernel should not be affected because AFAIK only Ubuntu allows mounting of overlayfs inside user namespaces. But of course it would be good to apply a potential fix upstream. So far I did not succeed in doing more than leaking the directory content, but of course that is no guarantee that it is not possible to do worse things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wendler3414 F pulseaudio /dev/snd/controlC0: wendler3414 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Sep 20 08:56:01 2018 HibernationDevice: RESUME=UUID=f9d1a1f9-50d2-4b7c-b7e4-66dc78d38062 InstallationDate: Installed on 2016-12-12 (646 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FXS1B700 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=/dev/mapper/ubuntu--vg-swap_1 swapaccount=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-04 (15 days ago) dmi.bios.date: 09/26/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET71W (2.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS1B700 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:
[Kernel-packages] [Bug 1793458] Re: Overlayfs in user namespace leaks directory content of inaccessible directories
I find the demand to test the fix within 5 days, combined with the threat of dropping the patch otherwise, unreasonable. In my original report of this security problem I have already provided a script that allows to reproduce the problem and check if it still exists. Requiring an answer within 5 days is too short, after all people can be on holiday or just busy for other reasons. And even if I as the original submitter wouldn't respond at all, this is a real security problem in Ubuntu that was already confirmed. Are you really going to drop the patch and let CVE-2018-6559 stay unfixed forever? Maybe I will find the time to test it on Bionic, but I will certainly not install a different version of Ubuntu than the one I am currently running. I hope that this is all just a misunderstanding and the message does not apply to security problems. In this case please consider changing the message or improving the process such that this confusion will be avoided for future reports. -- 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/1793458 Title: Overlayfs in user namespace leaks directory content of inaccessible directories Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: Summary: With a combination of overlayfs and user namespaces, regular users can see the content of directories that would otherwise be inaccessible to them because of directory permissions (e.g., all users can see content of "/root"). Details: For the exploit it is necessary to create user and mount namespaces and mount an overlayfs inside it. Ubuntu allows this for regular users. The lower dir of the overlay would be "/", and the upper dir an attacker-controlled temporary directory. If the attacker wants to see the content of "/root", they would create a directory "root" in the upper dir of the overlay. Overlays seems to get confused about the permissions, and instead of applying the restrictive permissions of "root" from the lower dir, it applies more relaxed restrictions of "root" from the upper dir, granting the attacker the possibility to list the directory contents of "/root". To reproduce, simply run the attached script as regular user. It will show the content of "/root", on my system the output is this: ``` /bin/ls: cannot access '/root/.cache': Permission denied /bin/ls: cannot access '/root/.bashrc': Permission denied /bin/ls: cannot access '/root/snap': Permission denied /bin/ls: cannot access '/root/.gnupg': Permission denied /bin/ls: cannot access '/root/.aptitude': Permission denied /bin/ls: cannot access '/root/.bash_history': Permission denied /bin/ls: cannot access '/root/.profile': Permission denied /bin/ls: cannot access '/root/.hplip': Permission denied total 8 drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 . drwxr-xr-x 1 nobody nogroup 4096 Sep 20 09:02 .. d? ? ? ? ?? .aptitude -? ? ? ? ?? .bash_history -? ? ? ? ?? .bashrc d? ? ? ? ?? .cache d? ? ? ? ?? .gnupg d? ? ? ? ?? .hplip -? ? ? ? ?? .profile d? ? ? ? ?? snap ``` The script also has some comments that explain the necessary steps in more details. I tested on Ubuntu 18.04 with Linux 4.15.0-34-generic, but the bug probably affects all Ubuntu versions of the last years. Other distributions and the vanilla kernel should not be affected because AFAIK only Ubuntu allows mounting of overlayfs inside user namespaces. But of course it would be good to apply a potential fix upstream. So far I did not succeed in doing more than leaking the directory content, but of course that is no guarantee that it is not possible to do worse things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wendler3414 F pulseaudio /dev/snd/controlC0: wendler3414 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Sep 20 08:56:01 2018 HibernationDevice: RESUME=UUID=f9d1a1f9-50d2-4b7c-b7e4-66dc78d38062 InstallationDate: Installed on 2016-12-12 (646 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FXS1B700 ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
I did post the issue to the mailing list but did not receive any answer for the past 14 days. I know that other users are affected too, for example at reddit. This is really bad, because it essentially means that this laptop can not be used with linux at all without external mouse. -- 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
Also did depmod -a update-initramfs -u and verified with lsmod | grep i2c that i2c_hid is not loaded. still elan_i2c kernel errors in syslog. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
modprobe -r elan_i2c disables the touchpad. modprobe -r i2c_hid doesn't seem to have any effect. echo "blacklist i2c_hid" | sudo tee -a /etc/modprobe.d/blacklist.conf doesn't seem to have any effect either. -- 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
Thanks for your reply. This is a new laptop, so I am not able to say anything about prior kernel versions. With upstream kernel v4.19 the issue persists. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
modprobe -r elan_i2c modprobe elan_i2c is a workaround. But Touchpad still freezes after some time. -- 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
After some time the Touchpad now stops working and is not usable. External Mouse works fine. -- 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1793960] [NEW] Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
Public bug reported: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic elan -- 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/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog Status in linux package in Ubuntu: Confirmed Bug description: The trackpad is working, but syslog is full of kernel errors regarding "kernel: [ 1228.364151] elan_i2c i2c-ELAN0609:00: invalid report id data (ff)" if the trackpad is touched. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mlku 1269 F pulseaudio CurrentDesktop: KDE Date: Sun Sep 23 15:48:36 2018 HibernationDevice: RESUME=UUID=83c21341-9f8a-4b04-8696-ba03f48c8561 InstallationDate: Installed on 2018-09-23 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80XR ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5RCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IAP dmi.modalias: dmi:bvnLENOVO:bvr5RCN36WW:bd08/06/2018:svnLENOVO:pn80XR:pvrLenovoideapad320-15IAP:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IAP: dmi.product.family: ideapad 320-15IAP dmi.product.name: 80XR dmi.product.version: Lenovo ideapad 320-15IAP dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+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 1788786] [NEW] installation of nvidia-396 fails due to "trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nv
Public bug reported: Installation of `nvidia-396` after `sudo add-apt-repository ppa :graphics-drivers/ppa` on Ubuntu 18.04 fails due to ``` > sudo apt-get install -f nvidia-driver-396 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 libnvidia-fbc1-396:i386 libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime nvidia-settings nvidia-utils-396 screen-resolution-extra xserver-xorg-video-nvidia-396 The following packages will be REMOVED: libnvidia-cfg1-390 libnvidia-compute-390 libnvidia-compute-390:i386 xserver-xorg-video-nvidia-390 The following NEW packages will be installed: libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 libnvidia-fbc1-396:i386 libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 nvidia-driver-396 nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime nvidia-settings nvidia-utils-396 screen-resolution-extra xserver-xorg-video-nvidia-396 0 upgraded, 25 newly installed, 4 to remove and 1 not upgraded. Need to get 0 B/88,1 MB of archives. After this operation, 224 MB of additional disk space will be used. Do you want to continue? [J/n] j (Reading database ... 748099 files and directories currently installed.) Preparing to unpack .../xserver-xorg-video-nvidia-396_396.54-0ubuntu0~gpu18.04.1_amd64.deb ... Unpacking xserver-xorg-video-nvidia-396 (396.54-0ubuntu0~gpu18.04.1) ... dpkg: error processing archive /var/cache/apt/archives/xserver-xorg-video-nvidia-396_396.54-0ubuntu0~gpu18.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-video-nvidia-390 390.48-0ubuntu3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/xserver-xorg-video-nvidia-396_396.54-0ubuntu0~gpu18.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` ** Affects: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided Status: New ** Description changed: Installation of `nvidia-396` after `sudo add-apt-repository ppa - :graphics-drivers/ppa` fails due to + :graphics-drivers/ppa` on Ubuntu 18.04 fails due to ``` > sudo apt-get install -f nvidia-driver-396 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following additional packages will be installed: - libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 libnvidia-fbc1-396:i386 - libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime nvidia-settings - nvidia-utils-396 screen-resolution-extra xserver-xorg-video-nvidia-396 + libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 libnvidia-fbc1-396:i386 + libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime nvidia-settings + nvidia-utils-396 screen-resolution-extra xserver-xorg-video-nvidia-396 The following packages will be REMOVED: - libnvidia-cfg1-390 libnvidia-compute-390 libnvidia-compute-390:i386 xserver-xorg-video-nvidia-390 + libnvidia-cfg1-390 libnvidia-compute-390 libnvidia-compute-390:i386 xserver-xorg-video-nvidia-390 The following NEW packages will be installed: - libnvidia-cfg1-396 libnvidia-common-396 libnvidia-compute-396 libnvidia-compute-396:i386 libnvidia-decode-396 libnvidia-decode-396:i386 libnvidia-encode-396 libnvidia-encode-396:i386 libnvidia-fbc1-396 libnvidia-fbc1-396:i386 - libnvidia-gl-396 libnvidia-gl-396:i386 libnvidia-ifr1-396 libnvidia-ifr1-396:i386 libxnvctrl0 nvidia-compute-utils-396 nvidia-dkms-396 nvidia-driver-396 nvidia-kernel-common-396 nvidia-kernel-source-396 nvidia-prime - nvidia-settings nvidia-utils-396 screen-resolution-extra xserver-xorg-video-nvidia-396 +
[Kernel-packages] [Bug 1740462] [NEW] Deletion of subvolumes by docker system prune causes btrfs to become unusable/unmountable because of skinny extends
Public bug reported: `docker system prune` caused a few processes to hang a few minutes while I could still capture ``` [ 85.821088] [ cut here ] [ 85.821108] WARNING: CPU: 6 PID: 75 at /build/linux-8h04gD/linux-4.13.0/fs/btrfs/extent-tree.c:3009 btrfs_run_delayed_refs+0x244/0x250 [btrfs] [ 85.821109] Modules linked in: rfcomm msr nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore iptable_filter cdc_ether usbnet pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) bnep r8152 vboxdrv(OE) bbswitch(OE) binfmt_misc btusb btrtl btbcm btintel rtsx_usb_ms memstick bluetooth ecdh_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev [ 85.821133] media hid_multitouch zfs(POE) zunicode(POE) zavl(POE) icp(POE) nls_iso8859_1 zcommon(POE) znvpair(POE) spl(OE) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate input_leds intel_rapl_perf joydev serio_raw ideapad_laptop sparse_keymap arc4 wmi iwldvm mac80211 iwlwifi mac_hid cfg80211 lpc_ich mei_me mei shpchp sunrpc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi coda parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid psmouse i915 video r8169 i2c_algo_bit mii drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops [ 85.821163] libahci drm [ 85.821165] CPU: 6 PID: 75 Comm: kworker/u16:1 Tainted: P OE 4.13.0-21-generic #24-Ubuntu [ 85.821166] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21) 07/12/2013 [ 85.821181] Workqueue: btrfs-extent-refs btrfs_extent_refs_helper [btrfs] [ 85.821182] task: 9a5c6c6b8000 task.stack: a8f681b58000 [ 85.821192] RIP: 0010:btrfs_run_delayed_refs+0x244/0x250 [btrfs] [ 85.821193] RSP: 0018:a8f681b5bd80 EFLAGS: 00010282 [ 85.821194] RAX: 0026 RBX: ffef RCX: [ 85.821194] RDX: RSI: 9a5c7f38dc78 RDI: 9a5c7f38dc78 [ 85.821195] RBP: a8f681b5bdd8 R08: 0001 R09: 042f [ 85.821196] R10: a8f681b5bc70 R11: R12: 9a5c6b3c5438 [ 85.821196] R13: 9a5c5fc3 R14: 9a5b85529a00 R15: 028f [ 85.821197] FS: () GS:9a5c7f38() knlGS: [ 85.821198] CS: 0010 DS: ES: CR0: 80050033 [ 85.821199] CR2: 5643c2753020 CR3: 0002e8e09000 CR4: 001406e0 [ 85.821200] Call Trace: [ 85.821211] delayed_ref_async_start+0x98/0xb0 [btrfs] [ 85.821224] btrfs_worker_helper+0x7a/0x2e0 [btrfs] [ 85.821235] btrfs_extent_refs_helper+0xe/0x10 [btrfs] [ 85.821239] process_one_work+0x1e7/0x410 [ 85.821241] worker_thread+0x4b/0x420 [ 85.821242] kthread+0x125/0x140 [ 85.821244] ? process_one_work+0x410/0x410 [ 85.821245] ? kthread_create_on_node+0x70/0x70 [ 85.821248] ret_from_fork+0x25/0x30 [ 85.821249] Code: fe ff 89 d9 ba c1 0b 00 00 48 c7 c6 60 28 7d c0 4c 89 e7 e8 e5 a2 09 00 e9 b5 fe ff ff 89 de 48 c7 c7 98 93 7d c0 e8 8d 02 7b ec <0f> ff eb d3 e8 60 a4 09 00 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 [ 85.821268] ---[ end trace 9bddba90bd2dbd28 ]--- [ 85.821271] BTRFS: error (device sda5) in btrfs_run_delayed_refs:3009: errno=-17 Object already exists [ 85.821274] BTRFS info (device sda5): forced readonly ``` from `dmesg`. After a forced restart with the power button, I could reproduce the issue (and had to restart with the power button every time), so that finally the filesystem because unmountable because of skinny extents (couldn't capture the stack for the unmountable state). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/pcmC0D0p: richter 19894 F...m pulseaudio /dev/snd/controlC0: richter 19894 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Dec 29 06:51:06 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (747 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release
[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes
Good to know, thank you for your support. The issue is fixed in 4.13.0-16-generic of Ubuntu 17.10 as stated in #16. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
91d57bae08689199c8acc77a8b3b41150cafab1c is good. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
525b8ed91671e29e187dfe02d408b11190ccf494 is good (assuming that the kernel image package with the later timestamp is the one representing the commit). -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
e7561f1633ac735df48c55ad09a2530e9ab9fab1 is good. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
2a55e98f9f76825d78a4e6ef315c35fccabf5212 is good. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
63841b2a6969501de183efafc14d20175e402804 is bad. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
2fcc112af37fa88f8da077d6dd3bb8e38e75adb1 is good. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
e0f3e8f14da868047c524a0cf11e08b95fd1b008 is bad. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
9bc088ab66be8978fbc981ba9644468fa2c2fd3f is bad. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
e7bd9ba20a9ec7024a0566a93c22b9571a48939a is bad. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
892ad5acca0b2ddb514fae63fa4686bf726d2471 is bad. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
1b044f1cfc65a7d90b209dfabd57e16d98b58c5b is good. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
cbcd4f08aa637b74f575268770da86a00fabde6d is good. Thanks for the kernels. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
The issue is fixed with the first 17.10 kernel 4.13.0-16-generic as expected. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
1849f800fba32cd5a0b647f824f11426b85310d8 is good, i.e. doesn't have the bug. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
> The only .deb package you need to install is: linux-image-4.12.0-041200-generic_4.12.0-041200.201710171537_amd64.deb Didn't know that, thank you. This version is good. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
> The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1721856 The _all package seems to be damaged/truncated. I'm getting `dpkg-deb: error: unexpected end of file in archive member header in linux- headers-4.12.0-041200_4.12.0-041200.201710171537_all.deb` and the package seems unusual small. > If you want to give the bisect a try, you can do that. I can assist with questions. Otherwise, I started a "Reverse" kernel bisect between v4.12 final and v4.13-rc1. The kernel bisect will require testing of about 10-13 test kernels. I'd be really happy if you can do the bisecting and building kernels for me to test. So, you'll build one kernel and then wait for me to report and then eventually build the next? -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
v4.13-rc1 is good. Please tell me if you need support for this issue from me. I'd like to take this opportunity to recommend you to improve instructions for bisecting with the mainline kernel releases and release candidates for reports like me. I'm not a Linux hacker, but I understand the principle of bisecting which is why I indicated to be ready to do bisecting work in the description. You could have directed me to a wiki article or else describing bisecting pre-work with kernel releases before bisecting commits, so that I'd have known that all sub-version including the release candidates are included into into this process. Also, if I didn't know what bisecting was, I might have tried all kernel versions instead of doing a binary search which would have most certainly caused unnecessary work. Thanks for your support and contributions so far. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
> We can perform a reverse bisect to identify the commit that fixes this bug. > We first need to identify the last bad kernel and first good one. Can you > test the following two kernels: > > v4.11: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11 > v4.12: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12 I tested: 4.10.17 bad 4.12.0 bad 4.12.14 bad 4.13.1 good 4.13.3 good 4.13.5 good Please instruct for the further bisection process. Thanks for your support so far. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: Triaged Status in linux source package in Zesty: Triaged Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
> Can you see if this bug is fixed in upstream 4.13 or 4.10, which will tell us if the fix was already cc'd to stable. Fixed in 4.13.5 and present in 4.10.17. -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: Triaged Status in linux source package in Zesty: Triaged Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1721856] Re: Suspend ends after seconds and laptop resumes
** Summary changed: - standby ends after seconds and laptop resumes + Suspend ends after seconds and laptop resumes ** Description changed: - The standby ends after seconds and the laptop resumes like it'd wake up - from standby. I didn't use standby for a long time (months or years) and - can't even estimate when it worked for the last time. + The suspend/standby ends after seconds and the laptop resumes like it'd + wake up from suspend. I didn't use suspend for a long time (months or + years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO -- 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: Triaged Status in linux source package in Zesty: Triaged Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias:
[Kernel-packages] [Bug 1721856] [NEW] standby ends after seconds and laptop resumes
Public bug reported: The standby ends after seconds and the laptop resumes like it'd wake up from standby. I didn't use standby for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Description changed: The standby ends after seconds and the laptop resumes like it'd wake up from standby. I didn't use standby for a long time (months or years) and can't even estimate when it worked for the last time. - This issue is fixed in 4.14-rc3 mainline kernel! I'm willing to do git - bisect work if you confirm me that this makes sense. + This issue is fixed in 4.14-rc3 mainline kernel - although some parts of + the installation don't work, like ZFS and nvidia-340 which might cause + the problem as well. + + I'm willing to do git bisect work if you confirm me that this makes + sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: - BEN.PID ZUGR. BEFEHL - /dev/snd/controlC0: richter 18896 F pulseaudio + BEN.PID ZUGR. BEFEHL + /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: - linux-restricted-modules-4.10.0-35-generic N/A - linux-backports-modules-4.10.0-35-generic N/A - linux-firmware 1.164.1 + linux-restricted-modules-4.10.0-35-generic N/A + linux-backports-modules-4.10.0-35-generic N/A + linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO -- You received this
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I managed to solve the issue for my case!! The problem was a nfs share defined in /etc/fstab. It seems it should be unmounted but networking already stopped. So i switched to autofs and successfuly rebooted twice without the problem. Thats how i defined the mount: server:/path/to/nfs-share /media/nfs-share nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90
[Kernel-packages] [Bug 1712765] Re: reboot instead of shutdown
** Description changed: - hallo - i have a acer aspire v5 571g laptop with former windows. after i installed ubuntu the computer refuses to shut down, instead it does a restart. - thanks + I have a Acer Aspire v5 571g laptop which initially had Windows + installed. After I installed Ubuntu (and overwrote Windows) the computer + shuts down when a restart is requested. Windows did not exhibit this + problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC0D0p: felix 1929 F...m pulseaudio - /dev/snd/controlC0: felix 1929 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: felix 1929 F...m pulseaudio + /dev/snd/controlC0: felix 1929 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Aug 24 10:24:56 2017 HibernationDevice: RESUME=UUID=9aa9aa29-eb16-473f-b28d-5d6c340eac81 InstallationDate: Installed on 2017-06-14 (70 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Acer Aspire V5-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.10.0-32-generic N/A - linux-backports-modules-4.10.0-32-generic N/A - linux-firmware 1.164.1 + linux-restricted-modules-4.10.0-32-generic N/A + linux-backports-modules-4.10.0-32-generic N/A + linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.12:bd06/12/2012:svnAcer:pnAspireV5-571G:pvrV1.12:rvnAcer:rnAspireV5-571G:rvrV1.12:cvnAcer:ct9:cvrV1.12: dmi.product.name: Aspire V5-571G dmi.product.version: V1.12 dmi.sys.vendor: Acer -- 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/1712765 Title: reboot instead of shutdown Status in linux package in Ubuntu: Confirmed Bug description: I have a Acer Aspire v5 571g laptop which initially had Windows installed. After I installed Ubuntu (and overwrote Windows) the computer shuts down when a restart is requested. Windows did not exhibit this problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: felix 1929 F...m pulseaudio /dev/snd/controlC0: felix 1929 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Aug 24 10:24:56 2017 HibernationDevice: RESUME=UUID=9aa9aa29-eb16-473f-b28d-5d6c340eac81 InstallationDate: Installed on 2017-06-14 (70 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Acer Aspire V5-571G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-32-generic N/A linux-backports-modules-4.10.0-32-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.12:bd06/12/2012:svnAcer:pnAspireV5-571G:pvrV1.12:rvnAcer:rnAspireV5-571G:rvrV1.12:cvnAcer:ct9:cvrV1.12: dmi.product.name: Aspire V5-571G dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1712765/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
After enabling proposed updates, I see 4.10.0-30-generic is available. Does it already contain the fix? -- 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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O4.10.0-15-generic #17-Ubuntu Apr 7 11:20:28 doe kernel: [26003.797175] Hardware name: ASUSTeK COMPUTER INC. UX305CA/UX305CA, BIOS UX305CA.201 09/11/2015 Apr 7 11:20:28 doe kernel: [26003.797206] task: 9bbaa201dc00 task.stack: c25b5ea8c000 Apr 7 11:20:28 doe kernel: [26003.797250] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.797279] RSP: 0018:c25b5ea8f880 EFLAGS: 00010246 Apr 7 11:20:28 doe kernel: [26003.797299] RAX: 9bba689be580 RBX: 0003 RCX: 0003 Apr 7 11:20:28 doe kernel: [26003.797325] RDX: RSI: 9bbae7c0a000 RDI: 9bbba0418000 Apr 7 11:20:28 doe kernel: [26003.797351] RBP: c25b5ea8f8d8 R08: R09: Apr 7 11:20:28 doe kernel: [26003.797378] R10: R11: 0041 R12: 9bbb5f00a000 Apr 7 11:20:28 doe kernel: [26003.797405] R13: 9bbba932bb10 R14: fff97000 R15: 8000 Apr 7 11:20:28 doe kernel: [26003.797440] FS: 7f70bd1df6c0() GS:93c0() knlGS: Apr 7 11:20:28 doe kernel: [26003.797470] CS: 0010 DS: ES: CR0: 80050033 Apr 7 11:20:28 doe kernel: [26003.797497] CR2: 0018 CR3: 00016942 CR4: 003406f0 Apr 7 11:20:28 doe kernel: [26003.797523] Call
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I created a separat issue in the lightdm tracker but could not link it properly, here is the link: https://bugs.launchpad.net/lightdm/+bug/1707574 -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112247] []
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
Today, after making some updates the issue still exists, but the shutdown screen got a little bit more verbose. It tells me "A stop job is running for Light Display Manager" followed by the original error from this issue. If i do the following i can shut down: 1) sudo systemctl stop lightdm.service 2) switch to tty1 (ctrl+alt+f1) 3) sudo poweroff If i type "sudo systemctl stop lightdm.service && sudo poweroff" it wont work The lightdm logs only contain 1 non-debug output: [+33.52s] CRITICAL: session_get_login1_session_id: assertion 'session != NULL' failed The lightdm/x-0.log.1.gz contains some errors too Errors from xkbcomp are not fatal to the X server (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b252dc7c6e] (EE) 1: /usr/lib/xorg/Xorg (0x55b252c15000+0x1b6ff9) [0x55b252dcbff9] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f68dad65000+0x354b0) [0x7f68dad9a4b0] (EE) 3: /usr/lib/xorg/modules/libfb.so (_fbGetWindowPixmap+0xd) [0x7f68d4028bdd] (EE) 4: /usr/lib/xorg/Xorg (0x55b252c15000+0x1353d7) [0x55b252d4a3d7] (EE) 5: /usr/lib/xorg/Xorg (0x55b252c15000+0x1354a5) [0x55b252d4a4a5] (EE) 6: /usr/lib/xorg/Xorg (0x55b252c15000+0x135c12) [0x55b252d4ac12] (EE) 7: /usr/lib/xorg/Xorg (0x55b252c15000+0x1347c3) [0x55b252d497c3] (EE) 8: /usr/lib/xorg/Xorg (0x55b252c15000+0xe4c58) [0x55b252cf9c58] (EE) 9: /usr/lib/xorg/Xorg (0x55b252c15000+0x132b64) [0x55b252d47b64] (EE) 10: /usr/lib/xorg/Xorg (0x55b252c15000+0x57f17) [0x55b252c6cf17] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f68dad85830] (EE) 12: /usr/lib/xorg/Xorg (_start+0x29) [0x55b252c57069] (EE) (EE) Segmentation fault at address 0x10 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) (EE) Both logs contain the following strings (maybe some redirected input?): ^@^@^@^@^@ (this goes on for some time) I hope this is of some help for you -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS:
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I can find the following line in the logs over and over again, could this be connected to the power-off issue i described above? nouveau :01:00.0: Refused to change power state, currently in D3 -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I get those messages every time i shut down, so basically every day. Installed Ubuntu 16.04 on nvme ssd, that i installed into a msi notebook. Integrated intel (i7 7700) + dedicated nvidia graphics (gtx 1050) PLEASE help me, turning off my laptop using the power button feels very unhealthy. Today i tried running lshw to give you some more information about my chipsets, etc. But the consequence was kind of a system freeze. Could not kill any processes anymore and one cpu core was at 100% - though htop did not tell me any process with 100% cpu load. Also networking and many other things were blocked. Last time i got: [992.132362] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [gpu-manager:8250] [1020.132749] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [gpu-manager:8250] [1025.232819] INFO: rcu_sched self-detected stall on CPU ...followed by some irq stuff I also got this message with kworker instead of gpu-manager I highly suspect the nvidia gpu to be the issue here. Or some other hardware-based kernel issue. Or maybe nfs, i mounted 2 nfs shares on this machine for the first time, from which only 1 is available (i use this notebook in different offices). uname -r: Kernel: 4.10.0-27-generic -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12
[Kernel-packages] [Bug 1695737] [NEW] BUG: unable to handle kernel NULL pointer dereference at 0000000000000030
Public bug reported: `dmesg` shows ``` [ 2278.123945] BUG: unable to handle kernel NULL pointer dereference at 0030 [ 2278.123990] IP: iput+0xd8/0x230 [ 2278.124002] PGD 0 [ 2278.124018] Oops: [#1] SMP [ 2278.124031] Modules linked in: msr rfcomm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat libcrc32c nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore iptable_filter pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) bnep cdc_ether usbnet r8152 rtsx_usb_ms memstick btusb btrtl btbcm btintel bluetooth binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media hid_multitouch zfs(POE) zunicode(POE) zavl(POE) icp(POE) nls_iso8859_1 zcommon(POE) [ 2278.124258] znvpair(POE) spl(OE) intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 arc4 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf iwldvm mac80211 input_leds joydev iwlwifi serio_raw cfg80211 ideapad_laptop sparse_keymap wmi mei_me mac_hid mei shpchp lpc_ich ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi coda parport_pc sunrpc ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid psmouse r8169 mii i915 fjes video i2c_algo_bit drm_kms_helper ahci syscopyarea libahci sysfillrect sysimgblt fb_sys_fops drm [ 2278.124475] CPU: 6 PID: 19534 Comm: firefox Tainted: P OE 4.10.0-21-generic #23-Ubuntu [ 2278.124503] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21) 07/12/2013 [ 2278.124528] task: 9e39bb841680 task.stack: acb24849c000 [ 2278.124548] RIP: 0010:iput+0xd8/0x230 [ 2278.125802] RSP: :acb24849f840 EFLAGS: 00010246 [ 2278.127039] RAX: RBX: RCX: 0001 [ 2278.128275] RDX: 0003 RSI: 9e362381e080 RDI: 9e362381e080 [ 2278.129508] RBP: acb24849f860 R08: 0101 R09: [ 2278.130748] R10: 00045fc3 R11: 7c6a R12: 9e362381dff8 [ 2278.131983] R13: 9e362381e080 R14: 9e362381e150 R15: 9e366fd5b680 [ 2278.133204] FS: 7f1de9068740() GS:9e3a3f38() knlGS: [ 2278.134427] CS: 0010 DS: ES: CR0: 80050033 [ 2278.135646] CR2: 0030 CR3: 00035a11b000 CR4: 001406e0 [ 2278.136954] Call Trace: [ 2278.138173] dentry_unlink_inode+0xc1/0x160 [ 2278.139425] __dentry_kill+0xbe/0x160 [ 2278.140654] shrink_dentry_list+0x151/0x300 [ 2278.141857] prune_dcache_sb+0x5a/0x80 [ 2278.143013] super_cache_scan+0x118/0x1a0 [ 2278.144167] shrink_slab.part.40+0x1f5/0x420 [ 2278.145317] shrink_slab+0x29/0x30 [ 2278.146432] shrink_node+0x108/0x320 [ 2278.147522] do_try_to_free_pages+0xf5/0x330 [ 2278.148599] try_to_free_pages+0xe9/0x190 [ 2278.149658] __alloc_pages_slowpath+0x40f/0xba0 [ 2278.150714] __alloc_pages_nodemask+0x209/0x260 [ 2278.151769] alloc_pages_vma+0xab/0x250 [ 2278.152791] handle_mm_fault+0xe59/0x1360 [ 2278.153800] __do_page_fault+0x23e/0x4e0 [ 2278.154814] do_page_fault+0x22/0x30 [ 2278.155907] page_fault+0x28/0x30 [ 2278.156909] RIP: 0033:0x55e596b8f996 [ 2278.157875] RSP: 002b:7ffc78bef880 EFLAGS: 00010283 [ 2278.158821] RAX: 7f1d30d0 RBX: 04b58ca8 RCX: 00bdaca8 [ 2278.159793] RDX: 55e596d96280 RSI: 7f1d42c7e000 RDI: 7f1d34c7e000 [ 2278.160766] RBP: 0800 R08: R09: 55e596d96248 [ 2278.161746] R10: 55e596d96248 R11: 7f1de7d03440 R12: 7f1d3ed0 [ 2278.162731] R13: 7f1d30d0 R14: 0400 R15: 7f1dd3967000 [ 2278.163687] Code: 1d 2e 7c ce 00 48 85 db 74 18 48 8b 13 48 8b 7b 08 48 83 c3 18 4c 89 e6 ff d2 48 8b 13 48 85 d2 75 eb eb a1 49 8b 5c 24 28 a8 08 <4c> 8b 73 30 0f 85 1a 01 00 00 49 8b 46 20 48 85 c0 74 5b 4c 89 [ 2278.165683] RIP: iput+0xd8/0x230 RSP: acb24849f840 [ 2278.166653] CR2: 0030 [ 2278.171736] ---[ end trace cf4a00bf24f77373 ]--- ``` randomly after connecting USB devices directly or via a hub. Random USB crashes occur more frequently than with Ubuntu 16.10, but less often than with < 16.10. This might be related to Firefox UI freezing and becoming unresponsive (while the process state is sleeping and the `rtsx_usb_ms_1` process/kernel thread is unresponsive constantly). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux
[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
>From the top of my head: 1) In grub, select Advanced options, then recovery mode 2) Select "Drop to root shell" 3) Press Enter to confirm 4) The filesystem is mounted read-only at this point, so remount it: mount -o rw,remount / 5) Install the needed package: apt install xserver-xorg-input-all 6) Press Ctrl+D to leave the root shell. 7) Select resume boot from the menu. Here are some more information regarding the recovery mode: https://wiki.ubuntu.com/RecoveryMode -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I fixed the problem by installing xserver-xorg-input-all. Since this pulls in xserver-xorg-input-evdev, I suspect that this was the problem, as this package was not installed. It must have been somehow uninstalled during the upgrade. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I can confirm this bug. Using 16.04 everything worked fine; after upgrading to 16.10, mouse and keyboard stopped working. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I should probably mention that the keyboard works fine in recovery mode, so I suspect it has something to do with X. -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1672536] Re: task btrfs:841 blocked for more than 120 seconds.
** Description changed: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,02] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,04] [] do_vfs_ioctl+0xa3/0x610 [ +0,02] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:55] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,09] btrfs D 9158a5cd3b08 0 841 26458
[Kernel-packages] [Bug 1672536] [NEW] task btrfs:841 blocked for more than 120 seconds.
Public bug reported: After starting `btrfs scrub start /` `dmesg` contains ``` [Mär13 21:49] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,09] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,02] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,03] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,02] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,02] [] ? do_nanosleep+0x96/0xf0 [ +0,03] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,02] [] ? do_nanosleep+0x5a/0xf0 [ +0,03] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:51] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,10] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,07] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,34] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,03] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,02] [] do_vfs_ioctl+0xa3/0x610 [ +0,03] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:53] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,05] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,32] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,05] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,03] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [ +0,03] 915bac310718 9158a5cd3b20 ae49bd35 [ +0,03] Call Trace: [ +0,09] [] schedule+0x35/0x80 [ +0,03] [] schedule_preempt_disabled+0xe/0x10 [ +0,02] [] __mutex_lock_slowpath+0xb9/0x130 [ +0,03] [] mutex_lock+0x1f/0x30 [ +0,33] [] btrfs_relocate_block_group+0x1a3/0x2a0 [btrfs] [ +0,22] [] btrfs_relocate_chunk.isra.40+0x49/0xd0 [btrfs] [ +0,18] [] __btrfs_balance+0x634/0xc70 [btrfs] [ +0,17] [] btrfs_balance+0x2d0/0x5e0 [btrfs] [ +0,18] [] btrfs_ioctl_balance+0x379/0x390 [btrfs] [ +0,18] [] btrfs_ioctl+0xd1b/0x2010 [btrfs] [ +0,02] [] ? __schedule+0x308/0x770 [ +0,04] [] ? hrtimer_try_to_cancel+0x2c/0x120 [ +0,03] [] ? do_nanosleep+0x96/0xf0 [ +0,04] [] do_vfs_ioctl+0xa3/0x610 [ +0,02] [] ? __hrtimer_init+0xa0/0xa0 [ +0,03] [] ? do_nanosleep+0x5a/0xf0 [ +0,02] [] SyS_ioctl+0x79/0x90 [ +0,03] [] entry_SYSCALL_64_fastpath+0x1e/0xa8 [Mär13 21:55] INFO: task btrfs:841 blocked for more than 120 seconds. [ +0,11] Tainted: PW OE 4.8.0-41-generic #44-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,09] btrfs D 9158a5cd3b08 0 841 26458 0x [ +0,07] 9158a5cd3b08 00ffadd9f58b 915bad6e1d80 915986fb2c40 [ +0,04] 9158a5cd3ae8 9158a5cd4000 915bac310714 915986fb2c40 [
[Kernel-packages] [Bug 1670930] Re: Laptop wakes up from sleep mode after seconds the second time it's put to sleep
** Summary changed: - Laptop wakes up from sleep mode after seconds + Laptop wakes up from sleep mode after seconds the second time it's put to sleep ** Description changed: - Laptop wakes up from sleep mode after seconds + Laptop wakes up from sleep mode after seconds the second time it's put + to sleep. The first time always works. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-39-generic 4.8.0-39.42 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - BEN.PID ZUGR. BEFEHL - /dev/snd/controlC0: richter 18063 F pulseaudio + BEN.PID ZUGR. BEFEHL + /dev/snd/controlC0: richter 18063 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 8 04:57:54 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (451 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: - linux-restricted-modules-4.8.0-39-generic N/A - linux-backports-modules-4.8.0-39-generic N/A - linux-firmware1.161.1 + linux-restricted-modules-4.8.0-39-generic N/A + linux-backports-modules-4.8.0-39-generic N/A + linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-17 (141 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO -- 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/1670930 Title: Laptop wakes up from sleep mode after seconds the second time it's put to sleep Status in linux package in Ubuntu: Incomplete Bug description: Laptop wakes up from sleep mode after seconds the second time it's put to sleep. The first time always works. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-39-generic 4.8.0-39.42 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: zfs zunicode icp zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18063 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 8 04:57:54 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (451 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.8.0-39-generic N/A linux-backports-modules-4.8.0-39-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-17 (141 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670930/+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 1654849] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1654849/+attachment/4835742/+files/ProcCpuinfo.txt
--
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/1654849
Title:
ethernet interface connection crashes due to "NETDEV WATCHDOG:
enx00e07cc862a1 (r8152): transmit queue 0 timed out"
Status in linux package in Ubuntu:
Expired
Bug description:
`dmesg` reveals
[124280.117155] [ cut here ]
[124280.117170] WARNING: CPU: 0 PID: 0 at
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316
dev_watchdog+0x22c/0x230
[124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue
0 timed out
[124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO)
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm
mac80211
[124280.117232] iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE
4.8.0-32-generic #34-Ubuntu
[124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21)
07/12/2013
[124280.117266] 0286 83418944731d8c97 a240ff203d60
bba2fc82
[124280.117268] a240ff203db0 a240ff203da0
bb6830fb
[124280.117270] 013cff2d9200 0001
[124280.117272] Call Trace:
[124280.117273][] dump_stack+0x63/0x81
[124280.117283] [] __warn+0xcb/0xf0
[124280.117285] [] warn_slowpath_fmt+0x5f/0x80
[124280.117289] [] ? cpu_load_update+0xdd/0x150
[124280.117291] [] dev_watchdog+0x22c/0x230
[124280.117292] [] ? qdisc_rcu_free+0x40/0x40
[124280.117298] [] call_timer_fn+0x35/0x120
[124280.117299] [] run_timer_softirq+0x215/0x4b0
[124280.117303] [] ? ktime_get+0x41/0xb0
[124280.117307] [] ? lapic_next_deadline+0x26/0x30
[124280.117310] [] __do_softirq+0x10d/0x298
[124280.117315] [] irq_exit+0xa3/0xb0
[124280.117316] [] smp_apic_timer_interrupt+0x42/0x50
[124280.117317] [] apic_timer_interrupt+0x82/0x90
[124280.117317][] ?
cpuidle_enter_state+0x122/0x2c0
[124280.117326] [] cpuidle_enter+0x17/0x20
[124280.117330] [] call_cpuidle+0x2a/0x50
[124280.117331] [] cpu_startup_entry+0x2a0/0x350
[124280.117338] [] rest_init+0x77/0x80
[124280.117341] [] start_kernel+0x448/0x469
[124280.117343] [] ?
early_idt_handler_array+0x120/0x120
[124280.117344] [] x86_64_start_reservations+0x24/0x26
[124280.117346] [] x86_64_start_kernel+0x14d/0x170
[124280.117347] ---[ end trace a17e9d5abd1ea1de ]---
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.8.0-32-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
Liste der Hardware-Geräte (CAPTURE)
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
BEN.PID ZUGR. BEFEHL
/dev/snd/pcmC0D0p: richter 20519 F...m pulseaudio
/dev/snd/controlC0: richter 20519 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
Mixer name : 'Realtek ALC269VC'
Components : 'HDA:10ec0269,17aac034,00100202
HDA:80862806,80860101,0010'
Controls : 30
Simple ctrls : 12
CurrentDesktop: Unity
Date: Sun Jan 8 15:03:36 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on
[Kernel-packages] [Bug 1654849] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1654849/+attachment/4835741/+files/Lsusb.txt
--
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/1654849
Title:
ethernet interface connection crashes due to "NETDEV WATCHDOG:
enx00e07cc862a1 (r8152): transmit queue 0 timed out"
Status in linux package in Ubuntu:
Expired
Bug description:
`dmesg` reveals
[124280.117155] [ cut here ]
[124280.117170] WARNING: CPU: 0 PID: 0 at
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316
dev_watchdog+0x22c/0x230
[124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue
0 timed out
[124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO)
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm
mac80211
[124280.117232] iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE
4.8.0-32-generic #34-Ubuntu
[124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21)
07/12/2013
[124280.117266] 0286 83418944731d8c97 a240ff203d60
bba2fc82
[124280.117268] a240ff203db0 a240ff203da0
bb6830fb
[124280.117270] 013cff2d9200 0001
[124280.117272] Call Trace:
[124280.117273][] dump_stack+0x63/0x81
[124280.117283] [] __warn+0xcb/0xf0
[124280.117285] [] warn_slowpath_fmt+0x5f/0x80
[124280.117289] [] ? cpu_load_update+0xdd/0x150
[124280.117291] [] dev_watchdog+0x22c/0x230
[124280.117292] [] ? qdisc_rcu_free+0x40/0x40
[124280.117298] [] call_timer_fn+0x35/0x120
[124280.117299] [] run_timer_softirq+0x215/0x4b0
[124280.117303] [] ? ktime_get+0x41/0xb0
[124280.117307] [] ? lapic_next_deadline+0x26/0x30
[124280.117310] [] __do_softirq+0x10d/0x298
[124280.117315] [] irq_exit+0xa3/0xb0
[124280.117316] [] smp_apic_timer_interrupt+0x42/0x50
[124280.117317] [] apic_timer_interrupt+0x82/0x90
[124280.117317][] ?
cpuidle_enter_state+0x122/0x2c0
[124280.117326] [] cpuidle_enter+0x17/0x20
[124280.117330] [] call_cpuidle+0x2a/0x50
[124280.117331] [] cpu_startup_entry+0x2a0/0x350
[124280.117338] [] rest_init+0x77/0x80
[124280.117341] [] start_kernel+0x448/0x469
[124280.117343] [] ?
early_idt_handler_array+0x120/0x120
[124280.117344] [] x86_64_start_reservations+0x24/0x26
[124280.117346] [] x86_64_start_kernel+0x14d/0x170
[124280.117347] ---[ end trace a17e9d5abd1ea1de ]---
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.8.0-32-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
Liste der Hardware-Geräte (CAPTURE)
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
BEN.PID ZUGR. BEFEHL
/dev/snd/pcmC0D0p: richter 20519 F...m pulseaudio
/dev/snd/controlC0: richter 20519 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
Mixer name : 'Realtek ALC269VC'
Components : 'HDA:10ec0269,17aac034,00100202
HDA:80862806,80860101,0010'
Controls : 30
Simple ctrls : 12
CurrentDesktop: Unity
Date: Sun Jan 8 15:03:36 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on 2015-12-12 (393 days
[Kernel-packages] [Bug 1654849] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1654849/+attachment/4835755/+files/ProcModules.txt
--
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/1654849
Title:
ethernet interface connection crashes due to "NETDEV WATCHDOG:
enx00e07cc862a1 (r8152): transmit queue 0 timed out"
Status in linux package in Ubuntu:
Expired
Bug description:
`dmesg` reveals
[124280.117155] [ cut here ]
[124280.117170] WARNING: CPU: 0 PID: 0 at
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316
dev_watchdog+0x22c/0x230
[124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue
0 timed out
[124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO)
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm
mac80211
[124280.117232] iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE
4.8.0-32-generic #34-Ubuntu
[124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21)
07/12/2013
[124280.117266] 0286 83418944731d8c97 a240ff203d60
bba2fc82
[124280.117268] a240ff203db0 a240ff203da0
bb6830fb
[124280.117270] 013cff2d9200 0001
[124280.117272] Call Trace:
[124280.117273][] dump_stack+0x63/0x81
[124280.117283] [] __warn+0xcb/0xf0
[124280.117285] [] warn_slowpath_fmt+0x5f/0x80
[124280.117289] [] ? cpu_load_update+0xdd/0x150
[124280.117291] [] dev_watchdog+0x22c/0x230
[124280.117292] [] ? qdisc_rcu_free+0x40/0x40
[124280.117298] [] call_timer_fn+0x35/0x120
[124280.117299] [] run_timer_softirq+0x215/0x4b0
[124280.117303] [] ? ktime_get+0x41/0xb0
[124280.117307] [] ? lapic_next_deadline+0x26/0x30
[124280.117310] [] __do_softirq+0x10d/0x298
[124280.117315] [] irq_exit+0xa3/0xb0
[124280.117316] [] smp_apic_timer_interrupt+0x42/0x50
[124280.117317] [] apic_timer_interrupt+0x82/0x90
[124280.117317][] ?
cpuidle_enter_state+0x122/0x2c0
[124280.117326] [] cpuidle_enter+0x17/0x20
[124280.117330] [] call_cpuidle+0x2a/0x50
[124280.117331] [] cpu_startup_entry+0x2a0/0x350
[124280.117338] [] rest_init+0x77/0x80
[124280.117341] [] start_kernel+0x448/0x469
[124280.117343] [] ?
early_idt_handler_array+0x120/0x120
[124280.117344] [] x86_64_start_reservations+0x24/0x26
[124280.117346] [] x86_64_start_kernel+0x14d/0x170
[124280.117347] ---[ end trace a17e9d5abd1ea1de ]---
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.8.0-32-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
Liste der Hardware-Geräte (CAPTURE)
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
BEN.PID ZUGR. BEFEHL
/dev/snd/pcmC0D0p: richter 20519 F...m pulseaudio
/dev/snd/controlC0: richter 20519 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
Mixer name : 'Realtek ALC269VC'
Components : 'HDA:10ec0269,17aac034,00100202
HDA:80862806,80860101,0010'
Controls : 30
Simple ctrls : 12
CurrentDesktop: Unity
Date: Sun Jan 8 15:03:36 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on
[Kernel-packages] [Bug 1654849] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1654849/+attachment/4835756/+files/UdevDb.txt
--
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/1654849
Title:
ethernet interface connection crashes due to "NETDEV WATCHDOG:
enx00e07cc862a1 (r8152): transmit queue 0 timed out"
Status in linux package in Ubuntu:
Expired
Bug description:
`dmesg` reveals
[124280.117155] [ cut here ]
[124280.117170] WARNING: CPU: 0 PID: 0 at
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316
dev_watchdog+0x22c/0x230
[124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue
0 timed out
[124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO)
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm
mac80211
[124280.117232] iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE
4.8.0-32-generic #34-Ubuntu
[124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21)
07/12/2013
[124280.117266] 0286 83418944731d8c97 a240ff203d60
bba2fc82
[124280.117268] a240ff203db0 a240ff203da0
bb6830fb
[124280.117270] 013cff2d9200 0001
[124280.117272] Call Trace:
[124280.117273][] dump_stack+0x63/0x81
[124280.117283] [] __warn+0xcb/0xf0
[124280.117285] [] warn_slowpath_fmt+0x5f/0x80
[124280.117289] [] ? cpu_load_update+0xdd/0x150
[124280.117291] [] dev_watchdog+0x22c/0x230
[124280.117292] [] ? qdisc_rcu_free+0x40/0x40
[124280.117298] [] call_timer_fn+0x35/0x120
[124280.117299] [] run_timer_softirq+0x215/0x4b0
[124280.117303] [] ? ktime_get+0x41/0xb0
[124280.117307] [] ? lapic_next_deadline+0x26/0x30
[124280.117310] [] __do_softirq+0x10d/0x298
[124280.117315] [] irq_exit+0xa3/0xb0
[124280.117316] [] smp_apic_timer_interrupt+0x42/0x50
[124280.117317] [] apic_timer_interrupt+0x82/0x90
[124280.117317][] ?
cpuidle_enter_state+0x122/0x2c0
[124280.117326] [] cpuidle_enter+0x17/0x20
[124280.117330] [] call_cpuidle+0x2a/0x50
[124280.117331] [] cpu_startup_entry+0x2a0/0x350
[124280.117338] [] rest_init+0x77/0x80
[124280.117341] [] start_kernel+0x448/0x469
[124280.117343] [] ?
early_idt_handler_array+0x120/0x120
[124280.117344] [] x86_64_start_reservations+0x24/0x26
[124280.117346] [] x86_64_start_kernel+0x14d/0x170
[124280.117347] ---[ end trace a17e9d5abd1ea1de ]---
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.8.0-32-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
Liste der Hardware-Geräte (CAPTURE)
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
BEN.PID ZUGR. BEFEHL
/dev/snd/pcmC0D0p: richter 20519 F...m pulseaudio
/dev/snd/controlC0: richter 20519 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
Mixer name : 'Realtek ALC269VC'
Components : 'HDA:10ec0269,17aac034,00100202
HDA:80862806,80860101,0010'
Controls : 30
Simple ctrls : 12
CurrentDesktop: Unity
Date: Sun Jan 8 15:03:36 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on 2015-12-12 (393
[Kernel-packages] [Bug 1654849] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1654849/+attachment/4835753/+files/ProcCpuinfo.txt
--
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/1654849
Title:
ethernet interface connection crashes due to "NETDEV WATCHDOG:
enx00e07cc862a1 (r8152): transmit queue 0 timed out"
Status in linux package in Ubuntu:
Expired
Bug description:
`dmesg` reveals
[124280.117155] [ cut here ]
[124280.117170] WARNING: CPU: 0 PID: 0 at
/build/linux-_qw1uB/linux-4.8.0/net/sched/sch_generic.c:316
dev_watchdog+0x22c/0x230
[124280.117172] NETDEV WATCHDOG: enx00e07cc862a1 (r8152): transmit queue
0 timed out
[124280.117173] Modules linked in: openafs(POE) xfs libcrc32c uas
usb_storage snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd
soundcore iptable_filter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE)
vboxnetflt(OE) vboxdrv(OE) bbswitch(OE) binfmt_misc zfs(PO) zunicode(PO)
zcommon(PO) znvpair(PO) spl(O) zavl(PO) rtsx_usb_ms memstick usblp
nls_iso8859_1 cdc_ether usbnet r8152 intel_rapl x86_pkg_temp_thermal coretemp
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel
aesni_intel uvcvideo aes_x86_64 videobuf2_vmalloc lrw videobuf2_memops
glue_helper ablk_helper cryptd videobuf2_v4l2 intel_cstate videobuf2_core
intel_rapl_perf hid_multitouch videodev media arc4 joydev input_leds iwldvm
mac80211
[124280.117232] iwlwifi cfg80211 serio_raw lpc_ich ideapad_laptop
sparse_keymap wmi mac_hid mei_me mei shpchp parport_pc ppdev lp sunrpc parport
coda ip_tables x_tables autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb
hid_generic usbhid hid psmouse ahci libahci i915 r8169 mii video i2c_algo_bit
drm_kms_helper fjes syscopyarea sysfillrect sysimgblt fb_sys_fops drm
[124280.117262] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P OE
4.8.0-32-generic #34-Ubuntu
[124280.117263] Hardware name: LENOVO 20221/INVALID, BIOS 71CN51WW(V1.21)
07/12/2013
[124280.117266] 0286 83418944731d8c97 a240ff203d60
bba2fc82
[124280.117268] a240ff203db0 a240ff203da0
bb6830fb
[124280.117270] 013cff2d9200 0001
[124280.117272] Call Trace:
[124280.117273][] dump_stack+0x63/0x81
[124280.117283] [] __warn+0xcb/0xf0
[124280.117285] [] warn_slowpath_fmt+0x5f/0x80
[124280.117289] [] ? cpu_load_update+0xdd/0x150
[124280.117291] [] dev_watchdog+0x22c/0x230
[124280.117292] [] ? qdisc_rcu_free+0x40/0x40
[124280.117298] [] call_timer_fn+0x35/0x120
[124280.117299] [] run_timer_softirq+0x215/0x4b0
[124280.117303] [] ? ktime_get+0x41/0xb0
[124280.117307] [] ? lapic_next_deadline+0x26/0x30
[124280.117310] [] __do_softirq+0x10d/0x298
[124280.117315] [] irq_exit+0xa3/0xb0
[124280.117316] [] smp_apic_timer_interrupt+0x42/0x50
[124280.117317] [] apic_timer_interrupt+0x82/0x90
[124280.117317][] ?
cpuidle_enter_state+0x122/0x2c0
[124280.117326] [] cpuidle_enter+0x17/0x20
[124280.117330] [] call_cpuidle+0x2a/0x50
[124280.117331] [] cpu_startup_entry+0x2a0/0x350
[124280.117338] [] rest_init+0x77/0x80
[124280.117341] [] start_kernel+0x448/0x469
[124280.117343] [] ?
early_idt_handler_array+0x120/0x120
[124280.117344] [] x86_64_start_reservations+0x24/0x26
[124280.117346] [] x86_64_start_kernel+0x14d/0x170
[124280.117347] ---[ end trace a17e9d5abd1ea1de ]---
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-32-generic 4.8.0-32.34
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: openafs zfs zunicode zcommon znvpair zavl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.8.0-32-generic.
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
ArecordDevices:
Liste der Hardware-Geräte (CAPTURE)
Karte 0: PCH [HDA Intel PCH], Gerät 0: ALC269VC Analog [ALC269VC Analog]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0
AudioDevicesInUse:
BEN.PID ZUGR. BEFEHL
/dev/snd/pcmC0D0p: richter 20519 F...m pulseaudio
/dev/snd/controlC0: richter 20519 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd361 irq 31'
Mixer name : 'Realtek ALC269VC'
Components : 'HDA:10ec0269,17aac034,00100202
HDA:80862806,80860101,0010'
Controls : 30
Simple ctrls : 12
CurrentDesktop: Unity
Date: Sun Jan 8 15:03:36 2017
HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
InstallationDate: Installed on
