[Kernel-packages] [Bug 1959970] Re: Microphone-mute LED regression with 5.13.0-28 kernel update
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959970 Title: Microphone-mute LED regression with 5.13.0-28 kernel update Status in linux package in Ubuntu: Expired Bug description: The bug 1955691 kernel update introduces undesirable behaviour on the HP Spectre x360 - the mic-mute LED is now lit at system startup, even though the microphone is NOT MUTED. This is undesirable because it is giving the user incorrect information; and also because the LED is a rather attention-grabbing vivid orange, which is distracting to have lit. After logging in to GNOME, opening the Sound settings and toggling the microphone mute state does cause the LED to follow future changes. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maxb 5509 F pulseaudio /dev/snd/pcmC0D0p: maxb 5509 F...m pulseaudio /dev/snd/pcmC0D6c: maxb 5509 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Feb 3 22:24:55 2022 InstallationDate: Installed on 2021-02-03 (364 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Spectre x360 Convertible 14-ea0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=11ab54a5-5193-4f3c-b722-124d50665745 ro i915.enable_dpcd_backlight=1 i8042.nopnp quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-15 (111 days ago) dmi.bios.date: 08/05/2021 dmi.bios.release: 15.23 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.49 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.49 dmi.modalias: dmi:bvnAMI:bvrF.23:bd08/05/2021:br15.23:efr40.49:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.49:cvnHP:ct31:cvrChassisVersion:sku2G2C7EA#ABU: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981723] Re: 5.15.0-33 & 5.15.0-41, sometimes the mouse freezes several times for a few seconds when I open a program with wine, which never happens with 5.13.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981723 Title: 5.15.0-33 & 5.15.0-41, sometimes the mouse freezes several times for a few seconds when I open a program with wine, which never happens with 5.13. Status in linux package in Ubuntu: Expired Bug description: It always happens to me when I open a program like "Mp3 Direct Cut" with wine. (https://mpesch3.de/) EDITION="Xfce" DESCRIPTION="Linux Mint 20.3 Una" System:Kernel: 5.13.0-52-generic x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal Machine: Type: Laptop System: GIGABYTE product: AORUS 7 KB v: N/A serial: Mobo: GIGABYTE model: AORUS 7 KB serial: UEFI: INSYDE v: FB06 date: 08/03/2020 Battery: ID-1: BAT0 charge: 44.8 Wh condition: 47.3/47.2 Wh (100%) model: Notebook BAT status: Unknown CPU: Topology: 6-Core model: Intel Core i7-10750H bits: 64 type: MT MCP arch: N/A L2 cache: 12.0 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 62399 Speed: 800 MHz min/max: 800/5000 MHz Core speeds (MHz): 1: 800 2: 838 3: 859 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 802 Graphics: Device-1: Intel UHD Graphics vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 Device-2: NVIDIA TU106 [GeForce RTX 2060] vendor: CLEVO/KAPOK driver: nvidia v: 515.57 bus ID: 01:00.0 Display: x11 server: X.Org 1.20.13 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa resolution: 1920x1080~144Hz OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 515.57 direct render: Yes Audio: Device-1: Intel Comet Lake PCH cAVS vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: NVIDIA TU106 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 Sound Server: ALSA v: k5.13.0-52-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 5000 bus ID: 0c:00.0 IF: wlp12s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 3000 bus ID: 0d:00.1 IF: enp13s0f1 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 1.12 TiB used: 627.73 GiB (54.7%) ID-1: /dev/nvme0n1 model: SX8200PNP-512GT-S size: 476.94 GiB ID-2: /dev/sda model: Q-720 size: 670.69 GiB Partition: ID-1: / size: 144.03 GiB used: 48.74 GiB (33.8%) fs: ext4 dev: /dev/nvme0n1p4 ID-2: /home size: 192.12 GiB used: 135.07 GiB (70.3%) fs: ext4 dev: /dev/nvme0n1p5 ID-3: swap-1 size: 14.65 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p6 Sensors: System Temperatures: cpu: 62.0 C mobo: N/A gpu: nvidia temp: 59 C Fan Speeds (RPM): cpu: 2171 Info: Processes: 322 Uptime: 17m Memory: 15.33 GiB used: 2.00 GiB (13.1%) Init: systemd runlevel: 5 Compilers: gcc: 9.4.0 clang: 10.0.0-4ubuntu1 Shell: bash v: 5.0.17 inxi: 3.0.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
I may have missed this one... I meant to add it if it's not already picked up in a different commit: ice: Fix not stopping Tx queues for VFs https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/intel/ice?id=b385cca47363316c6d9a74ae9db407bbc281f815 -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989258] Re: multiple kernel oops regarding hung tasks delaying boot
** Also affects: auto-package-testing 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/1989258 Title: multiple kernel oops regarding hung tasks delaying boot Status in Auto Package Testing: New Status in linux package in Ubuntu: Confirmed Bug description: Kinetic amd64 instances in the autopkgtest environment are regularly experiencing a slow boot process due to a hung task timeout which happens multiple times. The oops appears below: Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.485373] INFO: task systemd-udevd:140 blocked for more than 1208 seconds. Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.487120] Not tainted 5.19.0-15-generic #15-Ubuntu Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.490936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.492717] task:systemd-udevd state:D stack:0 pid: 140 ppid: 137 flags:0x4006 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.494612] Call Trace: Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.495202] Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.495727] __schedule+0x23b/0x5c0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.496559] ? sched_clock_cpu+0x12/0xf0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.497482] schedule+0x50/0xc0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.498237] schedule_preempt_disabled+0x15/0x30 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.499306] __mutex_lock.constprop.0+0x4e7/0x760 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.500409] __mutex_lock_slowpath+0x13/0x20 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.501420] mutex_lock+0x36/0x40 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.502211] add_early_randomness+0x1b/0xc0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.503178] hwrng_register+0x13e/0x1c0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.504068] virtrng_scan+0x19/0x30 [virtio_rng] Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.505152] virtio_dev_probe+0x1f9/0x2c0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.506096] really_probe+0x1d1/0x3a0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.506958] __driver_probe_device+0x11b/0x190 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.507993] driver_probe_device+0x24/0xd0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.508955] __driver_attach+0xd8/0x200 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.509859] ? __device_attach_driver+0x120/0x120 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.510952] bus_for_each_dev+0x7c/0xc0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.511846] driver_attach+0x1e/0x30 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.512692] bus_add_driver+0x178/0x220 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.513597] driver_register+0x8f/0xf0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.514474] ? 0xc0282000 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.515257] register_virtio_driver+0x20/0x40 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.516277] virtio_rng_driver_init+0x15/0x1000 [virtio_rng] Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.517602] do_one_initcall+0x4a/0x210 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.518498] ? kmem_cache_alloc_trace+0x181/0x300 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.519587] ? do_init_module+0x27/0x200 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.520516] do_init_module+0x50/0x200 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.521403] load_module+0xb60/0xcb0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.522243] __do_sys_finit_module+0xbd/0x130 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.523255] ? __do_sys_finit_module+0xbd/0x130 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.524312] __x64_sys_finit_module+0x18/0x20 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.525343] do_syscall_64+0x5b/0x80 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.526183] ? syscall_exit_to_user_mode+0x26/0x50 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.527287] ? __x64_sys_mmap+0x33/0x50 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.528180] ? do_syscall_64+0x67/0x80 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.529064] ? exit_to_user_mode_prepare+0x30/0xa0 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.530182] ? syscall_exit_to_user_mode+0x26/0x50 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.531289] ? __x64_sys_newfstatat+0x1c/0x30 Sep 9 22:31:32 bdmurray-test-systemd kernel: [ 1330.532310] ? do_syscall_64+0x67/0x80 Sep 9 22:31:32
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Thanks for trying to solve this. After removing the module the device directory looks like this. $ ls -a /sys/devices/pci:00/INT33C3:00/i2c-0/i2c-CPLM3218:00 total 0 drwxr-xr-x 3 root root0 Sep 13 2022 . drwxr-xr-x 6 root root0 Sep 13 2022 .. lrwxrwxrwx 1 root root0 Sep 13 00:01 firmware_node -> ../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/CPLM3218:00 -r--r--r-- 1 root root 4096 Sep 12 23:57 modalias -r--r--r-- 1 root root 4096 Sep 12 23:57 name drwxr-xr-x 2 root root0 Sep 12 23:59 power lrwxrwxrwx 1 root root0 Sep 13 2022 subsystem -> ../../../../../bus/i2c -rw-r--r-- 1 root root 4096 Sep 13 2022 uevent It is missing the iio:device0 directory and I cannot read light levels. the files above report the following $ cat name CPLM3218:00 $ cat modalias acpi:CPLM3218:CPLM3218: $ cat uevent MODALIAS=acpi:CPLM3218:CPLM3218: If I run modprobe I see no output. The /sys/devices directory above is unchanged, so still no iio:device so I cannot read light levels. The machine can recover from suspend. If I remove the module again, then load with "-v" I get some output $ sudo modprobe -v cm32181 insmod /lib/modules/5.15.0-48-generic/kernel/drivers/iio/industrialio.ko insmod /lib/modules/5.15.0-48-generic/kernel/drivers/iio/light/cm32181.ko And in my journalctl I see the following error 16 when loading the module. Sep 13 00:04:52 nmurphy-laptop sudo[5338]: nmurphy : TTY=pts/1 ; PWD=/home/nmurphy/computer_issues ; USER=root ; COMMAND=/usr/sbin/modprobe -r cm32181 Sep 13 00:04:52 nmurphy-laptop sudo[5338]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Sep 13 00:04:52 nmurphy-laptop sudo[5338]: pam_unix(sudo:session): session closed for user root Sep 13 00:04:55 nmurphy-laptop sudo[5346]: nmurphy : TTY=pts/1 ; PWD=/home/nmurphy/computer_issues ; USER=root ; COMMAND=/usr/sbin/modprobe -v cm32181 Sep 13 00:04:55 nmurphy-laptop sudo[5346]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Sep 13 00:04:55 nmurphy-laptop sudo[5346]: pam_unix(sudo:session): session closed for user root Sep 13 00:04:55 nmurphy-laptop kernel: i2c i2c-0: Failed to register i2c client dummy at 0x48 (-16) Sep 13 00:04:55 nmurphy-laptop kernel: cm32181: probe of i2c-CPLM3218:00 failed with error -16 -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
I was unable to locate the patch from comment #5 in linux-next or linus's tree as of yet. This patch may require a separate PR. -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
The following patches are already applied to the jammy master-next kernel (Ubuntu-5.15.0-48.54-2-gd250073d5172) 5951a2b9812d v5.16-rc6 iavf: Fix VLAN feature flags after VFR e6ba5273d4ed v5.16-rc6 ice: Fix race conditions between virtchnl handling and VF ndo ops b385cca47363 v5.16-rc6 ice: Fix not stopping Tx queues for VFs 1a8c7778bcde v5.16-rc6 ice: Fix VF true promiscuous mode I was able to apply (0299faeaf8eb v5.16-rc6 ice: Remove toggling of antispoof for VF trusted promiscuous model) after applying the following patch: 29e71f41e7d2f7069c12c686ca4d222e8be2a2ee ice: Remove boolean vlan_promisc flag from function Are the three patches in the description still necessary? -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989374] [NEW] Bionic update: upstream stable patchset 2022-09-12
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-09-12 Ported from the following upstream stable releases: v4.14.285, v4.19.249 from git://git.kernel.org/ UBUNTU: [Config] dkms-versions -- force wireguard-dkms update Revert "random: Make getrandom() ready earlier" 9p: missing chunk of "fs/9p: Don't update file type when updating file attributes" crypto: chacha20 - Fix keystream alignment for chacha20_block() random: always fill buffer in get_random_bytes_wait random: optimize add_interrupt_randomness drivers/char/random.c: remove unused dont_count_entropy random: Fix whitespace pre random-bytes work random: Return nbytes filled from hw RNG UBUNTU: [Config] updateconfigs for RANDOM_TRUST_CPU, RANDOM_TRUST_BOOTLOADER random: add a config option to trust the CPU's hwrng random: remove preempt disabled region random: Make crng state queryable random: make CPU trust a boot parameter drivers/char/random.c: constify poolinfo_table drivers/char/random.c: remove unused stuct poolinfo::poolbits drivers/char/random.c: make primary_crng static random: only read from /dev/random after its pool has received 128 bits random: move rand_initialize() earlier random: document get_random_int() family latent_entropy: avoid build error when plugin cflags are not set random: fix soft lockup when trying to read from an uninitialized blocking pool random: Support freezable kthreads in add_hwgenerator_randomness() fdt: add support for rng-seed random: Use wait_event_freezable() in add_hwgenerator_randomness() char/random: Add a newline at the end of the file Revert "hwrng: core - Freeze khwrng thread during suspend" crypto: Deduplicate le32_to_cpu_array() and cpu_to_le32_array() crypto: blake2s - generic C library implementation and selftest lib/crypto: blake2s: move hmac construction into wireguard lib/crypto: sha1: re-roll loops to reduce code size random: Don't wake crng_init_wait when crng_init == 1 random: Add a urandom_read_nowait() for random APIs that don't warn random: add GRND_INSECURE to return best-effort non-cryptographic bytes random: ignore GRND_RANDOM in getentropy(2) random: make /dev/random be almost like /dev/urandom random: fix crash on multiple early calls to add_bootloader_randomness() random: remove the blocking pool random: delete code to pull data into pools random: remove kernel.random.read_wakeup_threshold random: remove unnecessary unlikely() random: convert to ENTROPY_BITS for better code readability random: Add and use pr_fmt() random: fix typo in add_timer_randomness() random: remove some dead code of poolinfo random: split primary/secondary crng init paths random: avoid warnings for !CONFIG_NUMA builds x86: Remove arch_has_random, arch_has_random_seed powerpc: Remove arch_has_random, arch_has_random_seed s390: Remove arch_has_random, arch_has_random_seed linux/random.h: Remove arch_has_random, arch_has_random_seed linux/random.h: Use false with bool linux/random.h: Mark CONFIG_ARCH_RANDOM functions __must_check powerpc: Use bool in archrandom.h random: add arch_get_random_*long_early() random: avoid arch_get_random_seed_long() when collecting IRQ randomness random: remove dead code left over from blocking pool MAINTAINERS: co-maintain random.c crypto: blake2s - include instead of crypto: blake2s - adjust include guard naming random: document add_hwgenerator_randomness() with other input functions random: remove unused irq_flags argument from add_interrupt_randomness() random: use BLAKE2s instead of SHA1 in extraction random: do not sign extend bytes for rotation when mixing random: do not re-init if crng_reseed completes before primary init random: mix bootloader randomness into pool random: harmonize "crng init done" messages random: use IS_ENABLED(CONFIG_NUMA) instead of ifdefs random: initialize ChaCha20 constants with correct endianness random: early initialization of ChaCha constants random: avoid superfluous call to RDRAND in CRNG extraction random: don't reset crng_init_cnt on urandom_read() random: fix typo in comments random: cleanup poolinfo abstraction crypto: chacha20 - Fix chacha20_block() keystream alignment (again) random: cleanup integer types random: remove incomplete last_data logic random: remove unused extract_entropy() reserved argument random: rather than entropy_store abstraction, use global random: remove unused OUTPUT_POOL constants random: de-duplicate INPUT_POOL constants random: prepend remaining pool constants with POOL_ random: cleanup fractional entropy shift constants
[Kernel-packages] [Bug 1956101] Re: BUG: kernel NULL pointer dereference, address: 00000000000006c8
Oops I did it again... Hi folks, after moving my zpool to another hardware because of a broken system I got almost the same error with jammy. So it might not be fixed and I still have a problem. [ 48.494682] ZFS: Loaded module v2.1.2-1ubuntu3, ZFS pool version 5000, ZFS filesystem version 5 Begin: Importing ZFS root pool 'rpool_unencrypted' ... [ 51.538634] BUG: kernel NULL pointer dereference, address: 06c8 [ 51.545731] #PF: supervisor write access in kernel mode [ 51.551043] #PF: error_code(0x0002) - not-present page [ 51.556313] PGD 0 P4D 0 [ 51.558952] Oops: 0002 [#1] SMP PTI [ 51.562543] CPU: 4 PID: 665 Comm: zpool Tainted: P O 5.15.0-39-generic #42-Ubuntu [ 51.571448] Hardware name: Oracle Corporation SUN FIRE X4170 M3 /MOTHER BOARD ASSEMBL , BIOS 17160400 05/06/2020 [ 51.582183] RIP: 0010:mutex_lock+0x1e/0x40 [ 51.586384] Code: c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc e8 2d ed ff ff 31 c0 65 48 8b 14 25 c0 fb 01 00 49 0f b1 14 24 75 06 4c 8b 65 f8 c9 c3 4c 89 e7 e8 ac ff ff ff [ 51.605298] RSP: 0018:b0128eb03b40 EFLAGS: 00010246 [ 51.610628] RAX: RBX: 9c23604ac000 RCX: [ 51.617868] RDX: 9c2361613180 RSI: RDI: 06c8 [ 51.625106] RBP: b0128eb03b48 R08: 9c2347e5cda0 R09: 9c2347e5cda0 [ 51.632358] R10: 0001 R11: R12: 06c8 [ 51.639594] R13: R14: 06c8 R15: 06e8 [ 51.646831] FS: 7ff929d1e7c0() GS:9c3a5fb0() knlGS: [ 51.655035] CS: 0010 DS: ES: CR0: 80050033 [ 51.660878] CR2: 06c8 CR3: 000123c1e006 CR4: 000606e0 [ 51.669603] Call Trace: [ 51.672157] [ 51.674377] rrw_enter_read_impl+0x29/0x110 [zfs] [ 51.679459] rrw_enter_read+0x13/0x20 [zfs] [ 51.683981] rrw_enter+0x1d/0x20 [zfs] [ 51.688070] dsl_pool_config_enter+0x1d/0x20 [zfs] [ 51.693186] spa_prop_get+0x98/0x3c0 [zfs] [ 51.697624] ? spl_kmem_free_impl+0x25/0x30 [spl] [ 51.702441] ? kfree+0x216/0x250 [ 51.705782] ? __cond_resched+0x1a/0x50 [ 51.709727] ? avl_destroy_nodes+0x9e/0xf0 [zavl] [ 51.714522] ? __cond_resched+0x1a/0x50 [ 51.718445] ? do_raw_spin_unlock+0x9/0x10 [zfs] [ 51.723407] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 51.728307] ? spa_deactivate+0x22b/0x320 [zfs] [ 51.733181] ? do_raw_spin_unlock+0x9/0x10 [zfs] [ 51.738138] ? __raw_spin_unlock+0x9/0x10 [zfs] [ 51.743009] ? spa_name_compare+0xe/0x30 [zfs] [ 51.747801] ? avl_find+0x6b/0xd0 [zavl] [ 51.751814] zfs_ioc_pool_get_props+0x79/0x140 [zfs] [ 51.757145] zfsdev_ioctl_common+0x682/0x740 [zfs] [ 51.762312] ? __check_object_size.part.0+0x4a/0x150 [ 51.767389] ? _copy_from_user+0x2e/0x60 [ 51.771427] zfsdev_ioctl+0x57/0xe0 [zfs] [ 51.775802] __x64_sys_ioctl+0x91/0xc0 [ 51.779668] do_syscall_64+0x5c/0xc0 [ 51.783358] ? do_user_addr_fault+0x1e3/0x670 [ 51.787831] ? syscall_exit_to_user_mode+0x27/0x50 [ 51.792729] ? exit_to_user_mode_prepare+0x37/0xb0 [ 51.797635] ? irqentry_exit_to_user_mode+0x9/0x20 [ 51.802524] ? irqentry_exit+0x19/0x30 [ 51.806377] ? exc_page_fault+0x89/0x160 [ 51.810406] ? asm_exc_page_fault+0x8/0x30 [ 51.814610] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 51.819760] RIP: 0033:0x7ff92a473aff [ 51.823461] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 51.842366] RSP: 002b:7fff0a797390 EFLAGS: 0246 ORIG_RAX: 0010 [ 51.850070] RAX: ffda RBX: 5560b332ecb0 RCX: 7ff92a473aff [ 51.857302] RDX: 7fff0a7973f0 RSI: 5a27 RDI: 0003 [ 51.864547] RBP: 7fff0a79a9d0 R08: R09: 5560b3346e70 [ 51.871783] R10: 5560b3377000 R11: 0246 R12: 7fff0a7973f0 [ 51.879019] R13: 5560b3327320 R14: R15: 5560b332ecb0 [ 51.886259] [ 51.888535] Modules linked in: zfs(PO) zunicode(PO) zzstd(O) zlua(O) zcommon(PO) znvpair(PO) zavl(PO) icp(PO) spl(O) hid_generic cdc_ether usbhid usbnet mii hid i2c_algo_bit drm_vram_helper drm_ttm_helper uas ttm drm_kms_helper syscopyarea usb_storage sysfillrect qla2xxx sysimgblt nvme_fc fb_sys_fops ixgbe nvme_fabrics cec xfrm_algo nvme_core rc_core i2c_i801 ahci dca crc32_pclmul drm libahci i2c_smbus lpc_ich megaraid_sas scsi_transport_fc mdio [ 51.928267] CR2: 06c8 [ 51.931728] ---[ end trace ec5e771ef5c762aa ]--- [ 52.061046] RIP: 0010:mutex_lock+0x1e/0x40 [ 52.065232] Code: c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 49 89 fc e8 2d ed ff ff 31 c0 65 48 8b 14 25 c0 fb 01 00 49 0f b1 14 24 75 06 4c 8b 65 f8 c9 c3 4c 89 e7 e8 ac ff ff ff [ 52.084144] RSP:
[Kernel-packages] [Bug 1980473] Re: [Intel AX1650i] I can't activate my bluetooth anyway, the button to activate it isn't working
September 12th, same thing again. Unfortunately, this time the workaround mentioned above doesn't seem to work. So, for the time being, I'm out of proper Bluetooth sound. Last time, while issuing these commands something would pop up in between. (I don't remember what.) Today nothing in between. dmesg looks slightly different, too: 30398.432011] usb 1-7: new full-speed USB device number 15 using xhci_hcd [30398.581847] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2a, bcdDevice= 0.01 [30398.581853] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [30398.599309] Bluetooth: hci0: read Intel version: 370810011003110e00 [30398.599405] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq [30398.862420] Bluetooth: hci0: unexpected event for opcode 0xfc2f [30398.879516] Bluetooth: hci0: Intel firmware patch completed and activated [30416.968439] usbcore: deregistering interface driver btusb [30430.397152] usbcore: registered new interface driver btusb [30430.412277] Bluetooth: hci0: read Intel version: 370810011003110e32 [30430.412279] Bluetooth: hci0: Intel device is already patched. patch num: 32 Any help appreciated at bringing it back ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1980473 Title: [Intel AX1650i] I can't activate my bluetooth anyway, the button to activate it isn't working Status in bluez-firmware package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: When I enter in settings -> Bluetooth -> button to activate it, it doesn't work, it's locked ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 1 10:31:29 2022 InstallationDate: Installed on 2021-03-09 (479 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: bnep bluetooth MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash pci=nommconf pcie_aspm=off vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 070YWV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn070YWV:rvrA00:cvnDellInc.:ct10:cvr:sku096D: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez-firmware/+bug/1980473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
Hi Michael, Provided test kernel does not have BSG code. BSG enabled management application does not work with this driver. Could you please re-check and if possible share the driver source code ? Thanks, Sumit -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
additional patch to pick up that is supposed to help address the issue with MTUs ice: Fix interface being down after reset with link-down-on-close flag on https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/drivers/net/ethernet/intel?h=dev-queue=a2aa0cec547579cc137970c772ea82cbf5ee2608 So lets see if we can pull this in too, either with these patches or in a separate PR -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989340] 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 1989340 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/1989340 Title: installation crashes on a brand new VM on a brand new server Status in linux package in Ubuntu: Incomplete Bug description: Installation of Ubuntu 22.04 crashed on a VMware VM. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.17 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 14:24:17 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989340] Re: installation crashes on a brand new VM on a brand new server
Things start to go wrong with: Sep 12 12:19:03 ubuntu kernel: [ 1061.268314] sd 2:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s Sep 12 12:19:03 ubuntu kernel: [ 1061.268349] sd 2:0:0:0: [sdb] tag#0 Sense Key : Not Ready [current] Sep 12 12:19:03 ubuntu kernel: [ 1061.268361] sd 2:0:0:0: [sdb] tag#0 ASC=0x4 <>ASCQ=0xff Sep 12 12:19:03 ubuntu kernel: [ 1061.268370] sd 2:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 01 dc d9 b0 00 00 70 00 Sep 12 12:19:03 ubuntu kernel: [ 1061.268376] blk_update_request: I/O error, dev sdb, sector 31250864 op 0x1:(WRITE) flags 0x400 phys_seg 14 prio class 0 So it crashed because the disk was no longer available to the kernel. Since this is a VM, we should expect this was not caused by a hardware failure. Were changes being made to the VMWare configuration at the time? Is this crash reproducible for you? ** Package changed: ubiquity (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/1989340 Title: installation crashes on a brand new VM on a brand new server Status in linux package in Ubuntu: New Bug description: Installation of Ubuntu 22.04 crashed on a VMware VM. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.17 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 14:24:17 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Changed in: ubuntu-z-systems
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
== SRU Justification ==
Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is
offline") there was a timing window during recovery, that qeth_query_card_info
could be sent to the card, even before it was ready for it, leading to a
failing cardrecovery. There is evidence that this window was hit, as not
all callers of get_link_ksettings() check for netif_device_present.
This patch (Mainline commit 7a07a29e4f67) fixes the regression caused
by commit e6e771b3d897.
Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.
This patch is being requested in Jammy 5.15 and Kinetic 5.19.
== Fix ==
7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")
== Regression Potential ==
Low. This patch has been accepted in upstream stable and is limited to
the s390/qeth card.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989340] [NEW] installation crashes on a brand new VM on a brand new server
You have been subscribed to a public bug: Installation of Ubuntu 22.04 crashed on a VMware VM. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.17 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 14:24:17 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.17 ubuntu -- installation crashes on a brand new VM on a brand new server https://bugs.launchpad.net/bugs/1989340 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 1983489] Re: Enable headset mic on Asus X515
Victor, I've only had this laptop for a week or so but I didn't have any issues with it. Nonetheless, if you want to expand on this or talk about anything else regarding Ubuntu on this laptop feel free to contact me. -- 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/1983489 Title: Enable headset mic on Asus X515 Status in linux package in Ubuntu: Confirmed Bug description: The Asus X515 has a combo 3.5mm jack that accepts both a headphone output and microphone input. When I connect a headset on the jack, Ubuntu asks me if it is a headphone or a microphone (check screenshot: https://imgur.com/a/Nt9KeZ6), but it doesn't give an option that the device is in fact, both. The driver seems to be ALC897. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Wed Aug 3 16:32:47 2022 InstallationDate: Installed on 2022-07-04 (30 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 322e:2103 Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 003: ID 13d3:3557 IMC Networks Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515EA_F515EA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-43-generic root=UUID=0f623f90-25fc-4887-bdf5-bd0876d7a50e ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X515EA.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X515EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515EA.309:bd05/16/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515EA_F515EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUSLaptop dmi.product.name: VivoBook_ASUSLaptop X515EA_F515EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
SRU request submitted to UKT mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-September/133102.html
** Description changed:
+ == SRU Justification ==
+ Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is
offline") there was a timing window during recovery, that qeth_query_card_info
could be sent to the card, even before it was ready for it, leading to a
failing cardrecovery. There is evidence that this window was hit, as not
all callers of get_link_ksettings() check for netif_device_present.
+
+ This patch fixes the regression caused by commit e6e771b3d897.
+
+ Commit 7a07a29e4f67 is in mainline as of v6.0-rc1.
+
+ This patch is being requested in Jammy 5.15 and Kinetic 5.19. The
+
+
+ == Fix ==
+ 7a07a29e4f67 ("s390/qeth: cache link_info for ethtool")
+
+ == Regression Potential ==
+ Low. This patch has been accepted in upstream stable and is limited to
+ the s390/qeth card.
+
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug
reporter.
+ The bug reporter states the test kernel resolved the bug.
+
+
+
+
+
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
- kernel: qeth 0.0.0365: The qeth device driver failed to
- recover an error on the device
+ kernel: qeth 0.0.0365: The qeth device driver failed to
+ recover an error on the device
Problem: Since commit e6e771b3d897
- ("s390/qeth: detach netdevice while card is offline")
-there was a timing window during recovery, that
-qeth_query_card_info could be sent to the card, even before it
-was ready for it, leading to a failing card recovery. There is
-evidence that this window was hit, as not all callers of
-get_link_ksettings() check for netif_device_present.
- Solution: Use cached values in qeth_get_link_ksettings(), instead of
-calling qeth_query_card_info() and falling back to default
-values in case it fails. Link info is already updated when the
-card goes online, e.g. after STARTLAN (physical link up). Set
-the link info to default values, when the card goes offline or
-at STOPLAN (physical link down). A follow-on patch will improve
-values reported for link down.
-Fixes: e6e771b3d897
-("s390/qeth: detach netdevice while card is offline")
+ ("s390/qeth: detach netdevice while card is offline")
+ there was a timing window during recovery, that
+ qeth_query_card_info could be sent to the card, even before it
+ was ready for it, leading to a failing card recovery. There is
+ evidence that this window was hit, as not all callers of
+ get_link_ksettings() check for netif_device_present.
+ Solution: Use cached values in qeth_get_link_ksettings(), instead of
+ calling qeth_query_card_info() and falling back to default
+ values in case it fails. Link info is already updated when the
+ card goes online, e.g. after STARTLAN (physical link up). Set
+ the link info to default values, when the card goes offline or
+ at STOPLAN (physical link down). A follow-on patch will improve
+ values reported for link down.
+ Fixes: e6e771b3d897
+ ("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
-times in parallel and using iperf to get load on the interface.
+
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
Update from upstream: Please check out the other patches below that were sent together with the one patch I listed in my previous reply. Cherry-picking patches can be challenging with ice driver from later kernels as new features and bug fixes are sent continuously in each kernel and the dependency can be tricky. 5951a2b9812dv5.16-rc6 iavf: Fix VLAN feature flags after VFR e6ba5273d4edv5.16-rc6 ice: Fix race conditions between virtchnl handling and VF ndo ops b385cca47363v5.16-rc6 ice: Fix not stopping Tx queues for VFs 0299faeaf8ebv5.16-rc6 ice: Remove toggling of antispoof for VF trusted promiscuous mode 1a8c7778bcdev5.16-rc6 ice: Fix VF true promiscuous mode Regarding the issue of changing MTU, it is a known one in ice driver and the team is actively working on a fix. I will share once it is ready to be sent Linux upstream. Another note, for E810 NICs, please recommend customers to update the NVM image on the NIC to the latest one if possible. Here is the latest one: https://www.intel.com/content/www/us/en/download/19626/non-volatile-memory-nvm-update-utility-for-intel-ethernet-network-adapters-e810-series-linux.html -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989253] Re: Lenovo Thinkpad T14 G3 HDMI not working
Tested with 6.0.0 drm-tip kernel as well and still reproducible, filed https://gitlab.freedesktop.org/drm/intel/-/issues/6793 upstream. ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6793 https://gitlab.freedesktop.org/drm/intel/-/issues/6793 -- 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/1989253 Title: Lenovo Thinkpad T14 G3 HDMI not working Status in linux package in Ubuntu: Confirmed Bug description: On 22.10 with 5.19.0-15-generic on a ThinkPad T14 gen3 (intel-based), the HDMI port is not working, screen is not detected (both in xorg and wayland). Also tested with older 5.15.0-27-generic kernel, same result. I see the following traceback in dmesg: [3.510605] [ cut here ] [3.510615] i915 :00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref) [3.510663] WARNING: CPU: 8 PID: 263 at drivers/gpu/drm/i915/display/intel_pps.c:593 intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511147] Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel fb_sys_fops intel_lpss_pci i2c_hid_acpi aesni_intel nvme spi_intel_pci intel_lpss xhci_pci i2c_hid i2c_i801 drm crypto_simd psmouse e1000e thunderbolt nvme_core spi_intel i2c_smbus idma64 xhci_pci_renesas wmi hid cryptd video pinctrl_tigerlake [3.511228] CPU: 8 PID: 263 Comm: systemd-udevd Not tainted 5.19.0-15-generic #15-Ubuntu [3.511237] Hardware name: LENOVO 21AHCTO1WW/21AHCTO1WW, BIOS N3MET06W (1.03 ) 07/11/2022 [3.511241] RIP: 0010:intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511636] Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 43 8e 7e de 48 c7 c1 70 1a 97 c0 4c 89 f2 48 c7 c7 26 3a 94 c0 48 89 c6 e8 44 0e c8 de <0f> 0b e9 27 fe ff ff e8 5e 63 d3 de 66 66 2e 0f 1f 84 00 00 00 00 [3.511642] RSP: 0018:b6b6c0d3b380 EFLAGS: 00010282 [3.511649] RAX: RBX: 8a5f9d464170 RCX: a097b148 [3.511654] RDX: RSI: 0003 RDI: 0001 [3.511657] RBP: b6b6c0d3b3d8 R08: R09: a0fb5642 [3.511661] R10: R11: 03d7 R12: 8a5fa2788000 [3.511666] R13: R14: 8a5f82740a20 R15: 8a5fa27887e0 [3.511670] FS: 7ff53569d8c0() GS:8a6aaf60() knlGS: [3.511676] CS: 0010 DS: ES: CR0: 80050033 [3.511680] CR2: 55ae059d3140 CR3: 00011d7a2006 CR4: 00770ee0 [3.511686] PKRU: 5554 [3.511689] Call Trace: [3.511693] [3.511700] ? intel_display_power_get+0x56/0x70 [i915] [3.512087] intel_dp_aux_xfer+0x12c/0x860 [i915] [3.512427] ? raw_spin_rq_unlock+0x10/0x40 [3.512440] intel_dp_aux_transfer+0x1d0/0x2f0 [i915] [3.512757] drm_dp_dpcd_access+0xad/0x130 [drm_display_helper] [3.512791] drm_dp_dpcd_write+0xb2/0x100 [drm_display_helper] [3.512825] intel_dp_sink_set_decompression_state+0x86/0xd0 [i915] [3.513107] intel_disable_ddi+0x10b/0x1b0 [i915] [3.513391] intel_encoders_disable+0x9b/0xc0 [i915] [3.513699] hsw_crtc_disable+0x61/0x80 [i915] [3.513964] intel_old_crtc_state_disables+0x3d/0xb0 [i915] [3.514212] intel_commit_modeset_disables+0x2ab/0x330 [i915] [3.514465] ? modeset_get_crtc_power_domains+0x69/0xc0 [i915] [3.514707] intel_atomic_commit_tail+0x197/0xbb0 [i915] [3.514937] intel_atomic_commit+0x3b1/0x400 [i915] [3.515155] drm_atomic_commit+0x94/0xd0 [drm] [3.515231] ? drm_plane_create_color_properties.cold+0x45/0x45 [drm] [3.515320] intel_initial_commit+0x183/0x210 [i915] [3.515544] intel_modeset_init+0x22/0x80 [i915] [3.515765] i915_driver_probe+0x1ec/0x480 [i915] [3.515963] ? drm_privacy_screen_get+0x164/0x190 [drm] [3.516038] ? acpi_dev_found+0x64/0x70 [3.516046] i915_pci_probe+0x56/0x140 [i915] [3.516245] local_pci_probe+0x44/0x80 [3.516251] pci_call_probe+0x55/0x180 [3.516255] pci_device_probe+0x84/0x110 [3.516260] really_probe+0x1ce/0x3a0 [3.516267] __driver_probe_device+0x11b/0x190 [3.516272] driver_probe_device+0x24/0xd0 [3.516278] __driver_attach+0xd8/0x200 [3.516283] ? __device_attach_driver+0x120/0x120 [3.516289] bus_for_each_dev+0x79/0xc0 [3.516294] driver_attach+0x1e/0x30 [3.516299] bus_add_driver+0x178/0x220 [3.516304] driver_register+0x8f/0xf0 [3.516309] __pci_register_driver+0x62/0x70 [3.516313] i915_pci_register_driver+0x23/0x30 [i915] [3.516506] i915_init+0x3b/0xee [i915] [3.516706] ? 0xc0a2f000 [3.516710] do_one_initcall+0x47/0x210 [
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989253] Re: Lenovo Thinkpad T14 G3 HDMI not working
the upstream forum discussion would suggest this is a bug in the bios and a fix is coming at some point -- 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/1989253 Title: Lenovo Thinkpad T14 G3 HDMI not working Status in linux package in Ubuntu: Confirmed Bug description: On 22.10 with 5.19.0-15-generic on a ThinkPad T14 gen3 (intel-based), the HDMI port is not working, screen is not detected (both in xorg and wayland). Also tested with older 5.15.0-27-generic kernel, same result. I see the following traceback in dmesg: [3.510605] [ cut here ] [3.510615] i915 :00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref) [3.510663] WARNING: CPU: 8 PID: 263 at drivers/gpu/drm/i915/display/intel_pps.c:593 intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511147] Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel fb_sys_fops intel_lpss_pci i2c_hid_acpi aesni_intel nvme spi_intel_pci intel_lpss xhci_pci i2c_hid i2c_i801 drm crypto_simd psmouse e1000e thunderbolt nvme_core spi_intel i2c_smbus idma64 xhci_pci_renesas wmi hid cryptd video pinctrl_tigerlake [3.511228] CPU: 8 PID: 263 Comm: systemd-udevd Not tainted 5.19.0-15-generic #15-Ubuntu [3.511237] Hardware name: LENOVO 21AHCTO1WW/21AHCTO1WW, BIOS N3MET06W (1.03 ) 07/11/2022 [3.511241] RIP: 0010:intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511636] Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 43 8e 7e de 48 c7 c1 70 1a 97 c0 4c 89 f2 48 c7 c7 26 3a 94 c0 48 89 c6 e8 44 0e c8 de <0f> 0b e9 27 fe ff ff e8 5e 63 d3 de 66 66 2e 0f 1f 84 00 00 00 00 [3.511642] RSP: 0018:b6b6c0d3b380 EFLAGS: 00010282 [3.511649] RAX: RBX: 8a5f9d464170 RCX: a097b148 [3.511654] RDX: RSI: 0003 RDI: 0001 [3.511657] RBP: b6b6c0d3b3d8 R08: R09: a0fb5642 [3.511661] R10: R11: 03d7 R12: 8a5fa2788000 [3.511666] R13: R14: 8a5f82740a20 R15: 8a5fa27887e0 [3.511670] FS: 7ff53569d8c0() GS:8a6aaf60() knlGS: [3.511676] CS: 0010 DS: ES: CR0: 80050033 [3.511680] CR2: 55ae059d3140 CR3: 00011d7a2006 CR4: 00770ee0 [3.511686] PKRU: 5554 [3.511689] Call Trace: [3.511693] [3.511700] ? intel_display_power_get+0x56/0x70 [i915] [3.512087] intel_dp_aux_xfer+0x12c/0x860 [i915] [3.512427] ? raw_spin_rq_unlock+0x10/0x40 [3.512440] intel_dp_aux_transfer+0x1d0/0x2f0 [i915] [3.512757] drm_dp_dpcd_access+0xad/0x130 [drm_display_helper] [3.512791] drm_dp_dpcd_write+0xb2/0x100 [drm_display_helper] [3.512825] intel_dp_sink_set_decompression_state+0x86/0xd0 [i915] [3.513107] intel_disable_ddi+0x10b/0x1b0 [i915] [3.513391] intel_encoders_disable+0x9b/0xc0 [i915] [3.513699] hsw_crtc_disable+0x61/0x80 [i915] [3.513964] intel_old_crtc_state_disables+0x3d/0xb0 [i915] [3.514212] intel_commit_modeset_disables+0x2ab/0x330 [i915] [3.514465] ? modeset_get_crtc_power_domains+0x69/0xc0 [i915] [3.514707] intel_atomic_commit_tail+0x197/0xbb0 [i915] [3.514937] intel_atomic_commit+0x3b1/0x400 [i915] [3.515155] drm_atomic_commit+0x94/0xd0 [drm] [3.515231] ? drm_plane_create_color_properties.cold+0x45/0x45 [drm] [3.515320] intel_initial_commit+0x183/0x210 [i915] [3.515544] intel_modeset_init+0x22/0x80 [i915] [3.515765] i915_driver_probe+0x1ec/0x480 [i915] [3.515963] ? drm_privacy_screen_get+0x164/0x190 [drm] [3.516038] ? acpi_dev_found+0x64/0x70 [3.516046] i915_pci_probe+0x56/0x140 [i915] [3.516245] local_pci_probe+0x44/0x80 [3.516251] pci_call_probe+0x55/0x180 [3.516255] pci_device_probe+0x84/0x110 [3.516260] really_probe+0x1ce/0x3a0 [3.516267] __driver_probe_device+0x11b/0x190 [3.516272] driver_probe_device+0x24/0xd0 [3.516278] __driver_attach+0xd8/0x200 [3.516283] ? __device_attach_driver+0x120/0x120 [3.516289] bus_for_each_dev+0x79/0xc0 [3.516294] driver_attach+0x1e/0x30 [3.516299] bus_add_driver+0x178/0x220 [3.516304] driver_register+0x8f/0xf0 [3.516309] __pci_register_driver+0x62/0x70 [3.516313] i915_pci_register_driver+0x23/0x30 [i915] [3.516506] i915_init+0x3b/0xee [i915] [3.516706] ? 0xc0a2f000 [3.516710] do_one_initcall+0x47/0x210 [3.516716] ? kmem_cache_alloc_trace+0x181/0x300 [3.516721] ? do_init_module+0x27/0x200 [3.516726] do_init_module+0x50/0x200 [3.516729]
[Kernel-packages] [Bug 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: 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/1980861 Title: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU Status in Snappy: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: The snapd/desktop/advocacy team are investigating the startup performance of running snaps. While doing this and comparing various distros (fedora, opensuse, ubuntu) on Igors reference hardware we noticed that fedora is substantially faster at starting snaps. After some research it turns out that they use the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use CONFIG_SQUASHFS_DECOMP_SINGLE. I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that the first run firefox startup went from 15s to 6s (!) on Igors reference hardware. Given the dramatic performance improvements we would like to get this option switched. However we need to be careful and double check that the results from https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just mounting a snap would use up 131Mb or memory(!). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1980861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989334] 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 1989334 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/1989334 Title: remove circular dep between linux-image and modules Status in linux package in Ubuntu: Incomplete Bug description: remove circular dep between linux-image and modules Currently we have circular dependencies between linux-image and linux- modules/linux-modules-extra packages. This is redundant, and harmful when additional types of linux-images are provided (i.e. kernel.efi). Break the circular dependency by only keeping linux-image -> linux- modules dep, remove linux-modules -> linux-image dep, remove linux- modules-extra -> linux-image dep, add linux-modules-extra -> linux- modules dep. this is now applied in kinetic:linux, next need to apply to this to derivative kernels, and then we can roll it out to jammy too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989334] [NEW] remove circular dep between linux-image and modules
Public bug reported: remove circular dep between linux-image and modules Currently we have circular dependencies between linux-image and linux- modules/linux-modules-extra packages. This is redundant, and harmful when additional types of linux-images are provided (i.e. kernel.efi). Break the circular dependency by only keeping linux-image -> linux- modules dep, remove linux-modules -> linux-image dep, remove linux- modules-extra -> linux-image dep, add linux-modules-extra -> linux- modules dep. this is now applied in kinetic:linux, next need to apply to this to derivative kernels, and then we can roll it out to jammy too. ** 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/1989334 Title: remove circular dep between linux-image and modules Status in linux package in Ubuntu: New Bug description: remove circular dep between linux-image and modules Currently we have circular dependencies between linux-image and linux- modules/linux-modules-extra packages. This is redundant, and harmful when additional types of linux-images are provided (i.e. kernel.efi). Break the circular dependency by only keeping linux-image -> linux- modules dep, remove linux-modules -> linux-image dep, remove linux- modules-extra -> linux-image dep, add linux-modules-extra -> linux- modules dep. this is now applied in kinetic:linux, next need to apply to this to derivative kernels, and then we can roll it out to jammy too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983489] Re: Enable headset mic on Asus X515
Sorry for the offtopic, but Emiliano (emilianorios1), did you experienced any issues with the sleep/suspend function of your laptop with Ubuntu 22.04? I'm getting some and I think I should open a bug for it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983489 Title: Enable headset mic on Asus X515 Status in linux package in Ubuntu: Confirmed Bug description: The Asus X515 has a combo 3.5mm jack that accepts both a headphone output and microphone input. When I connect a headset on the jack, Ubuntu asks me if it is a headphone or a microphone (check screenshot: https://imgur.com/a/Nt9KeZ6), but it doesn't give an option that the device is in fact, both. The driver seems to be ALC897. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Wed Aug 3 16:32:47 2022 InstallationDate: Installed on 2022-07-04 (30 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 322e:2103 Sonix Technology Co., Ltd. USB2.0 HD UVC WebCam Bus 001 Device 003: ID 13d3:3557 IMC Networks Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515EA_F515EA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-43-generic root=UUID=0f623f90-25fc-4887-bdf5-bd0876d7a50e ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X515EA.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X515EA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515EA.309:bd05/16/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515EA_F515EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUSLaptop dmi.product.name: VivoBook_ASUSLaptop X515EA_F515EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989298] Re: amdgpu nullptr and video freeze
** Description changed: # The majority of kernel bug are hardware specific so be sure to note what hardware/device is being used. - AMD RX 460 2GB - Dual but different ASUS monitors - Android ADB, but it always worked alone and was idle for 1 hour prior to the problem # Document any known steps to reproduce the bug. - Cold boot no hibernate - ADB stuff 2 hours before + - Mesa is 22.1.7~kisak1~j - google-chrome-stable started with '/usr/bin/env LANGUAGE=ja_JP:ja LANG=ja_JP.UTF-8 /usr/bin/google-chrome-stable --enable-features=WebUIDarkMode,VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder --force-dark-mode %U' - - Watching a twitch.tv stream at source (1080p) resolution (VDAVideoDecoder/vaapi) maximized on left DVI monitor + - Watching a twitch.tv stream at 3x speed at source (1080p) resolution (VDAVideoDecoder/vaapi) maximized on left DVI monitor - Konsole with `sensors` on right HDMI monitor - Locked screen for 5+ minutes with stream on - Unlocked screen then tried to play/pause stream a few times. The sound changed started/stopped but there were no video changes but the mouse moved - I tried to focus the Konsole window but its decorations didn't change color - CTRL-ALT-F1 didn't respond until after a few seconds - The TTY was a blank terminal with a solid non-blinking cursor - I SSHed in and ran `dmesg` without problem - I might have been able to reboot with SSH, but I held down the power button instead # Also note whether the bug exists in previous kernel versions of Ubuntu or if it's a regression from previous kernel versions. - I did not experience runtime amdgpu problems in any Linux 5.x versions - Suspend/resume to mem/disk has always failed 80% of the time, and even on Windows 10 - RAM used to be buggy a few years ago but I replaced one ram stick # Finally, it's critical to also make sure to test the latest development Ubuntu kernel version as well as the latest upstream mainline kernel. This bug appears probabilistic and I don't know how to test it even on the current kernel version ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: home 1230 F pulseaudio - /dev/snd/controlC1: home 1230 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: home 1230 F pulseaudio + /dev/snd/controlC1: home 1230 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 11 19:58:18 2022 HibernationDevice: RESUME=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 RelatedPackageVersions: - linux-restricted-modules-5.15.0-47-generic N/A - linux-backports-modules-5.15.0-47-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.4 + linux-restricted-modules-5.15.0-47-generic N/A + linux-backports-modules-5.15.0-47-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-04 (130 days ago) dmi.bios.date: 05/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30BF_M32BF_A_F_K31BF_6 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd05/19/2017:br4.6:svnASUSTeKCOMPUTERINC.:pnK30BF_M32BF_A_F_K31BF_6:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30BF_M32BF_A_F_K31BF_6:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: Desktop dmi.product.name: K30BF_M32BF_A_F_K31BF_6 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1989298 Title: amdgpu nullptr and video freeze Status in linux package in Ubuntu: Confirmed Bug description: # The majority of kernel bug are hardware specific so be sure to note what hardware/device is being used. - AMD RX 460 2GB - Dual but different ASUS monitors - Android ADB, but it always worked alone and was idle for 1 hour prior to the problem #
[Kernel-packages] [Bug 1981699] Re: ubuntu_ltp.mm:thp02 times out on with 5.15 kernels on arm64 64k pages
** Changed in: ubuntu-kernel-tests Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981699 Title: ubuntu_ltp.mm:thp02 times out on with 5.15 kernels on arm64 64k pages Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Bug description: The thp02 testcase from ubuntu_ltp.mm running on 5.15 kernels times out on some arm64 systems with 64k pages flavours. INFO: Test start time: Wed Jul 13 17:55:36 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 205749 -n 205749 -f /tmp/ltp-gbCWODkS0Q/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1524: TINFO: Timeout per run is 0h 00m 30s thp02.c:68: TINFO: mremap (0xfffe6000-0xfffedfff) to (0xfffdc000-0xfffe3fff) thp02.c:68: TINFO: mremap (0xfffe6000-0xfffedfff) to (0xfffdc001-0xfffe4000) thp02.c:68: TINFO: mremap (0xfffe6001-0xfffee000) to (0xfffdc000-0xfffe3fff) Test timeouted, sending SIGKILL! tst_test.c:1569: TINFO: Killed the leftover descendant processes tst_test.c:1575: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1577: TBROK: Test killed! (timeout?) For now found with the following combinations: - jammy/linux generic-64k on starmie-kernel - focal/linux-lowlatency-hwe-5.15 lowlatency-64k on starmie-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1981699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality
@vanvugt Thank you very much for opening this bug and everyone else for the quick fix! -- 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/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: Triaged Bug description: Sony WH-1000XM4 missing the A2DP profile and defaults to low quality https://github.com/bluez/bluez/issues/313 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981699] Re: ubuntu_ltp.mm:thp02 times out on with 5.15 kernels on arm64 64k pages
This issue can be found on J-nvidia-64k 5.15.0-1006.6 with node starmie- kernel as well. ** Tags added: 5.15 arm64 jammy nvidia sru-20220829 ubuntu-ltp -- 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/1981699 Title: ubuntu_ltp.mm:thp02 times out on with 5.15 kernels on arm64 64k pages Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Bug description: The thp02 testcase from ubuntu_ltp.mm running on 5.15 kernels times out on some arm64 systems with 64k pages flavours. INFO: Test start time: Wed Jul 13 17:55:36 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 205749 -n 205749 -f /tmp/ltp-gbCWODkS0Q/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1524: TINFO: Timeout per run is 0h 00m 30s thp02.c:68: TINFO: mremap (0xfffe6000-0xfffedfff) to (0xfffdc000-0xfffe3fff) thp02.c:68: TINFO: mremap (0xfffe6000-0xfffedfff) to (0xfffdc001-0xfffe4000) thp02.c:68: TINFO: mremap (0xfffe6001-0xfffee000) to (0xfffdc000-0xfffe3fff) Test timeouted, sending SIGKILL! tst_test.c:1569: TINFO: Killed the leftover descendant processes tst_test.c:1575: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1577: TBROK: Test killed! (timeout?) For now found with the following combinations: - jammy/linux generic-64k on starmie-kernel - focal/linux-lowlatency-hwe-5.15 lowlatency-64k on starmie-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1981699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** Changed in: mutter Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in Mutter: New Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983291] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1983291 Title: Update firmware for DCN316/GFX1037 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Jammy already has firmware for upcoming product with GFX1037 and DCN316. However this firmware has some stability problems under stress and it should be updated to latest on linux-firmware.git to support systems that will take this firmware. [Fix] Upgrade following binaries: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122 [Test] Verify suspend/resume works. Verify that accelerated graphics works. Verify video playback works. [Where problems could occur] Firmware is only loaded to product with GFX1037/DCN316 This isn't yet on the market and regressions are not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983291] Re: Update firmware for DCN316/GFX1037
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.5 --- linux-firmware (20220329.git681281e4-0ubuntu3.5) jammy; urgency=medium * REQUEST add meson vdec firmware to arm64 linux-firmware package (LP: #1986743) - [Packaging] Include meson/vdec firmware * Update firmware for DCN316/GFX1037 (LP: #1983291) - amdgpu: update gc_10_3_7_rlc firmware - amdgpu: update psp_13_0_8 firmware - amdgpu: update dcn_3_1_6_dmcub firmware - amdgpu: update DMCUB firmware for DCN 3.1.6 * Linux Firmware drops AMD RX6650 XT Performance (LP: #1984004) - amdgpu: update dimgrey cavefish firmware for 22.10 - amdgpu: update dimgrey cavefish to release 22.20 -- Juerg Haefliger Wed, 31 Aug 2022 13:11:53 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1983291 Title: Update firmware for DCN316/GFX1037 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Jammy already has firmware for upcoming product with GFX1037 and DCN316. However this firmware has some stability problems under stress and it should be updated to latest on linux-firmware.git to support systems that will take this firmware. [Fix] Upgrade following binaries: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122 [Test] Verify suspend/resume works. Verify that accelerated graphics works. Verify video playback works. [Where problems could occur] Firmware is only loaded to product with GFX1037/DCN316 This isn't yet on the market and regressions are not possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984004] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all [Fix] Update amdgpu/dimgrey_cavefish_* firmware files to latest versions from kernel.org. [Test Case] See original description. [Where Problems Could Occur] Isolated to AMD GPUs that use dimgrey_cavefish firmware blobs. [Original Description] Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.5 --- linux-firmware (20220329.git681281e4-0ubuntu3.5) jammy; urgency=medium * REQUEST add meson vdec firmware to arm64 linux-firmware package (LP: #1986743) - [Packaging] Include meson/vdec firmware * Update firmware for DCN316/GFX1037 (LP: #1983291) - amdgpu: update gc_10_3_7_rlc firmware - amdgpu: update psp_13_0_8 firmware - amdgpu: update dcn_3_1_6_dmcub firmware - amdgpu: update DMCUB firmware for DCN 3.1.6 * Linux Firmware drops AMD RX6650 XT Performance (LP: #1984004) - amdgpu: update dimgrey cavefish firmware for 22.10 - amdgpu: update dimgrey cavefish to release 22.20 -- Juerg Haefliger Wed, 31 Aug 2022 13:11:53 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all [Fix] Update amdgpu/dimgrey_cavefish_* firmware files to latest versions from kernel.org. [Test Case] See original description. [Where Problems Could Occur] Isolated to AMD GPUs that use dimgrey_cavefish firmware blobs. [Original Description] Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1986743] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986743] Re: REQUEST add meson vdec firmware to arm64 linux-firmware package
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.5 --- linux-firmware (20220329.git681281e4-0ubuntu3.5) jammy; urgency=medium * REQUEST add meson vdec firmware to arm64 linux-firmware package (LP: #1986743) - [Packaging] Include meson/vdec firmware * Update firmware for DCN316/GFX1037 (LP: #1983291) - amdgpu: update gc_10_3_7_rlc firmware - amdgpu: update psp_13_0_8 firmware - amdgpu: update dcn_3_1_6_dmcub firmware - amdgpu: update DMCUB firmware for DCN 3.1.6 * Linux Firmware drops AMD RX6650 XT Performance (LP: #1984004) - amdgpu: update dimgrey cavefish firmware for 22.10 - amdgpu: update dimgrey cavefish to release 22.20 -- Juerg Haefliger Wed, 31 Aug 2022 13:11:53 +0200 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs [Test case] Load meson-vdec driver on HW that supports it and watch firmware load failure. [Fix] Include firmware blobs. [Where Problems Could Occur] This only affects very specific HW. And the blobs have shipped in older series but were dropped incorrectly in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989169] Re: No video output if displayport monitor off on boot
I've tested Ubuntu 20.04 and 22.04, they do not exhibit this issue. Kubuntu 20.04 still has this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989169 Title: No video output if displayport monitor off on boot Status in linux package in Ubuntu: Confirmed Bug description: Hi, on Kubuntu 22.04 Desktop (Minimal Install), I'm getting an issue where, if the monitor is turned off during boot, when the monitor is turned on later, no video signal will be found. Steps to reproduce: - Fresh install Kubuntu 22.04, minimal install, autologin. Install all updates as of 9/9/2022. - PCs we have tried: Dell Optiplex 7060, Lenovo ThinkCentre M73 - Monitor is connected via displayport. - Verify Kubuntu has installed correctly and everything is working. Shut down. - Turn off monitor via its power button. - Turn on PC. Wait for Kubuntu to boot. - Turn on Monitor. It shows "No Signal" and goes back to sleep. Expected behaviour: It displays the desktop as normal. - Pressing Ctrl+Alt+F2 will wake the monitor with the command prompt. Pressing Ctrl+Alt+F1 to switch to desktop will put the monitor back to sleep again with No Signal. - Connecting to the PC via a remote desktop software will only show a black screen instead of the desktop. GUI Applications autostarted via startup script will still be displayed, though. - I haven't found any way to get the desktop to display, except for restarting the PC with the monitor turned on. I have a specific use case where sometimes the monitor is off when a PC is booted, and it needs to function correctly when the monitor turns on later. Hopefully this is reproduceable on your end, and a solution or workaround can be found. Happy to supply any further information if needed. Thanks. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: build 825 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-12 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Dell MS116 Optical Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 003: ID 0461:4e04 Primax Electronics, Ltd Lenovo Keyboard KB1021 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=0fbbc1d9-9bfc-4328-b54c-ce0726462130 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0NC2VH dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0NC2VH:rvrA01:cvnDellInc.:ct3:cvr:sku085A: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7060 dmi.product.sku: 085A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989253] Re: Lenovo Thinkpad T14 G3 HDMI not working
FWIW I get the same error with the 5.19.0-16 package from -proposed -- 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/1989253 Title: Lenovo Thinkpad T14 G3 HDMI not working Status in linux package in Ubuntu: Confirmed Bug description: On 22.10 with 5.19.0-15-generic on a ThinkPad T14 gen3 (intel-based), the HDMI port is not working, screen is not detected (both in xorg and wayland). Also tested with older 5.15.0-27-generic kernel, same result. I see the following traceback in dmesg: [3.510605] [ cut here ] [3.510615] i915 :00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref) [3.510663] WARNING: CPU: 8 PID: 263 at drivers/gpu/drm/i915/display/intel_pps.c:593 intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511147] Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel fb_sys_fops intel_lpss_pci i2c_hid_acpi aesni_intel nvme spi_intel_pci intel_lpss xhci_pci i2c_hid i2c_i801 drm crypto_simd psmouse e1000e thunderbolt nvme_core spi_intel i2c_smbus idma64 xhci_pci_renesas wmi hid cryptd video pinctrl_tigerlake [3.511228] CPU: 8 PID: 263 Comm: systemd-udevd Not tainted 5.19.0-15-generic #15-Ubuntu [3.511237] Hardware name: LENOVO 21AHCTO1WW/21AHCTO1WW, BIOS N3MET06W (1.03 ) 07/11/2022 [3.511241] RIP: 0010:intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511636] Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 43 8e 7e de 48 c7 c1 70 1a 97 c0 4c 89 f2 48 c7 c7 26 3a 94 c0 48 89 c6 e8 44 0e c8 de <0f> 0b e9 27 fe ff ff e8 5e 63 d3 de 66 66 2e 0f 1f 84 00 00 00 00 [3.511642] RSP: 0018:b6b6c0d3b380 EFLAGS: 00010282 [3.511649] RAX: RBX: 8a5f9d464170 RCX: a097b148 [3.511654] RDX: RSI: 0003 RDI: 0001 [3.511657] RBP: b6b6c0d3b3d8 R08: R09: a0fb5642 [3.511661] R10: R11: 03d7 R12: 8a5fa2788000 [3.511666] R13: R14: 8a5f82740a20 R15: 8a5fa27887e0 [3.511670] FS: 7ff53569d8c0() GS:8a6aaf60() knlGS: [3.511676] CS: 0010 DS: ES: CR0: 80050033 [3.511680] CR2: 55ae059d3140 CR3: 00011d7a2006 CR4: 00770ee0 [3.511686] PKRU: 5554 [3.511689] Call Trace: [3.511693] [3.511700] ? intel_display_power_get+0x56/0x70 [i915] [3.512087] intel_dp_aux_xfer+0x12c/0x860 [i915] [3.512427] ? raw_spin_rq_unlock+0x10/0x40 [3.512440] intel_dp_aux_transfer+0x1d0/0x2f0 [i915] [3.512757] drm_dp_dpcd_access+0xad/0x130 [drm_display_helper] [3.512791] drm_dp_dpcd_write+0xb2/0x100 [drm_display_helper] [3.512825] intel_dp_sink_set_decompression_state+0x86/0xd0 [i915] [3.513107] intel_disable_ddi+0x10b/0x1b0 [i915] [3.513391] intel_encoders_disable+0x9b/0xc0 [i915] [3.513699] hsw_crtc_disable+0x61/0x80 [i915] [3.513964] intel_old_crtc_state_disables+0x3d/0xb0 [i915] [3.514212] intel_commit_modeset_disables+0x2ab/0x330 [i915] [3.514465] ? modeset_get_crtc_power_domains+0x69/0xc0 [i915] [3.514707] intel_atomic_commit_tail+0x197/0xbb0 [i915] [3.514937] intel_atomic_commit+0x3b1/0x400 [i915] [3.515155] drm_atomic_commit+0x94/0xd0 [drm] [3.515231] ? drm_plane_create_color_properties.cold+0x45/0x45 [drm] [3.515320] intel_initial_commit+0x183/0x210 [i915] [3.515544] intel_modeset_init+0x22/0x80 [i915] [3.515765] i915_driver_probe+0x1ec/0x480 [i915] [3.515963] ? drm_privacy_screen_get+0x164/0x190 [drm] [3.516038] ? acpi_dev_found+0x64/0x70 [3.516046] i915_pci_probe+0x56/0x140 [i915] [3.516245] local_pci_probe+0x44/0x80 [3.516251] pci_call_probe+0x55/0x180 [3.516255] pci_device_probe+0x84/0x110 [3.516260] really_probe+0x1ce/0x3a0 [3.516267] __driver_probe_device+0x11b/0x190 [3.516272] driver_probe_device+0x24/0xd0 [3.516278] __driver_attach+0xd8/0x200 [3.516283] ? __device_attach_driver+0x120/0x120 [3.516289] bus_for_each_dev+0x79/0xc0 [3.516294] driver_attach+0x1e/0x30 [3.516299] bus_add_driver+0x178/0x220 [3.516304] driver_register+0x8f/0xf0 [3.516309] __pci_register_driver+0x62/0x70 [3.516313] i915_pci_register_driver+0x23/0x30 [i915] [3.516506] i915_init+0x3b/0xee [i915] [3.516706] ? 0xc0a2f000 [3.516710] do_one_initcall+0x47/0x210 [3.516716] ? kmem_cache_alloc_trace+0x181/0x300 [3.516721] ? do_init_module+0x27/0x200 [3.516726] do_init_module+0x50/0x200 [3.516729] load_module+0xb60/0xcb0 [
