[Kernel-packages] [Bug 1964844] [NEW] linux-firmware upgrade started failing
Public bug reported: It was observed that linux-firmware upgrade started failing now. At the end of the apt upgrade process, the following message appeared (messages are in Portuguese): Erros foram encontrados durante o processamento de: /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In the middle of the upgrade process, there was the following error: A descompactar linux-firmware (20220314.gitcd01f857-0ubuntu1) sobre (20220302.gitee0667aa-0ubuntu1) ... dpkg: erro ao processar o arquivo /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): não foi possível abrir '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': Arquivo ou diretório inexistente No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic The suspect I have is that linux-firmware started requiring an executable /tmp. This computer has the following /tmp mount: tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,relatime,inode64) Considering dpkg/apt are already privileged processes, I find it strange it tries to extract and execute from /tmp when it could, theoretically, do this from another, safer, directory made specifically for dpkg/apt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario2559 F pipewire usuario2560 F wireplumber /dev/snd/pcmC0D0p: usuario2559 F...m pipewire /dev/snd/seq:usuario2559 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 14 20:43:31 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 HibernationDevice: RESUME=none InstallationDate: Installed on 2017-06-13 (1735 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 nbd.nbds_max=2 nbd.max_part=127 mtrr_gran_size=128M mtrr_chunk_size=256M log_buf_len=128M zswap.enabled=1 zswap.zpool=z3fold usbhid.quirks=0x0079:0x0006:0x10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2019-12-22 (813 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964844 Title: linux-firmware upgrade started failing Status in linux-firmware package in Ubuntu: New Bug description: It was observed that linux-firmware upgrade started failing now. At the end of the apt upgrade process, the following message appeared (messages are in Portuguese): Erros foram encontrados durante o processamento de: /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In the middle of the upgrade process, there was the following error: A descompactar linux-firmware (20220314.gitcd01f857-0ubuntu1) sobre
[Kernel-packages] [Bug 1949314] [NEW] intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Public bug reported: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: intel-gpu-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: New Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1948541] [NEW] Microphone is silent if left and right channels are set to the same volume
Public bug reported: If the microphone volume is set the same for both left and right channels, it's nearly silent, being unusable, as if the left and right channel cancel each other. The workaround I had on Focal was to create a remapped source only with the right channel. However, on jammy, another bug makes this workaround fail. While I reported the pipewire bug at https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1734 I'm also reporting this bug so, hopefully, the kernel could be fixed and no workaround would be required in the future. The following image shows an example of the volume disparity that makes the microphone work properly: https://media.discordapp.net/attachments/327981417407447040/901465383201013800/unknown.png While such setting allow to use the microphone, it's annoying for the people I'm talking with. The alsa report can be located at http://alsa- project.org/db/?f=0751ed5c43c0f35e5385971735a518951cb753f0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario 27750 F pipewire usuario 27751 F wireplumber /dev/snd/pcmC0D0p: usuario 27750 F...m pipewire /dev/snd/seq:usuario 27750 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Oct 23 14:51:11 2021 HibernationDevice: # RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1592 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 nbd.nbds_max=2 nbd.max_part=127 mtrr_gran_size=128M mtrr_chunk_size=256M log_buf_len=128M zswap.enabled=1 zswap.zpool=z3fold usbhid.quirks=0x0079:0x0006:0x10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.202 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2019-12-22 (670 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1948541 Title: Microphone is silent if left and right channels are set to the same volume Status in linux package in Ubuntu: New Bug description: If the microphone volume is set the same for both left and right channels, it's nearly silent, being unusable, as if the left and right channel cancel each other. The workaround I had on Focal was to create a remapped source only with the right channel. However, on jammy, another bug makes this workaround fail. While I reported the pipewire bug at https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1734 I'm also reporting this bug so, hopefully, the kernel could be fixed and no workaround would be required in the future. The following image shows an example of the volume disparity that makes the microphone work properly: https://media.discordapp.net/attachments/327981417407447040/901465383201013800/unknown.png While such setting allow to use the microphone, it's annoying for the people I'm talking with. The alsa report can be located at http://alsa- project.org/db/?f=0751ed5c43c0f35e5385971735a518951cb753f0 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname:
[Kernel-packages] [Bug 1946288] [NEW] iGVT-g guest freezes if idle for too long
Public bug reported: A Windows 10 iGVT-g guest is crashing if left idle for too long. "Too long" can mean hours or even minutes with no load. The QEMU command line is: /usr/bin/qemu-system-x86_64 -name Windows 10 -nodefaults -M pc,usb=true -machine kernel_irqchip=on -enable-kvm -mem-prealloc -mem-path /dev/hugepages/qemu -device qemu-xhci,id=qemu-xhci,addr=4,p2=15,p3=15,streams=on,command_serr_enable=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -drive file=./images/redm.qcow2,if=virtio -cpu host -smp sockets=1,cores=2,threads=1 -m 8192M -bios /usr/share/seabios/bios.bin -device usb-tablet,id=tablet,bus=qemu-xhci.0,port=1 -vga none -monitor vc -serial stdio -display gtk,gl=on -device vfio-pci-nohotplug,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4-448a-9f09-7b93adbf672c,x-igd-opregion=on,display=on,addr=0x3,rombar=0,id=iHD520,ramfb=on -device ivshmem-plain,memdev=HMB -object memory-backend-file,id=HMB,size=4M,mem-path=/dev/shm/test,share=on -netdev user,id=net0,hostfwd=::33890-:3389,smb=./TOSHIBA2TB/ -device virtio-net-pci,netdev=net0,id=n0,addr=0x8 -monitor telnet:127.0.0.1:5,server,nowait Normally, I use the machine pc-i440fx-3.1 but I set the latest one (pc, or pc-i440fx-4.2) for testing, which didn't fix this freeze. In this state, it's not possible to reclaim the memory and the virtual GPU, they are stuck until the computer is powered off. After this QEMU guest freeze, it is impossible to power off the computer cleanly: it's required to forcefully shutdown, as the system fails to The telnet server from the guest still connect, but doesn't respond. I installed the OEM kernel to get the 5.14 version of the kernel. Testing with drm-tip (commit 7c36ed237585ed2f645439e62dafccac070d5e33, from August), I was able to left the guest idle for hours with no problem multiple times, but using Ubuntu's generic (5.4, 5.8, 5.11) or oem (5.14) kernel this freeze is happening. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1004-oem 5.14.0-1004.4 ProcVersionSignature: Ubuntu 5.14.0-1004.4-oem 5.14.5 Uname: Linux 5.14.0-1004-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Oct 6 21:33:41 2021 InstallationDate: Installed on 2017-06-13 (1576 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: Upgraded to focal on 2019-12-22 (654 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-signed-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946288 Title: iGVT-g guest freezes if idle for too long Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: A Windows 10 iGVT-g guest is crashing if left idle for too long. "Too long" can mean hours or even minutes with no load. The QEMU command line is: /usr/bin/qemu-system-x86_64 -name Windows 10 -nodefaults -M pc,usb=true -machine kernel_irqchip=on -enable-kvm -mem-prealloc -mem-path /dev/hugepages/qemu -device qemu-xhci,id=qemu-xhci,addr=4,p2=15,p3=15,streams=on,command_serr_enable=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -drive file=./images/redm.qcow2,if=virtio -cpu host -smp sockets=1,cores=2,threads=1 -m 8192M -bios /usr/share/seabios/bios.bin -device usb-tablet,id=tablet,bus=qemu-xhci.0,port=1 -vga none -monitor vc -serial stdio -display gtk,gl=on -device vfio-pci-nohotplug,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4-448a-9f09-7b93adbf672c,x-igd-opregion=on,display=on,addr=0x3,rombar=0,id=iHD520,ramfb=on -device ivshmem-plain,memdev=HMB -object memory-backend-file,id=HMB,size=4M,mem-path=/dev/shm/test,share=on -netdev user,id=net0,hostfwd=::33890-:3389,smb=./TOSHIBA2TB/ -device virtio-net-pci,netdev=net0,id=n0,addr=0x8 -monitor telnet:127.0.0.1:5,server,nowait Normally, I use the machine pc-i440fx-3.1 but I set the latest one (pc, or pc-i440fx-4.2) for testing, which didn't fix this freeze. In this state, it's not possible to reclaim the memory and the virtual GPU, they are stuck until the computer is powered off. After this QEMU guest freeze, it is impossible to power off the computer cleanly: it's required to forcefully shutdown, as the system fails to The telnet server from the guest still connect, but doesn't respond. I installed the OEM kernel to get the 5.14 version of the kernel. Testing with drm-tip (commit 7c36ed237585ed2f645439e62dafccac070d5e33, from August), I was able to left the guest idle for hours with no problem multiple times, but using Ubuntu's generic (5.4, 5.8, 5.11) or oem (5.14) kernel this freeze is happening. ProblemType: Bug
[Kernel-packages] [Bug 1925263] Re: TL-WN821N V5 does not work
** Also affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1925263 Title: TL-WN821N V5 does not work Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: I bought a TP-Link TL-WN821N V5 wireless adapter and it is not working on Xubuntu 20.04. On dmesg, it is detected correctly. However, the authentication times out very quickly. The module from https://github.com/clnhub/rtl8192eu-linux.git works, but this is not ideal, because it requires rebuilding the module for every kernel version and, either disable Secure Boot or sign every module for every kernel update. The attached file has the full dmesg log, including trying rtl8xxxu with debug=0x log. I noticed the log shows this device is untested. lshw output for this device: *-network:1 description: Wireless interface physical id: 4 bus info: usb@1:1 logical name: wlxd03745cb0794 serial: d0:37:45:cb:07:94 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8xxxu driverversion=5.8.0-50-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11 lsusb: Bus 001 Device 005: ID 2357:0107 TP-Link TL-WN821N Version 5 RTL8192EU ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 20 19:42:11 2021 InstallationDate: Installed on 2017-06-13 (1406 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: Upgraded to focal on 2019-12-22 (485 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1925263/+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 1904953] Re: USB2.0 HUB only works after an USB device is connected
Using the kernel from comment 10, I did not observe an improvement: the devices connected to the hub aren't detected as often as before, requiring the same workaround. ** Attachment added: "Two dmesg with the test kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+attachment/5437638/+files/dmesg-510056-usbhub.zip -- 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/1904953 Title: USB2.0 HUB only works after an USB device is connected Status in linux package in Ubuntu: Incomplete Bug description: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+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 1904953] Re: USB2.0 HUB only works after an USB device is connected
Here are two dmesg with the arguments added. On first dmesg I connected the USB hub 3 times. The two devices connected to the hub were: 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 25a7:fa23 Compx 2.4G Receiver On the first attempt, all devices were detected. On the second and third attempt, only the USB hub was detected. For second dmesg, the log was cleared with dmesg -C, then the USB hub was connected, with both the Microsoft mouse (045e:00cb) and the wireless keyboard and mouse (25a7:fa23) connected to the hub, neither was detected at first. After the wireless keyboard and mouse (25a7:fa23) was disconnected, the Microsoft mouse (045e:00cb) was detected and the hub started working normally. ** Attachment added: "Two dmesg logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+attachment/5437283/+files/dmesg-510rc4-usbhub.txt.zip -- 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/1904953 Title: USB2.0 HUB only works after an USB device is connected Status in linux package in Ubuntu: Incomplete Bug description: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+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 1904953] Re: USB2.0 HUB only works after an USB device is connected
Using 5.10-rc4, the same problem was observed -- 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/1904953 Title: USB2.0 HUB only works after an USB device is connected Status in linux package in Ubuntu: Incomplete Bug description: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+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 1904953] Re: USB2.0 HUB only works after an USB device is connected
Disabling the autosuspend from the USB device fixed the problem.
However, I did not want to disable it for all USB devices, so I added an
udev rule:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="214b",
ATTR{idProduct}=="7000", ATTR{product}=="USB2.0 HUB",
TEST=="power/control", ATTR{power/control}:="on"
On Windows, the USB power saving is enabled but this does not happen.
Maybe Windows has a quirk configured for this device already?
--
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/1904953
Title:
USB2.0 HUB only works after an USB device is connected
Status in linux package in Ubuntu:
Confirmed
Bug description:
The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem
on Linux where often it is only detected after another device (for
example a mouse) is connected to it.
On the computer's firmware screen and configuration, and on Windows,
the hub works fine: once connected, it is detected and devices
connected on it are detected.
On Linux, most of the times nothing happens or only the hub is
detected (not the devices connected to it). After one of the devices
is disconnected and reconnected, or another USB device is connected in
the hub, then the hub and all devices connected to it are detected at
once.
I believe this is a problem related to the Linux kernel because I
never observed this behaviour on the computer's firmware or on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-53-generic 5.4.0-53.59
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Nov 19 23:54:44 2020
HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc
InstallationDate: Installed on 2017-06-13 (1255 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0
i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc
log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2
nbd.max_part=127
RelatedPackageVersions:
linux-restricted-modules-5.4.0-53-generic N/A
linux-backports-modules-5.4.0-53-generic N/A
linux-firmware1.187.4
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago)
dmi.bios.date: 08/09/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias:
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904953/+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 1904953] [NEW] USB2.0 HUB only works after an USB device is connected
Public bug reported: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (333 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** 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/1904953 Title: USB2.0 HUB only works after an USB device is connected Status in linux package in Ubuntu: Confirmed Bug description: The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on Linux where often it is only detected after another device (for example a mouse) is connected to it. On the computer's firmware screen and configuration, and on Windows, the hub works fine: once connected, it is detected and devices connected on it are detected. On Linux, most of the times nothing happens or only the hub is detected (not the devices connected to it). After one of the devices is disconnected and reconnected, or another USB device is connected in the hub, then the hub and all devices connected to it are detected at once. I believe this is a problem related to the Linux kernel because I never observed this behaviour on the computer's firmware or on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Nov 19 23:54:44 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1255 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic
[Kernel-packages] [Bug 1899063] [NEW] Deleting files on exFAT USB degrades system
Public bug reported: I was deleting a large amount of files from an exFAT USB pendrive and at 45% of the file deletion, the system became degraded: USB disks were no longer possible to mount or dismount, no new USB devices were detected, systemd-journal and syslog were using 100% CPU on htop each, shutdown, reboot and suspend were disabled, commands using sudo no longer worked. I was unable to obtain anything meaningful while the error was happening because of how slow the system became. The following line repeated endlessly: [ 4649.820335] [EXFAT] sector_read: out of range error! (sec = 330029325056) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1938 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 8 14:20:48 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1212 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 SourcePackage: linux StagingDrivers: exfat UpgradeStatus: Upgraded to focal on 2019-12-22 (290 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal staging -- 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/1899063 Title: Deleting files on exFAT USB degrades system Status in linux package in Ubuntu: New Bug description: I was deleting a large amount of files from an exFAT USB pendrive and at 45% of the file deletion, the system became degraded: USB disks were no longer possible to mount or dismount, no new USB devices were detected, systemd-journal and syslog were using 100% CPU on htop each, shutdown, reboot and suspend were disabled, commands using sudo no longer worked. I was unable to obtain anything meaningful while the error was happening because of how slow the system became. The following line repeated endlessly: [ 4649.820335] [EXFAT] sector_read: out of range error! (sec = 330029325056) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1938 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Oct 8 14:20:48 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1212 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=1M usbhid.quirks=0x0079:0x0006:0x10 nbd.nbds_max=2 nbd.max_part=127 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3
[Kernel-packages] [Bug 1824175] Re: iGVT-g guest does not load graphics: kernel WARNING and wedged GPU
I'm not able to reproduce this using 5.4.0-37-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/1824175 Title: iGVT-g guest does not load graphics: kernel WARNING and wedged GPU Status in linux package in Ubuntu: Incomplete Bug description: On an Ubuntu 19.04 Disco Dingo Beta (both live and installed) Intel GVT-g guest, it was noticed that the graphical interface does not load. The following message appears: [ 19.844904] i915 :00:03.0: Failed to initialize GPU, declaring it wedged! And there are two kernel WARNING that appear. The first WARNING seems harmless and it was already reported: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799102 and is related to the host kernel, on this case 4.18.0-17 from HWE. The second WARNING is new and probably is related to the failure to load the graphics. It is possible to access the guest using the serial console. While the system claims GDM is working, there is no graphical interface visible. I have tested with Xubuntu 19.04 Disco Dingo Beta too and the same problem was noticed: two kernel WARNING, a wedged GPU and failure to load the graphics, even if the LightDM services was shown as running by systemctl status. Ubuntu 18.04 guests with kernel 4.15 and 4.18 are working. Mageia 7 guests with kernel 5.0.7 are working too, this seems related to the 5.0.0 kernel from Disco. Tested with both 5.0.0-7 and 5.0.0-8. Example of QEMU command line used: qemu-system-x86_64 -global PIIX4_PM.disable_s4=1 -M pc,usb=false -machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -name "Ubuntu Disco" -k pt-br -nodefaults -accel kvm -m 2G -cpu host -smp cores=2,threads=1 -netdev user,id=net0 -device e1000,netdev=net0,addr=8 -device vfio- pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/84de120a-c340-48fc- ba40-62f54c76f3ad,rombar=0,display=on,addr=0x3,id=iHD520 -device nec- usb-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144 -device usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display gtk,gl=on -hda /home/usuario/.local/share/libvirt/images/ubuntu_disco.qcow2 -monitor vc -serial vc ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-8-generic 5.0.0-8.9 ProcVersionSignature: User Name 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu26 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Apr 10 12:04:47 2019 InstallationDate: Installed on 2019-04-09 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) IwConfig: ens8 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 002: ID 46f4:0002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=deb9f102-2eaf-4c05-96da-8c541c55726b ro quiet splash console=ttyS0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-3.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-3.1:cvnQEMU:ct1:cvrpc-i440fx-3.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-3.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824175/+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 1880049] Re: Using Lakka with Intel GVT-g freezes the host system
** 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/1880049 Title: Using Lakka with Intel GVT-g freezes the host system Status in linux package in Ubuntu: Confirmed Bug description: I tried to start Lakka (http://www.lakka.tv/) using QEMU with Intel GVT-g and, when the graphics should start loading, the system freezes. The command line used was: The command line I used to start QEMU was: sudo qemu-system-x86_64 -m 1024 -cpu Skylake-Client -vga none -accel kvm -device nec-usb-xhci -device usb-host,id=maxprint,vendorid=0x13fe -boot menu=on -serial vc -serial stdio -display gtk,gl=on -device vfio-pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4 -448a-9f09-7b93adbf672c,x-igd- opregion=on,display=on,addr=0x5,rombar=0,id=iHD520 -bios /usr/share/ovmf/OVMF.fd Relevant syslog messages with the BUG: May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207424] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: Adding to iommu group 0 May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207427] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: MDEV: group_id = 0 May 21 21:50:42 Lenovo-ideapad-310-14ISK dbus-daemon[21697]: [session uid=0 pid=21695] AppArmor D-Bus mediation is enabled May 21 21:51:06 Lenovo-ideapad-310-14ISK kernel: [ 7703.690519] usb 1-3: reset high-speed USB device number 10 using xhci_hcd May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354929] BUG: kernel NULL pointer dereference, address: 0008 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354932] #PF: supervisor write access in kernel mode May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354933] #PF: error_code(0x0002) - not-present page May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354935] PGD 0 P4D 0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354937] Oops: 0002 [#1] SMP PTI May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354940] CPU: 2 PID: 254 Comm: gvt workload 0 Tainted: P C O 5.4.0-32-generic #36-Ubuntu May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354941] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354979] RIP: 0010:prepare_workload+0xf6/0x480 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354981] Code: 1a 00 00 48 8b 4f 40 48 8b 40 20 4c 8b 40 40 31 c0 83 7f 18 0c 49 8b 90 f0 02 00 00 74 24 48 63 f0 48 83 c0 01 48 8b 54 f2 20 <48> 89 4a 08 48 83 f8 04 74 12 49 8b 90 f0 02 00 00 48 8b 4c c7 40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354983] RSP: 0018:b39a403fbdb0 EFLAGS: 00010202 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354984] RAX: 0001 RBX: 8c46bb376900 RCX: 0004565c8000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354985] RDX: RSI: RDI: 8c47d4f9a840 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354987] RBP: b39a403fbde8 R08: 8c471382fc00 R09: e658e558 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354988] R10: e45ce758 R11: e65ce55c R12: f5a6d1436180 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354989] R13: R14: 8c46bb376900 R15: 8c47d8e88000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354990] FS: () GS:8c47de30() knlGS: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354991] CS: 0010 DS: ES: CR0: 80050033 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354992] CR2: 0008 CR3: 0004565cc004 CR4: 003626e0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354994] DR0: DR1: DR2: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354995] DR3: DR6: fffe0ff0 DR7: 0400 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354996] Call Trace: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355028] workload_thread+0x50d/0xde0 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355032] ? __switch_to_asm+0x40/0x70 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355036] ? do_wait_intr_irq+0xa0/0xa0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355038] kthread+0x104/0x140 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355065] ? intel_vgpu_clean_workloads+0x100/0x100 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355067] ? kthread_park+0x90/0x90 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355070] ret_from_fork+0x35/0x40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [
[Kernel-packages] [Bug 1880049] Re: Using Lakka with Intel GVT-g freezes the host system
I tested 5.7.0-050700-generic, and the system didn't crash. I'm able to use Lakka from QEMU most of the times. Once, a GPU hang happened, but I was able to restart LightDM to fix it. The attached file is the card0/error after the GPU hang. ** Attachment added: "card0/error" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880049/+attachment/5379573/+files/gpuhanglakkagvtg.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/1880049 Title: Using Lakka with Intel GVT-g freezes the host system Status in linux package in Ubuntu: Confirmed Bug description: I tried to start Lakka (http://www.lakka.tv/) using QEMU with Intel GVT-g and, when the graphics should start loading, the system freezes. The command line used was: The command line I used to start QEMU was: sudo qemu-system-x86_64 -m 1024 -cpu Skylake-Client -vga none -accel kvm -device nec-usb-xhci -device usb-host,id=maxprint,vendorid=0x13fe -boot menu=on -serial vc -serial stdio -display gtk,gl=on -device vfio-pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4 -448a-9f09-7b93adbf672c,x-igd- opregion=on,display=on,addr=0x5,rombar=0,id=iHD520 -bios /usr/share/ovmf/OVMF.fd Relevant syslog messages with the BUG: May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207424] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: Adding to iommu group 0 May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207427] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: MDEV: group_id = 0 May 21 21:50:42 Lenovo-ideapad-310-14ISK dbus-daemon[21697]: [session uid=0 pid=21695] AppArmor D-Bus mediation is enabled May 21 21:51:06 Lenovo-ideapad-310-14ISK kernel: [ 7703.690519] usb 1-3: reset high-speed USB device number 10 using xhci_hcd May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354929] BUG: kernel NULL pointer dereference, address: 0008 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354932] #PF: supervisor write access in kernel mode May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354933] #PF: error_code(0x0002) - not-present page May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354935] PGD 0 P4D 0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354937] Oops: 0002 [#1] SMP PTI May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354940] CPU: 2 PID: 254 Comm: gvt workload 0 Tainted: P C O 5.4.0-32-generic #36-Ubuntu May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354941] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354979] RIP: 0010:prepare_workload+0xf6/0x480 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354981] Code: 1a 00 00 48 8b 4f 40 48 8b 40 20 4c 8b 40 40 31 c0 83 7f 18 0c 49 8b 90 f0 02 00 00 74 24 48 63 f0 48 83 c0 01 48 8b 54 f2 20 <48> 89 4a 08 48 83 f8 04 74 12 49 8b 90 f0 02 00 00 48 8b 4c c7 40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354983] RSP: 0018:b39a403fbdb0 EFLAGS: 00010202 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354984] RAX: 0001 RBX: 8c46bb376900 RCX: 0004565c8000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354985] RDX: RSI: RDI: 8c47d4f9a840 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354987] RBP: b39a403fbde8 R08: 8c471382fc00 R09: e658e558 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354988] R10: e45ce758 R11: e65ce55c R12: f5a6d1436180 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354989] R13: R14: 8c46bb376900 R15: 8c47d8e88000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354990] FS: () GS:8c47de30() knlGS: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354991] CS: 0010 DS: ES: CR0: 80050033 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354992] CR2: 0008 CR3: 0004565cc004 CR4: 003626e0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354994] DR0: DR1: DR2: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354995] DR3: DR6: fffe0ff0 DR7: 0400 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354996] Call Trace: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355028] workload_thread+0x50d/0xde0 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355032] ? __switch_to_asm+0x40/0x70 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355036] ? do_wait_intr_irq+0xa0/0xa0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355038] kthread+0x104/0x140 May 21 21:51:07
[Kernel-packages] [Bug 1880049] [NEW] Using Lakka with Intel GVT-g freezes the host system
Public bug reported: I tried to start Lakka (http://www.lakka.tv/) using QEMU with Intel GVT-g and, when the graphics should start loading, the system freezes. The command line used was: The command line I used to start QEMU was: sudo qemu-system-x86_64 -m 1024 -cpu Skylake-Client -vga none -accel kvm -device nec-usb-xhci -device usb-host,id=maxprint,vendorid=0x13fe -boot menu=on -serial vc -serial stdio -display gtk,gl=on -device vfio- pci,sysfsdev=/sys/bus/pci/devices/:00:02.0/20312cec-80f4-448a- 9f09-7b93adbf672c,x-igd- opregion=on,display=on,addr=0x5,rombar=0,id=iHD520 -bios /usr/share/ovmf/OVMF.fd Relevant syslog messages with the BUG: May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207424] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: Adding to iommu group 0 May 21 21:50:35 Lenovo-ideapad-310-14ISK kernel: [ 7672.207427] vfio_mdev 20312cec-80f4-448a-9f09-7b93adbf672c: MDEV: group_id = 0 May 21 21:50:42 Lenovo-ideapad-310-14ISK dbus-daemon[21697]: [session uid=0 pid=21695] AppArmor D-Bus mediation is enabled May 21 21:51:06 Lenovo-ideapad-310-14ISK kernel: [ 7703.690519] usb 1-3: reset high-speed USB device number 10 using xhci_hcd May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354929] BUG: kernel NULL pointer dereference, address: 0008 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354932] #PF: supervisor write access in kernel mode May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354933] #PF: error_code(0x0002) - not-present page May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354935] PGD 0 P4D 0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354937] Oops: 0002 [#1] SMP PTI May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354940] CPU: 2 PID: 254 Comm: gvt workload 0 Tainted: P C O 5.4.0-32-generic #36-Ubuntu May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354941] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354979] RIP: 0010:prepare_workload+0xf6/0x480 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354981] Code: 1a 00 00 48 8b 4f 40 48 8b 40 20 4c 8b 40 40 31 c0 83 7f 18 0c 49 8b 90 f0 02 00 00 74 24 48 63 f0 48 83 c0 01 48 8b 54 f2 20 <48> 89 4a 08 48 83 f8 04 74 12 49 8b 90 f0 02 00 00 48 8b 4c c7 40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354983] RSP: 0018:b39a403fbdb0 EFLAGS: 00010202 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354984] RAX: 0001 RBX: 8c46bb376900 RCX: 0004565c8000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354985] RDX: RSI: RDI: 8c47d4f9a840 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354987] RBP: b39a403fbde8 R08: 8c471382fc00 R09: e658e558 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354988] R10: e45ce758 R11: e65ce55c R12: f5a6d1436180 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354989] R13: R14: 8c46bb376900 R15: 8c47d8e88000 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354990] FS: () GS:8c47de30() knlGS: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354991] CS: 0010 DS: ES: CR0: 80050033 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354992] CR2: 0008 CR3: 0004565cc004 CR4: 003626e0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354994] DR0: DR1: DR2: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354995] DR3: DR6: fffe0ff0 DR7: 0400 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.354996] Call Trace: May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355028] workload_thread+0x50d/0xde0 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355032] ? __switch_to_asm+0x40/0x70 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355036] ? do_wait_intr_irq+0xa0/0xa0 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355038] kthread+0x104/0x140 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355065] ? intel_vgpu_clean_workloads+0x100/0x100 [i915] May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355067] ? kthread_park+0x90/0x90 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355070] ret_from_fork+0x35/0x40 May 21 21:51:07 Lenovo-ideapad-310-14ISK kernel: [ 7704.355071] Modules linked in: nls_utf8 exfat(C) ccm ip6table_nat xt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle xt_comment bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) nf_tables nfnetlink rfcomm cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl_msr ledtrig_audio
[Kernel-packages] [Bug 1877003] [NEW] BUG and panic when ejecting USB devices after a SD card is used at least once
Public bug reported: It was observed that after a SD card is used, the computer can have a kernel BUG or kernel panic after a partition from removable media is unmounted. Steps to reproduce: 1) Insert a SD card; 2) Mount the SD card; 3) Unmount the SD card; 4) Eject the SD card; 5) Try mount or unmount partitions from removable media. With panics, there are no saved messages, as syslog get corrupt. But when a BUG happens, the following appears: May 5 19:53:06 Lenovo-ideapad-310-14ISK kernel: [ 302.156578] BUG: unable to handle page fault for address: 8ec9aa20 The paste with the full BUG can be found at: https://paste.ubuntu.com/p/rtShbPjDrn/ This causes problems consistently with 5.4.0-29-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1824 F pulseaudio CasperMD5CheckResult: skip Date: Tue May 5 19:57:35 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1056 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 cgroup_enable=memory swapaccount=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2019-12-22 (135 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** 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/1877003 Title: BUG and panic when ejecting USB devices after a SD card is used at least once Status in linux package in Ubuntu: New Bug description: It was observed that after a SD card is used, the computer can have a kernel BUG or kernel panic after a partition from removable media is unmounted. Steps to reproduce: 1) Insert a SD card; 2) Mount the SD card; 3) Unmount the SD card; 4) Eject the SD card; 5) Try mount or unmount partitions from removable media. With panics, there are no saved messages, as syslog get corrupt. But when a BUG happens, the following appears: May 5 19:53:06 Lenovo-ideapad-310-14ISK kernel: [ 302.156578] BUG: unable to handle page fault for address: 8ec9aa20 The paste with the full BUG can be found at: https://paste.ubuntu.com/p/rtShbPjDrn/ This causes problems consistently with 5.4.0-29-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1824 F pulseaudio CasperMD5CheckResult: skip Date: Tue May 5 19:57:35 2020 HibernationDevice: RESUME=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc InstallationDate: Installed on 2017-06-13 (1056 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1
