[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874010] Re: [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot in kernel 5.4, but 5.5.19 has no problem
I just wanted to update that updating the bios for my laptop (Dell XPS 13 9300) fixed the issue without needing a different kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874010 Title: [Ice Lake] 2-second black screen blips when using Chrome or gnome- screenshot in kernel 5.4, but 5.5.19 has no problem Status in linux package in Ubuntu: Confirmed Bug description: Hi, Im using a HP 14s dq laptop with intel 630 graphics. I've tried both the mode setting and xserver-xorg-video-intel drivers, both result in the same 2-second black screen blips. The happens frequently using chrome, and always when using the gnome screenshot utility. Also, during boot teh screen flickers between black screen and boot splash a lot. setting nomodeset as a grub parameter stops the flickering, but is not a feasible solution as brightness can no longer be set. kind regards, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 21 08:15:51 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-21-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-24-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:86c8] InstallationDate: Installed on 2020-04-16 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 14s-dq1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-25-generic root=UUID=54a7cc42-ac04-4466-b29f-16b1a7016ed0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2019 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C8 dmi.board.vendor: HP dmi.board.version: 56.31 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.09:bd12/20/2019:svnHP:pnHPLaptop14s-dq1xxx:pvr:rvnHP:rn86C8:rvr56.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-dq1xxx dmi.product.sku: 8BL04EA#ABH dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 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/1874010/+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 1867686] Re: FC hosts become unresponsive during array upgrade
I am still seeing this with Ubuntu 20.04 LTS -- 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/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
This fix has been verified. bdmurray@clean-focal-amd64:~$ apt-cache policy apport apport: Installed: 2.20.11-0ubuntu27.2 Candidate: 2.20.11-0ubuntu27.2 Version table: *** 2.20.11-0ubuntu27.2 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 500 http://192.168.10.7/ubuntu focal/main i386 Packages bdmurray@clean-focal-amd64:~$ grep "ProcFB" /tmp/apport.linux-firmware._h6whqad.apport ProcFB: 0 qxldrmfb ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Committed Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
This fix has been verified. bdmurray@clean-focal-amd64:~$ apt-cache policy apport apport: Installed: 2.20.11-0ubuntu27.2 Candidate: 2.20.11-0ubuntu27.2 Version table: *** 2.20.11-0ubuntu27.2 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-proposed/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu27 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 500 http://192.168.10.7/ubuntu focal/main i386 Packages bdmurray@clean-focal-amd64:~$ grep "ProcFB" /tmp/apport.linux-firmware._h6whqad.apport ProcFB: 0 qxldrmfb -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Committed Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
There are now files in /var/crash kaa@kaa-XPS-13-9300:~$ ll /var/crash/*.crash -rw-r- 1 gdm whoopsie 21332092 maj 21 00:02 /var/crash/_usr_bin_gnome-shell.121.crash -rw-r- 1 gdm whoopsie 3269523 maj 21 00:04 /var/crash/_usr_bin_Xwayland.121.crash I uploaded these via ubuntu-bug as requested by Daniel. Xwayland bug: 1879799 gnome bug: 1879800 -- 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/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
I am seeing this on 18.04 Linux 5.3.0-1020-azure VM. Sister VM on same kernel, same patch level, same host does not see the issue. I isolated it to a Hyper-V integration service difference between the issue vm and it's non-affect sibling. The issue reliably appears and goes away if "data exchange services" under "integration services" are disabled or re-enabled on the VM. Data Exchange disabled produces the issue. Clue was found here https://askubuntu.com/questions/996171/hv-kvp- daemon-fails-in-ubuntu-16-04-on-hyper-v -- 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/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1875150] Re: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged
I'm experiencing the same behaviour under Ubuntu 18.04 with kernel 5.3.0-51-generic. My mouse is the Logitech Performance MX and my keyboard is the Logitech K800 (both connected to the Logitech USB unifying receiver)... -- 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/1875150 Title: Mouse and keyboard intermittently stop working until Logitech Unifying Receiver is replugged Status in linux package in Ubuntu: Confirmed Bug description: The mouse is MX Anywhere 2, the keyboard is K750. If the system is booted with the Logitech Unifying Receiver plugged in, the keyboard and mouse will keep losing connection. This is most visible after a short inactivity, i.e. I start typing and nothing appears on screen for a couple of seconds, or I start moving the mouse and the cursor takes a couple of seconds to start moving. This also happens while I'm using the input device, as I was typing this paragraph the keyboard cut out twice for a second or two. Additionally, every second time the mouse reconnects, scrolling via the scroll wheel is painfully slow. When this is going on, dmesg gets once in some seconds: [ 381.185787] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 507.351776] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 540.005778] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 627.051731] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 [ 769.329768] logitech-hidpp-device 0003:046D:404A.000A: multiplier = 8 I guess it happens when the mouse reconnects. This can be fixed by unplugging and replugging the Unifying Receiver. This fixes the problem until next boot. I tried a couple of older kernel versions and the same thing happened. I also just tried Fedora 32 beta and it didn't happen there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: domin 2235 F pulseaudio /dev/snd/controlC0: domin 2235 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Apr 26 10:25:57 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-12 (926 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=a2abd949-9a7b-43a5-9453-7471311a309b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-26 (30 days ago) WifiSyslog: dmi.bios.date: 08/07/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP61.88Z.005A.B00.1708072217 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.005A.B00.1708072217:bd08/07/17:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875150/+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 1879793] Re: Disco update: upstream stable patchset 2020-05-20
** Description changed: + SRU Justification - 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: - 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: + upstream stable patchset 2020-05-20 -upstream stable patchset 2020-05-20 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.122, v.5.4.40 + + from git://git.kernel.org/ + + vhost: vsock: kick send_pkt worker once device is started + powerpc/pci/of: Parse unassigned resources + ASoC: topology: Check return value of pcm_new_ver + selftests/ipc: Fix test failure seen after initial test run + ASoC: sgtl5000: Fix VAG power-on handling + usb: dwc3: gadget: Properly set maxpacket limit + ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode + ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode + ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry + drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) + wimax/i2400m: Fix potential urb refcnt leak + net: stmmac: fix enabling socfpga's ptp_ref_clock + net: stmmac: Fix sub-second increment + ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent + ASoC: rsnd: Fix "status check failed" spam for multi-SSI + cifs: protect updating server->dstaddr with a spinlock + scripts/config: allow colons in option strings for sed + lib/mpi: Fix building for powerpc with clang + net: bcmgenet: suppress warnings on failed Rx SKB allocations + net: systemport: suppress warnings on failed Rx SKB allocations + sctp: Fix SHUTDOWN CTSN Ack in the peer restart case + drm/amdgpu: Fix oops when pp_funcs is unset in ACPI event + hexagon: clean up ioremap + hexagon: define ioremap_uc + ALSA: hda: Match both PCI ID and SSID for driver blacklist + platform/x86: GPD pocket fan: Fix error message when temp-limits are out of range + mac80211: add ieee80211_is_any_nullfunc() + cgroup, netclassid: remove double cond_resched + ASoC: topology: Check return value of soc_tplg_create_tlv + ASoC: topology: Check return value of soc_tplg_*_create + ASoC: topology: Check return value of soc_tplg_dai_config + cifs: do not share tcons with DFS + udp: document udp_rcv_segment special case for looped packets + PM / devfreq: Add missing locking while setting suspend_freq + UBUNTU: upstream stable to v4.19.122, v5.4.40 -- 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/1879793 Title: Disco update: upstream stable patchset 2020-05-20 Status in linux package in Ubuntu: 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: upstream stable patchset 2020-05-20 Ported from the following upstream stable releases: v4.19.122, v.5.4.40 from git://git.kernel.org/ vhost: vsock: kick send_pkt worker once device is started powerpc/pci/of: Parse unassigned resources ASoC: topology: Check return value of pcm_new_ver selftests/ipc: Fix test failure seen after initial test run ASoC: sgtl5000: Fix VAG power-on handling usb: dwc3: gadget: Properly set maxpacket limit ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) wimax/i2400m: Fix potential urb refcnt leak net: stmmac: fix enabling socfpga's ptp_ref_clock net: stmmac: Fix sub-second increment ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent ASoC: rsnd: Fix "status check failed" spam
[Kernel-packages] [Bug 1879793] [NEW] Disco update: upstream stable patchset 2020-05-20
Public bug reported: 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: upstream stable patchset 2020-05-20 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1879793 Title: Disco update: upstream stable patchset 2020-05-20 Status in linux package in Ubuntu: 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: upstream stable patchset 2020-05-20 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879793/+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 1878045] Re: doing dist-upgrade got error related do Broadcom
Fresh 20.10 install, experienced the same issue caused when attempting either manually attempting to install "bcmwl-kernel-source_6.30.223.271 +bdcom-0ubuntu6_amd64.deb" or using "Additional Drivers". sudo apt-get remove --purge bcmwl-kernel-source Synaptic Package Manager installed: broadcom-sta-source broadcom-sta-dkms broadcom-sta-common (It also added some dependencies) Works again! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Confirmed Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
That doesn't explain why they show up sometimes, but not all of the time. There are 3 devices in play here. * The backing device, let's say /dev/vda; this is where we want to store the data. * The caching device, let's say /dev/vdb; this holds the cache. * The bcache device; this only appears when a backing device is detected; via bcache-probe which reads the header on the disk and indicates it's a bcache device. Now, there are a few sequences that we see: 1) make-bcache -b /dev/vda -c /deb/vdb will create a bcache0 with the cache and backing dev at the same time and emit the CACHED_UUID change event which runs *after* 60-persistent-storage, and adds the bcache/by-uuid links 2) After a reboot (or if you tear down a bcache0 by stopping them in sysfs) we have several scenarios where the 2 real block devices are found: 2a) order: backing, bcacheN, caching In this scenario, vda will run through 60-persistent-storage.rules and blkid will discover ID_FS_TYPE=bcache, and generates only by-path, by-id links for the device, 69-bcache.rules will run bcache-register /dev/vda which informs the kernel that a backing device has been found. If the cache device has not yet been handled by udev (we don't know if a cache device exists, bcache can work without one) then the kernel will create a bcacheN device, but without the cache device being present, it will *NOT* emit a CHANGE event with CACHED_UUID value. Now when the cache device (vdb) is going through, 60-persistent-storage.rules, blkid will discover the same settings, TYPE=bcache, generate by-path, by-id symlinks. Then 69-bcache.rules runs, triggers a bcache-register on vdb registering the cache device in the kernel and because the superblock on the backing device specifies the cache device UUID it used the kernel can bind the cache device into the correct bcacheN device. A mainline kernel (no sauce patch) does not emit a CHANGE event with CACHED_UUID value. Our sauce patch changes the kernel to emit the CHANGE event with CACHED_UUID whenever we bind a cache device to an existing bcacheN precisely so the bcache/by-* links get generated. 2b) order: cache, backing, bcacheN Here, when vdb is plugged in, the cache device is registered in the kernel, but without a backing device, no bcacheN device is created yet. Then the backing is probed, as in 2a; the bcache-register command will register it with the kernel, and create a bcache0, and since the cache device is present, mainline kernels (and ours) will emit the CHANGE event with CACHED_UUID With this in-mind; it appears to me that in the focal case we're seeing the bcache driver CHANGE event with CACHED_UUID and then additional change events from the block layer around the bcache0 device (but not emitted from the bcache driver code) So I'd like to understand why ... I expect those events to occur but not before the driver change event. And maybe that's the race here The happy path: 1. udev processing CHANGE on backing device, it's bcache so we register it 2. kernel bcache driver creates a bcache0 block device (udev ADD event) 3. udev processing CHANGE on bcache0 device 4. udev processing CHANGE on cache device, it's bcache so we register it 5. kernel bcache driver emits CHANGE event with CACHED_UUID 6. udev processing CHANGE on bcache0 device with CACHED_UUID The bad path 1. udev processing CHANGE on cache device, it's bcache so we register it 2. udev processing CHANGE on backing device, it's bcache so we register it 3. kernel bcache driver creates a bcache0 block device (udev ADD event) 4. kernel bcache driver emits CHANGE event with CACHED_UUID 5. udev processing CHANGE on bcache0 device with CACHED_UUID 6. udev processing CHANGE on bcache0 device without CACHED_UUID if the bcache change event occurs before the block layer change events, then the database does get clobbered ... but we've an incomplete trace; we should see pairs of events, one from KERNEL, and then one from UDEV. We should definitely get a complete capture for this bug. w.r.t the fix; I've a few concerns: 1) bcache-keep-symlinks relies on /dev/bcache/by-* links to exist, if they are removed, then the keep won't work. 2) The removal of the /dev/bcache/by-uuid/ happens during processing of 60-persistent-storage.rules, which will remove the link before bcache-keep-symlinks can run (it's in 69-bcache.rules) 3) since we cannot rely on the existing links, instead we should read and parse the bcache superblock devices, much like the one I put together (and you reminded me I wrote) https://github.com/g2p/bcache-tools/pull/29/files -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting
[Kernel-packages] [Bug 1877151] Re: root unable to write to file in directory with sticky bit with fs.protected_regular set
This is intention, even for root, and is due to the commit you referenced: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=30aba6656f61ed44cba445a3c0d38b296fa9e8f5 -- 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/1877151 Title: root unable to write to file in directory with sticky bit with fs.protected_regular set Status in linux package in Ubuntu: Confirmed Bug description: In Focal (kernel 5.4), given the following scenario... 1. Directory owned by root:root with mode 1775 (sticky bit set) 2. File inside directory owned by www-data:www-data with mode 0664 3. fs.protected_regular set to non-0 value (the default is now 2) ... root is unable to write to the file if O_CREAT is set when opening it. Setting fs.protected_regular=0 works around the problem. This seems to be the result of this change: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=30aba6656f61ed44cba445a3c0d38b296fa9e8f5 It's not explicit in the commit message or documentation, but i wouldn't expect this restriction to apply to root... right? Replication: % lsb_release -sd; cat /proc/version_signature Ubuntu 20.04 LTS Ubuntu 5.4.0-29.33-generic 5.4.30 # Create directory and file % sudo -u www-data touch /tmp/myfile % \ls -ld /tmp /tmp/myfile drwxrwxrwt 13 root root 4096 May 6 11:18 /tmp -rw-rw-r-- 1 www-data www-data0 May 6 11:18 /tmp/myfile # Write by owner: OK % sudo -u www-data sh -c 'whoami > /tmp/myfile' % cat /tmp/myfile www-data # Write by root, fs.protected_regular=2 (default): FAIL % sudo sysctl fs.protected_regular fs.protected_regular = 2 % sudo -u root sh -c 'whoami > /tmp/myfile' sh: 1: cannot create /tmp/myfile: Permission denied % cat /tmp/myfile www-data # Write by root, fs.protected_regular=1: FAIL # (NOTE: This one seems to succeed if /tmp/myfile is owned by www-data:root # instead of www-data:www-data) % sudo sysctl fs.protected_regular=1 fs.protected_regular = 1 % sudo -u root sh -c 'whoami > /tmp/myfile' sh: 1: cannot create /tmp/myfile: Permission denied % cat /tmp/myfile www-data # Write by root, fs.protected_regular=0: OK % sudo sysctl fs.protected_regular=0 fs.protected_regular = 0 % sudo -u root sh -c 'whoami > /tmp/myfile' % cat /tmp/myfile root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877151/+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 1879752] Re: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210
Confirmed we see this in SRU testing: http://10.246.72.4/test- results/4.4.0-180.210-lowlatency/rizzo__4.4.0-180.210__2020-05-20_05-12-00/ubuntu_bpf_jit/results/ubuntu_bpf_jit .ubuntu-bjf-jit/debug/ubuntu_bpf_jit.ubuntu-bjf-jit.DEBUG -- 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/1879752 Title: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz The test_bpf testcase what it does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan push/pop stress test". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879752/+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 1868551] Re: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire
** Changed in: linux (Ubuntu Focal) Status: Fix Committed => 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/1868551 Title: Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4) i915_active_acquire Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification: [Impact] Users are experiencing a frequent NULL pointer dereference crash in i915_active_acquire when using kms, which is used by default. [Fix] The fix is a cherry pick from upstream which was supposed to be backported to 5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to resolve some uninitialized pointer usage. [Test] Verified by multiple bug reporters. [Regression Potential] Medium. Although there are a lot of lines added, they're mostly boilerplate, and this patch is confirmed by multiple users to fix a crash. --- uname -a Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040 [ 2556.956084] #PF: supervisor read access in kernel mode [ 2556.956084] #PF: error_code(0x) - not-present page [ 2556.956085] PGD 0 P4D 0 [ 2556.956088] Oops: [#1] SMP NOPTI [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic #17-Ubuntu [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 10/03/2019 [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286 [ 2556.956165] RAX: RBX: 983831d3e480 RCX: [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 0008 [ 2556.956167] RBP: ac17c13279e0 R08: R09: 98382d6b6520 [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 983783475200 [ 2556.956169] R13: 0008 R14: 983783475200 R15: 98382d6b6400 [ 2556.956170] FS: 7f9031c28f00() GS:98383e50() knlGS: [ 2556.956171] CS: 0010 DS: ES: CR0: 80050033 [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 003606e0 [ 2556.956173] Call Trace: [ 2556.956199] i915_active_ref+0x24/0x200 [i915] [ 2556.956223] i915_vma_move_to_active+0x74/0xf0 [i915] [ 2556.956245] eb_submit+0xff/0x440 [i915] [ 2556.956267] i915_gem_do_execbuffer+0x88e/0xc20 [i915] [ 2556.956271] ? sock_def_readable+0x40/0x70 [ 2556.956274] ? __kmalloc_node+0x205/0x320 [ 2556.956294] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] [ 2556.956314] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956330] drm_ioctl_kernel+0xae/0xf0 [drm] [ 2556.956338] drm_ioctl+0x234/0x3d0 [drm] [ 2556.956358] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] [ 2556.956361] ? vfs_writev+0xc3/0xf0 [ 2556.956363] do_vfs_ioctl+0x407/0x670 [ 2556.956365] ? fput+0x13/0x15 [ 2556.956367] ? __sys_recvmsg+0x88/0xa0 [ 2556.956369] ksys_ioctl+0x67/0x90 [ 2556.956371] __x64_sys_ioctl+0x1a/0x20 [ 2556.956373] do_syscall_64+0x57/0x190 [ 2556.956376] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 2556.956377] RIP: 0033:0x7f9032b3f68b [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48 [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 0010 [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 7f9032b3f68b [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 000d [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 7f9022a4f460 [ 2556.956384] R13: R14: 7ffee39a0090 R15: 000d [ 2556.956385] Modules linked in: ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat typec_displayport iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables cmac nfnetlink algif_hash ip6table_filter ip6_tables iptable_filter algif_skcipher af_alg bpfilter bridge stp llc snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda
Re: [Kernel-packages] [Bug 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off
Tested. Is present also in the latest drm-tip kernel. There is something I have found that may help: If I install Ubuntu 16.04.0, the issue is not present, but once I update (apt-get upgrade) the problem appears, but there is the interesting detail: if I start the upgraded 16.04 with the initial kernel, the issue is still happening, so... Maybe is not a kernel related issue? Or a mix of the kernel and something else? El mié., 20 de mayo de 2020 7:50 a. m., Kai-Heng Feng < kai.heng.f...@canonical.com> escribió: > Hmm, please test latest drm-tip kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1878007 > > Title: >Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron > 7373. When the screen is turned off (so, the suspend or screen lock > features are affected), the system freeze and I need to force the > laptop turn off and on again. There are some cases when it turn off > the screen without issues, but most of the time it freezes. Even > "SysRq REISUB" does not work for rebooting when system crash. I can > reproduce the issue using `xset dpms force off`. > > Initially this bug report was filled thinking it was a suspend issue: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144 > > Syslog or systemd journal does not provide any error information about > the crash. > > "lsb_release -rd" output: > Description: Ubuntu 20.04 LTS > Release: 20.04 > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: cccaballero 2023 F pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2019-06-09 (344 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. > Integrated_Webcam_HD >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Dell Inc. Inspiron 7373 > Package: linux (not installed) > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic > root=UUID=d8203f53-c2e5-4934-8616-0a71507c9190 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-29-generic N/A >linux-backports-modules-5.4.0-29-generic N/A >linux-firmware1.187 > Tags: focal > Uname: Linux 5.4.0-29-generic x86_64 > UpgradeStatus: Upgraded to focal on 2020-05-02 (16 days ago) > UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 09/06/2019 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.15.0 > dmi.board.name: 0JW0D6 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 31 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.15.0:bd09/06/2019:svnDellInc.:pnInspiron7373:pvr:rvnDellInc.:rn0JW0D6:rvrA00:cvnDellInc.:ct31:cvr: > dmi.product.family: Inspiron > dmi.product.name: Inspiron 7373 > dmi.product.sku: 07EB > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878007/+subscriptions > -- 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/1878007 Title: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off Status in linux package in Ubuntu: Incomplete Bug description: This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron 7373. When the screen is turned off (so, the suspend or screen lock features are affected), the system freeze and I need to force the laptop turn off and on again. There are some cases when it turn off the screen without issues, but most of the time it freezes. Even "SysRq REISUB" does not work for rebooting when system crash. I can reproduce the issue using `xset dpms force off`. Initially this bug report was filled thinking it was a suspend issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144 Syslog or systemd journal does not provide any error information about the crash. "lsb_release -rd" output: Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
I have had this on 19.10 (see https://bugs.launchpad.net/ubuntu/+source /linux-oem-osp1/+bug/1864061/comments/42) and on 20.04. Adding "options snd-hda-intel dmic_detect=0" to the end of /etc/modprobe.d/alsa-base.conf has apparently fixed the issue on 20.04 (microphone is still working). I probably would have tried this earlier if anyone (@Hui Wang ?) had explained a bit more understandably what the problem is, what the workaround does, why it fixes the issue, and what the possible side effects are. Also the bug description says this issue does not arise in focal (20.04), which is incorrect in my and several other commenters' cases. -- 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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447]
[Kernel-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@raharper To my understanding with the change action udev removes the DEVLINKS which are not still valid. Udev can't tell which links are still valid in cache/by-*. The only reason udev knows about the links is because the rule added them with SYMLINK+= when the dev was created and it is a sane assumption that when a change action appears with DEVLINKS only the new DEVLINKS are valid. Hence the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-signed package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Invalid Status in linux-signed source package in Groovy: Invalid Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Hello You-Sheng, or anyone else affected, Accepted apport into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.11-0ubuntu27.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Committed Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias:
[Kernel-packages] [Bug 1864930] Re: brightness setting and sleep/suspend (echo mem > /sys/power/state) , s2ram and s2disk fail for 5.4.0 and s2disk fail for 5.4.22
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-5.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1864930 Title: brightness setting and sleep/suspend (echo mem > /sys/power/state) , s2ram and s2disk fail for 5.4.0 and s2disk fail for 5.4.22 Status in linux-5.4 package in Ubuntu: Confirmed Bug description: 1) After resuming from suspend (uswsusp/s2ram) and/or after resuming from "echo mem > /sys/power/state" there is a black screen on laptop after resume with 5.4.0-14-generic kernel only. Kernel seems to be working as CTRL+ALT+F2 and CTRL+ALT+DEL restarts laptop. A) 3 Different combinations of this distro with other kernels work well: kubunut20.04 + linux-image-5.3.0-40-generic (copied from kubuntu 19.10 from /lib/modules/5.3.0-40-generic and /boot/vmlinuz-5.3.0-40-generic) Installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc3/ kubuntu20.04 + linux-image-unsigned-5.5.6-050506-generic is working. kubuntu20.04 + linux-image-unsigned-5.6.0-050600rc3-generic is working. B) This kernel 5.4.0-14-generic when copied manually into kubuntu 19.10 behaves the same as in 20.04 (NOT WORKING for suspend to ram) 2) setting brightness with keys on laptop keyboard does not work for this kernel 5.4.0-14-generic only Neither using this command line method marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/max_brightness 255 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/max_brightness 255 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/actual_brightness 255 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/brightness 242 marian@kubuntu2004:~/Downloads$ echo 200 | sudo tee /sys/class/backlight/intel_backlight/brightness 200 marian@kubuntu2004:~/Downloads$ cat /sys/class/backlight/intel_backlight/brightness Again kernel 5.3 copied into kubuntu20.04 got working brigthness keys. However this works for all tested kernels above (including 5.4.0-14-generic) xrandr --output eDP-1 --brightness 0.8 3) after uswsusp/hibernate (s2disk) and "echo disk > /sys/power/state" do not seem to resume/thaw for those kernels: linux-image-5.4.0-14-generic, linux-image-unsigned-5.5.6-050506-generic , linux-image-unsigned-5.6.0-050600rc3-generic, on the other hand kernel linux-image-5.3.0-40-generic manually copied from kubuntu 19.10 into kubuntu 20.04 seems to be working fine when thawing/resuming from hibernation. Again I tested different combination of kernels and distros for this issue. This kernel (5.4.0-14-generic) also does not work for hibernate/resume even when copied from kubuntu20.04 into kubuntu19.10 4) Starting kubuntu without installation from daily build from 25th Feb 2020 shows the same problem for brightness setting and for black screen after resuming from sleep. http://cdimage.ubuntu.com/kubuntu/daily-live/current/ Note I always recreated imagerd in target place when copied kernels manually: update-initramfs -u -k 5.3.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marian 1214 F pulseaudio CurrentDesktop: KDE Date: Wed Feb 26 22:20:29 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision FHD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=/dev/mapper/sysvg-ub2004deboot ro resume=/dev/nvme0n1p8 quiet splash resume=/dev/nvme0n1p8 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 01/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
This bug was fixed in the package bcache-tools - 1.0.8-4 --- bcache-tools (1.0.8-4) unstable; urgency=medium [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 11 to 12. * Set debhelper-compat version in Build-Depends. [ Balint Reczey ] * Add Salsa CI configuration * Keep symlinks when udev changes /dev/bcacheN (LP: #1861941) * Drop update-initramfs trigger. With dh compat version 12 update-initramfs is inserted to postinst automatically -- Balint Reczey Wed, 20 May 2020 14:41:11 +0200 ** Changed in: bcache-tools (Ubuntu Groovy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-signed package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Invalid Status in linux-signed source package in Groovy: Invalid Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Oh, I see! I had no idea that error was related to secure boot. Thanks! I'll try that later and get back to you. The drm-tip download page ( https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ ) links to the following wiki pages, neither of which mention secure boot in any way. * https://wiki.ubuntu.com/Kernel/MainlineBuilds * https://wiki.ubuntu.com/Kernel/FAQ Maybe most folks who decide to install one of these kernels have enough background knowledge to figure this out; but if users are being invited to install these kernels as part of diagnosing bugs maybe it's worth adding a note to one of those pages about secure boot? -- 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/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+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 1879010] Re: Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink
1) This is the speaker in question: http://fugoo.com.au/fugoo-sport.php 2) Confirm - I can select the higher quality audio profile by going to settings after the speaker is paired / connected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1879010 Title: Bluetooth speaker defaults to lower quality (HSP/HFP) instead of higher quality (A2DP) sink Status in bluez package in Ubuntu: Incomplete Bug description: This seems identical to this bug: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046, but was suggested to open a new bug as the other one was closed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 16:13:24 2020 InstallationDate: Installed on 2020-05-06 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=21f0214d-8c30-4e9b-bf3b-1b3576c64628 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 54:8D:5A:D8:BA:43 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1126282 acl:178 sco:0 events:156624 errors:0 TX bytes:130927152 acl:152574 sco:8 commands:3326 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1879010/+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 1870995] Re: i8042: Warning: Keylock active
Alright; thanks! -- 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
I guess I don't understand why we see this in focal. The two events in
Colin's trace always happen on any Ubuntu kernel. We should see if we
can get another udev trace on bionic that captures both CHANGE events,
one will be from the bcache driver itself, and one is from the block
layer. THe order and content of the change event matter.
Another thing I don't understand is why does udev drop the a symlink created by
another rule? This seems like the core issue.
Looking at systemd/udev source code; udev will do a
FOREACH_DEVICE_DEVLINK and check if the name is in the database file for
the device. Its not clear to me yet how or when the database file get's
written.
The other question I have is: if we reversed the order of the focal
CHANGE events, wouldn't we see just the opposite happen (the
driver=bcache change event would not have all of the devlinks from a
blkid probe) and all of the /dev/disk/by-{id, uuid, ...} get removed
when running
I think the patch you're proposing should work; but I don't think we've
root caused why the link gets removed in the first place. Once we
understand the root cause, I think we can better understand what a fix
should look like.
Lastly, I think we might also test this out on mainline kernel; I wonder if our
SAUCE patch for emitting the CACHED_UUID needs an update (or could be dropped).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
Status in bcache-tools package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux-signed package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Status in bcache-tools source package in Focal:
New
Status in linux source package in Focal:
Invalid
Status in linux-signed source package in Focal:
New
Status in systemd source package in Focal:
Invalid
Status in bcache-tools source package in Groovy:
In Progress
Status in linux source package in Groovy:
Invalid
Status in linux-signed source package in Groovy:
Invalid
Status in systemd source package in Groovy:
Invalid
Bug description:
1.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
2.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
root@ubuntu:~# apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
*** 5.4.0.12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
*** 5.4.0-12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
+ ls -al /dev/bcache/by-uuid/
total 0
drwxr-xr-x 2 root root 60 Feb 4 23:31 .
drwxr-xr-x 3 root root 60 Feb 4 23:31 ..
lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a
-> ../../bcache0
4.
root@ubuntu:~# ls -al /dev/bcache/by-uuid
ls: cannot access '/dev/bcache/by-uuid': No such file or directory
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-12-generic 5.4.0-12.15
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb 4 23:31:52 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1879759] [NEW] Focal update: v5.4.42 upstream stable release
Public bug reported:
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.4.42 upstream stable release
from git://git.kernel.org/
net: dsa: Do not make user port errors fatal
shmem: fix possible deadlocks on shmlock_user_lock
net: phy: microchip_t1: add lan87xx_phy_init to initialize the lan87xx phy.
KVM: arm: vgic: Synchronize the whole guest on GIC{D,R}_I{S,C}ACTIVER read
gpio: pca953x: Fix pca953x_gpio_set_config
SUNRPC: Add "@len" parameter to gss_unwrap()
SUNRPC: Fix GSS privacy computation of auth->au_ralign
net/sonic: Fix a resource leak in an error handling path in 'jazz_sonic_probe()'
net: moxa: Fix a potential double 'free_irq()'
ftrace/selftests: workaround cgroup RT scheduling issues
drop_monitor: work around gcc-10 stringop-overflow warning
virtio-blk: handle block_device_operations callbacks after hot unplug
sun6i: dsi: fix gcc-4.8
net_sched: fix tcm_parent in tc filter dump
scsi: sg: add sg_remove_request in sg_write
mmc: sdhci-acpi: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA for AMDI0040
dpaa2-eth: properly handle buffer size restrictions
net: fix a potential recursive NETDEV_FEAT_CHANGE
netlabel: cope with NULL catmap
net: phy: fix aneg restart in phy_ethtool_set_eee
net: stmmac: fix num_por initialization
pppoe: only process PADT targeted at local interfaces
Revert "ipv6: add mtu lock check in __ip6_rt_update_pmtu"
tcp: fix error recovery in tcp_zerocopy_receive()
tcp: fix SO_RCVLOWAT hangs with fat skbs
virtio_net: fix lockdep warning on 32 bit
dpaa2-eth: prevent array underflow in update_cls_rule()
hinic: fix a bug of ndo_stop
net: dsa: loop: Add module soft dependency
net: ipv4: really enforce backoff for redirects
netprio_cgroup: Fix unlimited memory leak of v2 cgroups
net: tcp: fix rx timestamp behavior for tcp_recvmsg
nfp: abm: fix error return code in nfp_abm_vnic_alloc()
r8169: re-establish support for RTL8401 chip version
umh: fix memory leak on execve failure
riscv: fix vdso build with lld
dmaengine: pch_dma.c: Avoid data race between probe and irq handler
dmaengine: mmp_tdma: Do not ignore slave config validation errors
dmaengine: mmp_tdma: Reset channel error on release
selftests/ftrace: Check the first record for kprobe_args_type.tc
cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once
ALSA: hda/hdmi: fix race in monitor detection during probe
drm/amd/powerplay: avoid using pm_en before it is initialized revised
drm/amd/display: check if REFCLK_CNTL register is present
drm/amd/display: Update downspread percent to match spreadsheet for DCN2.1
drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper()
drm/amdgpu: simplify padding calculations (v2)
drm/amdgpu: invalidate L2 before SDMA IBs (v2)
ipc/util.c: sysvipc_find_ipc() incorrectly updates position index
ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse
gfs2: Another gfs2_walk_metadata fix
mmc: sdhci-pci-gli: Fix no irq handler from suspend
IB/hfi1: Fix another case where pq is left on waitlist
ACPI: EC: PM: Avoid premature returns from acpi_s2idle_wake()
pinctrl: sunrisepoint: Fix PAD lock register offset for SPT-H
pinctrl: baytrail: Enable pin configuration setting for GPIO chip
pinctrl: qcom: fix wrong write in update_dual_edge
pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler
bpf: Fix error return code in map_lookup_and_delete_elem()
ALSA: firewire-lib: fix 'function sizeof not defined' error of tracepoints
format
i40iw: Fix error handling in i40iw_manage_arp_cache()
drm/i915: Don't enable WaIncreaseLatencyIPCEnabled when IPC is disabled
bpf, sockmap: msg_pop_data can incorrecty set an sge length
bpf, sockmap: bpf_tcp_ingress needs to subtract bytes from sg.size
mmc: alcor: Fix a resource leak in the error path for ->probe()
mmc: sdhci-pci-gli: Fix can not access GL9750 after reboot from Windows 10
mmc: core: Check request type before completing the request
mmc: core: Fix recursive locking issue in CQE recovery path
mmc: block: Fix request completion in the CQE timeout path
gfs2: More gfs2_find_jhead fixes
fork: prevent accidental access to clone3 features
drm/amdgpu: force fbdev into vram
NFS: Fix fscache super_cookie index_key from changing after umount
nfs: fscache: use timespec64 in inode auxdata
NFSv4: Fix fscache cookie aux_data to ensure change_attr is included
netfilter: conntrack: avoid gcc-10 zero-length-bounds warning
drm/i915/gvt: Fix kernel oops for 3-level ppgtt guest
arm64: fix the flush_icache_range arguments in machine_kexec
nfs: fix NULL deference in nfs4_get_valid_delegation
SUNRPC: Signalled ASYNC tasks need to exit
netfilter: nft_set_rbtree: Introduce
[Kernel-packages] [Bug 1879752] [NEW] test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz The test_bpf testcase what it does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan push/pop stress test". ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux 4.4.0-180.210 ADT test failure with linux 4.4.0-180.210 + test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Invalid ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz + i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz + + The test_bpf testcase what it does is only loading the test_bpf module, + which reports the following error: + + May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop + jited:1 ret -12 != 3055 FAIL (1 times) + + This is cased by upstream commit 636c2628086e "net: skbuff: Remove + errornous length validation in skb_vlan_pop()" which we applied from + stable upstream v4.4.223. + + The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan + push/pop stress test". -- 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/1879752 Title: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz The test_bpf testcase what it does is only loading the test_bpf
[Kernel-packages] [Bug 1879755] [NEW] cp --reflink support
Public bug reported: With the recent efforts of promoting ZFS in Ubuntu, it might be a good idea to add support for 'cp --reflink=always' such that proven workflows for Btrfs can be easily transferred to ZFS. ** Affects: zfs Importance: Unknown Status: Unknown ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/openzfs/zfs/issues #10351 https://github.com/openzfs/zfs/issues/10351 ** Also affects: zfs via https://github.com/openzfs/zfs/issues/10351 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1879755 Title: cp --reflink support Status in Native ZFS for Linux: Unknown Status in zfs-linux package in Ubuntu: New Bug description: With the recent efforts of promoting ZFS in Ubuntu, it might be a good idea to add support for 'cp --reflink=always' such that proven workflows for Btrfs can be easily transferred to ZFS. To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1879755/+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 1870995] Re: i8042: Warning: Keylock active
Then we have nothing to worry about. -- 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+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 1873179] Re: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46
kernel 5.3.0-53 doesn't seem to have this issue -- 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/1873179 Title: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46 Status in linux package in Ubuntu: Confirmed Bug description: Hi. I'm running Xubuntu 5.3.0-45.37-generic 5.3.18 on ThinkPad P1 Gen2 (ThinkPad Carbon X1 without Nvidia graphics). This bug happens on Eoan kernel 5.3.0-46 only. Kernels -45 and earlier don't have it, so I had to revert to 5.3.0-45. Steps to reproduce: 1. Install ZOOM .deb from https://zoom.us/download?os=linux 2. Start it. 3. Try to start ZOOM meeting. 4. GUI becomes very-very slow, but not completely frozen. No crashes. 5. As soon as ZOOM meeting window is closed, lines "Resetting rcs0 for hang on rcs0" stop coming and GUI is OK. In syslog I see following lines: --- [ 111.956936] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 111.957947] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 119.951013] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 127.949941] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 135.950174] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 143.950558] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 151.950819] i915 :00:02.0: Resetting rcs0 for hang on rcs0 --- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vburdo 1450 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-03-15 (31 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QUS11E00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.183.5 Tags: eoan Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QUS11E00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QUS11E00:pvrThinkPadP1Gen2:rvnLENOVO:rn20QUS11E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QUS11E00 dmi.product.sku: LENOVO_MT_20QU_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-03-16T16:40:07.038972 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vburdo 1450 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-03-15 (31 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QUS11E00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.183.5 Tags: eoan Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QUS11E00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
my investigation came to same conclusion as #109 (but I'm on 20.04 and latest kernel, so this is still relevant) My configuration is as follows. It there is a need to get more information/logs, please let me know. -- Dell Latitude 7389 miki@DL-7389:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" miki@DL-7389:~$ uname -a Linux DL-7389 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux dmesg gets spammed by these error reports: [116522.584941] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [116522.584959] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [116522.584967] pcieport :00:1c.0: AER: device [8086:9d17] error status/mask=1000/2000 [116522.584973] pcieport :00:1c.0: AER:[12] Timeout [116533.643718] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [116533.643735] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [116533.643744] pcieport :00:1c.0: AER: device [8086:9d17] error status/mask=1000/2000 [116533.643751] pcieport :00:1c.0: AER:[12] Timeout [116559.755644] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [116559.755655] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [116559.755658] pcieport :00:1c.0: AER: device [8086:9d17] error status/mask=1000/2000 [116559.755660] pcieport :00:1c.0: AER:[12] Timeout Device causing it seems to be Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter: miki@DL-7389:~$ sudo lspci -t -v -[:00]-+-00.0 Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers +-02.0 Intel Corporation HD Graphics 620 +-04.0 Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem +-13.0 Intel Corporation Sunrise Point-LP Integrated Sensor Hub +-14.0 Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller +-14.2 Intel Corporation Sunrise Point-LP Thermal subsystem +-15.0 Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 +-15.1 Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 +-15.2 Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 +-16.0 Intel Corporation Sunrise Point-LP CSME HECI #1 +-1c.0-[01]00.0 Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter +-1d.0-[02]00.0 Toshiba Corporation Device 0116 +-1f.0 Intel Corporation Sunrise Point LPC Controller/eSPI Controller +-1f.2 Intel Corporation Sunrise Point-LP PMC +-1f.3 Intel Corporation Sunrise Point-LP HD Audio \-1f.4 Intel Corporation Sunrise Point-LP SMBus lspci -v detailed output for this device (strange that the serial number is read as zeros): 01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Dell QCA6174 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 145 Memory at ef00 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit- Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178] Latency Tolerance Reporting Capabilities: [180] L1 PM Substates Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci lshw output for this device (here the serial number is visible correctly, I redacted): *-pci:0 description: PCI bridge product: Sunrise Point-LP PCI Express Root Port #8 vendor: Intel Corporation physical id: 1c bus info: pci@:00:1c.0 version: f1 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:122 memory:ef00-ef1f *-network description: Wireless interface product: QCA6174 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:01:00.0 logical name: wlp1s0 version: 32 serial: --redacted-- width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
I confirmed that 5.4.0-29 does not show the problem, and -31 does. Then I built -31 with these three patches reverted: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay With those reverted I see the problem. It appears that this is a problem that the shiftfs hack for overlayfs was covering up, and then when the upstream behavior was restored whenever shiftfs is not the underlay it revealed the issue. -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1434579] Re: Unable to install VirtualBox Guest Service in 15.04
The issue in ubuntu-drivers-common has been reported again (bug #1878553). Since this bug was used to track fixes in other packages, instead of marking the new bug a duplicate, I'm splitting off the ubuntu-drivers-common task there. ** No longer affects: ubuntu-drivers-common (Ubuntu) ** Description changed: It is not longer possible to select VirtualBox Guest Service in 15.04. The only options available are: - * Continue using a manually install driver - * Do not use the device + * Continue using a manually install driver + * Do not use the device The option 'Using x86 virtualisation solution - guest addition module' is no longer selectable. See the attached screen shot. This is from a fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers have been manually installed. In light of the Virtualbox issue where new installs on Virtualbox have a resolution of 640x480 (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/) this is going to be a frustration for many users. + + EDIT: the ubuntu-drivers-common task is tracked bug #1878553 (see + comment #12). ** Description changed: It is not longer possible to select VirtualBox Guest Service in 15.04. The only options available are: * Continue using a manually install driver * Do not use the device The option 'Using x86 virtualisation solution - guest addition module' is no longer selectable. See the attached screen shot. This is from a fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers have been manually installed. In light of the Virtualbox issue where new installs on Virtualbox have a resolution of 640x480 (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/) this is going to be a frustration for many users. - EDIT: the ubuntu-drivers-common task is tracked bug #1878553 (see - comment #12). + EDIT: the ubuntu-drivers-common task is tracked by bug #1878553 (see + comment #12) -- 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/1434579 Title: Unable to install VirtualBox Guest Service in 15.04 Status in linux package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Bug description: It is not longer possible to select VirtualBox Guest Service in 15.04. The only options available are: * Continue using a manually install driver * Do not use the device The option 'Using x86 virtualisation solution - guest addition module' is no longer selectable. See the attached screen shot. This is from a fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers have been manually installed. In light of the Virtualbox issue where new installs on Virtualbox have a resolution of 640x480 (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/) this is going to be a frustration for many users. EDIT: the ubuntu-drivers-common task is tracked by bug #1878553 (see comment #12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434579/+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 1879704] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-20 11:37 EDT---
And in the meantime this has also been added to
the public s390 repository on kernel.org which also
includes the later Reviewed-by from Pierre Morel.
PCI/IOV: Introduce pci_iov_sysfs_link() function
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=a1ceea67f2e5b73cebd456e7fb463b3052bc6344
s390/pci: create links between PFs and VFs
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=e5794cf1a270d813a5b9373a6876487d4d154195
I've also tested that the patches apply clean on
focal master-next + the patches from LP 1874056
--
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/1879704
Title:
[UBUNTU 20.04] s390x/pci: implement linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
As with other architectures, we must be able on s390x to verify the
following relationships between PFs and VFs for proper management
(including by libvirt) of network interfaces:
1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can
be found here: https://www.kernel.org/doc/Documentation/ABI/testing
/sysfs-bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off by the
struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
This in turn allows for a graceful and orderly shutdown of VFs
associated with a VF as triggered by:
echo 0 > /sys/bus/pci/devices//sriov_numvfs
Previously this could leave the card in an unresponsive error state.
The patches for this have been discussed and Acked-by the
responsible upstream maintainer here:
[RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/
[RFC 1/2] PCI/IOV: Introduce pci_iov_sysfs_link() function
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
[RFC 2/2] s390/pci: create links between PFs and VFs
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
They are currently queued to be posted to the public s390 Kernel
repository and linux-next / 5.8.
These depend on the previous multi-function/enumeration rework.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879704/+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 1876875] Re: Improve download-signed script to support current & grub2
This bug was fixed in the package grub2-signed - 1.144 --- grub2-signed (1.144) groovy; urgency=medium * Fix arm64 download, grub2 package doesn't exist on that arch, use grub2-common instead. grub2-signed (1.143) groovy; urgency=medium * Support downloads from PPAs for additional signatures. LP: #1876875 -- Dimitri John Ledkov Wed, 20 May 2020 13:53:28 +0100 ** Changed in: grub2-signed (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: In Progress Status in s390-tools-signed package in Ubuntu: New Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+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 1832472] Re: cdc_ncm floods syslog unneccessarily
Well, use the Realtek r8156 driver until they made it upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832472 Title: cdc_ncm floods syslog unneccessarily Status in linux package in Ubuntu: Confirmed Bug description: Upon plugging in a USB adapter for NBase-T ethernet with an Realtek chip RTL8156 the kernel module cdc_ncm starts flooding /var/log/syslog with unneccessary status info. The status lines either say that there's no ethernet link or show the interface as connected and state the link speed. The relevant parts from /var/log/syslog after attaching the adapter without ethernet link read like this: [...] Jun 12 10:48:58 resdz-v13 kernel: [ 4240.398485] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419463] usb 2-3: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=30.00 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419469] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419472] usb 2-3: Product: USB 10/100/1G/2.5G LAN Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419475] usb 2-3: Manufacturer: Realtek Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419477] usb 2-3: SerialNumber: 1 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447769] cdc_ncm 2-3:2.0: MAC-Address: 00:13:3b:68:00:e9 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447775] cdc_ncm 2-3:2.0: setting rx_max = 16384 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447929] cdc_ncm 2-3:2.0: setting tx_max = 16384 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.448901] cdc_ncm 2-3:2.0 usb0: register 'cdc_ncm' at usb-:00:14.0-3, CDC NCM, 00:13:3b:68:00:e9 Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.1872] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8) Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-3" Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Using default interface naming scheme 'v240'. Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Jun 12 10:48:58 resdz-v13 kernel: [ 4240.466476] cdc_ncm 2-3:2.0 enx00133b6800e9: renamed from usb0 Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.2315] device (usb0): interface index 7 renamed iface from 'usb0' to 'enx00133b6800e9' Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Process 'vlan-network-interface UDEV' failed with exit code 1. Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.2431] device (enx00133b6800e9): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jun 12 10:48:58 resdz-v13 charon: 12[KNL] interface enx00133b6800e9 activated Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-3" Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device Jun 12 10:48:58 resdz-v13 kernel: [ 4240.524052] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.556109] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.588054] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.620383] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.652415] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected [...] Upon plugging in the ethernet cable I see [...] Jun 12 10:49:01 resdz-v13 kernel: [ 4243.372273] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink Jun 12 10:49:01 resdz-v13 kernel: [ 4243.404278] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected [...] and Network Manager starts its work. After the interface is up the flooding continues: [...] Jun 12 10:49:01 resdz-v13 kernel: [ 4243.564056] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink Jun 12 10:49:01 resdz-v13 kernel: [ 4243.596051] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] online Jun 12 10:49:01 resdz-v13 kernel: [ 4243.628055] cdc_ncm 2-3:2.0 enx00133b6800e9:
[Kernel-packages] [Bug 1879704] Re: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
The content of comment #2 was copied over as bug description.
The patch set in preparation is:
[RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/
[RFC 1/2] PCI/IOV: Introduce pci_iov_sysfs_link() function
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
[RFC 2/2] s390/pci: create links between PFs and VFs
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
As already mentioned, target to upstream acceptance is kernel 5.8.
** Description changed:
- Description will follow
+ As with other architectures, we must be able on s390x to verify the
+ following relationships between PFs and VFs for proper management
+ (including by libvirt) of network interfaces:
+
+ 1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
+ 2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
+ 3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
+
+ More details for the already existing parameters mentioned above can be
+ found here: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-
+ bus-pci
+
+ Moreover creating not just the sysfs but also the in-kernel link
+ (struct pci_dev->physfn) also allows us to use the common code path
+ for disabling/shutdown of PFs.
+ This code path is currently fenced off by the
+ struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
+
+ This in turn allows for a graceful and orderly shutdown of VFs
+ associated with a VF as triggered by:
+
+ echo 0 > /sys/bus/pci/devices//sriov_numvfs
+
+ Previously this could leave the card in an unresponsive error state.
+
+ The patches for this have been discussed and Acked-by the
+ responsible upstream maintainer here:
+
+ [RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
+
https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/
+
+ [RFC 1/2] PCI/IOV: Introduce pci_iov_sysfs_link() function
+
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
+
+ [RFC 2/2] s390/pci: create links between PFs and VFs
+
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
+
+ They are currently queued to be posted to the public s390 Kernel
+ repository and linux-next / 5.8.
+ These depend on the previous multi-function/enumeration rework.
--
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/1879704
Title:
[UBUNTU 20.04] s390x/pci: implement linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
As with other architectures, we must be able on s390x to verify the
following relationships between PFs and VFs for proper management
(including by libvirt) of network interfaces:
1. Determine if a device is a virtual function: for other architectures this
is currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other
architectures this is currently available as `virtfn{index}` links under the PF
device's directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can
be found here: https://www.kernel.org/doc/Documentation/ABI/testing
/sysfs-bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off by the
struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
This in turn allows for a graceful and orderly shutdown of VFs
associated with a VF as triggered by:
echo 0 > /sys/bus/pci/devices//sriov_numvfs
Previously this could leave the card in an unresponsive error state.
The patches for this have been discussed and Acked-by the
responsible upstream maintainer here:
[RFC 0/2] Enable PF-VF linking with pdev->no_vf_scan (s390)
https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/
[RFC 1/2] PCI/IOV: Introduce pci_iov_sysfs_link() function
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
[RFC 2/2] s390/pci: create links between PFs and VFs
https://lore.kernel.org/linux-pci/20200506154139.90609-2-schne...@linux.ibm.com/
They are
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
dmesg from good kernel 5.4.0-29-generic ** Attachment added: "dmesg.good" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+attachment/5374740/+files/dmesg.good -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
dmesg from bad kernel 5.4.0-31-generic ** Attachment added: "dmesg.bad" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+attachment/5374741/+files/dmesg.bad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1879707] Re: [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed
Does the mke2fs of the DASD FBA issue happen during an installation or post install on a running system? Please share the steps you performed that allow to reproduce and also the log (syslog). ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1879707 Title: [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of retries and failed Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879707/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Testing with the the 5.7.0-050700rc6-generic kernel does not change the behavior. Sound output does not work, and the 'Dummy Output' remains in the Sound section within the Settings application. When testing the system with Linux Mint 19.3 with kernel version 5.3.0-51 #44-18.04.2-Ubuntu sound works properly. Please let me know if I should provide new logs or any other additional information to help troubleshoot the problem. Thank you again for your help! -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) 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-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-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/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
I have reverted the following two commits from both Eoan 5.3.0-53 and Focal 5.4.0-31 and I was not able to reproduce the problem anymore: Revert "UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay" Revert "UBUNTU: SAUCE: overlayfs: fix shitfs special-casing" -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
[ 267.532883] audit: type=1400 audit(1589983933.896:66): apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/entrypoint.sh" pid=3373 comm="entrypoint.sh" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 in dmesg looks suspicious. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+attachment/5374739/+files/dmesg -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1879711] Re: aws: disable CONFIG_DMA_CMA
** Description changed: [Impact] The option CONFIG_DMA_CMA seems to cause resume problems on the t2.* instance types (Xen). - With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. - - However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. + With this option enabled device drivers are allowed to use the + Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can + allocate large physically-contiguous blocks of memory, instead of + relying on the I/O map or scatter-gather support. + + However, on resume, the memory used by DMA needs to be re-initialized / + re-allocated, but it may fail to allocate large chunks of contiguous + memory due to the fact that we also need to restore the hibernation + image, using more memory and causing a system hang during the resume + process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). + With this option disabled the success rate of hibernation on the t2.* + instance types during our tests jumped to 100%. + [Regression potential] It is a .config change, no regression potential except with the fact that disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. ** Description changed: [Impact] The option CONFIG_DMA_CMA seems to cause resume problems on the t2.* instance types (Xen). With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). With this option disabled the success rate of hibernation on the t2.* instance types during our tests jumped to 100%. [Regression potential] - It is a .config change, no regression potential except with the fact - that disabling this option also disables the module 'etnaviv' (Vivante + It is a .config change, no regression potential except for the fact that + disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. ** Description changed: [Impact] - The option CONFIG_DMA_CMA seems to cause resume problems on the t2.* - instance types (Xen). + The option CONFIG_DMA_CMA seems to cause hibernation failures on the + t2.* instance types (Xen). With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). With this option disabled the success rate of hibernation on the t2.* instance types during our tests jumped to 100%. [Regression potential] It is a .config change, no regression potential except for the fact that disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed
[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active
I don't even have PS/2 mouse/keyboard ports on the machine in question. They are only present on the docking station. If the computer is not plugged into the docking station, the warning still appears. If the computer is plugged into the docking station, USB keyboard and USB mouse are used. -- 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
** Description changed: - I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: + I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272G5DYEB. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is
[Kernel-packages] [Bug 1879704] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-20 09:57 EDT---
As with other architectures, we must be able to verify the following
relationships between PFs and VFs for proper management (including by libvirt)
of network interfaces:
1. Determine if a device is a virtual function: for other architectures this is
currently available in the file `physfn` which is a link to the parent PF's
device.
2. Determine virtual functions of a physical function: for other architectures
this is currently available as `virtfn{index}` links under the PF device's
directory.
3. Determine the physical function of a virtual function: on x86 this is
currently available in the file `physfn` which is a link to the parent PF
More details for the already existing parameters mentioned above can be
found here: https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-
bus-pci
Moreover creating not just the sysfs but also the in-kernel link
(struct pci_dev->physfn) also allows us to use the common code path
for disabling/shutdown of PFs.
This code path is currently fenced off by the
struct pci_dev->no_vf_scan flag of which s390 is currently the only user.
This in turn allows for a graceful and orderly shutdown of VFs
associated with a VF as triggered by:
echo 0 > /sys/bus/pci/devices//sriov_numvfs
Previously this could leave the card in an unresponsive error state.
The patches for this have been discussed and Acked-by the
responsible upstream maintainer here:
https://lore.kernel.org/linux-pci/20200506154139.90609-1-schne...@linux.ibm.com/
They are currently queued to be posted to the public s390 Kernel
repository and linux-next / 5.8.
These depend on the previous multi-function/enumeration rework.
--
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/1879704
Title:
[UBUNTU 20.04] s390x/pci: implement linking between PF and VF for
multifunction devices
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
Description will follow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879704/+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 1879708] Re: [UBUNTU 20.04] Subiquity installer does not accept user-data generated after manual installation
** Package changed: linux (Ubuntu) => subiquity (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical
Foundations Team (canonical-foundations)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Tags added: rls-ff-incoming
--
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/1879708
Title:
[UBUNTU 20.04] Subiquity installer does not accept user-data generated
after manual installation
Status in Ubuntu on IBM z Systems:
New
Status in subiquity package in Ubuntu:
New
Bug description:
I'm installing Ubuntu 20.04 with a nocloud-net installation source on
a z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.
After manual installation a user-data to repeat the process
automatically is stored in /var/log/installer/autoinstall-user-data.
However, it has two issues:
- there is no "version" entry, so Subiquity does not accept it at all:
curtin start subiquity/core_validation:
curtin finish subiquity/core_validation: 'version' is a required property
- when I add version: 1, I get the following error:
curtin start subiquity/Keyboard/load_autoinstall_data:
curtin finish subiquity/Keyboard/load_autoinstall_data: None is not of type
'string'
Failed validating 'type' in schema['properties']['toggle']:
{'type': 'string'}
On instance['toggle']:
None
And when I change this too I get the related issues with netplan and
storage configuration.
Kernel command line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/
User-data:
#cloud-config
autoinstall:
apt:
geoip: true
preserve_sources_list: false
primary:
- arches: [amd64, i386]
uri: http://archive.ubuntu.com/ubuntu
- arches: [default]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password:
/wjUJRFEEW5PA.CormpX2CYCxwoEAqGpB4sdIi8GgdJLd21tzNGDcZMDi0,
realname: user, username: user}
keyboard: {layout: us, toggle: null, variant: ''}
locale: en_US
network:
ethernets:
encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
nameservers:
addresses: [172.18.0.1]
version: 2
proxy: http://lnxproxy.lnxne.boe:3128
ssh:
allow-pw: true
authorized-keys: []
install-server: true
storage:
config:
- {device_id: 0.0.3695, blocksize: 4096, disk_layout: cdl, mode: quick,
preserve: false,
type: dasd, id: dasd-dasda}
- {ptable: vtoc, serial: 0X3695, path: /dev/dasda, wipe:
superblock-recursive,
preserve: false, name: '', grub_device: false, device_id: 0.0.3695,
type: disk,
id: disk-dasda}
- {device: disk-dasda, size: 22153265152, wipe: superblock, flag: '',
number: 1,
preserve: false, type: partition, id: partition-0}
- {fstype: ext4, volume: partition-0, preserve: false, type: format, id:
format-0}
- {device: format-0, path: /, type: mount, id: mount-0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879708/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
I just checked back with my Nvidia machine and instead of "amdgpu" it saying that "modeset" is doing the EDID'ing (both with open source and proprietary driver) and no 1080p 144 Hz: [18.782] (II) modeset(G0): EDID for output DP-1-1 [18.782] (II) modeset(G0): Printing probed modes for output DP-1-1 [18.782] (II) modeset(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [18.782] (II) modeset(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [18.782] (II) modeset(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) [18.782] (II) modeset(G0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e) [18.782] (II) modeset(G0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Where do I have to file the bug report in this case? I saw that there is a thing called modesetting that is part of the kernel. Do I have to file a report for the kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272G5DYEB. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2
[Kernel-packages] [Bug 1879711] [NEW] aws: disable CONFIG_DMA_CMA
Public bug reported: [Impact] The option CONFIG_DMA_CMA seems to cause resume problems on the t2.* instance types (Xen). With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). [Regression potential] It is a .config change, no regression potential except with the fact that disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-aws (Ubuntu Focal) Importance: High Assignee: Andrea Righi (arighi) Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-aws (Ubuntu) ** Changed in: linux-aws (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1879711 Title: aws: disable CONFIG_DMA_CMA Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Bug description: [Impact] The option CONFIG_DMA_CMA seems to cause resume problems on the t2.* instance types (Xen). With this option enabled device drivers are allowed to use the Contiguous Memory Allocator (CMA) for DMA operations. So, drivers can allocate large physically-contiguous blocks of memory, instead of relying on the I/O map or scatter-gather support. However, on resume, the memory used by DMA needs to be re-initialized / re-allocated, but it may fail to allocate large chunks of contiguous memory due to the fact that we also need to restore the hibernation image, using more memory and causing a system hang during the resume process. [Test case] Hibernate / resume any t2.* instance (especially t2.nano, where the problem seems to happen 100% of the times after 2 consecutive hibernate/resume cycles). [Fix] Disable CONFIG_DMA_CMA. NOTE: this option is already disabled in the generic kernel (see LP: #1362261). [Regression potential] It is a .config change, no regression potential except with the fact that disabling this option also disables the module 'etnaviv' (Vivante graphic card), that is not really needed in the aws kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1879711/+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 1870995] Re: i8042: Warning: Keylock active
i8042 is for PS/2 keyboard and mouse. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+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 1879707] [NEW] [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed
Public bug reported: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185933 severity-medium targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-185933 severity-medium 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/1879707 Title: [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of retries and failed Status in linux package in Ubuntu: New Bug description: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879707/+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 1879704] Re: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
This is a spin off of LP 1874056 - see comment #32 there. More details will follow here soon. ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-z-systems Status: New => Incomplete ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1879704 Title: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879704/+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 1879708] [NEW] [UBUNTU 20.04] Subiquity installer does not accept user-data generated after manual installation
Public bug reported:
I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.
After manual installation a user-data to repeat the process
automatically is stored in /var/log/installer/autoinstall-user-data.
However, it has two issues:
- there is no "version" entry, so Subiquity does not accept it at all:
curtin start subiquity/core_validation:
curtin finish subiquity/core_validation: 'version' is a required property
- when I add version: 1, I get the following error:
curtin start subiquity/Keyboard/load_autoinstall_data:
curtin finish subiquity/Keyboard/load_autoinstall_data: None is not of type
'string'
Failed validating 'type' in schema['properties']['toggle']:
{'type': 'string'}
On instance['toggle']:
None
And when I change this too I get the related issues with netplan and
storage configuration.
Kernel command line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/
User-data:
#cloud-config
autoinstall:
apt:
geoip: true
preserve_sources_list: false
primary:
- arches: [amd64, i386]
uri: http://archive.ubuntu.com/ubuntu
- arches: [default]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password:
/wjUJRFEEW5PA.CormpX2CYCxwoEAqGpB4sdIi8GgdJLd21tzNGDcZMDi0,
realname: user, username: user}
keyboard: {layout: us, toggle: null, variant: ''}
locale: en_US
network:
ethernets:
encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
nameservers:
addresses: [172.18.0.1]
version: 2
proxy: http://lnxproxy.lnxne.boe:3128
ssh:
allow-pw: true
authorized-keys: []
install-server: true
storage:
config:
- {device_id: 0.0.3695, blocksize: 4096, disk_layout: cdl, mode: quick,
preserve: false,
type: dasd, id: dasd-dasda}
- {ptable: vtoc, serial: 0X3695, path: /dev/dasda, wipe:
superblock-recursive,
preserve: false, name: '', grub_device: false, device_id: 0.0.3695, type:
disk,
id: disk-dasda}
- {device: disk-dasda, size: 22153265152, wipe: superblock, flag: '',
number: 1,
preserve: false, type: partition, id: partition-0}
- {fstype: ext4, volume: partition-0, preserve: false, type: format, id:
format-0}
- {device: format-0, path: /, type: mount, id: mount-0}
** Affects: ubuntu-z-systems
Importance: High
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Affects: subiquity (Ubuntu)
Importance: Undecided
Assignee: Canonical Foundations Team (canonical-foundations)
Status: New
** Tags: architecture-s39064 bugnameltc-185920 severity-high
targetmilestone-inin---
** Tags added: architecture-s39064 bugnameltc-185920 severity-high
targetmilestone-inin---
** 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/1879708
Title:
[UBUNTU 20.04] Subiquity installer does not accept user-data generated
after manual installation
Status in Ubuntu on IBM z Systems:
New
Status in subiquity package in Ubuntu:
New
Bug description:
I'm installing Ubuntu 20.04 with a nocloud-net installation source on
a z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.
After manual installation a user-data to repeat the process
automatically is stored in /var/log/installer/autoinstall-user-data.
However, it has two issues:
- there is no "version" entry, so Subiquity does not accept it at all:
curtin start subiquity/core_validation:
curtin finish subiquity/core_validation: 'version' is a required property
- when I add version: 1, I get the following error:
curtin start subiquity/Keyboard/load_autoinstall_data:
curtin finish subiquity/Keyboard/load_autoinstall_data: None is not of type
'string'
Failed validating 'type' in schema['properties']['toggle']:
{'type': 'string'}
On instance['toggle']:
None
And when I change this too I get the related issues with netplan and
storage configuration.
Kernel command line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
autoinstall
[Kernel-packages] [Bug 1870320] Re: [UBUNTU 18.04] zpcictl --reset - contribution for kernel
Thx for the verification - updating the tags...
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870320
Title:
[UBUNTU 18.04] zpcictl --reset - contribution for kernel
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* With zpci_disable() working, 'lockdep' detected a potential deadlock
(in the s390x zPCI subsystem).
* The deadlock is between recovering a PCI function via the
/sys/bus/pci/devices//recover attribute vs powering it off via
/sys/bus/pci/slots//power.
[Fix]
* Backport 1: https://launchpadlibrarian.net/479554961/0001-s390-pci-
Recover-handle-in-clp_set_pci_fn.patch
* Backport 2: https://launchpadlibrarian.net/478714295/0001-s390-pci-
Fix-possible-deadlock-in-recover_store.patch
[Test Case]
* It's best to (re-)test using the kernel's locking validator, also
known as 'lockdep'.
* Since this potential deadlock was identified by lockdep.
[Regression Potential]
* The regression potential can be considered as moderate, since:
* It is purely s390x specific code (arch/s390/include/asm/pci.h and
arch/s390/pci/{pci.c,pci_clp.c,pci_sysfs.c}).
* It only affects the zPCI, the s390x specific PCI code layer.
* PCI cards available for s390x are optional cards (RoCE and zEDC) and
not very wide-spread.
* The states between such a deadlock can happen (recover and power
off) are non standard and usually undesired states.
* The patches are upstream accepted since 5.6 and already landed in
eoan and focal.
[Other Info]
* Patches 17cdec960cf7 "s390/pci: Recover handle in clp_set_pci_fn()"
and 576c75e36c68 "s390/pci: Fix possible deadlock in recover_store()"
are upstream accepted since kernel 5.6, but they don't apply cleanly
on bionic master-next, hence backports are needed:
* 0001-s390-pci-Recover-handle-in-clp_set_pci_fn.patch is a backport
of 17cdec960cf776b20b1fb08c61babe591d51 17cdec960cf7 "s390/pci:
Recover handle in clp_set_pci_fn()"
* 0001-s390-pci-Fix-possible-deadlock-in-recover_store.patch is a
backport of 576c75e36c689bec6a940e807bae27291ab0c0de 576c75e36c68
"s390/pci: Fix possible deadlock in recover_store()"
* Both patches/commits already landed in focal (with LP 1863768) and in eoan
(with LP 1868324).
__
This Bug tracks the necessary backport for the Linux Kernel
to enable proper reset/recovery of PCI Functions in the error state.
There is a related fix to s390-tools but the relevant zpcictl command
is not part of Ubuntu 18.04
Upstream this includes the following commits:
In the Kernel:
17cdec960cf776b20b1fb08c61babe591d51 s390/pci: Recover handle in
clp_set_pci_fn()
Backport patch attached.
576c75e36c689bec6a940e807bae27291ab0c0de s390/pci: Fix possible deadlock in
recover_store()
applies cleanly but for the second a small backport change is necessary.
These fixes are already in 20.04 but need also be applied to 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1870320/+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 1879708] [NEW] [UBUNTU 20.04] Subiquity installer does not accept user-data generated after manual installation
You have been subscribed to a public bug:
I'm installing Ubuntu 20.04 with a nocloud-net installation source on a
z/VM guest. I'm currently limited to seeing installation output only
through webhook reporter, because I cannot access shell on the target
system during installation.
After manual installation a user-data to repeat the process
automatically is stored in /var/log/installer/autoinstall-user-data.
However, it has two issues:
- there is no "version" entry, so Subiquity does not accept it at all:
curtin start subiquity/core_validation:
curtin finish subiquity/core_validation: 'version' is a required property
- when I add version: 1, I get the following error:
curtin start subiquity/Keyboard/load_autoinstall_data:
curtin finish subiquity/Keyboard/load_autoinstall_data: None is not of type
'string'
Failed validating 'type' in schema['properties']['toggle']:
{'type': 'string'}
On instance['toggle']:
None
And when I change this too I get the related issues with netplan and
storage configuration.
Kernel command line:
cio_ignore=all,!condev,!0.0.3695,!0.0.bdf0-0.0.bdf2
url=http://bistro.lnxne.boe/ubuntu/UBUNTU20.04/ubuntu-20.04-live-server-s390x.iso
ip=172.18.76.38::172.18.0.1:255.254.0.0:m8330038.lnxne.boe:encbdf0:none:172.18.0.1
autoinstall ds=nocloud-net;s=http://t35lp37.lnxne.boe:8080/cfg/
User-data:
#cloud-config
autoinstall:
apt:
geoip: true
preserve_sources_list: false
primary:
- arches: [amd64, i386]
uri: http://archive.ubuntu.com/ubuntu
- arches: [default]
uri: http://us.ports.ubuntu.com/ubuntu-ports
identity: {hostname: m8330038, password:
/wjUJRFEEW5PA.CormpX2CYCxwoEAqGpB4sdIi8GgdJLd21tzNGDcZMDi0,
realname: user, username: user}
keyboard: {layout: us, toggle: null, variant: ''}
locale: en_US
network:
ethernets:
encbdf0:
addresses: [172.18.76.38/15]
gateway4: 172.18.0.1
nameservers:
addresses: [172.18.0.1]
version: 2
proxy: http://lnxproxy.lnxne.boe:3128
ssh:
allow-pw: true
authorized-keys: []
install-server: true
storage:
config:
- {device_id: 0.0.3695, blocksize: 4096, disk_layout: cdl, mode: quick,
preserve: false,
type: dasd, id: dasd-dasda}
- {ptable: vtoc, serial: 0X3695, path: /dev/dasda, wipe:
superblock-recursive,
preserve: false, name: '', grub_device: false, device_id: 0.0.3695, type:
disk,
id: disk-dasda}
- {device: disk-dasda, size: 22153265152, wipe: superblock, flag: '',
number: 1,
preserve: false, type: partition, id: partition-0}
- {fstype: ext4, volume: partition-0, preserve: false, type: format, id:
format-0}
- {device: format-0, path: /, type: mount, id: mount-0}
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-185920 severity-high
targetmilestone-inin---
--
[UBUNTU 20.04] Subiquity installer does not accept user-data generated after
manual installation
https://bugs.launchpad.net/bugs/1879708
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 1879707] [NEW] [UBUNTU 20.04] mke2fs dasd(fba), Failing CCW, default ERP has run out of retries and failed
You have been subscribed to a public bug: mke2fs,dasd(fba) guest edevices FBA,default ERP has run out of retries and failed,Failing CCW ---uname output--- xx - 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:27:18 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = IBM 3906 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- mke2fs to dasd(fba) devices Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. dasd(fba),Failing CCW,default ERP has run out of retries and failed between the following syslog events, mke2fs running, before mounting and starting IO to dasd(fba) devices May 14 14:33:32 ilabg13 root: ILAB_IO_FROM_MSDI_START May 14 14:48:34 ilabg13 root: ILAB_IO_FROM_MSDI_RUNNING ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185933 severity-medium targetmilestone-inin2004 -- [UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP has run out of retries and failed https://bugs.launchpad.net/bugs/1879707 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 1879690] Re: Docker registry doesn't stay up and keeps restarting
** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1879704] [NEW] [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
Public bug reported: Description will follow ** Affects: ubuntu-z-systems Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Incomplete ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Incomplete ** Tags: architecture-s39064 bugnameltc-185929 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-185929 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/1879704 Title: [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1879704/+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 1870995] Re: i8042: Warning: Keylock active
If WHAT doesn't affect normal usage? As all computers, the computer in question suffers various issues of varying degree of severity from time to time, starting with (luckily, extremely seldom) shutting itsself off without warning and ending with dozens of warning printfs scattered over dozens of log files. -- 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
@Mario Limonciello Sorry, I am a bit out of the loop. Does #61 solve the issue? And if so, are there negative aspects of blacklisting intel-hid? -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1870320] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-20 09:09 EDT---
Verified this is working as intended. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1870320
Title:
[UBUNTU 18.04] zpcictl --reset - contribution for kernel
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* With zpci_disable() working, 'lockdep' detected a potential deadlock
(in the s390x zPCI subsystem).
* The deadlock is between recovering a PCI function via the
/sys/bus/pci/devices//recover attribute vs powering it off via
/sys/bus/pci/slots//power.
[Fix]
* Backport 1: https://launchpadlibrarian.net/479554961/0001-s390-pci-
Recover-handle-in-clp_set_pci_fn.patch
* Backport 2: https://launchpadlibrarian.net/478714295/0001-s390-pci-
Fix-possible-deadlock-in-recover_store.patch
[Test Case]
* It's best to (re-)test using the kernel's locking validator, also
known as 'lockdep'.
* Since this potential deadlock was identified by lockdep.
[Regression Potential]
* The regression potential can be considered as moderate, since:
* It is purely s390x specific code (arch/s390/include/asm/pci.h and
arch/s390/pci/{pci.c,pci_clp.c,pci_sysfs.c}).
* It only affects the zPCI, the s390x specific PCI code layer.
* PCI cards available for s390x are optional cards (RoCE and zEDC) and
not very wide-spread.
* The states between such a deadlock can happen (recover and power
off) are non standard and usually undesired states.
* The patches are upstream accepted since 5.6 and already landed in
eoan and focal.
[Other Info]
* Patches 17cdec960cf7 "s390/pci: Recover handle in clp_set_pci_fn()"
and 576c75e36c68 "s390/pci: Fix possible deadlock in recover_store()"
are upstream accepted since kernel 5.6, but they don't apply cleanly
on bionic master-next, hence backports are needed:
* 0001-s390-pci-Recover-handle-in-clp_set_pci_fn.patch is a backport
of 17cdec960cf776b20b1fb08c61babe591d51 17cdec960cf7 "s390/pci:
Recover handle in clp_set_pci_fn()"
* 0001-s390-pci-Fix-possible-deadlock-in-recover_store.patch is a
backport of 576c75e36c689bec6a940e807bae27291ab0c0de 576c75e36c68
"s390/pci: Fix possible deadlock in recover_store()"
* Both patches/commits already landed in focal (with LP 1863768) and in eoan
(with LP 1868324).
__
This Bug tracks the necessary backport for the Linux Kernel
to enable proper reset/recovery of PCI Functions in the error state.
There is a related fix to s390-tools but the relevant zpcictl command
is not part of Ubuntu 18.04
Upstream this includes the following commits:
In the Kernel:
17cdec960cf776b20b1fb08c61babe591d51 s390/pci: Recover handle in
clp_set_pci_fn()
Backport patch attached.
576c75e36c689bec6a940e807bae27291ab0c0de s390/pci: Fix possible deadlock in
recover_store()
applies cleanly but for the second a small backport change is necessary.
These fixes are already in 20.04 but need also be applied to 18.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1870320/+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 1874056] Re: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter
First of all thanks for testing the PPA. I'm sure that helps in regard to the acceptance of the SRU. For the additional two patches it's best to open a separate LP ticket - and upstream acceptance is of course crucial, too. The common code change is quite critical (is it one of the two - or a third one?). I assume that you tried to make the needed modifications as small and limited as possible, clear and traceable. Since the these patches are based on one ones from above, I guess it's not possible to flag them upstream for an upstream release update - for 5.4 (at least the common code change)?! Please let me know the commit title and/or IDs. We have to have a deep look into it and a solid SRU justification -- 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/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: == [Impact] * Mellanox CX5 port multi-pathing is broken on s390x due to non- standard topology of PCI IDs (phys. and virtual) * The Mellanox Connect-X 5 PCI driver (mlx5) implements multi-path that can be used to combine multiple networking ports to improve performance and reliability. * For that purpose, the mlx5 driver combines PCI functions based on topology information (the function number) as determined by their PCI ID. * Currently the Linux on Z PCI bus does not reflect PCI topology information in the PCI ID. As a result, the mlx5 multi-path function is broken and cannot be activated. [Fix] * Backport 1: https://launchpadlibrarian.net/479699471/0001-s390-pci- Improve-handling-of-unset-UID.patch * Backport 2: https://launchpadlibrarian.net/479699482/0002-s390-pci- embedding-hotplug_slot-in-zdev.patch * Backport 3: https://launchpadlibrarian.net/479699492/0003-s390-pci- Expose-new-port-attribute-for-PCIe-function.patch * Backport 4: https://launchpadlibrarian.net/479699497/0004-s390-pci- adaptation-of-iommu-to-multifunction.patch * Backport 5: https://launchpadlibrarian.net/479700706/0005-s390-pci- define-kernel-parameters-for-PCI-multifunct.patch * Backport 6: https://launchpadlibrarian.net/479700712/0006-s390-pci- define-RID-and-RID-available.patch * Backport 7: https://launchpadlibrarian.net/479700739/0007-s390-pci- create-zPCI-bus.patch * Backport 8: https://launchpadlibrarian.net/479700769/0008-s390-pci- adapt-events-for-zbus.patch * Backport 9: https://launchpadlibrarian.net/479700786/0009-s390-pci- Handling-multifunctions.patch * Backport 10: https://launchpadlibrarian.net/479700794/0010-s390-pci- Do-not-disable-PF-when-VFs-exist.patch * Backport 11: https://launchpadlibrarian.net/479700798/0011-s390-pci- Documentation-for-zPCI.patch * Backport 12: https://launchpadlibrarian.net/479700799/0012-s390-pci- removes-wrong-PCI-multifunction-assignment.patch [Test Case] * Prepare an IBM z13 or LinuxONE III (or newer) system with two or more RoCE Express PCI 2(.1) adapters. * Assign the adapters (and it's virtual functions) to an LPAR. * Verify whether the physical and virtual functions are grouped in arbitrary order or in consecutive order - physical first (for example with lspci -t ...) [Regression Potential] * The regression potential can be considered as moderate, since: * It is purely s390x specific code (arch/s390/* drivers/iommu/s390-iommu.c and drivers/pci/hotplug/s390_pci_hpc.c - and some doc adjustments, too). * It largely affects zPCI, the s390x specific PCI code layer. * PCI cards available for s390x are optional cards (RoCE and zEDC) and not very wide-spread. * The situation described above affects the RoCE adapters only (Mellanox based). * The patches are also upstream accepted and available via linux-next, but to apply them to focal kernel 5.4 the above backports are needed. * However, the code is modified by several patches (12), hence there is a chance to break zPCI with them. * For upfront testing a PPA got created with a focal (master-next) kernel that incl. all the above patches. __ Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to
[Kernel-packages] [Bug 1879704] [NEW] [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices
You have been subscribed to a public bug: Description will follow ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185929 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] s390x/pci: implement linking between PF and VF for multifunction devices https://bugs.launchpad.net/bugs/1879704 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 1874062] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-20 09:04 EDT--- I just verified that this now works on the Ubuntu 20.04 proposed kernel. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874062 Title: [UBUNTU 20.04] Performance floating interrupt Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: With the introduction of CPU directed interrupts the kernel parameter pci=force_floating was introduced to fall back to the previous behavior using floating irqs. Furthermore this fallback is used on machines lacking support for directed interrupts. However we were still setting the affinity in that case, both in __irq_alloc_descs() and via the irq_set_affinity callback in struct irq_chip. This setting of the affinity leads to a performance regression in streaming workloads which can be seen with e.g. by an iperf streaming test between two LPARs using ConnectX-5 based nics. In some tests the performance would drop to 20% of the performance with older kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874062/+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 1874058] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-20 08:55 EDT--- Verified working with proposed kernel! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874058 Title: [UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: Using the mlx5 device driver on Ubuntu 20.04 (beta), the alloc_pages_nodemask code generates a stack trace when initializing a device. The driver tries to allocate more contiguous memory than is allowed by the platform specific FORCE_MAX_ZONEORDER setting. FORCE_MAX_ZONEORDER on s390x: 9 FORCE_MAX_ZONEORDER on other platforms: 11 or more This issue only occurs on ConnectX5 devices because the mlx5_fw_tracer code is only used for physical functions. A fix for this has recently been pulled into David Miller's net tree as part of a series of Mellanox fixes: https://lore.kernel.org/netdev/20200420213606.44292-1-sae...@mellanox.com/ It hasn't landed in Linus' tree yet though To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874058/+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 1874057] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-20 08:49 EDT---
Verified by IBM
--
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/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
than configured via CONFIG_PCI_NR_FUNCTIONS
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* PCI Functions with UIDs >128 are currently not accounted correctly
in the s390x/pci (zPCI) code.
* Furthermore, the code allows that more than CONFIG_PCI_NR_FUNCTIONS
are created.
* This can lead to issues with data structures which were only
allocated for CONFIG_PCI_NR_FUNCTIONS.
[Fix]
* https://launchpadlibrarian.net/478235080/0001-s390-pci-Fix-
zpci_alloc_domain-over-allocation.patch
[Test Case]
* Set the kernel parameter CONFIG_PCI_NR_FUNCTIONS to a specific
(reasonablly low) number.
* And check if more PCI functions can be created than specified by
CONFIG_PCI_NR_FUNCTIONS (e.g. using a RoCE adapter) and watch for
kernel message 'Adding PCI function ... failed'
[Regression Potential]
* There is regression potential can be considered as low, since:
* the zPCI cards are less wide spread than for example ccw adapters on
s390x
* the fix got already upstream accepted in 5.7, hence upstream
reviewed, too
* the modifications span just two files and both are s390x arch
specific
[Other Info]
* the above patch-file is based on commit
969ae01bab2fe938b4c8324836038b5ac1c78fac ("s390/pci: Fix
zpci_alloc_domain() over allocation"), but this backport was needed
for getting this applied to focal master-next
* and this patch got upstream accepted with kernel v5.7-rc1, hence on
the long term it should be in 'gorilla'
__
PCI Functions with UIDs >128 are currently not accounted correctly in
the s390x/pci code. Furthermore, the code allows that more than
CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
This has been fixed in the following upstream commit:
969ae01bab2fe938b4c8324836038b5ac1c78fac
("s390/pci: Fix zpci_alloc_domain() over allocation")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874057/+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 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670/+attachment/5374715/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
** Attachment added: "dpkg-l.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670/+attachment/5374716/+files/dpkg-l.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
** Attachment added: "sosreport.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670/+attachment/5374717/+files/sosreport.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/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
I have uploaded the requested information. I reproduced the crash to make sure the logs contains relevant information. The crash was reproduced by "vim /var/log/syslog" and hold down the down-arrow. The sosreport output may not be what you want however, as no plugins are enabled. -- 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/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1878670] Re: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308]
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878670/+attachment/5374714/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: [Ice Lake] WARN_ON(intel_wait_for_register(dev_priv, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1)) [from i915/intel_runtime_pm.c:308] Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1879690] 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 1879690 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 ** Changed in: linux (Ubuntu Eoan) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1876875] Re: Improve download-signed script to support current & grub2
linux-signed patch looks good to apw. Will start backporting those changes to grub2-signed and s390-tools-signed. ** Changed in: linux-signed (Ubuntu) Status: New => In Progress ** Description changed: [Impact] - * Improve and generalise download-signed script to allow using it with any signed binaries we care about - * Add support to download simply the most current version - * Add support to download /uefi/ signed binaries - * Clean up arg parsing, add help, drop unused statements & imports. + * Improve and generalise download-signed script to allow using it with any signed binaries we care about + * Add support to download simply the most current version + * Add support to download /uefi/ signed binaries + * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] - * Test downloading signed kernel works with public & private archives - * Test that rebuilt signed .debs are the same + * Test downloading signed kernel works with public & private archives + * Test that rebuilt signed .debs are the same [Regression Potential] - * This is a built time script, as long the binaries are downloaded & + * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] - - * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. + + * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. + * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1876875 Title: Improve download-signed script to support current & grub2 Status in grub2-signed package in Ubuntu: New Status in linux-signed package in Ubuntu: In Progress Status in s390-tools-signed package in Ubuntu: New Bug description: [Impact] * Improve and generalise download-signed script to allow using it with any signed binaries we care about * Add support to download simply the most current version * Add support to download /uefi/ signed binaries * Clean up arg parsing, add help, drop unused statements & imports. [Test Case] * Test downloading signed kernel works with public & private archives * Test that rebuilt signed .debs are the same [Regression Potential] * This is a built time script, as long the binaries are downloaded & packaged up the same, there is no end-user facing impact. [Other Info] * With these changes, download-signed script can be used by s390-tools-signed & grub2-signed, as well as all the kernels. * This is needed to support resigning with different keys for different ubuntu products. For example, UC20 uses the same grub binaries, but wants an additional trustpath to UC20 CA for grade:secured core images. At the moment creating such a signature is only possible via a round-trip in a PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876875/+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 1868568] Re: systemctl hibernate doesn't restore
Are things like resume, resume_offset are properly set? -- 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/1868568 Title: systemctl hibernate doesn't restore Status in linux package in Ubuntu: Confirmed Bug description: regression: systemctl suspend works in bionic but not in focal. in bionic the network resumes properly, in focal, it doesn't. also, systemctl hibernate, in both bionic and focal, seems to write to disk, and shuts down, but in both systems, boots up fresh, without restoring. fwiw bionic was installed by free geek before purchase, likely via ubuntu iso. focal was installed by me via lubuntu iso. might there perchance be any special setup needed? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 244.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Mon Mar 23 09:12:59 2020 InstallationDate: Installed on 2020-03-15 (7 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) MachineType: LENOVO 20C6008SUS ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/fl/boot/vmlinuz ro root=UUID=cb3d9931-e086-4632-8216-1f0aab276d73 subroot=/fl panic=30 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868568/+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 1879393] Re: Delayed failure in Genesys USB3 SD card reader
Started the bisection; this may take several days to finish (each "good" result takes many hours to verify given that the problem sometimes didn't manifest for several hours). I'll update the ticket when I've got some further results. -- 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/1879393 Title: Delayed failure in Genesys USB3 SD card reader Status in linux package in Ubuntu: Confirmed Bug description: I have a "UGreen USB3 Hub/SD card reader" which worked reliably under Ubuntu Xenial for many months. Recently, I re-installed the machine it was attached to with a fresh install of Ubuntu Focal. When initially booted, the device works perfectly (at least, the USB3 ports and SD card reader do; those are the only ports I use on it). However, after some period of time I inevitably find the device has stopped working, and dmesg is flooded with repeats of the following block of messages (I include several copies below so the typical time-delay between repeats can be observed): [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39826.850677] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39826.938742] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39859.618979] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39859.706965] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd The delay before failure (and these messages appearing) is highly variable. Sometimes it's within a couple of minutes of booting the machine; sometimes the device works happily for a couple of hours before failure. I've found that simply replugging the device (temporarily) solves the issue, but obviously I'd prefer the device to be as reliable as it was under the Xenial kernel. This may be related to LP: #1798979 which features extremely similar log messages on failure, but the symptoms are ever so slightly different (no CPU spike, no blinking LED), as is the model of card reader, hence why I've filed a separate bug. I'll add an apport report after filing this, but I should add there are multiple card-readers on this machine (my work involves raspberry pis, so I often find myself re-writing cards in bulk :). The specific one with the issue is listed as follows in the lsusb output: Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and microSDXC CardReader The other card reader listed in that output (realtek) is a separate device with no issues. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-09 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=cdabc2c5-6b02-4784-ba20-79dcc57ec8f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/09/2012 dmi.bios.vendor:
[Kernel-packages] [Bug 1874057] Re: [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions than configured via CONFIG_PCI_NR_FUNCTIONS
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874057
Title:
[UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
than configured via CONFIG_PCI_NR_FUNCTIONS
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* PCI Functions with UIDs >128 are currently not accounted correctly
in the s390x/pci (zPCI) code.
* Furthermore, the code allows that more than CONFIG_PCI_NR_FUNCTIONS
are created.
* This can lead to issues with data structures which were only
allocated for CONFIG_PCI_NR_FUNCTIONS.
[Fix]
* https://launchpadlibrarian.net/478235080/0001-s390-pci-Fix-
zpci_alloc_domain-over-allocation.patch
[Test Case]
* Set the kernel parameter CONFIG_PCI_NR_FUNCTIONS to a specific
(reasonablly low) number.
* And check if more PCI functions can be created than specified by
CONFIG_PCI_NR_FUNCTIONS (e.g. using a RoCE adapter) and watch for
kernel message 'Adding PCI function ... failed'
[Regression Potential]
* There is regression potential can be considered as low, since:
* the zPCI cards are less wide spread than for example ccw adapters on
s390x
* the fix got already upstream accepted in 5.7, hence upstream
reviewed, too
* the modifications span just two files and both are s390x arch
specific
[Other Info]
* the above patch-file is based on commit
969ae01bab2fe938b4c8324836038b5ac1c78fac ("s390/pci: Fix
zpci_alloc_domain() over allocation"), but this backport was needed
for getting this applied to focal master-next
* and this patch got upstream accepted with kernel v5.7-rc1, hence on
the long term it should be in 'gorilla'
__
PCI Functions with UIDs >128 are currently not accounted correctly in
the s390x/pci code. Furthermore, the code allows that more than
CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.
This has been fixed in the following upstream commit:
969ae01bab2fe938b4c8324836038b5ac1c78fac
("s390/pci: Fix zpci_alloc_domain() over allocation")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874057/+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 1876859] Re: Support DMIC micmute LED on HP platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876859 Title: Support DMIC micmute LED on HP platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Incomplete Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] DMIC micmute LED on HP platforms doesn't work. [Fix] Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to control micmute. [Test] After applying the fix, micmute LED can correctly indicate the status of micmute. [Regression Potential] Low. For now it only affects one platform, and it doesn't touch any core part of the subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1876859/+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 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
Hi Seth, I've upload a .4 - it may add a lot more debug but it will allow us to see the object type that is failing before the crash. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: New Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: New Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.637938] RIP: 0033:0x7fc305a905d7 [ 967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 0010 [ 967.637943]
[Kernel-packages] [Bug 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad
Still broken in the newer 4.15.0-101-generic kernel. But that has been somewhat expected, see comment #32 -- 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/1875916 Title: upgrading to 4.15.0-99-generic breaks the sound and the trackpad Status in linux package in Ubuntu: Confirmed Bug description: I am using kubuntu LTS 18.04. This morning I was promped to update the kernel to the 4.15.0-99-generic. After the upgrade I did not manage to get any sound. I checked everything, pavucontrol, alsamix, everything was in order, the streams showed as if they were playing, however I couldn't get any sound from the speakers headphones and I could not get any sound recorded either. I then rebooted with the previous version of the Kernel, and have my sound back without doing anything at all. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba InstallationDate: Installed on 2019-01-29 (455 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. wlp108s0 no wireless extensions. MachineType: Dell Inc. Latitude 7390 2-in-1 Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-99-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/27/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0YNG30 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7390 2-in-1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+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 1876645] Re: Unable to handle kernel pointer dereference in virtual kernel address space on Eoan
That's an unfortunate typo -- 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/1876645 Title: Unable to handle kernel pointer dereference in virtual kernel address space on Eoan Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Issue spotted on Eoan zVM / LPAR It looks like this happens when running the ubunut_fan_smoke_test (jenkins job hang with this one) [ 1225.137764] docker0: port 1(veth2fda0c6) entered blocking state [ 1225.137767] docker0: port 1(veth2fda0c6) entered disabled state [ 1225.138023] device veth2fda0c6 entered promiscuous mode [ 1225.148523] Unable to handle kernel pointer dereference in virtual kernel address space [ 1225.148529] Failing address: 6f766c5f646f5000 TEID: 6f766c5f646f5803 [ 1225.148531] Fault in home space mode while using kernel ASCE. [ 1225.148533] AS:00070d94c007 R3:0024 [ 1225.148575] Oops: 0038 ilc:3 [#1] SMP [ 1225.148578] Modules linked in: veth xt_nat vxlan ip6_udp_tunnel udp_tunnel nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter unix_diag sctp cuse vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vsock dccp_ipv4 dccp algif_rng aegis128 aegis128l aegis256 morus1280 morus640 algif_aead anubis fcrypt khazad seed sm4_generic tea md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic algif_hash blowfish_generic blowfish_common cast5_generic salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher af_alg xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat nf_conntrack [ 1225.148622] nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx4_ib ib_uverbs mlx4_en ptp ib_core pps_core pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 qeth_l2 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 1225.148711] CPU: 4 PID: 161930 Comm: dockerd Tainted: P O 5.3.0-52-generic #46-Ubuntu [ 1225.148714] Hardware name: IBM 2964 N63 400 (LPAR) [ 1225.148716] Krnl PSW : 0704d0018000 03ff808e972a (ovl_open_realfile+0x4a/0x148 [overlay]) [ 1225.148734]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 1225.148736] Krnl GPRS: 0064 6f766c5f646f5f6d 0007a14ac300 0003a5df6600 [ 1225.148738]8000 0001 0003 000372e45278 [ 1225.148740]03ff808ea508 000304048000 0005c7f32b68 00064a2ab900 [ 1225.148742]0003a5df6600 03ff808f31d8 03ff808e971a 03e009c0faf8 [ 1225.148749] Krnl Code: 03ff808e971a: a59a0404 oilh%r9,1028 03ff808e971e: e310f0c4 lg %r1,192(%r15) #03ff808e9724: e31010680004 lg %r1,104(%r1) >03ff808e972a: e3101064 lg %r1,96(%r1) 03ff808e9730: b9040082 lgr %r8,%r2 03ff808e9734: c21c6a656a62 cgfi %r1,1785031266 03ff808e973a: b9140039 lgfr%r3,%r9 03ff808e973e: e3100344 lg %r1,832 [ 1225.148766] Call Trace: [ 1225.148769] ([<>] 0x0) [ 1225.148774] [<03ff808ea582>] ovl_open+0x7a/0xc0 [overlay] [ 1225.148780] [<00070cbf2c04>] do_dentry_open+0x1fc/0x3b0 [ 1225.148784] [<00070cc0afd2>] do_last+0x1ba/0x970 [ 1225.148786] [<00070cc0b80e>] path_openat+0x86/0x2b8 [ 1225.148788] [<00070cc0cea4>] do_filp_open+0x7c/0xf8 [ 1225.148791] [<00070cbf4b5a>] do_sys_open+0x19a/0x2c8 [ 1225.148798] [<00070d1ebca8>] system_call+0xdc/0x2c8 [ 1225.148800] Last Breaking-Event-Address: [ 1225.148802] [<00070d1ed210>]
[Kernel-packages] [Bug 1879689] 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 1879689 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 -- 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/1879689 Title: No audio on Atom X5-z8350 Status in linux package in Ubuntu: Incomplete Bug description: I've made some research and didn't work for me. I have an Atom X5-z8350 and audio is not working at all, drivers seem to be installed correctly but no audio is outputting. Many thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879689/+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 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Secure Boot need to be disabled to load unsigned kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+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 1879690] [NEW] Docker registry doesn't stay up and keeps restarting
Public bug reported: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Description changed: - Affected kernels: + Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ - -v $auth_folder:/auth \ - -e "REGISTRY_AUTH=htpasswd" \ - -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ - -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ -registry:2 + -v $auth_folder:/auth \ + -e "REGISTRY_AUTH=htpasswd" \ + -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ + -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ + registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: - docker ps + docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE
[Kernel-packages] [Bug 1879402] Re: [amdgpu] Proper monitor resolution/refresh rate not available
Yes, the EDID needs to be read from DRM drivers, then userspace will use the EDID exported from DRM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879402 Title: [amdgpu] Proper monitor resolution/refresh rate not available Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272g. Things that I unsuccesfully tried to get a proper resolution: -Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source -Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor) -Using "GRUB_GFXMODE" config in grub (no change) -Searching through logs, only useleful thing I found was in the Xorg log: [12.117] (II) AMDGPU(0): EDID for output DisplayPort-0 [12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) -In Windows the resolution works fine -Both GPUs work fine with a different monitor I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.4.0-050400-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 22:16:58 2020 DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36] InstallationDate: Installed on 2019-11-26 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A34 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.LQ dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 PC MATE (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A34 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 26 22:01:15 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877889] Re: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
The regular kernel has since updated to 5.4.0-31.35, but I can confirm that the hang on boot still occurs. I haven't heard back in a few days on whether there is something else you would like me to try. Like I said previously the drm-tip kernel didn't boot at all for me (invalid signature error). Anecdotally, I feel like the hang on boot is more common when the laptop is running off battery only (no AC). I hope that's helpful. New kernel version: $ uname -a Linux len 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version Linux version 5.4.0-31-generic (buildd@lgw01-amd64-059) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 $ cat /proc/version_signature Ubuntu 5.4.0-31.35-generic 5.4.34 -- 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/1877889 Title: Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I see occasional hangs on boot. The hangs occur after entering the LUKS decryption password for the root filesystem, and before the login screen is displayed. The "/boot" filesystem is not encrypted, so the initramfs is loading fine etc. The hangs are intermittent. Sometimes I don't see a hang for 10+ boots in a row, and sometimes I'll get a hang 5 times in a row. When the hang occurs the boot splash screen is visible (not the login screen). The system is still responsive to SysRq keys, so I can somewhat safely issue S+U+S+B sequence to try booting again without corrupting much. I have tried removing the "quiet splash" kernel parameters that are enabled by default on Ubuntu desktop to see if any interesting messages occur that way. So far however I have not experienced a hang with "quiet splash" removed. This system is a Lenovo E595 (Ryzen 3500U) with the latest BIOS from Lenovo installed (v1.16), running Ubuntu 20.04 desktop. I am submitting this bug using `ubuntu-bug linux-image-generic`, but I don't know for sure if this is a kernel issue or something else. I suspect my bug might be the same as this one already reported ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594 ), but I'm filing my own anyway as a means to capture more details of my system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: paul 2507 F pulseaudio /dev/snd/controlC0: paul 2507 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 20:09:53 2020 MachineType: LENOVO 20NFCTO1WW ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=f466d4ea-c251-4721-b071-bd70c82f00e1 ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (15 days ago) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+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 1878479] Re: HP-OMEN 17t bc0xxx don't work sound and microphone
*** This bug is a duplicate of bug 1874698 *** https://bugs.launchpad.net/bugs/1874698 Check out the bug https://bugzilla.kernel.org/show_bug.cgi?id=206085 without Hdmi.conf did not work ** Bug watch added: Linux Kernel Bug Tracker #206085 https://bugzilla.kernel.org/show_bug.cgi?id=206085 -- 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/1878479 Title: HP-OMEN 17t bc0xxx don't work sound and microphone Status in linux package in Ubuntu: Incomplete Bug description: This problem has been resolved for kernel 5.7. * https://bugzilla.kernel.org/show_bug.cgi?id=206085 But I can’t work on it because I have more problems with the constant relogin https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878193 How to solve this problem with kernel trust supported by ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878479/+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 1878479] Re: HP-OMEN 17t bc0xxx don't work sound and microphone
*** This bug is a duplicate of bug 1874698 *** https://bugs.launchpad.net/bugs/1874698 Yes I replaced -- 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/1878479 Title: HP-OMEN 17t bc0xxx don't work sound and microphone Status in linux package in Ubuntu: Incomplete Bug description: This problem has been resolved for kernel 5.7. * https://bugzilla.kernel.org/show_bug.cgi?id=206085 But I can’t work on it because I have more problems with the constant relogin https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878193 How to solve this problem with kernel trust supported by ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878479/+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 1878007] Re: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off
Hmm, please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- 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/1878007 Title: Ubuntu 20.04 freeze on Dell inspiron 7373 when screen is turned off Status in linux package in Ubuntu: Incomplete Bug description: This issue is happening with Ubuntu 18.04 and 20.04 in a Dell Inspiron 7373. When the screen is turned off (so, the suspend or screen lock features are affected), the system freeze and I need to force the laptop turn off and on again. There are some cases when it turn off the screen without issues, but most of the time it freezes. Even "SysRq REISUB" does not work for rebooting when system crash. I can reproduce the issue using `xset dpms force off`. Initially this bug report was filled thinking it was a suspend issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144 Syslog or systemd journal does not provide any error information about the crash. "lsb_release -rd" output: Description: Ubuntu 20.04 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cccaballero 2023 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-06-09 (344 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7373 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d8203f53-c2e5-4934-8616-0a71507c9190 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-02 (16 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0JW0D6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd09/06/2019:svnDellInc.:pnInspiron7373:pvr:rvnDellInc.:rn0JW0D6:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7373 dmi.product.sku: 07EB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878007/+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 1878315] Re: Ubuntu is unable to detect my GPU
Can you attach the following, please? 1) the output of the following command: apt-cache policy ubuntu-drivers-common 2) the following file: /var/log/gpu-manager.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878315 Title: Ubuntu is unable to detect my GPU Status in linux package in Ubuntu: Incomplete Bug description: I have an MSI laptop which was working fine with Ubuntu 18, but I decided to upgrade. It has one of these dual graphics setups, which and Intel HD 630 and a NVIDIA GTX 1060 6GB. On Ubuntu 18, I simply get the NVIDIA GPU to work by selecting its drivers on the "Additional Drivers" tab under "Software and Updates", but on this version of Ubuntu, my GPU doesn't appear there any more. Also, if I type this in the console: $ lspci | grep -i --color 'vga\|3d\|2d' This is the only line I get: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) Just in case, my laptop model is this: https://es.msi.com/Laptop /GL72VR-7RFX Any help would be appreciated. Thanks. I forgot to say that I also have Windows on dual boot and the GPU works perfectly fine there. Also, it is not disabled on the BIOS or something like that. I don't think that is even possible on my BIOS either. $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) DeviceName: Onboard IGD Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 Kernel driver in use: i915 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) 03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10) 04:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller Looking at the output, I don't know why it says that my processor is an Intel Xeon... it's actually a i7-7700HQ. Here is a thread on the forum with more people experiencing this issue: https://ubuntuforums.org/showthread.php?t=2443007 Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel28254 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 03:56:36 2020 InstallationDate: Installed on 2018-10-02 (588 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Micro-Star International Co., Ltd. GL72VR 7RFX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=97a38a40-3df8-4990-a5bf-b879b481309b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-08 (4 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E179BIMS.312 dmi.board.asset.tag: Default string dmi.board.name: MS-179B dmi.board.vendor: Micro-Star International Co., Ltd.
[Kernel-packages] [Bug 1862159] Re: Networking through Thunderbolt 3 Gen 2 stops working after a while
Great, let's close it. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1862159 Title: Networking through Thunderbolt 3 Gen 2 stops working after a while Status in linux package in Ubuntu: Fix Released Bug description: After booting into 5.3.0-26 on my Lenovo X390, it has started to loose network connection when connected to the Thunderbolt 3 Gen 2 dock after a while. It varies how long it takes, but anywhere from quite fast after boot to several hours of uptime. Suddenly no traffic goes through the interface in the dock, but the device seems to be up. Enabling wifi after it happens works fine, but unselecting "Enable Networking" in network manager, or quitting it, makes the whole computer hang (can move mouse, but no input from keyboard is registered anymore, or so it seems at least) Rebooting after it happens requires hard reset, as nothing happens after Network Manager should stop. Probably related to the patch introduces in LP: #1827961 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: peder 3620 F pulseaudio /dev/snd/controlC1: peder 3620 F pulseaudio /dev/snd/pcmC1D0p: peder 3620 F...m pulseaudio /dev/snd/controlC0: peder 3620 F pulseaudio CurrentDesktop: i3 Date: Thu Feb 6 12:11:54 2020 InstallationDate: Installed on 2019-10-31 (98 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q1S6WC00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET77W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q1S6WC00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET77W(1.55):bd08/13/2019:svnLENOVO:pn20Q1S6WC00:pvrThinkPadX390:rvnLENOVO:rn20Q1S6WC00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q1S6WC00 dmi.product.sku: LENOVO_MT_20Q1_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862159/+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 1879689] [NEW] No audio on Atom X5-z8350
Public bug reported: I've made some research and didn't work for me. I have an Atom X5-z8350 and audio is not working at all, drivers seem to be installed correctly but no audio is outputting. Many thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1879689 Title: No audio on Atom X5-z8350 Status in linux package in Ubuntu: New Bug description: I've made some research and didn't work for me. I have an Atom X5-z8350 and audio is not working at all, drivers seem to be installed correctly but no audio is outputting. Many thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879689/+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 1879688] [NEW] shiftfs: fix btrfs snapshot deletion
Public bug reported: SRU Justification Impact: Stéphane discovered a problem during NorthSec which makes heavy use of shiftfs. In containers with a btrfs root filesystem that make use of shiftfs userns root is not able to delete subvolumes that have been created by another users which it would be able to do otherwise. This makes it impossible for LXD to delete nested containers. To reproduce this as root in the container: btrfs subvolume create my-subvol chown 1000:1000 my-subvol btrfs subvolume delete my-subvol The deletion will fail when it should have succeeded. Fix: For improved security we drop all capabilities before we forward btrfs ioctls in shiftfs. To fix the above problem we can retain the CAP_DAC_OVERRIDE capability only if we are userns root. Regression Potential: Limited to shiftfs. Even though we drop all capabilities in all capability sets we really mostly care about dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained in the underlay would allow you to list subvolumes you shouldn't be able to list. This fix only retains CAP_DAC_OVERRIDE and only for the deletion of subvolumes and only by userns root. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Christian Brauner (cbrauner) Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- 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/1879688 Title: shiftfs: fix btrfs snapshot deletion Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification Impact: Stéphane discovered a problem during NorthSec which makes heavy use of shiftfs. In containers with a btrfs root filesystem that make use of shiftfs userns root is not able to delete subvolumes that have been created by another users which it would be able to do otherwise. This makes it impossible for LXD to delete nested containers. To reproduce this as root in the container: btrfs subvolume create my-subvol chown 1000:1000 my-subvol btrfs subvolume delete my-subvol The deletion will fail when it should have succeeded. Fix: For improved security we drop all capabilities before we forward btrfs ioctls in shiftfs. To fix the above problem we can retain the CAP_DAC_OVERRIDE capability only if we are userns root. Regression Potential: Limited to shiftfs. Even though we drop all capabilities in all capability sets we really mostly care about dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained in the underlay would allow you to list subvolumes you shouldn't be able to list. This fix only retains CAP_DAC_OVERRIDE and only for the deletion of subvolumes and only by userns root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879688/+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 1862159] Re: Networking through Thunderbolt 3 Gen 2 stops working after a while
Seems to be working... worked for 6.5 hours (until i powered down) after booting into 5.4.0-31-generic yesterday. No crashes yet today (4:20 since boot). -- 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/1862159 Title: Networking through Thunderbolt 3 Gen 2 stops working after a while Status in linux package in Ubuntu: Incomplete Bug description: After booting into 5.3.0-26 on my Lenovo X390, it has started to loose network connection when connected to the Thunderbolt 3 Gen 2 dock after a while. It varies how long it takes, but anywhere from quite fast after boot to several hours of uptime. Suddenly no traffic goes through the interface in the dock, but the device seems to be up. Enabling wifi after it happens works fine, but unselecting "Enable Networking" in network manager, or quitting it, makes the whole computer hang (can move mouse, but no input from keyboard is registered anymore, or so it seems at least) Rebooting after it happens requires hard reset, as nothing happens after Network Manager should stop. Probably related to the patch introduces in LP: #1827961 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: peder 3620 F pulseaudio /dev/snd/controlC1: peder 3620 F pulseaudio /dev/snd/pcmC1D0p: peder 3620 F...m pulseaudio /dev/snd/controlC0: peder 3620 F pulseaudio CurrentDesktop: i3 Date: Thu Feb 6 12:11:54 2020 InstallationDate: Installed on 2019-10-31 (98 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20Q1S6WC00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 08/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET77W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Q1S6WC00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2JET77W(1.55):bd08/13/2019:svnLENOVO:pn20Q1S6WC00:pvrThinkPadX390:rvnLENOVO:rn20Q1S6WC00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X390 dmi.product.name: 20Q1S6WC00 dmi.product.sku: LENOVO_MT_20Q1_BU_Think_FM_ThinkPad X390 dmi.product.version: ThinkPad X390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862159/+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 1870995] Re: i8042: Warning: Keylock active
Nothing to worry about if it doesn't affect normal usage. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+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 1878899] Re: Call trace from __video_do_ioctl
Which camera was in use? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1878899 Title: Call trace from __video_do_ioctl Status in linux package in Ubuntu: Incomplete Bug description: [92420.303133] [ cut here ] [92420.303141] WARNING: CPU: 2 PID: 259541 at drivers/media/v4l2-core/v4l2-ioctl.c:1069 v4l_querycap+0x8f/0xa0 [videodev] [92420.303141] Modules linked in: btrfs xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs gspca_zc3xx joydev snd_seq_dummy iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc iptable_filter bpfilter v4l2loopback(OE) binfmt_misc nls_iso8859_1 uvcvideo gspca_vc032x gspca_main videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_usb_audio snd_usbmidi_lib mc snd_seq_midi snd_seq_midi_event snd_rawmidi edac_mce_amd kvm_amd ccp snd_hda_codec_realtek snd_seq snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_seq_device snd_pcm input_leds serio_raw k10temp fam15h_power snd_timer snd soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage dm_crypt amdgpu amd_iommu_v2 gpu_sched hid_generic usbhid hid crct10dif_pclmul crc32_pclmul [92420.303167] ghash_clmulni_intel radeon i2c_algo_bit ttm aesni_intel drm_kms_helper crypto_simd syscopyarea cryptd sysfillrect sysimgblt glue_helper fb_sys_fops ahci libahci i2c_piix4 drm r8169 realtek video [92420.303174] CPU: 2 PID: 259541 Comm: teams Tainted: GW OE 5.4.0-29-lowlatency #33-Ubuntu [92420.303175] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./G1.Sniper A88X-CF, BIOS F7 01/08/2014 [92420.303182] RIP: 0010:v4l_querycap+0x8f/0xa0 [videodev] [92420.303183] Code: 00 00 80 48 b9 00 00 20 00 00 00 20 00 48 0b 4b 54 21 d6 39 f2 75 13 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b eb d0 <0f> 0b 48 89 4b 54 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 [92420.303184] RSP: 0018:b4aa44dd7c78 EFLAGS: 00010202 [92420.303186] RAX: RBX: b4aa44dd7d88 RCX: 8520800185208001 [92420.303187] RDX: 85008003 RSI: 85008001 RDI: [92420.303188] RBP: b4aa44dd7ca0 R08: R09: 000a [92420.303188] R10: R11: R12: 994f4e421000 [92420.303189] R13: 994f4de6bf00 R14: 994f4c191940 R15: c0f2e360 [92420.303191] FS: 7f47f2ffd700() GS:994f5fb0() knlGS: [92420.303192] CS: 0010 DS: ES: CR0: 80050033 [92420.303193] CR2: 7f482c0e1000 CR3: 0003d0084000 CR4: 000406e0 [92420.303194] Call Trace: [92420.303201] __video_do_ioctl+0x1a7/0x410 [videodev] [92420.303204] ? default_send_IPI_single+0x20/0x40 [92420.303206] ? resched_curr+0x62/0xe0 [92420.303213] video_usercopy+0x2ad/0x690 [videodev] [92420.303220] ? v4l_s_fmt+0x670/0x670 [videodev] [92420.303224] ? wake_up_q+0x40/0x70 [92420.303230] video_ioctl2+0x15/0x20 [videodev] [92420.303237] v4l2_ioctl+0x4c/0x60 [videodev] [92420.303238] do_vfs_ioctl+0x405/0x660 [92420.303240] ? __fget+0x77/0xa0 [92420.303242] ksys_ioctl+0x67/0x90 [92420.303244] __x64_sys_ioctl+0x1a/0x20 [92420.303246] do_syscall_64+0x57/0x190 [92420.303248] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [92420.303249] RIP: 0033:0x7f489773737b [92420.303251] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [92420.303252] RSP: 002b:7f47f2ff77e8 EFLAGS: 0246 ORIG_RAX: 0010 [92420.303254] RAX: ffda RBX: 7f4824026900 RCX: 7f489773737b [92420.303255] RDX: 7f47f2ff78b0 RSI: 80685600 RDI: 0046 [92420.303256] RBP: 80685600 R08: R09: 5645ec03ee68 [92420.303257] R10: 0048 R11: 0246 R12: 0046 [92420.303258] R13: 7f47f2ff78b0 R14: 0015 R15: 7f485b666039 [92420.303260] ---[ end trace 6e9a5041142fdaab ]--- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-lowlatency 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 12:52:50 2020 HibernationDevice: RESUME=UUID=2ac5f511-9e86-402d-b41b-405dabdb7861 InstallationDate: Installed on 2014-04-14
[Kernel-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Confirmed Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: Confirmed Status in bluez source package in Focal: Invalid Bug description: bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1876645] Re: Unable to handle kernel pointer dereference in virtual kernel address space on Eoan
It's too late now, but there's a typo in the changelog: "shitfs". -- 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/1876645 Title: Unable to handle kernel pointer dereference in virtual kernel address space on Eoan Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Issue spotted on Eoan zVM / LPAR It looks like this happens when running the ubunut_fan_smoke_test (jenkins job hang with this one) [ 1225.137764] docker0: port 1(veth2fda0c6) entered blocking state [ 1225.137767] docker0: port 1(veth2fda0c6) entered disabled state [ 1225.138023] device veth2fda0c6 entered promiscuous mode [ 1225.148523] Unable to handle kernel pointer dereference in virtual kernel address space [ 1225.148529] Failing address: 6f766c5f646f5000 TEID: 6f766c5f646f5803 [ 1225.148531] Fault in home space mode while using kernel ASCE. [ 1225.148533] AS:00070d94c007 R3:0024 [ 1225.148575] Oops: 0038 ilc:3 [#1] SMP [ 1225.148578] Modules linked in: veth xt_nat vxlan ip6_udp_tunnel udp_tunnel nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter unix_diag sctp cuse vhost_net tap vhost_vsock vmw_vsock_virtio_transport_common vhost vsock dccp_ipv4 dccp algif_rng aegis128 aegis128l aegis256 morus1280 morus640 algif_aead anubis fcrypt khazad seed sm4_generic tea md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic algif_hash blowfish_generic blowfish_common cast5_generic salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher af_alg xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat nf_conntrack [ 1225.148622] nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_service_time mlx4_ib ib_uverbs mlx4_en ptp ib_core pps_core pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 qeth_l2 des_generic sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp scsi_transport_fc qeth qdio ccwgroup dasd_eckd_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 1225.148711] CPU: 4 PID: 161930 Comm: dockerd Tainted: P O 5.3.0-52-generic #46-Ubuntu [ 1225.148714] Hardware name: IBM 2964 N63 400 (LPAR) [ 1225.148716] Krnl PSW : 0704d0018000 03ff808e972a (ovl_open_realfile+0x4a/0x148 [overlay]) [ 1225.148734]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 PM:0 RI:0 EA:3 [ 1225.148736] Krnl GPRS: 0064 6f766c5f646f5f6d 0007a14ac300 0003a5df6600 [ 1225.148738]8000 0001 0003 000372e45278 [ 1225.148740]03ff808ea508 000304048000 0005c7f32b68 00064a2ab900 [ 1225.148742]0003a5df6600 03ff808f31d8 03ff808e971a 03e009c0faf8 [ 1225.148749] Krnl Code: 03ff808e971a: a59a0404 oilh%r9,1028 03ff808e971e: e310f0c4 lg %r1,192(%r15) #03ff808e9724: e31010680004 lg %r1,104(%r1) >03ff808e972a: e3101064 lg %r1,96(%r1) 03ff808e9730: b9040082 lgr %r8,%r2 03ff808e9734: c21c6a656a62 cgfi %r1,1785031266 03ff808e973a: b9140039 lgfr%r3,%r9 03ff808e973e: e3100344 lg %r1,832 [ 1225.148766] Call Trace: [ 1225.148769] ([<>] 0x0) [ 1225.148774] [<03ff808ea582>] ovl_open+0x7a/0xc0 [overlay] [ 1225.148780] [<00070cbf2c04>] do_dentry_open+0x1fc/0x3b0 [ 1225.148784] [<00070cc0afd2>] do_last+0x1ba/0x970 [ 1225.148786] [<00070cc0b80e>] path_openat+0x86/0x2b8 [ 1225.148788] [<00070cc0cea4>] do_filp_open+0x7c/0xf8 [ 1225.148791] [<00070cbf4b5a>] do_sys_open+0x19a/0x2c8 [ 1225.148798] [<00070d1ebca8>] system_call+0xdc/0x2c8 [ 1225.148800] Last Breaking-Event-Address: [
[Kernel-packages] [Bug 1875863] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-05-20 06:53 EDT--- @Canonical, Comment #10 is not preciseliy correct. IBM will verify the fix soon.. -- 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/1875863 Title: ceph -- Unable to mount ceph volume on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: SRU Justification: == [Impact] * Unable to mount ceph volumes on big endian systems, like s390x. * The mount operation always fails with an IO error. * This is caused by an endiness issue in function handle_session where variable features is always little endian. * But test_bit assumes the host order of bytes, hence causes a problem on big endian systems. [Fix] * 0fa8263367db9287aa0632f96c1a5f93cc478150 0fa8263367db "ceph: fix endianness bug when handling MDS session feature bits" [Test Case] * Setup ceph on s390x. * Try to mount a ceph volume. * If it mounts correctly the patch is applied and working. * Without the patch a mount always fails on big endian / s390x. [Regression Potential] * There is regression potential with having code changes in ceph's session handler, which is common code. * However, the patch was accepted (slightly changed) by the ceph maintainers and with that got upstream accepted, too. * The patch is fairly limited (5 lines removed, 3 added), hence the changes are quite traceable. __ When mounting a ceph volume, mount operation fails with an IO error. The problem is always reproducible. Identified potential root cause as kernel endian bug: In the function handle_session() variable @features always contains little endian order of bytes. Just because The feature mask sent by the MDS is little-endian (bits are packed bytewise from left to right in encode_supported_features()). However, test_bit(), called to check features availability, assumes the host order of bytes in that variable. This leads to problems on big endian architectures. Specifically it is impossible to mount ceph volume on s390. A fixup was proposed to convert little-endian order of bytes to the host one. That fixup was modified by ceph maintainers to use existing unpacking means for the conversion. The resulted patch attached. Related discussion in the ceph-development mailing list: https://marc.info/?l=ceph-devel=158815357301332=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1875863/+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
