[Kernel-packages] [Bug 1970453] Re: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970453 Title: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 22.04 with kernel 5.15.0.27.30 on an HPE ProLiant DL20 Gen9 server. The server has an HPE Smart HBA H240 SATA controller. Since Ubuntu 22.04, the kernel runs into trouble after a few hours of uptime. The problem starts with a few instances of a message such as this: Apr 26 12:03:37 kernel: DMAR: ERROR: DMA PTE for vPFN 0x7bf32 already set (to 7bf32003 not 24c563801) Apr 26 12:03:37 kernel: [ cut here ] Apr 26 12:03:37 kernel: WARNING: CPU: 1 PID: 10171 at drivers/iommu/intel/iommu.c:2391 __domain_mapping.cold+0x94/0xcb Apr 26 12:03:37 kernel: Modules linked in: tls rpcsec_gss_krb5 binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limi> Apr 26 12:03:37 kernel: drm_kms_helper aesni_intel syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci cec crypto_simd i2c_i801 rc_core cryptd drm xhci_pci_renesas ahci i2c_smbus tg3 hpsa> Apr 26 12:03:37 kernel: CPU: 1 PID: 10171 Comm: kworker/u4:0 Not tainted 5.15.0-27-generic #28-Ubuntu Apr 26 12:03:37 kernel: Hardware name: HP ProLiant DL20 Gen9/ProLiant DL20 Gen9, BIOS U22 04/01/2021 Apr 26 12:03:37 kernel: Workqueue: writeback wb_workfn (flush-253:2) Apr 26 12:03:37 kernel: RIP: 0010:__domain_mapping.cold+0x94/0xcb Apr 26 12:03:37 kernel: Code: 27 9d 4c 89 4d b8 4c 89 45 c0 e8 03 c5 fa ff 8b 05 e7 e6 40 01 4c 8b 45 c0 4c 8b 4d b8 85 c0 74 09 83 e8 01 89 05 d2 e6 40 01 <0f> 0b e9 7e b2 b1 ff 89 ca 48 83 > Apr 26 12:03:37 kernel: RSP: 0018:c077826b2fa0 EFLAGS: 00010202 Apr 26 12:03:37 kernel: RAX: 0004 RBX: 9f0042062990 RCX: Apr 26 12:03:37 kernel: RDX: RSI: 9f02b3d20980 RDI: 9f02b3d20980 Apr 26 12:03:37 kernel: RBP: c077826b2ff0 R08: 00024c563801 R09: 0024c563 Apr 26 12:03:37 kernel: R10: R11: c01550e0 R12: 000f Apr 26 12:03:37 kernel: R13: 0007bf32 R14: 9f00412f5800 R15: 9f0042062938 Apr 26 12:03:37 kernel: FS: () GS:9f02b3d0() knlGS: Apr 26 12:03:37 kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 26 12:03:37 kernel: CR2: 1530f676a01c CR3: 00029c210001 CR4: 002706e0 Apr 26 12:03:37 kernel: Call Trace: Apr 26 12:03:37 kernel: Apr 26 12:03:37 kernel: intel_iommu_map_pages+0xdc/0x120 Apr 26 12:03:37 kernel: ? __alloc_and_insert_iova_range+0x203/0x240 Apr 26 12:03:37 kernel: __iommu_map+0xda/0x270 Apr 26 12:03:37 kernel: __iommu_map_sg+0x8e/0x120 Apr 26 12:03:37 kernel: iommu_map_sg_atomic+0x14/0x20 Apr 26 12:03:37 kernel: iommu_dma_map_sg+0x345/0x4d0 Apr 26 12:03:37 kernel: __dma_map_sg_attrs+0x68/0x70 Apr 26 12:03:37 kernel: dma_map_sg_attrs+0xe/0x20 Apr 26 12:03:37 kernel: scsi_dma_map+0x39/0x50 Apr 26 12:03:37 kernel: hpsa_scsi_ioaccel2_queue_command.constprop.0+0x11e/0x570 [hpsa] Apr 26 12:03:37 kernel: ? __blk_rq_map_sg+0x36/0x160 Apr 26 12:03:37 kernel: hpsa_scsi_ioaccel_queue_command+0x82/0xd0 [hpsa] Apr 26 12:03:37 kernel: hpsa_ioaccel_submit+0x174/0x190 [hpsa] Apr 26 12:03:37 kernel: hpsa_scsi_queue_command+0x19c/0x240 [hpsa] Apr 26 12:03:37 kernel: ? recalibrate_cpu_khz+0x10/0x10 Apr 26 12:03:37 kernel: scsi_dispatch_cmd+0x93/0x1f0 Apr 26 12:03:37 kernel: scsi_queue_rq+0x2d1/0x690 Apr 26 12:03:37 kernel: blk_mq_dispatch_rq_list+0x126/0x600 Apr 26 12:03:37 kernel: ? __sbitmap_queue_get+0x1/0x10 Apr 26 12:03:37 kernel: __blk_mq_do_dispatch_sched+0xba/0x2d0 Apr 26 12:03:37 kernel: __blk_mq_sched_dispatch_requests+0x104/0x150 Apr 26 12:03:37 kernel: blk_mq_sched_dispatch_requests+0x35/0x60 Apr 26 12:03:37 kernel: __blk_mq_run_hw_queue+0x34/0xb0 Apr 26 12:03:37 kernel: __blk_mq_delay_run_hw_queue+0x162/0x170 Apr 26 12:03:37 kernel: blk_mq_run_hw_queue+0x83/0x120 Apr 26 12:03:37 kernel: blk_mq_sched_insert_requests+0x69/0xf0 Apr 26 12:03:37 kernel: blk_mq_flush_plug_list+0x103/0x1c0 Apr 26 12:03:37 kernel: blk_flush_plug_list+0xdd/0x100 Apr 26 12:03:37 kernel: blk_mq_submit_bio+0x2bd/0x600 Apr 26 12:03:37 kernel: __submit_bio+0x1ea/0x220 Apr 26 12:03:37 kernel: ? mempool_alloc_slab+0x17/0x20 Apr 26 12:03:37 kernel: __submit_bio_noacct+0x85/0x1f0 Apr 26 12:03:37 kernel: submit_bio_noacct+0x4e/0x120 Apr 26 12:03:37 kernel: ? radix_tree_lookup+0xd/0x10 Apr 26 12:03:37 kernel: ? bio_associate_blkg_from_css+0x1b2/0x310 Apr 26 12:03:37 kernel: submit_bio+0x4a/0x130
[Kernel-packages] [Bug 2009287] [NEW] When using this kernel, the HDMI audio output dissapears
Public bug reported: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description:Linux Mint 21.1 Release:21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected audio hdmi kernel-bug vera ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2009287/+attachment/5651691/+files/lspci-vnvn.log ** Tags added: apport-collected vera ** Description changed: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: rodolfo1805 F..
[Kernel-packages] [Bug 2009287] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651692/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651693/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651694/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651696/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651695/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651698/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651697/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651702/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651700/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651703/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651701/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651699/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651704/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651709/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651708/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651705/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651706/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2009287/+attachment/5651707/+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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: New Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: Confirmed Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
After upgrading Ubuntu to `Lunar Lobster`, I couldn't adjust the
brightness of my laptop under `Software Rendering` now😥.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009289] [NEW] 22.04 suspend not properly working
Public bug reported: very similar to:+Ubuntu 22.04 suspend improper working but happens always ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009289 Title: 22.04 suspend not properly working Status in linux package in Ubuntu: New Bug description: very similar to:+Ubuntu 22.04 suspend improper working but happens always To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009289] 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 2009289 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/2009289 Title: 22.04 suspend not properly working Status in linux package in Ubuntu: Incomplete Bug description: very similar to:+Ubuntu 22.04 suspend improper working but happens always To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009286] [NEW] linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI
You have been subscribed to a public bug: Description:Ubuntu 22.04.2 LTS Release:22.04 I am running linux-image-unsigned-6.1.15-060115-generic/now successfully. If I try to run any 6.2.x image, after the boot screen I get a filesystem check, then the boot screen again which just hangs. The Ubuntu GUI never loads. Very happy to provide any further information ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 6.2.x bot-comment focal -- linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI https://bugs.launchpad.net/bugs/2009286 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009286] Re: linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI
** Tags added: focal ** 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/2009286 Title: linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI Status in linux package in Ubuntu: New Bug description: Description:Ubuntu 22.04.2 LTS Release:22.04 I am running linux-image-unsigned-6.1.15-060115-generic/now successfully. If I try to run any 6.2.x image, after the boot screen I get a filesystem check, then the boot screen again which just hangs. The Ubuntu GUI never loads. Very happy to provide any further information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009294] [NEW] ZFS shares not available after reboot
Public bug reported: System: Ubuntu 22.04.1 LTS Issue: ZFS SMB shares not available after reboot Workaround: sed -i 's/smb.service/smbd.service/g' zfs-share.service ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2009294 Title: ZFS shares not available after reboot Status in zfs-linux package in Ubuntu: New Bug description: System: Ubuntu 22.04.1 LTS Issue: ZFS SMB shares not available after reboot Workaround: sed -i 's/smb.service/smbd.service/g' zfs-share.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2009294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009286] 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 2009286 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/2009286 Title: linux-image-unsigned-6.2.0-060200-generic/now doesn't load GUI Status in linux package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.2 LTS Release:22.04 I am running linux-image-unsigned-6.1.15-060115-generic/now successfully. If I try to run any 6.2.x image, after the boot screen I get a filesystem check, then the boot screen again which just hangs. The Ubuntu GUI never loads. Very happy to provide any further information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs
I'm also experiencing this on my Lenovo Gen 3 T14s w/ Ryzen CPU :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". EDIT: Changed title after confirmation for earlier Ryzen 5000 CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009296] [NEW] nvidia-dkms-390 390.157-0ubuntu0.22.04.1: nvidia kernel module failed to build
Public bug reported: nvidia kernel module failed to build, reporting flow initiated automatically. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 5.15.0-60-generic Date: Tue Feb 28 07:39:50 2023 InstallationDate: Installed on 2019-07-29 (1315 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.1) PackageVersion: 390.157-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.157-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to jammy on 2022-03-27 (342 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2009296 Title: nvidia-dkms-390 390.157-0ubuntu0.22.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: nvidia kernel module failed to build, reporting flow initiated automatically. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown DKMSKernelVersion: 5.15.0-60-generic Date: Tue Feb 28 07:39:50 2023 InstallationDate: Installed on 2019-07-29 (1315 days ago) InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.1) PackageVersion: 390.157-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-dkms-390 390.157-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: Upgraded to jammy on 2022-03-27 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003034] Re: system freezes after installing 22.04c
Upgrade tot 6.1.0-1007. The shell does not freeze any longer but firefox still does whenever it is requested to bring up a dialog window (for example to do perform download). The browser needs to be killed to become usable again. My journalctl log has this: mrt 05 16:13:20 Dapple firefox.desktop[674861]: [Parent 674861, Main Thread] WARNING: The peer-to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges.: 'glib warning', file /build/firefox-AoeKfi/firefox-110.0.1+build2/toolkit/xre/nsSigHandlers.cpp:167 mrt 05 16:13:20 Dapple firefox[674861]: The peer-to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. Nautilus would appear to be affected, too: mrt 05 16:14:35 Dapple gnome-shell[2966]: The peer-to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. mrt 05 16:14:35 Dapple nautilus[677317]: The peer-to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2003034 Title: system freezes after installing 22.04c Status in linux-meta-oem-6.1 package in Ubuntu: New Bug description: After upgrading to kernel 6.1 (linux-oem-20.04c), I experience system freezes within seconds from logging in. On the first two runs, the system only froze when I launched firefox. On the next run, it froze immediately after logging in. On all three occasions ,the Keyboard and mouse were instantly dead and connecting over the network turned out to be impossible. The system behaves as expected when I switch back to 6.0 (6.0.0.-1010). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-oem-22.04c 6.1.0.1004.4 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Jan 17 03:19:17 2023 InstallationDate: Installed on 2022-03-27 (295 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2003034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008245] Re: zfs-dkms: support linux 6.2
uploaded, thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2008245 Title: zfs-dkms: support linux 6.2 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Lunar: New Bug description: [Impact] The current version of zfs-dkms available in lunar fails to build with kernels >= 6.2, reporting the following configure error: configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.7-1ubuntu1 *** Compatible Kernels: 3.10 - 6.0 [Test case] $ apt install zfs-dkms [Fix] Resync with zfs version in Debian (2.1.9) and apply the usual Ubuntu specific changes. [Regression potential] We may experience zfs regressions due to a new major version, especially on zfs volumes / filesystems created with the previous versions. However this goes in pair with the new major kernel version and we need to upgrade the version of zfs to properly support the new kernel 6.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Re: When using this kernel, the HDMI audio output dissapears
I want to mention that there seems to be a few threads coming in for the same kernel showing similar behavior on various sound devices. https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too- many-bdl-entries-messages-in-system-log https://askubuntu.com/questions/1457524/hdmi-audio-not-detected-after- update-for-amd-graphics https://askubuntu.com/questions/1457579/hdmi-on-amd-video-card-doesnt- work-with-sound-on-ubuntu-22-10 https://askubuntu.com/questions/1457574/upgrade- kernel-5-19-0-35-generic-sound-blaster-recon3d-z-series-not-detected All of these posts were created between the last 72 hours it seems. -- 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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: Confirmed Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: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/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system
I just tried kernel 5.19.0-35-generic #36 on Ubuntu 22.10 (kinetic) that should contain the fix. A few times when I suspend my notebook (Yoga Slim 7 14are05), the issue occurred with Slack (a snap app): /var/log/syslog --- Mar 5 20:33:27 rzbox ModemManager[1095]: [sleep-monitor-systemd] system is about to suspend Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.6532] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.6533] device (eno1): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 5 20:33:27 rzbox kernel: [ 2079.870212] audit: type=1107 audit(1678044807.651:222): pid=998 uid=102 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedes ktop/login1" interface="org.freedesktop.login1.Manager" member="PrepareForSleep" name=":1.4" mask="receive" pid=6112 label="snap.slack.slack" peer_pid=1033 peer_label="unconfined" Mar 5 20:33:27 rzbox kernel: [ 2079.870212] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' Mar 5 20:33:27 rzbox google-chrome.desktop[4369]: [4363:4392:0305/203327.655811:ERROR:connection_factory_impl.cc(472)] ConnectionHandler failed with net error: -2 Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.6618] device (enp1s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.6721] manager: NetworkManager state is now ASLEEP Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.6724] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Mar 5 20:33:27 rzbox dbus-daemon[998]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.17' (uid=0 pid=1078 comm="/usr/sbin/NetworkMan ager --no-daemon" label="unconfined") Mar 5 20:33:27 rzbox systemd[1]: Starting Network Manager Script Dispatcher Service... Mar 5 20:33:27 rzbox dbus-daemon[998]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 5 20:33:27 rzbox systemd[1]: Started Network Manager Script Dispatcher Service. Mar 5 20:33:27 rzbox kernel: [ 2079.933073] wlp3s0: deauthenticating from d4:6e:0e:d9:d5:e7 by local choice (Reason: 3=DEAUTH_LEAVING) Mar 5 20:33:27 rzbox google-chrome.desktop[4369]: [4363:4392:0305/203327.718074:ERROR:connection_factory_impl.cc(427)] Failed to connect to MCS endpoint with error -105 Mar 5 20:33:27 rzbox gsd-media-keys[3663]: Unable to get default sink Mar 5 20:33:27 rzbox update-notifier[5690]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed Mar 5 20:33:27 rzbox wpa_supplicant[1079]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=d4:6e:0e:d9:d5:e7 reason=3 locally_generated=1 Mar 5 20:33:27 rzbox wpa_supplicant[1079]: wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all Mar 5 20:33:27 rzbox wpa_supplicant[1079]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9266] device (wlp3s0): supplicant interface state: completed -> disconnected Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9269] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') Mar 5 20:33:27 rzbox avahi-daemon[994]: Withdrawing address record for fe80::5525:e62a:821e:1665 on wlp3s0. Mar 5 20:33:27 rzbox avahi-daemon[994]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::5525:e62a:821e:1665. Mar 5 20:33:27 rzbox avahi-daemon[994]: Interface wlp3s0.IPv6 no longer relevant for mDNS. Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9683] dhcp4 (wlp3s0): canceled DHCP transaction Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9683] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 seconds) Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9684] dhcp4 (wlp3s0): state changed no lease Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9687] dhcp6 (wlp3s0): canceled DHCP transaction Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9687] dhcp6 (wlp3s0): activation: beginning transaction (timeout in 45 seconds) Mar 5 20:33:27 rzbox NetworkManager[1078]: [1678044807.9687] dhcp6 (wlp3s0): state changed no lease Mar 5 20:33:27 rzbox avahi-daemon[994]: Withdrawing address record for 172.16.10.104 on wlp3s0. Mar 5 20:33:27 rzbox avahi-daemon[994]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 172.16.10.104. Mar 5 20:33:27 rzbox systemd-resolved[789]: wlp3s0: Bus client set default route setting: no Mar 5 20:33:27 rzbox systemd-resolved[789]: wlp3s0: Bus client reset DNS server list. Mar 5 20:33:27 rzbox avahi-daemon[994]: Interface wlp3s0.IPv4 no longer relevant for mDNS. Mar
[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system
I get this error every time I try to open Spotify. Laptop: Lenovo ThinkPad L14 Gen 2a | AMD® Ryzen 5 5600u with radeon graphics × 12 Ubuntu: Ubuntu 22.04.2 LTS | 5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1995956 Title: amdgpu no-retry page fault resulting in black screen and unresponsive system Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This happens in a loop and eventually leads to GPU reset, which fails. Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=211509, emitted seq=211512 Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 154558 Nov 03 16:35:55 laptop
[Kernel-packages] [Bug 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
This bug was fixed in the package mesa-amber - 21.3.9-0ubuntu1 --- mesa-amber (21.3.9-0ubuntu1) lunar; urgency=medium * Merge from Debian. -- Timo Aaltonen Tue, 21 Feb 2023 09:38:30 +0200 ** Changed in: mesa-amber (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa-amber package in Ubuntu: Fix Released Bug description: I enabled lunar-proposed today (with APT::Default-Release "lunar- proposed";) and got the error below during update: Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/2006744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
6.1.0-1008-oem is working fine. Suspends and resumes with now issues so far. I think i have changed the tag from verification-needed-jammy to verification-done-jammy ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999750] Re: Set explicit CC in the headers package
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1999750 Title: Set explicit CC in the headers package Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.19 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-hwe-5.19 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-hwe-5.19 source package in Lunar: Invalid Bug description: [ Impact ] * Currently Ubuntu Linux kernel header packages use stock Makefile as shipped by upstream kernel. During linux kernel package build however HOSTCC and CC are typically overridden to use explicit complier version $(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms module build failures as despite all efforts to reuse matching gcc version out of .config, various shell scripts / build systems / makefiles do not pass the CC variable as a make variable to the end make call that is used to build dkms modules. To avoid this, hardcode the correct compiler in the linux headers package shipped Makefile. This is similar to the Makefile includes that debian ships, albeit with less indirections. [ Test Plan ] * adt-matrix for dkms modules should start to pass correctly [ Where problems could occur ] * headers package for hwe kernels may demand a newer compiler, for which runtime dependency does not exist. dkms package in jammy-updates already has explicit dependency on gcc-12 for that reason. Installing build-deps of the kernel package will install correct/required compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic -- 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/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK remote: To 54.69.112.110:kinetic.git ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsu
[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64
This bug is awaiting verification that the linux-aws/5.19.0-1021.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags removed: verification-done-kinetic
** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic
--
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/2000667
Title:
cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from
ubuntu_kernel_selftests hang with non-amd64
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
cmsg_* tests in net tests from ubuntu_kernel_selftests will hang on
non-amd64 systems and eventually causing "Incomplete" test results on
RISCV kernels due to the timeout setting.
This is because of an infinity while loop caused by a char variable
used here to take the getopt() return value in cmsg_sender.c, it should
be an int instead.
[Fix]
* 1573c68820 ("selftests: net: fix cmsg_so_mark.sh test hang")
This patch can be cherry-picked into both Kinetic and Lunar, these test
cases are only available in these newer kernels.
[Test]
Compile the patched cmsg_sender.c on a non-amd64 system, and the cmsg_*
tests will no longer hanging.
[Where problems could occur ]
Change limited to testing tools, no actual impact to real functions.
[Original Bug Report]
Issue found with 5.19.0-1010.11, 5.19.0-1011.12
This issue does not exist in 5.19.0-1009.10 because the net test can't
be built by that time.
Test output:
Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..1
# selftests: net: cmsg_so_mark.sh
Timer expired (5400 sec.), nuking pid 82951
A manual test shows it will stuck with:
$ sudo ./cmsg_so_mark.sh
+ NS=ns
+ IP4=172.16.0.1/24
+ TGT4=172.16.0.2
+ IP6=2001:db8:1::1/64
+ TGT6=2001:db8:1::2
+ MARK=1000
+ trap cleanup EXIT
+ ip netns add ns
+ ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647'
+ ip -netns ns link add type dummy
+ ip -netns ns link set dev dummy0 up
+ ip -netns ns addr add 172.16.0.1/24 dev dummy0
+ ip -netns ns addr add 2001:db8:1::1/64 dev dummy0
+ ip -netns ns rule add fwmark 1000 lookup 300
+ ip -6 -netns ns rule add fwmark 1000 lookup 300
+ ip -netns ns route add prohibit any table 300
+ ip -6 -netns ns route add prohibit any table 300
+ BAD=0
+ TOTAL=0
+ for ovr in setsock cmsg both
+ for i in 4 6
+ '[' 4 == 4 ']'
+ TGT=172.16.0.2
+ for p in u i r
+ '[' u == u ']'
+ prot=UDP
+ '[' u == i ']'
+ '[' u == r ']'
+ '[' setsock == setsock ']'
+ m=-M
+ '[' setsock == cmsg ']'
+ '[' setsock == both ']'
+ ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234
(test stuck here)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999556] Re: commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile
This bug is awaiting verification that the linux-aws/5.19.0-1021.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-kinetic-linux-aws
--
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/1999556
Title:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in
kinetic master to remove "hio" reference from Makefile
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Added Linux kernel remote branch for Kinetic raspi to test with 22.04
install (both master and master-next branches). When running "make
clean" noticed error referencing "hio" driver that's been removed from
Jammy kernels:
$ make clean
scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
make[2]: *** No rule to make target 'ubuntu/hio/Makefile'. Stop.
make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
make: *** [Makefile:1858: _clean_ubuntu] Error 2
Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7
Author: Thomas Lamprecht
Date: Sat Mar 12 16:19:10 2022 +0100
Ubuntu: remove leftover reference to ubuntu/hio driver
A single reference to the hio driver was forgotten when it was removed
recently. While this reference is not a problem for the build itself, it
breaks the __clean target from 'scripts/Makefile.clean' here, as make
cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.
Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
Signed-off-by: Thomas Lamprecht
Acked-by: Tim Gardner
Signed-off-by: Paolo Pisati
Here's some additional information for code repositories (didn't know
if this was helpful),
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
branch.kinetic-master-next.remote=kinetic-raspi
branch.kinetic-master-next.merge=refs/heads/master-next
branch.kinetic-master.remote=kinetic-raspi
branch.kinetic-master.merge=refs/heads/master
[Test Case]
See above.
[Fix]
Pick commit cf58599cded35cf4affed1e659c0e2c742d3fda7 from jammy.
[Where Problems Could Occur]
Build failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999556/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic -- 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [Impact] When trying to build powerpc tests from ubuntu_kernel_selftests, it will fail with: inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; | ^~ cc1: all warnings being treated as errors [Fix] * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning" This patch can be cherry-picked into Kinetic kernel. [Test] Apply this patch to the kernel tree and build it with: sudo make -C linux/tools/testing/selftests TARGETS=powerpc With this error fixed, test compliation can finish without any issue. [Where problems could occur] Change for test case, no impact to acutal function. [Original Bug Report] Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- 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/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998885 Title: Add additional Mediatek MT7922 BT device ID Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998882 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic -- 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Committed Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-aws -- 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/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux-aws/5.19.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-kinetic ** Tags added: kernel-spammed-kinetic-linux-aws verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009275] Re: HDMI audio doesn't work for AMD RX6700 XT
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009275 Title: HDMI audio doesn't work for AMD RX6700 XT Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the recent update to the 5.19.35 kernel (installed on 4th March 2023), the HDMI audio (out) of my AMD RX6700 XT doesn't work anymore. I don't see any devices in Gnome or when listing the devices with `aplay -a` In the ACPI error message on startup I see: kernel: snd_hda_intel :01:00.1: no codecs initialized kernel: hdaudio hdaudioC1D0: no AFG or MFG node found When I boot with the old 5.19.0.32 kernel version HDMI audio works perfectly. Ubuntu 22.04.2 LTS linux-image-5.19.0-35-generic: 5.19.0-35.36~22.04.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:49:59 2023 InstallationDate: Installed on 2022-04-24 (314 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1022.23)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1022.23) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure/5.19.0-1022.23)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.19.0-1022.23) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1021.22)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.19.0-1021.22) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.19.0-1021.22)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.19.0-1021.22) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009276] Re: Audio Hdmi (Radeon rx580) not recognized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [Impact] When trying to build powerpc tests from ubuntu_kernel_selftests, it will fail with: inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; | ^~ cc1: all warnings being treated as errors [Fix] * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning" This patch can be cherry-picked into Kinetic kernel. [Test] Apply this patch to the kernel tree and build it with: sudo make -C linux/tools/testing/selftests TARGETS=powerpc With this error fixed, test compliation can finish without any issue. [Where problems could occur] Change for test case, no impact to acutal function. [Original Bug Report] Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64
This bug is awaiting verification that the linux-azure/5.19.0-1022.23
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-kinetic-linux-azure
--
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/2000667
Title:
cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from
ubuntu_kernel_selftests hang with non-amd64
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
cmsg_* tests in net tests from ubuntu_kernel_selftests will hang on
non-amd64 systems and eventually causing "Incomplete" test results on
RISCV kernels due to the timeout setting.
This is because of an infinity while loop caused by a char variable
used here to take the getopt() return value in cmsg_sender.c, it should
be an int instead.
[Fix]
* 1573c68820 ("selftests: net: fix cmsg_so_mark.sh test hang")
This patch can be cherry-picked into both Kinetic and Lunar, these test
cases are only available in these newer kernels.
[Test]
Compile the patched cmsg_sender.c on a non-amd64 system, and the cmsg_*
tests will no longer hanging.
[Where problems could occur ]
Change limited to testing tools, no actual impact to real functions.
[Original Bug Report]
Issue found with 5.19.0-1010.11, 5.19.0-1011.12
This issue does not exist in 5.19.0-1009.10 because the net test can't
be built by that time.
Test output:
Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..1
# selftests: net: cmsg_so_mark.sh
Timer expired (5400 sec.), nuking pid 82951
A manual test shows it will stuck with:
$ sudo ./cmsg_so_mark.sh
+ NS=ns
+ IP4=172.16.0.1/24
+ TGT4=172.16.0.2
+ IP6=2001:db8:1::1/64
+ TGT6=2001:db8:1::2
+ MARK=1000
+ trap cleanup EXIT
+ ip netns add ns
+ ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647'
+ ip -netns ns link add type dummy
+ ip -netns ns link set dev dummy0 up
+ ip -netns ns addr add 172.16.0.1/24 dev dummy0
+ ip -netns ns addr add 2001:db8:1::1/64 dev dummy0
+ ip -netns ns rule add fwmark 1000 lookup 300
+ ip -6 -netns ns rule add fwmark 1000 lookup 300
+ ip -netns ns route add prohibit any table 300
+ ip -6 -netns ns route add prohibit any table 300
+ BAD=0
+ TOTAL=0
+ for ovr in setsock cmsg both
+ for i in 4 6
+ '[' 4 == 4 ']'
+ TGT=172.16.0.2
+ for p in u i r
+ '[' u == u ']'
+ prot=UDP
+ '[' u == i ']'
+ '[' u == r ']'
+ '[' setsock == setsock ']'
+ m=-M
+ '[' setsock == cmsg ']'
+ '[' setsock == both ']'
+ ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234
(test stuck here)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999836] Re: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500]
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1999836 Title: Fix SUT can't displayed after resume from WB/CB with dGFX installed(FR:6/10)[RX6300][RX6500] Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] SUT can't displayed after resume from WB/CB with dGFX installed. Recovery: SUT can display when the DP cable unplug and plug . [Fix] Use quirk to block the affected SKUes. [Test Case] 1.Install Ubuntu 22.04 on SUT with dGFX card. 2.Connect the DP cable to the dGFX port. 3.SUT do power off/restart. 4.SUT can display. [Where problems could occur] Add SKU's id to a quirk table, the impact would be small. [Other Info] * For the pure Jammy, Confronted the error of compilation. 1. Need 8e794421bc98) drm/amd/display: Fork thread to offload work ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1449:38: error: implicit declaration of function 'hpd_rx_irq_create_ workqueue'; did you mean 'hdcp_create_workqueue'? [-Werror=implicit-function-declaration] 18848 1449 | adev->dm.hpd_rx_offload_wq = hpd_rx_irq_create_workqueue(adev->dm.dc); 18849 | ^~~ 18850 | hdcp_create_workqueue ~~~ 2. Need 3ce51649cdf2) drm/amdgpu/display: add quirk handling for stutter ~~~ drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:1505:13: error: implicit declaration of function 'dm_should_disable_ stutter' [-Werror=implicit-function-declaration] 18838 1505 | if (dm_should_disable_stutter(adev->pdev)) ~~~ * hpd_disconnect_quirk_table is placed to the different location on J/OEM-5.17 and on K/OEM-6.0, so can't use a single patch for all. * Result from CBD ~~~ Jammy, remote: *** kernel-cbd * remote: * Queueing builds (your 'j_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-820f542767e6-ESq2 remote: * 192/672 cores busy (2/7 hosts), 0 builds queued remote: 2022-12-15 17:09:15 kobako-jammy-820f542767e6-ESq2/amd64/BUILD-OK remote: 2022-12-15 17:11:13 kobako-jammy-820f542767e6-ESq2/arm64/BUILD-OK remote: 2022-12-15 17:07:30 kobako-jammy-820f542767e6-ESq2/armhf/BUILD-OK remote: 2022-12-15 17:10:17 kobako-jammy-820f542767e6-ESq2/ppc64el/BUILD-OK remote: 2022-12-15 17:04:55 kobako-jammy-820f542767e6-ESq2/s390x/BUILD-OK remote: To 54.69.112.110:jammy.git ~~~ Kinetic remote: *** kernel-cbd * remote: * Queueing builds (your 'k_gen_nxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-kinetic-857358673609-X4Nz remote: * 0/672 cores busy (0/7 hosts), 0 builds queued remote: 2022-12-15 17:41:37 kobako-kinetic-857358673609-X4Nz/amd64/BUILD-OK remote: 2022-12-15 17:42:13 kobako-kinetic-857358673609-X4Nz/arm64/BUILD-OK remote: 2022-12-15 17:35:54 kobako-kinetic-857358673609-X4Nz/armhf/BUILD-OK remote: 2022-12-15 17:40:54 kobako-kinetic-857358673609-X4Nz/ppc64el/BUILD-OK remote: 2022-12-15 17:34:47 kobako-kinetic-857358673609-X4Nz/s390x/BUILD-OK remote: To 54.69.112.110:kinetic.git ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1999836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : http
[Kernel-packages] [Bug 1999750] Re: Set explicit CC in the headers package
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1999750 Title: Set explicit CC in the headers package Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.19 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-hwe-5.19 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-hwe-5.19 source package in Lunar: Invalid Bug description: [ Impact ] * Currently Ubuntu Linux kernel header packages use stock Makefile as shipped by upstream kernel. During linux kernel package build however HOSTCC and CC are typically overridden to use explicit complier version $(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms module build failures as despite all efforts to reuse matching gcc version out of .config, various shell scripts / build systems / makefiles do not pass the CC variable as a make variable to the end make call that is used to build dkms modules. To avoid this, hardcode the correct compiler in the linux headers package shipped Makefile. This is similar to the Makefile includes that debian ships, albeit with less indirections. [ Test Plan ] * adt-matrix for dkms modules should start to pass correctly [ Where problems could occur ] * headers package for hwe kernels may demand a newer compiler, for which runtime dependency does not exist. dkms package in jammy-updates already has explicit dependency on gcc-12 for that reason. Installing build-deps of the kernel package will install correct/required compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999556] Re: commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile
This bug is awaiting verification that the linux-azure/5.19.0-1022.23
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still exists, change the tag 'verification-needed-kinetic' to
'verification-failed-kinetic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-kinetic-linux-azure
--
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/1999556
Title:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in
kinetic master to remove "hio" reference from Makefile
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Added Linux kernel remote branch for Kinetic raspi to test with 22.04
install (both master and master-next branches). When running "make
clean" noticed error referencing "hio" driver that's been removed from
Jammy kernels:
$ make clean
scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
make[2]: *** No rule to make target 'ubuntu/hio/Makefile'. Stop.
make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
make: *** [Makefile:1858: _clean_ubuntu] Error 2
Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7
Author: Thomas Lamprecht
Date: Sat Mar 12 16:19:10 2022 +0100
Ubuntu: remove leftover reference to ubuntu/hio driver
A single reference to the hio driver was forgotten when it was removed
recently. While this reference is not a problem for the build itself, it
breaks the __clean target from 'scripts/Makefile.clean' here, as make
cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.
Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
Signed-off-by: Thomas Lamprecht
Acked-by: Tim Gardner
Signed-off-by: Paolo Pisati
Here's some additional information for code repositories (didn't know
if this was helpful),
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
branch.kinetic-master-next.remote=kinetic-raspi
branch.kinetic-master-next.merge=refs/heads/master-next
branch.kinetic-master.remote=kinetic-raspi
branch.kinetic-master.merge=refs/heads/master
[Test Case]
See above.
[Fix]
Pick commit cf58599cded35cf4affed1e659c0e2c742d3fda7 from jammy.
[Where Problems Could Occur]
Build failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999556/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998885 Title: Add additional Mediatek MT7922 BT device ID Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990161] Re: Fix RPL-S support on powercap/intel_rapl
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure-5.15/5.15.0.1035.42~20.04.25)
All autopkgtests for the newly accepted linux-meta-azure-5.15 (5.15.0.1035.42~20.04.25) for focal have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.12.5-1ubuntu2~20.04.4 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998882 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug is awaiting verification that the linux-azure/5.19.0-1022.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure -- 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Committed Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
It's fixed now in proposed kernel linux-oem-6.1/6.1.0-1008.8 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958692] Re: System crashes and reboots every 15min - 2hr
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-oem-5.14 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958692 Title: System crashes and reboots every 15min - 2hr Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: I have a NUC11NAHi5 system running Ubuntu 20.04.3, and every few minutes to hours it will crash: justin :0 :0 Fri Jan 21 19:46 - crash (00:37) justin :0 :0 Fri Jan 21 19:40 - crash (00:05) justin :0 :0 Fri Jan 21 17:33 - crash (02:07) justin :0 :0 Fri Jan 21 17:16 - crash (00:07) justin :0 :0 Fri Jan 21 17:13 - crash (00:02) justin :0 :0 Fri Jan 21 16:54 - crash (00:19) justin :0 :0 Fri Jan 21 16:25 - crash (00:28) justin :0 :0 Fri Jan 21 16:18 - crash (00:06) justin :0 :0 Fri Jan 21 16:11 - crash (00:07) justin :0 :0 Fri Jan 21 15:46 - crash (00:24) When it comes back up I see the following errors in journalctl: kernel: BERT: Error records from previous boot: kernel: [Hardware Error]: event severity: fatal kernel: [Hardware Error]: Error 0, type: fatal kernel: [Hardware Error]: section_type: Firmware Error Record Reference kernel: [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type2 kernel: [Hardware Error]: Revision: 2 kernel: [Hardware Error]: Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d followed by a large hex dump. It could be related to this issue: https://community.intel.com/t5/Processors/Frequent-crashes-on-i5-11500/td-p/1280709 The BIOS is up-to-date, as is the intel microcode package. It doesn't seem to matter which kernel I use. I'm using the OEM one since the regular kernels for 20.04.3 (a) also have this problem, and (b) have broken IR support (https://askubuntu.com/questions/1380500/kernel-rc- rc0-receive-overflow). System: NUC11PAHi5 SKU: RNUC11PAHi5000 BIOS: PATGL357.0041.2021.0811.1505 Board: NUC11PABi5 CPU: i5-1135G7 I'm not sure if it's a kernel issue, BIOS issue, microcode issue, or hardware issue, so I decided to start here. Let me know how else I can help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1020-oem 5.14.0-1020.22 ProcVersionSignature: Ubuntu 5.14.0-1020.22-oem 5.14.20 Uname: Linux 5.14.0-1020-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 21 20:44:43 2022 InstallationDate: Installed on 2022-01-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1958692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000772] Re: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19
We don't have PowerPC for AWS / Azure. ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/2000772 Title: powerpc-build in ubuntu_kernel_selftests failed on P9 with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [Impact] When trying to build powerpc tests from ubuntu_kernel_selftests, it will fail with: inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; | ^~ cc1: all warnings being treated as errors [Fix] * ff446cd768 "selftests/powerpc: Avoid GCC 12 uninitialised variable warning" This patch can be cherry-picked into Kinetic kernel. [Test] Apply this patch to the kernel tree and build it with: sudo make -C linux/tools/testing/selftests TARGETS=powerpc With this error fixed, test compliation can finish without any issue. [Where problems could occur] Change for test case, no impact to acutal function. [Original Bug Report] Issue found with K-5.19.0-28-generic on P9 node baltar This should not be considered as a regression since ubuntu_kernel_selftests will be blocked by the net test crash before this powerpc tests can be started. This was found by manually running the test. Test build failed with: gcc -std=gnu99 -O2 -Wall -Werror -DGIT_VERSION='"unknown"' -I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include -m64 -no-pie cycles_with_mmcr2_test.c ../../harness.c ../../utils.c ../event.c ../lib.c ebb.c ebb_handler.S trace.c busy_loop.S -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test In file included from /usr/include/stdio.h:906, from cycles_with_mmcr2_test.c:6: In function ‘printf’, inlined from ‘cycles_with_mmcr2’ at cycles_with_mmcr2_test.c:81:3: /usr/include/powerpc64le-linux-gnu/bits/stdio2.h:86:10: error: ‘actual’ may be used uninitialized [-Werror=maybe-uninitialized] 86 | return __printf_chk (__USE_FORTIFY_LEVEL - 1, __fmt, __va_arg_pack ()); | ^~~ cycles_with_mmcr2_test.c: In function ‘cycles_with_mmcr2’: cycles_with_mmcr2_test.c:25:36: note: ‘actual’ was declared here 25 | uint64_t val, expected[2], actual; |^~ cc1: all warnings being treated as errors make[3]: *** [../../../lib.mk:173: /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/pmu/ebb/cycles_with_mmcr2_test] Error 1 Please find attachment for the complete build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1021.22~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1021.22~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1021.22~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1021.22~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1022.23~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1022.23~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1022.23~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1022.23~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009114] Re: kernel crash dump caused by Google Chrome
apport information
** Tags added: apport-collected
** Description changed:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0xd8/0x2c0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882078]
do_user_addr_fault+0x1c2/0x660
Mar 3 11:34:13 tteikhua kernel: [ 6927.882080] exc_page_fault+0x77/0x170
Mar 3 11:34:13 tteikhua kernel: [ 6927.882083] asm_exc_page_fault+0x27/0x30
Mar 3 11:34:13 tteikhua kernel: [ 6927.882085] RIP: 0033:0x5650c5c1875a
Mar 3 11:3
[Kernel-packages] [Bug 2009114] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651869/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fa
[Kernel-packages] [Bug 2009114] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651867/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0xd8/
[Kernel-packages] [Bug 2009114] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651868/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] hand
[Kernel-packages] [Bug 2009114] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651870/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0xd
[Kernel-packages] [Bug 2009114] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651871/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fa
[Kernel-packages] [Bug 2009114] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651872/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0xd
[Kernel-packages] [Bug 2009114] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651873/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_faul
[Kernel-packages] [Bug 2009114] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651874/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_faul
[Kernel-packages] [Bug 2009114] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651875/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle
[Kernel-packages] [Bug 2009114] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651877/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle
[Kernel-packages] [Bug 2009114] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651876/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.8
[Kernel-packages] [Bug 2009114] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651879/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle
[Kernel-packages] [Bug 2009114] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651878/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077]
[Kernel-packages] [Bug 2009114] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651883/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_m
[Kernel-packages] [Bug 2009114] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651880/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_
[Kernel-packages] [Bug 2009114] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651881/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0
[Kernel-packages] [Bug 2009114] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651882/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0
[Kernel-packages] [Bug 2009114] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2009114/+attachment/5651884/+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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Confirmed
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
This is affecting Jammy OEM 6.1.0-1008.8 # [29] ftrace - test for function event triggers[FAIL] # [58] Meta-selftest: Checkbashisms[FAIL] # [98] (instance) ftrace - test for function event triggers[FAIL] ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] [NEW] NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
Public bug reported: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: New Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009325/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
