[Kernel-packages] [Bug 2008434] Re: NBS cleanup required in lunar-proposed
Removing packages from lunar: libcuda1-384 390.154-0ubuntu1 in lunar armhf libnvidia-cfg1-390 390.154-0ubuntu1 in lunar armhf libnvidia-compute-390 390.154-0ubuntu1 in lunar armhf libnvidia-fbc1-390 390.154-0ubuntu1 in lunar armhf libnvidia-gl-390 390.154-0ubuntu1 in lunar armhf libnvidia-ifr1-390 390.154-0ubuntu1 in lunar armhf nvidia-384 390.154-0ubuntu1 in lunar armhf nvidia-384-dev 390.154-0ubuntu1 in lunar armhf nvidia-compute-utils-390 390.154-0ubuntu1 in lunar armhf nvidia-dkms-390 390.154-0ubuntu1 in lunar armhf nvidia-driver-390 390.154-0ubuntu1 in lunar armhf nvidia-headless-390 390.154-0ubuntu1 in lunar armhf nvidia-headless-no-dkms-390 390.154-0ubuntu1 in lunar armhf nvidia-kernel-common-390 390.154-0ubuntu1 in lunar armhf nvidia-kernel-source-390 390.154-0ubuntu1 in lunar armhf nvidia-utils-390 390.154-0ubuntu1 in lunar armhf xserver-xorg-video-nvidia-390 390.154-0ubuntu1 in lunar armhf Comment: NBS 17 packages successfully removed. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Triaged => Fix Released -- 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/2008434 Title: NBS cleanup required in lunar-proposed Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2008434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982776] Re: linux-modules for -kvm does not include dm-crypt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1982776 Title: linux-modules for -kvm does not include dm-crypt Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Confirmed Status in linux-kvm source package in Jammy: Confirmed Bug description: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1982776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982776] Re: linux-modules for -kvm does not include dm-crypt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1982776 Title: linux-modules for -kvm does not include dm-crypt Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Confirmed Status in linux-kvm source package in Jammy: Confirmed Bug description: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1982776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Ok. I redacted: 0ca190805784 scsi: smartpqi: Call scsi_done() directly 64fc9015fbeb scsi: smartpqi: Switch to attribute groups Pulling 64fc9015fbeb scsi: smartpqi: Switch to attribute groups meant I had to update 3be5fe354d01 scsi: smartpqi: Enable SATA NCQ priority in sysfs For some reason I thought they would be added to your latest kernel. Sorry about that. Can we try again? I can give you some git format-patch tarball... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more
I have tested test kernel https://people.canonical.com/~mreed/dell/lp_1999883_dapc/. and i can able to see reduced bootup time. No other issues observed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008527 Title: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] When system profile is set to "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more
If there is more CPU cores then OS booting is taking more time to boot the OS, and then applied below patch and checked OS booting time is reducing 10sec in 192C CPU. I would request you to please consider this patch into Ubuntu-22.04 so that we can see faster os booting when cpu core count is more. [PATCH] cpufreq: acpi: Defer setting boost MSRs https://lore.kernel.org/linux-pm/20221102195957.82871-1-stuart.w.ha...@gmail.com/ Improved boot up time in Performance Per Watt (DAPC) before/after boot times results -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008527 Title: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] When system profile is set to "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more
I have created a test kernel can you test it and provide feedback? https://people.canonical.com/~mreed/dell/lp_1999883_dapc/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008527 Title: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] When system profile is set to "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] [NEW] [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more
Public bug reported: SRU Justification: [Impact] When system profile is set to "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] ** Affects: linux (Ubuntu) Importance: Low Assignee: Michael Reed (mreed8855) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Low Assignee: Michael Reed (mreed8855) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008527 Title: [SRU]When system profile is set to "Performance per Watt (DAPC)" in BIOS, Bootup time is taking more Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] When system profile is set to "Performance Per Watt (DAPC)" using BIOS setting, then install Ubuntu-22.04 and boot into OS then check the bootup time. How reproducible: Always Steps to Reproduce: 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007759] Re: Spotify freezes my entire system
Hello, I have the same problem on Lenovo "ThinkPad T14s Gen 1" and "AMD Ryzen 7 PRO 4750U with RadeonGraphics" on Ubuntu 22.04.2 LTS. Here are the last lines before freezing :( Feb 24 22:16:33 ntb2525 /usr/libexec/gdm-x-session[2298]: (II) event22 - RAPOO BT4.0 Mouse: SYN_DROPPED event - some input events have been lost. Feb 24 22:16:33 ntb2525 kernel: [123304.315870] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Feb 24 22:16:33 ntb2525 kernel: [123304.487830] gmc_v9_0_process_interrupt: 130817 callbacks suppressed Feb 24 22:16:33 ntb2525 kernel: [123304.487841] amdgpu :06:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:1 pasid:32785, for process spotify pid 333898 thread spotify:cs0 pid 333951) Feb 24 22:16:33 ntb2525 kernel: [123304.487860] amdgpu :06:00.0: amdgpu: in page starting at address 0x80010422 from IH client 0x12 (VMC) Feb 24 22:16:33 ntb2525 kernel: [123304.487869] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 24 22:16:33 ntb2525 kernel: [123304.487874] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 24 22:16:33 ntb2525 kernel: [123304.487879] amdgpu :06:00.0: amdgpu: MORE_FFeb 24 22:19:09 ntb2525 lvm[937]: 2 logical volume(s) in volume group "vgubuntu" monitored In the attachment there is a syslog after spotify run. Thank you ** Attachment added: "syslog-spotify-freeze.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007759/+attachment/5649874/+files/syslog-spotify-freeze.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007759 Title: Spotify freezes my entire system Status in linux package in Ubuntu: Confirmed Bug description: When I open spotify and have it open for a while my system freezes and I need to hard reset afterwards. ubuntu 22.10 spotify version 1.1.84.716.gc5f8b819 The main error that I always get aren't included in any txt files but here is the one error I copy paste from askubuntu: retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00140051 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: RW: 0x1 Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: [mmhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32776, for process spotify pid 13673 thread spotify:cs0 pid 13735) Feb 02 22:37:26 kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800106a2 from IH client 0x12 (VMC) -- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian 1576 F wireplumber /dev/snd/controlC0: adrian 1576 F wireplumber /dev/snd/seq:adrian 1573 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 20:11:39 2023 InstallationDate: Installed on 2023-01-27 (21 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy
[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
Update from upstream:
The patch (v2) was dropped because a customer reported it did not fix
their issue. I just reached out to the developer for an ETA to fix it
and will keep you posted.
Additionally there is ongoing discussion around the V2 of that patch here:
https://lore.kernel.org/intel-wired-lan/ygay1oxikvo.fsf@localhost/T/#m31a3f2847d013a41104524bd81e7f2fa481b4b97
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004262
Title:
Intel E810 NICs driver in causing hangs when booting and bonds
configured
Status in linux package in Ubuntu:
Incomplete
Bug description:
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
After beonding is enabled on switch and server side, the system will hang at
initialing ubuntu. The kernel loads but around starting the Network Services
the system can hang for sometimes 5 minutes, and in other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start
and never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup
and all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy
uec-images
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/14/2022
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 0PJ7YJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge R650
dmi.product.sku: SKU=0912;ModelName=PowerEdge R650
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008523] [NEW] Make kexec work by default on secureboot systems
Public bug reported: Make kexec work by default on secureboot systems Lots of people are confused by kexec failing on secureboot systems, without realising that on Ubuntu one needs to use the option to use a modern syscall that works on secureboot systems since like forever. Let's make the mode that works the default one. ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: Fix Committed ** Changed in: kexec-tools (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2008523 Title: Make kexec work by default on secureboot systems Status in kexec-tools package in Ubuntu: Fix Committed Bug description: Make kexec work by default on secureboot systems Lots of people are confused by kexec failing on secureboot systems, without realising that on Ubuntu one needs to use the option to use a modern syscall that works on secureboot systems since like forever. Let's make the mode that works the default one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/2008523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008522] 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 2008522 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/2008522 Title: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle Status in intel: Fix Released Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. Target Kernel: 6.3 Target Release: 23.10 [HW/SW Information] Meteor Lake [Business Justification] Platform enabling Upstream: Merged 6.3 Commit ID: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008522] [NEW] Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle
Public bug reported: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. Target Kernel: 6.3 Target Release: 23.10 [HW/SW Information] Meteor Lake [Business Justification] Platform enabling Upstream: Merged 6.3 Commit ID: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 ** Affects: intel Importance: High Status: Fix Released ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel-kernel-23.10 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008522 Title: Intel_powerclamp use powercap/idle-inject and allow cpumask to inject idle Status in intel: Fix Released Status in linux package in Ubuntu: New Bug description: [Feature Description] Use the powercap/idle-inject framework for intel Power clamp driver. Allow CPU mask and max idle percent as module parameter. This way way driver can be used for LPM mode in MTL. Target Kernel: 6.3 Target Release: 23.10 [HW/SW Information] Meteor Lake [Business Justification] Platform enabling Upstream: Merged 6.3 Commit ID: acbc661032b8,bbfc3349c4e7,c7cd6f04c0df,98e596fc85fe,ebf519710218,966d0ab67350,621084965459,8526eb7fc75a,8e4736358837,c4e927da893b68b99e94a4a2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1924623] Re: Bluetooth headset pairing issue (HOCO ES32 PLUS)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1924623 Title: Bluetooth headset pairing issue (HOCO ES32 PLUS) Status in bluez package in Ubuntu: Confirmed Bug description: I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is visible and in pairable mode, but after running: bluetoothctl [bluetooth]# show Controller 04:33:C2:AA:17:60 (public) Name: mykyt Alias: mykyt Class: 0x001c010c Powered: yes Discoverable: yes DiscoverableTimeout: 0x Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: yes Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded i get: Failed to pair: org.bluez.Error.AuthenticationTimeout or Failed to pair: org.bluez.Error.AuthenticationCanceled or Failed to pair: org.bluez.Error.Failed I tried every single solution i was able to find for similar problems, including changing controller mode to bredr, reinstalling pulseaudio, unblocking rfkill, checking if my device is in pairable mode, using blueman and so on. The fact is, bluetooth is working on my laptop (I can connect to my phone and my other bluetooth headset MEIZU EP51) and also my headset HOCO ES32 PLUS is working and is able to connect to my phone and my other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04. I really hope you can help me. Please tell me if you need more information and I will provide it. Thank you! -- lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy bluez bluez: Installed: 5.53-0ubuntu3 Candidate: 5.53-0ubuntu3 Version table: *** 5.53-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status -- Expected behavior: After turning on bluetooth and clicking on device name in settings -> bluetooth device is connecting and pairing successfully. Current behavior: Pairing fails. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 00:28:19 2021 InstallationDate: Installed on 2020-08-27 (231 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Swift SF314-57G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.14 dmi.modalias:
[Kernel-packages] [Bug 1988408] Re: bluetooth gaming controller
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988408 Title: bluetooth gaming controller Status in bluez package in Ubuntu: Confirmed Bug description: On 2 different ubuntu machines (laptop and desktop, with same ubuntu version and bluez) I can pair my generic BT game controller without any issues except for the fact that I can't send or receive any input. This controller with the same bluetooth dongle connects perfectly on windows 10 and 11 (had to dual boot to test it). The laptop itself, via dongle or via integrated BT receiver, can also connect perfectly and use it for steam on windows. There's something wrong going on with Bluez stack. Tried to use jstest-gtk and install xbox-drv to no avail. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 10:41:31 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2015 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.asset.tag: BC5FF494092A dmi.board.name: 960GM-VGS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd07/23/2015:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:A2:8B ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1035 acl:0 sco:0 events:60 errors:0 TX bytes:3694 acl:0 sco:0 commands:60 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Status: New => Triaged ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Focal: New Status in systemd source package in Focal: Triaged Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008466] Re: Will not wake up from suspend.
I have the same problem on HP EliteBook 845 G8 Notebook PC with AMD Ryzen 5 5600U with Radeon Graphics. Updated to 5.19.0-32 yesterday, since than the notebook won't wake up after opening the lid. Rebooted back to 5.15.0-58 and suspend/wake works again. Looked in the kern.log at the time of failed wake up, found this: Feb 24 19:32:58 petr-baloun kernel: [ 7152.582928] hid-generic 0003:0557:2213.0016: input,hidraw4: USB HID v1.10 Mouse [ATEN HDMI KVM V1.3.122] on usb-:04:00.4-1.1.1/input3 Feb 24 19:33:01 petr-baloun kernel: [ 7155.579659] wlp1s0: authenticate with 24:4b:fe:dd:07:24 Feb 24 19:33:02 petr-baloun kernel: [ 7155.909843] wlp1s0: send auth to 24:4b:fe:dd:07:24 (try 1/3) Feb 24 19:33:02 petr-baloun kernel: [ 7155.913157] wlp1s0: authenticated Feb 24 19:33:02 petr-baloun kernel: [ 7155.913465] wlp1s0: associate with 24:4b:fe:dd:07:24 (try 1/3) Feb 24 19:33:02 petr-baloun kernel: [ 7155.925750] wlp1s0: RX AssocResp from 24:4b:fe:dd:07:24 (capab=0x511 status=0 aid=1) Feb 24 19:33:02 petr-baloun kernel: [ 7155.926138] wlp1s0: associated Feb 24 19:33:02 petr-baloun kernel: [ 7155.981580] wlp1s0: Limiting TX power to 24 (27 - 3) dBm as advertised by 24:4b:fe:dd:07:24 Feb 24 19:33:02 petr-baloun kernel: [ 7156.029735] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Feb 24 19:33:37 petr-baloun kernel: [ 7191.177127] usb 5-1: USB disconnect, device number 2 Feb 24 19:33:37 petr-baloun kernel: [ 7191.177139] usb 5-1.1: USB disconnect, device number 25 Feb 24 19:33:37 petr-baloun kernel: [ 7191.177143] usb 5-1.1.1: USB disconnect, device number 26 Feb 24 19:33:37 petr-baloun kernel: [ 7191.212560] usb 6-1: USB disconnect, device number 2 Feb 24 19:33:37 petr-baloun kernel: [ 7191.212564] usb 6-1.3: USB disconnect, device number 3 Feb 24 19:33:38 petr-baloun kernel: [ 7191.661026] usb 5-1.2: USB disconnect, device number 4 Feb 24 19:33:38 petr-baloun kernel: [ 7191.661036] usb 5-1.2.1: USB disconnect, device number 6 Feb 24 19:33:38 petr-baloun kernel: [ 7191.661236] usb 5-1.2.2: USB disconnect, device number 7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.751023] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.753511] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.756051] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.771093] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.786661] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.787752] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.791048] wlp1s0: deauthenticating from 24:4b:fe:dd:07:24 by local choice (Reason: 3=DEAUTH_LEAVING) Feb 24 19:33:51 petr-baloun kernel: [ 7204.791276] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.792339] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.882041] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:51 petr-baloun kernel: [ 7204.962575] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Feb 24 19:33:52 petr-baloun kernel: [ 7205.951472] PM: suspend entry (s2idle) Feb 24 19:36:56 petr-baloun kernel: [0.00] Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17) Feb 24 19:36:56 petr-baloun kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Feb 24 19:36:56 petr-baloun kernel: [0.00] KERNEL supported cpus: Feb 24 19:36:56 petr-baloun kernel: [0.00] Intel GenuineIntel Feb 24 19:36:56 petr-baloun kernel: [0.00] AMD AuthenticAMD Feb 24 19:36:56 petr-baloun kernel: [0.00] Hygon HygonGenuine Feb 24 19:36:56 petr-baloun kernel: [0.00] Centaur CentaurHauls Feb 24 19:36:56 petr-baloun kernel: [0.00] zhaoxin Shanghai Feb 24 19:36:56 petr-baloun kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Feb 24 19:36:56 petr-baloun kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Feb 24 19:36:56 petr-baloun kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Feb 24 19:36:56 petr-baloun kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User
[Kernel-packages] [Bug 2008519] 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 2008519 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/2008519 Title: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] Ubuntu uses powersave governor as the default.While the powersave governor has much lower power, the performance is lower than +25% for several workloads compared to performance governor. Report is published: www.Phoronix.com showing difference of 37% The goal here is to keep mean performance delta of powersave governor from performance governor around 10% to 12% by running wide variety of server workloads. For some bursty workload, this delta can be still large, as ramp up of frequency will still lag with powersave governor irrespective of EPP setting. The performance governor always requests maximum frequency. Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for powersave governor is around 12%. But the EPP 0x20 has 18% lower average power. Also experiments are done by raising intel_pstate sysfs min_perf_pct as high as 50%. This didn't bring in any additional improvements compared to just changing EPP. Target Kernel: 6.3 Target Release: 22.04 (5.15 kernel) [HW/SW Information] Sapphire Rapids [Business Justification] Performance Improvements Upstream: Merged 6.3 Commit ID: To be added To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008519] [NEW] cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids
Public bug reported: [Feature Description] Ubuntu uses powersave governor as the default.While the powersave governor has much lower power, the performance is lower than +25% for several workloads compared to performance governor. Report is published: www.Phoronix.com showing difference of 37% The goal here is to keep mean performance delta of powersave governor from performance governor around 10% to 12% by running wide variety of server workloads. For some bursty workload, this delta can be still large, as ramp up of frequency will still lag with powersave governor irrespective of EPP setting. The performance governor always requests maximum frequency. Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for powersave governor is around 12%. But the EPP 0x20 has 18% lower average power. Also experiments are done by raising intel_pstate sysfs min_perf_pct as high as 50%. This didn't bring in any additional improvements compared to just changing EPP. Target Kernel: 6.3 Target Release: 22.04 (5.15 kernel) [HW/SW Information] Sapphire Rapids [Business Justification] Performance Improvements Upstream: Merged 6.3 Commit ID: To be added ** Affects: intel Importance: Critical Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: egs intel-kernel-22.04 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008519 Title: cpufreq: intel_pstate: Update Balance performance EPP for Sapphire Rapids Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] Ubuntu uses powersave governor as the default.While the powersave governor has much lower power, the performance is lower than +25% for several workloads compared to performance governor. Report is published: www.Phoronix.com showing difference of 37% The goal here is to keep mean performance delta of powersave governor from performance governor around 10% to 12% by running wide variety of server workloads. For some bursty workload, this delta can be still large, as ramp up of frequency will still lag with powersave governor irrespective of EPP setting. The performance governor always requests maximum frequency. Based on experiments, EPP of 0x00, 0x10, 0x20, the performance delta for powersave governor is around 12%. But the EPP 0x20 has 18% lower average power. Also experiments are done by raising intel_pstate sysfs min_perf_pct as high as 50%. This didn't bring in any additional improvements compared to just changing EPP. Target Kernel: 6.3 Target Release: 22.04 (5.15 kernel) [HW/SW Information] Sapphire Rapids [Business Justification] Performance Improvements Upstream: Merged 6.3 Commit ID: To be added To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2008519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144
It appears the last time this worked was around linux 5.4.0-122-generic, e.g. this test run: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/armhf/s/systemd/20220907_155827_ae562@/log.gz. Then we start seeing it around 5.4.0.128.129, e.g. this test run: https://autopkgtest.ubuntu.com/results/autopkgtest- focal/focal/armhf/s/systemd/20220922_145908_d6960@/log.gz. In other words, it started failing with newer kernels but no changes to systemd. I'm not sure this is having any real impact in the wild, but I don't want actual armhf regressions to be lost due to this (britney does not consider armhf failures a regression currently). I think we should just ignore this failed service on armhf only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991285 Title: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144 Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-128.144 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don, The kernel team tried applying these pulls today and the test builds broke, this is the comment from the update on the mailing list: Those will be dropped again because they break the build: https://kernel.ubuntu.com/~kernel-ppa/test- build/jammy/linux/LP%231998643-- bf73a7aff8a9516a913af89dc7a3bba77c2de62d/amd64/log ** Changed in: linux (Ubuntu Jammy) Status: In Progress => 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-cvm/5.4.0-1104.110+cvm1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-cvm (5.4.0-1104.110+cvm1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-cvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-cvm/5.4.0-1104.110+cvm1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-cvm (5.4.0-1104.110+cvm1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-cvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007633] Re: amdgpu fails to init with kernel 5.19.0
I too see the same issue as OP with 5.19.0-32-generic. Running 22.04.2 LTS with Kaveri. Here are some relevant messages: >From syslog: Feb 21 12:00:26 mythtv kernel: [4.725116] [drm] Loading kaveri Microcode ... Feb 21 12:00:26 mythtv kernel: [4.762659] [drm] Found UVD firmware Version: 1.64 Family ID: 9 >From dmesg: [7.619038] [drm] Found UVD firmware Version: 1.64 Family ID: 9 [7.619095] amdgpu: Move buffer fallback to memcpy unavailable [7.619111] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -19 [7.619626] amdgpu :00:01.0: amdgpu: amdgpu_device_ip_init failed [7.619632] amdgpu :00:01.0: amdgpu: Fatal error during GPU init [7.619637] amdgpu :00:01.0: amdgpu: amdgpu: finishing device. It goes on to load a generic display at 640x480 resolution. Reboot hangs and requires a rest. Using Ubuntu 5.15.0-60.66-generic 5.15.78 works successfully with no problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007633 Title: amdgpu fails to init with kernel 5.19.0 Status in linux package in Ubuntu: Confirmed Bug description: I recently installed apt upgrades, and among the upgrades, was the 5.19.0-32-generic kernel. I also still have installed the 5.15.0-58-generic kernel. Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280 GPU fails to init. This results in the computer effectively getting 'hung' part way through the kernel boot as X or Wayland, whatever should start up, doesn't. The kernel keeps running (I can see the hard drive light occasionally flash on my case, and the kernel logs continue after the point of the apparent hang - although kernel messages stop getting output to the console - to see the messages, I have to reboot with 5.15 then use journalctl to review the previous boot messages). It inits fine with the older kernel. Not sure what the root cause of the failure is. Found this in kernel boot logs (via "journalctl -b -1" to get the logs for the previous boot, that failed), which I think is indicative of the problem: Feb 16 21:37:17 jeff-linux kernel: status: Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 Family ID: 13 Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy unavailable Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -19 Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error during GPU init Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: finishing device. Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, address: 0090 -- version signature info (line 2 from kernel boot log): Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17) - root@jeff-linux:/home/jeff# lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 See attached lspci-vnvn.log --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeff 1525 F pulseaudio /dev/snd/controlC0: jeff 1525 F pulseaudio /dev/snd/controlC1: jeff 1525 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-27 (355 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: hci0: Bluetooth
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
Then I did the same on 5.19. There is a huge difference. I am fairly certaan that everything from "zio_execute" to "SHA256Tra..." is time spent in ZFS. To the right right side of `SHA256Tra...` is the compiler, I checked this when looking at it in more detail. The compiler graph is basically the same thing as in the 5.15 flamegraph, just relatively much smaller, because so much CPU is wasted otherwise. To the left the huge red block is kernel overhead as far as I can tell. ** Attachment added: "flamegraph-19.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+attachment/5649867/+files/flamegraph-19.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
I sampled 10s of the build in both kernels with `perf` and run hotspot on it for a flamegraph. ** Attachment added: "Flamegraph of 10s action on 15" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+attachment/5649865/+files/flamegraph-15.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
Test kernel can be found here: https://people.canonical.com/~khfeng/lp2007516/ ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
** Tags added: oem-priority originate-from-2002986 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
So I tried this again with 5.19.0-32 and "amd_pstate=passive". Checked with `dmesg` that it was indeed the right kernel and the right option. But it makes no difference. Still 45s build time on 5.15.0-60 vs 1m on 5.19.0-32. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008503] [NEW] Please apply another batch of Orin platform enablement patches
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2008503 Title: Please apply another batch of Orin platform enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2008503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008434] Re: NBS cleanup required in lunar-proposed
Specifically version 390.157-0ubuntu2 needs to be removed on i386 and armhf -- 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/2008434 Title: NBS cleanup required in lunar-proposed Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2008434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I have the same issue. I use generic bluetooth keyboard, Apple trackpad and bluetooth headphones, 3 devices, I connect all three without problem, only the Apple trackpad problem. But when I activate google meet, the apple trackpad disconnects every 10 seconds or less, I have to disconnect the headphones from the bluetooh. A rather unusual problem. System76 Galago Pro with Pop OS 22.04 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file.
[Kernel-packages] [Bug 1998870] Re: ZFS Pool hangs for more than 120 seconds under high I/O load
Also affects me. Some more information: After it gives that message, the I/O for any ZFS device gets really horrible (NVMe SSDs get a maximum throuput of 10MB/s while normally does 400MB/s) and only solves by restarting. Things I have tried based on what I saw over the internet for the same issue: 1. Removing all swap 2. Reducing / Increasing the ARC RAM (always keeping at least 16GB of RAM free in the OS) 3. Checked smart data for all disks (everything is fine) After rebooting, it _usually_ takes one or two days before the issue happens again. The performance is normal while it doesn't happen. I have several virtual machines that uses both SSD and disk drives. It usually starts running some backup routines from 10 PM to midnight, so it might be high I/O related stuff (although the backups usually only take a few minutes to do). My dmesg is a bit different though, I get this repeated about 4 ou 5 times with 20 minutes interval, and the it usually stops reporting it. [sex fev 24 02:31:53 2023] INFO: task txg_sync:2457 blocked for more than 120 seconds. [sex fev 24 02:31:53 2023] Tainted: P O 5.15.0-46-generic #49-Ubuntu [sex fev 24 02:31:53 2023] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [sex fev 24 02:31:53 2023] task:txg_syncstate:D stack:0 pid: 2457 ppid: 2 flags:0x4000 [sex fev 24 02:31:53 2023] Call Trace: [sex fev 24 02:31:53 2023] [sex fev 24 02:31:53 2023] __schedule+0x23d/0x590 [sex fev 24 02:31:53 2023] schedule+0x4e/0xc0 [sex fev 24 02:31:53 2023] schedule_timeout+0x87/0x140 [sex fev 24 02:31:53 2023] ? zio_issue_async+0x12/0x20 [zfs] [sex fev 24 02:31:53 2023] ? __bpf_trace_tick_stop+0x20/0x20 [sex fev 24 02:31:53 2023] io_schedule_timeout+0x51/0x80 [sex fev 24 02:31:53 2023] __cv_timedwait_common+0x12c/0x170 [spl] [sex fev 24 02:31:53 2023] ? wait_woken+0x70/0x70 [sex fev 24 02:31:53 2023] __cv_timedwait_io+0x19/0x20 [spl] [sex fev 24 02:31:53 2023] zio_wait+0x116/0x220 [zfs] [sex fev 24 02:31:53 2023] dsl_pool_sync+0xb6/0x400 [zfs] [sex fev 24 02:31:53 2023] ? __mod_timer+0x214/0x400 [sex fev 24 02:31:53 2023] spa_sync_iterate_to_convergence+0xe0/0x1f0 [zfs] [sex fev 24 02:31:53 2023] spa_sync+0x2dc/0x5b0 [zfs] [sex fev 24 02:31:53 2023] txg_sync_thread+0x266/0x2f0 [zfs] [sex fev 24 02:31:53 2023] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [sex fev 24 02:31:53 2023] thread_generic_wrapper+0x64/0x80 [spl] [sex fev 24 02:31:53 2023] ? __thread_exit+0x20/0x20 [spl] [sex fev 24 02:31:53 2023] kthread+0x12a/0x150 [sex fev 24 02:31:53 2023] ? set_kthread_struct+0x50/0x50 [sex fev 24 02:31:53 2023] ret_from_fork+0x22/0x30 [sex fev 24 02:31:53 2023] Machine: - Lenovo RD450 - Dual Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz - 192GB RAM DDR4 - 2x 4TB Disks WD RED (ZFS Mirror) - 2x 2TB Crucial NVMe (ZFS Mirror) - 2x 8TB Disks WD RED (ZFS Mirror) - 512GB WD Green SSD (OS Only) - QLCNIC 10Gbps NIC OS: - Distributor ID: Ubuntu - Description: Ubuntu 22.04.1 LTS - Release: 22.04 - Codename: jammy ZFS: zfs-2.1.4-0ubuntu0.1 zfs-kmod-2.1.4-0ubuntu0.1 -- 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/1998870 Title: ZFS Pool hangs for more than 120 seconds under high I/O load Status in zfs-linux package in Ubuntu: Confirmed Bug description: I see the issue happening when: 1.- deleting a FS --> sudo zfs destroy -r data/VMs 2.- then renaming a new FS as the (old) deleted --> sudo zfs rename data/VMsNew data/VMs 3.- removing data in other FS in the same zpool --> rm -rf * data/BackupsNew/* 4.- Also I've seen this messages when running a rsync operation between two FS in the same pool. [Dec 5 13:42] INFO: task txg_sync:5468 blocked for more than 120 seconds. [ +0,16] Tainted: P O 5.15.0-56-generic #62-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,04] task:txg_syncstate:D stack:0 pid: 5468 ppid: 2 flags:0x4000 [ +0,13] Call Trace: [ +0,05] [ +0,07] __schedule+0x24e/0x590 [ +0,16] schedule+0x69/0x110 [ +0,09] schedule_timeout+0x87/0x140 [ +0,11] ? __bpf_trace_tick_stop+0x20/0x20 [ +0,11] io_schedule_timeout+0x51/0x80 [ +0,11] __cv_timedwait_common+0x12c/0x170 [spl] [ +0,31] ? wait_woken+0x70/0x70 [ +0,11] __cv_timedwait_io+0x19/0x20 [spl] [ +0,27] zio_wait+0x116/0x220 [zfs] [ +0,000477] ? spa_sync_aux_dev+0x280/0x280 [zfs] [ +0,000404] spa_sync_frees+0x40/0x90 [zfs] [ +0,000396] spa_sync_iterate_to_convergence+0x10d/0x1f0 [zfs] [ +0,000399] spa_sync+0x2dc/0x5b0 [zfs] [ +0,000393] txg_sync_thread+0x266/0x2f0 [zfs] [ +0,000418] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ +0,000416] thread_generic_wrapper+0x61/0x80 [spl] [
[Kernel-packages] [Bug 1998870] Re: ZFS Pool hangs for more than 120 seconds under high I/O load
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- 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/1998870 Title: ZFS Pool hangs for more than 120 seconds under high I/O load Status in zfs-linux package in Ubuntu: Confirmed Bug description: I see the issue happening when: 1.- deleting a FS --> sudo zfs destroy -r data/VMs 2.- then renaming a new FS as the (old) deleted --> sudo zfs rename data/VMsNew data/VMs 3.- removing data in other FS in the same zpool --> rm -rf * data/BackupsNew/* 4.- Also I've seen this messages when running a rsync operation between two FS in the same pool. [Dec 5 13:42] INFO: task txg_sync:5468 blocked for more than 120 seconds. [ +0,16] Tainted: P O 5.15.0-56-generic #62-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,04] task:txg_syncstate:D stack:0 pid: 5468 ppid: 2 flags:0x4000 [ +0,13] Call Trace: [ +0,05] [ +0,07] __schedule+0x24e/0x590 [ +0,16] schedule+0x69/0x110 [ +0,09] schedule_timeout+0x87/0x140 [ +0,11] ? __bpf_trace_tick_stop+0x20/0x20 [ +0,11] io_schedule_timeout+0x51/0x80 [ +0,11] __cv_timedwait_common+0x12c/0x170 [spl] [ +0,31] ? wait_woken+0x70/0x70 [ +0,11] __cv_timedwait_io+0x19/0x20 [spl] [ +0,27] zio_wait+0x116/0x220 [zfs] [ +0,000477] ? spa_sync_aux_dev+0x280/0x280 [zfs] [ +0,000404] spa_sync_frees+0x40/0x90 [zfs] [ +0,000396] spa_sync_iterate_to_convergence+0x10d/0x1f0 [zfs] [ +0,000399] spa_sync+0x2dc/0x5b0 [zfs] [ +0,000393] txg_sync_thread+0x266/0x2f0 [zfs] [ +0,000418] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [ +0,000416] thread_generic_wrapper+0x61/0x80 [spl] [ +0,35] ? __thread_exit+0x20/0x20 [spl] [ +0,34] kthread+0x127/0x150 [ +0,11] ? set_kthread_struct+0x50/0x50 [ +0,12] ret_from_fork+0x1f/0x30 [ +0,17] [Dec 5 13:44] INFO: task rsync:165214 blocked for more than 120 seconds. [ +0,15] Tainted: P O 5.15.0-56-generic #62-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,04] task:rsync state:D stack:0 pid:165214 ppid: 1 flags:0x0006 [ +0,13] Call Trace: [ +0,04] [ +0,07] __schedule+0x24e/0x590 [ +0,14] ? kmem_cache_free+0x24f/0x290 [ +0,15] schedule+0x69/0x110 [ +0,12] cv_wait_common+0xf8/0x130 [spl] [ +0,29] ? wait_woken+0x70/0x70 [ +0,12] __cv_wait+0x15/0x20 [spl] [ +0,27] dmu_tx_wait+0x8e/0x1e0 [zfs] [ +0,000347] dmu_tx_assign+0x49/0x80 [zfs] [ +0,000322] zfs_write+0x45c/0xdb0 [zfs] [ +0,000465] ? unix_stream_recvmsg+0x8c/0xa0 [ +0,10] ? generic_write_checks+0x65/0xc0 [ +0,11] zpl_iter_write+0xe7/0x130 [zfs] [ +0,000443] new_sync_write+0x111/0x1a0 [ +0,11] vfs_write+0x1d5/0x270 [ +0,08] ksys_write+0x67/0xf0 [ +0,08] __x64_sys_write+0x19/0x20 [ +0,08] do_syscall_64+0x59/0xc0 [ +0,09] ? syscall_exit_to_user_mode+0x27/0x50 [ +0,10] ? __x64_sys_read+0x19/0x20 [ +0,07] ? do_syscall_64+0x69/0xc0 [ +0,07] ? do_syscall_64+0x69/0xc0 [ +0,06] ? do_syscall_64+0x69/0xc0 [ +0,08] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ +0,12] RIP: 0033:0x7f6b39c5fa37 [ +0,08] RSP: 002b:7fff8fe554f8 EFLAGS: 0246 ORIG_RAX: 0001 [ +0,09] RAX: ffda RBX: 7f6b390f2010 RCX: 7f6b39c5fa37 [ +0,06] RDX: 0004 RSI: 7f6b390f2010 RDI: 0001 [ +0,05] RBP: 0001 R08: 7f6b3912a010 R09: 0010 [ +0,05] R10: 000f R11: 0246 R12: 0004 [ +0,05] R13: 8000 R14: 8000 R15: 557bb34da730 [ +0,10] [Dec 6 01:45] INFO: task txg_sync:5468 blocked for more than 120 seconds. [ +0,16] Tainted: P O 5.15.0-56-generic #62-Ubuntu [ +0,06] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,04] task:txg_syncstate:D stack:0 pid: 5468 ppid: 2 flags:0x4000 [ +0,13] Call Trace: [ +0,04] [ +0,07] __schedule+0x24e/0x590 [ +0,16] schedule+0x69/0x110 [ +0,09] schedule_timeout+0x87/0x140 [ +0,11] ? __bpf_trace_tick_stop+0x20/0x20 [ +0,11] io_schedule_timeout+0x51/0x80 [ +0,12] __cv_timedwait_common+0x12c/0x170 [spl] [ +0,30] ? wait_woken+0x70/0x70 [ +0,12] __cv_timedwait_io+0x19/0x20 [spl] [ +0,27] zio_wait+0x116/0x220 [zfs] [ +0,000477] ?
[Kernel-packages] [Bug 1786013] Re: Packaging resync
** Description changed: - Ongoing packing resyncs. + Ongoing packaging resyncs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-xilinx-zynqmp verification-needed-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/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1022.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-focal ** Tags added: kernel-spammed-focal-linux-xilinx-zynqmp verification-needed-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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008050] Re: bmc virtual usb keyboard/mouse can't be detected when resting bmc
Tried to reload hid and xhci_pic and seems no chance too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/2008050 Title: bmc virtual usb keyboard/mouse can't be detected when resting bmc Status in linux-hwe-5.4 package in Ubuntu: New Bug description: In zte server, when reseting bmc or reload virtual keyboard/mouse driver in BMC, the keyboard/mouse on KVM will be hanged, it can resume working after reboot host OS which is Ubuntu 20.04 ga-kernel. This wouldn't happen on CentOS with kernel of 3.10.0-1160.317.x86_64, the keyboard/mouse of KVM keeps working when resting ibm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/2008050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2007038] Re: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04
OK, I tried it. It still fails in the infiniband infrastructure, but in a new way, and from an ib_core function rather than ib_mthca. There were still a couple of shift-out-of-bounds UBSAN warnings, but then an attempt to execute in a non-executable page, as if following a trashed function pointer. If there is other debugging information I should gather, please let me know. The kern.log is attached. On 2/22/23 18:45, Kai-Heng Feng wrote: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/ > > Headers are not needed. > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > ** Attachment added: "tate-6.2.0-kern.log" https://bugs.launchpad.net/bugs/2007038/+attachment/5649830/+files/tate-6.2.0-kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007038 Title: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04 Status in linux package in Ubuntu: Incomplete Bug description: I run some x86_64 machines with Infiniband interfaces (Mellanox MT25204, ib_mthca driver + ib_ipoib for IP-over-IB). This had worked fine for years under Ubuntu 20.04.1 LTS and under RHEL6 before it. But as soon as I updated to 22.04.1 LTS -- with both its default 5.15.0-60-generic kernel and also 6.1.0-1006-oem (the latest packaged one I could find), the IB interface doesn't work. dmesg shows some UBSAN shift-out-of-bounds warnings in mthca modules, e.g. "shift exponent -25557 is negative". That's a bizarre number - maybe a hint of something uninitialized? The crippling symptom shows up within a second after that: a NULL dereference within the ib_mthca driver -- the "BUG: kernel NULL pointer dereference", in mthca_poll_one. The interface never sets its RUNNING flag (as shown by ifconfig). The rest of the system remains usable after the "BUG" message -- the ethernet, disk, etc. drivers and other functions work as expected. Attempting to unload the ib_mthca driver causes a kernel panic. Is there anything I should try? Should I build a kernel from source with debugging? I could try installing the 5.4.0 kernel from 20.04, but would rather use something that will continue to get security patches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 12 14:12 seq crw-rw+ 1 root audio 116, 33 Feb 12 14:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sun Feb 12 14:17:28 2023 InstallationDate: Installed on 2020-11-22 (812 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X7DBR-8 PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=8624cf02-e743-4da6-9209-14ef2c2abd10 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-10 (2 days ago) dmi.bios.date: 12/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: X7DBR-8 dmi.board.vendor: Supermicro dmi.board.version: PCB Version dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/03/2007:svnSupermicro:pnX7DBR-8:pvr0123456789:rvnSupermicro:rnX7DBR-8:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:sku: dmi.product.name: X7DBR-8 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Changed in: lttng-modules (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: Fix Committed Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: Fix Committed Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: Fix Committed Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), \ 782 21:14:39 DEBUG| [stdout] | ^~~ 783 21:14:39 DEBUG| [stdout]
[Kernel-packages] [Bug 2008466] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008466 Title: Will not wake up from suspend. Status in linux package in Ubuntu: Confirmed Bug description: HP laptop Ryzen 7 4700 with Renoir graphics. Close lid which puts system into suspend. After say 20 mins open laptop, keyboard backlight comes on but system does not wake up. Have to force a power off. It works OK after only a few mins in suspend. Sames on mains or battery. Problem does not exist using kernel 5.15.0-60-generic. Problem started on upgrade to 5.19.0-32-generic. Tried switching between X-org and Wayland and disabled TPM in BIOS without any change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 09:32:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:876f] InstallationDate: Installed on 2022-09-12 (164 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ENVY x360 Convertible 15-ee0xxx ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-mono PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2022 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876F dmi.board.vendor: HP dmi.board.version: 13.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 13.47 dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx dmi.product.sku: 9QZ65EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008466] Re: Will not wake up from suspend.
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008466 Title: Will not wake up from suspend. Status in linux package in Ubuntu: Confirmed Bug description: HP laptop Ryzen 7 4700 with Renoir graphics. Close lid which puts system into suspend. After say 20 mins open laptop, keyboard backlight comes on but system does not wake up. Have to force a power off. It works OK after only a few mins in suspend. Sames on mains or battery. Problem does not exist using kernel 5.15.0-60-generic. Problem started on upgrade to 5.19.0-32-generic. Tried switching between X-org and Wayland and disabled TPM in BIOS without any change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 09:32:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:876f] InstallationDate: Installed on 2022-09-12 (164 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ENVY x360 Convertible 15-ee0xxx ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-mono PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2022 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876F dmi.board.vendor: HP dmi.board.version: 13.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 13.47 dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx dmi.product.sku: 9QZ65EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008466] [NEW] Will not wake up from suspend.
You have been subscribed to a public bug: HP laptop Ryzen 7 4700 with Renoir graphics. Close lid which puts system into suspend. After say 20 mins open laptop, keyboard backlight comes on but system does not wake up. Have to force a power off. It works OK after only a few mins in suspend. Sames on mains or battery. Problem does not exist using kernel 5.15.0-60-generic. Problem started on upgrade to 5.19.0-32-generic. Tried switching between X-org and Wayland and disabled TPM in BIOS without any change. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 09:32:13 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:876f] InstallationDate: Installed on 2022-09-12 (164 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ENVY x360 Convertible 15-ee0xxx ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-mono PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2022 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 876F dmi.board.vendor: HP dmi.board.version: 13.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 13.47 dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx dmi.product.sku: 9QZ65EA#ABU dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Will not wake up from suspend. https://bugs.launchpad.net/bugs/2008466 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 2008473] [NEW] b43 wifi connection impossible
Public bug reported: -Nearby wifi networks are visible. -Can connect to unprotected networks. -Can't connect to protected networks. Slow connection process until I receive error message: "No passphrase given" affect: firmware-b43-installer(1:019-7build2) affect OS: Kubuntu 22.04.1 LTS Kubuntu 22.10 Network/sys info: Network mode: WPA2+AES Support: b/g/n Wifi not in greenfield mode. Also tried splitting 2.4Ghz - 5Ghz to different ssid - Fail. Disabled n band - Fail. Secure boot: disabled Motherboard: F2A78M-D3H Bios: F4(latest stable) NIC: Belkin F5D7000-V1000 lspci -vknn 03:06.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Belkin F5D7000 v1000 Wireless G Desktop Card [1799:7000] Flags: bus master, fast devsel, latency 32, IRQ 20 Memory at fe10 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: b43-pci-bridge Kernel modules: ssb iwconfig wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Will also affect: firmware-b43-installer (1:019-8) (debian sid) - Fail firmware-b43-installer (1:019-3) (debian stretch) - Success ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firmware-b43-installer 1:019-7build2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 24 10:35:25 2023 InstallationDate: Installed on 2023-02-18 (6 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: b43-fwcutter UpgradeStatus: Upgraded to kinetic on 2023-02-19 (4 days ago) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/2008473 Title: b43 wifi connection impossible Status in b43-fwcutter package in Ubuntu: New Bug description: -Nearby wifi networks are visible. -Can connect to unprotected networks. -Can't connect to protected networks. Slow connection process until I receive error message: "No passphrase given" affect: firmware-b43-installer(1:019-7build2) affect OS: Kubuntu 22.04.1 LTS Kubuntu 22.10 Network/sys info: Network mode: WPA2+AES Support: b/g/n Wifi not in greenfield mode. Also tried splitting 2.4Ghz - 5Ghz to different ssid - Fail. Disabled n band - Fail. Secure boot: disabled Motherboard: F2A78M-D3H Bios: F4(latest stable) NIC: Belkin F5D7000-V1000 lspci -vknn 03:06.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03) Subsystem: Belkin F5D7000 v1000 Wireless G Desktop Card [1799:7000] Flags: bus master, fast devsel, latency 32, IRQ 20 Memory at fe10 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: b43-pci-bridge Kernel modules: ssb iwconfig wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Will also affect: firmware-b43-installer (1:019-8) (debian sid) - Fail firmware-b43-installer (1:019-3) (debian stretch) - Success ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: firmware-b43-installer 1:019-7build2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 24 10:35:25 2023 InstallationDate: Installed on 2023-02-18 (6 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: b43-fwcutter UpgradeStatus: Upgraded to kinetic on 2023-02-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2008473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986717] Re: [SRU]Update ice driver to support E823 devices
** 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/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera sometimes does not work on Ubuntu 22.04.2
** Summary changed: - Intel MIPI Camera sometimes does not work on Ubuntu 22.04.02 + Intel MIPI Camera sometimes does not work on Ubuntu 22.04.2 ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera sometimes does not work on Ubuntu 22.04.2 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Status in linux source package in Kinetic: New Status in v4l2-relayd source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in v4l2-relayd source package in Lunar: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23) and do `dist-upgrade`. The camera sometimes does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992468] Re: segfault in ld-linux-x86-64.so
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1992468
Title:
segfault in ld-linux-x86-64.so
Status in linux package in Ubuntu:
Invalid
Bug description:
My manually built elf x64 file has started crashing on load, within the last
month or so.
It worked fine on Ubuntu 20.04.x, but fails on 22.04 - same problem on Mint
19.3 and Fedora 36.
dmesg ... gives this:
[ 107.121214] p[4370]: segfault at 0 ip 7f3d725b8350 sp 7ffea111fba0
error 4 in ld-linux-x86-64.so.2[7f3d72598000+2a000]
[ 107.121230] Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01
00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49 f7 da 66 90 <8b> 08 83
f9 07 77 19 85 c9 74 45 83 f9 07 77 40 48 63 0c 8a 48 01
You can download the offending file (a single plain 4MB ELF x64) from
http://phix.x10.mx/p64
It almost certainly contains older/rarer forms of relocations and suchlike,
but
only about ten or so and meant to be as simple as possible.
If I need to change the binary content of that file, I can, but might
need a wee bit of help.
Of course, if/once it gets through ld-linux-x86-64.so and complains
about something else, ignore it, or should you be at all intrigued you
can visit http://phix.x10.mx/download.php to get the full package.
References, just in case you need them, or to ask a wider set than just me
for more details direct:
https://openeuphoria.org/forum/136972.wc?last_id=136973
https://github.com/petelomax/Phix/issues/13
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pete 1096 F pulseaudio
CasperMD5json: {
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-12-08 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
IwConfig:
lono wireless extensions.
enp0s3no wireless extensions.
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic
root=UUID=24d28a06-1b9b-4d48-9055-546f7a0e87a3 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
RelatedPackageVersions:
linux-restricted-modules-5.15.0-56-generic N/A
linux-backports-modules-5.15.0-56-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
RfKill:
Tags: vanessa
Uname: Linux 5.15.0-56-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992468/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
Issues reported by end users: https://askubuntu.com/questions/1455653/horizontal-colored-lines-appearing-on-display-ubuntu-22-04 https://askubuntu.com/questions/1455925/dell-xps-13-plus-9320-horizontal-lines-static-after-installing-latest-release https://askubuntu.com/questions/1456219/problems-after-updates-on-dell-xps-plus-9320 https://www.dell.com/community/Inspiron/Horizontal-lines-appearing-on-my-display-Ubuntu/td-p/8352881 ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera sometimes does not work on Ubuntu 22.04.02
Compare to the normal log, the sensor does not register completed. [Fail] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin intel-ipu6 intel-ipu: FW version: 20220510 intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 mei_vsc spi-INTC1094:00: gpio get resetfw failed mei_vsc: probe of spi-INTC1094:00 failed with error -22 [Success] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin intel-ipu6 intel-ipu: FW version: 20220510 intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a10 3-0036 nlanes is 1 port is 2 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera sometimes does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Status in linux source package in Kinetic: New Status in v4l2-relayd source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in v4l2-relayd source package in Lunar: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23) and do `dist-upgrade`. The camera sometimes does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
Test with warm boot 39 times and checked the log. I can reproduce this issue once. Please see the attached dmesg.txt. ** Description changed: - Install Ubuntu 22.04.02 daily build (2023-02-23), the camera sometimes - does not work with Google Meet and any sort of camera application. + Install Ubuntu 22.04.02 daily build (2023-02-23) and do `dist-upgrade`. + The camera sometimes does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 ** Summary changed: - Intel MIPI Camera does not work on Ubuntu 22.04.02 + Intel MIPI Camera sometimes does not work on Ubuntu 22.04.02 ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+attachment/5649783/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera sometimes does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Status in linux source package in Kinetic: New Status in v4l2-relayd source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in v4l2-relayd source package in Lunar: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23) and do `dist-upgrade`. The camera sometimes does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
** Changed in: linux (Ubuntu Jammy) 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Changed in: linux (Ubuntu Jammy) 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
** Changed in: linux (Ubuntu)
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/2003267
Title:
[EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
release
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Bug description:
== SRU Justification ==
Intel has requested the following patches which enable enable Intel_idle for
eagle stream.
Intel has customers that would like to use the intel_idle driver on latest
SPR (Sapphire Rapids).
These patches have all landed upstream, but are not in Jammy.
These patches will enable customers to use Ubuntu 22.04 on new hardware
from Intel.
== Fixes ==
9edf3c0ffef0 ("intel_idle: add SPR support")
da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")
== Regression Potential ==
Medium. These patches are specific to enable intel_idle support for Sapphire
Rapids. Changes
are specific to Intel and tested by Intel.
== Test Case ==
A test kernel was built with these patches and tested by Intel.
Intel tested on SPR-SP machine and see the correct 190us and 600us residency
for the C6 state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
** Description changed: - Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not - work with Google Meet and any sort of camera application. + Install Ubuntu 22.04.02 daily build (2023-02-23), the camera sometimes + does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Status in linux source package in Kinetic: New Status in v4l2-relayd source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in v4l2-relayd source package in Lunar: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera sometimes does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: v4l2-relayd (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Also affects: v4l2-relayd (Ubuntu Lunar) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Status in linux source package in Kinetic: New Status in v4l2-relayd source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in v4l2-relayd source package in Lunar: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
** Changed in: linux (Ubuntu)
Importance: High => 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/2003267
Title:
[EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
release
Status in intel:
Fix Released
Status in linux package in Ubuntu:
In Progress
Bug description:
== SRU Justification ==
Intel has requested the following patches which enable enable Intel_idle for
eagle stream.
Intel has customers that would like to use the intel_idle driver on latest
SPR (Sapphire Rapids).
These patches have all landed upstream, but are not in Jammy.
These patches will enable customers to use Ubuntu 22.04 on new hardware
from Intel.
== Fixes ==
9edf3c0ffef0 ("intel_idle: add SPR support")
da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")
== Regression Potential ==
Medium. These patches are specific to enable intel_idle support for Sapphire
Rapids. Changes
are specific to Intel and tested by Intel.
== Test Case ==
A test kernel was built with these patches and tested by Intel.
Intel tested on SPR-SP machine and see the correct 190us and 600us residency
for the C6 state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986717] Re: [SRU]Update ice driver to support E823 devices
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986717 Title: [SRU]Update ice driver to support E823 devices Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification: [Impact] Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. [Fix] e36aeec0f4e5 ice: add support for E823 devices 5d9e618cbb54 ice: Add device ids for E822 devices [Testcase] Load ice driver on system with E823 device present and ensure the device is seen by the system [Where problems could occur] The regression risk is low These patches did not cherry pick cleanly I had to make some minor changes. Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992696] Re: Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function
** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1992696 Title: Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Bug description: I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I get no networking from it. I also have a wireless N adapter on usb as well. This was pretty much the same behavior since 20.04. I haven't been able to use this adaptor for wifi for quite a while. I heard that Fedora has no problem with this device. It may be that the order of activation is what needs to be modified. Like activate the bluetooth first, and then make the wifi part active. Thanks for all the great work! Here is the Dmesg I get the following which shows up using dmesg... [ 107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, bcdDevice= 2.10 [ 107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter [ 107.405425] usb 3-3: Manufacturer: Realtek [ 107.405428] usb 3-3: SerialNumber: 123456 [ 107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822 [ 107.410730] Bluetooth: hci0: RTL: rom_version status=0 version=2 [ 107.410740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin [ 107.411027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin [ 107.411173] Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270 [ 108.152731] Bluetooth: hci0: RTL: fw version 0xab6b705c ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-19-generic 5.19.0-19.19 ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uplifting 4065 F wireplumber /dev/snd/seq:uplifting 4058 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 15:00:44 2022 MachineType: Hewlett-Packard HP ProBook 4540s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_uiqi22@/vmlinuz-5.19.0-19-generic root=ZFS=rpool/ROOT/ubuntu_uiqi22 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-19-generic N/A linux-backports-modules-5.19.0-19-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) dmi.bios.date: 05/20/2013 dmi.bios.release: 15.65 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.41 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 88.30 dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:br15.65:efr88.30:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:skuC9K70UT#ABA: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 4540s dmi.product.sku: C9K70UT#ABA dmi.product.version: A1019D1103 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007369] Re: Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux-firmware upgraded to 20220329.git681281e4-0ubuntu3.10
Can this bug be closed then? ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2007369 Title: Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux- firmware upgraded to 20220329.git681281e4-0ubuntu3.10 Status in linux-firmware package in Ubuntu: Incomplete Bug description: Xubuntu 22.04.1 LTS running 5.15.0-60-generic kernel. On last 'dist-upgrade' following packages get upgraded (according to /var/log/apt/history.log): gir1.2-javascriptcoregtk-4.0:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.9, 20220329.git681281e4-0ubuntu3.10), libwebkit2gtk-4.0-37:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1) End-Date: 2023-02-14 00:02:47 One of this was linux-firmware package. I 'lost' my wifi connectivity. dmesg|grep iwlwifi shows: [ 10.678853] iwlwifi :01:00.0: enabling device ( -> 0002) [ 10.691307] iwlwifi :01:00.0: api flags index 2 larger than supported by driver [ 10.691325] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 [ 10.691602] iwlwifi :01:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm [ 10.840186] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [ 11.852608] iwlwifi :01:00.0: SecBoot CPU1 Status: 0x7663, CPU2 Status: 0xb03 [ 11.852635] iwlwifi :01:00.0: UMAC PC: 0x8047f600 [ 11.852656] iwlwifi :01:00.0: LMAC PC: 0x0 [ 11.852659] iwlwifi :01:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 11.852866] iwlwifi :01:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [ 11.852870] iwlwifi :01:00.0: 0x | ADVANCED_SYSASSERT [ 11.852874] iwlwifi :01:00.0: 0x | trm_hw_status0 [ 11.852876] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 11.852878] iwlwifi :01:00.0: 0x | branchlink2 [ 11.852881] iwlwifi :01:00.0: 0x | interruptlink1 [ 11.852883] iwlwifi :01:00.0: 0x | interruptlink2 [ 11.852885] iwlwifi :01:00.0: 0x | data1 [ 11.852887] iwlwifi :01:00.0: 0x | data2 [ 11.852890] iwlwifi :01:00.0: 0x | data3 [ 11.852892] iwlwifi :01:00.0: 0x | beacon time [ 11.852894] iwlwifi :01:00.0: 0x | tsf low [ 11.852896] iwlwifi :01:00.0: 0x | tsf hi [ 11.852898] iwlwifi :01:00.0: 0x | time gp1 [ 11.852901] iwlwifi :01:00.0: 0x | time gp2 [ 11.852903] iwlwifi :01:00.0: 0x | uCode revision type [ 11.852906] iwlwifi :01:00.0: 0x | uCode version major [ 11.852908] iwlwifi :01:00.0: 0x | uCode version minor [ 11.852910] iwlwifi :01:00.0: 0x | hw version [ 11.852913] iwlwifi :01:00.0: 0x | board version [ 11.852915] iwlwifi :01:00.0: 0x | hcmd [ 11.852918] iwlwifi :01:00.0: 0x | isr0 [ 11.852920] iwlwifi :01:00.0: 0x | isr1 [ 11.852922] iwlwifi :01:00.0: 0x | isr2 [ 11.852924] iwlwifi :01:00.0: 0x | isr3 [ 11.852926] iwlwifi :01:00.0: 0x | isr4 [ 11.852928] iwlwifi :01:00.0: 0x | last cmd Id [ 11.852930] iwlwifi :01:00.0: 0x | wait_event [ 11.852933] iwlwifi :01:00.0: 0x | l2p_control [ 11.852935] iwlwifi :01:00.0: 0x | l2p_duration [ 11.852937] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 11.852940] iwlwifi :01:00.0: 0x | l2p_addr_match [ 11.852942] iwlwifi :01:00.0: 0x | lmpm_pmg_sel [ 11.852944] iwlwifi :01:00.0: 0x | timestamp [ 11.852947] iwlwifi :01:00.0: 0x | flow_handler [ 11.852993] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 11.852995] iwlwifi :01:00.0: Transport status: 0x0042, valid: 7 [ 11.852999] iwlwifi :01:00.0: 0x201013F2 | ADVANCED_SYSASSERT [ 11.853001] iwlwifi :01:00.0: 0x | umac branchlink1 [ 11.853004] iwlwifi :01:00.0: 0x8045DFC6 | umac branchlink2 [ 11.853006] iwlwifi :01:00.0: 0x | umac interruptlink1 [ 11.853009] iwlwifi :01:00.0: 0x | umac interruptlink2 [ 11.853011] iwlwifi :01:00.0: 0x000C | umac data1 [ 11.853013] iwlwifi :01:00.0: 0x0004 | umac data2 [ 11.853015] iwlwifi :01:00.0: 0xDEADBEEF | umac data3 [ 11.853018] iwlwifi :01:00.0: 0x0042 | umac major [ 11.853020] iwlwifi :01:00.0:
[Kernel-packages] [Bug 2000786] Re: Source not compile with default gcc-11 - comipe fails on lz4_decompress.c
** Changed in: linux-raspi (Ubuntu) Status: Incomplete => 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/2000786 Title: Source not compile with default gcc-11 - comipe fails on lz4_decompress.c Status in linux-raspi package in Ubuntu: Invalid Bug description: linux-raspi source code which downloaded from repository by '$ sudo apt source linux-image-5.15.0-1021-raspi' with kernel option CONFIG_STRICT_DEVMEM=n not compile by 'sudo make' if gcc = gcc-11 (gcc 11.3.0) which is the default on Debian 22.04 LTS. The make/gcc fail on lz4_decompress.c Details see at: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108232 With gcc-12 the compile go through lz4_decompress.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2000786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006942] Re: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does
Isn't it strange to change behaviour on a Kernel, especially amd_pstate which is not loaded anymore. BUT intel_pstate is still. shouldn't on a patch not to change this? it is really. Bad, how many users will suffer with their laptops, not understanding what is causing their battery drains. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2006942 Title: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: After upgrading to 5.19.0-31 (two of my systems) CPU driver changes to acpi-cpufreq. instead of amd_pstate. This causes cpu to keep higher frequency and increased consumption. ``` root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ls -l total 0 -r--r--r-- 1 root root 4096 Feb 10 13:27 affected_cpus -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_highest_perf -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_lowest_nonlinear_freq -r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_max_freq -r--r--r-- 1 root root 4096 Feb 10 12:54 cpuinfo_max_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_min_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_transition_latency -r--r--r-- 1 root root 4096 Feb 10 13:27 related_cpus -r--r--r-- 1 root root 4096 Feb 10 12:54 scaling_available_governors -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_cur_freq -r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_driver -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_governor -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_max_freq -rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_min_freq -rw-r--r-- 1 root root 4096 Feb 10 13:28 scaling_setspeed root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ``` with newer kernel also policy files for amd_pstate Tried it on 2 Asus PN51-S1 systems with AMD Ryzen 7 5700U I am currently staying at 5.19.0-29 as it is working better. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-31-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-11-18 (85 days ago) InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64 (20221019) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-S1 Package: linux-signed (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/system-root ro ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic uec-images Uname: Linux 5.19.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/10/2022 dmi.bios.release: 1.12 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0112 dmi.board.asset.tag: Default string dmi.board.name: PN51-S1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0112:bd08/10/2022:br1.12:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-S1:pvr0112:rvnASUSTeKCOMPUTERINC.:rnPN51-S1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN51-S1 dmi.product.version: 0112 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to:
