[Kernel-packages] [Bug 1986587] Re: Disable no longer supported architectures
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => High ** Changed in: linux (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1986587 Title: Disable no longer supported architectures Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Bug description: [Impact] Building some arches will take a long time. Disabling the ones that are not supported will help accelerate release of emergency respins. [Test case] Verify that when building on a PPA, only amd64 is built. [Potential regression] Some packages may stop being built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986587/+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 1953345] Re: memcg is disabled in v5.15 RT kernel (known issue)
This issue does not exist on J-realtime anymore. INFO: Test start time: Tue Aug 16 06:08:56 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 648348 -n 648348 -f /tmp/ltp-qVqxKBH0Bi/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... pids 1 TINFO: timeout per run is 0h 5m 0s pids 1 TINFO: test starts with cgroup version 2 pids 1 TINFO: Running testcase 1 with 1 processes pids 1 TPASS: fork didn't fail Summary: passed 1 failed 0 broken 0 skipped 0 warnings 0 INFO: ltp-pan reported all tests PASS LTP Version: 20220527 INFO: Test end time: Tue Aug 16 06:08:56 UTC 2022 ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- 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/1953345 Title: memcg is disabled in v5.15 RT kernel (known issue) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: From v5.15.2-rt20 announcement: Known issues: - The "Memory controller" (CONFIG_MEMCG) has been disabled. This might be the cause of ubuntu_ltp_controllers failure - ubuntu_ltp_controllers.pids_1_100: ## COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 466487 -n 466487 -f /tmp/ltp-DbBcUelSWj/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... pids 1 TINFO: timeout per run is 0h 5m 0s mount: /dev/cgroup: none already mounted on /sys/fs/bpf. pids 1 TBROK: mount -t cgroup -o pids none /dev/cgroup failed pids 1 TINFO: removing created directories rmdir: failed to remove '/dev/cgroup/ltp_pids_1': No such file or directory pids 1 TINFO: Umounting pids umount: /dev/cgroup: not mounted. pids 1 TINFO: AppArmor enabled, this may affect test results pids 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) pids 1 TINFO: loaded AppArmor profiles: none ## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953345/+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 1895426] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1895426 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tirtha 1397 F pulseaudio CasperMD5CheckResult: skip Date: Sun Sep 13 11:45:12 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=a24d343d-9753-4460-ac8f-43882d4197c7 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
1049 has been in proposed since Friday, have you been able to test it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy)
Fixed with LTP fork update (bug 1982995) With LTP fork updated, the ubuntu_ltp_controllers on Jammy is now failing with: * LP: #1986636 cpuset_inherit|cpuset_base_ops|cpuset_exclusive|cpuset_hierarchy| cpuset_syscall|cpuset_sched_domains|cpuset_load_balance| cpuset_hotplug|cpuset_memory|cpuset_memory_pressure * LP: #1986638 cpuset_regression_test ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) -- 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish ($cgroup_name already mounted or mount point busy) Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Won't Fix Bug description: Almost half of the ubuntu_ltp_controllers tests (142 out of 198) are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there could be an issue with the transition to cgroup-v2. There have been rumors on the ltp mailing list that one of these days the tests could break due to the transition. Switching to cgroup-v2, likely due to a systemd update, could cause these tests to break due to different mount and cgroup hierarchy semantics. I could only reproduce a subset of the new failures we are seeing, but after setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, a lot of the failures I could produce went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+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 1983108] Re: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371]
> that would break most of the software already installed and would leave me exposed to security bugs Incorrect. Apps generally don't know the difference between kernel versions and even the "old" 5.4 focal kernel is still supported with security updates (last one was 6 days ago): https://launchpad.net/ubuntu/+source/linux > I expect that in the future the nouveau driver will become the only one anyway and the Nvidia drivers will be integrated in it. I don't expect that. I would expect Nvidia to maintain the 'nvidia' kernel driver independently from the 'nouveau' driver that they did not write themselves. I would also not expect Nvidia to start supporting older GPUs that they already consider retired today. You might wait for the community to improve 'nouveau' with the newly released data but I would not hold my breath since many Nvidia GPUs have been waiting years already. So I expect your only realistic option is to install the original Ubuntu 20.04 (https://old- releases.ubuntu.com/releases/20.04/ubuntu-20.04-desktop-amd64.iso) which should keep you on kernel 5.4 (with security updates) and with a working nvidia-340 driver. This bug remains open waiting for nouveau fixes, but they might never come. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371] Status in linux-hwe-5.15 package in Ubuntu: New Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
Yeah there are positive test results in bug 1978067. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984117] Re: [VROC] Kernel panic during reshape - probably missing patch
Logs are added in description instead of attachment. Changing to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984117 Title: [VROC] Kernel panic during reshape - probably missing patch Status in linux package in Ubuntu: Confirmed Bug description: Bug found for Jammy (22.04) Steps to reproduce: 1. Create 3 partitions with parted tool on initial non-RAID drive # parted -s /dev/nvme6n1 mklabel gpt # parted -s /dev/nvme6n1 mkpart primary ext4 0% 30% # parted -s /dev/nvme6n1 mkpart primary btrfs 30% 60% # parted -s /dev/nvme6n1 mkpart primary xfs 60% 90% 2. Create filesystem on each partition # mkfs.ext4 /dev/nvme6n1p1 # mkfs.ext4 /dev/nvme6n1p2 # mkfs.ext4 /dev/nvme6n1p3 4. Create RAID container # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme4n1 /dev/nvme2n1 /dev/nvme1n1 --run –force 5. Create RAID on drive with data # mdadm --create /dev/md/volume --level=0 --chunk 64 --raid-devices=1 /dev/nvme6n1 --run –force 6. Make sure GPT data structures are in proper place # sgdisk -e /dev/md/volume 7. Grow temporary RAID 0 volume with two devices. Wait for reshape end. # mdadm --grow /dev/md/imsm0 --raid-devices=2 8. Grow temporary RAID 0 to RAID 10 # mdadm --grow /dev/md/volume --level=10 Results: Recovery starts but frozen. Kernel BUG occurs: [ 724.885252] md: recovery of RAID array md126 [ 724.885956] [ cut here ] [ 724.885960] kernel BUG at drivers/md/raid10.c:928! [ 724.891527] invalid opcode: [#1] SMP NOPTI [ 724.896736] CPU: 5 PID: 4872 Comm: md126_resync Not tainted 5.15.0-25-generic #25-Ubuntu [ 724.905943] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.SYS.0079.D34.2205030421 05/03/2022 [ 724.917839] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 724.923896] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 724.945031] RSP: 0018:ff3c62714464fbd8 EFLAGS: 00010246 [ 724.950978] RAX: RBX: ff3282bd578e4c00 RCX: [ 724.959064] RDX: RSI: 0001 RDI: ff3282bd578e4c00 [ 724.967154] RBP: ff3c62714464fc28 R08: ff3282b9cf23ca00 R09: 0001 [ 724.975239] R10: 0293 R11: ff3282bcae577590 R12: ff3282b9cf23ca00 [ 724.983306] R13: 0003 R14: 0080 R15: ff3282bd578e4c00 [ 724.991405] FS: () GS:ff3282bcae54() knlGS: [ 725.000572] CS: 0010 DS: ES: CR0: 80050033 [ 725.007105] CR2: 7f086b758a50 CR3: 44010001 CR4: 00771ee0 [ 725.015209] DR0: DR1: DR2: [ 725.023295] DR3: DR6: fffe07f0 DR7: 0400 [ 725.031391] PKRU: 5554 [ 725.034514] Call Trace: [ 725.037360] [ 725.039787] ? bio_reset+0x12/0x50 [ 725.043721] ? raid10_alloc_init_r10buf+0x6d/0xc0 [raid10] [ 725.049966] raid10_sync_request+0x77c/0x1600 [raid10] [ 725.055832] md_do_sync.cold+0x42c/0xa17 [ 725.060331] md_thread+0xaa/0x160 [ 725.064144] ? md_write_inc+0x50/0x50 [ 725.068350] kthread+0x127/0x150 [ 725.072055] ? set_kthread_struct+0x50/0x50 [ 725.076850] ret_from_fork+0x1f/0x30 [ 725.080963] [ 725.083515] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter bridge stp llc nf_tables nfnetlink nvme_fabrics intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl snd_hda_core snd_hwdep snd_pcm snd_timer snd efi_pstore joydev input_leds isst_if_mbox_pci pmt_telemetry idxd pmt_crashlog isst_if_mmio mei_me soundcore pmt_class isst_if_common mei idxd_bus ipmi_ssif acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 725.083585] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvme nvme_core hid_generic usbhid ast i2c_algo_bit hid drm_vram_helper drm_ttm_helper ttm ax88179_178a drm_kms_helper usbnet
[Kernel-packages] [Bug 1986668] [NEW] [VROC] Kernel does not contain fixes for iostat for md devices
Public bug reported: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: vroc ** Description changed: Hello, - I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not - contain fixes for IO statistics for md devices. IO statistics for md - devices were added to kernel 5.10 + I noticed that kernel which was used in ubuntu 22.04 does not contain + fixes for IO statistics for md devices. IO statistics for md devices + were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska -- 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/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Incomplete Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+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 1986668] 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 1986668 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/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Incomplete Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+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 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Ok, sorry, I didn't understand which kernel is used in Jammy correctly. I've opened new bug for 22.04 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668 . Verification for Kinetic in progress, I will let you know here if issue is reproducible there. -- 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/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+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 1983108] Re: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371]
Installing version 20.04 would get me stuck with the previous version of apps and libraries, and that would be more annoying that dealing with the bug (since it usually doesn't occur, and when it occurs it usually just require a system restart. Also, I replaced the Nvidia driver with nouveau since more than one year, and this specific bug occurred only in the last two months, so in general nouveau worked well for me (although it hanged on some web games). In some aspects, nouveau worked even better than the proprietary driver (for example, it allowed to use the text mode framebuffer at high resolution, while the proprietary driver didn't, it worked only for the xwindow mode) Last but not least: when booting from CD only nouveau driver is available anyway. So, as long as it's possible, I will wait for a fix: I am aware it might not come soon, but it would never come if no one reports the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371] Status in linux-hwe-5.15 package in Ubuntu: New Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983108/+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 1986668] Re: [VROC] Kernel does not contain fixes for iostat for md devices
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Confirmed Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13&qt=author&q=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+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 1983108] Re: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371]
Another option is to hope the issue is limited to plymouthd and just disable plymouthd with a kernel parameter: nosplash BTW newer Nvidia drivers (versions >= 510 at least) have fixed the text mode framebuffer resolution problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371] Status in linux-hwe-5.15 package in Ubuntu: New Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983108/+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 1986623] Re: cryptsetup fails to decrypt root partion during boot
** Changed in: cryptsetup (Ubuntu) Importance: Undecided => Critical ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1986623 Title: cryptsetup fails to decrypt root partion during boot Status in cryptsetup package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, digest 0. # Digest 0 (pbkdf2) verify failed with -1. # Trying to open LUKS2 keyslot 1. # Running keyslot key derivation. # Reading keyslot area [0x47000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvm
[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU
@koba I installed thermald_2.5.0-1_amd64 from Debian Sid (sha256 19840c0dffd4424996016293dcbd9402595cdb5c0b1c709f94f08a717a239b2e) just by grabbing the .deb and installing it Started the service and ran a quick test. My graphics card reached a peak of 81°C with no in-game slowdown whatsoever I hope that grabbing it from Debian was okay, I wanted to just keep it as a deb file with no hassle in case something wasn't right, ease of setup etc etc Is that test valid? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: New Bug description: I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 1986623] 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 1986623 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/1986623 Title: cryptsetup fails to decrypt root partion during boot Status in cryptsetup package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: During boot, cryptsetup fails to decrypt the root partition in a, seemingly, non-deterministic fashion. I know that the password is correct and that the keymap is not a fault either, because I have specifically chosen the very weak password "123456" for testing purposes. A hardware defect seems also rather unlikely as this behavior does not affect other Linux distributions or FreeBSD. Earlier Ubuntu versions do not seem to be affected either, as this bug appears to have been introduced during a kernel update in 20.04 and persists throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact kernel update that introduced this bug. I have appended the output of cryptsetup when manually called from the initramfs shell. Here the second attempt succeeded in decrypting the root partition, however, it usually takes a lot more attempts to do so. As for some additional information, I can decrypt the same luks partition from a live USB without any problems whatsoever. echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug /dev/nvme0n1p3 nvme0n1p3_crypt" # Running command open. # Locking memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. # Allocating context for crypt device /dev/nvme0n1p3. # Trying to open and read device /dev/nvme0n1p3 with direct-io. # Initialising device-mapper backend library. # Trying to load any crypt type from device /dev/nvme0n1p3. # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in cryptsetup library version 2.4.3. # Detected kernel Linux 5.15.0-46-generic x86_64. # Loading LUKS2 header (repair disabled). # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Trying to read primary LUKS2 header at offset 0x0. # Opening locked device /dev/nvme0n1p3 # Verifying locked device handle (bdev) # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (on-disk) # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc (in-memory) # Trying to read secondary LUKS2 header at offset 0x4000. # Reusing open ro fd on device /dev/nvme0n1p3 # LUKS2 header version 2 of size 16384 bytes, checksum sha256. # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (on-disk) # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c (in-memory) # Device size 497776852992, offset 16777216. # Device /dev/nvme0n1p3 READ lock released. # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, parallel_threads 4. # Activating volume nvme0n1p3_crypt using token (any type) -1. # dm version [ opencount flush ] [16384] (*1) # dm versions [ opencount flush ] [16384] (*1) # Detected dm-ioctl version 4.45.0. # Detected dm-crypt version 1.23.0. # Device-mapper backend running with UDEV support enabled. # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) No usable token is available. # STDIN descriptor passphrase entry requested. # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase. # dm versions [ opencount flush ] [16384] (*1) # dm status nvme0n1p3_crypt [ opencount noflush ] [16384] (*1) # Keyslot 0 priority 1 != 2 (required), skipped. # Keyslot 1 priority 1 != 2 (required), skipped. # Trying to open LUKS2 keyslot 0. # Running keyslot key derivation. # Reading keyslot area [0x8000]. # Acquiring read lock for device /dev/nvme0n1p3. # Opening lock resource file /run/cryptsetup/L_259:3 # Verifying lock handle for /dev/nvme0n1p3. # Device /dev/nvme0n1p3 READ lock taken. # Reusing open ro fd on device /dev/nvme0n1p3 # Device /dev/nvme0n1p3 READ lock released. # Verifying key from keyslot 0, dige
[Kernel-packages] [Bug 1983108] Re: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371]
As I said, most of the times boot proceeds with no issues. (I have heard that boot sequence is randomized to make it less easier to attack by code injection, maybe it depends on the order of loading?) What does the nosplash parameter do? For now, at least, I can live with this bug, since it rarely occurs, but I know this makes finding the cause more difficult (if I change something, and next time it boots with no issue, I have no way to know if I solved the problem or if the issue will strike after perhaps a week) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371] Status in linux-hwe-5.15 package in Ubuntu: New Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983108/+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 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
The next step to resolve this issue is to capture a trace of the USB bus with a logic analyzer. Does anyone affected by this problem happen to have access to a logic analyzer? If so, post a trace here and someone can see if it is the device, the cable, or the computer misbehaving. -- 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Confirmed Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+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 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
I am setting this to confirmed and assigning owning teams per https://wiki.ubuntu.com/UbuntuDevelopment/Merging Please let me know if I assigned teams incorrectly or if I can do more work for this merge. ** Changed in: amd64-microcode (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Confirmed ** Changed in: amd64-microcode (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: linux-firmware (Ubuntu) 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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+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 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
Thanks for taking the time to report this bug an trying to make Ubuntu better. Is this the only relevant message you found in the syslog? Is this error causing some unexpected behavior apart from this message in the syslog? You mentioned the error in the log but did not mention what is the impact of that, is this not allowing you to reboot the VM? I am setting the libvirt task to Incomplete until you provide more information, when you do that please set it back to New and we will take a look again. ** Changed in: libvirt (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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1986520/+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 1986713] [NEW] azure: Replace hyperv_fb with hyperv_drm
Public bug reported: SRU Justification [Impact] Microsoft has asked to replace hyperv_fb with hyperv_drm in linux- modules-azure. [Test Plan] Extract linux-modules and ensure hyperv_drm.ko exists and hyperv_fb.ko does not. [Where things could go wrong] According to Microsoft, hyperv_drm is a direct replacement for hyperv_fb, yet there could be cases where hyperv_fb is being explicitly installed by customized images. [Other Info] SF: #00342707 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986713 Title: azure: Replace hyperv_fb with hyperv_drm Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked to replace hyperv_fb with hyperv_drm in linux- modules-azure. [Test Plan] Extract linux-modules and ensure hyperv_drm.ko exists and hyperv_fb.ko does not. [Where things could go wrong] According to Microsoft, hyperv_drm is a direct replacement for hyperv_fb, yet there could be cases where hyperv_fb is being explicitly installed by customized images. [Other Info] SF: #00342707 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986713/+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 1986713] Re: azure: Replace hyperv_fb with hyperv_drm
Patch submitted: https://lists.ubuntu.com/archives/kernel- team/2022-August/132630.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986713 Title: azure: Replace hyperv_fb with hyperv_drm Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked to replace hyperv_fb with hyperv_drm in linux- modules-azure. [Test Plan] Extract linux-modules and ensure hyperv_drm.ko exists and hyperv_fb.ko does not. [Where things could go wrong] According to Microsoft, hyperv_drm is a direct replacement for hyperv_fb, yet there could be cases where hyperv_fb is being explicitly installed by customized images. [Other Info] SF: #00342707 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986713/+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 1986715] [NEW] Jammy update: v5.15.50 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.50 upstream stable release from git://git.kernel.org/ net: mana: Add handling of CQE_RX_TRUNCATED zonefs: fix zonefs_iomap_begin() for reads usb: gadget: u_ether: fix regression in setting fixed MAC address bpf: Fix calling global functions from BPF_PROG_TYPE_EXT programs selftests/bpf: Add selftest for calling global functions from freplace serial: core: Initialize rs485 RTS polarity already on probe arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer Linux 5.15.50 UBUNTU: Upstream stable to v5.15.50 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.50 upstream stable release + from git://git.kernel.org/ -v5.15.50 upstream stable release -from git://git.kernel.org/ + net: mana: Add handling of CQE_RX_TRUNCATED + zonefs: fix zonefs_iomap_begin() for reads + usb: gadget: u_ether: fix regression in setting fixed MAC address + bpf: Fix calling global functions from BPF_PROG_TYPE_EXT programs + selftests/bpf: Add selftest for calling global functions from freplace + serial: core: Initialize rs485 RTS polarity already on probe + arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer + Linux 5.15.50 + UBUNTU: Upstream stable to v5.15.50 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986715 Title: Jammy update: v5.15.50 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.50 upstream stable release from git://git.kernel.org/ net: mana: Add handling of CQE_RX_TRUNCATED zonefs: fix zonefs_iomap_begin() for reads usb: gadget: u_ether: fix regression in setting fixed MAC address bpf: Fix calling global functions from BPF_PROG_TYPE_EXT programs selftests/bpf: Add selftest for calling global functions from freplace serial: core: Initialize rs485 RTS polarity already on probe arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer Linux 5.15.50 UBUNTU: Upstream stable to v5.15.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https:
[Kernel-packages] [Bug 1986717] [NEW] Update ice driver to support E823 devices
Public bug reported: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. Fix: I think these are the necessary patches to add the support that are missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices af23635a5335 ice: add backslash-n to strings 7124507291cb ice: increase PF reset wait timeout to 300 milliseconds 5fa23e0b23fb ice: Support XDP UMEM wake up mechanism 31c5f7f3f45a ice: SW DCB, report correct max TC value 27d9be98eda1 ice: Report correct DCB mode c8608b5071d0 ice: Add DCBNL ops required to configure ETS in CEE for SW DCB 36be2baa09f0 ice: Always clear the QRXFLXP_CNTXT register for VF Rx queues a6892c96fc49 ice: Fix for TCAM entry management 9d5c5a5290d4 ice: update malicious driver detection event handling Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Jeff Lane (bladernr) Status: Incomplete ** Tags: servcert-456 ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Tags added: servcert-456 -- 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/1986717 Title: Update ice driver to support E823 devices Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. Fix: I think these are the necessary patches to add the support that are missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices af23635a5335 ice: add backslash-n to strings 7124507291cb ice: increase PF reset wait timeout to 300 milliseconds 5fa23e0b23fb ice: Support XDP UMEM wake up mechanism 31c5f7f3f45a ice: SW DCB, report correct max TC value 27d9be98eda1 ice: Report correct DCB mode c8608b5071d0 ice: Add DCBNL ops required to configure ETS in CEE for SW DCB 36be2baa09f0 ice: Always clear the QRXFLXP_CNTXT register for VF Rx queues a6892c96fc49 ice: Fix for TCAM entry management 9d5c5a5290d4 ice: update malicious driver detection event handling Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+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 1986717] 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 1986717 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/1986717 Title: Update ice driver to support E823 devices Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. Fix: I think these are the necessary patches to add the support that are missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices af23635a5335 ice: add backslash-n to strings 7124507291cb ice: increase PF reset wait timeout to 300 milliseconds 5fa23e0b23fb ice: Support XDP UMEM wake up mechanism 31c5f7f3f45a ice: SW DCB, report correct max TC value 27d9be98eda1 ice: Report correct DCB mode c8608b5071d0 ice: Add DCBNL ops required to configure ETS in CEE for SW DCB 36be2baa09f0 ice: Always clear the QRXFLXP_CNTXT register for VF Rx queues a6892c96fc49 ice: Fix for TCAM entry management 9d5c5a5290d4 ice: update malicious driver detection event handling Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986718] [NEW] Jammy update: v5.15.51 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.51 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) 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/1986718 Title: Jammy update: v5.15.51 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.51 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986718] Re: Jammy update: v5.15.51 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.51 upstream stable release + from git://git.kernel.org/ -v5.15.51 upstream stable release -from git://git.kernel.org/ + random: schedule mix_interrupt_randomness() less often + random: quiet urandom warning ratelimit suppression message + ALSA: hda/via: Fix missing beep setup + ALSA: hda/conexant: Fix missing beep setup + ALSA: hda/realtek: Add mute LED quirk for HP Omen laptop + ALSA: hda/realtek: Apply fixup for Lenovo Yoga Duet 7 properly + ALSA: hda/realtek: Add quirk for Clevo PD70PNT + ALSA: hda/realtek: Add quirk for Clevo NS50PU + net: openvswitch: fix parsing of nw_proto for IPv6 fragments + 9p: Fix refcounting during full path walks for fid lookups + 9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl + 9p: fix fid refcount leak in v9fs_vfs_get_link + btrfs: fix hang during unmount when block group reclaim task is running + btrfs: prevent remounting to v1 space cache for subpage mount + btrfs: add error messages to all unrecognized mount options + scsi: ibmvfc: Store vhost pointer during subcrq allocation + scsi: ibmvfc: Allocate/free queue resource only during probe/remove + mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing + mmc: mediatek: wait dma stop bit reset to 0 + xen/gntdev: Avoid blocking in unmap_grant_pages() + MAINTAINERS: Add new IOMMU development mailing list + ata: libata: add qc->flags in ata_qc_complete_template tracepoint + dm era: commit metadata in postsuspend after worker stops + dm mirror log: clear log bits up to BITS_PER_LONG boundary + tracing/kprobes: Check whether get_kretprobe() returns NULL in kretprobe_dispatcher() + drm/i915: Implement w/a 22010492432 for adl-s + USB: serial: pl2303: add support for more HXN (G) types + USB: serial: option: add Telit LE910Cx 0x1250 composition + USB: serial: option: add Quectel EM05-G modem + USB: serial: option: add Quectel RM500K module support + drm/msm: Ensure mmap offset is initialized + drm/msm: Fix double pm_runtime_disable() call + netfilter: use get_random_u32 instead of prandom + scsi: scsi_debug: Fix zone transition to full condition + drm/msm: Switch ordering of runpm put vs devfreq_idle + scsi: iscsi: Exclude zero from the endpoint ID range + xsk: Fix generic transmit when completion queue reservation fails + drm/msm: use for_each_sgtable_sg to iterate over scatterlist + bpf: Fix request_sock leak in sk lookup helpers + drm/sun4i: Fix crash during suspend after component bind failure + bpf, x86: Fix tail call count offset calculation on bpf2bpf call + scsi: storvsc: Correct reporting of Hyper-V I/O size limits + phy: aquantia: Fix AN when higher speeds than 1G are not advertised + KVM: arm64: Prevent kmemleak from accessing pKVM memory + net: Write lock dev_base_lock without disabling bottom halves. + net: fix data-race in dev_isalive() + tipc: fix use-after-free Read in tipc_named_reinit + igb: fix a use-after-free issue in igb_clean_tx_ring + bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers + ethtool: Fix get module eeprom fallback + net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms + drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf + drm/msm/dp: check core_initialized before disable interrupts at dp_display_unbind() + drm/msm/dp: Drop now unused hpd_high member + drm/msm/dp: dp_link_parse_sink_count() return immediately if aux read failed + drm/msm/dp: do not initialize phy until plugin interrupt received + drm/msm/dp: force link training for display resolution change + perf arm-spe: Don't set data source if it's not a memory operation + erspan: do not assume transport header is always set + net/tls: fix tls_sk_proto_close executed repeatedly + udmabuf: add back sanity check + selftests: netfilter: correct PKTGEN_SCRIPT_PATHS in nft_concat_range.sh + xen-blkfront: Handle NULL gendisk + x86/xen: Remove undefined behavior in setup_features() + MIPS: Remove repetitive increase irq_err_count + afs: Fix dynamic root getattr + ice: ethtool: advertise 1000M speeds properly + regmap-
[Kernel-packages] [Bug 1986724] [NEW] Jammy update: v5.15.52 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.52 upstream stable release from git://git.kernel.org/ tick/nohz: unexport __init-annotated tick_nohz_full_setup() xfs: use kmem_cache_free() for kmem_cache objects xfs: punch out data fork delalloc blocks on COW writeback failure xfs: Fix the free logic of state in xfs_attr_node_hasname xfs: remove all COW fork extents when remounting readonly xfs: check sb_meta_uuid for dabuf buffer recovery xfs: prevent UAF in xfs_log_item_in_current_chkpt xfs: only bother with sync_filesystem during readonly remount powerpc/ftrace: Remove ftrace init tramp once kernel init is complete fs: add is_idmapped_mnt() helper fs: move mapping helpers fs: tweak fsuidgid_has_mapping() fs: account for filesystem mappings docs: update mapping documentation fs: use low-level mapping helpers fs: remove unused low-level mapping helpers fs: port higher-level mapping helpers fs: add i_user_ns() helper fs: support mapped mounts of mapped filesystems fs: fix acl translation fs: account for group membership rtw88: 8821c: support RFE type4 wifi NIC rtw88: rtw8821c: enable rfe 6 devices net: mscc: ocelot: allow unregistered IP multicast flooding to CPU io_uring: fix not locked access to fixed buf table Linux 5.15.52 UBUNTU: Upstream stable to v5.15.52 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.15.52 upstream stable release + from git://git.kernel.org/ -v5.15.52 upstream stable release -from git://git.kernel.org/ + tick/nohz: unexport __init-annotated tick_nohz_full_setup() + xfs: use kmem_cache_free() for kmem_cache objects + xfs: punch out data fork delalloc blocks on COW writeback failure + xfs: Fix the free logic of state in xfs_attr_node_hasname + xfs: remove all COW fork extents when remounting readonly + xfs: check sb_meta_uuid for dabuf buffer recovery + xfs: prevent UAF in xfs_log_item_in_current_chkpt + xfs: only bother with sync_filesystem during readonly remount + powerpc/ftrace: Remove ftrace init tramp once kernel init is complete + fs: add is_idmapped_mnt() helper + fs: move mapping helpers + fs: tweak fsuidgid_has_mapping() + fs: account for filesystem mappings + docs: update mapping documentation + fs: use low-level mapping helpers + fs: remove unused low-level mapping helpers + fs: port higher-level mapping helpers + fs: add i_user_ns() helper + fs: support mapped mounts of mapped filesystems + fs: fix acl translation + fs: account for group membership + rtw88: 8821c: support RFE type4 wifi NIC + rtw88: rtw8821c: enable rfe 6 devices + net: mscc: ocelot: allow unregistered IP multicast flooding to CPU + io_uring: fix not locked access to fixed buf table + Linux 5.15.52 + UBUNTU: Upstream stable to v5.15.52 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986724 Title: Ja
[Kernel-packages] [Bug 1986728] [NEW] Jammy update: v5.15.53 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.53 upstream stable release from git://git.kernel.org/ Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" drm/amdgpu: To flush tlb for MMHUB of RAVEN series ksmbd: set the range of bytes to zero without extending file size in FSCTL_ZERO_DATA ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA ksmbd: use vfs_llseek instead of dereferencing NULL ipv6: take care of disable_policy when restoring routes net: phy: Don't trigger state machine while in suspend nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX S40G) nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 nvdimm: Fix badblocks clear off-by-one error powerpc/prom_init: Fix kernel config grep powerpc/book3e: Fix PUD allocation size in map_kernel_page() powerpc/bpf: Fix use of user_pt_regs in uapi dm raid: fix accesses beyond end of raid member array dm raid: fix KASAN warning in raid5_add_disks s390/archrandom: simplify back to earlier design and initialize earlier SUNRPC: Fix READ_PLUS crasher net: rose: fix UAF bugs caused by timer handler net: usb: ax88179_178a: Fix packet receiving virtio-net: fix race between ndo_open() and virtio_device_ready() selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test net: dsa: bcm_sf2: force pause link settings net: tun: unlink NAPI from device on destruction net: tun: stop NAPI when detaching queues net: dp83822: disable false carrier interrupt net: dp83822: disable rx error interrupt RDMA/qedr: Fix reporting QP timeout attribute RDMA/cm: Fix memory leak in ib_cm_insert_listen linux/dim: Fix divide by 0 in RDMA DIM net: usb: asix: do not force pause frames support usbnet: fix memory allocation in helpers selftests: mptcp: more stable diag tests net: ipv6: unexport __init-annotated seg6_hmac_net_init() NFSD: restore EINVAL error translation in nfsd_commit() vfs: fix copy_file_range() regression in cross-fs copies caif_virtio: fix race between virtio_device_ready() and ndo_open() PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events vdpa/mlx5: Update Control VQ callback information s390: remove unneeded 'select BUILD_BIN2C' netfilter: nft_dynset: restore set element counter when failing to update net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup() net/sched: act_api: Notify user space if any actions were flushed before error net: asix: fix "can't send until first packet is send" issue net: bonding: fix possible NULL deref in rlb code net: phy: ax88772a: fix lost pause advertisement configuration net: bonding: fix use-after-free after 802.3ad slave unbind powerpc/memhotplug: Add add_pages override for PPC nfc: nfcmrvl: Fix irq_of_parse_and_map() return value NFC: nxp-nci: Don't issue a zero length i2c_master_read() tipc: move bc link creation back to tipc_node_create epic100: fix use after free on rmmod io_uring: ensure that send/sendmsg and recv/recvmsg check sqe->ioprio ACPI: video: Change how we determine if brightness key-presses are handled tunnels: do not assume mac header is set in skb_tunnel_check_pmtu() ipv6/sit: fix ipip6_tunnel_get_prl return value ipv6: fix lockdep splat in in6_dump_addrs() mlxsw: spectrum_router: Fix rollback in tunnel next hop init net: tun: avoid disabling NAPI twice MAINTAINERS: add Leah as xfs maintainer for 5.15.y tcp: add a missing nf_reset_ct() in 3WHS handling selftests/bpf: Add test_verifier support to fixup kfunc call insns selftests/rseq: remove ARRAY_SIZE define from individual tests selftests/rseq: introduce own copy of rseq uapi header selftests/rseq: Remove useless assignment to cpu variable selftests/rseq: Remove volatile from __rseq_abi selftests/rseq: Introduce rseq_get_abi() helper selftests/rseq: Introduce thread pointer getters selftests/rseq: Uplift rseq selftests for compatibility with glibc-2.35 selftests/rseq: Fix ppc32: wrong rseq_cs 32-bit field pointer on big endian selftests/rseq: Fix ppc32 missing instruction selection "u" and "x" for load/store selftests/rseq: Fix ppc32 offsets by using long rather than off_t selftests/rseq: Fix warnings about #if checks of undefined tokens selftests/rseq: Remove arm/mips asm goto compiler work-around selftests/rseq: Fix: work-around asm goto compiler bugs selftests/rseq: x86-64: use %fs segment selector for accessing rseq thread area selftests/rseq: x86-32: use %gs segment selector for accessing rseq thread area selftests/rseq: Change type of rseq_offset to ptrdiff_t xen/blkfront: fix leaking data in shared pages xen/netfront: fix leaking dat
[Kernel-packages] [Bug 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)
** Changed in: amd64-microcode (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1983409 Title: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free) Status in amd64-microcode package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2 to 3.20220411.1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: New Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1986520/+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 1986717] Re: Update ice driver to support E823 devices
** Description changed: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. + Fix: + After talking with engineers upstream this should be the only patch needed to add the support that is missing in 5.4 - Fix: - I think these are the necessary patches to add the support that are missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices - af23635a5335 ice: add backslash-n to strings - 7124507291cb ice: increase PF reset wait timeout to 300 milliseconds - 5fa23e0b23fb ice: Support XDP UMEM wake up mechanism - 31c5f7f3f45a ice: SW DCB, report correct max TC value - 27d9be98eda1 ice: Report correct DCB mode - c8608b5071d0 ice: Add DCBNL ops required to configure ETS in CEE for SW DCB - 36be2baa09f0 ice: Always clear the QRXFLXP_CNTXT register for VF Rx queues - a6892c96fc49 ice: Fix for TCAM entry management - 9d5c5a5290d4 ice: update malicious driver detection event handling - Testcase: + Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1986717 Title: Update ice driver to support E823 devices Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. Fix: After talking with engineers upstream this should be the only patch needed to add the support that is missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+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 1986520] 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 1986520 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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1986520/+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 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
I did locate the second patch and I have created a test kernel, please test https://people.canonical.com/~mreed/misc/lp_1965927_mpt3sas/ -- 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Incomplete Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+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 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+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 1983108] Re: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371]
"nosplash" should just prevent the boot-up graphics from being displayed, which are done by plymouthd. And if plymouthd is not running then it can't get stuck on a nouveau kernel bug at boot time. Though there's still a risk of hitting the same or other nouveau bugs later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371] Status in linux-hwe-5.15 package in Ubuntu: New Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983108/+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 1986743] [NEW] REQUEST add meson vdec firmware to arm64 linux-firmware package
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1986743 Title: REQUEST add meson vdec firmware to arm64 linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04.1 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 20220329.git681281e40ubuntu3.4 3) What you expected to happen Linux Firmware would include meson vdec blobs https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/meson/vdec 4) What happened instead Linux Firmware does not include meson vdec blobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1986743/+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 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1976556 Title: [Lenovo 300e 2nd GEN] ELAN Touchpad not working Status in linux package in Ubuntu: Expired Bug description: Used Ubunutu 22.04 with the current 5.15.x Kernel, cross tested with Linux Mint and 5.14.x Kernel. I have a Lenovo 300e 2nd Gen with an ELAN Touchscreen AND Touchpad with AMD processor. The Touchscreen is working flawlessly. The TouchPAD is dead. According to the Windows driver: %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group2_Inst, HID\VEN_ELAN&DEV_0660&Col01; ClickPad for Capela 14e Windows %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN&DEV_0661&Col01; ClickPad for Windows 100e/300e %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group3_Inst, HID\VEN_ELAN&DEV_066C&Col01; ClickPad for 100e/300e AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN&DEV_066E&Col01; ClickPad for 100W&300W Gen3 AMD Pollock %ELANHIDDeviceDesc% = ETD_HID_PTP_WIN10_Group1_Inst, HID\VEN_ELAN&DEV_066F&Col01; ClickPad for 300W Gen3 Intel JasperLake it is an ELAN066C According to similar solutions i tried to block several built in kernel modules, without success. https://askubuntu.com/questions/1248176/ideapad-5-15are05-elan-touchpad-not-working-on-20-04-nor-on-18-04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pingu 1140 F pulseaudio /dev/snd/controlC0: pingu 1140 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2022-05-30 (17 days ago) InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220111 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 30c9:001e 8SSC20X63465V1SR135107E EasyCamera 1M Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 82GK Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 1.187.31 Tags: una Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/07/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: FRCN21WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0K13476WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo 300e 2nd Gen dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrFRCN21WW:bd07/07/2021:br1.21:efr1.15:svnLENOVO:pn82GK:pvrLenovo300e2ndGen:rvnLENOVO:rnLNVNB161216:rvrSDK0K13476WIN:cvnLENOVO:ct31:cvrLenovo300e2ndGen:skuLENOVO_MT_82GK_BU_idea_FM_300e2ndGen: dmi.product.family: 300e 2nd Gen dmi.product.name: 82GK dmi.product.sku: LENOVO_MT_82GK_BU_idea_FM_300e 2nd Gen dmi.product.version: Lenovo 300e 2nd Gen dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976556/+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 1986751] [NEW] Fix non-working I219 ethernet after s2idle
Public bug reported: [Impact] I219 may stop working after s2idle. The link is up but failed to get an IP address from DHCP server. [Fix] Revert the workaround patch "e1000e: Fix possible HW unit hang after an s0ix exit" so the new fix "e1000e: Enable GPT clock before sending message to CSME" can work. [Test] With the patch applied, the I219 device always get ip address and all the functionalities are working. [Where problems could occur] It's really hard to say since the interaction between I219 and Intel ME is very arcane. The good thing is that the fix is limited to e1000e. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1982822 stella ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1982822 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1986751 Title: Fix non-working I219 ethernet after s2idle Status in HWE Next: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Confirmed Bug description: [Impact] I219 may stop working after s2idle. The link is up but failed to get an IP address from DHCP server. [Fix] Revert the workaround patch "e1000e: Fix possible HW unit hang after an s0ix exit" so the new fix "e1000e: Enable GPT clock before sending message to CSME" can work. [Test] With the patch applied, the I219 device always get ip address and all the functionalities are working. [Where problems could occur] It's really hard to say since the interaction between I219 and Intel ME is very arcane. The good thing is that the fix is limited to e1000e. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1986751/+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 1963615] Re: Add proper runtime PM support to Realtek PCIe cardreader
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem-5.17 (Ubuntu Focal) ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress -- 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/1963615 Title: Add proper runtime PM support to Realtek PCIe cardreader Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] New generations of Realtek PCIe card reader cannot detect card insertion when the device is in PCI D3. [Fix] Rework the runtime PM flow and add chip specific support. [Test] With the series applied, the device can detect card insertion when it's in PCI D3. [Where problems could occur] System wide power management with less usage like hibernation, kexec reboot, etc. are not tested extensively. So these cases may be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963615/+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 1984034] Re: Backport patches needed to allow live migration under SEV
https://lists.ubuntu.com/archives/kernel-team/2022-August/132504.html https://lists.ubuntu.com/archives/kernel-team/2022-August/132508.html Patches have been sent to mailing list and applied. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1984034 Title: Backport patches needed to allow live migration under SEV Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: New Status in linux-gcp source package in Jammy: New Bug description: https://canonical.my.salesforce.com/5004K09oeuI Upstream (v5.16) patches needed to allow live migration of confidential VMs. [Impact] No support for live-migration of confidential VMs currently [Fix] Backport 5 patches from v5.16 [Test] GCP confirmed that live-migration works with these patches. [Regression Potential] This was never working so there should be low risk of regression. Most of the changes are KVM-related so could have an impact on KVM. However most of the changes are new code so risk is low. More details in the SF case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1984034/+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
