[Kernel-packages] [Bug 1920106] Re: [Dell Vostro 14 5401] Eye strain on using ubuntu but not windows
Your LCD has two detailed modes: 60Hz and 48Hz. Please check that you're in a 60Hz mode and not 48Hz. -- 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/1920106 Title: [Dell Vostro 14 5401] Eye strain on using ubuntu but not windows Status in linux package in Ubuntu: Incomplete Bug description: I am not sure if the bug is with intel drivers or with font rendering or with xorg but I am facing eye strain on ubuntu(and other distributions as well, and other desktop environments too) but not on windows. Although I'm not sure, if I had to guess I would say bug is in intel drivers. The issue exists when I switch to wayland as well. I have tried tweaking hinting and aliasing settings of fonts using gnome- tweaks(or equivalent in other DEs) but to no effect. Maybe something is wrong with colors on linux so I copied my ICC profile from windows over to linux and applied it but that didn't work either. I just want a fix for my problem as it prevents me from using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 11:38:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09ea] InstallationDate: Installed on 2021-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 14 5401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=18819299-a0e3-4e05-83b0-9d0f57b4c653 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0C54N1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd12/18/2020:br1.5:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn0C54N1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920106/+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 1920874] Re: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1920874 Title: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+ Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] Memory card removal event can not be reflected via uevent on some card readers Ex. Realtek card readers 0bda:0328 and 0bda:0158. Thus the file browser still see the ghost disk even it's already removed. [Fix] Found the commit 6540fbf6b643 in 5.9.0-rc3 introduce this regression. Fix it by making sure the partition scan will never be skipped for each vfs_open until the partition scan is really done [Test] Verified on the Realtek card reader 0bda:0328 on Dell Precision 7820 and the external Realtek usb interface card reader 0bda:0158. Insert the SD card in the card reader $ udevadm monitor Remove the SD card and check the udevadm monitor output KERNEL[188.377042] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.383261] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) KERNEL[188.390887] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.396012] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) The remove event should be observed from the output messages. On the affected card reader, only change event would be observed. [Where problem could occur] These kind of card readers doesn't send remove event of scsi_disk and scsi_device like others so they only depend on the block subsystem to detect the media change and relect the removal event by partition scan. The behavior related to media removal is changed after 5.9.0-rc3. The remove event is not able to be correcly reflected since then, the device node of the media will remain there until next card insertion. == Original Bug Description == Ubuntu version: 20.10 Kernel: 5.10.0-1013-oem Card reader: Realtek Card Reader (0bda:0328 and 0bda:0158) Summary === After upgrading to kernel 5.9.0-rc3 or later, the device node for the partitions on the memory cards will not disappear after removing the memory cards. This is confusing to the user level applications like File Browser since the partition label will remain there for a long time. Steps to reproduce == 1. Upgrade to kernel later than 5.9.0-rc3 2. Plug the external card reader and insert the formatted memory card 3. Verify if the memory card mounted and visible on File Browser 4. Remove the memory card from the card reader 5. Verify if the mounted memory card removed from the File Browser Expected results The mounted memory card identifier should be disappear after remove the memory card Actual results == The partition label of the memory card exists for a long time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dev1443 F pulseaudio /dev/snd/controlC0: dev1443 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_UX434IQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=ac0e9628-3402-4892-84ab-a1dfb21be15a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.190 Tags: groovy Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434IQ_UX434IQ.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434IQ
[Kernel-packages] [Bug 1920106] Re: [Dell Vostro 14 5401] Eye strain on using ubuntu but not windows
Yes I have tried both 60Hz and 48Hz refresh rates. Here's and askubuntu thread I had made where I listed lots of other things I tried: https://askubuntu.com/questions/1320941/eye-strain-on- kubuntu-but-not-on-windows -- 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/1920106 Title: [Dell Vostro 14 5401] Eye strain on using ubuntu but not windows Status in linux package in Ubuntu: Incomplete Bug description: I am not sure if the bug is with intel drivers or with font rendering or with xorg but I am facing eye strain on ubuntu(and other distributions as well, and other desktop environments too) but not on windows. Although I'm not sure, if I had to guess I would say bug is in intel drivers. The issue exists when I switch to wayland as well. I have tried tweaking hinting and aliasing settings of fonts using gnome- tweaks(or equivalent in other DEs) but to no effect. Maybe something is wrong with colors on linux so I copied my ICC profile from windows over to linux and applied it but that didn't work either. I just want a fix for my problem as it prevents me from using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 11:38:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09ea] InstallationDate: Installed on 2021-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 14 5401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=18819299-a0e3-4e05-83b0-9d0f57b4c653 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0C54N1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd12/18/2020:br1.5:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn0C54N1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920106/+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 1920106] Re: [Dell Vostro 14 5401] Eye strain on using ubuntu but not windows
We will need to wait for you to find a definite cause/description of the problem before we can do anything about it. This bug will close automatically if no further comments are added after 60 days. ** Package changed: linux (Ubuntu) => ubuntu -- 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/1920106 Title: [Dell Vostro 14 5401] Eye strain on using ubuntu but not windows Status in Ubuntu: Incomplete Bug description: I am not sure if the bug is with intel drivers or with font rendering or with xorg but I am facing eye strain on ubuntu(and other distributions as well, and other desktop environments too) but not on windows. Although I'm not sure, if I had to guess I would say bug is in intel drivers. The issue exists when I switch to wayland as well. I have tried tweaking hinting and aliasing settings of fonts using gnome- tweaks(or equivalent in other DEs) but to no effect. Maybe something is wrong with colors on linux so I copied my ICC profile from windows over to linux and applied it but that didn't work either. I just want a fix for my problem as it prevents me from using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 19 11:38:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09ea] InstallationDate: Installed on 2021-03-19 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 14 5401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=18819299-a0e3-4e05-83b0-9d0f57b4c653 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0C54N1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd12/18/2020:br1.5:svnDellInc.:pnVostro145401:pvr:rvnDellInc.:rn0C54N1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14 5401 dmi.product.sku: 09EA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1920106/+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 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Status: New => Triaged -- 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/1920030 Title: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Triaged Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Triaged Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Triaged Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] The Mute/Mic-mute LEDs are not work when muting audio-output/microphone on HP 850/840/440 G8 laptops. [Fix] Add three realtek quirks for them. [Test] After applying the quirks, the LEDs are functioned on HP 850/840/440 G8 laptops. [Where problems could occur] If HP ships the different system boards design with the same subsystem IDs of audio codec which are using different GPIO pins (different layout), then the quirks will not work (LEDs will not function when muting audio-output or microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920030/+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 1920995] Re: selftests: bpf verifier fails after sanitize_ptr_alu fixes
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- 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/1920995 Title: selftests: bpf verifier fails after sanitize_ptr_alu fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Bug description: [Impact] bpf selftests will fail after applying fixes from 5.8.0-48 and 5.4.0-70. [Fix] Apply selftests fixes and bpf verifier simplification and hardening. [Test Plan] Ran the verifier test and other tests for the latest BPF fixes. [Potential regression] BPF programs that worked before may stop working or, worse, programs that should not be allowed may start working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920995/+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 1916823] Re: Touchpad / keyboard don't work (randomly) after reboot on HP systems
Already in oem-5.10 762374d755b8f3aa4503c900b0f62d7528b37950 -- 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/1916823 Title: Touchpad / keyboard don't work (randomly) after reboot on HP systems Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On some HP laptops (e.g. HP ZBook Fury 15/17 G7, HP EliteBook 850 G7, HP ENVY x360 Convertible 15-cp0xxx), the touchpad / keyboard will probably be disabled after reboot because the hp-wmi reports the system is a tablet system but it's not a tablet system. After libinput received "SW_TABLET_MODE", then it will disable the keyboard and touchpad. [Test case] Test 200 times reboot with: 1. 5.10.0-1013-oem kernel: - the SW_TABLET_MODE was detected at 72 round and the keyboard / touchpad not work. 2. 5.10.0-1013-oem kernel + 67fbe02a5cebc3c653610f12e3c0424e58450153: - the SW_TABLET_MODE is not be detected within 200 times reboot. [Fix] Cherry-pick commit 67fbe02a5cebc3c653610f12e3c0424e58450153. It turns the tablet mode detection to off as default and could be enabled by module parameter "enable_tablet_mode_sw". [Regression potential] It will break tablet detection on all HP laptops but user can enable it back by adding module parameter. If without this patch then a lot of HP new laptops (with newer HP BIOS) will get the keyboard/touchpad not work after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1916823/+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 1916823] Re: Touchpad / keyboard don't work (randomly) after reboot on HP systems
** Tags added: oem-priority originate-from-1910370 stella ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => Fix Committed -- 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/1916823 Title: Touchpad / keyboard don't work (randomly) after reboot on HP systems Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On some HP laptops (e.g. HP ZBook Fury 15/17 G7, HP EliteBook 850 G7, HP ENVY x360 Convertible 15-cp0xxx), the touchpad / keyboard will probably be disabled after reboot because the hp-wmi reports the system is a tablet system but it's not a tablet system. After libinput received "SW_TABLET_MODE", then it will disable the keyboard and touchpad. [Test case] Test 200 times reboot with: 1. 5.10.0-1013-oem kernel: - the SW_TABLET_MODE was detected at 72 round and the keyboard / touchpad not work. 2. 5.10.0-1013-oem kernel + 67fbe02a5cebc3c653610f12e3c0424e58450153: - the SW_TABLET_MODE is not be detected within 200 times reboot. [Fix] Cherry-pick commit 67fbe02a5cebc3c653610f12e3c0424e58450153. It turns the tablet mode detection to off as default and could be enabled by module parameter "enable_tablet_mode_sw". [Regression potential] It will break tablet detection on all HP laptops but user can enable it back by adding module parameter. If without this patch then a lot of HP new laptops (with newer HP BIOS) will get the keyboard/touchpad not work after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1916823/+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 1882213] Re: cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang
Closing this as it's not reproduceable. Please open a new ticket if you run into the problem again. ** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => Invalid ** Changed in: linux-raspi (Ubuntu Groovy) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1882213 Title: cp file from external HDD to NFS on Pi 3B causes ubuntu 19.10 and 20.04 kernel to hang Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Eoan: Won't Fix Status in linux-raspi source package in Focal: Invalid Status in linux-raspi source package in Groovy: Invalid Bug description: Copying a large file using cp on my Raspberry Pi 3B (not 3B+) from an externally-powered USB hard disk (Seagate Expansion 2TB) to an NFS- mounted filesystem across Ethernet causes the kernel of releases 19.10 and 20.04 to hang/freeze. This happens every time the copy is attempted, although the exact duration from the start of the copy to the hang varies from a few seconds to a couple of minutes. The kernel does not recover even after long waits (30mins+), and a power reset (pulling the plug) is required. (Although I admit I haven't tried yet simply disconnecting the USB cable of the HDD during a hang. Update: I've now tried that - the system doesn't recover after pulling the USB cable out.) Likewise, messages are erratic and I suspect are only symptoms, notably watchdog BUG soft lockup messages and RCU stall messages on different CPU cores for different processes/threads. There are no hardware messages that I've seen recorded in log files (or appearing on the console) matching the incidents. When a hang happen, network connectivity is lost - ssh sessions fail, and the file copy stops (even when the cp is run on the console). Pings to the system from other hosts on the same Ethernet LAN (and switch) fail with destination host unreachable. Although I have had a swapfile configured on the SD card, the hangs continue to happen doing the cp after "swapoff -a". I've also tried playing with taskset affinities and snappiness to no obvious effect - the hangs still keep happening. Copying from the external HDD to the SD card is successful, as is copying from the SD card to the NFS. Raspbian 4.19.0-8 (armmp-lpae) does not have this problem; it successfully copies the file from HDD to NFS across Ethernet without stalling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1011-raspi 5.4.0-1011.11 ProcVersionSignature: Ubuntu 5.4.0-1011.11-raspi 5.4.34 Uname: Linux 5.4.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Jun 5 07:37:44 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: Upgraded to focal on 2020-05-21 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1882213/+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 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
Is this still an issue with the latest 5.4 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+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 1862760] Re: Unreliable 802.11ac connection on our raspi images
Somewhat related: LP: #1908951 -- 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/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in linux-firmware source package in Bionic: New Status in linux-firmware-raspi2 source package in Bionic: New Status in linux-raspi2-5.3 source package in Bionic: New Status in netplan.io source package in Bionic: New Status in linux-firmware source package in Eoan: Won't Fix Status in linux-firmware-raspi2 source package in Eoan: Won't Fix Status in linux-raspi2-5.3 source package in Eoan: Won't Fix Status in netplan.io source package in Eoan: Won't Fix Status in linux-firmware source package in Focal: New Status in linux-firmware-raspi2 source package in Focal: Triaged Status in linux-raspi source package in Focal: New Status in netplan.io source package in Focal: New Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+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 1921066] [NEW] thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels
You have been subscribed to a public bug: I am running 20.04.1 LTS on a Thinkpad X1 Yoga 3rd Gen. After recent routine kernel updates, touching the screen with the stylus freezes the whole operating system. It is not associated with a single application or package (I guess it is the kernel package, see below). I am running the default ubuntu desktop environment. I recently switched from fedora 33 on this same machine, and this problem occurred with it too. I "solved" it by simply loading an earlier kernel, and trying each updated kernel version until the problem did not occur. The problem occurs with the following ubuntu kernels: 5.8.0-45-generic 5.8.0-48-generic It does *not* occur with 5.8.0-44-generic Please advise what other debugging info I can supply. I am sorry I did not take note of the kernel versions that did or did not experience the problem in fedora, although I note that fedora 33 also seems to be using the same 5.8 series. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels https://bugs.launchpad.net/bugs/1921066 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1921066] Re: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels
*** This bug is a duplicate of bug 1919342 *** https://bugs.launchpad.net/bugs/1919342 ** Package changed: ubuntu => linux (Ubuntu) ** Tags added: 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/1921066 Title: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels Status in linux package in Ubuntu: New Bug description: I am running 20.04.1 LTS on a Thinkpad X1 Yoga 3rd Gen. After recent routine kernel updates, touching the screen with the stylus freezes the whole operating system. It is not associated with a single application or package (I guess it is the kernel package, see below). I am running the default ubuntu desktop environment. I recently switched from fedora 33 on this same machine, and this problem occurred with it too. I "solved" it by simply loading an earlier kernel, and trying each updated kernel version until the problem did not occur. The problem occurs with the following ubuntu kernels: 5.8.0-45-generic 5.8.0-48-generic It does *not* occur with 5.8.0-44-generic Please advise what other debugging info I can supply. I am sorry I did not take note of the kernel versions that did or did not experience the problem in fedora, although I note that fedora 33 also seems to be using the same 5.8 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921066/+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 1921066] Re: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels
*** This bug is a duplicate of bug 1919342 *** https://bugs.launchpad.net/bugs/1919342 Should be the duplicate of #1920785 -- 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/1921066 Title: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels Status in linux package in Ubuntu: New Bug description: I am running 20.04.1 LTS on a Thinkpad X1 Yoga 3rd Gen. After recent routine kernel updates, touching the screen with the stylus freezes the whole operating system. It is not associated with a single application or package (I guess it is the kernel package, see below). I am running the default ubuntu desktop environment. I recently switched from fedora 33 on this same machine, and this problem occurred with it too. I "solved" it by simply loading an earlier kernel, and trying each updated kernel version until the problem did not occur. The problem occurs with the following ubuntu kernels: 5.8.0-45-generic 5.8.0-48-generic It does *not* occur with 5.8.0-44-generic Please advise what other debugging info I can supply. I am sorry I did not take note of the kernel versions that did or did not experience the problem in fedora, although I note that fedora 33 also seems to be using the same 5.8 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921066/+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 1920995] Re: selftests: bpf verifier fails after sanitize_ptr_alu fixes
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1920995 Title: selftests: bpf verifier fails after sanitize_ptr_alu fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] bpf selftests will fail after applying fixes from 5.8.0-48 and 5.4.0-70. [Fix] Apply selftests fixes and bpf verifier simplification and hardening. [Test Plan] Ran the verifier test and other tests for the latest BPF fixes. [Potential regression] BPF programs that worked before may stop working or, worse, programs that should not be allowed may start working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920995/+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 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45
This is not yet fixed in 5.8.0-48. -- 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/1919342 Title: Stylus and touchscreen not working in kernel 5.8.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After an update from 16th March 2021, the stylus for Acer Spin 5 stopped working and wasn't charging. Returning to version 5.8.0-43 fixed the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 16:12:45 2021 InstallationDate: Installed on 2020-12-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919342/+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 1921066] Re: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels
*** This bug is a duplicate of bug 1919342 *** https://bugs.launchpad.net/bugs/1919342 ** This bug has been marked a duplicate of bug 1919342 Stylus and touchscreen not working in kernel 5.8.0-45 -- 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/1921066 Title: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels Status in linux package in Ubuntu: New Bug description: I am running 20.04.1 LTS on a Thinkpad X1 Yoga 3rd Gen. After recent routine kernel updates, touching the screen with the stylus freezes the whole operating system. It is not associated with a single application or package (I guess it is the kernel package, see below). I am running the default ubuntu desktop environment. I recently switched from fedora 33 on this same machine, and this problem occurred with it too. I "solved" it by simply loading an earlier kernel, and trying each updated kernel version until the problem did not occur. The problem occurs with the following ubuntu kernels: 5.8.0-45-generic 5.8.0-48-generic It does *not* occur with 5.8.0-44-generic Please advise what other debugging info I can supply. I am sorry I did not take note of the kernel versions that did or did not experience the problem in fedora, although I note that fedora 33 also seems to be using the same 5.8 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921066/+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 1921104] [NEW] net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
You have been subscribed to a public bug: x ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192185 severity-high targetmilestone-inin2004 -- net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 https://bugs.launchpad.net/bugs/1921104 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
Is this bug fixed in 5.4.0-70, which is available 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107&id=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1921104] [NEW] net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
Public bug reported: x ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-192185 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-192185 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- 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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921104/+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 1921104] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-24 07:23 EDT--- Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. -- 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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921104/+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 1921104] net/mlx5e: Add missing capability check for uplink follow
--- Comment (attachment only) From heinz-werner_se...@de.ibm.com 2021-03-24 07:21 EDT--- ** Attachment added: "net/mlx5e: Add missing capability check for uplink follow" https://bugs.launchpad.net/bugs/1921104/+attachment/5480455/+files/0001-Backport-net-mlx5e-Add-missing-capability-check-for-.patch -- 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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921104/+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 1921104] Re: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04
The patch/commit is as '9c9be85f6b59' in hirsute since Ubuntu-5.11.0-11.12. Hence marking the hirsute entry as Fix Released. The patch applies cleanly to focal master-next. A test kernel is currently build here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1921104 So updating the focal entry to Triaged. Need to check if the patch also applies to groovy's 5.8. ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Frank Heimes (fheimes) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Status: New => Triaged ** Description changed: - x + Expose firmware indication that it supports setting eswitch uplink state + to follow (follow the physical link). Condition setting the eswitch + uplink admin-state with this capability bit. Older FW may not support + the uplink state setting. + + Available fix with kernel 5.11. + https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d + + Now required for Ubuntu 20.04 via backport patch. ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Frank Heimes (fheimes) Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Released -- 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/1921104 Title: net/mlx5e: Add missing capability check for uplink follow for Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Status in linux source package in Groovy: New Status in linux source package in Hirsute: Fix Released Bug description: Expose firmware indication that it supports setting eswitch uplink state to follow (follow the physical link). Condition setting the eswitch uplink admin-state with this capability bit. Older FW may not support the uplink state setting. Available fix with kernel 5.11. https://github.com/torvalds/linux/commit/9c9be85f6b59d80efe4705109c0396df18d4e11d Now required for Ubuntu 20.04 via backport patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1921104/+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 1919123] Re: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep
** Changed in: linux (Ubuntu Focal) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => In Progress -- 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/1919123 Title: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] On some platforms, the EC doesn't support the register reading sequence for sentelic[1], and then make the EC can't respond commands for a while when probing. It leads to the keyboard is non-responsive for around 10 seconds while waking up from s2idle. [ 44.304488] i8042: [9804] d4 -> i8042 (command) [ 44.304634] i8042: [9804] f3 -> i8042 (parameter) [ 44.304787] i8042: [9804] fa <- i8042 (interrupt, 1, 12) [ 44.304855] i8042: [9804] d4 -> i8042 (command) [ 44.304938] i8042: [9804] 66 -> i8042 (parameter) [ 44.337698] i8042: [9813] d4 -> i8042 (command) [ 44.905695] i8042: [9942] 88 -> i8042 (parameter) [ 45.497478] i8042: [10102] d4 -> i8042 (command) [ 46.098041] i8042: [10253] f3 -> i8042 (parameter) [ 46.098070] i8042: [10253] fe <- i8042 (interrupt, 1, 12) [ 46.718154] i8042: [10386] d4 -> i8042 (command) [ 47.309915] i8042: [10386] f4 -> i8042 (parameter) [ 47.918961] i8042: [10556] d4 -> i8042 (command) [ 48.402624] i8042: [10556] f6 -> i8042 (parameter) [Fix] A DMI quirk to mark this platform doesn't have aux device could avoid those commands to be sent. And the system could still using i2c interface to communicate with the touchpad. https://lkml.org/lkml/2021/3/15/126 [Test] Verified on Dell Precision 5550 [Where problem could occur] The quirk only affects the listed platform, there is no regression could occur. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919123/+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 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45
Some details not pointed out in the original post: On my Lenovo Yoga C740, the touchscreen briefly works after booting, but will cease to work immediately after the stylus is moved into the proximity of the screen. -- 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/1919342 Title: Stylus and touchscreen not working in kernel 5.8.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After an update from 16th March 2021, the stylus for Acer Spin 5 stopped working and wasn't charging. Returning to version 5.8.0-43 fixed the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 16:12:45 2021 InstallationDate: Installed on 2020-12-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919342/+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 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
** Tags added: aws ** Tags added: sru-20210222 -- 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/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 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: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+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 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
The fix was sent to the kernel teams mailing list: https://lists.ubuntu.com/archives/kernel-team/2021-March/thread.html#118449 ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-power-systems Status: Confirmed => In Progress -- 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/1920784 Title: qemu-system-ppc64le fails with kvm acceleration Status in QEMU: Invalid Status in The Ubuntu-power-systems project: In Progress Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Bug description: (Suspected glibc issue!) qemu-system-ppc64(le) fails when invoked with kvm acceleration with error "illegal instruction" > qemu-system-ppc64(le) -M pseries,accel=kvm Illegal instruction (core dumped) In dmesg: Facility 'SCV' unavailable (12), exception at 0x7624f8134c0c, MSR=9280f033 Version-Release number of selected component (if applicable): qemu 5.2.0 Linux kernel 5.11 glibc 2.33 all latest updates as of submitting the bug report How reproducible: Always Steps to Reproduce: 1. Run qemu with kvm acceleration Actual results: Illegal instruction Expected results: Normal VM execution Additional info: The machine is a Raptor Talos II Lite with a Sforza V1 8-core, but was also observed on a Raptor Blackbird with the same processor. This was also observed on Fedora 34 beta, which uses glibc 2.33 Also tested on ArchPOWER (unofficial port of Arch Linux for ppc64le) with glibc 2.33 Fedora 33 and Ubuntu 20.10, both using glibc 2.32 do not have this issue, and downgrading the Linux kernel from 5.11 to 5.4 LTS on ArchPOWER solved the problem. Kernel 5.9 and 5.10 have the same issue when combined with glibc2.33 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qemu-system 1:5.2+dfsg-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' ApportVersion: 2.20.11-0ubuntu60 Architecture: ppc64el CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Mar 22 14:48:39 2021 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha ppc64el (20210321) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND ProcKernelCmdLine: root=UUID=f3d03315-0944-4a02-9c87-09c00eba9fa1 ro ProcLoadAvg: 1.20 0.73 0.46 1/1054 6071 ProcSwaps: Filename TypeSizeUsed Priority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.11.0-11-generic (buildd@bos02-ppc64el-002) (gcc (Ubuntu 10.2.1-20ubuntu1) 10.2.1 20210220, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #12-Ubuntu SMP Mon Mar 1 19:26:20 UTC 2021 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 acpidump: cpu_cores: Number of cores present = 8 cpu_coreson: Number of cores online = 8 cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+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 1920995] Re: selftests: bpf verifier fails after sanitize_ptr_alu fixes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1920995 Title: selftests: bpf verifier fails after sanitize_ptr_alu fixes Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Bug description: [Impact] bpf selftests will fail after applying fixes from 5.8.0-48 and 5.4.0-70. [Fix] Apply selftests fixes and bpf verifier simplification and hardening. [Test Plan] Ran the verifier test and other tests for the latest BPF fixes. [Potential regression] BPF programs that worked before may stop working or, worse, programs that should not be allowed may start working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920995/+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 1921137] [NEW] mount.ocfs2 causes kernel BUG at lib/string.c:1149!
Public bug reported: the ocfs2-tools autopkgtests for hirsute recently started failing, and a local test run shows this kernel bug occurring during the test: [ 100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E [ 108.864491] detected buffer overflow in strlen [ 108.869193] [ cut here ] [ 108.869196] kernel BUG at lib/string.c:1149! [ 108.869962] invalid opcode: [#1] SMP PTI [ 108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 5.11.0-11-generic #12-Ubuntu [ 108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 108.873701] RIP: 0010:fortify_panic+0x13/0x15 [ 108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.882165] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.883474] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.887163] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.888626] CS: 0010 DS: ES: CR0: 80050033 [ 108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 [ 108.890823] Call Trace: [ 108.891279] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] [ 108.892603] ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2] [ 108.893484] ? pointer+0x185/0x4d0 [ 108.894079] ocfs2_fill_super+0x15d/0x7a0 [ocfs2] [ 108.894965] mount_bdev+0x18d/0x1c0 [ 108.895570] ? ocfs2_remount+0x450/0x450 [ocfs2] [ 108.896518] ocfs2_mount+0x15/0x20 [ocfs2] [ 108.897293] legacy_get_tree+0x2b/0x50 [ 108.897939] vfs_get_tree+0x2a/0xc0 [ 108.898542] do_new_mount+0x14b/0x1a0 [ 108.899175] path_mount+0x1d4/0x4e0 [ 108.899789] __x64_sys_mount+0x108/0x140 [ 108.900465] do_syscall_64+0x38/0x90 [ 108.901129] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 108.902376] RIP: 0033:0x7f8441109bce [ 108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48 [ 108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 00a5 [ 108.907610] RAX: ffda RBX: RCX: 7f8441109bce [ 108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 55eec2b8f060 [ 108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 7fff92a4bd00 [ 108.912443] R10: R11: 0246 R12: 7fff92a4e390 [ 108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: [ 108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover virtio_blk i2c_piix4 pata_acpi floppy [ 108.925313] ---[ end trace 72e4f69b08b1a89a ]--- [ 108.927136] RIP: 0010:fortify_panic+0x13/0x15 [ 108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.934468] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.935659] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.936933] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.938141] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.939458] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.940898] CS: 0010 DS: ES: CR0: 80050033 [ 108.942104] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 For full logs see the autopkgtest results: https://autopkgtest.ubuntu.com/packages/ocfs2-tools To see the dmesg kernel BUG output requires running the autopkgtest locally with the --shell-fail command. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: hirsute ** Description changed: the
[Kernel-packages] [Bug 1921137] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1921137 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- 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/1921137 Title: mount.ocfs2 causes kernel BUG at lib/string.c:1149! Status in linux package in Ubuntu: Incomplete Bug description: the ocfs2-tools autopkgtests for hirsute recently started failing, and a local test run shows this kernel bug occurring during the test: [ 100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E [ 108.864491] detected buffer overflow in strlen [ 108.869193] [ cut here ] [ 108.869196] kernel BUG at lib/string.c:1149! [ 108.869962] invalid opcode: [#1] SMP PTI [ 108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 5.11.0-11-generic #12-Ubuntu [ 108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 108.873701] RIP: 0010:fortify_panic+0x13/0x15 [ 108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.882165] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.883474] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.887163] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.888626] CS: 0010 DS: ES: CR0: 80050033 [ 108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 [ 108.890823] Call Trace: [ 108.891279] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] [ 108.892603] ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2] [ 108.893484] ? pointer+0x185/0x4d0 [ 108.894079] ocfs2_fill_super+0x15d/0x7a0 [ocfs2] [ 108.894965] mount_bdev+0x18d/0x1c0 [ 108.895570] ? ocfs2_remount+0x450/0x450 [ocfs2] [ 108.896518] ocfs2_mount+0x15/0x20 [ocfs2] [ 108.897293] legacy_get_tree+0x2b/0x50 [ 108.897939] vfs_get_tree+0x2a/0xc0 [ 108.898542] do_new_mount+0x14b/0x1a0 [ 108.899175] path_mount+0x1d4/0x4e0 [ 108.899789] __x64_sys_mount+0x108/0x140 [ 108.900465] do_syscall_64+0x38/0x90 [ 108.901129] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 108.902376] RIP: 0033:0x7f8441109bce [ 108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48 [ 108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 00a5 [ 108.907610] RAX: ffda RBX: RCX: 7f8441109bce [ 108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 55eec2b8f060 [ 108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 7fff92a4bd00 [ 108.912443] R10: R11: 0246 R12: 7fff92a4e390 [ 108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: [ 108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover virtio_blk i2c_piix4 pata_acpi floppy [ 108.925313] ---[ end trace 72e4f69b08b1a89a ]--- [ 108.927136] RIP: 0010:fortify_panic+0x13/0x15 [ 108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.932308] RSP: 0018:a9cf81
[Kernel-packages] [Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** Also affects: glibc (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: qemu (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Frank Heimes (fheimes) Status: In Progress -- 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/1920784 Title: qemu-system-ppc64le fails with kvm acceleration Status in QEMU: Invalid Status in The Ubuntu-power-systems project: In Progress Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in glibc source package in Hirsute: Invalid Status in linux source package in Hirsute: In Progress Status in qemu source package in Hirsute: Invalid Bug description: (Suspected glibc issue!) qemu-system-ppc64(le) fails when invoked with kvm acceleration with error "illegal instruction" > qemu-system-ppc64(le) -M pseries,accel=kvm Illegal instruction (core dumped) In dmesg: Facility 'SCV' unavailable (12), exception at 0x7624f8134c0c, MSR=9280f033 Version-Release number of selected component (if applicable): qemu 5.2.0 Linux kernel 5.11 glibc 2.33 all latest updates as of submitting the bug report How reproducible: Always Steps to Reproduce: 1. Run qemu with kvm acceleration Actual results: Illegal instruction Expected results: Normal VM execution Additional info: The machine is a Raptor Talos II Lite with a Sforza V1 8-core, but was also observed on a Raptor Blackbird with the same processor. This was also observed on Fedora 34 beta, which uses glibc 2.33 Also tested on ArchPOWER (unofficial port of Arch Linux for ppc64le) with glibc 2.33 Fedora 33 and Ubuntu 20.10, both using glibc 2.32 do not have this issue, and downgrading the Linux kernel from 5.11 to 5.4 LTS on ArchPOWER solved the problem. Kernel 5.9 and 5.10 have the same issue when combined with glibc2.33 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qemu-system 1:5.2+dfsg-6ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic ppc64le .sys.firmware.opal.msglog: Error: [Errno 13] Permission denied: '/sys/firmware/opal/msglog' ApportVersion: 2.20.11-0ubuntu60 Architecture: ppc64el CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Mar 22 14:48:39 2021 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha ppc64el (20210321) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND ProcKernelCmdLine: root=UUID=f3d03315-0944-4a02-9c87-09c00eba9fa1 ro ProcLoadAvg: 1.20 0.73 0.46 1/1054 6071 ProcSwaps: Filename TypeSizeUsed Priority /swap.img file 8388544 0 -2 ProcVersion: Linux version 5.11.0-11-generic (buildd@bos02-ppc64el-002) (gcc (Ubuntu 10.2.1-20ubuntu1) 10.2.1 20210220, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #12-Ubuntu SMP Mon Mar 1 19:26:20 UTC 2021 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 acpidump: cpu_cores: Number of cores present = 8 cpu_coreson: Number of cores online = 8 cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+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 1921140] [NEW] Tegra "mmc0: Timeout waiting for hardware interrupt"
Public bug reported: On the NVIDIA (Tegra) Jetson AGX Xavier device running hirsute with any v5.11 kernel (5.11.0-13.14) the system intermittently gets the following "mmc0: Timeout" and then hangs. This generally occurs within 24 hours of uptime: [25610.386873] mmc0: Timeout waiting for hardware interrupt. [25610.392426] mmc0: sdhci: SDHCI REGISTER DUMP === [25610.399095] mmc0: sdhci: Sys addr: 0x | Version: 0x0505 [25610.405635] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x [25610.412184] mmc0: sdhci: Argument: 0x | Trn mode: 0x0013 [25610.418725] mmc0: sdhci: Present: 0x01fb02f6 | Host ctl: 0x0031 [25610.425252] mmc0: sdhci: Power: 0x0001 | Blk gap: 0x [25610.431896] mmc0: sdhci: Wake-up: 0x | Clock:0x000f [25610.438441] mmc0: sdhci: Timeout: 0x000e | Int stat: 0x [25610.444993] mmc0: sdhci: Int enab: 0x03ff000b | Sig enab: 0x03fc000b [25610.451533] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x [25610.458074] mmc0: sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18002f73 [25610.464717] mmc0: sdhci: Cmd: 0x083a | Max curr: 0x [25610.471268] mmc0: sdhci: Resp[0]: 0x0900 | Resp[1]: 0x04806288 [25610.477811] mmc0: sdhci: Resp[2]: 0x314a8000 | Resp[3]: 0x0240 [25610.484361] mmc0: sdhci: Host ctl2: 0x308b [25610.489132] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0xeec00200 [25610.496365] mmc0: sdhci: The error and hang can be induced on demand by running this command line twice: $ sudo cat /sys/kernel/debug/mmc0/mmc0:0001/ext_csd The first access of 'ext_csd' yields "mmc0: ADMA error: 0x0200" and a dump, then the second access yields the timeout and hang. All of that can be reproduced in mainline as well. ** Affects: linux (Ubuntu) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Description changed: - On the NVIDIA Jetson AGX Xavier device running hirsute with any v5.11 - kernel (5.11.0-13.14) the system intermittently gets the following + On the NVIDIA (Tegra) Jetson AGX Xavier device running hirsute with any + v5.11 kernel (5.11.0-13.14) the system intermittently gets the following "mmc0: Timeout" and then hangs. This generally occurs within 24 hours of uptime: [25610.386873] mmc0: Timeout waiting for hardware interrupt. [25610.392426] mmc0: sdhci: SDHCI REGISTER DUMP === [25610.399095] mmc0: sdhci: Sys addr: 0x | Version: 0x0505 [25610.405635] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x [25610.412184] mmc0: sdhci: Argument: 0x | Trn mode: 0x0013 [25610.418725] mmc0: sdhci: Present: 0x01fb02f6 | Host ctl: 0x0031 [25610.425252] mmc0: sdhci: Power: 0x0001 | Blk gap: 0x [25610.431896] mmc0: sdhci: Wake-up: 0x | Clock:0x000f [25610.438441] mmc0: sdhci: Timeout: 0x000e | Int stat: 0x [25610.444993] mmc0: sdhci: Int enab: 0x03ff000b | Sig enab: 0x03fc000b [25610.451533] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x [25610.458074] mmc0: sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18002f73 [25610.464717] mmc0: sdhci: Cmd: 0x083a | Max curr: 0x [25610.471268] mmc0: sdhci: Resp[0]: 0x0900 | Resp[1]: 0x04806288 [25610.477811] mmc0: sdhci: Resp[2]: 0x314a8000 | Resp[3]: 0x0240 [25610.484361] mmc0: sdhci: Host ctl2: 0x308b [25610.489132] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0xeec00200 [25610.496365] mmc0: sdhci: The error and hang can be induced on demand by running this command line twice: $ sudo cat /sys/kernel/debug/mmc0/mmc0:0001/ext_csd The first access of 'ext_csd' yields "mmc0: ADMA error: 0x0200" and a dump, then the second access yields the timeout and hang. All of that can be reproduced in mainline 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/1921140 Title: Tegra "mmc0: Timeout waiting for hardware interrupt" Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: On the NVIDIA (Tegra) Jetson AGX Xavier device running hirsute with any v5.11 kernel (5.11.0-13.14) the system intermittently gets the following "mmc0: Timeout" and then hangs. This generally occurs within 24 hours of uptime: [25610.386873] mmc0: Timeout waiting for hardware interrupt. [25610.392426] mmc0: sdhci: SDH
[Kernel-packages] [Bug 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops
** Also affects: linux (Ubuntu Hirsute) Importance: Medium Status: Triaged ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Groovy) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Triaged => Fix Committed -- 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/1920030 Title: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] The Mute/Mic-mute LEDs are not work when muting audio-output/microphone on HP 850/840/440 G8 laptops. [Fix] Add three realtek quirks for them. [Test] After applying the quirks, the LEDs are functioned on HP 850/840/440 G8 laptops. [Where problems could occur] If HP ships the different system boards design with the same subsystem IDs of audio codec which are using different GPIO pins (different layout), then the quirks will not work (LEDs will not function when muting audio-output or microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920030/+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 1921140] Re: Tegra "mmc0: Timeout waiting for hardware interrupt"
This patch from NVIDIA fixes the forced-replication method of inducing the timeout and appears to likewise fix the intermittent occurrence of it. The patch will be heading upstream in short order, per the author. ** Patch added: "0001-UBUNTU-SAUCE-mmc-host-Add-required-callbacks-to-set-.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921140/+attachment/5480526/+files/0001-UBUNTU-SAUCE-mmc-host-Add-required-callbacks-to-set-.patch -- 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/1921140 Title: Tegra "mmc0: Timeout waiting for hardware interrupt" Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: On the NVIDIA (Tegra) Jetson AGX Xavier device running hirsute with any v5.11 kernel (5.11.0-13.14) the system intermittently gets the following "mmc0: Timeout" and then hangs. This generally occurs within 24 hours of uptime: [25610.386873] mmc0: Timeout waiting for hardware interrupt. [25610.392426] mmc0: sdhci: SDHCI REGISTER DUMP === [25610.399095] mmc0: sdhci: Sys addr: 0x | Version: 0x0505 [25610.405635] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x [25610.412184] mmc0: sdhci: Argument: 0x | Trn mode: 0x0013 [25610.418725] mmc0: sdhci: Present: 0x01fb02f6 | Host ctl: 0x0031 [25610.425252] mmc0: sdhci: Power: 0x0001 | Blk gap: 0x [25610.431896] mmc0: sdhci: Wake-up: 0x | Clock:0x000f [25610.438441] mmc0: sdhci: Timeout: 0x000e | Int stat: 0x [25610.444993] mmc0: sdhci: Int enab: 0x03ff000b | Sig enab: 0x03fc000b [25610.451533] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x [25610.458074] mmc0: sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18002f73 [25610.464717] mmc0: sdhci: Cmd: 0x083a | Max curr: 0x [25610.471268] mmc0: sdhci: Resp[0]: 0x0900 | Resp[1]: 0x04806288 [25610.477811] mmc0: sdhci: Resp[2]: 0x314a8000 | Resp[3]: 0x0240 [25610.484361] mmc0: sdhci: Host ctl2: 0x308b [25610.489132] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0xeec00200 [25610.496365] mmc0: sdhci: The error and hang can be induced on demand by running this command line twice: $ sudo cat /sys/kernel/debug/mmc0/mmc0:0001/ext_csd The first access of 'ext_csd' yields "mmc0: ADMA error: 0x0200" and a dump, then the second access yields the timeout and hang. All of that can be reproduced in mainline as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921140/+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 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
I am experiencing the same issue. I am using a very old machine: it's an Acer T180 with a NVIDIA GT710 graphics card (driver nvidia-460) and an AMD Athlon 5600+. The process causing the crash is /usr/lib/gdm3/gdm-x-session. I will try to switch to Nouveau and Wayland and report back. -- 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/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-05-04 (906 days ago) InstallationMedia: Ubuntu 16.0
[Kernel-packages] [Bug 1921140] Re: Tegra "mmc0: Timeout waiting for hardware interrupt"
** Tags added: patch -- 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/1921140 Title: Tegra "mmc0: Timeout waiting for hardware interrupt" Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: On the NVIDIA (Tegra) Jetson AGX Xavier device running hirsute with any v5.11 kernel (5.11.0-13.14) the system intermittently gets the following "mmc0: Timeout" and then hangs. This generally occurs within 24 hours of uptime: [25610.386873] mmc0: Timeout waiting for hardware interrupt. [25610.392426] mmc0: sdhci: SDHCI REGISTER DUMP === [25610.399095] mmc0: sdhci: Sys addr: 0x | Version: 0x0505 [25610.405635] mmc0: sdhci: Blk size: 0x7200 | Blk cnt: 0x [25610.412184] mmc0: sdhci: Argument: 0x | Trn mode: 0x0013 [25610.418725] mmc0: sdhci: Present: 0x01fb02f6 | Host ctl: 0x0031 [25610.425252] mmc0: sdhci: Power: 0x0001 | Blk gap: 0x [25610.431896] mmc0: sdhci: Wake-up: 0x | Clock:0x000f [25610.438441] mmc0: sdhci: Timeout: 0x000e | Int stat: 0x [25610.444993] mmc0: sdhci: Int enab: 0x03ff000b | Sig enab: 0x03fc000b [25610.451533] mmc0: sdhci: ACmd stat: 0x | Slot int: 0x [25610.458074] mmc0: sdhci: Caps: 0x3f6cd08c | Caps_1: 0x18002f73 [25610.464717] mmc0: sdhci: Cmd: 0x083a | Max curr: 0x [25610.471268] mmc0: sdhci: Resp[0]: 0x0900 | Resp[1]: 0x04806288 [25610.477811] mmc0: sdhci: Resp[2]: 0x314a8000 | Resp[3]: 0x0240 [25610.484361] mmc0: sdhci: Host ctl2: 0x308b [25610.489132] mmc0: sdhci: ADMA Err: 0x | ADMA Ptr: 0xeec00200 [25610.496365] mmc0: sdhci: The error and hang can be induced on demand by running this command line twice: $ sudo cat /sys/kernel/debug/mmc0/mmc0:0001/ext_csd The first access of 'ext_csd' yields "mmc0: ADMA error: 0x0200" and a dump, then the second access yields the timeout and hang. All of that can be reproduced in mainline as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921140/+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 1901563] Re: [i915] Kernel crashed in vma_create when running Xorg
I have successfully switched to Nouveau and Wayland. I have not had any problem so far (it's been 30 minutes since I switched - maybe it's too soon to tell). I will test my current setup and report back in a week. -- 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/1901563 Title: [i915] Kernel crashed in vma_create when running Xorg Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I've just upgraded to 20.10. After logging in and using PyCharm for a while, the system froze, and I had to do a REISUB. It turned out to be a kernel panic and seems related to Xorg and the i915 driver. This has now happened multiple times, and not all crashes have happened while using PyCharm. I've tried using the ppa:canonical-kernel-team/ppa to install a new kernel (5.8.0-26-generic) but that did not help. [ 1620.425014] general protection fault, probably for non-canonical address 0xe296718293aa0a0a: [#1] SMP PTI [ 1620.425017] CPU: 2 PID: 1749 Comm: Xorg Tainted: GW 5.8.0-26-generic #27-Ubuntu [ 1620.425018] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.2.1 02/21/2018 [ 1620.425023] RIP: 0010:kmem_cache_alloc+0x7e/0x230 [ 1620.425025] Code: 95 01 00 00 4d 8b 07 65 49 8b 50 08 65 4c 03 05 a0 59 33 4d 4d 8b 20 4d 85 e4 0f 84 81 01 00 00 41 8b 47 20 49 8b 3f 4c 01 e0 <48> 8b 18 48 89 c1 49 33 9f 70 01 00 00 4c 89 e0 48 0f c9 48 31 cb [ 1620.425026] RSP: 0018:b1f6c19e79b0 EFLAGS: 00010286 [ 1620.425028] RAX: e296718293aa0a0a RBX: RCX: 0002 [ 1620.425029] RDX: 7d5e RSI: 0dc0 RDI: 441461604a80 [ 1620.425031] RBP: b1f6c19e79e0 R08: d1f6bfc84a80 R09: [ 1620.425032] R10: R11: 8de1eca2f6c2 R12: e296718293aa08b2 [ 1620.425033] R13: 0dc0 R14: 8de2488364c0 R15: 8de2488364c0 [ 1620.425034] FS: 7fe9c3b52a40() GS:8de25e68() knlGS: [ 1620.425035] CS: 0010 DS: ES: CR0: 80050033 [ 1620.425037] CR2: 7f6c1433c000 CR3: 000488622001 CR4: 003606e0 [ 1620.425038] Call Trace: [ 1620.425087] ? vma_create+0x30/0x460 [i915] [ 1620.425122] vma_create+0x30/0x460 [i915] [ 1620.425124] ? mutex_lock+0x13/0x40 [ 1620.425157] i915_vma_instance+0xd2/0xe0 [i915] [ 1620.425187] eb_lookup_vma+0xd7/0x1c0 [i915] [ 1620.425217] eb_lookup_vmas+0x79/0x200 [i915] [ 1620.425247] eb_relocate+0x18/0x1b0 [i915] [ 1620.425275] i915_gem_do_execbuffer+0x265/0x8d0 [i915] [ 1620.425278] ? enqueue_task_fair+0x159/0x590 [ 1620.425282] ? __radix_tree_replace+0x4a/0xe0 [ 1620.425285] ? _cond_resched+0x1a/0x50 [ 1620.425287] ? kmem_cache_alloc_trace+0x168/0x240 [ 1620.425290] ? __kmalloc_node+0x201/0x300 [ 1620.425320] i915_gem_execbuffer2_ioctl+0x237/0x4a0 [i915] [ 1620.425348] ? intel_engines_add_sysfs+0x150/0x150 [i915] [ 1620.425350] ? radix_tree_lookup+0xd/0x10 [ 1620.425379] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425395] drm_ioctl_kernel+0xae/0xf0 [drm] [ 1620.425406] drm_ioctl+0x238/0x3d0 [drm] [ 1620.425434] ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915] [ 1620.425437] ? fput+0x13/0x15 [ 1620.425440] ? __sys_recvmsg+0x94/0xb0 [ 1620.425442] ksys_ioctl+0x8e/0xc0 [ 1620.425444] __x64_sys_ioctl+0x1a/0x20 [ 1620.425447] do_syscall_64+0x49/0xc0 [ 1620.425449] entry_SYSCALL_64_after_hwframe+0x44/0xa9 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 26 16:33:28 2020 DistUpgraded: 2020-10-23 13:15:10,351 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-05-04 (906 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell
[Kernel-packages] [Bug 1921156] [NEW] cannot upgrade kernel on ssd booting raspberry pi 3b
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 linux-image-5.4.0-1029-raspi: Installed: 5.4.0-1029.32 Candidate: 5.4.0-1029.32 Version table: *** 5.4.0-1029.32 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main armhf Packages 500 http://ports.ubuntu.com/ubuntu-ports focal-security/main armhf Packages 100 /var/lib/dpkg/status I gather it's something to do with /boot partition having to be vfat and you cannot do symlinks there. But I don't know what to do about it. There was some post about editing /etc/kernel-img.conf but all that seemed to do was to kick the problem down the road to where a different link couldn't be made. This is on an ssd-booting system with mounts /dev/sda2 on / type ext4 (rw,noatime) /dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro) and the altered kernel-img.conf file is, currently: do_symlinks = no do_bootloader = no link_in_boot = no Here's the aptage: sudo apt update && sudo apt upgrade -y Hit:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Hit:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Hit:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Hit:5 https://deb.nodesource.com/node_15.x focal InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up initramfs-tools (0.136ubuntu6.4) ... update-initramfs: deferring update (trigger activated) Setting up linux-firmware (1.187.10) ... ln: failed to create hard link '/boot/initrd.img-5.4.0-1029-raspi.dpkg-bak' => '/boot/initrd.img-5.4.0-1029-raspi': Operation not permitted update-initramfs: Generating /boot/initrd.img-5.4.0-1029-raspi Using DTB: bcm2710-rpi-3-b.dtb Installing /lib/firmware/5.4.0-1029-raspi/device-tree/bcm2710-rpi-3-b.dtb into /boot/dtbs/5.4.0-1029-raspi/./bcm2710-rpi-3-b.dtb Taking backup of bcm2710-rpi-3-b.dtb. Installing new bcm2710-rpi-3-b.dtb. ln: failed to create symbolic link '/boot/dtb-5.4.0-1029-raspi': Operation not permitted run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Setting up linux-image-5.4.0-1029-raspi (5.4.0-1029.32) ... Processing triggers for initramfs-tools (0.136ubuntu6.4) ... ln: failed to create hard link '/boot/initrd.img-5.4.0-1029-raspi.dpkg-bak' => '/boot/initrd.img-5.4.0-1029-raspi': Oper ation not permitted update-initramfs: Generating /boot/initrd.img-5.4.0-1029-raspi Using DTB: bcm2710-rpi-3-b.dtb Installing /lib/firmware/5.4.0-1029-raspi/device-tree/bcm2710-rpi-3-b.dtb into /boot/dtbs/5.4.0-1029-raspi/./bcm2710-rpi -3-b.dtb Taking backup of bcm2710-rpi-3-b.dtb. Installing new bcm2710-rpi-3-b.dtb. ln: failed to create symbolic link '/boot/dtb-5.4.0-1029-raspi': Operation not permitted run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Processing triggers for linux-image-5.4.0-1029-raspi (5.4.0-1029.32) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-1029-raspi Using DTB: bcm2710-rpi-3-b.dtb Installing /lib/firmware/5.4.0-1029-raspi/device-tree/bcm2710-rpi-3-b.dtb into /boot/dtbs/5.4.0-1029-raspi/./bcm2710-rpi -3-b.dtb Taking backup of bcm2710-rpi-3-b.dtb. Installing new bcm2710-rpi-3-b.dtb. ln: failed to create symbolic link '/boot/dtb-5.4.0-1029-raspi': Operation not permitted run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-5.4.0-1029-raspi (--configure): installed linux-image-5.4.0-1029-raspi package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware initramfs-tools linux-image-5.4.0-1029-raspi E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1029-raspi 5.4.0-1029.32 ProcVersionSignature: Ubuntu 5.4.0-1028.31-raspi 5.4.78 Uname: Linux 5.4.0-1028-raspi armv7l ApportVersion: 2.20.11-0ubuntu27.16 Architecture: armhf CasperMD5CheckRes
[Kernel-packages] [Bug 1919492] Re: Hirsute update: v5.11.7 upstream stable release
Julian, you can see which upstream kernel it is based on with: /proc/version /proc/version_signature -- 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/1919492 Title: Hirsute update: v5.11.7 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.7 upstream stable release from git://git.kernel.org/ Linux 5.11.7 KVM: arm64: Fix nVHE hyp panic host context restore mm/page_alloc.c: refactor initialization of struct page for holes in memory layout mm/memcg: rename mem_cgroup_split_huge_fixup to split_page_memcg and add nr_pages argument mm/memcg: set memcg when splitting page mm/madvise: replace ptrace attach requirement for process_madvise mm/userfaultfd: fix memory corruption due to writeprotect mm/highmem.c: fix zero_user_segments() with start > end KVM: arm64: Fix exclusive limit for IPA size KVM: arm64: Reject VM creation when the default IPA size is unsupported KVM: arm64: nvhe: Save the SPE context early KVM: arm64: Avoid corrupting vCPU context register in guest exit KVM: arm64: Fix range alignment when walking page tables KVM: arm64: Ensure I-cache isolation between vcpus of a same VM KVM: kvmclock: Fix vCPUs > 64 can't be online/hotpluged KVM: x86: Ensure deadline timer has truly expired before posting its IRQ x86/entry: Fix entry/exit mismatch on failed fast 32-bit syscalls x86/sev-es: Use __copy_from_user_inatomic() x86/sev-es: Correctly track IRQ states in runtime #VC handler x86/sev-es: Check regs->sp is trusted before adjusting #VC IST stack x86/sev-es: Introduce ip_within_syscall_gap() helper x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2 kasan: fix KASAN_STACK dependency for HW_TAGS kasan, mm: fix crash with HW_TAGS and DEBUG_PAGEALLOC binfmt_misc: fix possible deadlock in bm_register_write powerpc: Fix missing declaration of [en/dis]able_kernel_vsx() powerpc: Fix inverted SET_FULL_REGS bitop powerpc/64s: Fix instruction encoding for lis in ppc_function_entry() efi: stub: omit SetVirtualAddressMap() if marked unsupported in RT_PROP table sched: Simplify set_affinity_pending refcounts sched: Fix affine_move_task() self-concurrency sched: Optimize migration_cpu_stop() sched: Simplify migration_cpu_stop() sched: Collate affine_move_task() stoppers sched/membarrier: fix missing local execution of ipi_sync_rq_state() sched: Fix migration_cpu_stop() requeueing linux/compiler-clang.h: define HAVE_BUILTIN_BSWAP* zram: fix broken page writeback zram: fix return value on writeback_store include/linux/sched/mm.h: use rcu_dereference in in_vfork() stop_machine: mark helpers __always_inline memblock: fix section mismatch warning seqlock,lockdep: Fix seqcount_latch_init() powerpc/64s/exception: Clean up a missed SRR specifier hrtimer: Update softirq_expires_next correctly after __hrtimer_get_next_event() perf/x86/intel: Set PERF_ATTACH_SCHED_CB for large PEBS and LBR perf/core: Flush PMU internal buffers for per-CPU events mptcp: fix memory accounting on allocation error mptcp: put subflow sock on connect error net: expand textsearch ts_state to fit skb_seq_state perf/arm_dmc620_pmu: Fix error return code in dmc620_pmu_device_probe() drm/nouveau: fix dma syncing for loops (v2) io_uring: perform IOPOLL reaping if canceler is thread itself arm64: mm: use a 48-bit ID map when possible on 52-bit VA builds configfs: fix a use-after-free in __configfs_open_file nvme-fc: fix racing controller reset and create association drm/ttm: Fix TTM page pool accounting block: rsxx: fix error return code of rsxx_pci_probe() NFSv4.2: fix return value of _nfs4_get_security_label() NFS: Don't gratuitously clear the inode cache when lookup failed NFS: Don't revalidate the directory permissions on a lookup failure SUNRPC: Set memalloc_nofs_save() for sync tasks arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory cpufreq: qcom-hw: Fix return value check in qcom_cpufreq_hw_cpu_init() cpufreq: qcom-hw: fix dereferencing freed memory 'data' net: macb: Add default usrio config to default gem config powerpc/sstep: Fix VSX instruction emulation sh_eth: fix TRSCER mask for R7S72100 net: phy: ti: take into account all possible interrupt sources mlxsw: spectrum_router: Ignore routes using a deleted ne
[Kernel-packages] [Bug 1920670] Re: [Dell Precision 5540] Screen glitches temporarily
Hello, Thanks for your suggestion, I updated my kernel version to the latest(5.11.8) , and have done some stress test(I began download from a lot of places, turn on some movies on full hd format) and can say that tis type of error(screen glitching) happens fewer, so I can say tat this not solve my problem but helped decrese numbers of errors. Maybe there is another solution to solve this problem once and for all. -- 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/1920670 Title: [Dell Precision 5540] Screen glitches temporarily Status in linux package in Ubuntu: Incomplete Bug description: Time by time screen glitches for some seconds. This problem happens independent of PC load (with both Intel and NVIDIA graphic cards). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 21 16:41:39 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0906] Subsystem: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:] InstallationDate: Installed on 2021-03-21 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Precision 5540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic root=UUID=d9d861fa-ee39-4c30-a652-d4c285927a01 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0WWHJ2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd12/14/2020:br1.9:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn0WWHJ2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5540 dmi.product.sku: 0906 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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 N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920670/+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 1916290] Re: Enforce CONFIG_DRM_BOCHS=m
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1916290 Title: Enforce CONFIG_DRM_BOCHS=m Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-aws source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: In Progress Bug description: [Impact] In LP:#1872863 we started to build and ship the bochs-drm.ko driver again, however this config wasn't enforced and because of that derivatives didn't inherit. We should enforce CONFIG_DRM_BOCHS=m to avoid problem in the future and to let the derivatives update their configuration to include it or not. [Testcase] This should be a no-op for bionic:linux causing no differences for the current kernel. For derivatives, it will prompt the kernel engineer to update the config or to annotate it. [Regression Potential] Since it's no-op, there's no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916290/+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 1905975] Re: kernel: Enable CONFIG_BPF_LSM on Ubuntu
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Groovy) Importance: Undecided => Medium -- 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/1905975 Title: kernel: Enable CONFIG_BPF_LSM on Ubuntu Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux source package in Groovy: Fix Committed Status in linux-aws source package in Groovy: In Progress Status in linux source package in Hirsute: Fix Released Status in linux-aws source package in Hirsute: New Bug description: == Impact == Enabling CONFIG_BPF_LSM in the KConfig of Ubuntu Kernels, allowing users to use BPF LSM programs. == Background == The BPF LSM was merged into the Linux kernel 5.7 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=641cd7b06c911c5935c34f24850ea18690649917 https://outflux.net/blog/archives/2020/09/21/security-things-in- linux-v5-7 It allows users to implement MAC and Audit Policies using BPF programs. As a follow-up from the interest generated by the LSM on BPF/Linux conferences and on request from users, we’d like to request the enabling of CONFIG_BPF_LSM on Ubuntu starting with H. The LSM won't be added to the list of active LSMs by default (in CONFIG_LSM or lsm= on the boot parameters) yet, as it adds an indirect function call overhead by registering an empty LSM hook for all hooks. However enabling it in the kernel config will support users who wish to use BPF LSM programs without needing to replace their kernel image. The LSM can be made "active" by default when our work on getting rid of this overhead is merged in the kernel: https://lore.kernel.org/bpf/20200820164753.3256899-1-jackm...@chromium.org == Regression Potential == None. The LSM is not active by default, so it does not have any performance or functional regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905975/+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 1921211] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1921211 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- 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/1921211 Title: Taking a memory dump of user mode process on Xenial hosts causes bugcheck/kernel panic and core dump Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Bug description: [Impact] We have some Ubuntu 16.04 hosts (in Hyper-V) being used for testing some Ubuntu 20.04 container. As part of the testing we were attempting to take a memory dump of a container running SQL Server with Ubuntu 20.04 on the Ubuntu 16.04 host we started seeing kernel panic and core dump. It started happening after a specific Xenial kernel update on the host. 4.4.0-204-generic - Systems that are crashing 4.4.0-201-generic - Systems that are able to capture dump Note from the developer indicates following logging showing up. Now the following is output right after I attempt to start the dump. (gdb, attach ###, generate-core-file /var/opt/mssql/log/rdorr.delme.core) [Fri Mar 19 20:01:38 2021] systemd-journald[581]: Successfully sent stream file descriptor to service manager. [Fri Mar 19 20:01:41 2021] cni0: port 9(vethdec5d2b7) entered forwarding state [Fri Mar 19 20:02:42 2021] systemd-journald[581]: Successfully sent stream file descriptor to service manager. [Fri Mar 19 20:03:04 2021] [ cut here ] [Fri Mar 19 20:03:04 2021] kernel BUG at /build/linux-qlAbvR/linux-4.4.0/mm/memory.c:3214! [Fri Mar 19 20:03:04 2021] invalid opcode: [#1] SMP [Fri Mar 19 20:03:04 2021] Modules linked in: veth vxlan ip6_udp_tunnel udp_tunnel xt_statistic xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs overlay nls_utf8 isofs crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds serio_raw i2c_piix4 hv_balloon hyperv_fb 8250_fintek joydev mac_hid autofs4 hid_generic hv_utils hid_hyperv ptp hv_netvsc hid hv_storvsc pps_core [Fri Mar 19 20:03:04 2021] hyperv_keyboard scsi_transport_fc psmouse pata_acpi hv_vmbus floppy fjes [Fri Mar 19 20:03:04 2021] CPU: 1 PID: 24869 Comm: gdb Tainted: G W 4.4.0-204-generic #236-Ubuntu [Fri Mar 19 20:03:04 2021] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 05/18/2018 [Fri Mar 19 20:03:04 2021] task: 880db9229c80 ti: 880d93b9c000 task.ti: 880d93b9c000 [Fri Mar 19 20:03:04 2021] RIP: 0010:[] [] handle_mm_fault+0x13de/0x1b80 [Fri Mar 19 20:03:04 2021] RSP: 0018:880d93b9fc28 EFLAGS: 00010246 [Fri Mar 19 20:03:04 2021] RAX: 0100 RBX: RCX: 0120 [Fri Mar 19 20:03:04 2021] RDX: 880ea635f3e8 RSI: 3000 RDI: [Fri Mar 19 20:03:04 2021] RBP: 880d93b9fce8 R08: 3ff32179a120 R09: 007d [Fri Mar 19 20:03:04 2021] R10: 880003e8 R11: 03e8 R12: 8800ea672708 [Fri Mar 19 20:03:04 2021] R13: R14: 00010247d000 R15: 8800f27fe400 [Fri Mar 19 20:03:04 2021] FS: 7fdc26061600() GS:88102564() knlGS: [Fri Mar 19 20:03:04 2021] CS: 0010 DS: ES: CR0: 80050033 [Fri Mar 19 20:03:04 2021] CR2: 55e3a0011290 CR3: 000d93ba4000 CR4: 00160670 [Fri Mar 19 20:03:04 2021] Stack: [Fri Mar 19 20:03:04 2021] 81082929 fffd 81082252 880d93b9fca8 [Fri Mar 19 20:03:04 2021] 811c7bca 8800f27fe400 00010247d000 880e74a88090 [Fri Mar 19 20:03:04 2021] 3a98d7f0 880e0001 880003e8 0017 [Fri Mar 19 20:03:04 2021] Call Trace: [Fri Mar 19 20:03:04 2021] [] ? mm_access+0x79/0xa0 [Fri Mar 19 20:03:04 2021] [] ? mmput+0x12/0x130 [Fri Mar 19 20:03:04 2021] [] ? follow_page_pte+0x1ca/0x3d0 [Fri Mar 19 20:03:04 20
[Kernel-packages] [Bug 1921211] [NEW] Taking a memory dump of user mode process on Xenial hosts causes bugcheck/kernel panic and core dump
Public bug reported: [Impact] We have some Ubuntu 16.04 hosts (in Hyper-V) being used for testing some Ubuntu 20.04 container. As part of the testing we were attempting to take a memory dump of a container running SQL Server with Ubuntu 20.04 on the Ubuntu 16.04 host we started seeing kernel panic and core dump. It started happening after a specific Xenial kernel update on the host. 4.4.0-204-generic - Systems that are crashing 4.4.0-201-generic - Systems that are able to capture dump Note from the developer indicates following logging showing up. Now the following is output right after I attempt to start the dump. (gdb, attach ###, generate-core-file /var/opt/mssql/log/rdorr.delme.core) [Fri Mar 19 20:01:38 2021] systemd-journald[581]: Successfully sent stream file descriptor to service manager. [Fri Mar 19 20:01:41 2021] cni0: port 9(vethdec5d2b7) entered forwarding state [Fri Mar 19 20:02:42 2021] systemd-journald[581]: Successfully sent stream file descriptor to service manager. [Fri Mar 19 20:03:04 2021] [ cut here ] [Fri Mar 19 20:03:04 2021] kernel BUG at /build/linux-qlAbvR/linux-4.4.0/mm/memory.c:3214! [Fri Mar 19 20:03:04 2021] invalid opcode: [#1] SMP [Fri Mar 19 20:03:04 2021] Modules linked in: veth vxlan ip6_udp_tunnel udp_tunnel xt_statistic xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs overlay nls_utf8 isofs crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds serio_raw i2c_piix4 hv_balloon hyperv_fb 8250_fintek joydev mac_hid autofs4 hid_generic hv_utils hid_hyperv ptp hv_netvsc hid hv_storvsc pps_core [Fri Mar 19 20:03:04 2021] hyperv_keyboard scsi_transport_fc psmouse pata_acpi hv_vmbus floppy fjes [Fri Mar 19 20:03:04 2021] CPU: 1 PID: 24869 Comm: gdb Tainted: G W 4.4.0-204-generic #236-Ubuntu [Fri Mar 19 20:03:04 2021] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 05/18/2018 [Fri Mar 19 20:03:04 2021] task: 880db9229c80 ti: 880d93b9c000 task.ti: 880d93b9c000 [Fri Mar 19 20:03:04 2021] RIP: 0010:[] [] handle_mm_fault+0x13de/0x1b80 [Fri Mar 19 20:03:04 2021] RSP: 0018:880d93b9fc28 EFLAGS: 00010246 [Fri Mar 19 20:03:04 2021] RAX: 0100 RBX: RCX: 0120 [Fri Mar 19 20:03:04 2021] RDX: 880ea635f3e8 RSI: 3000 RDI: [Fri Mar 19 20:03:04 2021] RBP: 880d93b9fce8 R08: 3ff32179a120 R09: 007d [Fri Mar 19 20:03:04 2021] R10: 880003e8 R11: 03e8 R12: 8800ea672708 [Fri Mar 19 20:03:04 2021] R13: R14: 00010247d000 R15: 8800f27fe400 [Fri Mar 19 20:03:04 2021] FS: 7fdc26061600() GS:88102564() knlGS: [Fri Mar 19 20:03:04 2021] CS: 0010 DS: ES: CR0: 80050033 [Fri Mar 19 20:03:04 2021] CR2: 55e3a0011290 CR3: 000d93ba4000 CR4: 00160670 [Fri Mar 19 20:03:04 2021] Stack: [Fri Mar 19 20:03:04 2021] 81082929 fffd 81082252 880d93b9fca8 [Fri Mar 19 20:03:04 2021] 811c7bca 8800f27fe400 00010247d000 880e74a88090 [Fri Mar 19 20:03:04 2021] 3a98d7f0 880e0001 880003e8 0017 [Fri Mar 19 20:03:04 2021] Call Trace: [Fri Mar 19 20:03:04 2021] [] ? mm_access+0x79/0xa0 [Fri Mar 19 20:03:04 2021] [] ? mmput+0x12/0x130 [Fri Mar 19 20:03:04 2021] [] ? follow_page_pte+0x1ca/0x3d0 [Fri Mar 19 20:03:04 2021] [] ? follow_page_mask+0x214/0x3a0 [Fri Mar 19 20:03:04 2021] [] __get_user_pages+0x130/0x680 [Fri Mar 19 20:03:04 2021] [] ? path_openat+0x348/0x1360 [Fri Mar 19 20:03:04 2021] [] get_user_pages+0x34/0x40 [Fri Mar 19 20:03:04 2021] [] __access_remote_vm+0xe4/0x2d0 [Fri Mar 19 20:03:04 2021] [] ? alloc_pages_current+0x8c/0x110 [Fri Mar 19 20:03:04 2021] [] access_remote_vm+0x1f/0x30 [Fri Mar 19 20:03:04 2021] [] mem_rw.isra.16+0xfa/0x190 [Fri Mar 19 20:03:04 2021] [] mem_read+0x18/0x20 [Fri Mar 19 20:03:04 2021] [] __vfs_read+0x1b/0x40 [Fri Mar 19 20:03:04 2021] [] vfs_read+0x86/0x130 [Fri Mar 19 20:03:04 2021] [] SyS_pread64+0x95/0xb0 [Fri Mar 19 20:03:04 2021] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [Fri Mar 19 20:03:04 2021] Code: d4 ee ff ff 48 8b 7d 98 89 45 88 e8 2d c7 fd ff 8b 45 88 89 c3 e9 be ee ff ff 48 8b bd 70 ff ff ff e8 c7 cf 69 00 e9 ad ee ff ff <0f> 0b 4c 89 e7 4c 89 9d 70 ff ff ff e8 f1 c9 00 00 85 c0 4c 8b [Fri Mar 19 20:03:04 2021] RIP [] handle_mm_fault+0x13de/0x1b80 [Fri Mar 19 20:03:04 2021] RSP [Fri Mar 19 20:03:04 2021] ---[ end trace
[Kernel-packages] [Bug 1921211] Re: Taking a memory dump of user mode process on Xenial hosts causes bugcheck/kernel panic and core dump
** Description changed: [Impact] We have some Ubuntu 16.04 hosts (in Hyper-V) being used for testing some Ubuntu 20.04 container. As part of the testing we were attempting to take a memory dump of a container running SQL Server with Ubuntu 20.04 on the Ubuntu 16.04 host we started seeing kernel panic and core dump. It started happening after a specific Xenial kernel update on the host. 4.4.0-204-generic - Systems that are crashing 4.4.0-201-generic - Systems that are able to capture dump - Note from the developer indicates following logging showing up. Now the following is output right after I attempt to start the dump. (gdb, attach ###, generate-core-file /var/opt/mssql/log/rdorr.delme.core) [Fri Mar 19 20:01:38 2021] systemd-journald[581]: Successfully sent stream file descriptor to service manager. [Fri Mar 19 20:01:41 2021] cni0: port 9(vethdec5d2b7) entered forwarding state [Fri Mar 19 20:02:42 2021] systemd-journald[581]: Successfully sent stream file descriptor to service manager. [Fri Mar 19 20:03:04 2021] [ cut here ] [Fri Mar 19 20:03:04 2021] kernel BUG at /build/linux-qlAbvR/linux-4.4.0/mm/memory.c:3214! [Fri Mar 19 20:03:04 2021] invalid opcode: [#1] SMP [Fri Mar 19 20:03:04 2021] Modules linked in: veth vxlan ip6_udp_tunnel udp_tunnel xt_statistic xt_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6_tables xt_comment xt_mark xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables br_netfilter bridge stp llc aufs overlay nls_utf8 isofs crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds serio_raw i2c_piix4 hv_balloon hyperv_fb 8250_fintek joydev mac_hid autofs4 hid_generic hv_utils hid_hyperv ptp hv_netvsc hid hv_storvsc pps_core [Fri Mar 19 20:03:04 2021] hyperv_keyboard scsi_transport_fc psmouse pata_acpi hv_vmbus floppy fjes [Fri Mar 19 20:03:04 2021] CPU: 1 PID: 24869 Comm: gdb Tainted: G W 4.4.0-204-generic #236-Ubuntu [Fri Mar 19 20:03:04 2021] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 05/18/2018 [Fri Mar 19 20:03:04 2021] task: 880db9229c80 ti: 880d93b9c000 task.ti: 880d93b9c000 [Fri Mar 19 20:03:04 2021] RIP: 0010:[] [] handle_mm_fault+0x13de/0x1b80 [Fri Mar 19 20:03:04 2021] RSP: 0018:880d93b9fc28 EFLAGS: 00010246 [Fri Mar 19 20:03:04 2021] RAX: 0100 RBX: RCX: 0120 [Fri Mar 19 20:03:04 2021] RDX: 880ea635f3e8 RSI: 3000 RDI: [Fri Mar 19 20:03:04 2021] RBP: 880d93b9fce8 R08: 3ff32179a120 R09: 007d [Fri Mar 19 20:03:04 2021] R10: 880003e8 R11: 03e8 R12: 8800ea672708 [Fri Mar 19 20:03:04 2021] R13: R14: 00010247d000 R15: 8800f27fe400 [Fri Mar 19 20:03:04 2021] FS: 7fdc26061600() GS:88102564() knlGS: [Fri Mar 19 20:03:04 2021] CS: 0010 DS: ES: CR0: 80050033 [Fri Mar 19 20:03:04 2021] CR2: 55e3a0011290 CR3: 000d93ba4000 CR4: 00160670 [Fri Mar 19 20:03:04 2021] Stack: [Fri Mar 19 20:03:04 2021] 81082929 fffd 81082252 880d93b9fca8 [Fri Mar 19 20:03:04 2021] 811c7bca 8800f27fe400 00010247d000 880e74a88090 [Fri Mar 19 20:03:04 2021] 3a98d7f0 880e0001 880003e8 0017 [Fri Mar 19 20:03:04 2021] Call Trace: [Fri Mar 19 20:03:04 2021] [] ? mm_access+0x79/0xa0 [Fri Mar 19 20:03:04 2021] [] ? mmput+0x12/0x130 [Fri Mar 19 20:03:04 2021] [] ? follow_page_pte+0x1ca/0x3d0 [Fri Mar 19 20:03:04 2021] [] ? follow_page_mask+0x214/0x3a0 [Fri Mar 19 20:03:04 2021] [] __get_user_pages+0x130/0x680 [Fri Mar 19 20:03:04 2021] [] ? path_openat+0x348/0x1360 [Fri Mar 19 20:03:04 2021] [] get_user_pages+0x34/0x40 [Fri Mar 19 20:03:04 2021] [] __access_remote_vm+0xe4/0x2d0 [Fri Mar 19 20:03:04 2021] [] ? alloc_pages_current+0x8c/0x110 [Fri Mar 19 20:03:04 2021] [] access_remote_vm+0x1f/0x30 [Fri Mar 19 20:03:04 2021] [] mem_rw.isra.16+0xfa/0x190 [Fri Mar 19 20:03:04 2021] [] mem_read+0x18/0x20 [Fri Mar 19 20:03:04 2021] [] __vfs_read+0x1b/0x40 [Fri Mar 19 20:03:04 2021] [] vfs_read+0x86/0x130 [Fri Mar 19 20:03:04 2021] [] SyS_pread64+0x95/0xb0 [Fri Mar 19 20:03:04 2021] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [Fri Mar 19 20:03:04 2021] Code: d4 ee ff ff 48 8b 7d 98 89 45 88 e8 2d c7 fd ff 8b 45 88 89 c3 e9 be ee ff ff 48 8b bd 70 ff ff ff e8 c7 cf 69 00 e9 ad ee ff ff <0f> 0b 4c 89 e7 4c 89 9d 70 ff ff ff e8 f1 c9 00 00 85 c0 4c 8b [Fri Mar 19 20:03:04 202
[Kernel-packages] [Bug 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
Results: https://kernel.ubuntu.com/~mhcerri/lp1919154/ ** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+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 1920030] Re: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops
** Changed in: oem-priority Status: Triaged => Fix Committed -- 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/1920030 Title: Mute/Mic-mute LEDs are not work on HP 850/840/440 G8 Laptops Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: New Bug description: [Impact] The Mute/Mic-mute LEDs are not work when muting audio-output/microphone on HP 850/840/440 G8 laptops. [Fix] Add three realtek quirks for them. [Test] After applying the quirks, the LEDs are functioned on HP 850/840/440 G8 laptops. [Where problems could occur] If HP ships the different system boards design with the same subsystem IDs of audio codec which are using different GPIO pins (different layout), then the quirks will not work (LEDs will not function when muting audio-output or microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920030/+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 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45
> Some details not pointed out in the original post: On my Lenovo Yoga C740, > the > touchscreen briefly works after booting, but will cease to work immediately > after the > stylus is moved into the proximity of the screen. I can confirm that I see the same behaviour in my Dell lattitude 7200 2-in-1. Actually, the touchscreen works with my fingers for as long as I can try, but as soon as I put the stylus on it it completely stops working and only a reboot makes it work again (until I touch it with the stylus). I've attached the relevant section of /var/log/syslog in case that can help. Same problem under 5.8.0-45 and 5.8.0-48, works fine under 5.8.0-44. ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919342/+attachment/5480549/+files/log.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/1919342 Title: Stylus and touchscreen not working in kernel 5.8.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After an update from 16th March 2021, the stylus for Acer Spin 5 stopped working and wasn't charging. Returning to version 5.8.0-43 fixed the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 16:12:45 2021 InstallationDate: Installed on 2020-12-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919342/+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 1921066] Re: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels
*** This bug is a duplicate of bug 1919342 *** https://bugs.launchpad.net/bugs/1919342 Please advise which logs are appropriate. I can boot into one of the "bad" kernels and collect standard logs etc. while it is running but *before* I try touching the screen with the stylus. This would give standard info but not necessarily pinpoint the issue. What I would really like to know is this: if I replicate the problem (i.e. freeze the OS), will this write appropriate diagnostic info to some log file which is then still available after a hard reboot? -- 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/1921066 Title: thinkpad yoga X1 3rd gen stylus freezes OS 20.04 LTS certain kernels Status in linux package in Ubuntu: New Bug description: I am running 20.04.1 LTS on a Thinkpad X1 Yoga 3rd Gen. After recent routine kernel updates, touching the screen with the stylus freezes the whole operating system. It is not associated with a single application or package (I guess it is the kernel package, see below). I am running the default ubuntu desktop environment. I recently switched from fedora 33 on this same machine, and this problem occurred with it too. I "solved" it by simply loading an earlier kernel, and trying each updated kernel version until the problem did not occur. The problem occurs with the following ubuntu kernels: 5.8.0-45-generic 5.8.0-48-generic It does *not* occur with 5.8.0-44-generic Please advise what other debugging info I can supply. I am sorry I did not take note of the kernel versions that did or did not experience the problem in fedora, although I note that fedora 33 also seems to be using the same 5.8 series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921066/+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 1919342] Re: Stylus and touchscreen not working in kernel 5.8.0-45
I posted https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921066 yesterday which was marked as a duplicate of this one, which I agree with. Please advise which logs are appropriate. I can boot into one of the "bad" kernels and collect standard logs etc. while it is running but *before* I try touching the screen with the stylus. This would give standard info but not necessarily pinpoint the issue. What I would really like to know is this: if I replicate the problem (i.e. freeze the OS), will this write appropriate diagnostic info to some log file which is then still available after a hard reboot? -- 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/1919342 Title: Stylus and touchscreen not working in kernel 5.8.0-45 Status in linux package in Ubuntu: Confirmed Bug description: After an update from 16th March 2021, the stylus for Acer Spin 5 stopped working and wasn't charging. Returning to version 5.8.0-43 fixed the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.30 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 16 16:12:45 2021 InstallationDate: Installed on 2020-12-23 (82 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919342/+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 1918443] Re: package linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de s
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Package changed: ubuntu => linux (Ubuntu) ** Information type changed from Private Security to Public -- 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/1918443 Title: package linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 failed to install/upgrade: el subproceso instalado el script post- installation devolvió el código de salida de error 135 Status in linux package in Ubuntu: Confirmed Bug description: quiero iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Sun Mar 7 16:39:01 2021 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 135 InstallationDate: Installed on 2021-03-03 (6 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: linux-signed-hwe Title: package linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918443/+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 1918443] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1918443 Title: package linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 failed to install/upgrade: el subproceso instalado el script post- installation devolvió el código de salida de error 135 Status in linux package in Ubuntu: Confirmed Bug description: quiero iniciar ubuntu ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Sun Mar 7 16:39:01 2021 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 135 InstallationDate: Installed on 2021-03-03 (6 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: linux-signed-hwe Title: package linux-image-4.15.0-136-generic 4.15.0-136.140~16.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918443/+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 1920221] Re: Xenial update: v4.4.262 upstream stable release
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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/1920221
Title:
Xenial update: v4.4.262 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v4.4.262 upstream stable release
from git://git.kernel.org/
uapi: nfnetlink_cthelper.h: fix userspace compilation error
ath9k: fix transmitting to stations in dynamic SMPS mode
net: Fix gro aggregation for udp encaps with zero csum
can: skb: can_skb_set_owner(): fix ref counting if socket was closed before
setting skb ownership
can: flexcan: assert FRZ bit in flexcan_chip_freeze()
can: flexcan: enable RX FIFO after FRZ/HALT valid
netfilter: x_tables: gpf inside xt_find_revision()
cifs: return proper error code in statfs(2)
floppy: fix lock_fdc() signal handling
Revert "mm, slub: consider rest of partial list if acquire_slab() fails"
futex: Change locking rules
futex: Cure exit race
futex: fix dead code in attach_to_pi_owner()
net/mlx4_en: update moderation when config reset
net: lapbether: Remove netif_start_queue / netif_stop_queue
net: davicom: Fix regulator not turned off on failed probe
net: davicom: Fix regulator not turned off on driver removal
media: usbtv: Fix deadlock on suspend
mmc: mxs-mmc: Fix a resource leak in an error handling path in
'mxs_mmc_probe()'
mmc: mediatek: fix race condition between msdc_request_timeout and irq
powerpc/perf: Record counter overflow always if SAMPLE_IP is unset
PCI: xgene-msi: Fix race in installing chained irq handler
s390/smp: __smp_rescan_cpus() - move cpumask away from stack
scsi: libiscsi: Fix iscsi_prep_scsi_cmd_pdu() error handling
ALSA: hda/hdmi: Cancel pending works before suspend
ALSA: hda: Avoid spurious unsol event handling during S3/S4
ALSA: usb-audio: Fix "cannot get freq eq" errors on Dell AE515 sound bar
s390/dasd: fix hanging DASD driver unbind
mmc: core: Fix partition switch time for eMMC
scripts/recordmcount.{c,pl}: support -ffunction-sections .text.* section names
libertas: fix a potential NULL pointer dereference
Goodix Fingerprint device is not a modem
usb: gadget: f_uac2: always increase endpoint max_packet_size by one audio
slot
usb: renesas_usbhs: Clear PIPECFG for re-enabling pipe with other EPNUM
xhci: Improve detection of device initiated wake signal.
USB: serial: io_edgeport: fix memory leak in edge_startup
USB: serial: ch341: add new Product ID
USB: serial: cp210x: add ID for Acuity Brands nLight Air Adapter
USB: serial: cp210x: add some more GE USB IDs
usbip: fix stub_dev to check for stream socket
usbip: fix vhci_hcd to check for stream socket
usbip: fix stub_dev usbip_sockfd_store() races leading to gpf
staging: rtl8192u: fix ->ssid overflow in r8192_wx_set_scan()
staging: rtl8188eu: prevent ->ssid overflow in rtw_wx_set_scan()
staging: rtl8712: unterminated string leads to read overflow
staging: rtl8188eu: fix potential memory corruption in rtw_check_beacon_data()
staging: rtl8712: Fix possible buffer overflow in r8712_sitesurvey_cmd
staging: rtl8192e: Fix possible buffer overflow in _rtl92e_wx_set_scan
staging: comedi: addi_apci_1032: Fix endian problem for COS sample
staging: comedi: addi_apci_1500: Fix endian problem for command sample
staging: comedi: adv_pci1710: Fix endian problem for AI command data
staging: comedi: das6402: Fix endian problem for AI command data
staging: comedi: das800: Fix endian problem for AI command data
staging: comedi: dmm32at: Fix endian problem for AI command data
staging: comedi: me4000: Fix endian problem for AI command data
staging: comedi: pcl711: Fix endian problem for AI command data
staging: comedi: pcl818: Fix endian problem for AI command data
NFSv4.2: fix return value of _nfs4_get_security_label()
block: rsxx: fix error return code of rsxx_pci_probe()
alpha: add $(src)/ rather than $(obj)/ to make source file path
alpha: merge build rules of division routines
alpha: make short build log available for division routines
alpha: Package string routines together
alpha: move exports to actual definitions
alpha: get rid of tail-zeroing in __copy_user()
alpha: switch __copy_user() and __do_clean_user() to normal calling
conventions
powerpc/64s: Fix instruction encoding fo
[Kernel-packages] [Bug 1920218] Re: Xenial update: v4.4.261 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1920218 Title: Xenial update: v4.4.261 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v4.4.261 upstream stable release from git://git.kernel.org/ futex: fix irq self-deadlock and satisfy assertion futex: fix spin_lock() / spin_unlock_irq() imbalance ALSA: ctxfi: cthw20k2: fix mask on conf to allow 4 bits rsxx: Return -EFAULT if copy_to_user() fails dm table: fix iterate_devices based device capability checks platform/x86: acer-wmi: Add new force_caps module parameter PCI: Add function 1 DMA alias quirk for Marvell 9215 SATA controller Linux 4.4.261 UBUNTU: upstream stable to v4.4.261 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920218/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
No, this bug is not fixed in 5.4.0-70. xen guests do not start with this kernel version. It seems this version has only the patches from 5.4.0-69 and 5.4.0-70 and NOT 5.4.0-68, see https://launchpad.net/ubuntu/+source/linux/5.4.0-70.78 -- 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107&id=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
This patch seems to be part of 5.4.0-71 https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?h=Ubuntu-5.4.0-71.79&id=b6c0a7f33687639b59ce52882cf35e95e5f5454a I will test if available in proposed-repo. -- 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107&id=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1912828] Re: USB resets since upgrade to 20.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1912828 Title: USB resets since upgrade to 20.04 Status in linux package in Ubuntu: Expired Bug description: since upgrading from 18.04 to 20.04 i experience interruptions of my usb keyboard every few minutes. during these events either keys are ignored or get repeated until i press the same key again. in dmesg it is shown like this: [206129.443725] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206131.063578] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206132.719719] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206134.143584] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci [206135.923480] usb 2-1.4: reset full-speed USB device number 7 using ehci-pci i tried plugging it to different usb ports. it happens on any ports but i noticed it happens way more frequently on the ports on the backside of the PC than on the front side (they happen to be different usb busses). i also did upgrade the BIOS to the latest version, but that did not change the behavior at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twix 3831 F pulseaudio /dev/snd/pcmC0D0p: twix 3831 F...m pulseaudio /dev/snd/controlC2: twix 3831 F pulseaudio /dev/snd/controlC1: twix 3831 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Jan 22 18:56:19 2021 HibernationDevice: RESUME=UUID=fd4b40d6-dd20-49d8-a82f-36efaec3481b InstallationDate: Installed on 2016-06-26 (1671 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Studio XPS 8100 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-62-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-62-generic N/A linux-backports-modules-5.4.0-62-generic N/A linux-firmware1.187.7 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-01-05 (17 days ago) dmi.bios.date: 07/08/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0T568R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/08/2010:svnDellInc.:pnStudioXPS8100:pvr:rvnDellInc.:rn0T568R:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 8100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912828/+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 1911042] Re: Touchpad does not appear in xinput log neither in cat /proc/bus/input/devices
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1911042 Title: Touchpad does not appear in xinput log neither in cat /proc/bus/input/devices Status in linux package in Ubuntu: Expired Bug description: I use dual boot and in Windows, after I'd installed the lenovo touchpad driver, the touchpad works fine but in xubuntu no, it doesn't even appear in the list of devices. I searched and tried to use an older version of kernel but had no resuts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joao 1062 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 11 15:13:51 2021 InstallationDate: Installed on 2020-12-30 (12 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82DJ ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=da16de8b-acdd-4891-afba-c370b2ee66eb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 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 S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 82DJ dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911042/+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 1912094] Re: touchpad not showing up and not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1912094 Title: touchpad not showing up and not working Status in linux package in Ubuntu: Expired Bug description: Hi, touchpad does not seem to be recognised at all and thus does not work, can you please help, thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leo1595 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 17 13:16:20 2021 InstallationDate: Installed on 2020-12-14 (33 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=0a29a516-0bd9-45c7-ab20-165d3b5a1d0e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912094/+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 1898436] Re: [Toshiba SATELLITE C55-A-1M7] touchpad not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1898436 Title: [Toshiba SATELLITE C55-A-1M7] touchpad not working Status in linux package in Ubuntu: Expired Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=04f2 Product=b3b1 Version=5716 N: Name="TOSHIBA Web Camera - HD: TOSHIB" P: Phys=usb-:00:14.0-10/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/input/input7 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input5 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs
[Kernel-packages] [Bug 1905103] Re: Unrecoverable random freezes; Ubuntu 20.04; HP Spectre X360
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1905103 Title: Unrecoverable random freezes; Ubuntu 20.04; HP Spectre X360 Status in linux package in Ubuntu: Expired Bug description: The system freezes at apparently random times with no warning and no possibility to recover. The system becomes completely unresponsive and has to be hard reset. The mouse cursor does not move and no keyboard input works. In particular, Alt+SysRq+REISUB does not work (confirmed that it is activated and works in normal conditions). Neither does Ctrl+Alt+F2,F3,etc. If a youtube music is playing in the background I hear the audio get stuck in a short repeat loop (stutter) then stop after a while. The freezes have been happening for the past month or so at intervals of about 1-3 days, not long after I installed Ubuntu 20.04 as the first linux distro on this machine. Not sure if it all started after an update. No program seems to crash before the freeze happens, and I have not found any pattern of activity that can reliably trigger the freeze. It has happened while surfing the internet or just viewing files. The kernel logs nothing unusual before the freeze (please see the attached kern.log file; it contains multiple instances of the freeze: look for where the system boots without proper shut down beforehand). I have tried switching between the open-source and the proprietary video drivers. It didn't help. Also uninstalled xserver-xorg-video-intel with no result, so installed it back. Not sure what to try next. Very frustrating as the hard resets can damage important work and data on disks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-54-generic 5.4.0-54.60 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: farshad1494 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 15:11:20 2020 InstallationDate: Installed on 2020-10-10 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201007) MachineType: HP HP Spectre x360 Convertible 15-df1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=0536b924-b1a1-4ba7-bff4-04df7284b913 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-54-generic N/A linux-backports-modules-5.4.0-54-generic N/A linux-firmware1.187.4 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2020 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd06/01/2020:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df1xxx dmi.product.sku: 7UT64UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905103/+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 1912056] Re: [Toshiba Satellite P750] Touch Pad doesnt work after update to Ubuntu 18.04.5 LTS
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1912056 Title: [Toshiba Satellite P750] Touch Pad doesnt work after update to Ubuntu 18.04.5 LTS Status in linux package in Ubuntu: Expired Bug description: Touch pad of Laptop does not work after upate to version :Ubuntu 18.04.5 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-121-generic 4.15.0-121.123 ProcVersionSignature: Ubuntu 4.15.0-121.123-generic 4.15.18 Uname: Linux 4.15.0-121-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kiran 1553 F pulseaudio /dev/snd/controlC0: kiran 1553 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 19:13:19 2021 InstallationDate: Installed on 2017-11-04 (1168 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA Satellite P750 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-121-generic root=UUID=1a3e664e-3ef9-4a3a-99e2-e4733086ce66 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-121-generic N/A linux-backports-modules-4.15.0-121-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2020-10-24 (83 days ago) dmi.bios.date: 12/15/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.40 dmi.board.asset.tag: NULL dmi.board.name: PEQAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.40:bd12/15/2011:svnTOSHIBA:pnSatelliteP750:pvrPSAY3A-02T001:rvnTOSHIBA:rnPEQAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite P750 dmi.product.version: PSAY3A-02T001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912056/+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 1908847] Re: [Realtek ALC298] No sound from internal speakers
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1908847 Title: [Realtek ALC298] No sound from internal speakers Status in linux package in Ubuntu: Expired Bug description: I've tried several ways to solve this problem but still have a problem. 1) alsa-info http://alsa-project.org/db/?f=7ba6e11f4fa1cfad5518a32bfcaaba5f5aff5aff 2) RtHDDumpo I attached output file. I found 'write I2C' sequence in it. ( to enable MAX98390 ) -- I tried the test below 1) options snd-intel-dspcfg dsp_driver=1 and 3 : same results, no sound 2) options snd-hda-intel dmic_detect=0 and options snd-hda-intel models : same results, no sound -- I think need a patch to support max98390. Could you give me some advice ? -- additional information 1) versions Ubuntu 5.8.0-31.33-generic 5.8.17 Description: Ubuntu 20.10 Release: 20.10 2) lspci 00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01) Subsystem: LG Electronics, Inc. 11th Gen Core Processor Host Bridge/DRAM Registers [1854:0402] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. UHD Graphics [1854:0402] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Address: fee00018 Data: Masking: Pending: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV) IOVCap: Migration-, Interrupt Message Number: 000 IOVCtl: Enable- Migration- Interrupt- MSE- ARIHierarchy- IOVSta: Migration- Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function Dependency Link: 00 VF offset: 1, stride: 1, Device ID: 9a49 Supported Page Size: 0553, System Page Size: 0001 Region 0: Memory at 00401000 (64-bit, non-prefetchable) Region 2: Memory at 00402000 (64-bit, prefetchable) VF Migration: offset: , BIR: 0 Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a03] (rev 01) Subsystem: LG Electronics, Inc. Device [1854:0402] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Steppi
[Kernel-packages] [Bug 1908919] Re: Touchpad is not present in input devices
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1908919 Title: Touchpad is not present in input devices Status in linux package in Ubuntu: Expired Bug description: Laptop Model : HP Pavilion Gaming Laptop 15-ec1071nf Touchpad : HP Imagepad, supposedly a Synaptics touchpad (TBC) First appearance : Fresh Ubuntu 18.04 install, immediately upgraded to 20.04. Tested with both available kernels : ii linux-image-5.3.0-28-generic 5.3.0-28.30~18.04.1 amd64Signed kernel image generic ii linux-image-5.4.0-58-generic 5.4.0-58.64 amd64Signed kernel image generic See attached file. Bug summited with the help of https://wiki.ubuntu.com/DebuggingTouchpadDetection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rgo1450 F pulseaudio /dev/snd/controlC1: rgo1450 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 17:21:08 2020 InstallationDate: Installed on 2020-12-21 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: HP HP Pavilion Gaming Laptop 15-ec1xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=9265c5e1-5392-458a-8f41-967a63493630 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-12-21 (0 days ago) dmi.bios.date: 07/22/2020 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87B1 dmi.board.vendor: HP dmi.board.version: 31.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.11:bd07/22/2020:svnHP:pnHPPavilionGamingLaptop15-ec1xxx:pvr:rvnHP:rn87B1:rvr31.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec1xxx dmi.product.sku: 1X2T6EA#ABF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908919/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux Status: New => Incomplete -- 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/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: Incomplete Status in linux package in Ubuntu: Won't Fix Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Won't Fix Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0
Hello, yes, the fix commit was rebased due to some other urgent security fixes. Thanks for clarifying that. -- 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/1920660 Title: Missing Commit for 5.4-Kernel breaks xen Dom0 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Bug description: You commited "xen: Fix event channel callback via INTX/GSI" for kernel 5.4.0-67 for HWE 18.04 and 20.04. This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also Commit "xen: Fix XenStore initialisation for XS_LOCAL" See https://lkml.org/lkml/2021/1/28/1235 See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 Upstream: Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2 Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1 5.10: Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11) Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13) 5.4: Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93) Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95) Without this patch you cannot start guests (DomU) on this machine! Error message while creating DomU: libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to add device with path / libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add disk devices See: - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14 - https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107&id=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95 - http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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
