[Kernel-packages] [Bug 1946638] Re: Kernet stack is corrupted on installation Ubuntu 21.10
*** This bug is a duplicate of bug 1945590 *** https://bugs.launchpad.net/bugs/1945590 ** This bug has been marked a duplicate of bug 1945590 Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint 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/1946638 Title: Kernet stack is corrupted on installation Ubuntu 21.10 Status in linux package in Ubuntu: Incomplete Bug description: Unable to install Ubuntu 21.10 getting error when try to run ubuntu from usb installation. Kernel Panic + Kernel stack is corrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946638/+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 1944575] Re: Acer Aspire 5 issue when headphone plug in before login
I tested this as well for shutdown/power up and reboot still same issue no changes at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944575 Title: Acer Aspire 5 issue when headphone plug in before login Status in linux package in Ubuntu: Confirmed Bug description: Hello, Acer Aspire A515-56-57XR with ALC255 when headphone is plugged in before login causes few issues. I will list them below: - When headphones are plugged in and if I restart/shutdown-turn on the laptop and log in it does not detect headphones microphone at all and internal microphone is selected by default. - For output device headphones are plugged in but left/right channel is merged into both channels - To fix this need to re-plug the headphones/earphones and the issue goes away or after a restart/shutdown plug in only after logging in. - This issue does not occur when log off and log in only after a restart or cold boot from a shutdown while headphones/earphones are left plugged in. In another similar thread to this lots of other issues were fixed and they have been already merged into official kernel now. I will put a link to it below for reference. Looking to fix this issue now. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bijay 2343 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-19 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-56 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=9c557228-52d9-4013-9bdb-4e16712575d1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.11.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 05/26/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:sku:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944575/+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 1946638] Re: Kernet stack is corrupted on installation Ubuntu 21.10
Does the panic always happen at the same place? i.e. elantech_change_report_id()? -- 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/1946638 Title: Kernet stack is corrupted on installation Ubuntu 21.10 Status in linux package in Ubuntu: Incomplete Bug description: Unable to install Ubuntu 21.10 getting error when try to run ubuntu from usb installation. Kernel Panic + Kernel stack is corrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946638/+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 1933359] Re: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request
Installed linux-image-unsigned, linux-modules & linux-modules-extra from the above link. # modinfo mpi3mr modinfo: ERROR: Module mpi3mr not found. # uname -r 5.13.0-18-generic Hi Michael, Looks like this kernel is missing mpi3mr. Can you please look into it? -- 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/1933359 Title: [Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+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 1944094] Re: Can't adjust screen backlight on Legion Slim 7 AMD
This seems to also effect the Legion 5 15ach6 (AMD) There are two versions of the legion 5, the 2020 version and the 2021 version. It seems that this issue is fixed on the 2020 version by adding the kernel parameter amdgpu.backlight=0 but I can confirm that this does not fix the issue on the 2021 version, so its likely that the 2021 laptop is suffering from whatever this issue is. I'm guessing that the MUX switch is involved in one way or another, as it means that the NVIDIA dGPU does not have to pass frames through the AMD iGPU, it connects to the display separately, and I'm not sure which GPU actually has control over the brightness control. I wonder if the brightness isn't tied to either GPU, maybe its a separate system entirely? ** Summary changed: - Can't adjust screen backlight on Legion Slim 7 AMD + Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD -- 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/1944094 Title: Can't adjust screen backlight on Legion Slim 7 / Legion 5 (2021) AMD Status in linux package in Ubuntu: Confirmed Bug description: The screen brightness controls don't work on the Legion Slim 7 (AMD) laptop running in hybrid/dynamic mode. The backlight control files appear in /sys/class/backlight/amdgpu_bl0, and writing to /sys/class/backlight/amdgpu_bl0/brightness changes the value in /sys/class/backlight/amdgpu_bl0/actual_brightness, but the screen brightness always remains at 100%. I have tried kernel boot parameters: acpi_backlight=vendor amdgpu.backlight=0 but neither makes any difference. I have read that users with the Legion 7 AMD and Legion 5 Pro AMD can get the backlight working with the amdgpu.backlight=0 kernel boot parameter. One difference between them and this laptop is that it has advanced optimus, meaning that it can switch the laptop display between the amdgpu and nvidia card without rebooting, if that is at all relevant. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1978 F pulseaudio /dev/snd/controlC1: rocko 1978 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 09:20:33 2021 InstallationDate: Installed on 2021-09-15 (5 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.200 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944094/+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 1944575] Re: Acer Aspire 5 issue when headphone plug in before login
Then please test this kernel: https://people.canonical.com/~hwang4/lp1944575/v2/ -- 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/1944575 Title: Acer Aspire 5 issue when headphone plug in before login Status in linux package in Ubuntu: Confirmed Bug description: Hello, Acer Aspire A515-56-57XR with ALC255 when headphone is plugged in before login causes few issues. I will list them below: - When headphones are plugged in and if I restart/shutdown-turn on the laptop and log in it does not detect headphones microphone at all and internal microphone is selected by default. - For output device headphones are plugged in but left/right channel is merged into both channels - To fix this need to re-plug the headphones/earphones and the issue goes away or after a restart/shutdown plug in only after logging in. - This issue does not occur when log off and log in only after a restart or cold boot from a shutdown while headphones/earphones are left plugged in. In another similar thread to this lots of other issues were fixed and they have been already merged into official kernel now. I will put a link to it below for reference. Looking to fix this issue now. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bijay 2343 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-19 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-56 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=9c557228-52d9-4013-9bdb-4e16712575d1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.11.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 05/26/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:sku:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944575/+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 1946219] Re: liburing stops working after upgrading to 5.4.0-1012
** 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946219 Title: liburing stops working after upgrading to 5.4.0-1012 Status in HWE Next: New Status in linux-bluefield package in Ubuntu: In Progress Status in linux-bluefield source package in Focal: Fix Committed Bug description: == Impact == After configuration multipath with io uring virtio_blk module is stuck == Fix == The issue was introduced by one of the stable updates merged in the base kernel Ubuntu-5.4.0-74.83. After reverting the commit the issue can not be reproduced any more. commit d6757b3e34831b7615edd3268b878536761f8b2e Author: Pavel Begunkov Date: Fri Nov 20 17:10:28 2020 + block: don't ignore REQ_NOWAIT for direct IO BugLink: https://bugs.launchpad.net/bugs/1926490 [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocking on eg request allocation on the storage side. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader == Risk of Regression == Medium. The commit has a good reason to be part of the stable updates. However the kernel passes Cert and Nvidia tests without the commit so reverting the commit should be an acceptable approach for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946219/+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 1935728] Re: [radeon] Mouse pointer randomly disappears - other mouse operations still work
Same here, seems like most apple iMacs running ubuntu have this issue, probably relates to ATI RV730 card. -- 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/1935728 Title: [radeon] Mouse pointer randomly disappears - other mouse operations still work Status in linux package in Ubuntu: Confirmed Bug description: The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and ubuntu 20.10). When this occurs all other mouse operations still function - left/right click - scroll wheel - mouse position still moves Just the actual mouse pointer not visible. Only way to resolve is to restart the machine. Tried numerous ways to restart the mouse driver but nothing else successful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 14:45:22 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2021-07-05 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Apple Inc. iMac10,1 ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 initrd=boot\initrd.img-5.8.0-59-generic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268DC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268DC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935728/+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 1946692] 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 1946692 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/1946692 Title: kernel panic stack corrupted syncing elantech_change_report Status in linux package in Ubuntu: Incomplete Bug description: Lenovo E15 laptop running Impish Indra kernels 5.13.0-16 and 5.13.0-19 both panic kernel-5.13.0-14 is the last kernel to boot ok. I have a screenshot of the failed boot but don't know how to submit it. It says "kernel stack is corrupted in elantech_change_report_id ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946692/+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 1946692] Re: kernel panic stack corrupted syncing elantech_change_report
attached screenshot of the panic. sorry it's not very clear. ** Attachment added: "e15-kernel-panic.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946692/+attachment/5532009/+files/e15-kernel-panic.jpg -- 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/1946692 Title: kernel panic stack corrupted syncing elantech_change_report Status in linux package in Ubuntu: Incomplete Bug description: Lenovo E15 laptop running Impish Indra kernels 5.13.0-16 and 5.13.0-19 both panic kernel-5.13.0-14 is the last kernel to boot ok. I have a screenshot of the failed boot but don't know how to submit it. It says "kernel stack is corrupted in elantech_change_report_id ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946692/+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 1946692] [NEW] kernel panic stack corrupted syncing elantech_change_report
Public bug reported: Lenovo E15 laptop running Impish Indra kernels 5.13.0-16 and 5.13.0-19 both panic kernel-5.13.0-14 is the last kernel to boot ok. I have a screenshot of the failed boot but don't know how to submit it. It says "kernel stack is corrupted in elantech_change_report_id ..." ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1946692 Title: kernel panic stack corrupted syncing elantech_change_report Status in linux package in Ubuntu: Incomplete Bug description: Lenovo E15 laptop running Impish Indra kernels 5.13.0-16 and 5.13.0-19 both panic kernel-5.13.0-14 is the last kernel to boot ok. I have a screenshot of the failed boot but don't know how to submit it. It says "kernel stack is corrupted in elantech_change_report_id ..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946692/+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 1946686] [NEW] Fix zfs_get_data access to files with wrong generation causing panics
Public bug reported: As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- 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/1946686 Title: Fix zfs_get_data access to files with wrong generation causing panics Status in zfs-linux package in Ubuntu: New Bug description: As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs- linux/+question/696659, the following pull request fixes a panic acquiring a lock: https://github.com/openzfs/zfs/pull/11682 This fix does not appear to be a part of the latest Ubuntu 20.04 release: zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.12 Version table: *** 0.8.3-1ubuntu12.12 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Of note is this issue where the bug is reported against the Ubuntu 0.8.3 packages: https://github.com/openzfs/zfs/issues/10642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946686/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
Looking for advice if anyone has it as to how I can recover my filesystem after being affected by this bug. I installed zfs 2.0.6 via dkms and have moved affected files like my chrome cache to a quarantine location as suggested by Trent. However, I seem to continue stumbling on affected files, and even with /sys/module/zfs/parameters/zfs_recover=1 set I see panics in dmesg and hung processes that cant be killed. >From what I've gathered: Running 2.0.6 via dkms means that I'm not running the affected code anymore. However, it seems like there is permanent FS corruption (which is very unfortunate since this is the sort of thing ZFS is supposed to be good at preventing). Is there a best course of action to prevent future kernel panics? Would reverting to a snapshot from before I noticed this issue work, or is there shared metadata that's been corrupted? Should I just copy the files I can access onto another disk and re-create my ZFS pool / dataset? Any advice is appreciated :/ Thanks -- 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/1906476 Title: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Status in Native ZFS for Linux: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS panic in the kernel log which was also hanging Disk I/O for all Chrome/Electron Apps. I have narrowed down a few important notes: - It does not happen with module version 0.8.4-1ubuntu11 built and included with 5.8.0-29-generic - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS on the same kernel and also on 5.8.18-acso (a custom kernel). - For whatever reason multiple Chrome/Electron apps were affected, specifically Discord, Chrome and Mattermost. In all cases they seem (but I was unable to strace the processes so it was a bit hard ot confirm 100% but by deduction from /proc/PID/fd and the hanging ls) they seem hung trying to open files in their 'Cache' directory, e.g. ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache .. while the issue was going on I could not list that directory either "ls" would just hang. - Once I removed zfs-dkms only to revert to the kernel built-in version it immediately worked without changing anything, removing files, etc. - It happened over multiple reboots and kernels every time, all my Chrome apps weren't working but for whatever reason nothing else seemed affected. - It would log a series of spl_panic dumps into kern.log that look like this: Dec 2 12:36:42 optane kernel: [ 72.857033] VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed Dec 2 12:36:42 optane kernel: [ 72.857036] PANIC at zfs_znode.c:335:zfs_znode_sa_init() I could only find one other google reference to this issue, with 2 other users reporting the same error but on 20.04 here: https://github.com/openzfs/zfs/issues/10971 - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure it was working on 0.8.4-1ubuntu15 but broken after upgrade to 0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify that. There were a few originating call stacks but the first one I hit was Call Trace: dump_stack+0x74/0x95 spl_dumpstack+0x29/0x2b [spl] spl_panic+0xd4/0xfc [spl] ? sa_cache_constructor+0x27/0x50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_buf_set_user_ie+0x54/0x80 [zfs] zfs_znode_sa_init+0xe0/0xf0 [zfs] zfs_znode_alloc+0x101/0x700 [zfs] ? arc_buf_fill+0x270/0xd30 [zfs] ? __cv_init+0x42/0x60 [spl] ? dnode_cons+0x28f/0x2a0 [zfs] ? _cond_resched+0x19/0x40 ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? aggsum_add+0x153/0x170 [zfs] ? spl_kmem_alloc_impl+0xd8/0x110 [spl] ? arc_space_consume+0x54/0xe0 [zfs] ? dbuf_read+0x4a0/0xb50 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dnode_rele_and_unlock+0x5a/0xc0 [zfs] ? _cond_resched+0x19/0x40 ? mutex_lock+0x12/0x40 ? dmu_object_info_from_dnode+0x84/0xb0 [zfs] zfs_zget+0x1c3/0x270 [zfs] ? dmu_buf_rele+0x3a/0x40 [zfs] zfs_dirent_lock+0x349/0x680 [zfs] zfs_dirlook+0x90/0x2a0 [zfs] ? zfs_zaccess+0x10c/0x480 [zfs] zfs_lookup+0x202/0x3b0 [zfs] zpl_lookup+0xca/0x1e0 [zfs] path_openat+0x6a2/0xfe0 do_filp_open+0x9b/0x110 ? __check_object_size+0xdb/0x1b0 ? __alloc_fd+0x46/0x170 do_sys_openat2+0x217/0x2d0 ? do_sys_openat2+0x217/0x2d0 do_sys_open+0x59/0x80 __x64_sys_openat+0x20/0x30 To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1906476/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1946024] Re: Focal update: v5.4.146 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946024 Title: Focal update: v5.4.146 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.146 upstream stable release from git://git.kernel.org/ locking/mutex: Fix HANDOFF condition regmap: fix the offset of register error log crypto: mxs-dcp - Check for DMA mapping errors sched/deadline: Fix reset_on_fork reporting of DL tasks power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() sched/deadline: Fix missing clock update in migrate_task_rq_dl() rcu/tree: Handle VM stoppage in stall detection hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() hrtimer: Ensure timerfd notification for HIGHRES=n udf: Check LVID earlier udf: Fix iocharset=utf8 mount option isofs: joliet: Fix iocharset=utf8 mount option bcache: add proper error unwinding in bcache_device_init nvme-tcp: don't update queue count when failing to set io queues nvme-rdma: don't update queue count when failing to set io queues nvmet: pass back cntlid on successful completion power: supply: max17042_battery: fix typo in MAx17042_TOFF s390/cio: add dev_busid sysfs entry for each subchannel libata: fix ata_host_start() crypto: qat - do not ignore errors from enable_vf2pf_comms() crypto: qat - handle both source of interrupt in VF ISR crypto: qat - fix reuse of completion variable crypto: qat - fix naming for init/shutdown VF to PF notifications crypto: qat - do not export adf_iov_putmsg() fcntl: fix potential deadlock for _struct.fa_lock udf_get_extendedattr() had no boundary checks. s390/kasan: fix large PMD pages address alignment check s390/debug: fix debug area life cycle m68k: emu: Fix invalid free in nfeth_cleanup() sched: Fix UCLAMP_FLAG_IDLE setting spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config spi: spi-pic32: Fix issue with uninitialized dma_slave_config genirq/timings: Fix error return code in irq_timings_test_irqs() lib/mpi: use kcalloc in mpi_resize clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel crypto: qat - use proper type for vf_mask certs: Trigger creation of RSA module signing key if it's not an RSA key regulator: vctrl: Use locked regulator_get_voltage in probe path regulator: vctrl: Avoid lockdep warning in enable/disable ops spi: sprd: Fix the wrong WDG_LOAD_VAL spi: spi-zynq-qspi: use wait_for_completion_timeout to make zynq_qspi_exec_mem_op not interruptible EDAC/i10nm: Fix NVDIMM detection drm/panfrost: Fix missing clk_disable_unprepare() on error in panfrost_clk_init() media: TDA1997x: enable EDID support soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally media: cxd2880-spi: Fix an error handling path bpf: Fix a typo of reuseport map in bpf.h. bpf: Fix potential memleak and UAF in the verifier. ARM: dts: aspeed-g6: Fix HVI3C function-group in pinctrl dtsi arm64: dts: renesas: r8a77995: draak: Remove bogus adv7511w properties soc: qcom: rpmhpd: Use corner in power_off media: dvb-usb: fix uninit-value in dvb_usb_adapter_dvb_init media: dvb-usb: fix uninit-value in vp702x_read_mac_addr media: dvb-usb: Fix error handling in dvb_usb_i2c_init media: go7007: remove redundant initialization media: coda: fix frame_mem_ctrl for YUV420 and YVU420 formats Bluetooth: sco: prevent information leak in sco_conn_defer_accept() 6lowpan: iphc: Fix an off-by-one check of array index netns: protect netns ID lookups with RCU drm/amdgpu/acp: Make PM domain really work tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos ARM: dts: meson8: Use a higher default GPU clock frequency ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties ARM: dts: meson8b: mxq: Fix the pwm regulator supply properties ARM: dts: meson8b: ec100: Fix the pwm regulator supply properties net/mlx5e: Prohibit inner indir TIRs in IPoIB cgroup/cpuset: Fix a partition bug with hotplug net: cipso: fix warnings in netlbl_cipsov4_add_std i2c: highlander: add IRQ check leds: lt3593: Put fwnode in any case during ->probe()
[Kernel-packages] [Bug 1942932] Re: oob_net0 up but stops processing Rx packets
Hi David, may you please verify this is resolved in the kernel sitting in proposed? You can find instructions for how to do this in comment #1. thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1942932 Title: oob_net0 up but stops processing Rx packets Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The oob_net0 interface, managed by the mlxbf_gige driver, will be up and enabled but can stop processing received packets if three specific conditions occur: 1) driver has received more than (N * RxRingSize) packets but less than (N+1 * RxRingSize) packets where N is an odd number. Note: the command "ethtool -g oob_net0" will display the current receive ring size, which currently defaults to 128. 2) the driver's interface was disabled via "ifconfig oob_net0 down" during the window described in #1. 3) the driver's interface is re-enabled via "ifconfig oob_net0 up" Without this fix, the driver needs to be unloaded and re-loaded to correct this condition. [Fix] * The fix is to ensure that the driver's "valid_polarity" field is cleared during the open() method so that it always matches the receive polarity used by hardware. [Test Case] * To test this fix, need to send in a specific number of packets to the "oob_net0" interface, then issue "ifconfig oob_net0 down" to disable the interface. A subsequent "ifconfig oob_net0 up" command will succesfully bring up the "oob_net0" interface and start the processing of received packets. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942932/+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 1942931] Re: "ethtool -S oob_net0" does not report interrupt counts
Hi David, may you please verify this bug is resolved in the kernel sitting in proposed? You can find instructions for how to complete that in comment #1. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1942931 Title: "ethtool -S oob_net0" does not report interrupt counts Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The command "ethtool -S oob_net0" displays a set of statistics related to mlxbf_gige driver. This set of statistics does not include the driver's interrupt counts. [Fix] * The fix is to extend the statistics list supported by "ethtool -S" so that it includes MAC, receive packet, and LLU/PLU interrupt counts. [Test Case] * The command "ethtool -S oob_net0" should be executed before and after this fix to verify that three new fields are displayed: mac_intr_count rx_intr_count llu_plu_intr_count [Regression Potential] * There is low risk of this fix causing any problems. [Other] * n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1942931/+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 1943065] Re: mlxbf_gige: update driver version to 1.25
Hi David, may you please verify this bug is resolved in the kernel in proposed? You can find instructions in comment #2 https://bugs.launchpad.net/ubuntu/+source/linux- bluefield/+bug/1943065/comments/2 Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+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 1943065] Re: mlxbf_gige: update driver version to 1.25
Hi Meriton, the fix is currently in linux-bluefield/5.4.0-1020.23 which is in proposed. As long as test reviews continue to go well, this will be scheduled to release next week. Schedule can be found here: https://kernel.ubuntu.com/ If you are able to complete the verification mentioned in comment #2, it would be very helpful. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1943065 Title: mlxbf_gige: update driver version to 1.25 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] * The mlxbf_gige driver needs a version increase to identify a driver containing recent important bug fixes. [Fix] * The driver version implemented by the DRV_VERSION define and MODULE_VERSION macro will be incremented from 1.24 to 1.25 [Test Case] * To test this fix, need to check the driver version shown in the output of "modinfo mlxbf_gige" command. [Regression Potential] * There is low risk of this fix causing any problems. [Other] * The mlxbf_gige driver will display v1.25 in modinfo after these changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1943065/+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 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** 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/1942902 Title: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption" Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: In order to address https://bugs.launchpad.net/bugs/1933074 the following SAUCE patch was introduced. Colin Ian King (1): UBUNTU: SAUCE: ext4: fix directory index node split corruption fs/ext4/namei.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) Meanwhile the issue addressed by this patch was fixed upstream with commit 877ba3f729fd ("ext4: fix potential htree corruption when growing large_dir directories"). The upstream patch was already cherry-picked to hirsute with "upstream stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with "v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6). [1] BugLink: https://bugs.launchpad.net/bugs/1942123 [2] BugLink: https://bugs.launchpad.net/bugs/1941798 Therefore the SAUCE patch is obsolete and can be either dropped or reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I can confirm also for me 5.13.8-051308-generic boots ok -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I can confirm also for me 5.13.8-051308-generic boots ok -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
5.13.8-051308-generic still boots ok, but 5.13.9-051309-generic fails -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot
** Bug watch added: Linux Kernel Bug Tracker #214259 https://bugzilla.kernel.org/show_bug.cgi?id=214259 -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
*** Bug 214259 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
Just wanted to leave a note here that this issue continues to be a problem with descrete thundebold 4 chips: https://bugzilla.kernel.org/show_bug.cgi?id=214259 The hack from https://bugzilla.kernel.org/show_bug.cgi?id=206459#c46 fixes the dock on that Laptop, the cleaner hack I have yet to try. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
Just a testing update: As of today (2020-11-12), the patch: - Still hasn't landed - Still applies cleanly on kernel 5.10-rc3 - Is still needed, otherwise thunderbolt doesn't work at all on affected hardware upon reconnect. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
Any updates on if a fix for this has arrived? So far I've just been applying the patch (287661) and compiling the kernel myself for my Yoga C940, but it's rather finnicky. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
I suggest you to reply on that email thread that there is a real problem that needs to be solved so we get some traction from the maintainers. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
Hi, sorry about this. I did not get any comments from x86 maintainers for this and the comment from Bjorn (the author of the original code) seems to suggest rather big rework so I simply haven't had time to look at it at the moment. Can send a ping on that thread? Maybe we get some x86 maintainers to comment it then. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1932157] Re: [21.10 FEAT] KVM: Use interpretation of specification exceptions
** Changed in: ubuntu-z-systems 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/1932157 Title: [21.10 FEAT] KVM: Use interpretation of specification exceptions Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: This allows KVM to let SIE interpret specification exceptions instead of doing this itself, leading to performance improvements. This feature will be made available with kernel >=5.15 A backport will be provided once available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932157/+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 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO
Document: https://software.intel.com/content/www/us/en/develop/documentation/tcc- tools-2021-2-developer-guide/top/time-synchronization-and-communication- tools/time-aware-gpio-tgpio-samples.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929890 Title: [EHL][TGL][ADL] PMC Time-aware GPIO Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description GPIO controller on CNL PCH has a new feature which allows for timed trigger of GPIO events. We should consider at least following aspects and if needed we can create subtasks: Translation of ART->System Time on input Any output GPIO Cross-timestamp and/or edge counting of input GPIOs supporting high frequency input Similar feature to input, counting output edges Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment Time Aware GPIO Output - Fire on Trigger Time Aware GPIO Input - Stamp on Edge Detection Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929890/+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 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Identical problem. only that my machine is frozen after the nvidia error messages. Running Ubuntu 20.04 LTS / Nvidia driver 470.57.02 on Razer Blade 15 Advanced (2018) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O) snd_soc_hdac_hda
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Hey Kleber, Thanks for confirming. I guess there might be something wrong with the boot process on r5.metal, specifically: - there's no issue with kexec boot, just with normal boot (same code and from/to versions) - there's no issue with normal boot on similar instance types (r5d.metal, r5.24xlarge) - rarely, but sometimes, it works with normal boot. I'm looking forward to hearing back from Ian on whether he could get additional information from AWS, or how to reach out to them, about getting the serial console log from the r5.metal instances internally, via AWS support, so we know what the actual issue is. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1944397] Re: HDMI does not display anything with Impish RPi desktop image
This bug was fixed in the package linux-raspi - 5.13.0-1008.9 --- linux-raspi (5.13.0-1008.9) impish; urgency=medium * impish/linux-raspi: 5.13.0-1008.9 -proposed tracker (LP: #1944938) * Speakup modules not included in Hirsute kernel (LP: #1942459) - [Config] raspi: Enable ACCESSIBILITY and set SPEAKUP*=m * Virtual CAN (vcan) driver missing in raspi 5.13 kernel (LP: #1944593) - [Packaging] Add drivers/net/can/* to linux-image-modules * HDMI does not display anything with Impish RPi desktop image (LP: #1944397) - Move clk_request_done() for hsm_req to the correct location - drm/vc4: hdmi: Make sure the controller is powered up during bind - drm/vc4: hdmi: Remove unnecessary pm_runtime_put * Miscellaneous Ubuntu changes - [Packaging] raspi: remove remaining references to ports [ Ubuntu: 5.13.0-17.17 ] * impish/linux: 5.13.0-17.17 -proposed tracker (LP: #1944943) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) - debian/dkms-versions -- update from kernel-versions (main/master) * Medion Notebook Keyboard not working (LP: #1909814) - ACPI: resources: Add DMI-based legacy IRQ override quirk * Can not boot impish in Cavium ThunderX (LP: #1942633) - arm64: Restore forced disabling of KPTI on ThunderX * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: vmd: fixup bridge ASPM by driver name instead * CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform (LP: #1943935) - SAUCE: ALSA: hda/cs8409: Setup Dolphin Headset Mic as Phantom Jack - ALSA: hda/cs8409: Initialize Codec only in init fixup. - ALSA: hda/cs8409: Ensure Type Detection is only run on startup when necessary * psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish (LP: #1892213) - selftests/net: remove min gso test in packet_snd * Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 (LP: #1935034) - scsi: mpt3sas: Documentation cleanup - scsi: mpt3sas: Handle firmware faults during first half of IOC init - scsi: mpt3sas: Handle firmware faults during second half of IOC init - scsi: core: Introduce scsi_build_sense() - scsi: mpt3sas: Fix fall-through warnings for Clang - scsi: mpt3sas: Fix Coverity reported issue - scsi: mpt3sas: Bump driver version to 38.100.00.00 * Update fix for LP: #1936708 (LP: #1942972) - Revert "UBUNTU: SAUCE: drm/i915/dp: Use max params for older panels" - drm/i915/dp: Use max params for panels < eDP 1.4 * [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * Speakup modules not included in Hirsute kernel (LP: #1942459) - [Config] CONFIG_SPEAKUP=m * s390x BPF JIT vulnerabilities (LP: #1943960) - s390/bpf: Fix branch shortening during codegen pass - s390/bpf: Fix 64-bit subtraction of the -0x8000 constant - s390/bpf: Fix optimizing out zero-extensions * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() * CVE-2021-40490 - ext4: fix race writing to an inline_data file while its xattrs are changing * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * Noise will pop up during WB or stay in Ubuntu OS when external speaker attached (LP: #1942043) - Revert "UBUNTU: SAUCE: ALSA: hda/cs8409: Prevent pops and clicks during reboot" - ALSA: hda: Release controller display power during shutdown/reboot - ALSA: hda: Release codec display power during shutdown/reboot - ALSA: hda: conexant: Turn off EAPD at suspend, too - ALSA: hda: Suspend codec at shutdown - ALSA: hda: Nuke unused reboot_notify callback - ALSA: hda: Disable runtime resume at shutdown * ALSA: hda/cs8409: Add support for dolphin (LP: #1939541) - ALSA: hda/cirrus: Move CS8409 HDA bridge to separate module - ALSA: hda/cs8409: Move arrays of configuration to a new file - ALSA: hda/cs8409: Use enums for register names and coefficients - ALSA: hda/cs8409: Mask all CS42L42 interrupts on initialization - ALSA: hda/cs8409: Reduce HS pops/clicks for Cyborg - ALSA: hda/cs8409: Disable unnecessary Ring Sense for Cyborg/Warlock/Bullseye - ALSA: hda/cs8409: Disable unsolicited responses during suspend - ALSA: hda/cs8409: Disable unsolicited response for the first boot - ALSA: hda/cs8409: Mask CS42L42 wake events - ALSA: hda/cs8409: Simplify CS42L42 jack detect. - ALSA: hda/cs8409: Prevent I2C access during suspend time - ALSA: hda/cs8409: Generalize volume controls - ALSA: hda/cs8409: Dont disable I2C clock between consecutive accesses - ALSA: hda/cs8409: Avoid
[Kernel-packages] [Bug 1944593] Re: Virtual CAN (vcan) driver missing in raspi 5.13 kernel
This bug was fixed in the package linux-raspi - 5.13.0-1008.9 --- linux-raspi (5.13.0-1008.9) impish; urgency=medium * impish/linux-raspi: 5.13.0-1008.9 -proposed tracker (LP: #1944938) * Speakup modules not included in Hirsute kernel (LP: #1942459) - [Config] raspi: Enable ACCESSIBILITY and set SPEAKUP*=m * Virtual CAN (vcan) driver missing in raspi 5.13 kernel (LP: #1944593) - [Packaging] Add drivers/net/can/* to linux-image-modules * HDMI does not display anything with Impish RPi desktop image (LP: #1944397) - Move clk_request_done() for hsm_req to the correct location - drm/vc4: hdmi: Make sure the controller is powered up during bind - drm/vc4: hdmi: Remove unnecessary pm_runtime_put * Miscellaneous Ubuntu changes - [Packaging] raspi: remove remaining references to ports [ Ubuntu: 5.13.0-17.17 ] * impish/linux: 5.13.0-17.17 -proposed tracker (LP: #1944943) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) - debian/dkms-versions -- update from kernel-versions (main/master) * Medion Notebook Keyboard not working (LP: #1909814) - ACPI: resources: Add DMI-based legacy IRQ override quirk * Can not boot impish in Cavium ThunderX (LP: #1942633) - arm64: Restore forced disabling of KPTI on ThunderX * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: vmd: fixup bridge ASPM by driver name instead * CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform (LP: #1943935) - SAUCE: ALSA: hda/cs8409: Setup Dolphin Headset Mic as Phantom Jack - ALSA: hda/cs8409: Initialize Codec only in init fixup. - ALSA: hda/cs8409: Ensure Type Detection is only run on startup when necessary * psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish (LP: #1892213) - selftests/net: remove min gso test in packet_snd * Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 (LP: #1935034) - scsi: mpt3sas: Documentation cleanup - scsi: mpt3sas: Handle firmware faults during first half of IOC init - scsi: mpt3sas: Handle firmware faults during second half of IOC init - scsi: core: Introduce scsi_build_sense() - scsi: mpt3sas: Fix fall-through warnings for Clang - scsi: mpt3sas: Fix Coverity reported issue - scsi: mpt3sas: Bump driver version to 38.100.00.00 * Update fix for LP: #1936708 (LP: #1942972) - Revert "UBUNTU: SAUCE: drm/i915/dp: Use max params for older panels" - drm/i915/dp: Use max params for panels < eDP 1.4 * [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock (LP: #1942999) - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough * Speakup modules not included in Hirsute kernel (LP: #1942459) - [Config] CONFIG_SPEAKUP=m * s390x BPF JIT vulnerabilities (LP: #1943960) - s390/bpf: Fix branch shortening during codegen pass - s390/bpf: Fix 64-bit subtraction of the -0x8000 constant - s390/bpf: Fix optimizing out zero-extensions * CVE-2021-41073 - io_uring: ensure symmetry in handling iter types in loop_rw_iter() * CVE-2021-40490 - ext4: fix race writing to an inline_data file while its xattrs are changing * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * Noise will pop up during WB or stay in Ubuntu OS when external speaker attached (LP: #1942043) - Revert "UBUNTU: SAUCE: ALSA: hda/cs8409: Prevent pops and clicks during reboot" - ALSA: hda: Release controller display power during shutdown/reboot - ALSA: hda: Release codec display power during shutdown/reboot - ALSA: hda: conexant: Turn off EAPD at suspend, too - ALSA: hda: Suspend codec at shutdown - ALSA: hda: Nuke unused reboot_notify callback - ALSA: hda: Disable runtime resume at shutdown * ALSA: hda/cs8409: Add support for dolphin (LP: #1939541) - ALSA: hda/cirrus: Move CS8409 HDA bridge to separate module - ALSA: hda/cs8409: Move arrays of configuration to a new file - ALSA: hda/cs8409: Use enums for register names and coefficients - ALSA: hda/cs8409: Mask all CS42L42 interrupts on initialization - ALSA: hda/cs8409: Reduce HS pops/clicks for Cyborg - ALSA: hda/cs8409: Disable unnecessary Ring Sense for Cyborg/Warlock/Bullseye - ALSA: hda/cs8409: Disable unsolicited responses during suspend - ALSA: hda/cs8409: Disable unsolicited response for the first boot - ALSA: hda/cs8409: Mask CS42L42 wake events - ALSA: hda/cs8409: Simplify CS42L42 jack detect. - ALSA: hda/cs8409: Prevent I2C access during suspend time - ALSA: hda/cs8409: Generalize volume controls - ALSA: hda/cs8409: Dont disable I2C clock between consecutive accesses - ALSA: hda/cs8409: Avoid
[Kernel-packages] [Bug 1945707] Re: BCM57800 SRIOV bug causes interfaces to disappear
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945707 Title: BCM57800 SRIOV bug causes interfaces to disappear Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Bug description: [Impact] bnx2x driver won't add all devices ports/interfaces. [Test case] Boot system with bnx2x device and verify all ports/interfaces have been added. [Potential regression] bnx2x devices won't be properly probed. Devices won't be added or SR-IOV won't be correctly supported. --- Original Description --- Works with focal kernel 5.4.0-80 Broken with focal kernel 5.4.0-88 On a Dell R720 with the BCM57800 based 1/10 Gigabit Integrated Network cards Kernel 5.11.22-3 causes half of the network interfaces to disappear specifically the 1gb ports. Commands like "ip link show" and "dmesg" no longer show eno3 and eno4 nor any other interface name for these ports. I've read the note in the release notes and this does not appear to be a case of the interface changing names, the 3rd and 4th interface don't show up at all. The card is based on the BCM57800 chipset and has two SFP+ and two gigabit ports on the same card. Commands like "ip link show" no longer show ports 3 and 4. "lspci" still shows four items. dmesg only shows the first two interfaces. This problem seems to be known upstream, and seems to be a regression. More information at https://bugzilla.proxmox.com/show_bug.cgi?id=3558 This is being seen at a customer during an openstack install. It would be appreciated if a workaround could be provided or the fix could be prioritized. Using standard Focal 20.04 LTS kernel (it installs ok with the working kernel then upgrades to the non-working one -- this is done through maas and is difficult to control). Tested other kernels like hwe-* and all seem to be affected too. Client does not want to disable SRIOV on whole card and also cannot disable only ports 3/4 (the bios will not allow it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945707/+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 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Hi Mauricio, We are seeing the issue only on r5.metal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1943817] Re: Realtek 8852 wifi kernel module is missing
Some recent kernel reviewing updates: https://patchwork.kernel.org/project/linux-wireless/list/?series=559649 Could anyone from kernel team tell us what's the plan here? Are we waiting for reviewing to be completed? At the moment, rt 8852a users rely on a third party package, so that's not good either... :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943817 Title: Realtek 8852 wifi kernel module is missing Status in linux package in Ubuntu: Confirmed Bug description: Hi, Just got a Thinkpad with Realtek 8852a wifi card. I installed Impish daily (kernel 5.13). Not recognized. The firmware is natively present in firmware folder, /rtw89/rtw8852a_fw.bin . But the kernel module is not loaded and in fact no module is loadable! sudo modprobe rtw8[completion] does not return this wifi card's module. So I did run for: https://github.com/lwfinger/rtw89 and it does work but needs to be done for each kernel upgrade... Note that Bluetooth was natively ok. I tried 5.14 Ubuntu kernel from unstable ppa but same issue. lspci 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: fthx 2333 F pulseaudio /dev/snd/controlC1: fthx 2333 F pulseaudio /dev/snd/controlC0: fthx 2333 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-9-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9.9-generic 5.14.1 RelatedPackageVersions: linux-restricted-modules-5.14.0-9-generic N/A linux-backports-modules-5.14.0-9-generic N/A linux-firmware1.199 Tags: impish Uname: Linux 5.14.0-9-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR 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.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943817/+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 1899953] Re: Crackling audio on Raspberry Pi Desktop
Worth noting that this issue only appears to occur when the fkms ("fake" KMS) overlay is in use on the Ubuntu Desktop for Raspberry Pi images. Under the kms ("full" KMS) overlay, the audio is fine. While kms is indeed the default overlay, it is likely (due to LP: #1946368 on impish) that many may be using fkms as a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1899953 Title: Crackling audio on Raspberry Pi Desktop Status in PulseAudio: Unknown Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: Attempting to play audio (e.g. from rhythmbox) on the raspberry pi desktop image, results in broken up / crackling audio. The "tsched=0" workaround noted in https://wiki.ubuntu.com/Audio/PositionReporting#Turning_off_PulseAudio_timer_scheduling successfully avoids the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1899953/+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 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
Hi Kleber, Thanks for the info. The impact on bionic/generic is also exclusively on aws r5.metal or broader? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1946642] Re: nvidia-graphics-drivers-390 ftbfs on armhf
That failed, missed one more place. Retesting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1946642] Re: nvidia-graphics-drivers-390 ftbfs on armhf
** Patch added: "lp1946642.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531917/+files/lp1946642.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1946642] Re: nvidia-graphics-drivers-390 ftbfs on armhf
Testing in https://bileto.ubuntu.com/#/ticket/4681 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1946231] Re: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)
adding the option "--before no_reset" seems to solve the issue with kernel 5.11.0-37 esptool --before no_reset --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin Even if I do not understand the why, this solves the issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946231 Title: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 14:59:58 2021 InstallationDate: Installed on 2020-08-29 (403 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946231/+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 1909814] Re: Medion Notebook Keyboard not working
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => 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/1909814 Title: Medion Notebook Keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: Fix Released Bug description: [Impact] The keyboard of some medion laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Bug description: [Impact] The expected to fail 'raw gso min size - 1' test in psock_snd.sh is not failing as expected, and thus this test will fail with: raw gso min size - 1 (expected to fail) tx: 1524 rx: 1472 OK This is because after commit 7c6d2ec ("net: be more gentle about silly gso requests coming from user"), we relaxed the min gso_size check in virtio_net_hdr_to_skb(). So when a packet which is smaller then the gso_size, GSO for this packet will not be set, the packet will be send/recv successfully. [Fix] * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd This patch can be cherry-picked into all affected kernels. I decided to skip those 5.8 variants, as the current cycle (2021-09-06) might be the last cycle for them. [Test] Run this psock_snd.sh script, this test will no longer exist and the script can proceed with the next test. [Where problems could occur] Removing this broken test should not have any negative impact to our tests. We will need to update our hints later. [Original Bug Report] Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG|
[Kernel-packages] [Bug 1939541] Re: ALSA: hda/cs8409: Add support for dolphin
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939541 Title: ALSA: hda/cs8409: Add support for dolphin Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] Dolphin devices have CS8409 HDA Bridge connected to two CS42L42 codecs. Codec 1 supports Headphone and Headset Mic. Codec 2 supports Line Out. [Fix] In order to support multiple CS42L42 codecs connected to a CS8409 HDA Bridge, a changeset of 27 patches is proposed to https://patchwork.kernel.org/project/alsa-devel/cover/20210811185654.6837-1-vita...@opensource.cirrus.com/ (now in linux-next), as well as two additional patches in https://lore.kernel.org/lkml/20210812183433.6330-1-vita...@opensource.cirrus.com/ that fixes pop sounds at insertion of earphone jack and reboot. The second patch of the latter changeset is on hold because of another fix series that deprecates the reboot_notify callback of HD-audio by forcibly doing runtime-suspend at shutdown. A Ubuntu sauced patch is also added to enable the now stand alone module snd-hda-codec-cs8409. [Test Case] Test on oem dolphin platform, as well as previous cs8409 platforms with one single codec. [Where problems could occur] While this is the first platform we have multiple codecs connected to a CS8409 HDA bridge, we may still have further stability or acoustic quality issues as we had for previous cirrus platforms. [Other Info] This also fixes default sample rate problem that was previously fixed by a oem-only package oem-fix-audio-cirrus-default-sample-rate. == original bug report == Dolphin devices have CS8409 HDA Bridge connected to two CS42L42 codecs. Codec 1 supports Headphone and Headset Mic. Codec 2 supports Line Out. Features: - Front and Read Jacks appear as separate jacks; Removal or connection of on jack should not affect the connection of the other. - Front Jack only shows up on jack detection. - Rear Jack is Phantom Jack. - Separate Volume Controls for each Jack To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939541/+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 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: Confirmed => 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/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: Fix Released Bug description: [Impact] This is a feature request to update the mpt3sas driver to latest version in upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04. This will allow users to use fixes and enhancements that landed upstream in 5.14. For this reason, Broadcom and Dell have requested to pull these patches to update the mpt3sas driver to the current upstream version. I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver v36.100.00.00, following are the commit ID's to update to 38.100.00.00 [Fixes] 8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers() 39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> "compatibility" bfb3f00c06 scsi: mpt3sas: Simplify bool comparison d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation 664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug 688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface 446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00 8278807abd scsi: core: Add scsi_device_busy() wrapper 020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic() 2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot 54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params 782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a static one d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within same 4 GB region 7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 GB region 970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 GB region 58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 GB region 2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within same 4 GB region c569de899b scsi: mpt3sas: Force reply post array allocations to be within same 4 GB region 37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00 a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues 3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach() 206a3afa94 scsi: mpt3sas: Fix a typo 4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement 3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset 16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query 3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers 2910a4a9e9 scsi: mpt3sas: Documentation cleanup e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware event 19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC init f2b1e9c6f8 scsi: core: Introduce scsi_build_sense() 84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add() Note: We have already posted patch to update driver version to 38.100.00.00 Other patches are already available in upstream . [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+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 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not covered by previous LTR reset fix in bug 1896598. [Fix] Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is requierd: * ADL-M: [8086:464d] * ADL-P: [8086:51b0] * ADL-S: [8086:7ab4] [Test Case] $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' ... 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ [Where problems could occur] This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT values to a fixed 3145728ns that is used on Windows. Devices might want to set itself to a smaller value, but while this is not yet correctly supported by VMD controller driver, so the device power consumption might be little worse than ideal. [Other Info] VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions newer than 5.6 should have already the supporting function. This patch targets Alder Lake cpus that are supported since 5.10-oem and on. == original bug report == * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, https://bugs.launchpad.net/bugs/1896598. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7
[Kernel-packages] [Bug 1914685] Re: Please enable CONFIG_UBSAN_BOUNDS
This bug was fixed in the package linux-oracle - 5.13.0-1008.10 --- linux-oracle (5.13.0-1008.10) impish; urgency=medium * impish/linux-oracle: 5.13.0-1008.10 -proposed tracker (LP: #1946331) * Miscellaneous Ubuntu changes - [Config] update toolchain version in configs after rebase [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 17:26:41 +0200 ** Changed in: linux-oracle (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux source package in Hirsute: Confirmed Status in linux-oracle source package in Hirsute: Confirmed Status in linux source package in Impish: Fix Released Status in linux-oracle source package in Impish: Fix Released Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+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 1942633] Re: Can not boot impish in Cavium ThunderX
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu) 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/1942633 Title: Can not boot impish in Cavium ThunderX Status in linux package in Ubuntu: Fix Released Bug description: Hi I am trying to deploy a Impish server (Ubuntu 5.11.0-13.14-generic 5.11.7) in arm64 description: Computer product: Cavium ThunderX CN88XX board width: 64 bits I tried 2 releases: - 20210817 ( https://images.maas.io/ephemeral-v3/stable/impish/arm64/20210817/ga-21.10/ ) - 20210830 ( https://images.maas.io/ephemeral-v3/candidate/impish/arm64/20210830/ ) 20210817: Ends the deploy successfully but fails to boot from disk: ``` [0.00] Booting Linux on physical CPU 0x00 [0x431f0a11] [0.00] Linux version 5.13.0-14-generic (buildd@bos02-arm64-018) (gcc (Ubuntu 10.3.0-6ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.37) #14-Ubuntu SMP Mon Aug 2 12:40:58 UTC 2021 (Ubuntu 5.13.0-14.14-generic 5.13.1) [0.00] Machine model: Cavium ThunderX CN88XX board [ 139.896752] raid6: xor() 1224 MB/s, rmw enabled [ 139.957046] raid6: using neon recovery algorithm [ 140.020937] xor: measuring software checksum speed [ 140.085571]8regs : 2432 MB/sec [ 140.149834]32regs : 2687 MB/sec [ 140.212202]arm64_neon : 4390 MB/sec [ 140.271985] xor: using function: arm64_neon (4390 MB/sec) [ 140.335013] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... [ 140.569847] Btrfs loaded, crc32c=crc32c-generic, zoned=yes Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf file were found. done. mdadm: No devices listed in conf file were found. ``` 20210830 Fails the network boot: ``` [ 140.351066] async_tx: api initialized (async) done. Begin: Running /scripts/init-premount ... cloud-initramfs-dyn-netconf: did no find a nic with 1c:1b:0d:0d:52:7c done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Waiting up to 180 secs for BOOTIF to become available ... Failure: Interface BOOTIF did not appear in time done. ipconfig: BOOTIF: SIOCGIFINDEX: No such device ipconfig: no devices to configure ``` I will attach full logs of each try. JFYI, this is the same machine as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942633/+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 1942043] Re: Noise will pop up during WB or stay in Ubuntu OS when external speaker attached
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942043 Title: Noise will pop up during WB or stay in Ubuntu OS when external speaker attached Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] HD-audio codec shutdown is not quite right when powering off the controller side. This causes pop noises on some platforms. [Fix] While previously in bug 1939541, a local fix for Cirrus CS8409 only is proposed the upstream as in https://lore.kernel.org/lkml/20210812183433.6330-2-vita...@opensource.cirrus.com/ . This initiated a discuss to create a generic solution as in https://lore.kernel.org/all/20210813081230.4268-1-ti...@suse.de/ . [Test Case] Shutdown Ubuntu that is running a patched kernel and see if a pop sound is still made. [Where problems could occur] While this tries to suspend the codec devices at shutting down, out of tree drivers without (runtime-)suspend support may fail to react correctly. And since this removes .reboot_notify callback from struct hda_codec_ops, it may break such oot drivers, too. [Other Info] This depends on patches for https://bugs.launchpad.net/bugs/1939541 . == original bug report == [Reproduce Steps] 1. Attach external speaker to SUT 2. Try to reboot SUT or stay in OS. [Results] Expected Result No noise. Actual Result Noise will pop up during WB or stay in Ubuntu OS when external speaker attached. [Others] [Scenario 1] Login to the Ubuntu OS. (Occurs only in Cirrus, within 5 seconds after logging in to OS) Can 100% reproduce on Cirrus MB with Ubuntu. Noise can be heard (咚咚 Sounds) after login the Ubuntu within 5 secs. [Scenario 2] Reboot Ubuntu OS (Both Curris and Realtek happen. WB/CB/shutdown OS) Can 100% reproduce on Cirrus MB with Ubuntu. Noise can be heard While both exiting OS and entering OS. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942043/+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 1942459] Re: Speakup modules not included in Hirsute kernel
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => 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/1942459 Title: Speakup modules not included in Hirsute kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] The kernel modules for the speakup screen reader are not available in Ubuntu 21.04/hirsute. $ modinfo speakup_ltlk modinfo: ERROR: Module speakup_ltlk not found. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: john 3207 F pulseaudio /dev/snd/pcmC0D0p: john 3207 F...m pulseaudio /dev/snd/controlC1: john 3207 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Sep 2 10:46:10 2021 InstallationDate: Installed on 2021-08-25 (8 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. enxf2766f074582 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=de5924a4-e0f6-4c11-a364-ea107efc1086 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2018 dmi.bios.release: 65.29 dmi.bios.vendor: Dell Inc. dmi.bios.version: A29 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA29:bd12/13/2018:br65.29:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. [Fix] CONFIG_ACCESSIBILITY=y CONFIG_SPEAKUP=y [Test Plan] Extract modules from linux-modules-extra and verify that speakup* modules exist. [Where problems could occur] Enabling CONFIG_ACCESSIBILITY could affect console output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459/+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 1928921] Re: LRMv5: switch primary version handling to kernel-versions data set
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1928921 Title: LRMv5: switch primary version handling to kernel-versions data set Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-restricted-modules source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-restricted-modules source package in Hirsute: Fix Released Bug description: Switch fetching dkms-versions data for these packages to the kernel- versions dataset. Currently the primary dkms-versions data is committed directly to the primary kernel packages. This allows this information to cascade reliably to all derivatives and their associated LRM packages. But once the primaries are closed it is increasingly hard to change this data. This makes performing an LRM-only respin very difficult as it differs in handling from a primary spin. We move the primary version dataset out of the kernel packages into a shared external "kernel-versions" dataset. Each package which needs this data then obtains the information it needs directly, with it committed locally to that package at update time. This renders preparation of am initial (-1) spin and a later LRM-only respin identicle. We simply update the shared dataset and perform a no-change rebuild (./update-versions) on them and they will automatically get the updated version information. We will want to update update-dkms-versions in all primary main packages, and introduce same into all LRM packages. As we already run update-dkms-versions in the primary main packages, and are introducing update-dkms-versions handling to update-versions in LRM this should not change kernel crank proceedure. The cycle proceedure will need a new step to update the shared kernel-versions dataset before cranking commences. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928921/+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 1932157] Re: [21.10 FEAT] KVM: Use interpretation of specification exceptions
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu) 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/1932157 Title: [21.10 FEAT] KVM: Use interpretation of specification exceptions Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Bug description: This allows KVM to let SIE interpret specification exceptions instead of doing this itself, leading to performance improvements. This feature will be made available with kernel >=5.15 A backport will be provided once available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1932157/+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 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method
This bug was fixed in the package linux-oracle - 5.13.0-1008.10 --- linux-oracle (5.13.0-1008.10) impish; urgency=medium * impish/linux-oracle: 5.13.0-1008.10 -proposed tracker (LP: #1946331) * Miscellaneous Ubuntu changes - [Config] update toolchain version in configs after rebase [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 17:26:41 +0200 ** Changed in: linux-oracle (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1931725 Title: initramfs-tools & kernel: use zstd as the default compression method Status in Ubuntu on IBM z Systems: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed- eoan-5.3/kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). amd64 supports zstd, but s390x does not. Will use this bug to enable zstd support on s390x. Upstream submitted patch https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+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 1942644] Re: Impish update: v5.13.14 upstream stable release
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) 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/1942644 Title: Impish update: v5.13.14 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.14 upstream stable release from git://git.kernel.org/ net: qrtr: fix another OOB Read in qrtr_endpoint_post bpf: Fix ringbuf helper function compatibility ASoC: rt5682: Adjust headset volume button threshold ASoC: component: Remove misplaced prefix handling in pin control functions platform/x86: Add and use a dual_accel_detect() helper ARC: Fix CONFIG_STACKDEPOT netfilter: ipset: Limit the maximal range of consecutive elements to add/delete netfilter: conntrack: collect all entries in one cycle once: Fix panic when module unload io_uring: rsrc ref lock needs to be IRQ safe blk-iocost: fix lockdep warning on blkcg->lock ovl: fix uninitialized pointer read in ovl_lookup_real_one() net: mscc: Fix non-GPL export of regmap APIs can: usb: esd_usb2: esd_usb2_rx_event(): fix the interchange of the CAN RX and TX error counters ceph: correctly handle releasing an embedded cap flush dt-bindings: sifive-l2-cache: Fix 'select' matching riscv: Ensure the value of FP registers in the core dump file is up to date powerpc: Re-enable ARCH_ENABLE_SPLIT_PMD_PTLOCK mm/memory_hotplug: fix potential permanent lru cache disable Revert "btrfs: compression: don't try to compress if we don't have enough pages" net: stmmac: fix kernel panic due to NULL pointer dereference of xsk_pool net: stmmac: fix kernel panic due to NULL pointer dereference of buf->xdp drm/i915: Fix syncmap memory leak drm/i915/dp: Drop redundant debug print drm/amdgpu: Cancel delayed work when GFXOFF is disabled drm/amdgpu: use the preferred pin domain after the check drm/amdgpu: Fix build with missing pm_suspend_target_state module export Revert "USB: serial: ch341: fix character loss at high transfer rates" USB: serial: option: add new VID/PID to support Fibocom FG150 usb: renesas-xhci: Prefer firmware loading on unknown ROM state usb: typec: tcpm: Raise vdm_sm_running flag only when VDM SM is running usb: dwc3: gadget: Fix dwc3_calc_trbs_left() usb: dwc3: gadget: Stop EP0 transfers during pullup disable scsi: core: Fix hang of freezing queue between blocking and running device RDMA/mlx5: Fix crash when unbind multiport slave RDMA/uverbs: Track dmabuf memory regions RDMA/bnxt_re: Add missing spin lock initialization IB/hfi1: Fix possible null-pointer dereference in _extend_sdma_tx_descs() RDMA/bnxt_re: Remove unpaired rtnl unlock in bnxt_re_dev_init() RDMA/rxe: Fix memory allocation while in a spin lock ice: do not abort devlink info if board identifier can't be found net: usb: pegasus: fixes of set_register(s) return value evaluation; igc: Use num_tx_queues when iterating over tx_ring queue e1000e: Fix the max snoop/no-snoop latency for 10M RDMA/efa: Free IRQ vectors on error flow ip_gre: add validation for csum_start xgene-v2: Fix a resource leak in the error handling path of 'xge_probe()' net: marvell: fix MVNETA_TX_IN_PRGRS bit number ucounts: Increase ucounts reference counter before the security hook net/sched: ets: fix crash when flipping from 'strict' to 'quantum' SUNRPC: Fix XPT_BUSY flag leakage in svc_handle_xprt()... ipv6: use siphash in rt6_exception_hash() ipv4: use siphash instead of Jenkins in fnhe_hashfun() cxgb4: dont touch blocked freelist bitmap after free net: dsa: hellcreek: Fix incorrect setting of GCL net: dsa: hellcreek: Adjust schedule look ahead window rtnetlink: Return correct error on changing device netns net: hns3: clear hardware resource when loading driver net: hns3: add waiting time before cmdq memory is released net: hns3: fix speed unknown issue in bond 4 net: hns3: fix duplicate node in VLAN list net: hns3: fix get wrong pfc_en when query PFC configuration media:
[Kernel-packages] [Bug 1940564] Re: Azure kernels fail to boot on some large Azure instance types
This bug was fixed in the package linux-azure - 5.13.0-1006.7 --- linux-azure (5.13.0-1006.7) impish; urgency=medium * impish/linux-azure: 5.13.0-1006.7 -proposed tracker (LP: #1946329) * Azure kernels fail to boot on some large Azure instance types (LP: #1940564) - Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue" * impish:linux 5.13 panic during systemd autotest (LP: #1946001) - azure: [Config] disable KFENCE [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 16:13:17 +0200 ** Changed in: linux-azure (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1940564 Title: Azure kernels fail to boot on some large Azure instance types Status in linux package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure-5.4 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-5.11 source package in Bionic: Invalid Status in linux-azure-5.4 source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure-5.4 source package in Focal: Invalid Status in linux source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-azure-5.4 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-azure source package in Impish: Fix Released Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure-5.4 source package in Impish: Invalid Bug description: [Impact] Azure kernels fail to boot on large Azure instance types. [Fix] revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to v4.14.240, v4.19.198" This commit originates from an unreleased kernel (5.14-rc1). According to the commit log it purports to head off possible future problems. It does not appear to address a specific bug. It has been backported to 4.14.y and 4.19.y. [Test Plan] Install and boot on an Azure Standard_D48_v3 instance. [Where problems could occur] iscsi requests could hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940564/+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 1942972] Re: Update fix for LP: #1936708
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942972 Title: Update fix for LP: #1936708 Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] There's a new fix for LP: #1936708, and it's more reliable than the old approach. So replace it. [Fix] Use eDP as predicate to enable max params. [Test] Users confirmed the fix can resolve their issue. [Where problems could occur] This patch reverts to the old behavior, which is to use max parameters, for older panels. If there's any new panel reports with older eDP version, this might change the behavior on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942972/+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 1940392] Re: fs: removing mandatory locks
This bug was fixed in the package linux-oracle - 5.13.0-1008.10 --- linux-oracle (5.13.0-1008.10) impish; urgency=medium * impish/linux-oracle: 5.13.0-1008.10 -proposed tracker (LP: #1946331) * Miscellaneous Ubuntu changes - [Config] update toolchain version in configs after rebase [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 17:26:41 +0200 ** Changed in: linux-oracle (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1940392 Title: fs: removing mandatory locks Status in linux package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Released Status in linux-oracle source package in Impish: Fix Released Bug description: Hello, Upstream is dicussing the removal of mandatory locks. To actually do this at some point distros will need to start disabling CONFIG_MANDATORY_FILE_LOCKING. It seems our kernel still defaults to CONFIG_MANDATORY_FILE_LOCKING=y. If feasible I'd like to propose disabling CONFIG_MANDATORY_FILE_LOCKING in the upcoming kernel releases. From the thread it seems that RHEL 8 and Fedora already disable mandatory locks: https://lore.kernel.org/lkml/c65c4e42-9661-1321-eaf8-61b1d6f89...@redhat.com Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940392/+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 1943935] Re: CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1943935 Title: CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] When output device is set to HDMI/DP and headset plugged in, there is no Headset device available in sound settings. [Fix] Proposed fix in https://patchwork.kernel.org/project/alsa-devel/patch/20210916095646.7631-1-vita...@opensource.cirrus.com/ , already accepted as https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=94d508fa3186d0cbc63765aa94d5cf3bd847694c . This also depends on two commits which already in mainline kernel that refactor device init. [Test Case] 1. Set output device to HDMI/DP 2. Plug headset 3. Check Sound settings for a new headset device [Where problems could occur] The last patch simply makes the onboard audio jack to use phantom jack. No much potential risk introduced. The two prerequisites simplifies init procedures and may need to receive some more stress tests especially those for suspend/resume, plug/unplug. [Other Info] This is for the new oem Dolphin platform that is only available in oem-5.13/oem-5.14 and impish. See bug 1939541. == original bug report == [Steps to reproduce] 1. Check output device is HDMI/DP audio and it works 2. Plug headset 3. Check Sound settings for Input & Output [Expected result] Sound settings should have headset when plugging [Actual result] Sound settings has no headset To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943935/+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 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock
This bug was fixed in the package linux - 5.13.0-19.19 --- linux (5.13.0-19.19) impish; urgency=medium * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE -- Andrea Righi Thu, 07 Oct 2021 11:09:51 +0200 ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: New Status in linux source package in Impish: Fix Released Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+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 1944028] Re: linux-aws 5.13: KCSAN bug on Xen-based instances
This bug was fixed in the package linux-aws - 5.13.0-1005.6 --- linux-aws (5.13.0-1005.6) impish; urgency=medium * impish/linux-aws: 5.13.0-1005.6 -proposed tracker (LP: #1946328) * linux-tools-aws package does not contain libperf-jvmti.so (LP: #1944754) - [Packaging] aws: Support building libperf-jvmti.so * Miscellaneous Ubuntu changes - [Config] aws: update configs and annotations after rebase [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 08:16:10 +0200 ** Changed in: linux-aws (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1944028 Title: linux-aws 5.13: KCSAN bug on Xen-based instances Status in linux-aws package in Ubuntu: Fix Released Bug description: 5.13 with KCSAN enabled reports the following bug on Xen-based instances. Maybe it's worth investigating to determine if they are false positives or not, for now, I think we can just disable CONFIG_KCSAN to prevent this boot problem: 200 01:51:29 INFO | kernel: [2.887005] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 201 01:51:29 INFO | kernel: [3.532196] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x26a/0x2f0 202 01:51:29 INFO | kernel: [6.159297] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 203 01:51:29 INFO | kernel: [ 10.502736] BUG: KCSAN: data-race in mutex_spin_on_owner+0x5b/0x130 204 01:51:29 INFO | kernel: [ 10.615868] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 205 01:51:29 INFO | kernel: [ 12.026134] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x26a/0x2f0 206 01:51:29 INFO | kernel: [ 12.543270] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 207 01:51:29 INFO | kernel: [ 13.687048] BUG: KCSAN: data-race in __xen_evtchn_do_upcall+0x60/0x100 208 01:51:29 INFO | kernel: [ 15.529253] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 209 01:51:29 INFO | kernel: [ 16.923586] BUG: KCSAN: data-race in mutex_spin_on_owner+0x5b/0x130 210 01:51:29 INFO | kernel: [ 17.501250] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x26a/0x2f0 211 01:51:29 INFO | kernel: [ 17.896641] BUG: KCSAN: data-race in mark_page_accessed / workingset_activation 212 01:51:29 INFO | kernel: [ 18.099471] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 213 01:51:29 INFO | kernel: [ 18.548714] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 214 01:51:29 INFO | kernel: [ 24.382191] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x26a/0x2f0 215 01:51:29 INFO | kernel: [ 24.590778] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 216 01:51:29 INFO | kernel: [ 24.743774] BUG: KCSAN: data-race in do_task_stat / handle_mm_fault 217 01:51:29 INFO | kernel: [ 25.029528] BUG: KCSAN: data-race in rwsem_spin_on_owner+0xd0/0x130 218 01:51:29 INFO | kernel: [ 28.295636] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 219 01:51:29 INFO | kernel: [ 28.340049] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 220 01:51:29 INFO | kernel: [ 33.598326] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 221 01:51:29 INFO | kernel: [ 40.784905] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 222 01:51:29 INFO | kernel: [ 45.871317] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 223 01:51:29 INFO | kernel: [ 48.590241] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 224 01:51:29 INFO | kernel: [ 55.486723] BUG: KCSAN: data-race in xen_vcpu_stolen+0x33/0x40 225 01:51:29 INFO | kernel: [ 55.825362] BUG: KCSAN: data-race in evtchn_2l_handle_events+0x103/0x2f0 226 01:51:29 INFO | kernel: [ 59.420467] BUG: KCSAN: data-race in
[Kernel-packages] [Bug 1944754] Re: linux-tools-aws package does not contain libperf-jvmti.so
This bug was fixed in the package linux-aws - 5.13.0-1005.6 --- linux-aws (5.13.0-1005.6) impish; urgency=medium * impish/linux-aws: 5.13.0-1005.6 -proposed tracker (LP: #1946328) * linux-tools-aws package does not contain libperf-jvmti.so (LP: #1944754) - [Packaging] aws: Support building libperf-jvmti.so * Miscellaneous Ubuntu changes - [Config] aws: update configs and annotations after rebase [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 08:16:10 +0200 ** Changed in: linux-aws (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1944754 Title: linux-tools-aws package does not contain libperf-jvmti.so Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws source package in Impish: Fix Released Bug description: SRU Justification [Impact] For debugging purposes, on EC2, people will install linux-tools-$(uname -r) to help with debugging the system. This selects the kernel specific linux-tools package, and for the AWS variant, we are missing the library libperf-jvmti.so to enable tracing Java applications with perf. To get a libperf-jvmti.so library, we need to perform an additional and confusing step by installing linux-tools-generic to get a copy of the library. Customers on AWS EC2 should not have to do this. We would like the linux-tools-aws packages to contain libperf-jvmti.so. [Test Plan] Install linux-tools-aws, check for libperf-jvmti.so [Where problems could occur] Given that linux-tools-aws installs in a versioned (unique) directory, there should be no conflicts or possibility of regression. [Additional info] SF: #00319833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1944754/+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 1946001] Re: impish:linux 5.13 panic during systemd autotest
This bug was fixed in the package linux-aws - 5.13.0-1005.6 --- linux-aws (5.13.0-1005.6) impish; urgency=medium * impish/linux-aws: 5.13.0-1005.6 -proposed tracker (LP: #1946328) * linux-tools-aws package does not contain libperf-jvmti.so (LP: #1944754) - [Packaging] aws: Support building libperf-jvmti.so * Miscellaneous Ubuntu changes - [Config] aws: update configs and annotations after rebase [ Ubuntu: 5.13.0-19.19 ] * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337) * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001) - [Config] disable KFENCE [ Ubuntu: 5.13.0-18.18 ] * impish/linux: 5.13.0-18.18 -proposed tracker (LP: #1945995) * [21.10 FEAT] KVM: Use interpretation of specification exceptions (LP: #1932157) - KVM: s390: Enable specification exception interpretation -- Andrea Righi Fri, 08 Oct 2021 08:16:10 +0200 ** Changed in: linux-aws (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1946001 Title: impish:linux 5.13 panic during systemd autotest Status in Release Notes for Ubuntu: New Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Impish: Fix Released Bug description: Found this when running the systemd autopkgtest on linux-aws 5.13.0-1004.5 (apparently it seems to affect nested kvm only): systemd-testsuite login: [ 70.235559] int3: [#1] SMP NOPTI [ 70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 5.13.0-1004-aws #5-Ubuntu [ 70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 [ 70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7 [ 70.237994] RSP: 0018:aabd001cfd78 EFLAGS: 0286 [ 70.239655] RAX: 97e8411da400 RBX: 1000 RCX: 0400 [ 70.239670] RDX: 0001 RSI: 0cc0 RDI: 97e8411da400 [ 70.239679] RBP: aabd001cfdb8 R08: R09: 9802 [ 70.239688] R10: R11: R12: 97e8411da400 [ 70.239696] R13: 97e8411da400 R14: 0cc0 R15: b2737cf0 [ 70.239705] FS: 7fc6fc243380() GS:97e85c00() knlGS: [ 70.239713] CS: 0010 DS: ES: CR0: 80050033 [ 70.239720] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 06f0 [ 70.239727] Call Trace: [ 70.239733] getname_flags.part.0+0x30/0x1b0 [ 70.239741] getname+0x35/0x50 [ 70.239746] do_sys_openat2+0x64/0x150 [ 70.239753] __x64_sys_openat+0x55/0x90 [ 70.239759] do_syscall_64+0x61/0xb0 [ 70.239766] ? do_syscall_64+0x6e/0xb0 [ 70.239772] ? do_sync_core+0x26/0x30 [ 70.239779] ? flush_smp_call_function_queue+0x119/0x190 [ 70.239786] ? exit_to_user_mode_prepare+0x37/0xb0 [ 70.239793] ? irqentry_exit_to_user_mode+0x9/0x20 [ 70.239800] ? irqentry_exit+0x19/0x30 [ 70.239807] ? sysvec_call_function+0x4e/0x90 [ 70.239813] ? asm_sysvec_call_function+0xa/0x20 [ 70.239819] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 70.239826] RIP: 0033:0x7fc6fca946e4 [ 70.239834] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 16 d2 f7 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 4 [ 70.239845] RSP: 002b:7ffc9699f1a0 EFLAGS: 0293 ORIG_RAX: 0101 [ 70.240063] RAX: ffda RBX: RCX: 7fc6fca946e4 [ 70.240075] RDX: 00080802 RSI: 556e8d5885d0 RDI: ff9c [ 70.240085] RBP: 556e8d5885d0 R08: R09: [ 70.240095] R10: R11: 0293 R12: 00080802 [ 70.240104] R13: R14: 556e8d59dd90 R15: fffa [ 70.240113] Modules linked in: btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raidy [ 70.281001] ---[ end trace 044cf87b8c867a36 ]--- [ 70.281099] RIP: 0010:kmem_cache_alloc+0x57/0x240 [ 70.281107] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7 [ 70.281115] RSP: 0018:aabd001cfd78 EFLAGS: 0286 [ 70.281132] RAX: 97e8411da400 RBX: 1000 RCX: 0400 [ 70.281138] RDX: 0001 RSI: 0cc0 RDI: 97e8411da400 [ 70.281143] RBP: aabd001cfdb8 R08: R09: 9802 [ 70.281148] R10: R11: R12: 97e8411da400 [ 70.281154] R13:
[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
This issue is also affecting the bionic/linux generic kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal Status in linux-aws package in Ubuntu: New Bug description: When creating an r5.metal instance on AWS, the default kernel is bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux- aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel. If I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel- team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' from mount options and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+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 1946642] Re: nvidia-graphics-drivers-390 ftbfs on armhf
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
Verification can only be done as an inverse proof. The revert is included and we have not heard about any issues. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942902 Title: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption" Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: In order to address https://bugs.launchpad.net/bugs/1933074 the following SAUCE patch was introduced. Colin Ian King (1): UBUNTU: SAUCE: ext4: fix directory index node split corruption fs/ext4/namei.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) Meanwhile the issue addressed by this patch was fixed upstream with commit 877ba3f729fd ("ext4: fix potential htree corruption when growing large_dir directories"). The upstream patch was already cherry-picked to hirsute with "upstream stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with "v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6). [1] BugLink: https://bugs.launchpad.net/bugs/1942123 [2] BugLink: https://bugs.launchpad.net/bugs/1941798 Therefore the SAUCE patch is obsolete and can be either dropped or reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+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 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
Looking at the latest ADT run [1] this subtest is no longer failing. [1] https://autopkgtest.ubuntu.com/results/autopkgtest- hirsute/hirsute/amd64/l/linux/20210928_124449_9b7e9@/log.gz ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Bug description: [Impact] The expected to fail 'raw gso min size - 1' test in psock_snd.sh is not failing as expected, and thus this test will fail with: raw gso min size - 1 (expected to fail) tx: 1524 rx: 1472 OK This is because after commit 7c6d2ec ("net: be more gentle about silly gso requests coming from user"), we relaxed the min gso_size check in virtio_net_hdr_to_skb(). So when a packet which is smaller then the gso_size, GSO for this packet will not be set, the packet will be send/recv successfully. [Fix] * cfba3fb68960b4 selftests/net: remove min gso test in packet_snd This patch can be cherry-picked into all affected kernels. I decided to skip those 5.8 variants, as the current cycle (2021-09-06) might be the last cycle for them. [Test] Run this psock_snd.sh script, this test will no longer exist and the script can proceed with the next test. [Where problems could occur] Removing this broken test should not have any negative impact to our tests. We will need to update our hints later. [Original Bug Report] Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset
[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs
This message re appeared and is flooding my syslog file. I am now on Ubuntu 20.04 kernel version 5.4.0. I am investigating. Any tips will be appreciated. I have tried a couple of the above fixes no luck yet. -- 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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+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 1946643] [NEW] Error on prime-supported not being installed
Public bug reported: - install impish daily on a thinkpad P15 with nvidia - log into a wayland session - install and try to start nvidia-settings, you get that warning ** (nvidia-settings:82581): WARNING **: 13:46:03.769: PRIME: Failed to execute child process ?/usr/bin/prime-supported? (No such file or directory) should nvidia-settings recommends at least nvidia-prime? ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1946643 Title: Error on prime-supported not being installed Status in nvidia-settings package in Ubuntu: New Bug description: - install impish daily on a thinkpad P15 with nvidia - log into a wayland session - install and try to start nvidia-settings, you get that warning ** (nvidia-settings:82581): WARNING **: 13:46:03.769: PRIME: Failed to execute child process ?/usr/bin/prime-supported? (No such file or directory) should nvidia-settings recommends at least nvidia-prime? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1946643/+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 1946642] Re: nvidia-graphics-drivers-390 ftbfs on armhf
Testing patch in https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4680 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1946642] Re: nvidia-graphics-drivers-390 ftbfs on armhf
** Patch added: "lp1946642.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531904/+files/lp1946642.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1946642] [NEW] nvidia-graphics-drivers-390 ftbfs on armhf
Public bug reported: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz ** Affects: nvidia-graphics-drivers-390 (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-390 in Ubuntu. https://bugs.launchpad.net/bugs/1946642 Title: nvidia-graphics-drivers-390 ftbfs on armhf Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia-graphics-drivers-390 ftbfs on armhf In file included from /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:16: /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c: In function ‘os_flush_cpu_write_combine_buffer’: /var/lib/dkms/nvidia/390.144/build/common/inc/nv-linux.h:467:43: error: implicit declaration of function ‘outer_sync’ [-Werror=implicit-function-declaration] 467 | #define WRITE_COMBINE_FLUSH(){ dsb(); outer_sync(); } | ^~ /var/lib/dkms/nvidia/390.144/build/nvidia/os-interface.c:951:5: note: in expansion of macro ‘WRITE_COMBINE_FLUSH’ 951 | WRITE_COMBINE_FLUSH(); | ^~~ https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/n/nvidia-graphics- drivers-390/20211011_104931_6a71c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+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 1946638] Re: Kernet stack is corrupted on installation Ubuntu 21.10
System isn’t starting unable to collect logs. -- 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/1946638 Title: Kernet stack is corrupted on installation Ubuntu 21.10 Status in linux package in Ubuntu: Incomplete Bug description: Unable to install Ubuntu 21.10 getting error when try to run ubuntu from usb installation. Kernel Panic + Kernel stack is corrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946638/+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 1946231] Re: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)
I confirm the problem on my two computers with KDE Neon after upgrading the kernel to 5.11.0-37-generic. There is no problem on kernel 5.11.0-36-generic. I use a development board NodeMCU with CH340G -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946231 Title: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 14:59:58 2021 InstallationDate: Installed on 2020-08-29 (403 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946231/+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 1946231] Re: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1946231 Title: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: the esp8266 development boards like wemos D1 mini have an integrated usb-uart converter which allows to flash/monitor/debug the esp8266 by usb cable and a tool called esptool on linux, which is either standalone (esptool package) or integrated into some IDE (platformio + visio) dmesg output: [ 46.614510] usbcore: registered new interface driver usbserial_generic [ 46.614523] usbserial: USB Serial support registered for generic [ 46.615912] usbcore: registered new interface driver ch341 [ 46.615925] usbserial: USB Serial support registered for ch341-uart [ 46.615938] ch341 1-9:1.0: ch341-uart converter detected [ 46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0 This convenient flashing method worked without issues up to kernel 5.11.0-36-generic and stopped working with 5.11.0-37-generic. The issue remains the same whether I use the esptool package or the version bundled with platformio, >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 0x firmware.bin esptool.py v2.8 Serial port /dev/ttyUSB0 Connecting_._._._._._._ A fatal error occurred: Failed to connect to ESP8266: Timed out waiting for packet header The communication to the esp8266 still seems to work, but the flash process includes some additional DTR/RTS magic in the beginning to switch the esp into flash mode before transmitting the data. My impression is that this DTR/RTS process might be broken. I can flash an esp with an external UART (some dongle) and manually triggering the flash mode. I tried with several cables, esps, ... Booting the older kernel (5.11.0-36-generic) solves the issue ... There seems to be an update to the ch341 from kernel -36 to -37, but it is beyond my knowledge whether there is any connection. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 6 14:59:58 2021 InstallationDate: Installed on 2020-08-29 (403 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1946231/+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 1946393] Re: Fix byte count on fragmented packets in tc ct action
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1946393 Title: Fix byte count on fragmented packets in tc ct action Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: In Progress Bug description: * Explain the bug First fragmented packets (frag offset = 0) byte len is zeroed when stolen by ip_defrag(). And since act_ct update the stats only afterwards (at end of execute), bytes aren't correctly accounted for such packets. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules as below e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run fragmented icmp ping traffic (e.g ping -s 2000) dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on frag=first rule: ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first), packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1) bytes would be zero if bug occurs. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1946393/+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 1946638] 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 1946638 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/1946638 Title: Kernet stack is corrupted on installation Ubuntu 21.10 Status in linux package in Ubuntu: Incomplete Bug description: Unable to install Ubuntu 21.10 getting error when try to run ubuntu from usb installation. Kernel Panic + Kernel stack is corrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946638/+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 1946638] Re: Kernet stack is corrupted on installation Ubuntu 21.10
** Project changed: ubuntu-desktop-installer => 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/1946638 Title: Kernet stack is corrupted on installation Ubuntu 21.10 Status in linux package in Ubuntu: New Bug description: Unable to install Ubuntu 21.10 getting error when try to run ubuntu from usb installation. Kernel Panic + Kernel stack is corrupted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946638/+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 1946638] [NEW] Kernet stack is corrupted on installation Ubuntu 21.10
You have been subscribed to a public bug: Unable to install Ubuntu 21.10 getting error when try to run ubuntu from usb installation. Kernel Panic + Kernel stack is corrupted. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 21.10 beta impish indri ubuntu -- Kernet stack is corrupted on installation Ubuntu 21.10 https://bugs.launchpad.net/bugs/1946638 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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Same for me (Thinkpad E15 Gen3) The last kernel that worked was 5.12.19-051219-generic (which I need to make wifi work) -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX 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.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
** Tags removed: bugnameltc-192677 severity-high ** Tags added: bugnameltc-194783 severity-medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+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 1946486] 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 1946486 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Confirmed Bug description: It looks like this issue is affecting some ARM64 bare metal node: * helo-kernel 2 failed out of 2 attempts * kuzzle 11 failed out of 13 attempts (as far as I can recall 2 deployments failed early, the system was not deployed at all, so probably we can call it 9 failed) The boot test will fail, the system was unable to reboot with the 5.11.0-27-realtime kernel, here is the steps (integrated with the deployment script) 1. Deploy this node with Hirsute 2. Install the 5.11.0-27-realtime kernel and set to boot with this kernel by using the boot-kernel-simple in ckct. Reboot 3. System can boot with 5.11.0-27-realtime, reboot again to make sure it's OK It seem the system will stuck at the last reboot attempt in step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+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 1946486] Re: Unable to reboot ARM64 node with 5.11.0-27-realtime
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => Incomplete ** Changed in: linux (Ubuntu Hirsute) 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/1946486 Title: Unable to reboot ARM64 node with 5.11.0-27-realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Bug description: It looks like this issue is affecting some ARM64 bare metal node: * helo-kernel 2 failed out of 2 attempts * kuzzle 11 failed out of 13 attempts (as far as I can recall 2 deployments failed early, the system was not deployed at all, so probably we can call it 9 failed) The boot test will fail, the system was unable to reboot with the 5.11.0-27-realtime kernel, here is the steps (integrated with the deployment script) 1. Deploy this node with Hirsute 2. Install the 5.11.0-27-realtime kernel and set to boot with this kernel by using the boot-kernel-simple in ckct. Reboot 3. System can boot with 5.11.0-27-realtime, reboot again to make sure it's OK It seem the system will stuck at the last reboot attempt in step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1946486/+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 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
Launchpad has imported 1 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=2009977. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-10-02T15:29:29+00:00 byron.c.hawkins wrote: 1. Please describe the problem: Fedora 34 is totally unusable on an Acer Aspire 1 A114-32-P9MN (laptop), which probably does not have a quality BIOS implementation, but does work fine with Debian 11, Oracle Linux 8.4, etc. It only has problems with Fedora 34. The machine constantly reports "soft lockup" and something about a watchdog, which I know nothing about, really. The "soft lockup" occurs in many different modules and contexts (as indicated by the vast number of stack traces in the system logs). Booting from a live USB of Fedora 34, it often took more than 30 minutes to reach the initial desktop, whereas Oracle Linux boots in about 10 seconds and never causes a "soft lockup". I tried dozens of configuration adjustments to workaround the problem, but nothing improved. Considering the large number of user reports mentioning "soft lockup" on Fedora 34, it seems to me that something is seriously wrong with the build. For now, I have moved to Oracle Linux and will not install Fedora again on any machine. 2. What is the Version-Release number of the kernel: 5.13.4-200.fc34.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : I didn't notice any problems on Fedora 32. After upgrading to Fedora 34 (5.13.4-200.fc34.x86_64), the machine is totally unusable because of constant "soft lockups" occurring in many different components and contexts. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Install Fedora 34 on an Acer Aspire 1 A114-32-P9MN, or just boot from a live USB. It will hang with soft lockups. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Sorry, I switched to Oracle Linux, and am in the process of migrating all my machines. Fedora is not an option if it has such severe problems on basic commodity hardware. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No, just a plain live USB will trigger the problem at its fullest severity. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Sorry, the system has been wiped clean for an install of Oracle Linux, which works with no problems. But it any case, the machine was responding so poorly under Fedora 34 that it would have been nearly impossible to obtain the logs, even by simply copying them to a USB drive. The machine is entirely crippled under Fedora 34. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- hwe-5.11/+bug/1931001/comments/7 ** Changed in: fedora Status: Unknown => Confirmed ** Changed in: fedora Importance: Unknown => Undecided -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0]
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
I also tied blacklisting only "i801_smbus" but that gave the same issue. Only blacklisting "i2c_i801" is currently the best workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+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 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
** Bug watch added: Red Hat Bugzilla #2009977 https://bugzilla.redhat.com/show_bug.cgi?id=2009977 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=2009977 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+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 1946601] Re: linux-image-5.13.0-1007-raspi does not include cdc_acm module
You need to install the package linux-modules-extra (which is new in impish). ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1946601 Title: linux-image-5.13.0-1007-raspi does not include cdc_acm module Status in linux-raspi package in Ubuntu: Invalid Bug description: I recently upgraded to 21.10 to give it a spin. Till now the cdc_acm kernel module was included, however this is not the case for 5.13. An equivalent amd64 5.13 kernel does. root@rpi:~# dlocate -S cdc-acm.ko linux-modules-5.11.0-1019-raspi: /lib/modules/5.11.0-1019-raspi/kernel/drivers/usb/class/cdc-acm.ko root@pc:~# dlocate -S cdc-acm.ko linux-modules-extra-5.11.0-37-generic: /lib/modules/5.11.0-37-generic/kernel/drivers/usb/class/cdc-acm.ko linux-modules-extra-5.13.0-16-generic: /lib/modules/5.13.0-16-generic/kernel/drivers/usb/class/cdc-acm.ko I have run the following to circumvent this issue: # flash-kernel --force 5.11.0-1019-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946601/+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 1905591] Re: no brightness control in {455, 460} after update from 450
Hi All, Please try with the EnableBrightnessControl =1 as kernel parameter or add it in xorg.conf file. You can add it in device section as shown below - Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "NVIDIA RTX A3000 Laptop GPU" Option "RegistryDwords" "EnableBrightnessControl=1" EndSection After change in the xorg, please uninstall / install the driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1905591 Title: no brightness control in {455,460} after update from 450 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-455 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile]: WORKS FINE: nvidia-driver-450: 450.102.04-0ubuntu0.18.04.1 NO BRIGHTNESS CONTROL: nvidia-driver-455: 455.38-0ubuntu0.18.04.1 nvidia-driver-460: 460.32.03-0ubuntu0.18.04.1 nvidia-driver-460: 460.39-0ubuntu0.18.04.1 *WORKAROUND: See comment #11 (add nvidia drivers to initramfs). *Note that 460 fixes it for a 20.04 ThinkPad P73 per comment #6, but not for my 18.04.5 Lenovo ThinkPad X1 per comment #5. Updating to nvidia-driver-455 (or -460) results in loss of brightness control. On boot, the laptop display brightness is somewhat less than fully bright and cannot be changed. The brightness up/down keys do pop up the gnome gui brightness widget, and /sys/class/backlight/nvidia_0/* values do change, but the actual display's brightness does not. Problem occurs with either version of nvidia-driver-455 (the archive or the ~graphics-drivers/PPA) or any version of -460. Normal functionality returns if I downgrade to any version of nvidia- driver-450. Also observed: 455 and 460 temporarily display some pixel garbage while mode-switching during the graphic login sequence. Only a minor glitch, but note that 450 does not exhibit that issue either. Note also that manually applying this to /lib/systemd/system/nvidia-persistenced.service has no effect on the problem: https://github.com/hugh712/nvidia-graphics-drivers/commit/bccad5ee6444dd8c5c47ba19ea0232106a1086f5 Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic kernel: 5.4.0-54-generic #60~18.04.1-Ubuntu SMP Fri Nov 6 17:25:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1905591/+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 1944575] Re: Acer Aspire 5 issue when headphone plug in before login
I tested this kernel found no change at all. Still left/right channel are merged into both for headphones and microphone is not detected after a shutdown/power up or reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944575 Title: Acer Aspire 5 issue when headphone plug in before login Status in linux package in Ubuntu: Confirmed Bug description: Hello, Acer Aspire A515-56-57XR with ALC255 when headphone is plugged in before login causes few issues. I will list them below: - When headphones are plugged in and if I restart/shutdown-turn on the laptop and log in it does not detect headphones microphone at all and internal microphone is selected by default. - For output device headphones are plugged in but left/right channel is merged into both channels - To fix this need to re-plug the headphones/earphones and the issue goes away or after a restart/shutdown plug in only after logging in. - This issue does not occur when log off and log in only after a restart or cold boot from a shutdown while headphones/earphones are left plugged in. In another similar thread to this lots of other issues were fixed and they have been already merged into official kernel now. I will put a link to it below for reference. Looking to fix this issue now. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bijay 2343 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-19 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing Bus 001 Device 003: ID 8087:0026 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-56 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=9c557228-52d9-4013-9bdb-4e16712575d1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-34-generic N/A linux-backports-modules-5.11.0-34-generic N/A linux-firmware 1.187.16 Tags: focal Uname: Linux 5.11.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 05/26/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:sku:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944575/+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