[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
Re secureboot In my case my macbook air was not secure boot enabled but with the same no wireless observation -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015139] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bi
Hello, please check your host system's logs for things like hard drive failure. I don't know vmware, I'm not sure what exactly they would look like. Thanks ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2015139 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado Status in linux-firmware package in Ubuntu: New Bug description: Its block everything i can not use ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.10 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonny 4894 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 3 19:35:21 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DpkgHistoryLog: Start-Date: 2023-04-03 19:34:56 Commandline: aptdaemon role='role-commit-packages' sender=':1.187' Upgrade: linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.10, 20220329.git681281e4-0ubuntu3.11) ErrorMessage: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2023-03-05 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. ens33 no wireless extensions. MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=118d92a8-1f56-4180-8fc6-b52a55e9d30e ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to install/upgrade: não pode copiar dados extráidos para './lib/firmware/ath11k/QCA6390/hw2.0/amss.bin' para '/lib/firmware/ath11k/QCA6390/hw2.0/amss.bin.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2015139/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015165] Re: Update to 22.04 deletes HDMI audio
The 5.19.0.-32-generic kernel does have working HDMI audio. My thanks for telling me how to use an older (not broken) kernel. -- 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/2015165 Title: Update to 22.04 deletes HDMI audio Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: The latest update 5.19.0.-38-generic does include the HDMI audio output. The only problem is that the audio still does not work. I will try rebooting with an earlier kernel. Keep trying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Mon Apr 3 20:41:56 2023 InstallationDate: Installed on 2022-03-05 (394 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-01-15 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2015165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015165] [NEW] Update to 22.04 deletes HDMI audio
Public bug reported: The latest update 5.19.0.-38-generic does include the HDMI audio output. The only problem is that the audio still does not work. I will try rebooting with an earlier kernel. Keep trying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Mon Apr 3 20:41:56 2023 InstallationDate: Installed on 2022-03-05 (394 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-01-15 (78 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2015165 Title: Update to 22.04 deletes HDMI audio Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: The latest update 5.19.0.-38-generic does include the HDMI audio output. The only problem is that the audio still does not work. I will try rebooting with an earlier kernel. Keep trying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Mon Apr 3 20:41:56 2023 InstallationDate: Installed on 2022-03-05 (394 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-01-15 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2015165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015164] Re: btrfs send BUG or NULL pointer derefence
btrfs send ioctl requires CAP_SYS_ADMIN on the initial user namespace. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Low ** Also affects: ubuntu-kernel-tests 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/2015164 Title: btrfs send BUG or NULL pointer derefence Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Bug description: When running xfstests btrfs/187, btrfs send will cause a NULL pointer dereference or a BUG. [ 308.924126] BTRFS error (device xvdb2): did not find backref in send_root. inode=44681, offset=0, disk_byte=3193700352 found extent=3193700352 [ 310.054883] BTRFS info (device xvdb2): found 15529 extents [ 310.099436] BTRFS info (device xvdb2): relocating block group 4194304 flags 4 [ 310.369359] BTRFS info (device xvdb2): found 473 extents [ 310.393830] BTRFS info (device xvdb2): relocating block group 0 flags 2 [ 310.420026] BTRFS info (device xvdb2): found 1 extents [ 311.561421] BTRFS info (device xvdb2): relocating block group 7000293376 flags 2 [ 311.592206] BTRFS info (device xvdb2): relocating block group 6731857920 flags 4 [ 312.268390] BTRFS error (device xvdb2): parent transid verify failed on 6483984384 wanted 25 found 54 [ 312.277947] BUG: unable to handle kernel NULL pointer dereference at (null) [ 312.285471] IP: [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.285471] PGD 8000c3509067 PUD c350a067 PMD 0 [ 312.285471] Oops: [#1] SMP [ 312.285471] Modules linked in: lkp_Ubuntu_4_4_0_1128_142_aws_83(OE) binfmt_misc serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd [ 312.285471] CPU: 0 PID: 1464 Comm: btrfs Tainted: G OE K 4.4.0-1128-aws #142-Ubuntu [ 312.285471] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 312.285471] task: 8800e8f57000 ti: 8800c3518000 task.ti: 8800c3518000 [ 312.285471] RIP: 0010:[] [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.285471] RSP: 0018:8800c351bb38 EFLAGS: 00010292 [ 312.285471] RAX: RBX: 0011 RCX: 0011 [ 312.285471] RDX: 0065 RSI: 8800c351bb97 RDI: [ 312.285471] RBP: 8800c351bb68 R08: 00018140 R09: 00019140 [ 312.421177] R10: ea0002a021c0 R11: R12: 8800c351bb97 [ 312.421177] R13: 8800c351bc45 R14: R15: 8800c351bc3c [ 312.421177] FS: 7fd136bdd8c0() GS:88010b20() knlGS: [ 312.421177] CS: 0010 DS: ES: CR0: 80050033 [ 312.421177] CR2: CR3: c34dc000 CR4: 00160670 [ 312.421177] Stack: [ 312.421177] 0674 8800b62d3d80 8800c351bc45 [ 312.421177] 0002 8800c351bc3c 8800c351bb78 c014fba2 [ 312.421177] 8800c351bbd8 c01088df 8800c351bc45 0eff8800c1d2d000 [ 312.421177] Call Trace: [ 312.421177] [] btrfs_node_key+0x22/0x30 [btrfs] [ 312.421177] [] tree_advance+0x12f/0x1d0 [btrfs] [ 312.421177] [] btrfs_compare_trees+0x264/0x720 [btrfs] [ 312.492582] BTRFS info (device xvdb2): found 2362 extents [ 312.421177] [] ? process_all_refs+0x200/0x200 [btrfs] [ 312.421177] [] btrfs_ioctl_send+0xf62/0x11c0 [btrfs] [ 312.421177] [] ? ___slab_alloc+0x207/0x4b0 [ 312.421177] [] ? update_curr+0x79/0x170 [ 312.421177] [] btrfs_ioctl+0x29d/0x26a0 [btrfs] [ 312.421177] [] ? update_cfs_shares+0xb1/0xf0 [ 312.530672] BTRFS info (device xvdb2): relocating block group 6463422464 flags 4 [ 312.421177] [] ? check_preempt_wakeup+0xfa/0x220 [ 312.421177] [] do_vfs_ioctl+0x2af/0x4b0 [ 312.421177] [] ? _do_fork+0xec/0x360 [ 312.421177] [] SyS_ioctl+0x79/0x90 [ 312.421177] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ 312.421177] Code: 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 49 89 fe 53 49 89 f4 48 89 cb 48 83 ec 08 <48> 8b 3f 49 8b 4e 08 48 89 fe 81 e6 ff 0f 00 00 4c 8d 2c 16 4d [ 312.421177] RIP [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.421177] RSP [ 312.421177] CR2:
[Kernel-packages] [Bug 2015164] Re: btrfs send BUG or NULL pointer derefence
Adding ubuntu-kernel-tests as this won't be fixed in the kernel, so we should skip this particular test when running on 4.4. Cascardo. ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: ubuntu-kernel-tests Status: New => Triaged -- 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/2015164 Title: btrfs send BUG or NULL pointer derefence Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Bug description: When running xfstests btrfs/187, btrfs send will cause a NULL pointer dereference or a BUG. [ 308.924126] BTRFS error (device xvdb2): did not find backref in send_root. inode=44681, offset=0, disk_byte=3193700352 found extent=3193700352 [ 310.054883] BTRFS info (device xvdb2): found 15529 extents [ 310.099436] BTRFS info (device xvdb2): relocating block group 4194304 flags 4 [ 310.369359] BTRFS info (device xvdb2): found 473 extents [ 310.393830] BTRFS info (device xvdb2): relocating block group 0 flags 2 [ 310.420026] BTRFS info (device xvdb2): found 1 extents [ 311.561421] BTRFS info (device xvdb2): relocating block group 7000293376 flags 2 [ 311.592206] BTRFS info (device xvdb2): relocating block group 6731857920 flags 4 [ 312.268390] BTRFS error (device xvdb2): parent transid verify failed on 6483984384 wanted 25 found 54 [ 312.277947] BUG: unable to handle kernel NULL pointer dereference at (null) [ 312.285471] IP: [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.285471] PGD 8000c3509067 PUD c350a067 PMD 0 [ 312.285471] Oops: [#1] SMP [ 312.285471] Modules linked in: lkp_Ubuntu_4_4_0_1128_142_aws_83(OE) binfmt_misc serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd [ 312.285471] CPU: 0 PID: 1464 Comm: btrfs Tainted: G OE K 4.4.0-1128-aws #142-Ubuntu [ 312.285471] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 312.285471] task: 8800e8f57000 ti: 8800c3518000 task.ti: 8800c3518000 [ 312.285471] RIP: 0010:[] [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.285471] RSP: 0018:8800c351bb38 EFLAGS: 00010292 [ 312.285471] RAX: RBX: 0011 RCX: 0011 [ 312.285471] RDX: 0065 RSI: 8800c351bb97 RDI: [ 312.285471] RBP: 8800c351bb68 R08: 00018140 R09: 00019140 [ 312.421177] R10: ea0002a021c0 R11: R12: 8800c351bb97 [ 312.421177] R13: 8800c351bc45 R14: R15: 8800c351bc3c [ 312.421177] FS: 7fd136bdd8c0() GS:88010b20() knlGS: [ 312.421177] CS: 0010 DS: ES: CR0: 80050033 [ 312.421177] CR2: CR3: c34dc000 CR4: 00160670 [ 312.421177] Stack: [ 312.421177] 0674 8800b62d3d80 8800c351bc45 [ 312.421177] 0002 8800c351bc3c 8800c351bb78 c014fba2 [ 312.421177] 8800c351bbd8 c01088df 8800c351bc45 0eff8800c1d2d000 [ 312.421177] Call Trace: [ 312.421177] [] btrfs_node_key+0x22/0x30 [btrfs] [ 312.421177] [] tree_advance+0x12f/0x1d0 [btrfs] [ 312.421177] [] btrfs_compare_trees+0x264/0x720 [btrfs] [ 312.492582] BTRFS info (device xvdb2): found 2362 extents [ 312.421177] [] ? process_all_refs+0x200/0x200 [btrfs] [ 312.421177] [] btrfs_ioctl_send+0xf62/0x11c0 [btrfs] [ 312.421177] [] ? ___slab_alloc+0x207/0x4b0 [ 312.421177] [] ? update_curr+0x79/0x170 [ 312.421177] [] btrfs_ioctl+0x29d/0x26a0 [btrfs] [ 312.421177] [] ? update_cfs_shares+0xb1/0xf0 [ 312.530672] BTRFS info (device xvdb2): relocating block group 6463422464 flags 4 [ 312.421177] [] ? check_preempt_wakeup+0xfa/0x220 [ 312.421177] [] do_vfs_ioctl+0x2af/0x4b0 [ 312.421177] [] ? _do_fork+0xec/0x360 [ 312.421177] [] SyS_ioctl+0x79/0x90 [ 312.421177] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ 312.421177] Code: 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 49 89 fe 53 49 89 f4 48 89 cb 48 83 ec 08 <48> 8b 3f 49 8b 4e 08 48 89 fe 81 e6 ff 0f 00 00 4c 8d 2c 16 4d [ 312.421177] RIP [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.421177] RSP [ 312.421177] CR2: [ 312.623966] ---[ end trace 6b9120b9ed5a31b6 ]--- To manage notifications about this bug go to:
[Kernel-packages] [Bug 2015164] [NEW] btrfs send BUG or NULL pointer derefence
Public bug reported: When running xfstests btrfs/187, btrfs send will cause a NULL pointer dereference or a BUG. [ 308.924126] BTRFS error (device xvdb2): did not find backref in send_root. inode=44681, offset=0, disk_byte=3193700352 found extent=3193700352 [ 310.054883] BTRFS info (device xvdb2): found 15529 extents [ 310.099436] BTRFS info (device xvdb2): relocating block group 4194304 flags 4 [ 310.369359] BTRFS info (device xvdb2): found 473 extents [ 310.393830] BTRFS info (device xvdb2): relocating block group 0 flags 2 [ 310.420026] BTRFS info (device xvdb2): found 1 extents [ 311.561421] BTRFS info (device xvdb2): relocating block group 7000293376 flags 2 [ 311.592206] BTRFS info (device xvdb2): relocating block group 6731857920 flags 4 [ 312.268390] BTRFS error (device xvdb2): parent transid verify failed on 6483984384 wanted 25 found 54 [ 312.277947] BUG: unable to handle kernel NULL pointer dereference at (null) [ 312.285471] IP: [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.285471] PGD 8000c3509067 PUD c350a067 PMD 0 [ 312.285471] Oops: [#1] SMP [ 312.285471] Modules linked in: lkp_Ubuntu_4_4_0_1128_142_aws_83(OE) binfmt_misc serio_raw ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd [ 312.285471] CPU: 0 PID: 1464 Comm: btrfs Tainted: G OE K 4.4.0-1128-aws #142-Ubuntu [ 312.285471] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [ 312.285471] task: 8800e8f57000 ti: 8800c3518000 task.ti: 8800c3518000 [ 312.285471] RIP: 0010:[] [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.285471] RSP: 0018:8800c351bb38 EFLAGS: 00010292 [ 312.285471] RAX: RBX: 0011 RCX: 0011 [ 312.285471] RDX: 0065 RSI: 8800c351bb97 RDI: [ 312.285471] RBP: 8800c351bb68 R08: 00018140 R09: 00019140 [ 312.421177] R10: ea0002a021c0 R11: R12: 8800c351bb97 [ 312.421177] R13: 8800c351bc45 R14: R15: 8800c351bc3c [ 312.421177] FS: 7fd136bdd8c0() GS:88010b20() knlGS: [ 312.421177] CS: 0010 DS: ES: CR0: 80050033 [ 312.421177] CR2: CR3: c34dc000 CR4: 00160670 [ 312.421177] Stack: [ 312.421177] 0674 8800b62d3d80 8800c351bc45 [ 312.421177] 0002 8800c351bc3c 8800c351bb78 c014fba2 [ 312.421177] 8800c351bbd8 c01088df 8800c351bc45 0eff8800c1d2d000 [ 312.421177] Call Trace: [ 312.421177] [] btrfs_node_key+0x22/0x30 [btrfs] [ 312.421177] [] tree_advance+0x12f/0x1d0 [btrfs] [ 312.421177] [] btrfs_compare_trees+0x264/0x720 [btrfs] [ 312.492582] BTRFS info (device xvdb2): found 2362 extents [ 312.421177] [] ? process_all_refs+0x200/0x200 [btrfs] [ 312.421177] [] btrfs_ioctl_send+0xf62/0x11c0 [btrfs] [ 312.421177] [] ? ___slab_alloc+0x207/0x4b0 [ 312.421177] [] ? update_curr+0x79/0x170 [ 312.421177] [] btrfs_ioctl+0x29d/0x26a0 [btrfs] [ 312.421177] [] ? update_cfs_shares+0xb1/0xf0 [ 312.530672] BTRFS info (device xvdb2): relocating block group 6463422464 flags 4 [ 312.421177] [] ? check_preempt_wakeup+0xfa/0x220 [ 312.421177] [] do_vfs_ioctl+0x2af/0x4b0 [ 312.421177] [] ? _do_fork+0xec/0x360 [ 312.421177] [] SyS_ioctl+0x79/0x90 [ 312.421177] [] entry_SYSCALL_64_fastpath+0x22/0xd0 [ 312.421177] Code: 40 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 49 89 fe 53 49 89 f4 48 89 cb 48 83 ec 08 <48> 8b 3f 49 8b 4e 08 48 89 fe 81 e6 ff 0f 00 00 4c 8d 2c 16 4d [ 312.421177] RIP [] read_extent_buffer+0x1f/0x190 [btrfs] [ 312.421177] RSP [ 312.421177] CR2: [ 312.623966] ---[ end trace 6b9120b9ed5a31b6 ]--- ** Affects: ubuntu-kernel-tests Importance: Medium Status: Triaged ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Low Status: Won't Fix -- 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/2015164 Title: btrfs send BUG or NULL pointer derefence Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Bug description: When running xfstests btrfs/187, btrfs send will cause a NULL pointer dereference or a BUG. [ 308.924126] BTRFS error (device xvdb2): did not find backref in send_root. inode=44681, offset=0, disk_byte=3193700352
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
> I can enable that successfully from the live session but > wireless networks are not available in network manager This is expected if SecureBoot is enabled on your system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
In a live session 'ubuntu-drivers install' indicates that "All the available drivers are already installed". Additionally, the bcma kernel module is loaded and used by my broadcom device. However, no wireless device is currently available and the "Additional Drivers" section of software-properties-gtk is somewhat confusing because the two radio buttons say "Using dkms..." and "Do not use device" but "Do not use device" is selected. (I wouldn't expect the words "Using" if it isn't being used.) Using software-properties-gtk to install the additional drivers did not end up allowing the wireless device to be available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
I was also able to recreate this today using the ubuntu-desktop-legacy- amd64 image with serial 20230403. I neglected to check the 'ubuntu- drivers install' in the live environment but will run through the process again. bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers devices == /sys/devices/pci:00/:00:02.4/:05:00.0 == modalias : pci:v14E4d43B1sv1043sd85BAbc02sc80i00 vendor : Broadcom Inc. and subsidiaries model: BCM4352 802.11ac Wireless Network Adapter driver : broadcom-sta-dkms - distro non-free bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers list broadcom-sta-dkms, (kernel modules provided by broadcom-sta-dkms) bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ apt-cache policy broadcom-sta-dkms broadcom-sta-dkms: Installed: (none) Candidate: 6.30.223.271-23ubuntu1 Version table: 6.30.223.271-23ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/restricted amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu lunar/restricted i386 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015136] [NEW] Support hardware stats for tc actions
Public bug reported:
Support hardware stats for tc actions
* Explain the bug(s)
tc hardware stats are not offloaded from some offloaded actions (pedit, sample,
skbedit)
* brief explanation of fixes
Implement the necessary callbacks to report back stats for these actions.
* How to test
Configure two mlx5 rep devices and VFs.
Add tc offloaded tc rules with pedit action, and hit that rule with traffic
e.g:
mac1=`cat /sys/class/net/$VF/address`
mac2=`cat /sys/class/net/$VF2/address`
fake_mac="20:22:33:44:55:66"
IP1="7.7.7.1"
IP2="7.7.7.2"
function config_vf() {
local ns=$1
local vf=$2
local rep=$3
local ip=$4 # optional
local mac=$5 # optional
local prefix=24
if [[ "$ip" == *":"* ]]; then
# ipv6
prefix=64
fi
echo "[$ns] VF $vf (${mac:+$mac/}$ip) -> REP $rep"
ip address flush dev $rep
ip link set dev $rep up
ip netns add $ns
${mac:+ip link set $vf address $mac}
ip link set $vf netns $ns
${ip:+ip -netns $ns address replace dev $vf $ip/$prefix}
ip -netns $ns link set $vf up
}
tc qdisc add dev $REP ingress
tc qdisc add dev $REP2 ingress
config_vf ns0 $VF $REP $IP1
config_vf ns1 $VF2 $REP2 $IP2
tc filter add dev $REP ingress protocol arp prio 1 flower \
action mirred egress redirect dev $REP2
tc filter add dev $REP2 ingress protocol arp prio 1 flower \
action mirred egress redirect dev $REP
echo "add ct rules"
# req
tc filter add dev $REP ingress protocol ip prio 2 flower \
dst_mac $fake_mac ct_state -trk \
action ct action goto chain 1
tc filter add dev $REP ingress protocol ip chain 1 prio 2 flower \
dst_mac $fake_mac ct_state +trk+new \
action ct commit \
action pedit ex munge eth dst set $mac2 pipe \
action mirred egress redirect dev $REP2
tc filter add dev $REP ingress protocol ip chain 1 prio 2 flower \
dst_mac $fake_mac ct_state +trk+est \
action pedit ex munge eth dst set $mac2 pipe \
action mirred egress redirect dev $REP2
# reply chain0,ct -> chain1,fwd
tc filter add dev $REP2 ingress protocol ip prio 2 flower \
dst_mac $mac1 \
action ct action goto chain 1
tc filter add dev $REP2 ingress protocol ip prio 2 chain 1 flower \
dst_mac $mac1 ct_state +trk+est \
action mirred egress redirect dev $REP
echo "run traffic"
ip netns exec ns1 timeout 13 iperf -s &
sleep 0.5
ip netns exec ns0 ip n r $IP2 dev $VF lladdr $fake_mac
ip netns exec ns0 timeout 13 iperf -t 12 -c $IP2 &
tc -s filter show dev $REP ingress
see pedit hw counters are advancing (or not if patches not applied):
filter pref 2 flower
filter pref 2 flower handle 0x1
dst_mac 20:22:33:44:55:66
eth_type ipv4
ct_state -trk
in_hw in_hw_count 1
action order 1: ct zone 0 pipe
index 1 ref 1 bind 1 installed 2 sec used 0 sec firstused 2 sec
Action statistics:
Sent 6521850590 bytes 4307703 pkt (dropped 0, overlimits 0 requeues 0)
Sent software 112 bytes 2 pkt
Sent hardware 6521850478 bytes 4307701 pkt
backlog 0b 0p requeues 0
action order 2: gact action goto chain 1
random type none pass val 0
index 1 ref 1 bind 1 installed 2 sec used 0 sec firstused 2 sec
Action statistics:
Sent 6521850590 bytes 4307703 pkt (dropped 0, overlimits 0 requeues 0)
Sent software 112 bytes 2 pkt
Sent hardware 6521850478 bytes 4307701 pkt
backlog 0b 0p requeues 0
* What it could break.
Hardware counters of tc pedit, sample, and skbedit actions.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2015136
Title:
Support hardware stats for tc actions
Status in linux-bluefield package in Ubuntu:
New
Bug description:
Support hardware stats for tc actions
* Explain the bug(s)
tc hardware stats are not offloaded from some offloaded actions (pedit,
sample, skbedit)
* brief explanation of fixes
Implement the necessary callbacks to report back stats for these actions.
* How to test
Configure two mlx5 rep devices and VFs.
Add tc offloaded tc rules with pedit action, and hit that rule with traffic
e.g:
mac1=`cat /sys/class/net/$VF/address`
mac2=`cat /sys/class/net/$VF2/address`
fake_mac="20:22:33:44:55:66"
IP1="7.7.7.1"
IP2="7.7.7.2"
function config_vf() {
local ns=$1
local vf=$2
local rep=$3
local ip=$4 # optional
local mac=$5 # optional
local prefix=24
if [[ "$ip" == *":"* ]]; then
# ipv6
prefix=64
fi
echo "[$ns] VF $vf (${mac:+$mac/}$ip) -> REP $rep"
ip address flush dev $rep
ip link set dev $rep up
ip netns add $ns
${mac:+ip link set $vf address $mac}
ip link set $vf netns $ns
[Kernel-packages] [Bug 2015131] [NEW] package linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-38-generic package post-installation script sub
Public bug reported: updating using apt HW is an HP Elitebook 840 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-modules-5.15.0-69-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Apr 3 21:26:31 2023 ErrorMessage: installed linux-image-5.19.0-38-generic package post-installation script subprocess returned error exit status 134 InstallationDate: Installed on 2023-02-18 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-38-generic package post-installation script subprocess returned error exit status 134 UpgradeStatus: Upgraded to jammy on 2023-02-18 (44 days ago) ** Affects: linux-signed-hwe-5.19 (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 linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2015131 Title: package linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-38-generic package post- installation script subprocess returned error exit status 134 Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: updating using apt HW is an HP Elitebook 840 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-modules-5.15.0-69-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Apr 3 21:26:31 2023 ErrorMessage: installed linux-image-5.19.0-38-generic package post-installation script subprocess returned error exit status 134 InstallationDate: Installed on 2023-02-18 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-38-generic package post-installation script subprocess returned error exit status 134 UpgradeStatus: Upgraded to jammy on 2023-02-18 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2015131/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015106] Re: linux kernel 5.19 apport bug logs
** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Incomplete -- 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/2015106 Title: linux kernel 5.19 apport bug logs Status in linux-signed-hwe-5.19 package in Ubuntu: Incomplete Bug description: linux kernel 5.19 apport bug logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 19:09:36 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.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/2015106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013088] uaccess clear_user() fix
--- Comment on attachment From h.carst...@de.ibm.com 2023-04-03 14:32 EDT--- Attached patch applies to 18.04 and 20.04. ** Attachment added: "uaccess clear_user() fix" https://bugs.launchpad.net/bugs/2013088/+attachment/5660553/+files/s390-uaccess.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: In Progress Bug description: SRU Bug Template: = [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [ Test Plan ] * A little test program in C is used for testing (?) * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 right now, and will submit an SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.182.03-0ubuntu1
---
nvidia-graphics-drivers-470-server (470.182.03-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_6.2.patch.
-- Alberto Milone Fri, 24 Mar 2023
11:18:45 +
** Changed in: nvidia-graphics-drivers-470-server (Ubuntu)
Status: Triaged => Fix Released
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.105.17-0ubuntu1
---
nvidia-graphics-drivers-525-server (525.105.17-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
* debian/templates/control.in:
- Switch to libcuda.so.1 and libnvidia-ml.so.1 provides.
-- Alberto Milone Mon, 27 Mar 2023
18:07:22 +
** Changed in: nvidia-graphics-drivers-525-server (Ubuntu)
Status: Triaged => Fix Released
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.182.03-0ubuntu1
---
nvidia-graphics-drivers-470 (470.182.03-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_6.2.patch.
-- Alberto Milone Mon, 27 Mar 2023
09:30:58 +
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Triaged => Fix Released
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in fabric-manager-470 source package in
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.236.01-0ubuntu1
---
nvidia-graphics-drivers-450-server (450.236.01-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
* debian/dkms_nvidia/patches/buildfix_kernel_6.2.patch:
- Refresh for 450.236.01.
-- Alberto Milone Wed, 22 Mar 2023
15:43:35 +
** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
Status: Triaged => Fix Released
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in fabric-manager-470
[Kernel-packages] [Bug 2013758] Re: Add support for 200G/400G speed to bond
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Fix Released ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => Bodong Wang (bodong-wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2013758 Title: Add support for 200G/400G speed to bond Status in linux-bluefield package in Ubuntu: Fix Released Status in linux-bluefield source package in Focal: In Progress Bug description: SRU Justification: [Impact] * 5.4 kernel can't work with bond for 200G/400G NIC [Fix] * cherry pick the commits to support 200G/400G [Test Plan] * Test on 200G/400G bond To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013349] Re: Azure: smb3: allow deferred close timeout to be configurable
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2013349
Title:
Azure: smb3: allow deferred close timeout to be configurable
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-azure source package in Kinetic:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft has requested the ability to set a deferred close timeout to
SMB3 connections.
Upstream commit 5efdd9122eff772eae2feae9f0fc0ec02d4846a3 ('smb3: allow
deferred close timeout to be configurable')
commit 7e0e76d99079be13c9961dde7c93b2d1ee665af4 ('smb3: lower default
deferred close timeout to address perf regression')
commit 47f9e4c924025c5be87959d3335e66fcbb7f6b5c ('keys: Do not cache key in
task struct if key is requested from kernel thread')
[ Regression Potential ]
This patch was committed to 6.0. Possible regressions include
connections not closing, or closing later then the timeout would
indicate.
[ Test Plan ]
Microsoft tested.
[ Other Info ]
SF: #00357322
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2013349/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015106] [NEW] linux kernel 5.19 apport bug logs
Public bug reported: linux kernel 5.19 apport bug logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 19:09:36 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: linux kernel 5.19 apport bug logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 19:09:36 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fi_FI.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2015106 Title: linux kernel 5.19 apport bug logs Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: linux kernel 5.19 apport bug logs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-38-generic 5.19.0-38.39~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 19:09:36 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.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/2015106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014015] Re: Azure: Add new MANA VF performance counters for easier troubleshooting
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Won't Fix -- 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/2014015 Title: Azure: Add new MANA VF performance counters for easier troubleshooting Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Won't Fix Status in linux-azure source package in Kinetic: In Progress Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] Add new MANA VF performance counters for easier troubleshooting. [Regression potential] Regression potential is low given that this a new feature. [Test Plan] Microsoft tested. [Other Info] SF: #00357417 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2014015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012559] Re: 6.2 kernel won't boot, may be nvidia related?
Apart from having to manually install the new versions of some of the dependencies (libnvidia-cfg1-470, libnvidia-fbc1-470, libnvidia-ifr1-470 and nvidia-utils-470), this now seems to be working. -- 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/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in linux source package in Lunar: Confirmed Status in nvidia-graphics-drivers-515 source package in Lunar: In Progress Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-515-server -
515.105.01-0ubuntu1
---
nvidia-graphics-drivers-515-server (515.105.01-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
* debian/templates/control.in:
- Switch to libcuda.so.1 and libnvidia-ml.so.1 provides.
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_6.2.patch.
-- Alberto Milone Fri, 24 Mar 2023
14:26:58 +
** Changed in: nvidia-graphics-drivers-515-server (Ubuntu)
Status: Triaged => Fix Released
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
New drivers are available in proposed (e.g. 515.105.01-0ubuntu1), can you test them and and report your results? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 RCX: 7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RDX: RSI: 55f373889af0 RDI: 0012 mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08: R09: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars 27 10:33:54
[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix
** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015097] Re: Kernel crash during Mellanox performance testing
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Description changed: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test - * IBM performance test + * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic -- 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/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015097] 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 2015097 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/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015097] [NEW] Kernel crash during Mellanox performance testing
Public bug reported: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012529] Autopkgtest regression report (nvidia-graphics-drivers-515/515.105.01-0ubuntu0.22.10.1)
All autopkgtests for the newly accepted nvidia-graphics-drivers-515
(515.105.01-0ubuntu0.22.10.1) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
pyopencl/2022.1.6-2 (armhf)
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#nvidia-graphics-drivers-515
[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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
This bug was fixed in the package nvidia-graphics-drivers-515 -
515.105.01-0ubuntu1
---
nvidia-graphics-drivers-515 (515.105.01-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
* debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.
- Switch to libcuda.so.1 and libnvidia-ml.so.1 provides.
* debian/templates/dkms_nvidia{_open}.conf.in:
- Drop buildfix_kernel_6.2.patch.
-- Alberto Milone Mon, 27 Mar 2023
10:02:56 +
** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
Status: Triaged => Fix Released
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in
[Kernel-packages] [Bug 2012559] Re: 6.2 kernel won't boot, may be nvidia related?
The latest drivers should be available in Lunar now. Please upgrade, and see if it helps. -- 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/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in linux source package in Lunar: Confirmed Status in nvidia-graphics-drivers-515 source package in Lunar: In Progress Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
** Also affects: fabric-manager-470 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fabric-manager-450 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fabric-manager-515 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fabric-manager-525 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libnvidia-nscq-450 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libnvidia-nscq-470 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libnvidia-nscq-515 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libnvidia-nscq-525 (Ubuntu)
Importance: Undecided
Status: New
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
** Information type changed from Private Security to Public Security
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in fabric-manager-515 package in Ubuntu:
New
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in libnvidia-nscq-515 package in Ubuntu:
New
Status in libnvidia-nscq-525 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in fabric-manager-515 source package in Bionic:
New
Status in fabric-manager-525 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in libnvidia-nscq-515 source package in Bionic:
New
Status in libnvidia-nscq-525 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-515 source package in Bionic:
New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
New
Status in nvidia-graphics-drivers-525 source package in Bionic:
New
Status in nvidia-graphics-drivers-525-server source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-515 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-515 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-515 source package in Focal:
New
Status in nvidia-graphics-drivers-515-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-515 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-515 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in linux-restricted-modules source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-515 source package in Jammy:
New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in fabric-manager-470 source package in Kinetic:
New
Status in fabric-manager-515 source package in Kinetic:
New
Status in fabric-manager-525 source package in Kinetic:
New
Status in libnvidia-nscq-450 source package in Kinetic:
New
Status in libnvidia-nscq-470 source package in Kinetic:
New
Status in libnvidia-nscq-515 source package in Kinetic:
New
Status in libnvidia-nscq-525 source package in Kinetic:
New
Status in
[Kernel-packages] [Bug 2009882] Re: Linux 5.4.0-144-generic x86_64 multithread / fork issues
Thanks Matt. I can confirm our issue is completely gone and performance is back with 5.4.0-146-generic. Alfredo -- 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/2009882 Title: Linux 5.4.0-144-generic x86_64 multithread / fork issues Status in linux package in Ubuntu: Confirmed Bug description: We have same servers already running in 5.4.0-122 , 126, 128 and 131 releases with no issues whatsoever and exceptional good performance. They basically have either Apache/2.4.41/mod_php7.4 or Apache/2.4.41/mpm_event with phm7.4-fpm setups, all working perfect. When we load kernel 5.4.0-144 CPU processing go thru the roof, and process kworker/u17:0-xprtiod show at the top. Both setups perform badly with Apache performance going avg 200ms/req in older kernels to over 4,500ms/req in this 144 release. CPU usage from avg 0.4% to over 50% under same traffic and requests rate. We just reloaded old kernels back, via /etc/default/grub, and performance is right back. Same packages, same services, everything the same but the Linux kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-144-generic 5.4.0-144.161 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 13:21 seq crw-rw 1 root audio 116, 33 Mar 9 13:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Thu Mar 9 13:22:31 2023 InstallationDate: Installed on 2021-11-17 (477 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-144-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/12/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32
Hello Heitor, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.15 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Committed Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993665] Re: Update the 470-server NVIDIA driver
This bug was fixed in the package libnvidia-nscq-470 - 470.182.03-0ubuntu1 --- libnvidia-nscq-470 (470.182.03-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2012529). -- Alberto Milone Mon, 27 Mar 2023 16:00:16 + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in fabric-manager-470 source package in Kinetic: Fix Released Status in libnvidia-nscq-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993665] Re: Update the 470-server NVIDIA driver
This bug was fixed in the package fabric-manager-470 - 470.182.03-0ubuntu1 --- fabric-manager-470 (470.182.03-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2012529). -- Alberto Milone Mon, 27 Mar 2023 17:10:12 + ** Changed in: fabric-manager-470 (Ubuntu) Status: In Progress => Fix Released ** Changed in: libnvidia-nscq-470 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in fabric-manager-470 source package in Kinetic: Fix Released Status in libnvidia-nscq-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
** Tags removed: verification-needed-bionic verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid 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 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-43-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.0.0-43.47~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-43-generic N/A linux-backports-modules-5.0.0-43-generic N/A linux-firmware1.173.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux
[Kernel-packages] [Bug 2014037] Re: ACPI bios error on dell laptop.
** 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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660388/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660387/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660389/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660385/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660386/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660379/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660384/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Confirmed Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660381/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660382/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660380/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660383/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660378/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660377/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660374/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660375/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660376/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660373/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660372/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014037] Re: ACPI bios error on dell laptop.
apport information ** Tags added: apport-collected focal ** Description changed: - Identified a bug ACPI bios error on dell laptop. In kernel version - 5.14.0-1058-oem no existing a bug, after update kernel to - 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu - version used is a 20.04 + Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.25 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: juliano 27180 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2023-03-11 (23 days ago) + InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) + MachineType: Dell Inc. Inspiron 15 3511 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-69-generic N/A + linux-backports-modules-5.15.0-69-generic N/A + linux-firmware 1.187.36 + Tags: focal + Uname: Linux 5.15.0-69-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/27/2022 + dmi.bios.release: 1.18 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.18.2 + dmi.board.name: 0XNM93 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 15 3511 + dmi.product.sku: 0AB0 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2014037/+attachment/5660371/+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/2014037 Title: ACPI bios error on dell laptop. Status in linux package in Ubuntu: Incomplete Bug description: Identified a bug ACPI bios error on dell laptop. In kernel version 5.14.0-1058-oem no existing a bug, after update kernel to 5.15.0-67-generic or 5.15.0-69-generic the bug is throwed. Ubuntu version used is a 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juliano 27180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2023-03-11 (23 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: Dell Inc. Inspiron 15 3511 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=6b3928ba-140b-49cd-844c-4b7461a8dfde ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 1.187.36 Tags: focal Uname: Linux 5.15.0-69-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/27/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.2 dmi.board.name: 0XNM93 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.2:bd10/27/2022:br1.18:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0XNM93:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2014037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
@ahasenack in lunar wireguard dropped depends on neither. Because it is expected to be built in, and the wireguard-dkms module is out of date, like a lot. Please discuss this further with the SRU team on https://bugs.launchpad.net/ubuntu/kinetic/+source/wireguard/+bug/2008086 as kernel's team position is that nobody should be using wireguard-dkms in jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix
** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012559] Re: 6.2 kernel won't boot, may be nvidia related?
Update: Installing the latest 470 driver (version 470.182.03) from the Nidia website resolves the problem for my GTX660. The version in the Ubuntu repositories is 470.161.03-0ubuntu2 as of the Lunar beta, so I guess this just needs the latest version packaging. -- 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/2012559 Title: 6.2 kernel won't boot, may be nvidia related? Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in linux source package in Lunar: Confirmed Status in nvidia-graphics-drivers-515 source package in Lunar: In Progress Bug description: After installing most recent Lunar updates, linux- image-6.2.0-18-generic won't boot. First attempt to boot hung with gpu-manager service and other services blocked, something related to nvidia seemed to be going wrong. Subsequent attempts blocked at systemd-modules, I believe. Reverting to 6.1, boots fine. It did boot up enough on one attempt that I was able to SSH in, even though I couldn't log in on the console because it never got the point of starting up the session manager or init on the other VTs. I'm attaching a journalctl log from before the first reboot attempt. Perhaps there is something illuminating in there; I honestly can't tell. Note that while trying to get it to finish booting the first time when I was SSH'd in I did kill some processes, so you'll see that in the log. But just to reiterate, I attempted booting several times after that and it never came up to the point of being on the network. I thought maybe it might be a DisplayLink issue, but the problem persisted even when I rebooted without the DisplayLink hub plugged in. Note also that as I said above I had to revert to 6.1 to get it to boot, so you'll see that as the last (successful) boot attempt in the log file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-18-generic 6.2.0-18.18 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 22 16:33:06 2023 InstallationDate: Installed on 2019-01-02 (1540 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Predator G6-710 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.1.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-16-generic N/A linux-backports-modules-6.1.0-16-generic N/A linux-firmware20230316.gitc761dbe8-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2022-11-24 (118 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Yesterday I did an Intel update under w10 (dual Boot) for the realtek driver and it failed under Intel's install program. I tried a download version and it repeatedly failed to install properly although it went through the motions. Upon trying VLC it crashed immediately. It looks like it might be a Realtek Issue which has been carried through to Linux in the upgrade process. -- 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/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012743] Re: Support Nvidia BlueField-3 GPIO driver and pin controller
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Jammy) Assignee: (unassigned) => Asmaa Mnebhi (asmaam) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2012743 Title: Support Nvidia BlueField-3 GPIO driver and pin controller Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Support the BlueField-3 SoC GPIO driver for handling interrupts and providing the option to change the direction and value of a GPIO. Support the BlueField-3 SoC pin controller driver for allowing a select number of GPIO pins to be manipulated from userspace or the kernel. All these changes have been accepted for upstream but most of them are not yet in the tree/branches. PLEASE NOTE: This change is dependent on changes done in the ACPI tables. So the UEFI image needs to be updated accordingly. [Fix] * Add support for the BlueField-3 SoC GPIO driver. This driver configures and handles GPIO interrupts. It also enables a user to manipulate certain GPIO pins via libgpiod tools or other kernel drivers. The usable pins are defined via the "gpio-reserved-ranges" property. * NVIDIA BlueField-3 SoC has a few pins that can be used as GPIOs or take the default hardware functionality. Add a driver for the pin muxing. * The following gpiolib commits are bug fixes and are required for the gpio driver to work: 443a0a0f0cf4f432c7af6654b7f2f920d411d379 Although the following have been accepted by maintainers, they are not present in any tree/branch yet so these will be pushed as SAUCE for now: [PATCH v4] gpio: mmio: handle "ngpios" properly in bgpio_init() [PATCH v1] gpio: mmio: fix calculation of bgpio_bits [Test Case] * Check if the gpio-mlxbf3 driver is loaded * Check if the pinctrl-mlxbf3 driver is loaded * check if the mlxbf-gige driver is loaded * check if the pwr-mlxbf driver is loaded * Check that the oob_net0 interface is up and operational * Do reset and powercycle and check the oob_net0 interface again * Test power GPIO interrupt on BF3. [Regression Potential] * The Mellanox drivers could fail to be loaded. * The mlxbf-gige PHY interrupt or pwr-mlxbf interrupt could fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015001] Re: Missing zfs module
** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Lunar) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2015001 Title: Missing zfs module Status in linux-raspi package in Ubuntu: Fix Committed Status in linux-raspi source package in Lunar: Fix Committed Bug description: I upgraded my kinetic raspiberry pi4 to lunar, and to my surprise the zfs module is missing: root@pi4:~# apt-file find zfs.ko linux-modules-6.2.0-1002-aws: /lib/modules/6.2.0-1002-aws/kernel/zfs/zfs.ko linux-modules-6.2.0-1002-azure: /lib/modules/6.2.0-1002-azure/kernel/zfs/zfs.ko linux-modules-6.2.0-1002-lowlatency: /lib/modules/6.2.0-1002-lowlatency/kernel/zfs/zfs.ko linux-modules-6.2.0-1002-lowlatency-64k: /lib/modules/6.2.0-1002-lowlatency-64k/kernel/zfs/zfs.ko linux-modules-6.2.0-1002-oracle: /lib/modules/6.2.0-1002-oracle/kernel/zfs/zfs.ko linux-modules-6.2.0-1004-gcp: /lib/modules/6.2.0-1004-gcp/kernel/zfs/zfs.ko linux-modules-6.2.0-18-generic: /lib/modules/6.2.0-18-generic/kernel/zfs/zfs.ko linux-modules-6.2.0-18-generic-64k: /lib/modules/6.2.0-18-generic-64k/kernel/zfs/zfs.ko root@pi4:~# uname -a Linux pi4 6.2.0-1003-raspi #3-Ubuntu SMP PREEMPT Thu Mar 9 19:24:05 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux root@pi4:~# modprobe zfs modprobe: FATAL: Module zfs not found in directory /lib/modules/6.2.0-1003-raspi root@pi4:~# zfs mount -al The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them. This pi4 system serves as a NAS to my local network, and now it can't mount my external ZFS disks. I'm resorting to a dkms build, which will take a while as you can imagine :( --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 20 14:17 seq crw-rw 1 root audio 116, 33 Mar 20 14:17 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.2.0-1003-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown CloudBuildName: server CloudSerial: DistroRelease: Ubuntu 23.04 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 002: ID 152d:0561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS551 - Sharkoon SATA QuickPort Duo Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux-raspi 6.2.0.1003.4 PackageArchitecture: arm64 PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color XDG_RUNTIME_DIR= ProcFB: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:6B:96:DB vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc ProcVersionSignature: Ubuntu 6.2.0-1003.3-raspi 6.2.2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-1003-raspi N/A linux-backports-modules-6.2.0-1003-raspi N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' StagingDrivers: bcm2835_v4l2 rpivid_hevc bcm2835_isp vc_sm_cma snd_bcm2835 bcm2835_mmal_vchiq bcm2835_codec Tags: cloud-image lunar staging Uname: Linux 6.2.0-1003-raspi aarch64 UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2015001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007829] Re: USB keyboard not detected
*** This bug is a duplicate of bug 2013743 *** https://bugs.launchpad.net/bugs/2013743 ** This bug has been marked a duplicate of bug 2013743 USB not working on Nezha D1 -- 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/2007829 Title: USB keyboard not detected Status in linux package in Ubuntu: Incomplete Bug description: I am currently testing the Nezha image according to http://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271832/testcases/1755/results When I plugin a USB keyboard after the system is up it is correctly discovered. When I power up the device with a plugged in USB keyboard it is not detected. See the relevant kernel messages below. [ +0.000651] usbcore: registered new interface driver usbfs [ +0.000162] usbcore: registered new interface driver hub [ +0.000128] usbcore: registered new device driver usb [ +0.001479] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ +0.000489] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ +0.000532] uhci_hcd: USB Universal Host Controller Interface driver [ +0.000787] usbcore: registered new interface driver uas [ +0.000157] usbcore: registered new interface driver usb-storage [ +0.000300] usbcore: registered new interface driver usbserial_generic [ +0.000104] usbserial: USB Serial support registered for generic [ +0.000118] usbcore: registered new interface driver ch341 [ +0.94] usbserial: USB Serial support registered for ch341-uart [ +0.007873] ehci-platform 4101000.usb: EHCI Host Controller [ +0.005820] ehci-platform 4101000.usb: new USB bus registered, assigned bus number 1 [ +0.008338] ehci-platform 4101000.usb: irq 107, io mem 0x04101000 [ +0.014689] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00 [ +0.006889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.17 [ +0.008389] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007304] usb usb1: Product: EHCI Host Controller [ +0.004955] usb usb1: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd [ +0.006776] usb usb1: SerialNumber: 4101000.usb [ +0.006016] hub 1-0:1.0: USB hub found [ +0.006124] ehci-platform 420.usb: EHCI Host Controller [ +0.005820] ehci-platform 420.usb: new USB bus registered, assigned bus number 2 [ +0.008177] ehci-platform 420.usb: irq 109, io mem 0x0420 [ +0.019500] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00 [ +0.006924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.17 [ +0.008406] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007308] usb usb2: Product: EHCI Host Controller [ +0.004956] usb usb2: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd [ +0.006773] usb usb2: SerialNumber: 420.usb [ +0.006015] hub 2-0:1.0: USB hub found [ +0.030690] ohci-platform 4101400.usb: Generic Platform OHCI controller [ +0.006797] ohci-platform 4101400.usb: new USB bus registered, assigned bus number 3 [ +0.008115] ohci-platform 4101400.usb: irq 108, io mem 0x04101400 [ +0.069475] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.17 [ +0.008365] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007300] usb usb3: Product: Generic Platform OHCI controller [ +0.006002] usb usb3: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd [ +0.006775] usb usb3: SerialNumber: 4101400.usb [ +0.005758] hub 3-0:1.0: USB hub found [ +0.006081] ohci-platform 4200400.usb: Generic Platform OHCI controller [ +0.006750] ohci-platform 4200400.usb: new USB bus registered, assigned bus number 4 [ +0.008506] ohci-platform 4200400.usb: irq 110, io mem 0x04200400 [ +0.068747] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.17 [ +0.008395] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ +0.007335] usb usb4: Product: Generic Platform OHCI controller [ +0.006003] usb usb4: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd [ +0.006778] usb usb4: SerialNumber: 4200400.usb [ +0.006154] hub 4-0:1.0: USB hub found [ +0.016572] usb 2-1: new high-speed USB device number 2 using ehci-platform [ +0.613864] usb 4-1: new low-speed USB device number 2 using ohci-platform [ +0.207989] usb 4-1: device descriptor read/64, error -62 [ +0.304014] usb 4-1: device descriptor read/64, error -62 [ +0.29] usb 4-1: new low-speed USB device number 3 using ohci-platform [ +0.208012] usb 4-1: device descriptor read/64, error -62 [ +0.303984] usb 4-1: device descriptor read/64, error -62 [ +0.112175] usb usb4-port1: attempt power cycle [ +0.511829] usb 4-1: new low-speed USB device number 4 using ohci-platform [ +0.431956] usb 4-1: device not accepting address
[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints
** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Focal) 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/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: In Progress Bug description: SRU Bug Template: = [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [ Test Plan ] * A little test program in C is used for testing (?) * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 right now, and will submit an SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013743] Re: USB not working on Nezha D1
@Kai-Heng Feng (kaihengfeng) Concerning your question in LP #2007829: If this is a regression cannot be answered as the test case did not cover it. ** Changed in: linux-allwinner (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2013743 Title: USB not working on Nezha D1 Status in linux-allwinner package in Ubuntu: Confirmed Bug description: I am testing the Allwinner Nezha D1 board according to http://iso.qa.ubuntu.com/qatracker/milestones/444/builds/275098/testcases/1755/results Hitting a key on the USB keyboard (that was plugged in at boot) results in [ 760.275027] usb 3-1: device descriptor read/64, error -71 [ 761.671031] usb 1-1: device descriptor read/64, error -62 [ 761.975011] usb 1-1: device descriptor read/64, error -62 [ 762.466981] usb 1-1: device descriptor read/64, error -62 [ 762.770995] usb 1-1: device descriptor read/64, error -62 [ 763.514994] usb 1-1: device not accepting address 17, error -62 [ 764.122989] usb 1-1: device not accepting address 18, error -62 [ 764.129829] usb usb1-port1: unable to enumerate USB device lsusb does not show the keyboard: $ lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-5.19.0-1003-allwinner 5.19.0-1003.3 ProcVersionSignature: Ubuntu 5.19.0-1003.3-allwinner 5.19.7 Uname: Linux 5.19.0-1003-allwinner riscv64 ApportVersion: 2.26.0-0ubuntu2 Architecture: riscv64 CasperMD5CheckResult: unknown CloudArchitecture: riscv64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230329 CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net) Date: Fri Mar 31 14:31:08 2023 ProcCpuinfoMinimal: processor: 0 hart : 0 isa : rv64imafdc mmu : sv39 uarch: thead,c906 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=vt220 SourcePackage: linux-allwinner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2013743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2014986] Re: [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExte
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High ** Tags added: regression-release rls-ll-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
In response to #6 $ echo mem | sudo tee /sys/power/state That works for me too - but then there's no password protection on resume... -- 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/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~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: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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/2008774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002968] Re: Fix flicker display problem on some panels which support PSR2
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Invalid -- 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/2002968 Title: Fix flicker display problem on some panels which support PSR2 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete 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: Invalid 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 Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some PSR2 supported panels, which connects to Intel Graphics has flicker symptom. It gets normal after booting the kernel with parameter `i915. enable_psr=0` [Fix] Backport one patch from upstream. https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87 [Test] Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if the display has abnormal flickering problem on graphics interfaces. [Where problems could occur] The risk of regression is low. It only fixes problem on panels which support PSR2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015033] Re: 5.15.0-69 breaks my wifi
Note, the internal intel wlan device has no antenna connected. It is probably working. The broadcom wlan device has an antenna connected and stopped working. -- 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/2015033 Title: 5.15.0-69 breaks my wifi Status in linux package in Ubuntu: Confirmed Bug description: Latest linux kernel completely kills my Wifi. Have had to use the GRUB boot loader to revert the kernel back twice. wlan devices are recognized, but they cannot find any network. Reinstall of device driver did not help. Revert to Kernel 5.15.0-67 brings wlan back. see also bug 2013186 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andreas1177 F pulseaudio /dev/snd/controlC1: andreas1177 F pulseaudio /dev/snd/controlC2: andreas1177 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 06:32:09 2023 InstallationDate: Installed on 2019-04-09 (1454 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408.2) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=1bc58a0c-41ca-4f6a-ad9d-df0a5fe02b37 ro quiet splash systemd.unified_cgroup_hierarchy=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-69-generic N/A linux-backports-modules-5.15.0-69-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-06-10 (296 days ago) dmi.bios.date: 12/21/2018 dmi.bios.release: 7.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS XI HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd12/21/2018:br7.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL 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/2015033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
