[Kernel-packages] [Bug 1960729] 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 1960729 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/1960729 Title: Thinkpad T14 gen2 AMD - spontaneous reboot Status in linux package in Ubuntu: Incomplete Bug description: After my Thinkpad T14 gen2 AMD spontaneously rebooted I found this in the kernel log: [6.211553] === [6.211556] UBSAN: invalid-load in /build/linux-PqLDBN/linux-5.15.15/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5882:84 [6.211558] load of value 187 is not a valid value for type '_Bool' [6.211560] CPU: 2 PID: 414 Comm: plymouthd Tainted: G OE 5.15.15-76051515-generic #202201160435~1642693824~21.10~97db1bb [6.211561] Hardware name: LENOVO 20XKCTO1WW/20XKCTO1WW, BIOS R1MET43W (1.13 ) 11/05/2021 [6.211562] Call Trace: [6.211563] [6.211565] show_stack+0x52/0x58 [6.211569] dump_stack_lvl+0x4a/0x5f [6.211573] dump_stack+0x10/0x12 [6.211574] ubsan_epilogue+0x9/0x45 [6.211575] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [6.211577] create_stream_for_sink.cold+0x5d/0xbb [amdgpu] [6.211697] ? __free_pages_ok+0x31b/0x470 [6.211699] create_validate_stream_for_sink+0x59/0x150 [amdgpu] [6.211802] dm_update_crtc_state+0x235/0x7b0 [amdgpu] [6.211894] amdgpu_dm_atomic_check+0x596/0xcd0 [amdgpu] [6.211983] ? dm_plane_format_mod_supported+0x1f/0x100 [amdgpu] [6.212069] ? drm_plane_check_pixel_format+0x45/0x90 [drm] [6.212084] ? drm_atomic_plane_check+0x12f/0x360 [drm] [6.212095] drm_atomic_check_only+0x253/0x4b0 [drm] [6.212103] ? handle_conflicting_encoders+0x26b/0x2a0 [drm_kms_helper] [6.212113] drm_atomic_commit+0x18/0x50 [drm] [6.212122] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [6.212128] drm_mode_setcrtc+0x1f9/0x7c0 [drm] [6.212137] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212146] drm_ioctl_kernel+0xae/0xf0 [drm] [6.212155] drm_ioctl+0x264/0x4b0 [drm] [6.212163] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212172] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [6.212231] __x64_sys_ioctl+0x91/0xc0 [6.212234] do_syscall_64+0x5c/0xc0 [6.212235] ? amdgpu_drm_ioctl+0x6f/0x80 [amdgpu] [6.212294] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212296] ? syscall_exit_to_user_mode+0x27/0x50 [6.212298] ? do_syscall_64+0x69/0xc0 [6.212299] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212300] ? irqentry_exit_to_user_mode+0x9/0x20 [6.212301] ? irqentry_exit+0x19/0x30 [6.212302] ? exc_page_fault+0x89/0x160 [6.212303] ? asm_exc_page_fault+0x8/0x30 [6.212305] entry_SYSCALL_64_after_hwframe+0x44/0xae [6.212306] RIP: 0033:0x7fc4c316a9cb [6.212308] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 4 8 [6.212309] RSP: 002b:7b5d2fb8 EFLAGS: 0246 ORIG_RAX: 0010 [6.212310] RAX: ffda RBX: 7b5d2ff0 RCX: 7fc4c316a9cb [6.212311] RDX: 7b5d2ff0 RSI: c06864a2 RDI: 0009 [6.212312] RBP: c06864a2 R08: R09: 5566798141f0 [6.212312] R10: R11: 0246 R12: 0067 [6.212313] R13: 0009 R14: 556679814140 R15: 556679814180 [6.212314] [6.212314] === --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 21.10 Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Tags: impish Uname: Linux 5.15.15-76051515-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sudo _MarkForUpload: True To manage notifications about this bug
[Kernel-packages] [Bug 1960729] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960729/+attachment/5560602/+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/1960729 Title: Thinkpad T14 gen2 AMD - spontaneous reboot Status in linux package in Ubuntu: New Bug description: After my Thinkpad T14 gen2 AMD spontaneously rebooted I found this in the kernel log: [6.211553] === [6.211556] UBSAN: invalid-load in /build/linux-PqLDBN/linux-5.15.15/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5882:84 [6.211558] load of value 187 is not a valid value for type '_Bool' [6.211560] CPU: 2 PID: 414 Comm: plymouthd Tainted: G OE 5.15.15-76051515-generic #202201160435~1642693824~21.10~97db1bb [6.211561] Hardware name: LENOVO 20XKCTO1WW/20XKCTO1WW, BIOS R1MET43W (1.13 ) 11/05/2021 [6.211562] Call Trace: [6.211563] [6.211565] show_stack+0x52/0x58 [6.211569] dump_stack_lvl+0x4a/0x5f [6.211573] dump_stack+0x10/0x12 [6.211574] ubsan_epilogue+0x9/0x45 [6.211575] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [6.211577] create_stream_for_sink.cold+0x5d/0xbb [amdgpu] [6.211697] ? __free_pages_ok+0x31b/0x470 [6.211699] create_validate_stream_for_sink+0x59/0x150 [amdgpu] [6.211802] dm_update_crtc_state+0x235/0x7b0 [amdgpu] [6.211894] amdgpu_dm_atomic_check+0x596/0xcd0 [amdgpu] [6.211983] ? dm_plane_format_mod_supported+0x1f/0x100 [amdgpu] [6.212069] ? drm_plane_check_pixel_format+0x45/0x90 [drm] [6.212084] ? drm_atomic_plane_check+0x12f/0x360 [drm] [6.212095] drm_atomic_check_only+0x253/0x4b0 [drm] [6.212103] ? handle_conflicting_encoders+0x26b/0x2a0 [drm_kms_helper] [6.212113] drm_atomic_commit+0x18/0x50 [drm] [6.212122] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [6.212128] drm_mode_setcrtc+0x1f9/0x7c0 [drm] [6.212137] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212146] drm_ioctl_kernel+0xae/0xf0 [drm] [6.212155] drm_ioctl+0x264/0x4b0 [drm] [6.212163] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212172] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [6.212231] __x64_sys_ioctl+0x91/0xc0 [6.212234] do_syscall_64+0x5c/0xc0 [6.212235] ? amdgpu_drm_ioctl+0x6f/0x80 [amdgpu] [6.212294] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212296] ? syscall_exit_to_user_mode+0x27/0x50 [6.212298] ? do_syscall_64+0x69/0xc0 [6.212299] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212300] ? irqentry_exit_to_user_mode+0x9/0x20 [6.212301] ? irqentry_exit+0x19/0x30 [6.212302] ? exc_page_fault+0x89/0x160 [6.212303] ? asm_exc_page_fault+0x8/0x30 [6.212305] entry_SYSCALL_64_after_hwframe+0x44/0xae [6.212306] RIP: 0033:0x7fc4c316a9cb [6.212308] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 4 8 [6.212309] RSP: 002b:7b5d2fb8 EFLAGS: 0246 ORIG_RAX: 0010 [6.212310] RAX: ffda RBX: 7b5d2ff0 RCX: 7fc4c316a9cb [6.212311] RDX: 7b5d2ff0 RSI: c06864a2 RDI: 0009 [6.212312] RBP: c06864a2 R08: R09: 5566798141f0 [6.212312] R10: R11: 0246 R12: 0067 [6.212313] R13: 0009 R14: 556679814140 R15: 556679814180 [6.212314] [6.212314] === --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 21.10 Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Tags: impish Uname: Linux 5.15.15-76051515-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960729] [NEW] Thinkpad T14 gen2 AMD - spontaneous reboot
Public bug reported: After my Thinkpad T14 gen2 AMD spontaneously rebooted I found this in the kernel log: [6.211553] === [6.211556] UBSAN: invalid-load in /build/linux-PqLDBN/linux-5.15.15/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5882:84 [6.211558] load of value 187 is not a valid value for type '_Bool' [6.211560] CPU: 2 PID: 414 Comm: plymouthd Tainted: G OE 5.15.15-76051515-generic #202201160435~1642693824~21.10~97db1bb [6.211561] Hardware name: LENOVO 20XKCTO1WW/20XKCTO1WW, BIOS R1MET43W (1.13 ) 11/05/2021 [6.211562] Call Trace: [6.211563] [6.211565] show_stack+0x52/0x58 [6.211569] dump_stack_lvl+0x4a/0x5f [6.211573] dump_stack+0x10/0x12 [6.211574] ubsan_epilogue+0x9/0x45 [6.211575] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [6.211577] create_stream_for_sink.cold+0x5d/0xbb [amdgpu] [6.211697] ? __free_pages_ok+0x31b/0x470 [6.211699] create_validate_stream_for_sink+0x59/0x150 [amdgpu] [6.211802] dm_update_crtc_state+0x235/0x7b0 [amdgpu] [6.211894] amdgpu_dm_atomic_check+0x596/0xcd0 [amdgpu] [6.211983] ? dm_plane_format_mod_supported+0x1f/0x100 [amdgpu] [6.212069] ? drm_plane_check_pixel_format+0x45/0x90 [drm] [6.212084] ? drm_atomic_plane_check+0x12f/0x360 [drm] [6.212095] drm_atomic_check_only+0x253/0x4b0 [drm] [6.212103] ? handle_conflicting_encoders+0x26b/0x2a0 [drm_kms_helper] [6.212113] drm_atomic_commit+0x18/0x50 [drm] [6.212122] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [6.212128] drm_mode_setcrtc+0x1f9/0x7c0 [drm] [6.212137] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212146] drm_ioctl_kernel+0xae/0xf0 [drm] [6.212155] drm_ioctl+0x264/0x4b0 [drm] [6.212163] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212172] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [6.212231] __x64_sys_ioctl+0x91/0xc0 [6.212234] do_syscall_64+0x5c/0xc0 [6.212235] ? amdgpu_drm_ioctl+0x6f/0x80 [amdgpu] [6.212294] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212296] ? syscall_exit_to_user_mode+0x27/0x50 [6.212298] ? do_syscall_64+0x69/0xc0 [6.212299] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212300] ? irqentry_exit_to_user_mode+0x9/0x20 [6.212301] ? irqentry_exit+0x19/0x30 [6.212302] ? exc_page_fault+0x89/0x160 [6.212303] ? asm_exc_page_fault+0x8/0x30 [6.212305] entry_SYSCALL_64_after_hwframe+0x44/0xae [6.212306] RIP: 0033:0x7fc4c316a9cb [6.212308] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 4 8 [6.212309] RSP: 002b:7b5d2fb8 EFLAGS: 0246 ORIG_RAX: 0010 [6.212310] RAX: ffda RBX: 7b5d2ff0 RCX: 7fc4c316a9cb [6.212311] RDX: 7b5d2ff0 RSI: c06864a2 RDI: 0009 [6.212312] RBP: c06864a2 R08: R09: 5566798141f0 [6.212312] R10: R11: 0246 R12: 0067 [6.212313] R13: 0009 R14: 556679814140 R15: 556679814180 [6.212314] [6.212314] === --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 21.10 Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Tags: impish Uname: Linux 5.15.15-76051515-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sudo _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected impish ** Tags added: apport-collected impish ** Description changed: After my Thinkpad T14 gen2 AMD spontaneously rebooted I found this in the kernel log: [6.211553] === [6.211556] UBSAN: invalid-load in /build/linux-PqLDBN/linux-5.15.15/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5882:84 [6.211558] load of value 187 is not a valid value for type '_Bool' [6.211560] CPU: 2 PID: 414 Comm: plymouthd Tainted: G OE 5.15.15-76051515-generic #202201160435~1642693824~21.10~97db1bb [6.211561] Hardware name: LENOVO 20XKCTO1WW/20XKCTO1WW, BIOS R1MET43W (1.13 ) 11/05/2021 [6.211562] Call Trace: [6.211563] [6.211565] show_stack+0x52/0x58 [6.211569] dump_stack_lvl+0x4a/0x5f [6.211573] dump_stack+0x10/0x12 [6.211574] ubsan_epilogue+0x9/0x45 [6.211575] __ubsan_hand
[Kernel-packages] [Bug 1384746] Re: Support multiple versions of AppArmor policy cache files
Indeed https://bugs.launchpad.net/apparmor/+bug/1384746/comments/2 should be tracked else where. It really should split out into two separate tracking issues. 1. either generating the feature file from the kernel on build. To track this I have opened https://gitlab.com/apparmor/apparmor/-/issues/217 to track. 2. OS integration so that a kernel packages can build cache files on install. To track this I have opened https://gitlab.com/apparmor/apparmor/-/issues/218 ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #217 https://gitlab.com/apparmor/apparmor/-/issues/217 ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #218 https://gitlab.com/apparmor/apparmor/-/issues/218 -- 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/1384746 Title: Support multiple versions of AppArmor policy cache files Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: The AppArmor parser should support multiple directories of policy cache files. Directories should be specific to a certain AppArmor kernel feature set. From a distro standpoint, this would allow policy caches to be created during kernel install/upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1384746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1379535] Re: policy namespace stacking
This is indeed upstream, and works as far as it goes. There are currently issues when crossing system namespace boundaries but those are being treated as separate issues. The stacking it self works policy when crossing ns boundaries has to be aware of it and more relaxed than we would like. -- 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/1379535 Title: policy namespace stacking Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Tracking bug for supporting stacked policy namesapaces (ie, different profiles on host, container, container in a container, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1379535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression
I've created a diff of the systemd boot journal for working and failing boot. journalctl --no-pager -b-0|cut -f 4- -d' ' > allb0 journalctl --no-pager -b-1|cut -f 4- -d' ' > allb1 diff allb0 allb1 >alldiff ** Attachment added: "diff of boot journal working/failing" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960018/+attachment/5560557/+files/alldiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960018 Title: Boot Failure - linux-image-5.13.0-28-generic | regression Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 Installed since May 2020, now fails to boot into graphics mode after upgrade to kernel version linux-image-5.13.0-27-generic - Have tried linux-image-5.13.0-28-generic with same result, I have reverted back to 5.11.0.40 which works correctly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1890 F pulseaudio /dev/snd/controlC0: christian 1890 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (639 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.11.0-40-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: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960711] [NEW] USB does not work any more after wake up from suspend
Public bug reported: On Lenovo E14 Gen 2 kernel 5.13.0-22 exhibits multiple bugs, one of them is that he USB sometimes does not work any more after suspend and a reboot is necessary. This problem occurs every few kernel versions, so it would be really nice if there would be a way to reload the build in usb module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 16:42:10 2022 InstallationDate: Installed on 2015-11-05 (2291 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-09-10 (520 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024 ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960711 Title: USB does not work any more after wake up from suspend Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: On Lenovo E14 Gen 2 kernel 5.13.0-22 exhibits multiple bugs, one of them is that he USB sometimes does not work any more after suspend and a reboot is necessary. This problem occurs every few kernel versions, so it would be really nice if there would be a way to reload the build in usb module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 16:42:10 2022 InstallationDate: Installed on 2015-11-05 (2291 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-09-10 (520 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1960711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960710] [NEW] Ant war on primary laptop screen after attaching an external monitor and switching it on and off
Public bug reported: On Lenovo E14 Gen 2 kernel 5.13.0-22 exhibits multiple bugs, one of them is that the primary screen shows white noise (ant war) after attaching an external monitor and switching it on and oft This cannot be solved by switching to tty or restarting the display manager, reboot necessary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 16:34:08 2022 InstallationDate: Installed on 2015-11-05 (2291 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-09-10 (520 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024 ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960710 Title: Ant war on primary laptop screen after attaching an external monitor and switching it on and off Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: On Lenovo E14 Gen 2 kernel 5.13.0-22 exhibits multiple bugs, one of them is that the primary screen shows white noise (ant war) after attaching an external monitor and switching it on and oft This cannot be solved by switching to tty or restarting the display manager, reboot necessary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 16:34:08 2022 InstallationDate: Installed on 2015-11-05 (2291 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-09-10 (520 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1960710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960709] [NEW] Recent bluez update broke Bluetooth for setups using a BT dongle
Public bug reported: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle Status in bluez package in Ubuntu: New Bug description: A recent upgrade (seemingly 5.53-0ubuntu3.5) broke Bluetooth functionality for certain setups. Specifically, the `ConditionPathIsDirectory=` parameter has been added to the `bluetooth` Systemd unit. This breaks setups where users use a Bluetooth dongle, since when the system starts, the BT device may not be connected, and due to the condition, the `bluetooth` unit won't start at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956461] Re: Creative HD720p webcam doesn't work
Thanks to macg3, the workaround you suggested works for me on kernel 5.4.0-99.112. There is one correction. The name of the audio driver is snd_usb_audio and not snd-usb-audio. So in my case after a fresh boot the webcam did not work, and after executing: sudo modprobe -r snd_usb_audio sudo modprobe -r uvcvideo sudo modprobe uvcvideo sudo modprobe snd_usb_audio It started to work OK. -- 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/1956461 Title: Creative HD720p webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen by the system. There is no /dev/vl4/ folder --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 3094 F pulseaudio /dev/snd/controlC0: piotr 3094 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-06-07 (578 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: Tags: uma Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960703] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: alsa-base
[Kernel-packages] [Bug 1960703] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560541/+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/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1
[Kernel-packages] [Bug 1960703] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560540/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Rele
[Kernel-packages] [Bug 1960703] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560536/+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/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" -
[Kernel-packages] [Bug 1960703] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560537/+files/AudioDevicesInUse.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/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 L
[Kernel-packages] [Bug 1960703] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560542/+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/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa"
[Kernel-packages] [Bug 1960703] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560539/+files/Dependencies.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/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal
[Kernel-packages] [Bug 1960703] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1960703/+attachment/5560538/+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/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases Status in linux package in Ubuntu: Confirmed Bug description: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal
[Kernel-packages] [Bug 1960703] [NEW] USB TASCAM US-122L audio interface crashes when system load increases
Public bug reported: The TASCAM US-122L, in previous versions of Ubuntu worked okay, with an occasional xrun reported by jackd, running with default settings (sample rate: 48000, frames/period: 1024). In Ubuntu 21.10 the device loads without problem, playback is perfect, but when the system load increases, it immediately crashes. dmesg: [ 218.607518] xhci_hcd :00:14.0: ERROR unknown event type 37 [ 218.613370] underrun, status=4294967278 jackd (hangs): ALSA: prepare audio_reservation_init Acquire audio card Audio1 creating alsa driver ... usb_stream:US122L|usb_stream:US122L|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 24bit little-endian in 3bytes format ALSA: use 2 periods for playback error for playback on "usb_stream:US122L" (Input/output error) JackAudioDriver::ProcessAsync: read error, stopping... Jack: JackPosixThread::ThreadHandler : exit lsusb: Bus 001 Device 003: ID 0644:800e TEAC Corp. TASCAM US-122L $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 Reproduction steps: 1) Start jackd 2) Start OBS with an USB webcam at 1080p 3) OBS monitor out goes to jackd/us-122L system port 4) Start Zoom, Thunderbird etc to generate some load 5) Immediately crashes Crash occurs even quicker when adding and actively using another 4 channel USB audio device(same sample rate and period size). So the issue seems related to the load on the USB subsystem as well as the CPU load. I've tried just about anything to find out if the issue is hardware related. Changed cables, used different hubs, no-hub, used different USB ports on the laptop, etc, etc, etc. Same result every time. Also normal playback using PulseAudio instead of Jack suffers from the same. Each time a reset of Jack is needed to get the US-122L to work again. I've tried, besides the default Ubuntu kernel(5.13.0-28-generic) the latest upstream mainline kernel(5.17.0-051700rc3-generic) as well as the low latency kernel (5.13.0-28-lowlatency). Same result. If more information is needed, please let me know. Any help is much appreciated. Thank you in advance. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 12 14:22:37 2022 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20N3S77637 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash intel_iommu=on RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S77637 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.19:svnLENOVO:pn20N3S77637:pvrThinkPadT490:rvnLENOVO:rn20N3S77637:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S77637 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-12-13 (425 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: alsa-base 1.0.25+dfsg-0ubuntu7 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Tags: impish Uname: Linux 5.13.0-28-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-31 (103 days ago) UserGroups: adm audio cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Availabl
[Kernel-packages] [Bug 1379535] Re: policy namespace stacking
I see this is "Fix Released" everywhere but on the upstream AppArmor project. I understand this has made its way upstream and works with mainline kernel, e.g. for LXC. If my understanding is incorrect, please clarify what's left to do here (or perhaps track it on a finer-grained follow-up bug :) ** Changed in: apparmor Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1379535 Title: policy namespace stacking Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Tracking bug for supporting stacked policy namesapaces (ie, different profiles on host, container, container in a container, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1379535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1384746] Re: Support multiple versions of AppArmor policy cache files
It seems to me this was fixed & released a while ago. https://bugs.launchpad.net/apparmor/+bug/1384746/comments/2 could be tracked on a new, follow-up bug, if still desired. ** Changed in: apparmor Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1384746 Title: Support multiple versions of AppArmor policy cache files Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Triaged Bug description: The AppArmor parser should support multiple directories of policy cache files. Directories should be specific to a certain AppArmor kernel feature set. From a distro standpoint, this would allow policy caches to be created during kernel install/upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1384746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zsys (Ubuntu) Status: New => Confirmed -- 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/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960696] [NEW] Running "apt upgrade" nvidia-dkms-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: Popup requested that I report nvidia-dkms-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-28-generic Date: Sat Feb 12 11:09:29 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.39-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.39/build/nvidia-drm/nvidia-drm-drv.c:824:38: error: ‘drm_gem_dumb_destroy’ undeclared (first use in this function); did you mean ‘drm_mode_destroy’? InstallationDate: Installed on 2021-03-01 (347 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 460.39-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1960696 Title: Running "apt upgrade" nvidia-dkms-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Popup requested that I report nvidia-dkms-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-28-generic Date: Sat Feb 12 11:09:29 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.39-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.39/build/nvidia-drm/nvidia-drm-drv.c:824:38: error: ‘drm_gem_dumb_destroy’ undeclared (first use in this function); did you mean ‘drm_mode_destroy’? InstallationDate: Installed on 2021-03-01 (347 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 460.39-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1960696/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly
** Bug watch removed: github.com/flatpak/flatpak/issues #4609 https://github.com/flatpak/flatpak/issues/4609 -- 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/1958975 Title: linux-image-5.13.0-28-generic hangs randomly Status in linux package in Ubuntu: Confirmed Bug description: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C95 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958975] Re: linux-image-5.13.0-28-generic hangs randomly
I have a similar issue, but on Ubuntu 20.04. When I use kernel 5.13.0-28, the system will hard freeze every time I open a file from a flatpak using the xdg-desktop-portal file picker. The last thing I can see in the logs is: "BUG: Bad page state in process xdg-document-po pfn:19f8d2". On 5.13.0-27 this doesn't happen. This seems really similar to https://github.com/flatpak/flatpak/issues/4609 but there it happens with openSUSE Tumbleweed on kernel 5.15.5-1. ** Bug watch added: github.com/flatpak/flatpak/issues #4609 https://github.com/flatpak/flatpak/issues/4609 -- 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/1958975 Title: linux-image-5.13.0-28-generic hangs randomly Status in linux package in Ubuntu: Confirmed Bug description: Kernel image 5.13.0-28 hangs with "BUG: Bad page state in process ". Using previous build (5.13.0-25) solves the problem. The symptoms are that the system just hangs up. Only hardreset works. I started ubuntu-bug with 5.13.0-25 kernel, because the system is stable with this kernel, but I also add a journalctl output with -28 kernel to indicate the problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 25 13:30:53 2022 IwConfig: lono wireless extensions. enp42s0 no wireless extensions. virbr0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C95 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=a5b5bfb1-d905-4b38-acee-3e3392aee389 ro intel_iommu=off quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2022-01-11 (13 days ago) dmi.bios.date: 06/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550M PRO-VDH (MS-7C95) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.80:bd06/22/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDH(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C95 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845214] Re: Keyboard NumLock indicator turns off on connecting another keyboard
It's been several years since my report! Still reproducible on latest Ubuntu. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1845214 Title: Keyboard NumLock indicator turns off on connecting another keyboard Status in linux-meta-hwe package in Ubuntu: Confirmed Bug description: My USB HID keyboard has NumLock LED. It usually works fine. However, when I plug in YubiKey (hardware security token, it is also identified as a USB HID keyboard) NumLock LED turns OFF, but the NumLock feature is still ON. If I press NumLock, NumLock becomes disabled (it is displayed by DE and checked by typing). If I press NumLock again, NumLock turns back ON with LED. I originally thought that issue could be related to the fact that YubiKey does not have a NumLock led, so it reports LED as nonexisting and stuff happens. However, today I tried attaching another USB keyboard: LED on first one still goes off; but LED on second goes ON immediately after plugging in. Pressing NumLock once disables NumLock and LED on first keyboard, as with YubiKey; pressing again enabled NumLock and both LEDs. Seems like my user session (on vt2) is running Xorg while login screen (on vt1, the one that allows to choose a user and that you see before first login) is running Wayland; both are faulty. Because of this, I believe the issue is in the kernel. However, I am not sure, so you can ask for way more reports to be added, I will add those. Reproducing should be pretty easy with any cheap USB keyboards, nothing special is used by me. Operating system: Ubuntu 18.04 Bionic Beaver. Linux kernel: 18.04 HWE, 5.0.0-25. However, I think I saw this blinking before upgrading to HWE. DE: GNOME. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.0.0.29.86 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 16:52:08 2019 SourcePackage: linux-meta-hwe UpgradeStatus: Upgraded to bionic on 2018-09-03 (386 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1845214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests
This bug is awaiting verification that the linux-azure/5.13.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: In Progress Status in linux-meta-azure package in Ubuntu: In Progress Status in linux-signed-azure package in Ubuntu: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-meta-azure source package in Hirsute: Fix Released Status in linux-signed-azure source package in Hirsute: Fix Released Status in linux-azure source package in Impish: In Progress Status in linux-meta-azure source package in Impish: In Progress Status in linux-signed-azure source package in Impish: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-meta-azure source package in Jammy: In Progress Status in linux-signed-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. [Other info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959216] Re: linux-azure: CONFIG_FB_EFI=y
This bug is awaiting verification that the linux-azure/5.13.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959216 Title: linux-azure: CONFIG_FB_EFI=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure-5.13 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure-5.11 source package in Bionic: Invalid Status in linux-azure-5.13 source package in Bionic: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-4.15 source package in Impish: Invalid Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure-5.13 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-4.15 source package in Jammy: Invalid Status in linux-azure-5.11 source package in Jammy: Invalid Status in linux-azure-5.13 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. The issue was noticed in Ubuntu 18.04 linux-azure kernel, but actually exists in the latest mainline kernel. The issue happens when the below conditions are met: hyperv_pci is built into the kernel and hyperv_fb is not, i.e., this means hyperv_pci loads before hyperv_fb loads. CONFIG_FB_EFI is not defined, i.e., the efifb driver is not used. Here is how the bug happens: Linux VM starts, and vmbus_reserve_fb() reserves the VRAM [base=0xf800, length=8MB]. hyper-pci loads, gets MMIO [base=0xf880, lengh=8KB] as the bridge config window, and may get some other 64-bit MMIO ranges, and some 32-bit MMIO ranges (if needed.) hyperv-fb loads, and gets MMIO [base=0xf800, lengh=8MB or a different length], and sets screen_info.lfb_base = 0. VM panics. The kdump kernel starts to run, and vmbus_reserve_fb() is not reserving [base=0xf800, length=8MB] due to the lfb_base==0. hyperv-pci loads and gets [base=0xf800, lengh=8KB] and the host PCI VSP driver rejects this address as the bridge config window. The crux of the problem is that Linux vmbus driver itself is unable to detect the VRAM base/length (it looks like a video BIOS call is needed to get this info and such a BIOS call is inappropriate or impossible in hv_vmbus) and has to rely on screen_info.lfb_base (which is set by grub or the kdump/kexec tool and can be reset to zero by hyperv_fb/drm). Solution: Enable CONFIG_FB_EFI=y [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect
This bug is awaiting verification that the linux-azure/5.13.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1958990 Title: Add sunrpc module parameters for NFSv3 nconnect Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-5.11 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Microsoft has requested the addition of 2 module parameters to sunrpc. The primary purpose of which is to restrict or pin NFSv3 TCP connections to one server in order to take advantage of local server connection caching. In the presence of a load balancer, round robin connection requests defeats the advantages of local caching. [Test Plan] Microsoft tested [Where things could go wrong] NFSv3 connection attempts could be slow or fail altogether. [Other Info] SF: #00312346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958252] Re: Support networking XDP
This bug is awaiting verification that the linux-azure/5.13.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1958252 Title: Support networking XDP Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure source package in Focal: In Progress Status in linux-azure-5.11 source package in Focal: New Status in linux-azure source package in Hirsute: Won't Fix Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.11 source package in Impish: Invalid Bug description: SRU Justification [Impact] Enable XDP support in Azure tuned kernels. [Test Plan] Microsoft tested. [Where things could go wrong] Network performance could be impacted or base functionality could fail. [Other Info] SF: #00324494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959012] Re: MANA updates
This bug is awaiting verification that the linux-azure/5.13.0-1014.16
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists, change the tag 'verification-needed-impish' to
'verification-failed-impish'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-impish
--
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/1959012
Title:
MANA updates
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-azure source package in Focal:
New
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-azure source package in Jammy:
Fix Committed
Bug description:
SRU Justification
[Impact]
The MANA driver is missing 2 updates.
commit 6cc74443a7732d7e93bee3d0c3704a22cc7274d9 ("net: mana: Add RX fencing")
commit 9acfc57fa2b8944ed079cedbf846823ea32b8a31 ("net: mana: Fix memory leak
in mana_hwc_create_wq")
[Test Plan]
Microsoft tested
[Where things could go wrong]
Fencing requests could get dropped or sent out of order.
[Other Info]
SF: #00324494
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959012/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960669] Re: the display doesn't appear after suspend, i915
install 'linux-generic-hwe-20.04' and then you'll get a newer kernel does it fix this? ** Package changed: libdrm (Ubuntu) => linux (Ubuntu) ** 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/1960669 Title: the display doesn't appear after suspend, i915 Status in linux package in Ubuntu: Incomplete Bug description: System: Lenovo T470s Kernel: 5.4.0-97-generic #110-Ubuntu SMP After S3 suspend and resuming the external display doesn't work. C-A-F1, C-A-F7 solves the problem. The regression appears 2-3 weeks ago after update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request
thanks for testing! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960669] [NEW] the display doesn't appear after suspend, i915
You have been subscribed to a public bug: System: Lenovo T470s Kernel: 5.4.0-97-generic #110-Ubuntu SMP After S3 suspend and resuming the external display doesn't work. C-A-F1, C-A-F7 solves the problem. The regression appears 2-3 weeks ago after update. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- the display doesn't appear after suspend, i915 https://bugs.launchpad.net/bugs/1960669 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
