[Kernel-packages] [Bug 1896350] Re: nbd: requests can become stuck when disconnecting from server with qemu-nbd
Performing verification for Focal. I started a fresh Focal VM, and installed qemu-utils. I then ran reproducer.sh from the testcase section. The kernel is 5.4.0-124-generic from -updates. Within 30 seconds of starting the reproducer, the testcase script hung, and the following was in dmesg: Aug 23 04:49:26 focal-nbd kernel: block nbd15: NBD_DISCONNECT Aug 23 04:49:26 focal-nbd kernel: block nbd15: Send disconnect failed -32 Aug 23 04:49:26 focal-nbd sudo[1804]: pam_unix(sudo:session): session closed for user root Aug 23 04:49:26 focal-nbd sudo[1807]: ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img Aug 23 04:49:26 focal-nbd sudo[1807]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) Aug 23 04:49:26 focal-nbd kernel: ldm_validate_partition_table(): Disk read failed. Aug 23 04:49:26 focal-nbd kernel: Dev nbd15: unable to read RDB block 0 Aug 23 04:49:26 focal-nbd kernel: nbd15: unable to read partition table Aug 23 04:49:56 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 30 seconds Aug 23 04:50:26 focal-nbd systemd-udevd[419]: nbd15: Worker [1198] processing SEQNUM=5582 is taking a long time Aug 23 04:50:27 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 60 seconds Aug 23 04:50:58 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 90 seconds Aug 23 04:51:29 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 120 seconds Aug 23 04:51:59 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 150 seconds Aug 23 04:52:26 focal-nbd systemd-udevd[419]: nbd15: Worker [1198] processing SEQNUM=5582 killed Aug 23 04:52:30 focal-nbd kernel: block nbd15: Possible stuck request 4d5cc344: control (read@523988992,36864B). Runtime 180 seconds Aug 23 04:53:27 focal-nbd kernel: INFO: task qemu-nbd:1815 blocked for more than 120 seconds. Aug 23 04:53:27 focal-nbd kernel: Not tainted 5.4.0-124-generic #140-Ubuntu Aug 23 04:53:27 focal-nbd kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 23 04:53:27 focal-nbd kernel: qemu-nbdD0 1815 1 0x Aug 23 04:53:27 focal-nbd kernel: Call Trace: Aug 23 04:53:27 focal-nbd kernel: __schedule+0x2e3/0x740 Aug 23 04:53:27 focal-nbd kernel: ? __kfifo_to_user_r+0xa0/0xa0 Aug 23 04:53:27 focal-nbd kernel: schedule+0x42/0xb0 Aug 23 04:53:27 focal-nbd kernel: blk_mq_freeze_queue_wait+0x4b/0xb0 Aug 23 04:53:27 focal-nbd kernel: ? __wake_up_pollfree+0x40/0x40 Aug 23 04:53:27 focal-nbd kernel: blk_mq_freeze_queue+0x1b/0x20 Aug 23 04:53:27 focal-nbd kernel: nbd_add_socket+0x5e/0x1d0 [nbd] Aug 23 04:53:27 focal-nbd kernel: nbd_ioctl+0x2f7/0x410 [nbd] Aug 23 04:53:27 focal-nbd kernel: blkdev_ioctl+0x383/0xa30 Aug 23 04:53:27 focal-nbd kernel: block_ioctl+0x3d/0x50 Aug 23 04:53:27 focal-nbd kernel: do_vfs_ioctl+0x407/0x670 Aug 23 04:53:27 focal-nbd kernel: ? putname+0x4a/0x50 Aug 23 04:53:27 focal-nbd kernel: ksys_ioctl+0x67/0x90 Aug 23 04:53:27 focal-nbd kernel: __x64_sys_ioctl+0x1a/0x20 Aug 23 04:53:27 focal-nbd kernel: do_syscall_64+0x57/0x190 Aug 23 04:53:27 focal-nbd kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Aug 23 04:53:27 focal-nbd kernel: RIP: 0033:0x7fd12b7573ab Aug 23 04:53:27 focal-nbd kernel: Code: Bad RIP value. Aug 23 04:53:27 focal-nbd kernel: RSP: 002b:7fd129fa2a18 EFLAGS: 0246 ORIG_RAX: 0010 Aug 23 04:53:27 focal-nbd kernel: RAX: ffda RBX: 0001 RCX: 7fd12b7573ab Aug 23 04:53:27 focal-nbd kernel: RDX: 000b RSI: ab00 RDI: 000d Aug 23 04:53:27 focal-nbd kernel: RBP: 7fd129fa2aa8 R08: R09: 0001 Aug 23 04:53:27 focal-nbd kernel: R10: R11: 0246 R12: 7fd129fa2ab0 Aug 23 04:53:27 focal-nbd kernel: R13: 000d R14: 1f40 R15: 7fd12b80 I then rebooted, enabled -proposed and installed kernel 5.4.0-125-generic. I left the reproducer.sh script running for a bit over an hour, and it was still running perfectly fine when I got back to it. Requests are still moving smoothly, and no longer getting stuck. The 5.4.0-125-generic kernel in -proposed fixes the issue. Happy to mark it verified. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896350 Title: nbd: requests can become stuck when disconnecting from server with qemu-nbd Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status
[Kernel-packages] [Bug 1986976] Re: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login.
ACPI errors are theoretically BIOS bugs, not Linux bugs. Although the fact that you can see the messages is bug 1970069. Since it sounds like the flickering has stopped we can mark this as a duplicate of bug 1958191. -- 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/1986976 Title: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login. Status in linux package in Ubuntu: Incomplete Bug description: I do remember such BIOS related issues back in 2019 for now I do have the list of the kernel error messages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: labdom 3949 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-07-15 (1130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 003: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ea604268-2faf-42c2-abf5-69e0de92b334 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy wayland-session Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-17 (2 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2018 dmi.bios.release: 7.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.12:bd09/06/2018:br7.12:efr7.13:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965307] Re: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- 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/1965307 Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux-firmware package in Ubuntu: Expired Bug description: 'linux-firmware_1.187.27_all.deb' in unbutu package ---> does not exist !!! And can not upgrading : package linux-firmware 1.187.26 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.26 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sirenux1759 F pulseaudio /dev/snd/controlC3: sirenux1759 F pulseaudio /dev/snd/controlC2: sirenux1759 F pulseaudio /dev/snd/controlC0: sirenux1759 F pulseaudio CasperMD5CheckResult: skip Date: Thu Mar 17 15:00:10 2022 Dependencies: DuplicateSignature: package:linux-firmware:1.187.26 Removing linux-image-generic-hwe-20.04 (5.13.0.30.33~20.04.17) ... dpkg: error processing package linux-firmware (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2022-01-19 (56 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp27s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd MS-7B07 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=c0e47fc1-d36a-4d49-a7fb-c934c673b142 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.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-VH PLUS (MS-7B07) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.C0:bd11/06/2018:br5.13:svnMicro-StarInternationalCo.,Ltd:pnMS-7B07:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VHPLUS(MS-7B07):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B07 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1965307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979599] Re: [Dell Latitude 5490] Touchpad works only for a little while
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1979599 Title: [Dell Latitude 5490] Touchpad works only for a little while Status in libinput package in Ubuntu: Expired Status in linux-hwe-5.13 package in Ubuntu: Expired Bug description: When I work with my mouse pad or external mouse it stops working short after I started ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 23 09:53:51 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0816] InstallationDate: Installed on 2021-11-27 (207 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0c45:6717 Microdia Integrated_Webcam_HD Bus 001 Device 005: ID 248a:8367 Maxxter Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-51-generic root=UUID=2bb9fec0-37e2-4386-bf2f-31a193b03072 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DH2HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd10/06/2021:br1.19:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816: dmi.product.family: Latitude dmi.product.name: Latitude 5490 dmi.product.sku: 0816 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1979599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979599] Re: [Dell Latitude 5490] Touchpad works only for a little while
[Expired for linux-hwe-5.13 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1979599 Title: [Dell Latitude 5490] Touchpad works only for a little while Status in libinput package in Ubuntu: Expired Status in linux-hwe-5.13 package in Ubuntu: Expired Bug description: When I work with my mouse pad or external mouse it stops working short after I started ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 23 09:53:51 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0816] InstallationDate: Installed on 2021-11-27 (207 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0c45:6717 Microdia Integrated_Webcam_HD Bus 001 Device 005: ID 248a:8367 Maxxter Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-51-generic root=UUID=2bb9fec0-37e2-4386-bf2f-31a193b03072 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0DH2HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd10/06/2021:br1.19:svnDellInc.:pnLatitude5490:pvr:rvnDellInc.:rn0DH2HV:rvrA00:cvnDellInc.:ct10:cvr:sku0816: dmi.product.family: Latitude dmi.product.name: Latitude 5490 dmi.product.sku: 0816 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1979599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987247] Re: The SD card can't find after cool boot from Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Package changed: thermald (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1987247 Title: The SD card can't find after cool boot from Ubuntu. Status in Ubuntu: New Bug description: Issue brief: With Linux (Ubuntu 22.04/ Kernel 5.15.0-25), we are meeting an issue of SD card reorganization after cold boot under Jasper Lake platform. When inserting an SD card and cold boot the device, the device boot into system without detecting the SD card. The card reader is from Intel SOC, and Jasper lake CRB is able to duplicate the SD card reorganization issue with Ubuntu, whereas OS Windows does not have the same trouble. Expected result: The SD card should be detect after cold boot. We also found a new clue that under normal status (with or without TF card inserted after booting), the mmc_rescan() function starts from "test--->mmc_rescan:0" to output the logs, and finally executes to "test--->mmc_rescan:9", execute the mmc_rescan() function. But when TF card is powered on (poweron-with-card.log), after mmc_rescan() executes to "test--->mmc_rescan_try_freq:0:40", "test--->mmc_rescan:0 log" appears again. That means, "mmc_rescan" has not been executed before executed again. We are wondering if this is the reason why the TF card cannot be recognized when the TF card is turned-on. We attached the logs of this issue: 1. poweron-with-card.log 2. poweron-without-card.txt 3. OK.log 4. ./mmc: This directory corresponds to the log code, please search for "KERN_ERR" in the code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1987247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987148] Re: package linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-43-generic package pre-removal script subprocess
Kernel folks, what's the deal with this message? I thought I deleted my current kernel occasionally but I can't recall seeing this screen before. 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/1987148 Title: package linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-43-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: not sure exactly what is causing this. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: linux-image-5.15.0-43-generic:amd64: Remove linux-image-unsigned-5.15.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 19 10:17:17 2022 ErrorMessage: installed linux-image-5.15.0-43-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-06 (409 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-43-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1987148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981526] Re: i915 drivers unstable with i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3135 end=3136) t
@Nusch, would you please try 5.17-oem? the patches that applied in 5.10-oem would be also applied on 5.17-oem. Need to know if it's a regression. 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/1981526 Title: i915 drivers unstable with i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3135 end=3136) t Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: There are ocasional flickerings with i915 drivers, the dmesg discovered one of possible reasons on Dell XPS13 9310: [10103.828209] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3135 end=3136) time 2743 us, min 2385, max 2399, scanline start 2131, end 68 I'm eager to debug it further if needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nusch 16067 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 08:06:54 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2622 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1057-oem root=/dev/mapper/ubuntu--vg-root ro intel_idle.max_cstate=4 i915.enable_psr=0 i915.reset=2 tsc=unstable quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1057-oem N/A linux-backports-modules-5.10.0-1057-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2022 dmi.bios.release: 3.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.7.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.7.0:bd05/09/2022:br3.7:svnDellInc.:pnXPS139310:pvr:sku0991:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1981526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987148] Re: package linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-43-generic package pre-removal script subprocess
** 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-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1987148 Title: package linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-43-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: not sure exactly what is causing this. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: linux-image-5.15.0-43-generic:amd64: Remove linux-image-unsigned-5.15.0-43-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 19 10:17:17 2022 ErrorMessage: installed linux-image-5.15.0-43-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-06 (409 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-43-generic 5.15.0-43.46~20.04.1 failed to install/upgrade: installed linux-image-5.15.0-43-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1987148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987345] [NEW] Kinetic update: v5.19.3 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.3 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: 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/1987345 Title: Kinetic update: v5.19.3 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.3 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610833/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610832/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610828/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610829/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610831/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610830/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610826/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610827/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610825/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610824/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610823/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610822/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610821/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610820/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 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-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy Uname: Linux 5.15.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/26/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1985688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1985688] Re: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46
apport information ** Tags added: apport-collected jammy ** Description changed: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: libcha 956 F pulseaudio + /dev/snd/controlC2: libcha 956 F pulseaudio + /dev/snd/controlC1: libcha 956 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-04-24 (120 days ago) + InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + IwConfig: + lono wireless extensions. + + enp2s0no wireless extensions. + MachineType: To be filled by O.E.M. To be filled by O.E.M. + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + LANGUAGE= + TERM=xterm-256color + PATH=(custom, no user) + LANG=cs_CZ.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=013374aa-b474-4e69-8b0e-01bf8d43faaa ro delayacct quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 + 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-41-generic N/A + linux-backports-modules-5.15.0-41-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.2 + RfKill: + + Tags: jammy + Uname: Linux 5.15.0-41-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/26/2015 + dmi.bios.release: 4.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2603 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: M5A97 R2.0 + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: To be filled by O.E.M. + dmi.product.sku: SKU + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: To be filled by O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1985688/+attachment/5610819/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1985688 Title: Kubuntu freezes at boot after kernel upgraded to 5.15.0-46 Status in linux package in Ubuntu: Incomplete Bug description: My Kubuntu 22.04 upgraded itself via "unattended upgrade". This included new kernel version 5.15.0-46 . Since then, the boot process always freezes at the stage when there is something like "Terminate Plymouth Boot Screen Finished" printed on it. It doesn't react to anything further, except NumLock. When I choose older kernel 5.15.0-41 in Grub, Kubuntu boots without problem. I'm not sure what specific configuration information to share. Please inform me what is needed. Here are some random facts: I use proprietary nvidia-driver-390 powering my GeForce GT520 This system had been updated from Kubuntu 21.10 several months ago AMD FX(tm)-8300 Eight-Core Processor + ASUS M5A97 R2.0 Thank you! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: libcha 956 F pulseaudio /dev/snd/controlC2: libcha 956 F pulseaudio /dev/snd/controlC1: libcha 956 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-24 (120 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono
[Kernel-packages] [Bug 1987232] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610813/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] Re: WARN in trace_event_dyn_put_ref
The fix has also been added to the Stable queue for 5.15 and 5.19 as of this morning: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/tree/queue-5.19/tracing-perf-fix-double-put-of-trace-event- when-init-fails.patch https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable- queue.git/tree/queue-5.15/tracing-perf-fix-double-put-of-trace-event- when-init-fails.patch -- 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/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610814/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610815/+files/acpidump.txt ** 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/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610812/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610811/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610808/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610810/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610809/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.12xlarge dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] Re: WARN in trace_event_dyn_put_ref
apport information ** Tags added: apport-collected focal uec-images ** Description changed: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d - The problem started appearing as soon as our systems picked up the - linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory - serves). Could you please cherry pick this fix and pull it back to the - the linux and linux-aws kernels for Focal? There's test here: - https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ - that reproduces the problem very reliably for me. With the patch - applied, I no longer get the WARNs. + The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Aug 22 17:32 seq + crw-rw 1 root audio 116, 33 Aug 22 17:32 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Amazon EC2 c5d.12xlarge + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 + ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-1015-aws N/A + linux-backports-modules-5.15.0-1015-aws N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal uec-images + Uname: Linux 5.15.0-1015-aws x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 10/16/2017 + dmi.bios.release: 1.0 + dmi.bios.vendor: Amazon EC2 + dmi.bios.version: 1.0 + dmi.board.asset.tag: i-03f5d8581c7ad94aa + dmi.board.vendor: Amazon EC2 + dmi.chassis.asset.tag: Amazon EC2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Amazon EC2 + dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: + dmi.product.name: c5d.12xlarge + dmi.sys.vendor: Amazon EC2 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1987232/+attachment/5610807/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See
[Kernel-packages] [Bug 1986976] Re: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login.
oh sorry I have to rectify. I was probably too fast to report or I did a cold start in the subsequent tests, no more sure. But, now the "flickering" does not happen anyway in any scenari oy logout power off, suspend or restart. Only the restart process is still verbose and shows ACpi Error kind messages (it is viable) so far, will continue to try and report within 24 hours Thanks, anyway -- 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/1986976 Title: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login. Status in linux package in Ubuntu: Incomplete Bug description: I do remember such BIOS related issues back in 2019 for now I do have the list of the kernel error messages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: labdom 3949 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-07-15 (1130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 003: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ea604268-2faf-42c2-abf5-69e0de92b334 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy wayland-session Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-17 (2 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2018 dmi.bios.release: 7.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.12:bd09/06/2018:br7.12:efr7.13:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986976] Re: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login.
What I did according https://wiki.ubuntu.com/Kernel/KernelBootParameters?_ga=2.33092154.52927536.1661185095-1335890214.1657710128 1. under a terminal : sudo gedit /etc/default/grub 2. insert the parameters as on conversation#25 after the word splash + one space 3. save the file 4. sudo update-grub 5. restart The "flickering" still occurs ! -- 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/1986976 Title: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login. Status in linux package in Ubuntu: Incomplete Bug description: I do remember such BIOS related issues back in 2019 for now I do have the list of the kernel error messages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: labdom 3949 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-07-15 (1130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 003: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ea604268-2faf-42c2-abf5-69e0de92b334 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy wayland-session Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-17 (2 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2018 dmi.bios.release: 7.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.12:bd09/06/2018:br7.12:efr7.13:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610795/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610796/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610794/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610797/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610793/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610792/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610789/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610791/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610790/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610786/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610788/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610784/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610785/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610787/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610782/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610783/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610781/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610780/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610779/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy Uname: Linux 5.15.0-46-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: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS 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.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS 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/1987249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987249] Re: Asus ROG Zephyrus GX701L sound problem
apport information ** Tags added: apport-collected jammy ** Description changed: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rakic 1415 F pulseaudio + /dev/snd/controlC1: rakic 1415 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-22 (0 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-46-generic N/A + linux-backports-modules-5.15.0-46-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.4 + Tags: jammy + Uname: Linux 5.15.0-46-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: 04/19/2021 + dmi.bios.release: 5.17 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GX701LWS.310 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: GX701LWS + 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.7 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: + dmi.product.family: ROG Zephyrus S17 + dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1987249/+attachment/5610778/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu
[Kernel-packages] [Bug 1982501] Re: NVIDIA CVE-2022-{31607|31608}
This bug was fixed in the package fabric-manager-470 -
470.141.03-0ubuntu1
---
fabric-manager-470 (470.141.03-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1982501).
-- Alberto Milone Mon, 25 Jul 2022
14:34:20 +
** Changed in: fabric-manager-470 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1982501
Title:
NVIDIA CVE-2022-{31607|31608}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-470 package in Ubuntu:
Fix Released
Status in fabric-manager-510 package in Ubuntu:
Fix Released
Status in fabric-manager-515 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-470 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-510 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
New
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
New
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-470 source package in Bionic:
Fix Released
Status in fabric-manager-510 source package in Bionic:
Fix Released
Status in fabric-manager-515 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-510 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-510-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-470 source package in Focal:
Fix Released
Status in fabric-manager-510 source package in Focal:
Fix Released
Status in fabric-manager-515 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in libnvidia-nscq-470 source package in Focal:
Fix Released
Status in libnvidia-nscq-510 source package in Focal:
Fix Released
Status in libnvidia-nscq-515 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-510 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-510-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Jammy:
Fix Released
Status in fabric-manager-470 source package in Jammy:
Fix Released
Status in fabric-manager-510 source package in Jammy:
Fix Released
Status in fabric-manager-515 source package in Jammy:
Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-510 source package in Jammy:
Fix Released
Status in
[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device failure at resuming from s2idle
Backport-iwlwifi-dkms is also being upgraded to upstream revision 9904 in bug 1987048. -- 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/1987312 Title: IWLMEI may cause device failure at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987312] [NEW] IWLMEI may cause device failure at resuming from s2idle
Public bug reported: Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: backport-iwlwifi-dkms (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: backport-iwlwifi-dkms (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: backport-iwlwifi-dkms (Ubuntu Kinetic) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1986771 somerville ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: backport-iwlwifi-dkms (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy) Status: New => Invalid ** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic) Status: New => In Progress ** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Tags added: oem-priority originate-from-1986771 somerville ** Description changed: - TBD. + Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN + POR is only for Windows project design. Please remove or disable + CONFIG_IWLMEI from Linux. -- 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/1987312 Title: IWLMEI may cause device failure at resuming from s2idle Status in HWE Next: New Status in backport-iwlwifi-dkms package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986724] Re: Jammy update: v5.15.52 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986724 Title: Jammy update: v5.15.52 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.52 upstream stable release from git://git.kernel.org/ tick/nohz: unexport __init-annotated tick_nohz_full_setup() xfs: use kmem_cache_free() for kmem_cache objects xfs: punch out data fork delalloc blocks on COW writeback failure xfs: Fix the free logic of state in xfs_attr_node_hasname xfs: remove all COW fork extents when remounting readonly xfs: check sb_meta_uuid for dabuf buffer recovery xfs: prevent UAF in xfs_log_item_in_current_chkpt xfs: only bother with sync_filesystem during readonly remount powerpc/ftrace: Remove ftrace init tramp once kernel init is complete fs: add is_idmapped_mnt() helper fs: move mapping helpers fs: tweak fsuidgid_has_mapping() fs: account for filesystem mappings docs: update mapping documentation fs: use low-level mapping helpers fs: remove unused low-level mapping helpers fs: port higher-level mapping helpers fs: add i_user_ns() helper fs: support mapped mounts of mapped filesystems fs: fix acl translation fs: account for group membership rtw88: 8821c: support RFE type4 wifi NIC rtw88: rtw8821c: enable rfe 6 devices net: mscc: ocelot: allow unregistered IP multicast flooding to CPU io_uring: fix not locked access to fixed buf table Linux 5.15.52 UBUNTU: Upstream stable to v5.15.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986728] Re: Jammy update: v5.15.53 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986728 Title: Jammy update: v5.15.53 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.53 upstream stable release from git://git.kernel.org/ Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" drm/amdgpu: To flush tlb for MMHUB of RAVEN series ksmbd: set the range of bytes to zero without extending file size in FSCTL_ZERO_DATA ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA ksmbd: use vfs_llseek instead of dereferencing NULL ipv6: take care of disable_policy when restoring routes net: phy: Don't trigger state machine while in suspend nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX S40G) nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 nvdimm: Fix badblocks clear off-by-one error powerpc/prom_init: Fix kernel config grep powerpc/book3e: Fix PUD allocation size in map_kernel_page() powerpc/bpf: Fix use of user_pt_regs in uapi dm raid: fix accesses beyond end of raid member array dm raid: fix KASAN warning in raid5_add_disks s390/archrandom: simplify back to earlier design and initialize earlier SUNRPC: Fix READ_PLUS crasher net: rose: fix UAF bugs caused by timer handler net: usb: ax88179_178a: Fix packet receiving virtio-net: fix race between ndo_open() and virtio_device_ready() selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test net: dsa: bcm_sf2: force pause link settings net: tun: unlink NAPI from device on destruction net: tun: stop NAPI when detaching queues net: dp83822: disable false carrier interrupt net: dp83822: disable rx error interrupt RDMA/qedr: Fix reporting QP timeout attribute RDMA/cm: Fix memory leak in ib_cm_insert_listen linux/dim: Fix divide by 0 in RDMA DIM net: usb: asix: do not force pause frames support usbnet: fix memory allocation in helpers selftests: mptcp: more stable diag tests net: ipv6: unexport __init-annotated seg6_hmac_net_init() NFSD: restore EINVAL error translation in nfsd_commit() vfs: fix copy_file_range() regression in cross-fs copies caif_virtio: fix race between virtio_device_ready() and ndo_open() PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events vdpa/mlx5: Update Control VQ callback information s390: remove unneeded 'select BUILD_BIN2C' netfilter: nft_dynset: restore set element counter when failing to update net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup() net/sched: act_api: Notify user space if any actions were flushed before error net: asix: fix "can't send until first packet is send" issue net: bonding: fix possible NULL deref in rlb code net: phy: ax88772a: fix lost pause advertisement configuration net: bonding: fix use-after-free after 802.3ad slave unbind powerpc/memhotplug: Add add_pages override for PPC nfc: nfcmrvl: Fix irq_of_parse_and_map() return value NFC: nxp-nci: Don't issue a zero length i2c_master_read() tipc: move bc link creation back to tipc_node_create epic100: fix use after free on rmmod io_uring: ensure that send/sendmsg and recv/recvmsg check sqe->ioprio ACPI: video: Change how we determine if brightness key-presses are handled tunnels: do not assume mac header is set in skb_tunnel_check_pmtu() ipv6/sit: fix ipip6_tunnel_get_prl return value ipv6: fix lockdep splat in in6_dump_addrs() mlxsw: spectrum_router: Fix rollback in tunnel next hop init net: tun: avoid disabling NAPI twice MAINTAINERS: add Leah as xfs maintainer for 5.15.y tcp: add a missing nf_reset_ct() in 3WHS handling selftests/bpf: Add test_verifier support to fixup kfunc call insns selftests/rseq: remove ARRAY_SIZE define from individual tests selftests/rseq: introduce own copy of rseq uapi header selftests/rseq: Remove useless assignment to cpu variable selftests/rseq: Remove volatile from __rseq_abi selftests/rseq: Introduce rseq_get_abi() helper selftests/rseq: Introduce thread pointer getters selftests/rseq: Uplift rseq selftests for compatibility with glibc-2.35 selftests/rseq: Fix ppc32: wrong rseq_cs 32-bit field pointer on big endian selftests/rseq: Fix ppc32 missing instruction selection "u" and
[Kernel-packages] [Bug 1987294] Re: azure-5.15: Remove circular dependency on linux-modules and linux-image
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux-azure-5.15 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1987294 Title: azure-5.15: Remove circular dependency on linux-modules and linux- image Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.15 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.15 source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-5.15 source package in Jammy: Invalid Status in linux-azure source package in Kinetic: Fix Committed Status in linux-azure-5.15 source package in Kinetic: Invalid Bug description: SRU Justification [Impact] linux-image-azure-5.15 currently has a dependency on linux-modules- azure-5.15. Similarly, linux-modules-azure-5.15 depends on linux- image-azure-515. This circular dependency is unnecessary since the meta packages quite effectively manage those relationships. Furthermore, this dependency breaks the construction of FDE-5.15 packages by pulling in unwanted dependencies during FDE image creation. [Where things could go wrong] Installations where this dependency is assumed could stop working. This is unlikely since all cloud images start from correctly installed meta packages. This circular dependency is also new with 5.15 packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986718] Re: Jammy update: v5.15.51 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986718 Title: Jammy update: v5.15.51 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.51 upstream stable release from git://git.kernel.org/ random: schedule mix_interrupt_randomness() less often random: quiet urandom warning ratelimit suppression message ALSA: hda/via: Fix missing beep setup ALSA: hda/conexant: Fix missing beep setup ALSA: hda/realtek: Add mute LED quirk for HP Omen laptop ALSA: hda/realtek: Apply fixup for Lenovo Yoga Duet 7 properly ALSA: hda/realtek: Add quirk for Clevo PD70PNT ALSA: hda/realtek: Add quirk for Clevo NS50PU net: openvswitch: fix parsing of nw_proto for IPv6 fragments 9p: Fix refcounting during full path walks for fid lookups 9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl 9p: fix fid refcount leak in v9fs_vfs_get_link btrfs: fix hang during unmount when block group reclaim task is running btrfs: prevent remounting to v1 space cache for subpage mount btrfs: add error messages to all unrecognized mount options scsi: ibmvfc: Store vhost pointer during subcrq allocation scsi: ibmvfc: Allocate/free queue resource only during probe/remove mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing mmc: mediatek: wait dma stop bit reset to 0 xen/gntdev: Avoid blocking in unmap_grant_pages() MAINTAINERS: Add new IOMMU development mailing list ata: libata: add qc->flags in ata_qc_complete_template tracepoint dm era: commit metadata in postsuspend after worker stops dm mirror log: clear log bits up to BITS_PER_LONG boundary tracing/kprobes: Check whether get_kretprobe() returns NULL in kretprobe_dispatcher() drm/i915: Implement w/a 22010492432 for adl-s USB: serial: pl2303: add support for more HXN (G) types USB: serial: option: add Telit LE910Cx 0x1250 composition USB: serial: option: add Quectel EM05-G modem USB: serial: option: add Quectel RM500K module support drm/msm: Ensure mmap offset is initialized drm/msm: Fix double pm_runtime_disable() call netfilter: use get_random_u32 instead of prandom scsi: scsi_debug: Fix zone transition to full condition drm/msm: Switch ordering of runpm put vs devfreq_idle scsi: iscsi: Exclude zero from the endpoint ID range xsk: Fix generic transmit when completion queue reservation fails drm/msm: use for_each_sgtable_sg to iterate over scatterlist bpf: Fix request_sock leak in sk lookup helpers drm/sun4i: Fix crash during suspend after component bind failure bpf, x86: Fix tail call count offset calculation on bpf2bpf call scsi: storvsc: Correct reporting of Hyper-V I/O size limits phy: aquantia: Fix AN when higher speeds than 1G are not advertised KVM: arm64: Prevent kmemleak from accessing pKVM memory net: Write lock dev_base_lock without disabling bottom halves. net: fix data-race in dev_isalive() tipc: fix use-after-free Read in tipc_named_reinit igb: fix a use-after-free issue in igb_clean_tx_ring bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers ethtool: Fix get module eeprom fallback net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf drm/msm/dp: check core_initialized before disable interrupts at dp_display_unbind() drm/msm/dp: Drop now unused hpd_high member drm/msm/dp: dp_link_parse_sink_count() return immediately if aux read failed drm/msm/dp: do not initialize phy until plugin interrupt received drm/msm/dp: force link training for display resolution change perf arm-spe: Don't set data source if it's not a memory operation erspan: do not assume transport header is always set net/tls: fix tls_sk_proto_close executed repeatedly udmabuf: add back sanity check selftests: netfilter: correct PKTGEN_SCRIPT_PATHS in nft_concat_range.sh xen-blkfront: Handle NULL gendisk x86/xen: Remove undefined behavior in setup_features() MIPS: Remove repetitive increase irq_err_count afs: Fix dynamic root getattr ice: ethtool: advertise 1000M speeds properly regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips regmap-irq: Fix offset/index mismatch in read_sub_irq_data() virtio_net: fix
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
Yes, if it get it incl. in the focal 5.4 (GA), it will automatically find it's way into the bionic hwe-5.4 as well. -- 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/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ffbrc 8,3bfa682a 3bfa6630: c004004bbrcl 0,3bfa66c6 [ 659.104261] Call Trace: [ 659.104263] ([<>] 0x0) [ 659.104265] [<3bfa6aa2>] queue_work_on+0x62/0x70 [ 659.104329] [<03ff80a2920a>] cmd_exec+0x4ea/0x840 [mlx5_core] [ 659.104349] [<03ff80a29680>] mlx5_cmd_exec+0x40/0x70 [mlx5_core] [ 659.104369] [<03ff80a334a8>] mlx5_core_access_reg+0x108/0x150 [mlx5_core] [ 659.104387] [<03ff80a3354e>] mlx5_query_port_ptys+0x5e/0x70 [mlx5_core] [ 659.104407] [<03ff80a5b928>]
[Kernel-packages] [Bug 1983149] Re: Jammy update: v5.15.49 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983149 Title: Jammy update: v5.15.49 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.49 upstream stable release from git://git.kernel.org/ Revert "drm/amd/display: Fix DCN3 B0 DP Alt Mapping" nfsd: Replace use of rwsem with errseq_t arm64: dts: imx8mm-beacon: Enable RTS-CTS on UART3 arm64: dts: imx8mn-beacon: Enable RTS-CTS on UART3 powerpc/kasan: Silence KASAN warnings in __get_wchan() ASoC: nau8822: Add operation for internal PLL off and on drm/amd/display: Read Golden Settings Table from VBIOS drm/amdkfd: Use mmget_not_zero in MMU notifier dma-debug: make things less spammy under memory pressure ASoC: cs42l52: Fix TLV scales for mixer controls ASoC: cs35l36: Update digital volume TLV ASoC: cs53l30: Correct number of volume levels on SX controls ASoC: cs42l52: Correct TLV for Bypass Volume ASoC: cs42l56: Correct typo in minimum level for SX volume controls ASoC: cs42l51: Correct minimum value for SX volume control drm/amdkfd: add pinned BOs to kfd_bo_list ata: libata-core: fix NULL pointer deref in ata_host_alloc_pinfo() quota: Prevent memory allocation recursion while holding dq_lock ASoC: wm8962: Fix suspend while playing music ASoC: es8328: Fix event generation for deemphasis control ASoC: wm_adsp: Fix event generation for wm_adsp_fw_put() Input: soc_button_array - also add Lenovo Yoga Tablet2 1051F to dmi_use_low_level_irq scsi: vmw_pvscsi: Expand vcpuHint to 16 bits scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion scsi: mpt3sas: Fix out-of-bounds compiler warning scsi: ipr: Fix missing/incorrect resource cleanup in error case scsi: pmcraid: Fix missing resource cleanup in error case ALSA: hda/realtek - Add HW8326 support virtio-mmio: fix missing put_device() when vm_cmdline_parent registration failed nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg net: ethernet: mtk_eth_soc: fix misuse of mem alloc interface netdev[napi]_alloc_frag gcc-12: disable '-Wdangling-pointer' warning for now mellanox: mlx5: avoid uninitialized variable warning with gcc-12 MIPS: Loongson-3: fix compile mips cpu_hwmon as module build error. random: credit cpu and bootloader seeds by default gpio: dwapb: Don't print error on -EPROBE_DEFER platform/x86: gigabyte-wmi: Add Z690M AORUS ELITE AX DDR4 support platform/x86: gigabyte-wmi: Add support for B450M DS3H-CF platform/x86/intel: hid: Add Surface Go to VGBS allow list staging: r8188eu: fix rtw_alloc_hwxmits error detection for now staging: r8188eu: Use zeroing allocator in wpa_set_encryption() staging: r8188eu: Fix warning of array overflow in ioctl_linux.c pNFS: Don't keep retrying if the server replied NFS4ERR_LAYOUTUNAVAILABLE pNFS: Avoid a live lock condition in pnfs_update_layout() sunrpc: set cl_max_connect when cloning an rpc_clnt clocksource: hyper-v: unexport __init-annotated hv_init_clocksource() i40e: Fix adding ADQ filter to TC0 i40e: Fix calculating the number of queue pairs i40e: Fix call trace in setup_tx_descriptors Drivers: hv: vmbus: Release cpu lock in error case tty: goldfish: Fix free_irq() on remove misc: atmel-ssc: Fix IRQ check in ssc_probe io_uring: fix races with file table unregister io_uring: fix races with buffer table unregister drm/i915/reset: Fix error_state_read ptr + offset use net: hns3: split function hclge_update_port_base_vlan_cfg() net: hns3: set port base vlan tbl_sta to false before removing old vlan net: hns3: don't push link state to VF if unalive net: hns3: fix tm port shapping of fibre port is incorrect after driver initialization nvme: add device name to warning in uuid_show() mlxsw: spectrum_cnt: Reorder counter pools net: bgmac: Fix an erroneous kfree() in bgmac_remove() net: ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg arm64: ftrace: fix branch range checks arm64: ftrace: consistently handle PLTs. certs/blacklist_hashes.c: fix
[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
After removing i350 OCP, the errors disappears in the syslog. I also found there is this message "Unknown small resource type 06, will not decode more." when using "lspci -vvv" as comment 12# "Lspci.txt" It looks like intel i350 OCP related issue. Any idea? -- 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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-18 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220816) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894 Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Lenovo ThinkEdge SE450 Package: linux (not installed) ProcCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/ubuntu--vg--1-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/08/2022 dmi.bios.release: 1.23 dmi.bios.vendor: Lenovo dmi.bios.version: CME105F-1.23 dmi.board.asset.tag: none dmi.board.name: 7D8TCTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.40 dmi.modalias:
[Kernel-packages] [Bug 1986715] Re: Jammy update: v5.15.50 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986715 Title: Jammy update: v5.15.50 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.50 upstream stable release from git://git.kernel.org/ net: mana: Add handling of CQE_RX_TRUNCATED zonefs: fix zonefs_iomap_begin() for reads usb: gadget: u_ether: fix regression in setting fixed MAC address bpf: Fix calling global functions from BPF_PROG_TYPE_EXT programs selftests/bpf: Add selftest for calling global functions from freplace serial: core: Initialize rs485 RTS polarity already on probe arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer Linux 5.15.50 UBUNTU: Upstream stable to v5.15.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983146] Re: Jammy update: v5.15.48 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983146 Title: Jammy update: v5.15.48 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.48 upstream stable release from git://git.kernel.org/ Note: Every commit from v5.15.48 had already been applied. Linux 5.15.48 UBUNTU: Upstream stable to v5.15.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-08-22 11:48 EDT--- @Canonical: As the problem occurred in the Cloud environment running on a 18.04 HWE kernel, we need to make sure that the fix will also be included there. With adding to focal, will the patch land in 18.04 HWE kernel as well or do we need to open an additional separate bug / launchpad entry for the 18.04 HWE kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ffbrc 8,3bfa682a 3bfa6630: c004004bbrcl 0,3bfa66c6 [ 659.104261] Call Trace: [ 659.104263] ([<>] 0x0) [ 659.104265] [<3bfa6aa2>] queue_work_on+0x62/0x70 [ 659.104329] [<03ff80a2920a>] cmd_exec+0x4ea/0x840 [mlx5_core] [ 659.104349]
[Kernel-packages] [Bug 1982968] Re: Jammy update: v5.15.47 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982968 Title: Jammy update: v5.15.47 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.47 upstream stable release from git://git.kernel.org/ pcmcia: db1xxx_ss: restrict to MIPS_DB1XXX boards staging: greybus: codecs: fix type confusion of list iterator variable iio: adc: ad7124: Remove shift from scan_type lkdtm/bugs: Check for the NULL pointer after calling kmalloc lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP tty: goldfish: Use tty_port_destroy() to destroy port tty: serial: owl: Fix missing clk_disable_unprepare() in owl_uart_probe tty: n_tty: Restore EOF push handling behavior serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe tty: serial: fsl_lpuart: fix potential bug when using both of_alias_get_id and ida_simple_get remoteproc: imx_rproc: Ignore create mem entry for resource table usb: usbip: fix a refcount leak in stub_probe() usb: usbip: add missing device lock on tweak configuration cmd USB: storage: karma: fix rio_karma_init return usb: musb: Fix missing of_node_put() in omap2430_probe staging: fieldbus: Fix the error handling path in anybuss_host_common_probe() pwm: lp3943: Fix duty calculation in case period was clamped pwm: raspberrypi-poe: Fix endianness in firmware struct rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback usb: dwc3: pci: Fix pm_runtime_get_sync() error checking misc: fastrpc: fix an incorrect NULL check on list iterator firmware: stratix10-svc: fix a missing check on list iterator usb: typec: mux: Check dev_set_name() return value rpmsg: virtio: Fix possible double free in rpmsg_probe() rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev() rpmsg: virtio: Fix the unregistration of the device rpmsg_ctrl iio: adc: stmpe-adc: Fix wait_for_completion_timeout return value check iio: proximity: vl53l0x: Fix return value check of wait_for_completion_timeout iio: adc: sc27xx: fix read big scale voltage not right iio: adc: sc27xx: Fine tune the scale calibration values rpmsg: qcom_smd: Fix returning 0 if irq_of_parse_and_map() fails pvpanic: Fix typos in the comments misc/pvpanic: Convert regular spinlock into trylock on panic path phy: qcom-qmp: fix pipe-clock imbalance on power-on failure power: supply: axp288_fuel_gauge: Drop BIOS version check from "T3 MRD" DMI quirk serial: sifive: Report actual baud base rather than fixed 115200 export: fix string handling of namespace in EXPORT_SYMBOL_NS soundwire: intel: prevent pm_runtime resume prior to system suspend coresight: cpu-debug: Replace mutex with mutex_trylock on panic notifier ksmbd: fix reference count leak in smb_check_perm_dacl() extcon: ptn5150: Add queue work sync before driver release soc: rockchip: Fix refcount leak in rockchip_grf_init clocksource/drivers/riscv: Events are stopped during CPU suspend ARM: dts: aspeed: ast2600-evb: Enable RX delay for MAC0/MAC1 rtc: mt6397: check return value after calling platform_get_resource() rtc: ftrtc010: Use platform_get_irq() to get the interrupt rtc: ftrtc010: Fix error handling in ftrtc010_rtc_probe staging: r8188eu: add check for kzalloc tty: n_gsm: Don't ignore write return value in gsmld_output() tty: n_gsm: Fix packet data hex dump output serial: meson: acquire port->lock in startup() serial: 8250_fintek: Check SER_RS485_RTS_* only with RS485 serial: cpm_uart: Fix build error without CONFIG_SERIAL_CPM_CONSOLE serial: digicolor-usart: Don't allow CS5-6 serial: rda-uart: Don't allow CS5-6 serial: txx9: Don't allow CS5-6 serial: sh-sci: Don't allow CS5-6 serial: sifive: Sanitize CSIZE and c_iflag serial: st-asc: Sanitize CSIZE and correct PARENB for CS7 serial: stm32-usart: Correct CSIZE, bits, and parity firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle bus: ti-sysc: Fix warnings for unbind for serial driver: base: fix UAF when driver_attach failed driver core: fix deadlock in __device_attach watchdog: rti-wdt: Fix pm_runtime_get_sync() error checking watchdog: ts4800_wdt:
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
Juerg, yes. The Breaks line of comment 15 used the most recently available version (<< 20220711.gitdfa29317-0~). -- 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/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Committed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
** Changed in: linux-firmware (Ubuntu Jammy) Status: Incomplete => Triaged ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Triaged Bug description: Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984004] Re: Linux Firmware drops AMD RX6650 XT Performance
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1984004 Title: Linux Firmware drops AMD RX6650 XT Performance Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: Kernel: 5.15.0-43-generic linux-firmware: 20220329.git681281e4-0ubuntu3.3 Tested with: Mint 21 Cinnamon (Ubuntu 22.04 based) In e.g. the Unigine benchmark, the linux-firmware packages drops the performance of my AMD RX 6650 XT GPU from 98 FPS in 1080p-high down to 23 FPS. That wasn't a problem in Mint 20.3 with kernel 5.15 (Ubuntu 20.04 based). Getting the firmware directly from git brings the performance back to about 100 FPS: git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git cd linux-firmware sudo make install sudo update-initramfs -c -k all Re-installing the linux-firmware package causes the performance to drop again. So there is a problem with the linux firmware at least for the RX 6650 XT, maybe for the whole RX 6000 series. The linux-firmware package in Ubuntu 22.04 should be updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daelach1352 F pulseaudio /dev/snd/controlC0: daelach1352 F pulseaudio /dev/snd/controlC1: daelach1352 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Dependencies: firmware-sof-signed 2.0-1ubuntu3 [origin: Ubuntu] DistroRelease: Linux Mint 21 InstallationDate: Installed on 2020-08-24 (714 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=UUID=a4b18dd9-4989-4bf5-8107-e55b8f8f6df4 ro amd_iommu=on iommu=pt quiet loglevel=3 splash ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: Tags: vanessa third-party-packages Uname: Linux 5.15.0-43-generic x86_64 UnreportableReason: This does not seem to be an official Linux package. Please retry after updating the indexes of available packages. If that does not work, then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4901:bd07/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1984004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this type of change had an interesting discussion
about the implementation approach a few years ago [1], but it
seems it ceased as the sender didn't provide further replies.
Your understanding of the tech details seems very deep, so it
might hopefully be a good opportunity to propose that again :)
Thanks!
[1] https://lists.gnu.org/archive/html/grub-devel/2017-03/msg00032.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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
[Kernel-packages] [Bug 1982501] Re: NVIDIA CVE-2022-{31607|31608}
This bug was fixed in the package libnvidia-nscq-470 -
470.141.03-0ubuntu1
---
libnvidia-nscq-470 (470.141.03-0ubuntu1) kinetic; urgency=medium
* New upstream release (LP: #1982501).
-- Alberto Milone Mon, 25 Jul 2022
14:54:45 +
** Changed in: libnvidia-nscq-470 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1982501
Title:
NVIDIA CVE-2022-{31607|31608}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-510 package in Ubuntu:
Fix Released
Status in fabric-manager-515 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-470 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-510 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
New
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
New
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-515 package in Ubuntu:
New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-470 source package in Bionic:
Fix Released
Status in fabric-manager-510 source package in Bionic:
Fix Released
Status in fabric-manager-515 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
Fix Released
Status in libnvidia-nscq-510 source package in Bionic:
Fix Released
Status in libnvidia-nscq-515 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-510 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-510-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-515-server source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-470 source package in Focal:
Fix Released
Status in fabric-manager-510 source package in Focal:
Fix Released
Status in fabric-manager-515 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in libnvidia-nscq-470 source package in Focal:
Fix Released
Status in libnvidia-nscq-510 source package in Focal:
Fix Released
Status in libnvidia-nscq-515 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-510 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-510-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-515-server source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Jammy:
Fix Released
Status in fabric-manager-470 source package in Jammy:
Fix Released
Status in fabric-manager-510 source package in Jammy:
Fix Released
Status in fabric-manager-515 source package in Jammy:
Fix Released
Status in libnvidia-nscq-450 source package in Jammy:
Fix Released
Status in libnvidia-nscq-470 source package in Jammy:
Fix Released
Status in libnvidia-nscq-510 source package in Jammy:
Fix Released
Status in libnvidia-nscq-515 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-390 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-470 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-470-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-510 source package in Jammy:
Fix Released
Status in
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Also, could there be a bios parameter that could be changed to help 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Incomplete Status in linux package in Ubuntu: Won't Fix Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hey Sujith, so far no real update from nVidia other than the fact that not just the GPUs were having issues: Jun 21 06:14:47 R750XAS kernel: [ 59.183873] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active) Jun 21 06:14:47 R750XAS kernel: [ 59.183896] pnp 00:01: disabling [mem 0xff00-0x] because it overlaps :17:00.0 BAR 8 [mem 0x-0x13 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 59.334512] pnp 00:01: disabling [mem 0xff00-0x disabled] because it overlaps :65:00.0 BAR 8 [mem 0x-0x13 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 59.494432] pnp 00:01: disabling [mem 0xff00-0x disabled] because it overlaps :ca:00.0 BAR 8 [mem 0x-0x13 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 59.654396] pnp 00:01: disabling [mem 0xff00-0x disabled] because it overlaps :e3:00.0 BAR 8 [mem 0x-0x13 64bit pref] COuld this be something firmware related going on? -- 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Incomplete Status in linux package in Ubuntu: Won't Fix Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
The patch mentioned is upstream since kernel v5.7-rc7, hence it's only needed for focal (already incl. in jammy and kinetic). ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) -- 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/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ff
[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32
Hey Heitor! Thank you for following up on Robie's questions. As this is a bug in the current upstream versions of zfs-linux + currently LTS upgrades to jammy are enabled, I'm starting to lean towards getting this accepted into focal-proposed. Out of curiosity, what is the situation on bionic btw.? What is the behavior there? Too bad there's simply no way of knowing how many people would be potentially affected by the inversion of the behavior. Did we see any reports of this being a problem on jammy, after we switched upgrades from focal? The thing is that, potentially, some might want to stay of focal to not have to deal with incompatibilities like that after upgrades. So we need to be considerate of such people. Although I do agree the reducing of ZFS memory footprint being much more common. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Incomplete Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981526] Re: i915 drivers unstable with i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3135 end=3136) t
Why are you uncomfortable running an OEM kernel? It's the kernel that is certified for that particular HW so should support all the laptop specific gimmicks. You are free to install whatever you want but don't expect everything to work smoothly with a non-certified kernel. By now you should be running a 5.15 kernel, I think. Does your problem still exist? ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- 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/1981526 Title: i915 drivers unstable with i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3135 end=3136) t Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: There are ocasional flickerings with i915 drivers, the dmesg discovered one of possible reasons on Dell XPS13 9310: [10103.828209] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3135 end=3136) time 2743 us, min 2385, max 2399, scanline start 2131, end 68 I'm eager to debug it further if needed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nusch 16067 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 08:06:54 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2015-05-08 (2622 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1057-oem root=/dev/mapper/ubuntu--vg-root ro intel_idle.max_cstate=4 i915.enable_psr=0 i915.reset=2 tsc=unstable quiet splash crashkernel=512M-:192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1057-oem N/A linux-backports-modules-5.10.0-1057-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2022 dmi.bios.release: 3.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.7.0 dmi.board.name: 0DXP1F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.7.0:bd05/09/2022:br3.7:svnDellInc.:pnXPS139310:pvr:sku0991:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1981526/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987294] Re: azure-5.15: Remove circular dependency on linux-modules and linux-image
** Also affects: linux-azure-5.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure-5.15 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure-5.15 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure-5.15 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure-5.15 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-azure-5.15 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-azure (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1987294 Title: azure-5.15: Remove circular dependency on linux-modules and linux- image Status in linux-azure package in Ubuntu: In Progress Status in linux-azure-5.15 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.15 source package in Focal: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure-5.15 source package in Jammy: Invalid Status in linux-azure source package in Kinetic: In Progress Status in linux-azure-5.15 source package in Kinetic: Invalid Bug description: SRU Justification [Impact] linux-image-azure-5.15 currently has a dependency on linux-modules- azure-5.15. Similarly, linux-modules-azure-5.15 depends on linux- image-azure-515. This circular dependency is unnecessary since the meta packages quite effectively manage those relationships. Furthermore, this dependency breaks the construction of FDE-5.15 packages by pulling in unwanted dependencies during FDE image creation. [Where things could go wrong] Installations where this dependency is assumed could stop working. This is unlikely since all cloud images start from correctly installed meta packages. This circular dependency is also new with 5.15 packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
# JAMMY - proposed testing # enable proposed repo cat /proc/sysrq-trigger cd /var/crash -rw-r- 1 root root 18552 Aug 22 13:32 linux- image-5.15.0-1014-azure-202208221332.crash ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-jammy ** Tags added: verification-done-bionic verification-done-focal verification-done-jammy -- 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: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed 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: Fix Committed 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 Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a 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 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties
[Kernel-packages] [Bug 1987294] [NEW] azure-5.15: Remove circular dependency on linux-modules and linux-image
Public bug reported: SRU Justification [Impact] linux-image-azure-5.15 currently has a dependency on linux-modules- azure-5.15. Similarly, linux-modules-azure-5.15 depends on linux-image- azure-515. This circular dependency is unnecessary since the meta packages quite effectively manage those relationships. Furthermore, this dependency breaks the construction of FDE-5.15 packages by pulling in unwanted dependencies during FDE image creation. [Where things could go wrong] Installations where this dependency is assumed could stop working. This is unlikely since all cloud images start from correctly installed meta packages. This circular dependency is also new with 5.15 packages. ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Kinetic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Summary changed: - azure: Remove circular dependency on linux-modules and linux-image + azure-5.15: Remove circular dependency on linux-modules and linux-image ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1987294 Title: azure-5.15: Remove circular dependency on linux-modules and linux- image Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Bug description: SRU Justification [Impact] linux-image-azure-5.15 currently has a dependency on linux-modules- azure-5.15. Similarly, linux-modules-azure-5.15 depends on linux- image-azure-515. This circular dependency is unnecessary since the meta packages quite effectively manage those relationships. Furthermore, this dependency breaks the construction of FDE-5.15 packages by pulling in unwanted dependencies during FDE image creation. [Where things could go wrong] Installations where this dependency is assumed could stop working. This is unlikely since all cloud images start from correctly installed meta packages. This circular dependency is also new with 5.15 packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel"
Found this on Jammy 5.15.0-47.51 with node howzit-kernel. ** Tags added: sru-20220808 -- 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/1973153 Title: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel" Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu and Jammy 5.15.0-27-generic with ARM64 node helo-kernel only. It looks like this is hardware-specific. The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and test will timeout. Steps to reproduce this: git clone -b sru git://git.launchpad.net/~canonical-kernel-team/+git/ltp cd ltp make autotools ./configure make sudo make install echo "read_all_sys read_all -d /sys -q -r 3" > /tmp/fs sudo /opt/ltp/runltp -f /tmp/fs Test log: <<>> tag=read_all_sys stime=1652343855 cmdline="read_all -d /sys -q -r 3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1456: TINFO: Timeout per run is 0h 30m 00s Test timeouted, sending SIGKILL! tst_test.c:1500: TINFO: Killed the leftover descendant processes tst_test.c:1506: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1508: TBROK: Test killed! (timeout?) Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1800 termination_type=exited termination_id=2 corefile=no cutime=39 cstime=140 <<>> dmesg output: [ 1614.203083] LTP: starting read_all_sys (read_all -d /sys -q -r 3) [ 1617.509566] mpt3sas :8d:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 1617.543837] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550373] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550381] mpt3sas_cm0: host_trace_buffer_size_show: host_trace_buffer is not registered [ 1617.550474] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550504] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.550593] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.550622] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.598371] mpt3sas_cm0: host_trace_buffer_show: host_trace_buffer is not registered [ 1617.606183] mpt3sas_cm0: BRM_status_show: BRM attribute is only for warpdrive [ 1617.641990] mpt3sas :8d:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update [ 1617.973894] WARNING! power/level is deprecated; use power/control instead [ 1619.368112] bdi 7:6: the stable_pages_required attribute has been removed. Use the stable_writes queue attribute instead. [ 1627.430319] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.438256] Mem abort info: [ 1627.441086] ESR = 0x9621 [ 1627.444133] EC = 0x25: DABT (current EL), IL = 32 bits [ 1627.449469] SET = 0, FnV = 0 [ 1627.452515] EA = 0, S1PTW = 0 [ 1627.455676] FSC = 0x21: alignment fault [ 1627.459701] Data abort info: [ 1627.462597] ISV = 0, ISS = 0x0021 [ 1627.466449] CM = 0, WnR = 0 [ 1627.469434] swapper pgtable: 4k pages, 48-bit VAs, pgdp=f4aba000 [ 1627.476160] [800033b503bf] pgd=10bffcfff003, p4d=10bffcfff003, pud=10bffcffe003, pmd=1008948f5003, pte=006880213f0f [ 1627.488712] Internal error: Oops: 9621 [#1] SMP [ 1627.493585] Modules linked in: efi_pstore nls_iso8859_1 joydev input_leds acpi_ipmi ipmi_ssif thunderx2_pmu cppc_cpufreq sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid uas hid usb_storage ast drm_vram_helper drm_ttm_helper i2c_smbus ttm i2c_algo_bit drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 rc_core sha1_ce qede mpt3sas qed raid_class drm scsi_transport_sas xhci_pci ahci xhci_pci_renesas gpio_xlp i2c_xlp9xx aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 1627.500861] Unable to handle kernel paging request at virtual address 800033b503bf [ 1627.562614] CPU: 71 PID: 4190 Comm: read_all Not tainted 5.17.0-8-generic #8~22.04.2-Ubuntu [ 1627.562623] Hardware name: To be filled by O.E.M. Saber/Saber, BIOS 0ACKL030 06/04/2020 [ 1627.562626] pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT
[Kernel-packages] [Bug 1987287] Backport of upstream commit to 5.4.0-124.140
Default Comment by Bridge ** Attachment added: "Backport of upstream commit to 5.4.0-124.140" https://bugs.launchpad.net/bugs/1987287/+attachment/5610710/+files/0001-net-mlx5-Avoid-processing-commands-before-cmdif-is-r.patch ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in linux package in Ubuntu: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ffbrc 8,3bfa682a 3bfa6630: c004004bbrcl 0,3bfa66c6 [ 659.104261] Call Trace: [ 659.104263] ([<>] 0x0) [ 659.104265] [<3bfa6aa2>] queue_work_on+0x62/0x70 [ 659.104329] [<03ff80a2920a>] cmd_exec+0x4ea/0x840 [mlx5_core] [ 659.104349] [<03ff80a29680>] mlx5_cmd_exec+0x40/0x70 [mlx5_core] [ 659.104369] [<03ff80a334a8>]
[Kernel-packages] [Bug 1987287] [NEW] [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
You have been subscribed to a public bug: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ffbrc 8,3bfa682a 3bfa6630: c004004bbrcl 0,3bfa66c6 [ 659.104261] Call Trace: [ 659.104263] ([<>] 0x0) [ 659.104265] [<3bfa6aa2>] queue_work_on+0x62/0x70 [ 659.104329] [<03ff80a2920a>] cmd_exec+0x4ea/0x840 [mlx5_core] [ 659.104349] [<03ff80a29680>] mlx5_cmd_exec+0x40/0x70 [mlx5_core] [ 659.104369] [<03ff80a334a8>] mlx5_core_access_reg+0x108/0x150 [mlx5_core] [ 659.104387] [<03ff80a3354e>] mlx5_query_port_ptys+0x5e/0x70 [mlx5_core] [ 659.104407] [<03ff80a5b928>] mlx5e_ethtool_get_link_ksettings+0x58/0x460 [mlx5_core] [ 659.104410] [<3c662a68>] duplex_show+0x78/0xe0 [ 659.104414] [<3c538ecc>] dev_attr_show+0x2c/0x70 [ 659.104417] [<3c293386>] sysfs_kf_seq_show+0xa6/0x150 [ 659.104420] [<3c207470>] seq_read+0xe0/0x4f0 [ 659.104422] [<3c1d4cf4>] vfs_read+0x94/0x160 [ 659.104423] [<3c1d4ea8>] ksys_read+0x68/0x100 [ 659.104426] [<3c7f2034>] system_call+0xd8/0x2c8 [ 659.104427] Last Breaking-Event-Address: [ 659.104428] [<3bfa65d6>] __queue_work+0xb6/0x520 [ 659.104430] ---[ end trace
[Kernel-packages] [Bug 1983193] Re: Internet connectivity through AR8131 Gigabit Ethernet breaks
So am I correct then this wasn't even worth a look to see if there was any code that might have changed that could have caused this? If so, I really disagree with the approach of just changing the status, and certainly with no communication, from a quality standpoint. If you all truly don't wish to know when something breaks after a package update, fine, won't spend time reporting things. The thing is, the Ubuntu documentation is full of preachy admonitions to get involved, let us know when there is a problem, showing humanity to one another, blah blah blah. (And no, I'm not a new user even though the profile is new, not looking for a place to get "technical support", I had a previous launchpad account that I deleted, try to guess why). -- 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/1983193 Title: Internet connectivity through AR8131 Gigabit Ethernet breaks Status in linux-firmware package in Ubuntu: Invalid Bug description: 20220329.git681281e4-0ubuntu3.3 (later referenced as *3) for linux- firmware breaks internet connectivity/there is no internet connectivity through AR8131 Gigabit Ethernet interface. Using the installed package prior to this update, 20220329.git681281e4-0ubuntu1 (later referenced as *1), does not cause an issue. Ubuntu release: 22.04 When I installed *3, rebooted the next day and internet was no longer available. Checked with the the internet service provider, and connected the ethernet cable to a separate matchine and had connectivity. A boot with live Ubuntu 22.04 USB showed no connectivity issues (which I assume is using *1). Reinstalled a fresh Ubuntu 22.04 and held back *3.3 and now have internet. The only other update made on the day of the update of *3 was wireless-regdb. This package was not held back when I reinstalled Ubuntu 22.04, seems to be causing no issue. **Update** Tried going to *3 package today and internet connectivity works. Maybe there was corruption but received no messages of same the day of the original upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967842] Re: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working
Hi, running the current 5.15 Kernel, wifi is working again with the firmware from the jammy repository. $ uname -a Linux hostname 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ md5sum /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode dcf642fd7412614e19d1d54f57147539 /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Thanks. (My machine has no dual boot) ** Changed in: linux-firmware (Ubuntu Jammy) Status: Incomplete => Fix Released ** Changed in: linux-firmware (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967842 Title: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: Hi with the current Ubuntu 22.04 beta my WIFI device Intel Corporation Wireless-AC 9260 is not shown/working. If I copy/use the firmware from an current Ubuntu 20.04 system it is working again. Md5sum working from Ubuntu 20.04 linux-firmware: 0668e93b8766bf95d6adffdb33ec7bdb /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Md5sum not working from Ubuntu 22.04 linux-firmware: dcf642fd7412614e19d1d54f57147539 /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Outputs from the Ubuntu 22.04 system: Device Dell 7530: # lspci -Q -v -s 6e:00.0 6e:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Subsystem: Intel Corporation Device 4010 Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 16 Memory at a000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi # dpkg -l | grep linux-firmware ii linux-firmware 20220329.git681281e4-0ubuntu1 # uname -a Linux hostname 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # dmesg with broken firmware: [ 13.690647] kernel: iwlwifi :6e:00.0: enabling device ( -> 0002) [ 13.707780] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 0 [ 13.707784] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 1 [ 13.707786] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 2 [ 13.707787] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 3 [ 13.707788] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 4 [ 13.707790] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 6 [ 13.707791] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 8 [ 13.707792] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 9 [ 13.707793] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 10 [ 13.707795] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 11 [ 13.707796] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 15 [ 13.707797] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 16 [ 13.707798] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 18 [ 13.707800] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 19 [ 13.707801] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 20 [ 13.707802] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 21 [ 13.707804] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 28 [ 13.708080] kernel: iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [ 13.954798] kernel: iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [ 14.779900] kernel: iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [ 14.779904] kernel: iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [ 15.045652] kernel: iwlwifi :6e:00.0: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [ 15.045657] kernel: iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 15.293971] kernel: iwlwifi :6e:00.0: Not valid error log pointer 0x for Init uCode [ 15.294270] kernel: iwlwifi :6e:00.0: Hardware error detected. Restarting. [ 15.294271] kernel: iwlwifi :6e:00.0: IML/ROM dump: [ 15.294272] kernel: iwlwifi :6e:00.0: 0xA5A5 | IML/ROM SYSASSERT [ 15.294273] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM error/state [ 15.294420] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM data1 [ 15.294429] kernel: iwlwifi :6e:00.0: Fseq
[Kernel-packages] [Bug 1942999] Re: Fix invalid MAC address after hotplug tbt dock
** Summary changed: - [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after hotplug tbt dock + Fix invalid MAC address after hotplug tbt dock -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: Fix invalid MAC address after hotplug tbt dock Status in HWE Next: Fix Committed Status in linux 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-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Committed 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-oem-5.17 source package in Jammy: Fix Committed Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967935] Re: Bluetooth doesn't work on Google Beltino board (AR9462 PCI, IMC Networks USB)
*** This bug is a duplicate of bug 1969853 *** https://bugs.launchpad.net/bugs/1969853 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-firmware (Ubuntu) Status: Fix Committed => Fix Released ** This bug has been marked a duplicate of bug 1969853 No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) -- 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/1967935 Title: Bluetooth doesn't work on Google Beltino board (AR9462 PCI, IMC Networks USB) Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Bug description: 21.10 there was bluetooth no problem 22.04 bluetooth is off and stays off ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 20:07:02 2022 InstallationDate: Installed on 2022-01-30 (65 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: bnep btusb bluetooth MachineType: GOOGLE Panther ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-31 (5 days ago) dmi.bios.date: 01/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Panther dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:br4.0:efr0.0:svnGOOGLE:pnPanther:pvr1.0:rvnGOOGLE:rnPanther:rvr1.0:cvnGOOGLE:ct3:cvr:sku: dmi.product.family: Google_Beltino dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969853] Re: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works)
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Invalid -- 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/1969853 Title: No Bluetooth Found on QCA9565 (but replacing the ar3k firmware works) Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Bug description: [Impact] No bluetooth found on QCA9565. [Test Case] See below. [Fix] Provide ar3k/* firmware blobs. [Where Problems Could Occur] None expected, this is a regression from Impish. [Original Description] After updating to version 22.04, with kernel 5.15.0-25, Bluettoth stopped working via menu. Before I used versions 20.04 and 21.10, the latter with kernel 5.13, and Bluetooth was recognized normally. The bluetooth status in the terminal is this: diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago Docs: man:bluetoothd(8) Main PID: 1100 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18808) Memory: 1.8M CPU: 66ms CGroup: /system.slice/bluetooth.service └─1100 /usr/lib/bluetooth/bluetoothd abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service... abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64 abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service. abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management interface 1.21 initialized --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 2220 F pulseaudio /dev/snd/pcmC0D0p: diego 2220 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-23 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15-3567 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=bf1a2827-c8db-4042-aa45-5db6ad9d1449 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.15.0-27-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: 12/15/2021 dmi.bios.release: 2.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.18.0 dmi.board.name: 0MM5K1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.18.0:bd12/15/2021:br2.18:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0MM5K1:rvrA00:cvnDellInc.:ct9:cvr:sku078B: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958952] Re: ARM64 node appleton-kernel dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"
** Summary changed: - ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9" + ARM64 node appleton-kernel dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9" -- 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/1958952 Title: ARM64 node appleton-kernel dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: While investigating the SRU deployment failure, I noticed the dmesg will be spammed with: Jan 25 07:48:36 appleton-kernel kernel: [ 22.885627] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885628] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885629] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885631] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Issue found with Focal 5.4.0-96-generic Please find attachment for the syslog. Not sure if this is cause of our deployment issue, but it seems odd to me. And here is our deployment issue: 1. System successfully deployed with Focal 2. Deployment process hangs with "Enabling PPA" stage 3. I cannot connect to this system manually, ssh hangs (soft lockup maybe?) after: Warning: Permanently added '10.229.50.13' (ECDSA) to the list of known hosts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-96-generic 5.4.0-96.109 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 25 07:48 seq crw-rw 1 root audio 116, 33 Jan 25 07:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Jan 25 07:53:33 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd. Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Hisilicon D05 PciMultimedia: ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic root=UUID=3abb8e5a-2f46-4221-b664-cb02a273a249 ro sysrq_always_enabled RelatedPackageVersions: linux-restricted-modules-5.4.0-96-generic N/A linux-backports-modules-5.4.0-96-generic N/A linux-firmware1.187.25 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC11SPCD dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Hisilicon dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.50:bd06/01/2018:svnHisilicon:pnD05:pvrV100R001C00:rvnHuawei:rnBC11SPCD:rvrVER.A:cvnHisilicon:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: D05 dmi.product.sku: To be filled by O.E.M. dmi.product.version: V100R001C00 dmi.sys.vendor: Hisilicon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967842] Re: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working
Is this still an issue with the latest 5.15 kernel and linux-firmware in 22.04? Reverting firmware to make it work is an interesting data point but obviously not a long-term solution. If you still encounter problems, please run 'apport-collect 1967842'. Also please indicate if the machine is set up for dual-boot with Windows. ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu Jammy) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967842 Title: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: Hi with the current Ubuntu 22.04 beta my WIFI device Intel Corporation Wireless-AC 9260 is not shown/working. If I copy/use the firmware from an current Ubuntu 20.04 system it is working again. Md5sum working from Ubuntu 20.04 linux-firmware: 0668e93b8766bf95d6adffdb33ec7bdb /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Md5sum not working from Ubuntu 22.04 linux-firmware: dcf642fd7412614e19d1d54f57147539 /lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Outputs from the Ubuntu 22.04 system: Device Dell 7530: # lspci -Q -v -s 6e:00.0 6e:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Subsystem: Intel Corporation Device 4010 Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 16 Memory at a000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] L1 PM Substates Kernel driver in use: iwlwifi Kernel modules: iwlwifi # dpkg -l | grep linux-firmware ii linux-firmware 20220329.git681281e4-0ubuntu1 # uname -a Linux hostname 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # dmesg with broken firmware: [ 13.690647] kernel: iwlwifi :6e:00.0: enabling device ( -> 0002) [ 13.707780] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 0 [ 13.707784] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 1 [ 13.707786] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 2 [ 13.707787] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 3 [ 13.707788] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 4 [ 13.707790] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 6 [ 13.707791] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 8 [ 13.707792] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 9 [ 13.707793] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 10 [ 13.707795] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 11 [ 13.707796] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 15 [ 13.707797] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 16 [ 13.707798] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 18 [ 13.707800] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 19 [ 13.707801] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 20 [ 13.707802] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 21 [ 13.707804] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 28 [ 13.708080] kernel: iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [ 13.954798] kernel: iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [ 14.779900] kernel: iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [ 14.779904] kernel: iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [ 15.045652] kernel: iwlwifi :6e:00.0: SecBoot CPU1 Status: 0xa5a5a5a2, CPU2 Status: 0xa5a5a5a2 [ 15.045657] kernel: iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 15.293971] kernel: iwlwifi :6e:00.0: Not valid error log pointer 0x for Init uCode [ 15.294270] kernel: iwlwifi :6e:00.0: Hardware error detected. Restarting. [ 15.294271] kernel: iwlwifi :6e:00.0: IML/ROM dump: [ 15.294272] kernel: iwlwifi :6e:00.0: 0xA5A5 | IML/ROM SYSASSERT [ 15.294273] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM error/state [ 15.294420] kernel: iwlwifi
[Kernel-packages] [Bug 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
For people who believe they're seeing this issue with the -66 firmware, please provide logs by running 'apport-collect 1966793' after the problem occurred (obviously with the -66 firmware and latest 5.15 kernel). Reverting back to an older version if OK as a workaround but not a long term solution. ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Incomplete Bug description: This problem exists on an HP ProBook 440 G8 Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Wifi Adapter information : description: Wireless interface product: Wi-Fi 6 AX201 vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlp0s20f3 version: 20 serial: 28:d0:ea:21:6a:a1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.15.0-23-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff irq:16 memory:600324c000-600324 Error Information: [ 60.882505] CPU: 6 PID: 630 Comm: wpa_supplicant Not tainted 5.15.0-23-generic #23-Ubuntu [ 60.882512] Hardware name: HP HP ProBook 440 G8 Notebook PC/8807, BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+0x52/0x58 [ 60.882532] dump_stack_lvl+0x4a/0x5f [ 60.882541] dump_stack+0x10/0x12 [ 60.882545] iwl_trans_txq_send_hcmd_sync+0x345/0x350 [iwlwifi] [ 60.882582] ? wait_woken+0x70/0x70 [ 60.882589] iwl_trans_txq_send_hcmd+0xaa/0x140 [iwlwifi] [ 60.882619] iwl_trans_send_cmd+0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_send_cmd_pdu+0x6d/0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ppag_send_cmd+0x1b5/0x270 [iwlmvm] [ 60.882695] iwl_mvm_up+0x656/0xa80 [iwlmvm] [ 60.882716] ? __iwl_err.cold+0x25/0x2a [iwlwifi] [ 60.882755] __iwl_mvm_mac_start+0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_mac_start+0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_do_open+0x488/0x9c0 [mac80211] [ 60.882926] ? ieee80211_check_concurrent_iface+0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_open+0x6c/0x90 [mac80211] [ 60.883048] __dev_open+0xf0/0x1c0 [ 60.883054] __dev_change_flags+0x1a3/0x220 [ 60.883058] dev_change_flags+0x26/0x60 [ 60.883061] devinet_ioctl+0x598/0x6f0 [ 60.883068] ? netdev_name_node_lookup_rcu+0x6b/0x80 [ 60.883075] ? _copy_from_user+0x2e/0x60 [ 60.883082] inet_ioctl+0x165/0x190 [ 60.883088] sock_do_ioctl+0x42/0x100 [ 60.883093] ? do_readlinkat+0x10f/0x120 [ 60.883099] sock_ioctl+0xef/0x310 [ 60.883103] ? do_syscall_64+0x69/0xc0 [ 60.883110] __x64_sys_ioctl+0x91/0xc0 [ 60.883116] do_syscall_64+0x59/0xc0 [ 60.883120] ? do_syscall_64+0x69/0xc0 [ 60.883125] ? do_syscall_64+0x69/0xc0 [ 60.883129] ? syscall_exit_to_user_mode+0x27/0x50 [ 60.883133] ? __x64_sys_readlink+0x1e/0x30 [ 60.883137] ? do_syscall_64+0x69/0xc0 [ 60.883142] ? do_syscall_64+0x69/0xc0 [ 60.883147] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 60.883162] RSP: 002b:7ffc168507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00:14.3: failed to send PER_PLATFORM_ANT_GAIN_CMD (-5) [ 60.894910] iwlwifi :00:14.3: mac start retry 1 [ 61.068762] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 61.068863] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 61.068866] iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 [ 61.068871] iwlwifi :00:14.3: Loaded firmware version: 66.f1c864e0.0 QuZ-a0-jf-b0-66.ucode
[Kernel-packages] [Bug 1965572] Re: My mouse and keyboard are disconnecting frequently.
Is this still an issue with the current 5.15 HWE kernel? ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1965572 Title: My mouse and keyboard are disconnecting frequently. Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Incomplete Bug description: My mouse and keyboard are disconnecting frequently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.27 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: softvaro 1463 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 15:05:28 2022 Dependencies: InstallationDate: Installed on 2022-02-13 (32 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 0cf3:e005 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3576 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=7952701f-4382-4f8b-b0d7-410f5f5af678 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-35-generic N/A linux-backports-modules-5.13.0-35-generic N/A linux-firmware 1.187.27 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2018 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0208V7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/18/2018:br1.5:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0208V7:rvrA01:cvnDellInc.:ct10:cvr:sku083F: dmi.product.family: Inspiron dmi.product.name: Inspiron 3576 dmi.product.sku: 083F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1965572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966793] Re: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Invalid -- 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/1966793 Title: Wi-Fi 6 AX201 not working on 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: New Bug description: This problem exists on an HP ProBook 440 G8 Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Wifi Adapter information : description: Wireless interface product: Wi-Fi 6 AX201 vendor: Intel Corporation physical id: 14.3 bus info: pci@:00:14.3 logical name: wlp0s20f3 version: 20 serial: 28:d0:ea:21:6a:a1 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.15.0-23-generic firmware=66.f1c864e0.0 QuZ-a0-jf-b0-66.u latency=0 link=no multicast=yes wireless=IEEE 802.11 resources: iomemory:600-5ff irq:16 memory:600324c000-600324 Error Information: [ 60.882505] CPU: 6 PID: 630 Comm: wpa_supplicant Not tainted 5.15.0-23-generic #23-Ubuntu [ 60.882512] Hardware name: HP HP ProBook 440 G8 Notebook PC/8807, BIOS T85 Ver. 01.06.03 08/26/2021 [ 60.882514] Call Trace: [ 60.882517] [ 60.882521] show_stack+0x52/0x58 [ 60.882532] dump_stack_lvl+0x4a/0x5f [ 60.882541] dump_stack+0x10/0x12 [ 60.882545] iwl_trans_txq_send_hcmd_sync+0x345/0x350 [iwlwifi] [ 60.882582] ? wait_woken+0x70/0x70 [ 60.882589] iwl_trans_txq_send_hcmd+0xaa/0x140 [iwlwifi] [ 60.882619] iwl_trans_send_cmd+0x84/0x110 [iwlwifi] [ 60.882646] iwl_mvm_send_cmd_pdu+0x6d/0xc0 [iwlmvm] [ 60.882675] iwl_mvm_ppag_send_cmd+0x1b5/0x270 [iwlmvm] [ 60.882695] iwl_mvm_up+0x656/0xa80 [iwlmvm] [ 60.882716] ? __iwl_err.cold+0x25/0x2a [iwlwifi] [ 60.882755] __iwl_mvm_mac_start+0x2b/0x1a0 [iwlmvm] [ 60.882777] iwl_mvm_mac_start+0x5f/0xc0 [iwlmvm] [ 60.882799] drv_start+0x4f/0xe0 [mac80211] [ 60.882858] ieee80211_do_open+0x488/0x9c0 [mac80211] [ 60.882926] ? ieee80211_check_concurrent_iface+0x158/0x1c0 [mac80211] [ 60.882987] ieee80211_open+0x6c/0x90 [mac80211] [ 60.883048] __dev_open+0xf0/0x1c0 [ 60.883054] __dev_change_flags+0x1a3/0x220 [ 60.883058] dev_change_flags+0x26/0x60 [ 60.883061] devinet_ioctl+0x598/0x6f0 [ 60.883068] ? netdev_name_node_lookup_rcu+0x6b/0x80 [ 60.883075] ? _copy_from_user+0x2e/0x60 [ 60.883082] inet_ioctl+0x165/0x190 [ 60.883088] sock_do_ioctl+0x42/0x100 [ 60.883093] ? do_readlinkat+0x10f/0x120 [ 60.883099] sock_ioctl+0xef/0x310 [ 60.883103] ? do_syscall_64+0x69/0xc0 [ 60.883110] __x64_sys_ioctl+0x91/0xc0 [ 60.883116] do_syscall_64+0x59/0xc0 [ 60.883120] ? do_syscall_64+0x69/0xc0 [ 60.883125] ? do_syscall_64+0x69/0xc0 [ 60.883129] ? syscall_exit_to_user_mode+0x27/0x50 [ 60.883133] ? __x64_sys_readlink+0x1e/0x30 [ 60.883137] ? do_syscall_64+0x69/0xc0 [ 60.883142] ? do_syscall_64+0x69/0xc0 [ 60.883147] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 60.883152] RIP: 0033:0x7f66c7592aff [ 60.883158] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 [ 60.883162] RSP: 002b:7ffc168507c0 EFLAGS: 0246 ORIG_RAX: 0010 [ 60.883168] RAX: ffda RBX: 0001 RCX: 7f66c7592aff [ 60.883171] RDX: 7ffc16850820 RSI: 8914 RDI: 0009 [ 60.883174] RBP: 0009 R08: R09: 55e021909e90 [ 60.883176] R10: 0007 R11: 0246 R12: 55e02190e028 [ 60.883178] R13: R14: 7ffc16850820 R15: 0005 [ 60.883182] [ 60.883206] iwlwifi :00:14.3: failed to send PER_PLATFORM_ANT_GAIN_CMD (-5) [ 60.894910] iwlwifi :00:14.3: mac start retry 1 [ 61.068762] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 61.068863] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 61.068866] iwlwifi :00:14.3: Transport status: 0x004B, valid: 6 [ 61.068871] iwlwifi :00:14.3: Loaded firmware version: 66.f1c864e0.0 QuZ-a0-jf-b0-66.ucode [ 61.068874] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 61.068878] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [ 61.068881] iwlwifi :00:14.3: 0x | trm_hw_status1 [
[Kernel-packages] [Bug 1987265] Re: drm/i915, turbostat: Support for ADL-N, RPL-P
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Fix Committed -- 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/1987265 Title: drm/i915, turbostat: Support for ADL-N, RPL-P Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] We're missing support for ADL-N/RPL-P and some RPL-S pci-id's. [Test case] Boot a system with these pci-id's, see that graphics now work [What could go wrong] These are new pci-id's, no change for current platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1987265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958952] Re: ARM64 node dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"
I can see this issue with 5.4.0-124-generic #140~18.04.1-Ubuntu on node
appleton-kernel as well.
After this, it's cpu soft lockup:
[ 19.296854] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 0): Completion
event for bogus CQ 0x5a5aa9
[ 19.296855] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 0): Completion
event for bogus CQ 0x5a5aa9
[ 19.296858] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 0): Completion
event for bogus CQ 0x5a5aa9
[ 19.296860] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 0): Completion
event for bogus CQ 0x5a5aa9
[ 19.347370] mlx5_core 0005:01:00.0 enP5p1s0f0: Link down
[ 19.634790] ixgbe 000a:11:00.0: registered PHC device on enP10p17s0f0
[ 21.492952] hns-nic HISI00C2:00 enahisic2i0: link up
[ 21.492971] IPv6: ADDRCONF(NETDEV_CHANGE): enahisic2i0: link becomes ready
[ 25.794327] EXT4-fs (nvme0n1p2): resizing filesystem from 390571008 to
390572113 blocks
[ 25.794567] EXT4-fs (nvme0n1p2): resized filesystem to 390572113
[ 27.550919] new mount options do not match the existing superblock, will be
ignored
[ 32.692121] fbcon: Taking over console
[ 32.698403] Console: switching to colour frame buffer device 100x37
[ 64.276773] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0]
[ 64.283899] Modules linked in: nls_iso8859_1 ipmi_ssif input_leds joydev
ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4
btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq
async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear
mlx5_ib hibmc_drm drm_vram_helper ses enclosure ttm hid_generic usbhid
ib_uverbs hid ib_core marvell drm_kms_helper syscopyarea sysfillrect sysimgblt
fb_sys_fops crct10dif_ce mlx5_core hisi_sas_v2_hw ghash_ce sha2_ce sha256_arm64
ixgbe sha1_ce tls hisi_sas_main nvme xfrm_algo drm megaraid_sas nvme_core mdio
mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio
hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher
[ 64.283952] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-124-generic
#140~18.04.1-Ubuntu
[ 64.283954] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018
[ 64.283956] pstate: 4045 (nZcv daif +PAN -UAO)
[ 64.283962] pc : __do_softirq+0x98/0x350
[ 64.283966] lr : irq_exit+0xc0/0xc8
[ 64.283967] sp : 8000123b3ef0
[ 64.283969] x29: 8000123b3ef0 x28: 002fb7193d00
[ 64.283971] x27: x26: 8000123b4000
[ 64.283972] x25: 8000123b x24: 001fba073600
[ 64.283974] x23: 8000127cbdb0 x22:
[ 64.283976] x21: 0282 x20: 0002
[ 64.283977] x19: 800011b84000 x18: 800011268830
[ 64.283979] x17: x16:
[ 64.283980] x15: 0001 x14: 002fbb9f21c8
[ 64.283982] x13: 0004 x12: 0003
[ 64.283984] x11: x10: 0040
[ 64.283985] x9 : 80001208f358 x8 : 80001208f350
[ 64.283987] x7 : 001fb9002270 x6 : 0002a698ef5f
[ 64.283989] x5 : 0031 x4 : 802fa9e81000
[ 64.283991] x3 : 800011b84780 x2 : 802fa9e81000
[ 64.283993] x1 : 00e0 x0 : 800011b84780
[ 64.283995] Call trace:
[ 64.283998] __do_softirq+0x98/0x350
[ 64.284000] irq_exit+0xc0/0xc8
[ 64.284003] __handle_domain_irq+0x6c/0xc0
[ 64.284005] gic_handle_irq+0x84/0x2c0
[ 64.284007] el1_irq+0x104/0x1c0
[ 64.284010] arch_cpu_idle+0x34/0x1c0
[ 64.284014] default_idle_call+0x24/0x60
[ 64.284016] do_idle+0x1d8/0x2b8
[ 64.284017] cpu_startup_entry+0x2c/0xb0
[ 64.284020] secondary_start_kernel+0x198/0x288
[ 98.196663] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 98.202575] rcu: 16-: (3 GPs behind) idle=8fa/0/0x3 softirq=983/983
fqs=7488
[ 98.210133] (detected by 5, t=15002 jiffies, g=4709, q=3243)
[ 98.210134] Task dump for CPU 16:
[ 98.210137] swapper/16 R running task0 0 1 0x002a
[ 98.210140] Call trace:
[ 98.210146] __switch_to+0xcc/0x210
[ 98.210149] 0x0
[ 119.928660] rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: {
16-... } 15393 jiffies s: 229 root: 0x2/.
[ 119.939266] rcu: blocking rcu_node structures: l=1:16-31:0x1/.
[ 119.945099] Task dump for CPU 16:
[ 119.945102] swapper/16 R running task0 0 1 0x002a
[ 119.945108] Call trace:
[ 119.945120] __switch_to+0xcc/0x210
[ 119.945127] 0x0
[ 242.808432] INFO: task ureadahead:1097 blocked for more than 120 seconds.
[ 242.815214] Tainted: G L5.4.0-124-generic
#140~18.04.1-Ubuntu
[ 242.822868] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 242.830691] ureadahead D0 1097 1 0x
[ 242.830695] Call trace:
[
[Kernel-packages] [Bug 1987269] 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 1987269 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/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel:
