[Kernel-packages] [Bug 1882623] Re: VM enter into hung status after triggering a crash
Hi Team, When kdumping on 4.15.18 kernel in an Azure instance, we observe quite frequently a stall on the kdump kernel, it gets blocked and soon we see a stack like the following: INFO: rcu_sched detected stalls on CPUs/tasks: 1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0 (detected by 0, t=15002 jiffies, g=707, c=706, q=8457) rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 We tried porting this change https://lore.kernel.org/lkml/20171031221849.12117-1-mikel...@exchange.microsoft.com/ which seems to be the potential cause of above issue, but after this regular azure instance is hanging during the boot. Please let me know if I am missing any patches to solve this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-4.15 in Ubuntu. https://bugs.launchpad.net/bugs/1882623 Title: VM enter into hung status after triggering a crash Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-4.15 source package in Bionic: Fix Released Bug description: [Impact] * When kdumping on trusty/4.15 in an Azure instance, we observe quite frequently a stall on the kdump kernel, it gets blocked and soon we see a stack like the following: [ 65.452007] INFO: rcu_sched detected stalls on CPUs/tasks: [ 65.456004] 1-...!: (0 ticks this GP) idle=488/0/0 softirq=1/1 fqs=0 [ 65.456004] (detected by 0, t=15002 jiffies, g=707, c=706, q=8457) [ 65.456004] rcu_sched kthread starved for 15002 jiffies! g707 c706 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1 * By using the Azure serial console, we collected a sysrq-w when the issue happens: [ 529.515013] sysrq: Show Blocked State [ 529.517730] taskPC stack pid father [ 529.519006] kworker/u4:2D094 2 0x8000 [ 529.519006] Workqueue: events_unbound fsnotify_mark_destroy_workfn [ 529.519006] Call Trace: [ 529.519006] __schedule+0x292/0x880 [ 529.519006] schedule+0x36/0x80 [ 529.519006] schedule_timeout+0x1d5/0x2f0 [ 529.519006] ? check_preempt_wakeup+0x162/0x260 [ 529.519006] wait_for_completion+0xa5/0x110 [ 529.519006] ? wake_up_q+0x80/0x80 [ 529.519006] __synchronize_srcu.part.14+0x67/0x80 [ 529.519006] ? trace_raw_output_rcu_utilization+0x50/0x50 [ 529.519006] ? __switch_to_asm+0x41/0x70 [ 529.519006] synchronize_srcu+0xd1/0xd6 [ 529.519006] fsnotify_mark_destroy_workfn+0x6d/0xc0 [ 529.519006] process_one_work+0x14e/0x390 [ 529.519006] worker_thread+0x1cc/0x3d0 [ 529.519006] kthread+0x105/0x140 [ 529.519006] ? max_active_store+0x60/0x60 [ 529.519006] ? kthread_bind+0x20/0x20 [ 529.519006] ret_from_fork+0x35/0x40 [ 529.519006] udevadm D0 544 1 0x [ 529.519006] Call Trace: [ 529.519006] __schedule+0x292/0x880 [ 529.519006] schedule+0x36/0x80 [ 529.519006] schedule_timeout+0x1d5/0x2f0 [ 529.519006] ? try_to_wake_up+0x4a/0x460 [ 529.519006] ? try_to_wake_up+0x4a/0x460 [ 529.519006] wait_for_completion+0xa5/0x110 [ 529.519006] ? wake_up_q+0x80/0x80 [ 529.519006] __flush_work.isra.29+0x119/0x1b0 [ 529.519006] ? destroy_worker+0x90/0x90 [ 529.519006] flush_delayed_work+0x3f/0x50 [ 529.519006] fsnotify_wait_marks_destroyed+0x15/0x20 [ 529.519006] fsnotify_destroy_group+0x4e/0xc0 [ 529.519006] inotify_release+0x1e/0x50 [ 529.519006] __fput+0xea/0x220 [ 529.519006] fput+0xe/0x10 [ 529.519006] task_work_run+0x8c/0xb0 [ 529.519006] exit_to_usermode_loop+0x70/0xa9 [ 529.519006] do_syscall_64+0x1b5/0x1e0 [ 529.519006] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 529.519006] dhclientD0 573572 0x [ 529.519006] Call Trace: [ 529.519006] __schedule+0x292/0x880 [ 529.519006] schedule+0x36/0x80 [ 529.519006] schedule_timeout+0x1d5/0x2f0 [ 529.519006] ? aa_profile_af_perm+0xb4/0xf0 [ 529.519006] wait_for_completion+0xa5/0x110 [ 529.519006] ? wake_up_q+0x80/0x80 [ 529.519006] __wait_rcu_gp+0x123/0x150 [ 529.519006] synchronize_sched+0x4e/0x60 [ 529.519006] ? __call_rcu+0x2f0/0x2f0 [ 529.519006] ? trace_raw_output_rcu_utilization+0x50/0x50 [ 529.519006] synchronize_net+0x1c/0x30 [ 529.519006] __unregister_prot_hook+0xcd/0xf0 [ 529.519006] packet_do_bind+0x1bd/0x250 [ 529.519006] packet_bind+0x2f/0x50 [ 529.519006] SYSC_bind+0xd8/0x110 [ 529.519006] ? sock_alloc_file+0x91/0x130 [ 529.519006] SyS_bind+0xe/0x10 [ 529.519006] do_syscall_64+0x80/0x1e0 [ 529.519006] entry_SYSCALL_64_after_hwframe+0x41/0xa6 * Bisecting mainline kernels, we found that v4.17-rc1 didn't reproduce the issue, whereas v4.16 reproduced. Then, a fine-grained git bisect led us to the
[Kernel-packages] [Bug 1905272] Re: Can't get h/w video acceleration on rpi4
[Expired for snapd because there has been no activity for 60 days.] ** Changed in: snapd Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 Status in snapd: Expired Status in linux-raspi package in Ubuntu: Invalid Bug description: Hi, we've run into an issue where we can't get h/w video acceleration working on rpi4 on ubuntu core 18 (and 20). Our snap is using the following stack: Qt 5 eglfs + gstreamer + mesa. Raspberry's config txt has: dt_overlay=vc4-fkms-v3d, gpu_mem=256. I've enabled all video/opengl related interfaces: - opengl - hardware-observe - framebuffer. Gstreamer can't detect that it has support for h264 h/w decoding using v4l2 plugin. The very same snap unpacked on the raspbian and that is running in a pretty same way it is on the core immediately detects that h264 decoding is available (i.e. I unsquashfs it there, set the LD_LIBRARY_PATH, WEBGL_DRIVERS_PATH, and all other environment variables that are returned from `env` command when running snap run --shell my_snap). Because of that Qt falls back to the GStreamer pipeline with s/w decoder (avdec) and outputs like 0.5 frames per second (I am not sure if OpenGL actually works with h/w acceleration because even then it's so slow). Running on core 20 did not help - I tried running it in devmode as well without any differences. Raspbian, where it works, has 5.5 version of Linux kernel, I did try the beta version of core 20 which had 5.4 kernel version but it made no difference. lsmod on raspbian shows some extra modules related to vc4 not present on the core (not sure how relevant they are though): - v4l2_mem2mem - bcm2835_codec To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933373] Re: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05. It didn't work on Ubuntu 21.04 eit
[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/1933373 Title: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05. It didn't work on Ubuntu 21.04 either . But I can change brightness from brightness slider. Status in linux package in Ubuntu: Expired Bug description: I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: akash 1329 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 23:41:15 2021 InstallationDate: Installed on 2021-06-21 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82FG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=4d6dc3f0-ff06-49a5-b093-ae70cd670931 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: FHCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ITL05 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrFHCN24WW:bd01/14/2021:br1.24:efr1.24:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05: dmi.product.family: IdeaPad 5 15ITL05 dmi.product.name: 82FG dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05 dmi.product.version: IdeaPad 5 15ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933697] Re: touchpad not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933697 Title: touchpad not working Status in linux package in Ubuntu: Expired Bug description: my touchpad and mouses are not recongnized by ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-59-generic 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: spiders17 4049 F pulseaudio /dev/snd/controlC0: spiders17 4049 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 21:00:22 2021 InstallationDate: Installed on 2020-10-09 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-43 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=d1574370-d401-4eaa-86d0-ceeec8393f1b ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/18/2019:svnAcer:pnNitroAN515-43:pvrV1.06:rvnPK:rnOctavia_PKS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933752] Re: [Lenovo Legion 5 15ARH05] Touchpad + brightness
[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/1933752 Title: [Lenovo Legion 5 15ARH05] Touchpad + brightness Status in linux package in Ubuntu: Expired Bug description: Touchpad not work Cant change brightness ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-59-generic 5.8.0-59.66 ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: prometheus 4120 F pulseaudio /dev/snd/controlC0: prometheus 4120 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 27 14:33:32 2021 InstallationDate: Installed on 2021-06-05 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=76FC4166FC4121AB loop=/hostname/disks/root.disk ro ipv6.disable=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-59-generic N/A linux-backports-modules-5.8.0-59-generic N/A linux-firmware1.190.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982749] Re: New device IDs for Intel Raptor Lake S platform
All the device IDs, except for NPK and NPK/CPU, are in oem-5.17 as well. Submitted in bug 1978794. ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Incomplete Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
** Tags removed: bugnameltc-194783 severity-medium ** Tags added: bugnameltc-192677 severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])
** Tags added: sru-20220711 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1]) Status in ubuntu-kernel-tests: New Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: New Bug description: It looks like our P8 node "entei" tend to fail with the IPv6 TCP test from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels: # send cpu 119, receive socket 119 # send cpu 121, receive socket 121 # send cpu 123, receive socket 123 # send cpu 125, receive socket 125 # send cpu 127, receive socket 127 # IPv6 TCP publish-job-status: using request.json It failed silently here, this can be 100% reproduced with Groovy 5.8 and Focal 5.8. This will cause the ubuntu_kernel_selftests being interrupted, the test result for other tests cannot be processed to our result page. Please find attachment for the complete "net" test result on this node with Groovy 5.8.0-52.59 Add the kqa-blocker tag as this might needs to be manually verified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882669] Re: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
** Tags added: sru-20220711 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1882669 Title: Focal / Groovy aws and azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Focal: Confirmed Status in linux-azure source package in Groovy: Fix Released Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206] mmiotrace: enabled CPU14. kernel: [ 2236.232207] mmiotrace: enabled CPU15. kernel: [ 2236.264224] mmiotrace: enabled CPU16. kernel: [ 2236.300207] mmiotrace: enabled CPU17. kernel: [ 2236.332210] mmiotrace: enabled CPU18. kernel: [ 2236.372224] mmiotrace: enabled CPU19. kernel: [ 2236.404147] mmiotrace: enabled CPU20. kernel: [ 2236.452153] mmiotrace: enabled CPU21. kernel: [ 2236.492152] mmiotrace: enabled CPU22. kernel: [ 2236.524153] mmiotrace: enabled CPU23. kernel: [ 2236.564211] mmiotrace: enabled CPU24. kernel: [ 2236.612204] mmiotrace: enabled CPU25. kernel: [ 2236.644353] smpboot: Booting Node 0 Processor 26 APIC 0x1a kernel: [ 2236.645769] mmiotrace: enabled CPU26. kernel: [ 2236.684537] smpboot: Booting Node 0 Processor 27 APIC 0x1b kernel: [ 22
[Kernel-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** Changed in: mesa Status: Unknown => 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in Mesa: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 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-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-co
[Kernel-packages] [Bug 1982477] Re: [nvidia] Xorg cannot start with kernel 5.15.0-41
Yes please boot a kernel that works (like 5.15.0-40) and then run: lspci -k > lspci-nobug.txt journalctl -b0 > journal-nobug.txt and attach the resulting text files here. -- 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/1982477 Title: [nvidia] Xorg cannot start with kernel 5.15.0-41 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982749] Re: New device IDs for Intel Raptor Lake S platform
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
fcole90, The next step is to temporarily remove Nvidia from the equation. Please try: * Disable the Nvidia GPU in the BIOS if you can; or * Uninstall the Nvidia driver; or * Select 'Ubuntu on Wayland' at the login screen ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
Thanks. The log in comment #15 looks like the system is trying to resume, and Xorg is trying to resume. So I would bet this is probably an Nvidia driver problem. -- 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/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in Ubuntu: Incomplete Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #6887 https://gitlab.freedesktop.org/mesa/mesa/-/issues/6887 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/6887 Importance: Unknown Status: Unknown -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in Mesa: Unknown Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 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-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.comp
[Kernel-packages] [Bug 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works)
** Summary changed: - [amdgpu] System freezes coming out from suspension or randomly from screen power save + [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works) -- 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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save (5.15.0 fails but 5.18.14 works) Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961739] Re: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1961739
Title:
PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp
platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms, PS/2 keyboard cannot wake system up from s2idle.
[Fix]
Mainline commit cb1f65c1e142 ("PM: s2idle: ACPI: Fix wakeup interrupts
handling") picks up the missed wakeup interrupt.
[Test Case]
Use button press on PS/2 keyboard to wake suspended system.
[Where problems could occur]
It may still discard irqs under some very rare corner cases that are not
yet identified, but the implementation can be extended easily when
necessary.
[Other Info]
This affects 5.4+ kernels and has been proposed for linux-stable. While
this is merged in v5.17-rc4, linux-unstable will have this soon so
nomination is skipped.
== original bug report ==
With bug 1957026 and bug 1960434, suspend/resume using rtc and power
button work as expected, but PS/2 or USB keyboard still do not work
well as an wakeup source. This focus on fixes for PS/2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1961739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798552] Re: Enable keyboard wakeup for S2Idle laptops
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798552 Title: Enable keyboard wakeup for S2Idle laptops Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] Laptops default to S2Idle can't be woken up by keyboard during suspend. Most laptops can be woken up by keyboard in S3. To align the behavior, let's do the same for S2Idle laptops. [Fix] Set the serio keyboard wakeup to "enabled" as default. [Test] With this patch, XPS 9370 can be woken up by its keyboard during suspend. [Regression Potential] Low. This has the same effect as chaging sysfs knob "power/wakeup" from "disabled" to "enabled". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972134] Re: AMD APU s2idle is broken after the ASIC reset fix
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1972134 Title: AMD APU s2idle is broken after the ASIC reset fix Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The AMD based system can not reach s2idle after fix for LP: #1968475. [Fix] No need to evict resources for s2idle case. [Test] Test on a Cezanne, confirmed the 5.14.0-1035 breaks s2idle, and applying the fix can make s2idle work again. [Where problems could occur] The fix only applies to AMD APU, and the resources sould stay at carved out region over sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981910] Re: ACPI boot errors for kernel 5.15.0-41
I just started noticing this same error/bug when using 5.15.0-41-generic. I am able still to boot using this kernel, however it is very slow and when it does boot the screen resolution is stuck at 800x600 and the Nvidia drivers do not work (according to nvidia-smi). On the other hand if i boot with 5.13.0-30-generic, everything is normal, as far as i can tell. Thanks-- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1981910 Title: ACPI boot errors for kernel 5.15.0-41 Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: [0.481472] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481488] No Local Variables are initialized for Method [_CPC] [0.481490] No Arguments are initialized for method [_CPC] [0.481492] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.481552] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481561] No Local Variables are initialized for Method [_CPC] [0.481563] No Arguments are initialized for method [_CPC] [0.481565] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.481615] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481623] No Local Variables are initialized for Method [_CPC] [0.481625] No Arguments are initialized for method [_CPC] [0.481627] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.481680] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481687] No Local Variables are initialized for Method [_CPC] [0.481689] No Arguments are initialized for method [_CPC] [0.481691] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.481743] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481751] No Local Variables are initialized for Method [_CPC] [0.481753] No Arguments are initialized for method [_CPC] [0.481755] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.481813] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481820] No Local Variables are initialized for Method [_CPC] [0.481822] No Arguments are initialized for method [_CPC] [0.481824] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.481874] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.481882] No Local Variables are initialized for Method [_CPC] [0.481883] No Arguments are initialized for method [_CPC] [0.481885] ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) regression from kernel 5.13 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jul 16 17:53:02 2022 InstallationDate: Installed on 2021-07-04 (377 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1981910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
** Tags added: verification-done-jammy -- 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/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971193] 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 1971193 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/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470509] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470509] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470510] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470510] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470510] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470511] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470511] ? __schedule+0x280/0x700 [56048.470511] ? finish_wait+0x80/0x80 [56048.470512] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470512] kthread+0x112/0x130 [56048.470513] ? kthread_flush_work_fn+0x10/0x10 [56048.470513] ret_from_fork+0x1f/0x40 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/module/lpfc/version 0:14.0.390.2 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-
[Kernel-packages] [Bug 1972806] Re: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1972806 Title: [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] WCN6855-hw2.1 failed to resume after s2idle on AMD RMB [Fix] Update firmware of WCN6855-hw2.1 wifi to fix the issue of s2idle. [Test] Verified on WCN6855 hw2.0 and hw2.1, they work fine, s2idle OK. Wifi works fine after resume [Where problems could occur] These firmware is specific for WCN6855, it should be low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1972806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982524] Re: QCNFA765 in Lenovo Z16 fails after waking from s2idle
*** This bug is a duplicate of bug 1972806 *** https://bugs.launchpad.net/bugs/1972806 You're just a little ahead of the curve using this machine before it's certified and ready to go. You'll keep getting updates, that package was just in progress (In the "proposed" repo). It will promote to updates repo soon. I'll mark this as a duplicate of the other in progress bug for that WLAN firmware. ** This bug has been marked a duplicate of bug 1972806 [SRU][F][linux-firmware] UBUNTU: SAUCE: Update firmware of WCN6855 -- 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/1982524 Title: QCNFA765 in Lenovo Z16 fails after waking from s2idle Status in linux package in Ubuntu: Confirmed Bug description: Hi, I use a pretty new model laptop lenovo z16 running kubuntu. Biggest issue right now is it has an issue where when it wakes up from sleep the wifi adapter fails to work. I have tried restarting network related services with no success. Visually it seems the wifi adapter may not be recognized as it only shows the lan icon after waking. The I have found some relevant output in /var/log/syslog that seems to confirm the issue (wlp4s0) but not much else and I'm not sure where best to look for more detailed information on this type of issue. I attached that output as it is a couple hundred lines even though I tried to just get some informative bits. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D4_BU_Think_FM_ThinkPadZ16Gen1: dmi.product.family: ThinkPad Z16 Gen 1 dmi.product.name: 21D421D400 dmi.product.sku: LENOVO_MT_21D4_BU_Think_FM_ThinkPad Z16 Gen 1 dmi.product.version: ThinkPad Z16 Gen 1 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dm
[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
** Changed in: linux (Ubuntu) Status: Expired => 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/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session Status in linux package in Ubuntu: New Bug description: [Impact] Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470509] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470509] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470510] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470510] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470510] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470511] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470511] ? __schedule+0x280/0x700 [56048.470511] ? finish_wait+0x80/0x80 [56048.470512] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470512] kthread+0x112/0x130 [56048.470513] ? kthread_flush_work_fn+0x10/0x10 [56048.470513] ret_from_fork+0x1f/0x40 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/module/lpfc/version 0:14.0.390.2 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/modeldesc Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/fwrev 14.0.390.1, sli-4:2:c 14.0.390.1, sli-4:2:c [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/fc_host/host*/port_name 0x1090faf09459 0x1090faf0945a [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]#
[Kernel-packages] [Bug 1982787] [NEW] system locks up
Public bug reported: After starting a video, I noticed that my mouse and keyboard had become unresponsive. The video kept on playing but there was nothing I could do to take back control. I then tried to log in over SSH from another computer on my local network but there was "no route to host" and ping showed that the system was unreachable. At this stage, I did a cold reboot. Journalctl has recorded some 4000 lines describing a kernel bug at/around the time that the system locked up. See the bottom of the included file for details. Apt history shows that my current kernel was installed (upgraded) on 19 July. It has been a week but this is the first time that this locking issue has played up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1013-oem 5.17.0-1013.14 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 Uname: Linux 5.17.0-1013-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jul 25 22:25:08 2022 InstallationDate: Installed on 2022-03-27 (120 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: linux-signed-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "journalctl-full-220725.txt" https://bugs.launchpad.net/bugs/1982787/+attachment/5605252/+files/journalctl-full-220725.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1982787 Title: system locks up Status in linux-signed-oem-5.17 package in Ubuntu: New Bug description: After starting a video, I noticed that my mouse and keyboard had become unresponsive. The video kept on playing but there was nothing I could do to take back control. I then tried to log in over SSH from another computer on my local network but there was "no route to host" and ping showed that the system was unreachable. At this stage, I did a cold reboot. Journalctl has recorded some 4000 lines describing a kernel bug at/around the time that the system locked up. See the bottom of the included file for details. Apt history shows that my current kernel was installed (upgraded) on 19 July. It has been a week but this is the first time that this locking issue has played up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1013-oem 5.17.0-1013.14 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 Uname: Linux 5.17.0-1013-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Jul 25 22:25:08 2022 InstallationDate: Installed on 2022-03-27 (120 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: linux-signed-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.17/+bug/1982787/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982524] Re: QCNFA765 in Lenovo Z16 fails after waking from s2idle
Aaron and Mario, TYVM! This package has indeed fixed my error! Waking from sleep is also much faster which was probably related to having driver problems while waking. Will updates continue as normal leaving this installed? I figure apt will recognize newer versions as they become available. I am simply not sure how that would work though to be honest. Also, is there anyway to repay for this service? Perhaps donation to canonical? This has been wonderful and super helpful. -- 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/1982524 Title: QCNFA765 in Lenovo Z16 fails after waking from s2idle Status in linux package in Ubuntu: Confirmed Bug description: Hi, I use a pretty new model laptop lenovo z16 running kubuntu. Biggest issue right now is it has an issue where when it wakes up from sleep the wifi adapter fails to work. I have tried restarting network related services with no success. Visually it seems the wifi adapter may not be recognized as it only shows the lan icon after waking. The I have found some relevant output in /var/log/syslog that seems to confirm the issue (wlp4s0) but not much else and I'm not sure where best to look for more detailed information on this type of issue. I attached that output as it is a couple hundred lines even though I tried to just get some informative bits. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D4_BU_Think_FM_ThinkPadZ16Gen1: dmi.product.family: ThinkPad Z16 Gen 1 dmi.product.name: 21D421D400 dmi.product.sku: LENOVO_MT_21D4_BU_Think_FM_ThinkPad Z16 Gen 1 dmi.product.version: ThinkPad Z16 Gen 1 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Kernel-packages] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=195453.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2017-04-18T13:22:33+00:00 colin.king wrote:
There is a race condition on the fs->users counter and fs->in_exec flag
that impacts exec() on a suid program when there are multiple threads
being created and destroyed by a parent process. This in_exec flag was
introduced way back in 2009 with commit:
commit 498052bba55ecaff58db6a1436b0e25bfd75a7ff
Author: Al Viro
Date: Mon Mar 30 07:20:30 2009 -0400
When performing an exec() on a suid program, check_unsafe_exec() checks to see
we have more f->fs->users than the count of child threads that share the same
fs with the parent.
However, there are two race conditions that this seems to fail on:
1. The parent may be creating a new thread and copy_fs in kernel/fork.c
bumps the fs->users count before the thread is attached to the parent
hence causing the check p->fs->users > n_fs in check_unsafe_exec() to be
true in check_unsafe_exec() and cause the execution a the suid program
by the parent to fail to marked as unsafe and so it executes as a non-
suid executable. The crux of the matter is that the fs->user count
temporarily ahead by 1 with the number of threads linked to the process
and we don't have any locking mechanism to protect us from this in the
exec phase.
2. A thread my be dying and the associated fs pointer is nullified
before it is removed from the parent and this also causes issues in the
check_unsafe_exec() fs sanity check. I believe this can be fixed
checking for t->fs being NULL, e.g.:
diff --git a/fs/exec.c b/fs/exec.c
index 72934df68471..ebfd9b76b69f 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -1447,7 +1447,7 @@ static void check_unsafe_exec(struct linux_binprm *bprm)
spin_lock(&p->fs->lock);
rcu_read_lock();
while_each_thread(p, t) {
- if (t->fs == p->fs)
+ if (t->fs == p->fs || !t->fs)
n_fs++;
}
rcu_read_unlock();
The reproducer is quite simple and always easy to reproduce:
$ cat Makefile
ALL=a b
all: $(ALL)
a: LDFLAGS=-pthread
b: b.c
$(CC) b.c -o b
sudo chown root:root b
sudo chmod u+s b
test:
for I in $$(seq 1000); do echo $I; ./a ; done
clean:
rm -vf $(ALL)
$ cat a.c
#include
#include
#include
#include
void *nothing(void *p)
{
return NULL;
}
void *target(void *p) {
for (;;) {
pthread_t t;
if (pthread_create(&t, NULL, nothing, NULL) == 0)
pthread_join(t, NULL);
}
return NULL;
}
int main(void)
{
struct timespec tv;
int i;
for (i = 0; i < 10; i++) {
pthread_t t;
pthread_create(&t, NULL, target, NULL);
}
tv.tv_sec = 0;
tv.tv_nsec = 10;
nanosleep(&tv, NULL);
if (execl("./b", "./b", NULL) < 0)
perror("execl");
return 0;
}
$ cat b.c
#include
#include
#include
int main(void)
{
const uid_t euid = geteuid();
if (euid != 0) {
printf("Failed, got euid %d (expecting 0)\n", euid);
return 1;
}
return 0;
}
To reproduce:
make
make test
You will see "Failed, got euid 1000 (expecting 0)" errors whenever the
suid program being exec'd fails to exec as a suid process because of the
race and failure in check_unsafe_exec()
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/comments/12
On 2017-04-21T00:36:08+00:00 dev.jongy wrote:
I don't think the second condition you gave is relevant, because once
the task_struct->fs pointer is nullified, this thread is not accounted
in fs->users anymore. Since this thread doesn't count for neither
fs->count nor n_fs, it is okay.
The first condition is indeed a problem. I'm not sure of the wanted fix
(probably some kind of locking in copy_process, that while_each_thread
could use too), but currently this race is bad.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/comments/14
On 2017-04-21T09:47:07+00:00 colin.king wrote:
Thanks for looking at this. The locking on copy_process concerns me as
I didn't want to introduce a locking fix that caused a serious
performance regression on the copy and exec paths.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819/comments/15
On 2017-05-03T10:55:47+00:00 colin.king wrot
[Kernel-packages] [Bug 1690085]
(In reply to Hanna Baker from comment #777) > (In reply to Riccardo Gori from comment #7) > > I have the exact same problem with the same setup (Ryzen 1700X). > > > > I have experienced the problem with kernels 4.4, 4.10 and now 4.12.8. The > > system freeze also without X and without nvidia proprietary drivers. > > https://www.shoviv.com https://www.shoviv.com/imap-backup-and-restore.html https://www.shoviv.com/gmail-backup-tool.html https://www.shoviv.com/import-eml-to-office-365.html https://www.shoviv.com/mbox-to-office365.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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=x
[Kernel-packages] [Bug 1690085]
(In reply to Riccardo Gori from comment #7) > I have the exact same problem with the same setup (Ryzen 1700X). > > I have experienced the problem with kernels 4.4, 4.10 and now 4.12.8. The > system freeze also without X and without nvidia proprietary drivers. https://www.shoviv.com -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1982782] [NEW] Bionic update: upstream stable patchset 2022-07-25
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-07-25 Ported from the following upstream stable releases: v4.14.283, v4.19.247 v4.14.284, v4.19.248 from git://git.kernel.org/ Note: All patches from v4.14.284 and v4.19.248 had previously been applied. binfmt_flat: do not stop relocating GOT entries prematurely on riscv USB: serial: option: add Quectel BG95 modem USB: new quirk for Dell Gen 2 devices ptrace/xtensa: Replace PT_SINGLESTEP with TIF_SINGLESTEP ptrace: Reimplement PTRACE_KILL by always sending SIGKILL btrfs: add "0x" prefix for unsupported optional features btrfs: repair super block num_devices automatically drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes mwifiex: add mutex lock for call in mwifiex_dfs_chan_sw_work_queue b43legacy: Fix assigning negative value to unsigned variable b43: Fix assigning negative value to unsigned variable ipw2x00: Fix potential NULL dereference in libipw_xmit() ACPICA: Avoid cache flush inside virtual machines ALSA: jack: Access input_dev under mutex drm/amd/pm: fix double free in si_parse_power_table() ath9k: fix QCA9561 PA bias level media: venus: hfi: avoid null dereference in deinit media: pci: cx23885: Fix the error handling in cx23885_initdev() media: cx25821: Fix the warning when removing the module scsi: megaraid: Fix error check return value of register_chrdev() drm/amd/pm: fix the compile warning ipv6: Don't send rs packets to the interface of ARPHRD_TUNNEL ASoC: dapm: Don't fold register value changes into notifications s390/preempt: disable __preempt_count_add() optimization for PROFILE_ALL_BRANCHES dma-debug: change allocation mode from GFP_NOWAIT to GFP_ATIOMIC ipmi:ssif: Check for NULL msg when handling events and messages rtlwifi: Use pr_warn instead of WARN_ONCE openrisc: start CPU timer early in boot nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags ASoC: rt5645: Fix errorenous cleanup order net: phy: micrel: Allow probing without .driver_data media: exynos4-is: Fix compile warning rxrpc: Return an error to sendmsg if call failed eth: tg3: silence the GCC 12 array-bounds warning ARM: dts: ox820: align interrupt controller node name with dtschema fs: jfs: fix possible NULL pointer dereference in dbFree() ARM: OMAP1: clock: Fix UART rate reporting algorithm fat: add ratelimit to fat*_ent_bread() ARM: versatile: Add missing of_node_put in dcscb_init ARM: dts: exynos: add atmel,24c128 fallback to Samsung EEPROM ARM: hisi: Add missing of_node_put after of_find_compatible_node PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() tracing: incorrect isolate_mote_t cast in mm_vmscan_lru_isolate powerpc/xics: fix refcount leak in icp_opal_init() macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled RDMA/hfi1: Prevent panic when SDMA is disabled drm: fix EDID struct for old ARM OABI format ath9k: fix ar9003_get_eepmisc ASoC: mediatek: Fix error handling in mt8173_max98090_dev_probe ASoC: mediatek: Fix missing of_node_put in mt2701_wm8960_machine_probe x86/delay: Fix the wrong asm constraint in delay_loop() drm/mediatek: Fix mtk_cec_mask() spi: spi-ti-qspi: Fix return value handling of wait_for_completion_timeout NFC: NULL out the dev->rfkill to prevent UAF efi: Add missing prototype for efi_capsule_setup_info HID: hid-led: fix maximum brightness for Dream Cheeky spi: img-spfi: Fix pm_runtime_get_sync() error checking ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix inotify: show inotify mask flags in proc fdinfo fsnotify: fix wrong lockdep annotations x86/pm: Fix false positive kmemleak report in msr_build_context() drm/msm/dsi: fix error checks and return values for DSI xmit functions drm/msm/hdmi: check return value after calling platform_get_resource_byname() drm/rockchip: vop: fix possible null-ptr-deref in vop_bind() x86: Fix return value of __setup handlers irqchip/aspeed-i2c-ic: Fix irq_of_parse_and_map() return value x86/mm: Cleanup the control_va_addr_alignment() __setup handler drm/msm: return an error pointer in msm_gem_prime_get_sg_table() media: uvcvideo: Fix missing check to determine if element is found in list ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt media: st-delta: Fix PM disable depth imbalance in delta_probe media: exynos4-is: Change clk_disable to clk_disable_unprepare media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init Bl
[Kernel-packages] [Bug 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save
Any hope to see backported amdgpu driver on Ubuntu 22.04 kernel mainline? It's because official kernels are signed. Using different kernels it's mandatory to disable UEFI Sercure Boot. And if there's dual boot with Windows 10/11 I need to change continuosly into bios Secure Boot settings. Anyway I'm testing now the 5.18.14-051814-generic and it seems to work. But I needed change Secure Boot to Other OS. Yes I tried to sign but it didn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982483] Re: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274)
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=216139. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-06-15T20:06:45+00:00 ernstp wrote: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982483/comments/0 On 2022-07-14T00:21:42+00:00 ernstp wrote: Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982483/comments/1 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: h
[Kernel-packages] [Bug 1982780] [NEW] Missing dm-thin-pool Causes LXD LVM Failure
Public bug reported: Summary: Missing dm-thin-pool.ko causes LXD failure. 1) Release root@jammy-vm:~# lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) Package root@jammy-vm:~# apt-cache policy linux-modules-5.15.0-1002-kvm linux-modules-5.15.0-1002-kvm: Installed: 5.15.0-1002.2 Candidate: 5.15.0-1002.2 Version table: *** 5.15.0-1002.2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) What I expect to happen The following command should succeed. lxd init --auto --storage-backend=lvm 4) What happened: Lxd's default lvm storage backend fails on linux-kvm due to missing dm- thin-pool.ko. Output: root@jammy-vm:~# uname -a Linux jammy-vm 5.15.0-1002-kvm #2-Ubuntu SMP Wed Feb 9 10:14:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@jammy-vm:~# modinfo dm-thin-pool modinfo: ERROR: Module dm-thin-pool not found. root@jammy-vm:~# lxd init --auto --storage-backend=lvm Error: Failed to create storage pool 'default': Error creating LVM thin pool named "LXDThinPool": Failed to run: lvcreate --yes --wipesignatures y --poolmetadatasize 1G --thinpool default/LXDThinPool --extents 100%FREE: modprobe: FATAL: Module dm-thin-pool not found in directory /lib/modules/5.15.0-1002-kvm /sbin/modprobe failed: 1 thin-pool: Required device-mapper target(s) not detected in your kernel. Run `lvcreate --help' for more information. I haven't found any -kvm kernels yet that have this kmod, so I suspect a backport of the fix will be required to supported releases. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1982780 Title: Missing dm-thin-pool Causes LXD LVM Failure Status in linux-kvm package in Ubuntu: New Bug description: Summary: Missing dm-thin-pool.ko causes LXD failure. 1) Release root@jammy-vm:~# lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 2) Package root@jammy-vm:~# apt-cache policy linux-modules-5.15.0-1002-kvm linux-modules-5.15.0-1002-kvm: Installed: 5.15.0-1002.2 Candidate: 5.15.0-1002.2 Version table: *** 5.15.0-1002.2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) What I expect to happen The following command should succeed. lxd init --auto --storage-backend=lvm 4) What happened: Lxd's default lvm storage backend fails on linux-kvm due to missing dm-thin-pool.ko. Output: root@jammy-vm:~# uname -a Linux jammy-vm 5.15.0-1002-kvm #2-Ubuntu SMP Wed Feb 9 10:14:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux root@jammy-vm:~# modinfo dm-thin-pool modinfo: ERROR: Module dm-thin-pool not found. root@jammy-vm:~# lxd init --auto --storage-backend=lvm Error: Failed to create storage pool 'default': Error creating LVM thin pool named "LXDThinPool": Failed to run: lvcreate --yes --wipesignatures y --poolmetadatasize 1G --thinpool default/LXDThinPool --extents 100%FREE: modprobe: FATAL: Module dm-thin-pool not found in directory /lib/modules/5.15.0-1002-kvm /sbin/modprobe failed: 1 thin-pool: Required device-mapper target(s) not detected in your kernel. Run `lvcreate --help' for more information. I haven't found any -kvm kernels yet that have this kmod, so I suspect a backport of the fix will be required to supported releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1982780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918960] Re: kernel does not honor mokx revocations, allowing kexec lockdown bypass
This has been addressed in Ubuntu kernels derived from upstream 5.4 and later. 4.15 kernels and older still need to be addressed. -- 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/1918960 Title: kernel does not honor mokx revocations, allowing kexec lockdown bypass Status in linux package in Ubuntu: Confirmed Bug description: All kernels do not honor mokx certificate revocations, and thus does not honor the 2012 certificate revocation, nor the post 2017 certificate signed kernels that allow acpi bypass. This can allow bypass of lockdown restrictions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982286] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982286 Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: .15.0-41-generic tried to reinstall linux kernals and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: seth 1145 F pulseaudio /dev/snd/controlC0: seth 1145 F pulseaudio /dev/snd/controlC1: seth 1145 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue Jul 19 22:02:25 2022 ErrorMessage: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-18 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IV_GA401IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=84f082e4-3567-461b-a1db-0de43bb5668e ro 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IV.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IV 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.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IV.219:bd12/30/2020:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IV_GA401IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IV_GA401IV 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/1982286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982285] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982285 Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: .15.0-41-generic tried to reinstall linux kernals and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: seth 1145 F pulseaudio /dev/snd/controlC0: seth 1145 F pulseaudio /dev/snd/controlC1: seth 1145 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue Jul 19 22:02:25 2022 ErrorMessage: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-18 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IV_GA401IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=84f082e4-3567-461b-a1db-0de43bb5668e ro 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IV.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IV 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.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IV.219:bd12/30/2020:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IV_GA401IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IV_GA401IV 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/1982285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982285] Re: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982285 Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: .15.0-41-generic tried to reinstall linux kernals and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: seth 1145 F pulseaudio /dev/snd/controlC0: seth 1145 F pulseaudio /dev/snd/controlC1: seth 1145 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue Jul 19 22:02:25 2022 ErrorMessage: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-18 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IV_GA401IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=84f082e4-3567-461b-a1db-0de43bb5668e ro 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IV.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IV 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.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IV.219:bd12/30/2020:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IV_GA401IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IV_GA401IV 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/1982285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982286] Re: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982286 Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: .15.0-41-generic tried to reinstall linux kernals and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: seth 1145 F pulseaudio /dev/snd/controlC0: seth 1145 F pulseaudio /dev/snd/controlC1: seth 1145 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Tue Jul 19 22:02:25 2022 ErrorMessage: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-18 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IV_GA401IV ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=84f082e4-3567-461b-a1db-0de43bb5668e ro 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. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux Title: package linux-image-5.15.0-41-generic 5.15.0-41.44 failed to install/upgrade: installed linux-image-5.15.0-41-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IV.219 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IV 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.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IV.219:bd12/30/2020:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IV_GA401IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IV_GA401IV 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/1982286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783] Re: there is an ACPI error message every time it booting
Launchpad has imported 69 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=213023. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-05-10T17:23:25+00:00 ionut_n2001 wrote: Hi Kernel Team, Observe this issue: [2.057284] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330) [2.057339] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [2.057443] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330) [2.057484] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) [2.057569] ACPI BIOS Error (bug): Could not resolve symbol [\_PR.CPU0._CPC], AE_NOT_FOUND (20210105/psargs-330) [2.057610] ACPI Error: Aborting method \_PR.CPU3._CPC due to previous error (AE_NOT_FOUND) (20210105/psparse-529) lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 142 Model name: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz Stepping:9 CPU MHz: 2200.000 CPU max MHz: 3400. CPU min MHz: 400. BogoMIPS:4399.99 Virtualization: VT-x L1d cache: 64 KiB L1i cache: 64 KiB L2 cache:512 KiB L3 cache:4 MiB NUMA node0 CPU(s): 0-3 Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Not affected Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_t sc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibp b stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsav ec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d dmesg | grep -E "ACPI|BIOS" [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x00057fff] usable [0.00] BIOS-e820: [mem 0x00058000-0x00058fff] reserved [0.00] BIOS-e820: [mem 0x00059000-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x6cdbefff] usable [0.00] BIOS-e820: [mem 0x6cdbf000-0x6cdb] ACPI NVS [0.00] BIOS-e820: [mem 0x6cdc-0x6cdc0fff] reserved [0.00] BIOS-e820: [mem 0x6cdc1000-0x7a465fff] usable [0.00] BIOS-e820: [mem 0x7a466000-0x7a7a4fff] reserved [0.00] BIOS-e820: [mem 0x7a7a5000-0x7a7e2fff] ACPI data [0.00] BIOS-e820: [mem 0x7a7e3000-0x7afbafff] ACPI NVS [0.00] BIOS-e820: [mem 0x7afbb000-0x7b3fdfff] reserved [0.00] BIOS-e820: [mem 0x7b3fe000-0x7b3fefff] usable [
[Kernel-packages] [Bug 1975454] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: Confirmed Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982524] Re: QCNFA765 in Lenovo Z16 fails after waking from s2idle
Thanks Aaron! @josh if https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.3/+build/24103899/+files/linux- firmware_20220329.git681281e4-0ubuntu3.3_all.deb solves it we should mark this as a duplicate of #1972806 for you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982524 Title: QCNFA765 in Lenovo Z16 fails after waking from s2idle Status in linux package in Ubuntu: Confirmed Bug description: Hi, I use a pretty new model laptop lenovo z16 running kubuntu. Biggest issue right now is it has an issue where when it wakes up from sleep the wifi adapter fails to work. I have tried restarting network related services with no success. Visually it seems the wifi adapter may not be recognized as it only shows the lan icon after waking. The I have found some relevant output in /var/log/syslog that seems to confirm the issue (wlp4s0) but not much else and I'm not sure where best to look for more detailed information on this type of issue. I attached that output as it is a couple hundred lines even though I tried to just get some informative bits. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D4_BU_Think_FM_ThinkPadZ16Gen1: dmi.product.family: ThinkPad Z16 Gen 1 dmi.product.name: 21D421D400 dmi.product.sku: LENOVO_MT_21D4_BU_Think_FM_ThinkPad Z16 Gen 1 dmi.product.version: ThinkPad Z16 Gen 1 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:c
[Kernel-packages] [Bug 1975454] Re: [Dell XPS 15 7590] Cannot resume after suspend
Hi, here's the needed log, finally :D ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+attachment/5605240/+files/prevboot.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1975454 Title: [Dell XPS 15 7590] Cannot resume after suspend Status in linux package in Ubuntu: New Bug description: For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text: ``` Bluetooth hcio: Timed out waiting for suspend events Bluetooth hcio: Suspend timeout bit: 6 Bluetooth hcio: Suspend notifier action (3) failed: -110 ``` (There might be typos, I retyped it from a photo) Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session. I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected. Let me know if you need more information or digging into the logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 23 08:44:30 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2020-04-03 (779 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://l
[Kernel-packages] [Bug 1982776] [NEW] linux-modules for -kvm does not include dm-crypt
Public bug reported: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1982776 Title: linux-modules for -kvm does not include dm-crypt Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Focal: New Status in linux-kvm source package in Jammy: New Bug description: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1982776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
** Description changed: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create VM on Azure Install crash dump utilies (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) sudo apt install linux-crashdump Say (y) to all questions during install Reboot the VM As root on the VM after reboot: kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1085-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1085-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1085-azure root=UUID=a117a689-aa1d-4cdc-8a30-7b9fbf174437 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console Outcome after removing "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger #kdump works, VM eventually (several minutes) reboots # Login to VM and check that there is a core file in /var/crash: ls /var/crash [Where Problems Could Occur] This change modifies the debian/rules. The package could fail to build properly if mistyped. [Other] Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. - target series - Kinetic -> Bionic + target series - Bionic, Focal, Jammy upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 *Note: There are two source packages needed changes, kdump-tools for Impish -> Kinetic and makedumpfile for series Focal -> Bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Committed Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: New Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Incomplete Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Committed Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create VM on Azure Install crash dump utilies (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) sudo apt install linux-crashdump Say (y) to all questions during install Reboot the VM As root on the VM after reboot: kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1085-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1085-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1085-azure root=UUID=a117a689-aa1d-4cdc-8a30-7b9fbf174437 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 Outcome with "ata_p
[Kernel-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** Changed in: linux Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 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-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-
[Kernel-packages] [Bug 1982093] Re: Screen/display issue
Hi, was the system installed with the stock 22.04 kernel (5.15)? If yes, did it have the same issue? It should still be installed on the disk and easy to test with it ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1982093 Title: Screen/display issue Status in linux-oem-5.17 package in Ubuntu: Incomplete Bug description: After updates my laptop screen goes psychedelic when my cursor is near the bottom of my screen. I have a video of it but can't upload it. It happened first in Montreal when support updated my kernel, so they put me back on the previous kernel and it fixed it. But I did updates yesterday and since restarting it's happened again ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1013-oem 5.17.0-1013.14 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 Uname: Linux 5.17.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 19 09:23:52 2022 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claire 2352 F pulseaudio /dev/snd/pcmC0D0p: claire 2352 F...m pulseaudio /dev/snd/pcmC0D6c: claire 2352 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21CBCTO1WW Package: linux-signed-oem-5.17 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.0-1013-oem root=UUID=d4f57971-5311-4b4a-aab5-ee87020fbbfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1013-oem N/A linux-backports-modules-5.17.0-1013-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.17.0-1013-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/31/2022 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET60W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrN3AET60W(1.25):bd05/31/2022:br1.25:efr1.13:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: claire 2352 F pulseaudio /dev/snd/pcmC1D0c: claire 2352 F...m pulseaudio /dev/snd/controlC0: claire 2352 F pulseaudio /dev/snd/pcmC0D0p: claire 2352 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21CBCTO1WW Package: linux-signed-oem-5.17 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.0-1013-oem root=UUID=d4f57971-5311-4b4a-aab5-ee87020fbbfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1013-oem N/A linux-backports-modules-5.17.0-1013-oem N/A linux-firmware
[Kernel-packages] [Bug 1982093] Re: Screen/display issue
** No longer affects: linux-signed-oem-5.17 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1982093 Title: Screen/display issue Status in linux-oem-5.17 package in Ubuntu: Incomplete Bug description: After updates my laptop screen goes psychedelic when my cursor is near the bottom of my screen. I have a video of it but can't upload it. It happened first in Montreal when support updated my kernel, so they put me back on the previous kernel and it fixed it. But I did updates yesterday and since restarting it's happened again ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1013-oem 5.17.0-1013.14 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 Uname: Linux 5.17.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 19 09:23:52 2022 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claire 2352 F pulseaudio /dev/snd/pcmC0D0p: claire 2352 F...m pulseaudio /dev/snd/pcmC0D6c: claire 2352 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21CBCTO1WW Package: linux-signed-oem-5.17 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.0-1013-oem root=UUID=d4f57971-5311-4b4a-aab5-ee87020fbbfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1013-oem N/A linux-backports-modules-5.17.0-1013-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.17.0-1013-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/31/2022 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET60W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrN3AET60W(1.25):bd05/31/2022:br1.25:efr1.13:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: claire 2352 F pulseaudio /dev/snd/pcmC1D0c: claire 2352 F...m pulseaudio /dev/snd/controlC0: claire 2352 F pulseaudio /dev/snd/pcmC0D0p: claire 2352 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21CBCTO1WW Package: linux-signed-oem-5.17 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.0-1013-oem root=UUID=d4f57971-5311-4b4a-aab5-ee87020fbbfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1013-oem N/A linux-backports-modules-5.17.0-1013-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.17.0-1013-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm
[Kernel-packages] [Bug 1975649] Re: flowtable: fix TCP flow teardown
This bug was fixed in the package linux-bluefield - 5.4.0-1042.47 --- linux-bluefield (5.4.0-1042.47) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1042.47 -proposed tracker (LP: #1979463) * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - [Config] bluefield: update configs for NVM * flowtable: fix TCP flow teardown (LP: #1975649) - netfilter: flowtable: fix TCP flow teardown * remove offload_pickup sysctl again (LP: #1975820) - netfilter: conntrack: remove offload_pickup sysctl again * mlxbf_gige: remove driver-managed interrupt counts (LP: #1975749) - mlxbf_gige: remove driver-managed interrupt counts [ Ubuntu: 5.4.0-122.138 ] * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: c
[Kernel-packages] [Bug 1975749] Re: mlxbf_gige: remove driver-managed interrupt counts
This bug was fixed in the package linux-bluefield - 5.4.0-1042.47 --- linux-bluefield (5.4.0-1042.47) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1042.47 -proposed tracker (LP: #1979463) * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - [Config] bluefield: update configs for NVM * flowtable: fix TCP flow teardown (LP: #1975649) - netfilter: flowtable: fix TCP flow teardown * remove offload_pickup sysctl again (LP: #1975820) - netfilter: conntrack: remove offload_pickup sysctl again * mlxbf_gige: remove driver-managed interrupt counts (LP: #1975749) - mlxbf_gige: remove driver-managed interrupt counts [ Ubuntu: 5.4.0-122.138 ] * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: c
[Kernel-packages] [Bug 1975820] Re: remove offload_pickup sysctl again
This bug was fixed in the package linux-bluefield - 5.4.0-1042.47 --- linux-bluefield (5.4.0-1042.47) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1042.47 -proposed tracker (LP: #1979463) * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - [Config] bluefield: update configs for NVM * flowtable: fix TCP flow teardown (LP: #1975649) - netfilter: flowtable: fix TCP flow teardown * remove offload_pickup sysctl again (LP: #1975820) - netfilter: conntrack: remove offload_pickup sysctl again * mlxbf_gige: remove driver-managed interrupt counts (LP: #1975749) - mlxbf_gige: remove driver-managed interrupt counts [ Ubuntu: 5.4.0-122.138 ] * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: c
[Kernel-packages] [Bug 1980730] Re: OVS internal port Hardware Offload implementation is missing in Jammy kernel
Hi Zack, I tried to install this kernel pkgs (headers, image, modules), however when trying to boot with this kernel it fails over a failure to detect root file system (see screenshot). When I revert back to the default kernel it boots. What did I miss? ** Attachment added: "kernel_rootfs.PNG" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980730/+attachment/5605217/+files/kernel_rootfs.PNG -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980730 Title: OVS internal port Hardware Offload implementation is missing in Jammy kernel Status in linux package in Ubuntu: Incomplete Bug description: Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic When deploying Charmed Openstack deployment with HW Offload over Jammy series, some of the traffic workloads (mainly those related to Floating IP and NAT) will not be properly offloaded. In order to solve it, "OVS internal port offload" feature was introduced and pushed to upstream kernel. These are the main base patches for the feature we call "OVS internal port offload": b16eb3c81fe27978afdb2c111908d4d627a88d99 net/mlx5: Support internal port as decap route device 5e9942721749fc96b9df4b0545474153316c0571 net/mlx5e: Term table handling of internal port rules 166f431ec6beaf472bc2e116a202a127b64779e4 net/mlx5e: Add indirect tc offload of ovs internal port 100ad4e2d75837c9b42f49b3814b4b42ec9ebe46 net/mlx5e: Offload internal port as encap route device 27484f7170edabbda7b53650cd24d38295cffe60 net/mlx5e: Offload tc rules that redirect to ovs internal port dbac71f22954276633e525f958994f84a7bd303f net/mlx5e: Accept action skbedit in the tc actions list 4f4edcc2b84fecec66748ecbb90a84b981ecdaae net/mlx5: E-Switch, Add ovs internal port mapping to metadata support 189ce08ebf876df2b51f625877731055475352df net/mlx5e: Use generic name for the forwarding dev pointer 28e7606fa8f106cdc0355e0548396c037443e063 net/mlx5e: Refactor rx handler of represetor device Please make sure to take as well all patches the came later on top of those base patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Hi, I experience the same problem with my Lenovo ThinkPad T14 Gen 2a (AMD Ryzen 7 PRO 5850U). Also, about 1 hour after waking up from suspend mode. $ uname -a Linux ThinkPad-T14-Gen-2a 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux The following is a condensed excerpt from the /var/log/syslog: rtw89_pci :03:00.0: FW status = 0x77001100 rtw89_pci :03:00.0: FW BADADDR = 0x0 rtw89_pci :03:00.0: FW EPC/RA = 0x0 rtw89_pci :03:00.0: FW MISC = 0x0 rtw89_pci :03:00.0: R_AX_HALT_C2H = 0x1000 rtw89_pci :03:00.0: R_AX_SER_DBG_INFO = 0x100 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fea5 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898ffad rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fe8b rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fe93 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898ff9b rtw89_pci :03:00.0: [ERR]fw PC = 0xb898ffad rtw89_pci :03:00.0: [ERR]fw PC = 0xb898ff97 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898ff9b rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fe87 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fe8f rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fe95 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898feb3 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898fea3 rtw89_pci :03:00.0: [ERR]fw PC = 0xb898febf rtw89_pci :03:00.0: [ERR]fw PC = 0xb898ff95 rtw89_pci :03:00.0: ---> err=0x1000 rtw89_pci :03:00.0: R_AX_SER_DBG_INFO =0x0100 rtw89_pci :03:00.0: R_AX_CMAC_ERR_ISR =0x rtw89_pci :03:00.0: R_AX_DMAC_ERR_ISR =0x0100 rtw89_pci :03:00.0: R_AX_WDE_ERR_FLAG_CFG =0x rtw89_pci :03:00.0: R_AX_PLE_ERR_FLAG_CFG =0x rtw89_pci :03:00.0: R_AX_HOST_DISPATCHER_ALWAYS_IMR=0x0c40 rtw89_pci :03:00.0: R_AX_HOST_DISPATCHER_ALWAYS_ISR=0x0040 rtw89_pci :03:00.0: R_AX_CPU_DISPATCHER_ALWAYS_IMR=0x0462 rtw89_pci :03:00.0: R_AX_CPU_DISPATCHER_ALWAYS_ISR=0x rtw89_pci :03:00.0: R_AX_OTHER_DISPATCHER_ALWAYS_IMR=0x rtw89_pci :03:00.0: R_AX_OTHER_DISPATCHER_ALWAYS_ISR=0x rtw89_pci :03:00.0: R_AX_RPQ_RXBD_IDX =0x003d003d rtw89_pci :03:00.0: R_AX_DBG_ERR_FLAG=0x rtw89_pci :03:00.0: R_AX_LBC_WATCHDOG=0x0041 rtw89_pci :03:00.0: <--- rtw89_pci :03:00.0: ser event = 0x1000 rtw89_pci :03:00.0: firmware failed to ack for leaving ps mode rtw89_pci :03:00.0: pci dmach busy1 0x28 rtw89_pci :03:00.0: pci dmach busy1 0x28 rtw89_pci :03:00.0: lv1 rcvy pci stop dma fail rtw89_pci :03:00.0: sec cam entry is empty rtw89_pci :03:00.0: sec cam entry is empty rtw89_pci :03:00.0: sec cam entry is empty ieee80211 phy0: Hardware restart was requested rtw89_pci :03:00.0: MAC has already powered on rtw89_pci :03:00.0: failed to get available bssid cam rtw89_pci :03:00.0: failed to init bssid cam rtw89_pci :03:00.0: failed to get available bssid cam rtw89_pci :03:00.0: failed to init bssid cam The last two lines are repeated until the machine is rebooted. For now, I will try the options suggested in https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1971656/comments/13 -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ Packag
[Kernel-packages] [Bug 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
I just verified: 5.15.0-40-generic definitely shows the symptoms. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Guessing from the description of the symptoms and the dependency on linux-modules-extra I would suspect the problem to be in the i915 driver (which is responsible for accelerated graphics on Intel GPUs). That would also explain problems of SDM to come up. Safe mode would likely choose a much lower resolution on whatever fallback graphics driver the system comes up with. But then breaking between -39 and -40 makes no sense since there is no change at all to that driver between those versions. Breaking between -40 and -41 would be more plausible since there are 4: e53980320c13 drm/i915: update new TMDS clock setting defined by VBT 04d6fb5f9f53 drm/i915: Fix SEL_FETCH_PLANE_*(PIPE_B+) register addresses bf7bdd3e16a4 drm/i915: Check EDID for HDR static metadata when choosing blc 082bac8947b5 drm/i915/display/psr: Unset enable_psr2_sel_fetch if other checks in intel_psr2_config_valid() fails The first one to me would sound most likely but I don't have that much insight into that driver, so it is hard to make connections between the descriptions and the symptoms described. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: EL
[Kernel-packages] [Bug 1982749] Re: New device IDs for Intel Raptor Lake S platform
** Description changed: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 - SMBus 0x7a23 https://lore.kernel.org/linux-i2c/20220211150001.1004004-1-jarkko.nik...@linux.intel.com/T/#u - I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ - HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ - SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ + SMBus 0x7a23 9c02d4011e92 v5.18-rc1 + I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 + HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 + SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 - GPIO INTC1085 https://lore.kernel.org/linux-gpio/20220215152800.21104-2-andriy.shevche...@linux.intel.com/ + GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class ** Description changed: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 - SPI Flash Controller 0x7a24 + SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class -- 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/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982477] Re: [nvidia] Xorg cannot start with kernel 5.15.0-41
As I stated earlier my network driver also has problems with the new kernel version. I assume that running apport-collect will only provide useful information if I run it while running the problematic kernel version. What commands shall I run to collect logs? I will then attach them here after rebooting into the older kernel version that works. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982477 Title: [nvidia] Xorg cannot start with kernel 5.15.0-41 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982739] Re: BlueZ 5.65 release
** Attachment added: "bluez_5.65-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+attachment/5605211/+files/bluez_5.65-0ubuntu1.debian.tar.xz -- 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/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982739] Re: BlueZ 5.65 release
** Attachment added: "bluez_5.65.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+attachment/5605210/+files/bluez_5.65.orig.tar.xz -- 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/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982749] 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 1982749 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/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 9c02d4011e92 v5.18-rc1 I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1 HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1 SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1 SPI Flash Controller 0x7a24 GPIO INTC1085 ddfdd1304e59 v5.18-rc1 NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982749] Re: New device IDs for Intel Raptor Lake S platform
** Description changed: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. - USB device/xDCI 0x7a61 https://lore.kernel.org/linux-usb/20220214141948.18637-1-heikki.kroge...@linux.intel.com/ + USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 https://lore.kernel.org/linux-i2c/20220211150001.1004004-1-jarkko.nik...@linux.intel.com/T/#u I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI Flash Controller 0x7a24 GPIO INTC1085 https://lore.kernel.org/linux-gpio/20220215152800.21104-2-andriy.shevche...@linux.intel.com/ NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class -- 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/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6 SMBus 0x7a23 https://lore.kernel.org/linux-i2c/20220211150001.1004004-1-jarkko.nik...@linux.intel.com/T/#u I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI Flash Controller 0x7a24 GPIO INTC1085 https://lore.kernel.org/linux-gpio/20220215152800.21104-2-andriy.shevche...@linux.intel.com/ NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982749] [NEW] New device IDs for Intel Raptor Lake S platform
Public bug reported: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 https://lore.kernel.org/linux-usb/20220214141948.18637-1-heikki.kroge...@linux.intel.com/ SMBus 0x7a23 https://lore.kernel.org/linux-i2c/20220211150001.1004004-1-jarkko.nik...@linux.intel.com/T/#u I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI Flash Controller 0x7a24 GPIO INTC1085 https://lore.kernel.org/linux-gpio/20220215152800.21104-2-andriy.shevche...@linux.intel.com/ NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: intel oem-priority originate-from-1960931 ** Tags added: intel oem-priority originate-from-1960931 -- 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/1982749 Title: New device IDs for Intel Raptor Lake S platform Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Feature Description] This task is to identify what new device IDs are required for RPL-S. Placeholder for RPL-S IDs that should be published. USB device/xDCI 0x7a61 https://lore.kernel.org/linux-usb/20220214141948.18637-1-heikki.kroge...@linux.intel.com/ SMBus 0x7a23 https://lore.kernel.org/linux-i2c/20220211150001.1004004-1-jarkko.nik...@linux.intel.com/T/#u I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b https://lore.kernel.org/lkml/20220211145055.992179-1-jarkko.nik...@linux.intel.com/ SPI Flash Controller 0x7a24 GPIO INTC1085 https://lore.kernel.org/linux-gpio/20220215152800.21104-2-andriy.shevche...@linux.intel.com/ NPK 0x7a26 NPK/CPU 0xA76Fh TBT AHCI Binds by PCI Class XHCI Binds by PCI Class To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982739] Re: BlueZ 5.65 release
** Changed in: bluez (Ubuntu) Status: Triaged => In Progress -- 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/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980688] Re: [Lenovo ThinkPad T14] Mouse / trackpad buttons sometimes don't work after waking up from suspend
Here are some additional information: - When the error occurs, not only do the keys of the trackpad of the T14 stop to work, but also any USB mouse that is connected shows the same problem. - The errors seems to mostly occur when the laptop is not connected to any external device (monintor, USB devices) at the time of wake-up. -- 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/1980688 Title: [Lenovo ThinkPad T14] Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982477] Re: [nvidia] Xorg cannot start with kernel 5.15.0-41
** Tags added: i915 -- 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/1982477 Title: [nvidia] Xorg cannot start with kernel 5.15.0-41 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
** Summary changed: - Latest kernel breaks LCD screen + [Medion Akoya E3223] Latest kernel breaks LCD screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982716] Re: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Also affects: linux-hwe-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.17 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-hwe-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982716 Title: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-hwe-5.17 source package in Jammy: In Progress Bug description: [Impact] The audio mute key (F5) and mic-mute LED (F8) don't work on some HP 440/450/640/650 G9 laptops. [Fix] The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple motherboard design and they are using different subsystem ID of audio codec. Add the same quirk for other MBs. [Test] After applying the fix, the mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then the LED may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1982716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
** Changed in: linux (Ubuntu Jammy) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982477] Re: [nvidia] Xorg cannot start with kernel 5.15.0-41
Something strange in comment #7 - Your Intel GPU has no kernel driver loaded. And it's usually the only one wired to the screen. So that would explain a lot. It would also explain why I don't see other reports of the problem against the Nvidia driver if it's really an Intel GPU problem. -- 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/1982477 Title: [nvidia] Xorg cannot start with kernel 5.15.0-41 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982477] 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 1982477 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/1982477 Title: [nvidia] Xorg cannot start with kernel 5.15.0-41 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982477] Re: [nvidia] Xorg cannot start with kernel 5.15.0-41
That's the latest Nvidia driver and the latest kernel, so I am wondering what else is unique about this system since no one else seems to be reporting the bug. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982477 Title: [nvidia] Xorg cannot start with kernel 5.15.0-41 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: After upgrading my Linux kernel to version 5.15.0-41, I am no longer able to get into the UI. After booting and unlocking the disk I end up on a black screen with a blinking underscore in the top left corner. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 21 12:14:04 2022 InstallationDate: Installed on 2021-12-03 (229 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=linux SHELL=/usr/bin/zsh PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978252] Re: Fix screen flickering caused by PSR on Intel TGL platform
** Changed in: hwe-next Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978252 Title: Fix screen flickering caused by PSR on Intel TGL platform Status in HWE Next: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Screen flickers on certain Intel TGL laptops. [Fix] Enable PSR2 selective fetch along with several PSR fixes. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] PSR can be glitchy. Fortunately it's not system breaking so we can push subsequent fixes if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982739] [NEW] BlueZ 5.65 release
Public bug reported: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz ** Affects: bluez (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: kinetic upgrade-software-version -- 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/1982739 Title: BlueZ 5.65 release Status in bluez package in Ubuntu: Triaged Bug description: Release BlueZ 5.65 to kinetic: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
SRU: https://lists.ubuntu.com/archives/kernel-team/2022-July/132126.html (jammy, V2) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982736] [NEW] system hang when running dmidecode on arm64
Public bug reported: Running the following commands on NVIDIA Jeston Xavier NX devkit (ARM64 device) can cause system hang. $ sudo dmidecode --type system The solution we found to fix this issue is as below. 1. Get Source & Debian files from https://packages.ubuntu.com/impish/dmidecode • dmidecode_3.3.orig.tar.xz • dmidecode_3.3-3.debian.tar.xz 2. Ignore override_dh_auto_build in debian/rules for aarch64 # override_dh_auto_build: # dh_auto_build -- CC=$(CC) CFLAGS="$(CFLAGS) $(CPPFLAGS) -Os -ansi" LDFLAGS="$(LDFLAGS)" It looks like the source code is OK, but the way to build dmidecode is set improperly to cause this issue on ARM64 only. An alternative way to fix it is to build source with single make command. $ sudo apt-get install make $ git clone git://git.savannah.gnu.org/dmidecode.git $ cd dmidecode $ make $ sudo make install Thanks! ** Affects: dmidecode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1982736 Title: system hang when running dmidecode on arm64 Status in dmidecode package in Ubuntu: New Bug description: Running the following commands on NVIDIA Jeston Xavier NX devkit (ARM64 device) can cause system hang. $ sudo dmidecode --type system The solution we found to fix this issue is as below. 1. Get Source & Debian files from https://packages.ubuntu.com/impish/dmidecode • dmidecode_3.3.orig.tar.xz • dmidecode_3.3-3.debian.tar.xz 2. Ignore override_dh_auto_build in debian/rules for aarch64 # override_dh_auto_build: # dh_auto_build -- CC=$(CC) CFLAGS="$(CFLAGS) $(CPPFLAGS) -Os -ansi" LDFLAGS="$(LDFLAGS)" It looks like the source code is OK, but the way to build dmidecode is set improperly to cause this issue on ARM64 only. An alternative way to fix it is to build source with single make command. $ sudo apt-get install make $ git clone git://git.savannah.gnu.org/dmidecode.git $ cd dmidecode $ make $ sudo make install Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1982736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
All proposed patches have been in 5.17 or above. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Incomplete Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982627] Re: MT7612u wireless chipset not working on Raspberry Pi 400
** Tags added: kern-3993 -- 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/1982627 Title: MT7612u wireless chipset not working on Raspberry Pi 400 Status in linux-firmware package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: I purchased the Alfa AWUS036ACM wireless adapter to use with my Raspberry Pi 400. The adapter works when using Raspberry Pi OS, but not when using "Ubuntu for Raspberry Pi" release 22.04. I have tested 64-bit variants for Ubuntu Desktop and Ubuntu Server, and the results are the same. I followed the Kernel Firmware Debugging steps, and included its output below. The LinuxWireless Debugging steps seem to only be appropriate if the wireless adapter is working to some capacity so the below output does not include those steps. I also attempted to follow the Kernel USB Debugging steps, but the commands do not seem appropriate for the Raspberry Pi 400. For example, `/proc/bus/usb` and `/sys/kernel/debug/usb/usbmon/` do not exist on the filesystem. As part of troubleshooting, I updated the bootloader for the Raspberry Pi 400 to version 507b2360 which was built on 2022-04-26. I also ran `sudo apt update` and `sudo apt full-upgrade`. Neither of these troubleshooting steps resolved the problem. On a separate note, I have another Ubuntu Server release 22.04 that is installed on dedicated hardware (not the "Ubuntu for Raspberry Pi" variant), and the wireless adapter does work on this machine. Raspberry Pi 400 Output $ sudo modprobe usbmon modprobe: FATAL: Module usbmon not found in directory /lib/modules/5.15.0-1012-raspi $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.2 Candidate: 20220329.git681281e4-0ubuntu3.2 Version table: *** 20220329.git681281e4-0ubuntu3.2 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages $ sudo udevadm control --log-priority debug $ tail -f /var/log/syslog Jul 22 20:56:03 ubuntu kernel: [ 533.687623] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd Jul 22 20:56:03 ubuntu kernel: [ 533.709177] usb 2-1: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00 Jul 22 20:56:03 ubuntu kernel: [ 533.709203] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4 Jul 22 20:56:03 ubuntu kernel: [ 533.709214] usb 2-1: Product: Wireless Jul 22 20:56:03 ubuntu kernel: [ 533.709222] usb 2-1: Manufacturer: MediaTek Inc. Jul 22 20:56:03 ubuntu kernel: [ 533.709230] usb 2-1: SerialNumber: 0 Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: Validate module index Jul 22 20:56:03 ubuntu systemd-udevd[451]: Check if link configuration needs reloading. Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device ready for processing (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: Successfully forked off 'n/a' as PID 1330. Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Worker [1330] is forked for processing SEQNUM=4179. Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Processing device (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Failed to get watch handle, ignoring: No such file or directory Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'usb_id' Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: Device is queued (SEQNUM=4180, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: SEQNUM=4180 blocked by SEQNUM=4179 Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued (SEQNUM=4181, ACTION=bind) Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: SEQNUM=4181 blocked by SEQNUM=4179 Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb' Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: hwdb modalias key: "usb:v0E8Dp7612:Wireless " Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:50 MODE 0664 Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id' Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Setting permissions /dev/bus/usb/002/003, uid=0, gid=0, mode=0664 Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Handling device nod
[Kernel-packages] [Bug 1982650] Re: screen flickering
Thanks for the bug report. This is most likely to be bug 1958191 which for most people was fixed in kernel 5.15.0-40. So please update your system: sudo apt update sudo apt full-upgrade and then reboot. If that doesn't fix it then please try adding kernel parameter: intel_iommu=igfx_off ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982650 Title: screen flickering Status in linux package in Ubuntu: Incomplete Bug description: [Sat Jul 23 11:32:16 2022] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Sat Jul 23 11:33:39 2022] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-39-generic 5.15.0-39.42 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hari 1074 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 23 11:44:21 2022 InstallationDate: Installed on 2021-02-24 (513 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Inspiron 5559 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=e2bb84ca-dd6e-40ec-8b37-00f696fb958e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-25 (89 days ago) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd09/07/2020:br1.9:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct10:cvr:sku06B2: dmi.product.family: Inspiron dmi.product.name: Inspiron 5559 dmi.product.sku: 06B2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking
That's what I'm doing currently - using Windows for the time being. From personal experience I can say that the chance of something being fixed in BIOS is fairly low and can take a loong time. But why would Lenovo want to release a new BIOS for this since it works flawlessly in Windows? Perhaps a software fix in the i915 driver is possible? -- 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/1982679 Title: Lenovo T16 unable to wake up from sleep, screen blinking Status in linux package in Ubuntu: Confirmed Bug description: Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics. Running Ubuntu 22.04 LTS. Unable to wake up from sleep - the screen backlight is on, but the screen is solid black. After a while it starts randomly flashing with a login screen for about ~300ms and also each time I type a character. Also the "reboot" command hangs. Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in BIOS - same issue. Not sure if relevant, but journal log contains these lines: jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes still around after SIGKILL. Ignoring. jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable link training jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-post' timed out. Terminating. jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'final-sigterm' timed out. Killing. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1761 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 09:22:18 2022 InstallationDate: Installed on 2022-07-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
Remove linux-firmware from affected packages as there is no change to be submitted for it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01 BT driver support: USB\VID_0489&PID_E0C9&REV_0001 Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01 BT driver support: USB\VID_0489&PID_E0CC&REV_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
WCN6856 6G support was explicitly turned off in bug 1954938, making the commits porting to jammy meaningless. (And yet all the 6G support should have been in position in oem-5.17) The "UBUNTU: SAUCE: Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller", which is not related to WiFi 6G, has been committed separately in bug 1955689. No further work to do in Jammy migration. ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Fix Released ** No longer affects: linux-firmware (Ubuntu) ** No longer affects: linux-firmware (Ubuntu Focal) ** No longer affects: linux-firmware (Ubuntu Hirsute) ** No longer affects: linux-firmware (Ubuntu Impish) ** No longer affects: linux-firmware (Ubuntu Jammy) ** No longer affects: linux-firmware (Ubuntu Kinetic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01 BT driver support: USB\VID_0489&PID_E0C9&REV_0001 Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01 BT driver support: USB\VID_0489&PID_E0CC&REV_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982524] Re: QCNFA765 in Lenovo Z16 fails after waking from s2idle
ath11k issue will be fixed by next release of linux-firmware which is already in proposed channel. 20220329.git681281e4-0ubuntu3.3 WCN6855 firmware version: ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 -- 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/1982524 Title: QCNFA765 in Lenovo Z16 fails after waking from s2idle Status in linux package in Ubuntu: Confirmed Bug description: Hi, I use a pretty new model laptop lenovo z16 running kubuntu. Biggest issue right now is it has an issue where when it wakes up from sleep the wifi adapter fails to work. I have tried restarting network related services with no success. Visually it seems the wifi adapter may not be recognized as it only shows the lan icon after waking. The I have found some relevant output in /var/log/syslog that seems to confirm the issue (wlp4s0) but not much else and I'm not sure where best to look for more detailed information on this type of issue. I attached that output as it is a couple hundred lines even though I tried to just get some informative bits. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21D4_BU_Think_FM_ThinkPadZ16Gen1: dmi.product.family: ThinkPad Z16 Gen 1 dmi.product.name: 21D421D400 dmi.product.sku: LENOVO_MT_21D4_BU_Think_FM_ThinkPad Z16 Gen 1 dmi.product.version: ThinkPad Z16 Gen 1 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 9506 F pulseaudio /dev/snd/controlC1: josh 9506 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-14 (8 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21D421D400 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e3c131dd-33bc-483e-aa46-b73d2d084cd4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2022 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N3GET35W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21D421D400 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3GET35W(1.16):bd06/29/2022:br1.16:efr1.17:svnLENOVO:pn21D421D400:pvrThinkPadZ16Gen1:rvnLENOVO:rn21D421D400:rvrNotDefined:cvnLENOVO:ct
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1939528 Title: Need support of Qualcomm WCN6856 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-firmware source package in Hirsute: Won't Fix Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Won't Fix Status in linux-firmware source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: New Status in linux-firmware source package in Jammy: New Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Incomplete Status in linux-firmware source package in Kinetic: Confirmed Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Qualcomm WCN685x is not supported yet. [Fix] Qualcomm WCN685x support are mostly available in linux-next and mainline with one patch currently in kvalo/ath tree, and 3 additional in review. [Test Case] Test hardware connectivity, stability with basic checkbox tests: $ lspci -nnk | grep Network -A 3 :02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0b8] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci [Where problems could occur] While this introduces a new hardware, it might need further polishments. [Other Info] WCN685x WiFi 6E capability is still under development and is moved to next milestone for oem projects. Firmware blobs for both WiFi and Bluetooth are also needed and will be SRUed when a formal release is made. == original bug report == Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01 BT driver support: USB\VID_0489&PID_E0C9&REV_0001 Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01 BT driver support: USB\VID_0489&PID_E0CC&REV_0001 https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/ Already landed to mainline kernel v5.14-rc1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981922] Re: Upgrade yellow carp DMCUB firmware to fix suspend failure
Any ETA for the fix landed focal proposed or update channel? Thanks. -- 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/1981922 Title: Upgrade yellow carp DMCUB firmware to fix suspend failure Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Certain Rembrandt designs use LPDDR memory and current firmware in linux-firmware package in Focal and Jammy has a failure resuming from s0i3 on DC power with it. Some sample designs affected by the failure are Thinkpad X13, Z13, Z16. This failure doesn't affect resume with AC power or designs without LPDDR memory. [Fix] Upgrade yellow carp DMCUB firmware binary. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=4458bb4185b6d6e1f5c586fcf4b8cf6f5d3c8e24 [Test] Verify suspend/resume works. Verify that externally plugged displays haven't regressed. [Where problems could occur] Firmware is only loaded to Rembrandt designs. Regressions would be tied to those platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982679] Re: Lenovo T16 unable to wake up from sleep, screen blinking
This is a known issue of new vbios, please wait for a new BIOS to fix 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/1982679 Title: Lenovo T16 unable to wake up from sleep, screen blinking Status in linux package in Ubuntu: Confirmed Bug description: Lenovo T16 Gen1 (2022), Intel Core i7-1270P (12 gen) integrated graphics. Running Ubuntu 22.04 LTS. Unable to wake up from sleep - the screen backlight is on, but the screen is solid black. After a while it starts randomly flashing with a login screen for about ~300ms and also each time I type a character. Also the "reboot" command hangs. Tried with both "Suspend-to-Idle" and "Linux S3" suspend settings in BIOS - same issue. Not sure if relevant, but journal log contains these lines: jul 24 08:59:07 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:10 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:12 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI jul 24 08:59:15 me7 systemd[1653]: org.gnome.Shell@wayland.service: Processes still around after SIGKILL. Ignoring. jul 24 08:59:17 me7 kernel: i915 :00:02.0: [drm] *ERROR* failed to enable link training jul 24 08:59:20 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:20 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'stop-post' timed out. Terminating. jul 24 08:59:21 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:23 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x60 jul 24 08:59:25 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92 jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: State 'final-sigterm' timed out. Killing. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 1908 (gnome-shell) with signal SIGKILL. jul 24 08:59:25 me7 systemd[1653]: org.gnome.Shell@wayland.service: Killing process 9858 (pool-gnome-shel) with signal SIGKILL. jul 24 08:59:29 me7 kernel: i915 :00:02.0: [drm] *ERROR* Failed to write source OUI ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1761 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 24 09:22:18 2022 InstallationDate: Installed on 2022-07-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21BVCTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=e7d73517-9423-4c2b-9ed8-92c32e2796e7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2022 dmi.bios.release: 1.2 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET05W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET05W(1.02):bd06/07/2022:br1.2:efr1.3:svnLENOVO:pn21BVCTO1WW:pvrThinkPadT16Gen1:rvnLENOVO:rn21BVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BV_BU_Think_FM_ThinkPadT16Gen1: dmi.product.family: ThinkPad T16 Gen 1 dmi.product.name: 21BVCTO1WW dmi.product.sku: LENOVO_MT_21BV_BU_Think_FM_ThinkPad T16 Gen 1 dmi.product.version: ThinkPad T16 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982621] Re: Spinner vanishes from screen during 22.04 boot from USB
I agree the time between the spinner vanishing and the live session starting is too long. Though I've never seen the spinner come back... or do you mean the mouse cursor appearing in the bottom right quadrant of the screen? ** No longer affects: 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/1982621 Title: Spinner vanishes from screen during 22.04 boot from USB Status in plymouth package in Ubuntu: Confirmed Bug description: I burnt Ubuntu 22.04 to USB and used it to boot a stock Dell XPS 15 laptop. It started the boot OK, showed the splash screen with the spinner rotating. After about two minutes the spinner disappears for 55 secs, then reappears, and the disappears again. The system continues to boot successfully from USB. The problem is that it is VERY unnerving for a new or potential user when the only sign of life vanishes without trace or warning. I have watched new users get up and walk away permanently from systems that do this because to then it means it has hung, and won't be coming back. Is it possible to nice(1) the background processes to the point where they do not usurp all cycles from the spinner? A blind process (like a splash screen) should NEVER stop communicating to the users that it is still alive and kicking. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5442 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 LiveMediaBuild: 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 003: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0 Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 18a5:0302 Verbatim, Ltd Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-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: 08/30/2017 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:br1.5:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:sku07BE: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1982621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
