[Kernel-packages] [Bug 2056616] Re: left-over ceph debugging printks
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056616] Re: left-over ceph debugging printks
** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056616] Re: left-over ceph debugging printks
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056616] [NEW] left-over ceph debugging printks
Public bug reported: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: New Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next&id=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037490] Re: UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c
Looks like this patch fixes the problem https://github.com/torvalds/linux/commit/aa4db51bbd51654e215905f384eecf22327bafa9 -- 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/2037490 Title: UBSAN: array-index-out-of-bounds in /build/linux- IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c Status in linux package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. install a ubuntu 23.10 VM on an ESXi Server 2. hot add a lsilogicsas controller and a lsilogicsas disk Call Trace will be reported in dmesg log [ 176.181166] [ 176.181167] UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22 [ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]' [ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted 6.5.0-5-generic #5-Ubuntu [ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023 [ 176.181179] Call Trace: [ 176.181181] [ 176.181183] dump_stack_lvl+0x48/0x70 [ 176.181228] dump_stack+0x10/0x20 [ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas] [ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas] [ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10 [ 176.181264] ? rpm_idle+0x1dc/0x2b0 [ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas] [ 176.181277] ? scsi_autopm_put_host+0x1a/0x30 [ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas] [ 176.181289] mptsas_probe+0x1e/0x30 [mptsas] [ 176.181298] local_pci_probe+0x44/0xb0 [ 176.181302] pci_call_probe+0x55/0x190 [ 176.181307] pci_device_probe+0x84/0x120 [ 176.181312] really_probe+0x1c4/0x410 [ 176.181316] __driver_probe_device+0x8c/0x180 [ 176.181320] driver_probe_device+0x24/0xd0 [ 176.181324] __driver_attach+0x10b/0x210 [ 176.181327] ? __pfx___driver_attach+0x10/0x10 [ 176.181330] bus_for_each_dev+0x8a/0xf0 [ 176.181333] driver_attach+0x1e/0x30 [ 176.181336] bus_add_driver+0x127/0x240 [ 176.181340] driver_register+0x5e/0x130 [ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas] [ 176.181352] __pci_register_driver+0x62/0x70 [ 176.181356] mptsas_init+0x119/0xff0 [mptsas] [ 176.181365] do_one_initcall+0x5b/0x340 [ 176.181371] do_init_module+0x68/0x260 [ 176.181375] load_module+0xba1/0xcf0 [ 176.181380] ? vfree+0xff/0x2d0 [ 176.181385] init_module_from_file+0x96/0x100 [ 176.181388] ? init_module_from_file+0x96/0x100 [ 176.181394] idempotent_init_module+0x11c/0x2b0 [ 176.181399] __x64_sys_finit_module+0x64/0xd0 [ 176.181402] do_syscall_64+0x59/0x90 [ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0 [ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60 [ 176.181417] ? do_syscall_64+0x68/0x90 [ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60 [ 176.181424] ? do_syscall_64+0x68/0x90 [ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 176.181432] RIP: 0033:0x7f847a725c5d [ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48 [ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX: 0139 [ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX: 7f847a725c5d [ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI: 000d [ 176.181488] RBP: 7f847aa0144a R08: 0040 R09: fde0 [ 176.181490] R10: fe18 R11: 0246 R12: 0002 [ 176.181526] R13: 563ba2216ae0 R14: R15: 563ba20dff90 [ 176.181531] [ 176.181532] --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:vmware 950 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) IwConfig: lono wireless extensions. ens33 no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash
[Kernel-packages] [Bug 2056498] Re: Kernel crash in amd gpu driver
The above crash was happening with large downloads of img files or git clones of large repositories (Ubuntu kernels) over wifi. I have changed to hard wired ethernet and I've not been able to reproduce it. With Wifi it's been very reproduceable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056498 Title: Kernel crash in amd gpu driver Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Mar 7 19:07:10 ripper kernel: [9.873538] CPU: 4 PID: 849 Comm: systemd-udevd Not tainted 6.5.0-17-generic #17~22.04.1-Ubuntu Mar 7 19:07:10 ripper kernel: [9.873542] Hardware name: LENOVO 30E1S3VV00/1046, BIOS S07KT45A 01/20/2022 Mar 7 19:07:10 ripper kernel: [9.873544] Call Trace: Mar 7 19:07:10 ripper kernel: [9.873545] Mar 7 19:07:10 ripper kernel: [9.873547] dump_stack_lvl+0x48/0x70 Mar 7 19:07:10 ripper kernel: [9.873551] dump_stack+0x10/0x20 Mar 7 19:07:10 ripper kernel: [9.873554] __ubsan_handle_out_of_bounds+0xc6/0x110 Mar 7 19:07:10 ripper kernel: [9.873560] smu7_get_pp_table_entry_callback_func_v1+0x9b7/0xa00 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.873897] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.873900] ? vi_pcie_rreg+0x6e/0x90 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874187] ? __pfx_smu7_get_pp_table_entry_callback_func_v1+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874515] get_powerplay_table_entry_v1_0+0xf8/0x490 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874842] smu7_get_pp_table_entry_v1+0x41/0x4c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875169] smu7_get_pp_table_entry+0x3d/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875495] psm_init_power_state_table+0x161/0x250 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875826] hwmgr_hw_init+0xe3/0x1e0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876150] pp_hw_init+0x16/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876484] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876749] amdgpu_device_init+0x9a2/0x1150 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877014] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877278] amdgpu_pci_probe+0x182/0x450 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877541] local_pci_probe+0x47/0xb0 Mar 7 19:07:10 ripper kernel: [9.877545] pci_call_probe+0x55/0x190 Mar 7 19:07:10 ripper kernel: [9.877550] pci_device_probe+0x84/0x120 Mar 7 19:07:10 ripper kernel: [9.877553] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.877557] really_probe+0x1cc/0x430 Mar 7 19:07:10 ripper kernel: [9.877560] __driver_probe_device+0x8c/0x190 Mar 7 19:07:10 ripper kernel: [9.877563] driver_probe_device+0x24/0xd0 Mar 7 19:07:10 ripper kernel: [9.877566] __driver_attach+0x10b/0x210 Mar 7 19:07:10 ripper kernel: [9.877569] ? __pfx___driver_attach+0x10/0x10 Mar 7 19:07:10 ripper kernel: [9.877572] bus_for_each_dev+0x8d/0xf0 Mar 7 19:07:10 ripper kernel: [9.877576] driver_attach+0x1e/0x30 Mar 7 19:07:10 ripper kernel: [9.877579] bus_add_driver+0x127/0x240 Mar 7 19:07:10 ripper kernel: [9.877583] driver_register+0x5e/0x130 Mar 7 19:07:10 ripper kernel: [9.877586] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877849] __pci_register_driver+0x62/0x70 Mar 7 19:07:10 ripper kernel: [9.877852] amdgpu_init+0x69/0xff0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.878111] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878114] do_one_initcall+0x5e/0x340 Mar 7 19:07:10 ripper kernel: [9.878120] do_init_module+0x68/0x260 Mar 7 19:07:10 ripper kernel: [9.878123] load_module+0xb85/0xcd0 Mar 7 19:07:10 ripper kernel: [9.878128] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878131] ? security_kernel_post_read_file+0x75/0x90 Mar 7 19:07:10 ripper kernel: [9.878136] init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878139] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878142] ? init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878149] idempotent_init_module+0x11c/0x2b0 Mar 7 19:07:10 ripper kernel: [9.878155] __x64_sys_finit_module+0x64/0xd0 Mar 7 19:07:10 ripper kernel: [9.878159] do_syscall_64+0x5b/0x90 Mar 7 19:07:10
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048951] Re: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux-image-6.5.0-18-generic (linux-image-generic-hwe-22.04)
Still reproducible with 6.5.0-25-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048951 Title: Kernel Oops - kernel NULL pointer dereference (apparmor_bprm_creds_for_exec, profile_transition) with linux- image-6.5.0-18-generic (linux-image-generic-hwe-22.04) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Today one of my NUCs got new kernel 6.5.0-14 and the host started to hang few minutes after the boot. I can't find anything in the journal for the previous boot it just ends without any error. Remote syslog server does not receive any error log from this host. I've tried running journalctl on the local console and wait for the hang got nothing. On the screen (this is Ubuntu Server) I see 18 hex numbers at the top of the screen and the rest is what was on the console before the hang: ff ff 73 01 c3 48 8b 0d 74 ed 12 00 f7 d8 64 89 01 48 Booting the previous HWE linux-image-6.2.0-39-generic fixes the issue, so it is definitely the new kernel. I don't have enough time to generate report with ubuntu-bug on the new kernel, so attaching dmidecode, lspci, lsusb and dmesg from the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2048951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056594] [NEW] apply nvidia-tegra patches 2024 Mar 8
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056585] [NEW] Asus Vivobook Go E1404FA - snd_intel_hda not detecting built-in microphone - ALC897 / ALC256
Public bug reported: [Impact] Built-in microphone of the laptop is not detected and thus does not work. [Fix] None identified so far. [Test Case] Have Ubuntu 22.04 LTS installed on an Asus Vivobook Go E1404FA, using the 6.5 HWE kernel. Open the Sound settings and set the device "Family 17h [...]" to stereo duplex: The builtin speakers work but the internal microphone does not show up. Checking dmesg for snd-hda-intel shows nothing under inputs for the device. The follow module options for snd-hda-intel have no effect: model=auto model=laptop-amic [Where problems could occur] Likely in hardware detection for the snd-hda-intel module [Other Info] mittebam@duchesse:~$ cat /proc/version_signature Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 mittebam@duchesse:~$ lspci | grep Audio 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1640 03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 6f) 03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller mittebam@duchesse:~$ sudo dmidecode -H 0x0032 # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 3.5.0 present. Table at 0xBACE6000. Handle 0x0032, DMI type 41, 11 bytes Onboard Device Reference Designation: Realtek ALC256 Type: Sound Status: Enabled Type Instance: 1 Bus Address: :03:00.6 mittebam@duchesse:~$ sudo dmesg | grep snd [6.284080] snd_pci_acp6x :03:00.5: enabling device ( -> 0002) [6.416621] snd_hda_intel :03:00.1: enabling device ( -> 0002) [6.417219] snd_hda_intel :03:00.1: Handle vga_switcheroo audio client [6.417431] snd_hda_intel :03:00.6: enabling device ( -> 0002) [6.438262] snd_hda_intel :03:00.1: bound :03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [6.450675] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC897: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [6.450685] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [6.450690] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [6.450693] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0 [6.450696] snd_hda_codec_realtek hdaudioC1D0:inputs: mittebam@duchesse:~$ lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 mittebam@duchesse:~$ apt-cache policy linux-image-generic-hwe-22.04 linux-image-generic-hwe-22.04: Installed: 6.5.0.25.25~22.04.12 Candidate: 6.5.0.25.25~22.04.12 Version table: *** 6.5.0.25.25~22.04.12 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages mittebam@duchesse:~$ apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.25.25~22.04.12 Candidate: 6.5.0.25.25~22.04.12 Version table: *** 6.5.0.25.25~22.04.12 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages mittebam@duchesse:~$ apt-cache policy firmware-sof-signed firmware-sof-signed: Installed: 2.0-1ubuntu4.5 Candidate: 2.0-1ubuntu4.5 Version table: *** 2.0-1ubuntu4.5 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/restricted i386 Packages 100 /var/lib/dpkg/status 2.0-1ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu jammy/restricted i386 Packages ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci_vnvn.log" https://bugs.launchpad.net/bugs/2056585/+attachment/5754121/+files/lspci_vnvn.log ** Package changed: linux (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056585 Title: Asus Vivobook Go E1404FA - snd_intel_hda not detecting built-in microphone - ALC897 / ALC256 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: [Impact] Built-in microphone of the laptop is not detected and thus does not work. [Fix] None identified so far. [Test Case] Have Ubuntu 22.04 LTS installed on an Asus Vivobook Go E1404FA, using the 6.5 HWE kernel. Open the Sound settings and set the device "Family 17h [...]" to stereo duplex: The builtin speakers work but the internal microphone does not show up. Checking
[Kernel-packages] [Bug 2056354] Re: qat: Improve error recovery flows
** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056354 Title: qat: Improve error recovery flows Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: [Impact] This set improves the error recovery flows in the QAT drivers and adds a mechanism to test it through an heartbeat simulator. This is an upstream patch set applied to linux-next and scheduled for 6.9. Link to the upstream submission: https://patchwork.kernel.org/project/linux-crypto/cover/20240202105324.50391-1-mun.chun@intel.com/ We should apply this set to the Noble 6.8 kernel, in order to experience less issues with qat and improve maintainability. An added commit is required to update the configuration. [Test case] Unload and reload the module to verify that qat recover and log issues properly. Use the added error injection mechanism to verify the recovery flow. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Paolo, I was able to install it (image from March 1st `20240301`) , update to the bootstrap kernel from the PPA you sent: patricia@noble-1mar:~$ cat /var/log/installer/media-info Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily ppc64el (20240301)patricia@noble-1mar:~$ patricia@noble-1mar:~$ apt list --upgradable |grep linux-gen linux-generic/noble 6.8.0-15.15 ppc64el [upgradable from: 6.8.0-11.11+1] ... and boot: patricia@noble-1mar:~$ uname -a Linux noble-1mar 6.8.0-15-generic #15-Ubuntu SMP Mon Mar 4 12:38:17 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056574] ss2
Default Comment by Bridge ** Attachment added: "ss2" https://bugs.launchpad.net/bugs/2056574/+attachment/5754069/+files/Captura_de_pantalla_2024-03-06_202037.png ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056574 Title: Can't install Ubuntu 23.10 bot from SAN Status in linux package in Ubuntu: New Bug description: == Comment:- Melisa Arzola Ruiz == ---Problem Description--- I want to install the Ubuntu 23.10 version and the installer has restarted for an error Contact Information = melisa.arz...@ibm.com ---Steps to Reproduce--- Insert an USB With an Ubuntu 23.10 image try to install the operative system select the LUN (should be bot from SAN) the installer crash ---uname output--- N/A ---Debugger--- A debugger is not configured ---Additional Hardware Info--- hosts HBA Brand:Lenovo Model: X3650 M5: 5462-AC1 Memory: 64 GB HBA Brand:Lenovo Model: LPe32002-M2-L Brand:EMULEX Model: 10GbE VFA3 PCIe: IBM 95Y3766 DS8000 Release 9.4 bundle 89.40.48.0 Product DS8910F Connected via Fiber channel on switches Brand: Broadcomm Model: G620 Brand:BROCADE Model: G630 Machine Type = Lenovo X3650 M5: 5462-AC1 Userspace tool common name: N/A Userspace rpm: N/A The userspace tool has the following bit modes: N/A Userspace tool obtained from project website: na *Additional Instructions for melisa.arz...@ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. -Attach: /proc/partitions /proc/mounts/ /etc/lvm/lvm.conf dmsetup ls dmsetup table dmsetup targets dmsetup version lvm version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056574] [NEW] Can't install Ubuntu 23.10 bot from SAN
You have been subscribed to a public bug: == Comment:- Melisa Arzola Ruiz == ---Problem Description--- I want to install the Ubuntu 23.10 version and the installer has restarted for an error Contact Information = melisa.arz...@ibm.com ---Steps to Reproduce--- Insert an USB With an Ubuntu 23.10 image try to install the operative system select the LUN (should be bot from SAN) the installer crash ---uname output--- N/A ---Debugger--- A debugger is not configured ---Additional Hardware Info--- hosts HBA Brand: Lenovo Model: X3650 M5: 5462-AC1 Memory: 64 GB HBA Brand: Lenovo Model: LPe32002-M2-L Brand: EMULEX Model: 10GbE VFA3 PCIe: IBM 95Y3766 DS8000 Release 9.4 bundle 89.40.48.0 Product DS8910F Connected via Fiber channel on switches Brand: Broadcomm Model: G620 Brand: BROCADE Model: G630 Machine Type = Lenovo X3650 M5: 5462-AC1 Userspace tool common name: N/A Userspace rpm: N/A The userspace tool has the following bit modes: N/A Userspace tool obtained from project website: na *Additional Instructions for melisa.arz...@ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. -Attach: /proc/partitions /proc/mounts/ /etc/lvm/lvm.conf dmsetup ls dmsetup table dmsetup targets dmsetup version lvm version ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-x86all bugnameltc-205799 severity-high targetmilestone-inin2310 -- Can't install Ubuntu 23.10 bot from SAN https://bugs.launchpad.net/bugs/2056574 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056451]
Correction, I meant to say: Course bisect, 5.15 OK, 6.5.0 onwards fail, so this looks like a regression -- 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/2056451 Title: hfs: concurrent create/unlink can trip -EEXIST on non-existent files Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Summary: create hfs file system, loop-back mount it, run filename stressor with stress-ng to exercise filename create/stat/unlink and we get unexpected -EEXIST errors. This can be worked around by adding a sync() call after the unlink() to ensure metadata is sync'd. Kernel: 6.8.0-11-generic test case: sudo apt-get install hfsprogs dd if=/dev/zero of=fs.img bs=1M count=2048 mkfs.hfs fs.img sudo mount fs.img /mnt sudo mkdir /mnt/x sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20 stress-ng: info: [132412] setting to a 20 secs run per stressor stress-ng: info: [132412] dispatching hogs: 8 filename stress-ng: fail: [132424] filename: open failed on file of length 1 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 20 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132421] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132426] filename: open failed on file of length 23 bytes, errno=17 (File exists) stress-ng: fail: [132425] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 1 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 7 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 11 bytes, errno=17 (File exists) stress-ng: fail: [132426] filename: open failed on file of length 24 bytes, errno=17 (File exists) adding a sync() call in the stress-ng stressor fixes the issue: git diff diff --git a/stress-filename.c b/stress-filename.c index a64898fb1..b8266f91e 100644 --- a/stress-filename.c +++ b/stress-filename.c @@ -308,6 +308,7 @@ static void stress_filename_test( VOID_RET(int, shim_stat(filename, &buf)); (void)shim_unlink(filename); + (void)sync(); } /* exercise dcache lookup of non-existent filename */ sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20 stress-ng: info: [132461] setting to a 20 secs run per stressor stress-ng: info: [132461] dispatching hogs: 8 filename stress-ng: info: [132461] skipped: 0 stress-ng: info: [132461] passed: 8: filename (8) stress-ng: info: [132461] failed: 0 stress-ng: info: [132461] metrics untrustworthy: 0 stress-ng: info: [132461] successful run completed in 20.05 secs The sync should not be required by the way, I just added it to illustrate that there is a racy metadata sync issue in hfs. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056451]
Course bisect, 4.4 to 5.15 OK, 6.5.0 onwards fail, so this looks like a regression -- 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/2056451 Title: hfs: concurrent create/unlink can trip -EEXIST on non-existent files Status in Linux: Confirmed Status in linux package in Ubuntu: New Bug description: Summary: create hfs file system, loop-back mount it, run filename stressor with stress-ng to exercise filename create/stat/unlink and we get unexpected -EEXIST errors. This can be worked around by adding a sync() call after the unlink() to ensure metadata is sync'd. Kernel: 6.8.0-11-generic test case: sudo apt-get install hfsprogs dd if=/dev/zero of=fs.img bs=1M count=2048 mkfs.hfs fs.img sudo mount fs.img /mnt sudo mkdir /mnt/x sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20 stress-ng: info: [132412] setting to a 20 secs run per stressor stress-ng: info: [132412] dispatching hogs: 8 filename stress-ng: fail: [132424] filename: open failed on file of length 1 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 20 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132421] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132426] filename: open failed on file of length 23 bytes, errno=17 (File exists) stress-ng: fail: [132425] filename: open failed on file of length 30 bytes, errno=17 (File exists) stress-ng: fail: [132428] filename: open failed on file of length 1 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 7 bytes, errno=17 (File exists) stress-ng: fail: [132423] filename: open failed on file of length 11 bytes, errno=17 (File exists) stress-ng: fail: [132426] filename: open failed on file of length 24 bytes, errno=17 (File exists) adding a sync() call in the stress-ng stressor fixes the issue: git diff diff --git a/stress-filename.c b/stress-filename.c index a64898fb1..b8266f91e 100644 --- a/stress-filename.c +++ b/stress-filename.c @@ -308,6 +308,7 @@ static void stress_filename_test( VOID_RET(int, shim_stat(filename, &buf)); (void)shim_unlink(filename); + (void)sync(); } /* exercise dcache lookup of non-existent filename */ sudo stress-ng --temp-path /mnt/x --filename 8 --filename-opts posix -t 20 stress-ng: info: [132461] setting to a 20 secs run per stressor stress-ng: info: [132461] dispatching hogs: 8 filename stress-ng: info: [132461] skipped: 0 stress-ng: info: [132461] passed: 8: filename (8) stress-ng: info: [132461] failed: 0 stress-ng: info: [132461] metrics untrustworthy: 0 stress-ng: info: [132461] successful run completed in 20.05 secs The sync should not be required by the way, I just added it to illustrate that there is a racy metadata sync issue in hfs. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056354] Re: qat: Improve error recovery flows
** Summary changed: - qat: Improve error/reset handling + qat: Improve error recovery flows -- 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/2056354 Title: qat: Improve error recovery flows Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] This set improves the error recovery flows in the QAT drivers and adds a mechanism to test it through an heartbeat simulator. This is an upstream patch set applied to linux-next and scheduled for 6.9. Link to the upstream submission: https://patchwork.kernel.org/project/linux-crypto/cover/20240202105324.50391-1-mun.chun@intel.com/ We should apply this set to the Noble 6.8 kernel, in order to experience less issues with qat and improve maintainability. An added commit is required to update the configuration. [Test case] Unload and reload the module to verify that qat recover and log issues properly. Use the added error injection mechanism to verify the recovery flow. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux/4.15.0-223.235 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-bionic-linux' to 'verification-done-bionic-linux'. If the problem still exists, change the tag 'verification-needed-bionic- linux' to 'verification-failed-bionic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-v2 verification-needed-bionic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
SRU request submitted to the Ubuntu kernel team mailing list for mantic, lunar and jammy. https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149437 Changing status to 'In Progress' for jammy and focal. ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). * The remaning 6 commits are needed for HVCS, that is essentially broken without them. Overall, issues they fix are race conditions, hotplug remove issues, as well as memory leaks. * Please notice that this is entirely ppc64el architecture-specifc. [Other Info] * All the commits listed above are included in mantic and noble. Hence these are set to Invalid. * Meanwhile these requested commits have been added to other kernels and distros. __ ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging
[Kernel-packages] [Bug 2038443] Re: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected.
*** This bug is a duplicate of bug 2051932 *** https://bugs.launchpad.net/bugs/2051932 ** This bug has been marked a duplicate of bug 2051932 attach_disconnected test from test_regression_testsuite of ubuntu_qrt_apparmor failed with "Unable to run test sub-executable" on Mantic -- 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/2038443 Title: mantic:linux: ubuntu_qrt_apparmor: ApparmorTestsuites.test_regression_testsuiteattach_disconnected. Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Confirmed Bug description: This might be apparmor, the test case, kernel or anything in between: 7720s running attach_disconnected 7720s Fatal Error (unix_fd_server): Unable to run test sub-executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2038443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Here is the latest crash file. Unresponsive - even trying ssh won't work ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754028/+files/prevboot.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/2054121 Title: Random Freezing Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-545 package in Ubuntu: Incomplete Bug description: Random lockups in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28 15:37:48 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 09:08:41 2024 DistUpgraded: Fresh install DistroCodename: mantic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db] InstallationDate: Installed on 2024-02-16 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: M3JKT3CA dmi.board.name: 32DD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305435660291 dmi.chassis.type: 35 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny: dmi.product.family: ThinkStation P350 Tiny dmi.product.name: 30EF004VUS dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny dmi.product.version: ThinkStation P350 Tiny dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
** Description changed: + SRU Justification: + == + + [Impact] + + * HVCS (Hypervisor Virtual Console Server) is broken because the +virtual terminal mkvterm fails, caused by pvmutil failing. + + * When mkvterm is ran, it ultimately fails because it calls pvmutil +which fails. +pvmutil calls drmgr, and drmgr is adding a slot correctly. +However, when drmgr writes the slot information to ?/add_slot, +the return is -ENODEV. + + * This leads to HVCS never having probe() called. + + * In addition, HVCS is missing patches/fixes, and is broken without + them. + + [Fix] + + * Fix one and two is required for focal only, all other for focal and + jammy: + + * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 +"powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" + + * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa +"powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" + + * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc +"hvcs: Fix hvcs port reference counting" + + * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 +"hvcs: Use dev_groups to manage hvcs device attributes" + + * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a +"hvcs: Use driver groups to manage driver attributes" + + * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 +"hvcs: Get reference to tty in remove" + + * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 +"hvcs: Use vhangup in hotplug remove" + + * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f +"hvcs: Synchronize hotplug remove with port free" + + [Test Plan] + + * The high level test plan is to run mkvterm with an id. + + * mkvterm will fail because /dev/hvcs* device nodes are missing. + + * Details see https://bugs.launchpad.net/bugs/2023243 for more information. +Especially the script provided by IBM +(see original bug description: `---Steps to Reproduce---`). + + * IBM will (stress) test the updated kernel(s) provided in -proposed. + + [Where problems could occur] + + * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c +and are needed to fix the hotplugging issue seen when drmgr goes to write +the slot information to /sys/bus/pci/slots/control/add_slot. +In case of issues here hotplugging with drmgr might break. + + * The issue lies in rpadlpar_io and rpaphp calling an of helper function +of_read_drc_info_cell(). Without these commits, the value stored +drc_index_start is incorrect. +This ultimately results in the entire SLOT string being incorrect, +and rpaphp never finding the newly added slot by drmgr. +rpadlpar then returns -ENODEV. +Therefore, HVCS is never probed, and the device nodes are never created. + + * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded +prior to drmgr adding a vio slot. +If rpadlpar_io and rpaphp are not loaded, drmgr will load them. +In addition, if rpadlpar_io and rpaphp register the new slot correctly, +rpadlpar_io will call dlpar_add_vio_slot(), +which calls vio_register_device_node() with the device node. +This is what tells the driver core to init and probe HVCS +(which is needed to create the device nodes). + + * The remaning 6 commits are needed for HVCS, that is essentially +broken without them. +Overall, issues they fix are race conditions, hotplug remove issues, +as well as memory leaks. + + * Please notice that this is entirely ppc64el architecture-specifc. + + [Other Info] + + * All the commits listed above are included in mantic and noble. +Hence these are set to Invalid. + + * Meanwhile these requested commits have been added to other +kernels and distros. + __ + ---Problem Description--- - Issues with HVCS and hotplugging issues. + Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. - When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. - + When mkvterm is ran, it ultimately fails because it calls pvmutil which + fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. + However, when drmgr writes the slot information to ?/add_slot, the + return is -ENODEV. This leads to HVCS never having probe() called. In + addition, HVCS is missing patches, and is broken without them. 8 kernel + patches have been ident
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
Currently test kernels are being build for focal/20.04 and jammy/22.04 in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp2056373 ** Changed in: linux (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: ubuntu-power-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. ---uname output--- Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information. 2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug. The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). In addition to the 2 commits mentioned above, 6 HVCS commits are needed. HVCS is essentially broken without them. Issues include race conditions, hotplug remove issues, as well as memory leaks. These commits have been added to other distros after multiple issues were seen. Without these commits, 20.04 will experience the same issues. IBM plans on stress testing these changes after an updated kernel is provided in focal-proposed. --- 2 commits that make changes to arch/powerpc/platforms/pseries/of_helpers.c: powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57409d4fb12c185b2c0689e0496878c8f6bb5b58 powerpc/pseries: Fix of_read_drc_info_cell() to point at next record https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5e76fa05b2df519b9f08571cc57e623c1569faa HVCS commits: hvcs: Fix hvcs port reference counting https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9a733edd46732e906d976dc21a42dd361e53cc hvcs: Use dev_groups to manage hvcs device attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=760aa5e81f33e0da82512c4288489739a6d1c556 hvcs: Use driver groups to manage driver attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=503a90dd619d52dcac2cc68bd742aa914c7cd47a hvcs: Get reference to tty in remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a8d3b366ce47024bf274eac783f8af5df2780f5 hvcs: Use vhangup in hotplug remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d432228bc7b1b3f0ed
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
** Summary changed: - Multiple issues found on Ubuntu 20.04 against HVCS + Problems with HVCS and hotplugging -- 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/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. ---uname output--- Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information. 2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug. The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). In addition to the 2 commits mentioned above, 6 HVCS commits are needed. HVCS is essentially broken without them. Issues include race conditions, hotplug remove issues, as well as memory leaks. These commits have been added to other distros after multiple issues were seen. Without these commits, 20.04 will experience the same issues. IBM plans on stress testing these changes after an updated kernel is provided in focal-proposed. --- 2 commits that make changes to arch/powerpc/platforms/pseries/of_helpers.c: powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57409d4fb12c185b2c0689e0496878c8f6bb5b58 powerpc/pseries: Fix of_read_drc_info_cell() to point at next record https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5e76fa05b2df519b9f08571cc57e623c1569faa HVCS commits: hvcs: Fix hvcs port reference counting https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9a733edd46732e906d976dc21a42dd361e53cc hvcs: Use dev_groups to manage hvcs device attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=760aa5e81f33e0da82512c4288489739a6d1c556 hvcs: Use driver groups to manage driver attributes https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=503a90dd619d52dcac2cc68bd742aa914c7cd47a hvcs: Get reference to tty in remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a8d3b366ce47024bf274eac783f8af5df2780f5 hvcs: Use vhangup in hotplug remove https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d432228bc7b1b3f0ed06510278ff5a77b3749fe6 hvcs: Synchronize hotplug remove with port free https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f To manage notifications about this bug go to: https://bugs.launchpad.ne
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Changed in: initramfs-tools (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Can you update a working image to the latest bootstrap kernel and try again? https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap - 6.8.0-15.15 -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056373] Re: Multiple issues found on Ubuntu 20.04 against HVCS
Hello and many thanks for raising these HVCS issue. I first of all analyzed the commits upstream and in the specific Ubuntu kernel trees and found that focal and to some extend jammy are affected. Mantic and noble are not affected: commit 57409d4fb12c got upstream accepted with v5.5(-rc1) commit c5e76fa05b2d got upstream accepted with v5.7(-rc1) commit 6a9a733edd46 got upstream accepted with v6.3(-rc1) commit 760aa5e81f33 got upstream accepted with v6.3(-rc1) commit 503a90dd619d got upstream accepted with v6.3(-rc1) commit 3a8d3b366ce4 got upstream accepted with v6.3(-rc1) commit d432228bc7b1 got upstream accepted with v6.3(-rc1) commit 28d49f8cbe9c got upstream accepted with v6.3(-rc1) commits/release focal jammy mantic noble 57409d4fb12cn y y y c5e76fa05b2dn y y y 6a9a733edd46n n y y 760aa5e81f33n n y y 503a90dd619dn n y y 3a8d3b366ce4n n y y d432228bc7b1n n y y 28d49f8cbe9cn n y y So I'm adding focal and jammy as targets. ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Also affects: linux (Ubuntu Noble) Importance: High Status: Invalid ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Importance: High => Undecided ** Changed in: linux (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056373 Title: Multiple issues found on Ubuntu 20.04 against HVCS Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Triaged Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: ---Problem Description--- Issues with HVCS and hotplugging issues. When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot. When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues. ---uname output--- Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information. 2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug. The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). In addition to