[Kernel-packages] [Bug 1990698] Re: Bionic update: upstream stable patchset 2022-09-23
This bug is awaiting verification that the linux- azure-4.15/4.15.0-1157.172 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-azure-4.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990698 Title: Bionic update: upstream stable patchset 2022-09-23 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released 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: upstream stable patchset 2022-09-23 Ported from the following upstream stable releases: v4.14.291, v4.19.256 from git://git.kernel.org/ Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put ntfs: fix use-after-free in ntfs_ucsncmp() ARM: crypto: comment out gcc warning that breaks clang builds mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. ACPI: video: Force backlight native for some TongFang devices macintosh/adb: fix oob read in do_adb_query() function Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments ALSA: bcd2000: Fix a UAF bug on the error path of probing add barriers to buffer_uptodate and set_buffer_uptodate HID: wacom: Don't register pad_input for touch switch KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile usbnet: Fix linkwatch use-after-free on disconnect parisc: Fix device names in /proc/iomem drm/nouveau: fix another off-by-one in nvbios_addr drm/amdgpu: Check BO's requested pinning domains against its preferred_domains iio: light: isl29028: Fix the warning in isl29028_remove() fuse: limit nsec md-raid10: fix KASAN warning ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr() PCI: Add defines for normal and subtractive PCI bridges powerpc/fsl-pci: Fix Class Code of PCIe Root Port powerpc/powernv: Avoid crashing if rng is NULL MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK USB: HCD: Fix URB giveback issue in tasklet function netfilter: nf_tables: fix null deref due to zeroed list head arm64: Do not forget syscall when starting a new thread. arm64: fix oops in concurrently setting insn_emulation sysctls ext2: Add more validity checks for inode counts ARM: dts: imx6ul: add missing properties for sram ARM: dts: imx6ul: fix qspi node compatible ARM: OMAP2+: display: Fix refcount leak bug ACPI: PM: save NVS memory for Lenovo G40-45 ACPI: LPSS: Fix missing check in register_device_clock() PM: hibernate: defer device probing when resuming from hibernation selinux: Add boundary check in put_entry() ARM: findbit: fix overflowing offset ARM: bcm: Fix refcount leak in bcm_kona_smc_init x86/pmem: Fix platform-device leak in error path ARM: dts: ast2500-evb: fix board compatible soc: fsl: guts: machine variable might be unset cpufreq: zynq: Fix refcount leak in zynq_get_revision ARM: dts: qcom: pm8841: add required thermal-sensor-cells arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node regulator: of: Fix refcount leak bug in of_get_regulation_constraints() thermal/tools/tmon: Include pthread and time headers in tmon.h dm: return early from dm_pr_call() if DM device is suspended drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() drm/mediatek: Add pull-down MIPI operation in mtk_dsi_poweroff function i2c: Fix a potential use after free wifi: iwlegacy: 4965: fix potential off-by-one overflow in il4965_rs_fill_link_cmd() drm: bridge:
[Kernel-packages] [Bug 1990434] Re: Bionic update: upstream stable patchset 2022-09-21
This bug is awaiting verification that the linux/4.15.0-200.211 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux -- 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/1990434 Title: Bionic update: upstream stable patchset 2022-09-21 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released 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: upstream stable patchset 2022-09-21 Ported from the following upstream stable releases: v4.14.290, v4.19.254 v4.19.255 from git://git.kernel.org/ xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() ip: Fix a data-race around sysctl_fwmark_reflect. tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept. tcp: Fix a data-race around sysctl_tcp_probe_threshold. tcp: Fix a data-race around sysctl_tcp_probe_interval. i2c: cadence: Change large transfer count reset logic to be unconditional net: stmmac: fix dma queue left shift overflow issue igmp: Fix data-races around sysctl_igmp_llm_reports. igmp: Fix a data-race around sysctl_igmp_max_memberships. tcp: Fix a data-race around sysctl_tcp_notsent_lowat. be2net: Fix buffer overflow in be_get_module_eeprom Revert "Revert "char/random: silence a lockdep splat with printk()"" mm/mempolicy: fix uninit-value in mpol_rebind_policy() bpf: Make sure mac_header was set before using it drm/tilcdc: Remove obsolete crtc_mode_valid() hack tilcdc: tilcdc_external: fix an incorrect NULL check on list iterator ALSA: memalloc: Align buffer allocations in page size Bluetooth: Add bt_skb_sendmsg helper Bluetooth: Add bt_skb_sendmmsg helper Bluetooth: SCO: Replace use of memcpy_from_msg with bt_skb_sendmsg Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg Bluetooth: Fix passing NULL to PTR_ERR Bluetooth: SCO: Fix sco_send_frame returning skb->len Bluetooth: Fix bt_skb_sendmmsg not allocating partial chunks tty: drivers/tty/, stop using tty_schedule_flip() tty: the rest, stop using tty_schedule_flip() tty: drop tty_schedule_flip() tty: extract tty_flip_buffer_commit() from tty_flip_buffer_push() tty: use new tty_insert_flip_string_and_push_buffer() in pty_write() PCI: hv: Fix multi-MSI to allow more than one MSI vector PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() PCI: hv: Fix interrupt mapping for multi-MSI ip: Fix data-races around sysctl_ip_fwd_use_pmtu. ip: Fix data-races around sysctl_ip_nonlocal_bind. tcp: Fix data-races around sysctl_tcp_mtu_probing. tcp: Fix data-races around sysctl_tcp_reordering. tcp: Fix data-races around some timeout sysctl knobs. tcp: Fix a data-race around sysctl_tcp_tw_reuse. tcp: Fix data-races around sysctl_tcp_fastopen. tcp: Fix a data-race around sysctl_tcp_early_retrans. tcp: Fix data-races around sysctl_tcp_recovery. tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts. tcp: Fix data-races around sysctl_tcp_slow_start_after_idle. tcp: Fix a data-race around sysctl_tcp_retrans_collapse. tcp: Fix a data-race around sysctl_tcp_stdurg. tcp: Fix a data-race around sysctl_tcp_rfc1337. tcp: Fix data-races around sysctl_tcp_max_reordering. ima: remove the IMA_TEMPLATE Kconfig option UBUNTU: [Config] updateconfigs for IMA_TEMPLATE UBUNTU: Upstream stable to v4.14.290, v4.19.254 s390/archrandom: prevent CPACF trng invocations in interrupt context tcp: Fix data-races around sysctl_tcp_dsack. tcp: Fix a data-race around sysctl_tcp_app_win. tcp: Fix a data-race around
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => In Progress -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Also affects: dkms Importance: Undecided Status: New ** No longer affects: dkms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1998141] [NEW] touchpad worked sometimes for a few second but most o fthe time didn't worked neither was recognised from the sistem
Public bug reported: I've installed Ubuntu on dual boot whit windows ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 1336 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 21:23:25 2022 InstallationDate: Installed on 2022-11-18 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: SiComputer S.p.A. Nauta 01E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=5e0686ef-7fa5-4a80-aee1-10ffa8b184ba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2020 dmi.bios.release: 2.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.01.01 dmi.board.asset.tag: Default string dmi.board.name: Nauta 01E dmi.board.vendor: SiComputer dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.01.01:bd06/22/2020:br2.1:efr1.0:svnSiComputerS.p.A.:pnNauta01E:pvrDefaultstring:rvnSiComputer:rnNauta01E:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuSID0032675K: dmi.product.family: Nauta dmi.product.name: Nauta 01E dmi.product.sku: SID0032675K dmi.product.version: Default string dmi.sys.vendor: SiComputer S.p.A. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- 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/1998141 Title: touchpad worked sometimes for a few second but most o fthe time didn't worked neither was recognised from the sistem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu on dual boot whit windows ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 1336 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 21:23:25 2022 InstallationDate: Installed on 2022-11-18 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: SiComputer S.p.A. Nauta 01E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=5e0686ef-7fa5-4a80-aee1-10ffa8b184ba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2020 dmi.bios.release: 2.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.01.01 dmi.board.asset.tag: Default string dmi.board.name: Nauta 01E dmi.board.vendor: SiComputer dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.01.01:bd06/22/2020:br2.1:efr1.0:svnSiComputerS.p.A.:pnNauta01E:pvrDefaultstring:rvnSiComputer:rnNauta01E:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuSID0032675K: dmi.product.family: Nauta dmi.product.name: Nauta 01E dmi.product.sku: SID0032675K dmi.product.version: Default string dmi.sys.vendor: SiComputer S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998141/+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 1995766] Re: X server segfault when starting youtube videos
Oops, didn't realize I was behind on the driver, sorry. I'm on 515 now. I'll report back soon(ish) with results. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=8M mtrr_chunk_size=32M quiet splash nomodeset vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-14 (174
[Kernel-packages] [Bug 1998141] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998141 Title: touchpad worked sometimes for a few second but most o fthe time didn't worked neither was recognised from the sistem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu on dual boot whit windows ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diego 1336 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 21:23:25 2022 InstallationDate: Installed on 2022-11-18 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: SiComputer S.p.A. Nauta 01E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=5e0686ef-7fa5-4a80-aee1-10ffa8b184ba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2020 dmi.bios.release: 2.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.01.01 dmi.board.asset.tag: Default string dmi.board.name: Nauta 01E dmi.board.vendor: SiComputer dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.01.01:bd06/22/2020:br2.1:efr1.0:svnSiComputerS.p.A.:pnNauta01E:pvrDefaultstring:rvnSiComputer:rnNauta01E:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuSID0032675K: dmi.product.family: Nauta dmi.product.name: Nauta 01E dmi.product.sku: SID0032675K dmi.product.version: Default string dmi.sys.vendor: SiComputer S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998141/+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 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach
> Is there a way to run/debug the cable bandwidth test? I don't know but excellent question. AFAIK it's just invisible logic in the kernel which will hide modes that require too much bandwidth. -- 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/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 4 23:29:27 2022 DistUpgraded: Fresh
[Kernel-packages] [Bug 1995021] Re: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash
** Tags added: regression-update ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995021 Title: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995021/+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 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
** Changed in: linux (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1733194 Title: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Fix Released Bug description: When in AP mode after some time, get this BUG: Nov 18 23:21:31 bifrost kernel: [18345.860393] BUG: unable to handle kernel NULL pointer dereference at 0070 Nov 18 23:21:31 bifrost kernel: [18345.860552] IP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.860644] PGD 0 Nov 18 23:21:31 bifrost kernel: [18345.860646] P4D 0 Nov 18 23:21:31 bifrost kernel: [18345.860682] Nov 18 23:21:31 bifrost kernel: [18345.860747] Oops: 0002 [#1] SMP Nov 18 23:21:31 bifrost kernel: [18345.860800] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter nls_iso8859_1 cmdlinepart intel_spi_platform intel_spi spi_nor mtd arc4 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp kvm_intel bridge kvm stp llc iwlmvm irqbypass punit_atom_debug mac80211 intel_cstate snd_hda_codec_hdmi iwlwifi snd_hda_codec_realtek snd_hda_codec_generic cfg80211 btusb snd_hda_intel lpc_ich btrtl snd_hda_codec snd_intel_sst_acpi Nov 18 23:21:31 bifrost kernel: [18345.861897] mei_txe snd_hda_core mei snd_hwdep shpchp snd_intel_sst_core snd_soc_sst_atom_hifi2_platform hci_uart snd_soc_sst_match snd_soc_core btbcm serdev snd_compress btqca ac97_bus btintel snd_pcm_dmaengine snd_pcm dw_dmac dw_dmac_core snd_timer bluetooth snd soundcore mac_hid intel_int0002_vgpio ecdh_generic spi_pxa2xx_platform rfkill_gpio pwm_lpss_platform pwm_lpss 8250_dw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 drm_kms_helper crct10dif_pclmul igb syscopyarea sysfillrect crc32_pclmul sysimgblt fb_sys_fops dca ghash_clmulni_intel i2c_algo_bit cryptd ahci ptp drm pps_core libahci video Nov 18 23:21:31 bifrost kernel: [18345.862995] i2c_hid hid sdhci_acpi sdhci Nov 18 23:21:31 bifrost kernel: [18345.863068] CPU: 1 PID: 1202 Comm: kworker/1:2 Tainted: GW 4.13.0-16-generic #19-Ubuntu Nov 18 23:21:31 bifrost kernel: [18345.863203] Hardware name: NF541 NF541/NF541, BIOS BAR1NA02 02/25/2016 Nov 18 23:21:31 bifrost kernel: [18345.863326] Workqueue: events iwl_mvm_add_new_dqa_stream_wk [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.863428] task: 96862c1c5800 task.stack: a98a817c Nov 18 23:21:31 bifrost kernel: [18345.863539] RIP: 0010:iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.863635] RSP: 0018:a98a817c3be0 EFLAGS: 00010246 Nov 18 23:21:31 bifrost kernel: [18345.863718] RAX: 09c4 RBX: 001f RCX: Nov 18 23:21:31 bifrost kernel: [18345.863824] RDX: RSI: 001f RDI: 2710 Nov 18 23:21:31 bifrost kernel: [18345.863932] RBP: a98a817c3c30 R08: 2710 R09: 0001 Nov 18 23:21:31 bifrost kernel: [18345.864039] R10: R11: 9686344ce010 R12: Nov 18 23:21:31 bifrost kernel: [18345.864145] R13: 96862c9d0018 R14: R15: Nov 18 23:21:31 bifrost kernel: [18345.864253] FS: () GS:96863fc8() knlGS: Nov 18 23:21:31 bifrost kernel: [18345.864373] CS: 0010 DS: ES: CR0: 80050033 Nov 18 23:21:31 bifrost kernel: [18345.864461] CR2: 0070 CR3: 00023068b000 CR4: 001006e0 Nov 18 23:21:31 bifrost kernel: [18345.864568] Call Trace: Nov 18 23:21:31 bifrost kernel: [18345.864633] iwl_mvm_enable_txq+0x212/0x3a0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864732] iwl_mvm_add_new_dqa_stream_wk+0x7e8/0x15e0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864843] ? iwl_mvm_add_new_dqa_stream_wk+0x7e8/0x15e0 [iwlmvm] Nov 18 23:21:31 bifrost kernel: [18345.864945] ? __switch_to+0x211/0x520 Nov 18 23:21:31 bifrost kernel: [18345.865008] ? put_prev_entity+0x23/0xf0 Nov 18 23:21:31 bifrost kernel: [18345.865075] process_one_work+0x1e7/0x410 Nov 18 23:21:31 bifrost kernel: [18345.865143] worker_thread+0x4a/0x410
[Kernel-packages] [Bug 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Changed in: dkms (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1997944] Re: Soundwire support for the Intel RPL Gen platforms
** Tags added: originate-from-1997690 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997944 Title: Soundwire support for the Intel RPL Gen platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: New Status in firmware-sof source package in Lunar: New Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997944/+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 1990698] Re: Bionic update: upstream stable patchset 2022-09-23
This bug is awaiting verification that the linux-aws/4.15.0-1146.158 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990698 Title: Bionic update: upstream stable patchset 2022-09-23 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released 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: upstream stable patchset 2022-09-23 Ported from the following upstream stable releases: v4.14.291, v4.19.256 from git://git.kernel.org/ Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put ntfs: fix use-after-free in ntfs_ucsncmp() ARM: crypto: comment out gcc warning that breaks clang builds mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. ACPI: video: Force backlight native for some TongFang devices macintosh/adb: fix oob read in do_adb_query() function Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments ALSA: bcd2000: Fix a UAF bug on the error path of probing add barriers to buffer_uptodate and set_buffer_uptodate HID: wacom: Don't register pad_input for touch switch KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile usbnet: Fix linkwatch use-after-free on disconnect parisc: Fix device names in /proc/iomem drm/nouveau: fix another off-by-one in nvbios_addr drm/amdgpu: Check BO's requested pinning domains against its preferred_domains iio: light: isl29028: Fix the warning in isl29028_remove() fuse: limit nsec md-raid10: fix KASAN warning ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr() PCI: Add defines for normal and subtractive PCI bridges powerpc/fsl-pci: Fix Class Code of PCIe Root Port powerpc/powernv: Avoid crashing if rng is NULL MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK USB: HCD: Fix URB giveback issue in tasklet function netfilter: nf_tables: fix null deref due to zeroed list head arm64: Do not forget syscall when starting a new thread. arm64: fix oops in concurrently setting insn_emulation sysctls ext2: Add more validity checks for inode counts ARM: dts: imx6ul: add missing properties for sram ARM: dts: imx6ul: fix qspi node compatible ARM: OMAP2+: display: Fix refcount leak bug ACPI: PM: save NVS memory for Lenovo G40-45 ACPI: LPSS: Fix missing check in register_device_clock() PM: hibernate: defer device probing when resuming from hibernation selinux: Add boundary check in put_entry() ARM: findbit: fix overflowing offset ARM: bcm: Fix refcount leak in bcm_kona_smc_init x86/pmem: Fix platform-device leak in error path ARM: dts: ast2500-evb: fix board compatible soc: fsl: guts: machine variable might be unset cpufreq: zynq: Fix refcount leak in zynq_get_revision ARM: dts: qcom: pm8841: add required thermal-sensor-cells arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node regulator: of: Fix refcount leak bug in of_get_regulation_constraints() thermal/tools/tmon: Include pthread and time headers in tmon.h dm: return early from dm_pr_call() if DM device is suspended drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() drm/mediatek: Add pull-down MIPI operation in mtk_dsi_poweroff function i2c: Fix a potential use after free wifi: iwlegacy: 4965: fix potential off-by-one overflow in il4965_rs_fill_link_cmd() drm: bridge: adv7511: Add
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I put together some notes and work-arounds in order to provide a simpler reference for people hitting this issue. I didn't test everything below but nothing should be risky. # Summary Grub attempts to read the initrd into a memory location that is too small. This issue is caused by a combination of several factors: - Grub not setting aside enough space for the initrd in memory and not at the right location, - Initrds having grown due to holding more modules and more firmware. This is especially the case with the nvidia proprietary driver. - Typical screen resolutions and their associated buffers in memory having increased. A related issue is not having enough space in /boot to hold enough initrds. # Solutions There are four ways to tackle these issues: - Patch grub, - Have fewer modules, - Compress initrds more, - Lower screen resolution at boot. ## Patch grub This is being worked on. It’s the trickier option so I’m not going to provide details but you can find that in the discussion above. ## Have fewer modules The default configuration creates initrds that are meant to be universal in order to accommodate as many hardware variants as possible. Unsurprisingly this makes initrds much bigger. It is possible to change the value of MODULES to ‘dep’ in /etc/initramfs-tools/initramfs.conf . This will drastically reduce the initrd size in virtually every configuration at the cost of not supporting during boot hardware that is not plugged when the initrd generation takes place. ## Compress initrds more Change the value of COMPRESS in /etc/initramfs-tools/initramfs.conf . In terms of compression level, you will have something along the lines of the following: lz4: 74066711 zstd: 54260379 gzip: 53829310 xz: 29665544 NB: these values are only valid on one specific machine and configuration; they are only meant to give an idea of compression ratio that can be obtained but the initrd uses MODULES=dep as outlined above. With a small hack, it is also possible to make xz compression much faster at a small cost in compression by adding the following at the end of initramfs.conf: export XZ_OPT='--lzma2=preset=0,dict=8M' In the future, it will be possible to directly set compression levels for every compression method. ## Lower screen resolution at boot You can use a lower resolution screen when booting. You can also edit /etc/default/grub and use the following: GRUB_GFXMODE=640x480 Remember to run update-grub afterwards. If you need to do it at boot-time, you will use GFXMODE instead (no ‘GRUB_’ prefix). -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which
[Kernel-packages] [Bug 1998154] [NEW] dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
Public bug reported: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1996053] Re: No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works)
OK if kernel 5.19 works now then we can close the bug. Feel free to open new bugs for any problems you find. ** 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/1996053 Title: No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works) Status in linux package in Ubuntu: Invalid Bug description: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996053/+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 1995021] 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 1995021 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/1995021 Title: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995021/+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 1997686] Re: Enable Intel FM350 wwan CCCI driver port logging
** Tags added: oem-priority originate-from-1997535 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997686 Title: Enable Intel FM350 wwan CCCI driver port logging Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997686/+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 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach
Hi Daniel, I just tested with the new kernel: $ uname -a Linux omer 6.1.0-060100rc5drmtip20221118-generic #202211180211 SMP PREEMPT_DYNAMIC Fri Nov 18 03:02:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux But still the same issue. The cable should be OK, as it didn't change since the time it was working perfect for more than a year. Is there a way to run/debug the cable bandwidth test? -- 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/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error:
[Kernel-packages] [Bug 1982582] Re: [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest)
This bug was fixed in the package kdump-tools - 1:1.8ubuntu2 --- kdump-tools (1:1.8ubuntu2) lunar; urgency=medium * Modifed ucf call in d/kdump-tools.postinst to use option '--debconf-ok' to fix a package install issue (LP: #1982582). -- Frank Heimes Wed, 23 Nov 2022 19:40:57 +0100 ** Changed in: kdump-tools (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1982582 Title: [UBUNTU 22.04] Unable to install kdump-tools on 22.04 on s390x (LPAR nor z/VM guest) Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Fix Released Status in kdump-tools source package in Jammy: New Status in kdump-tools source package in Kinetic: New Status in kdump-tools source package in Lunar: Fix Released Bug description: Unable to install kdump-tools on 22.04 (Jammy) on s390x (LPAR nor z/VM guest) Errors were encountered while processing: kdump-tools needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Contact Information = Vanessa Baeza/vanessa.ba...@ibm.com ---uname output--- Linux ilzlnx15 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:22:27 UTC 2022 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- apt-get install kdump-tools or apt-get install linux-crashdump == Comment: #1 - Ruth Vanessa Baeza Elizalde - 2022-07-21 14:09:21 == == Comment: #6 - Steffen Maier - 2022-07-22 06:15:06 == (In reply to comment #1) > Created attachment 155027 [details] > sosreport-ilzlnx15-199072-2022-07-21-cpplakh [maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ cat sos_commands/kdump/kdump-config_show * /etc/default/kdump-tools: USE_KDUMP is not set or zero * no crashkernel= parameter in the kernel cmdline [maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ cat ./proc/cmdline root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH [maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ cat etc/zipl.conf # This has been modified by the MAAS curtin installer [defaultboot] default=ubuntu [ubuntu] target = /boot image = /boot/vmlinuz ramdisk = /boot/initrd.img parameters = root=/dev/disk/by-id/dm-uuid-LVM-pgDF7ojWA1Vra6LMB3aPVQt9xStlmQK2he2ApvXaEuUKbGUMrJf8Kv7yIs9yAZzH Looks like some preconditions for kdump are not fulfilled. [https://ubuntu.com/server/docs/kernel-crash-dump] Are those supposed to be created by the installation of kdump-tools or does that package require those pre-reqs to already be fulfilled to get installed? (I'm not familiar with kdump tooling on Ubuntu.) Vanessa, is this different from previous Ubuntu versions you deployed? (cf. bug 194306) FYI, there's also this known kdump bug 195646. While kdump is really nice, you could continue with just a working standalone dump for the time being in order not to jeopardize your schedules. (In reply to comment #0) > ---Problem Description--- > Unable to install kdump-tools on 22.04 (Jammy Jellyfish) on s390x (LPAR nor > zVM guest) > Errors were encountered while processing: > kdump-tools > needrestart is being skipped since dpkg has failed > E: Sub-process /usr/bin/dpkg returned an error code (1) Are there any more details on the error it faced? Copy from the terminal? (issued command and its output) [maier:~/docs/zfcp/issues/ilab/ltc199072-u2204-error-on-installing_kdump-tools/sosreport-ilzlnx15-199072-2022-07-21-cpplakh](0)$ fgrep kdump var/log/dpkg.log 465:2022-07-21 10:48:56 install kdump-tools:s390x 1:1.6.10ubuntu1 467:2022-07-21 10:48:56 status half-installed kdump-tools:s390x 1:1.6.10ubuntu1 468:2022-07-21 10:48:56 status unpacked kdump-tools:s390x 1:1.6.10ubuntu1 489:2022-07-21 10:49:05 configure kdump-tools:s390x 1:1.6.10ubuntu1 490:2022-07-21 10:49:05 status unpacked kdump-tools:s390x 1:1.6.10ubuntu1 491:2022-07-21 10:49:05 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1 502:2022-07-21 10:54:06 configure kdump-tools:s390x 1:1.6.10ubuntu1 504:2022-07-21 10:54:06 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1 509:2022-07-21 11:04:42 status half-configured kdump-tools:s390x 1:1.6.10ubuntu1 510:2022-07-21 11:04:43 remove kdump-tools:s390x 1:1.6.10ubuntu1 512:2022-07-21 11:04:43 status half-installed kdump-tools:s390x 1:1.6.10ubuntu1 514:2022-07-21 11:04:46 status config-files kdump-tools:s390x
[Kernel-packages] [Bug 1993349] Re: Bionic update: upstream stable patchset 2022-10-18
This bug is awaiting verification that the linux/4.15.0-200.211 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux -- 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/1993349 Title: Bionic update: upstream stable patchset 2022-10-18 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-10-18 from git://git.kernel.org/ bpf: Verifer, adjust_scalar_min_max_vals to always call update_reg_bounds() selftests/bpf: Fix test_align verifier log patterns drm/msm/dsi: Fix number of regulators for msm8996_dsi_cfg platform/x86: pmc_atom: Fix SLP_TYPx bitfield mask wifi: cfg80211: debugfs: fix return type in ht40allow_map_read() ethernet: rocker: fix sleep in atomic context bug in neigh_timer_handler kcm: fix strp_init() order and cleanup serial: fsl_lpuart: RS485 RTS polariy is inverse staging: rtl8712: fix use after free bugs vt: Clear selection before changing the font USB: serial: ftdi_sio: add Omron CS1W-CIF31 device id binder: fix UAF of ref->proc caused by race condition drm/i915/reg: Fix spelling mistake "Unsupport" -> "Unsupported" Input: rk805-pwrkey - fix module autoloading hwmon: (gpio-fan) Fix array out of bounds access thunderbolt: Use the actual buffer in tb_async_error() xhci: Add grace period after xHC start to prevent premature runtime suspend. USB: serial: cp210x: add Decagon UCA device id USB: serial: option: add support for OPPO R11 diag port USB: serial: option: add Quectel EM060K modem USB: serial: option: add support for Cinterion MV32-WA/WB RmNet mode usb: dwc2: fix wrong order of phy_power_on and phy_init USB: cdc-acm: Add Icom PMR F3400 support (0c26:0020) usb-storage: Add ignore-residue quirk for NXP PN7462AU s390/hugetlb: fix prepare_hugepage_range() check for 2 GB hugepages s390: fix nospec table alignments USB: core: Prevent nested device-reset calls usb: gadget: mass_storage: Fix cdrom data transfers on MAC-OS wifi: mac80211: Don't finalize CSA in IBSS mode if state is disconnected net: mac802154: Fix a condition in the receive path ALSA: seq: oss: Fix data-race for max_midi_devs access ALSA: seq: Fix data-race at module auto-loading efi: capsule-loader: Fix use-after-free in efi_capsule_write wifi: iwlegacy: 4965: corrected fix for potential off-by-one overflow in il4965_rs_fill_link_cmd() fs: only do a memory barrier for the first set_buffer_uptodate() Revert "mm: kmemleak: take a full lowmem check in kmemleak_*_phys()" drm/amdgpu: Check num_gfx_rings for gfx v9_0 rb setup. drm/radeon: add a force flush to delay work when radeon parisc: ccio-dma: Handle kmalloc failure in ccio_init_resources() parisc: Add runtime check to prevent PA2.0 kernels on PA1.x machines fbdev: chipsfb: Add missing pci_disable_device() in chipsfb_pci_init() ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() ALSA: aloop: Fix random zeros in capture data when using jiffies timer ALSA: usb-audio: Fix an out-of-bounds bug in __snd_usb_parse_audio_interface() kprobes: Prohibit probes in gate area scsi: mpt3sas: Fix use-after-free warning driver core: Don't probe devices after bus_type.match() probe deferral netfilter: br_netfilter: Drop dst references before setting. netfilter: nf_conntrack_irc: Fix forged IP logic sch_sfb: Don't assume the skb is still around after enqueueing to child tipc: fix shift wrapping bug in map_get() ipv6: sr: fix out-of-bounds read when setting HMAC data. tcp: fix early ETIMEDOUT after spurious non-SACK RTO sch_sfb: Also store skb len before calling child enqueue usb: dwc3: fix PHY disable sequence USB: serial: ch341: fix lost character on LCR updates USB: serial: ch341: fix disabled rx timer on older devices MIPS: loongson32: ls1c: Fix
[Kernel-packages] [Bug 1992112] Re: Bionic update: upstream stable patchset 2022-10-06
This bug is awaiting verification that the linux/4.15.0-200.211 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux -- 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/1992112 Title: Bionic update: upstream stable patchset 2022-10-06 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-10-06 from git://git.kernel.org/ audit: fix potential double free on error path from fsnotify_add_inode_mark parisc: Fix exception handler for fldw and fstw instructions pinctrl: amd: Don't save/restore interrupt status and wake status bits xfrm: fix refcount leak in __xfrm_policy_check() rose: check NULL rose_loopback_neigh->loopback bonding: 802.3ad: fix no transmission of LACPDUs net: ipvtap - add __init/__exit annotations to module init/exit funcs netfilter: ebtables: reject blobs that don't provide all entry points netfilter: nft_payload: report ERANGE for too long offset and length netfilter: nft_payload: do not truncate csum_offset and csum_type net: Fix data-races around weight_p and dev_weight_[rt]x_bias. ratelimit: Fix data-races in ___ratelimit(). net: Fix a data-race around sysctl_tstamp_allow_data. net: Fix a data-race around sysctl_net_busy_poll. net: Fix a data-race around sysctl_net_busy_read. net: Fix a data-race around netdev_budget. net: Fix a data-race around netdev_budget_usecs. net: Fix a data-race around sysctl_somaxconn. ixgbe: stop resetting SYSTIME in ixgbe_ptp_start_cyclecounter btrfs: check if root is readonly while setting security xattr loop: Check for overflow while configuring loop asm-generic: sections: refactor memory_intersects mm/hugetlb: fix hugetlb not supporting softdirty tracking md: call __md_stop_writes in md_stop mm: Force TLB flush for PFNMAP mappings before unlink_file_vma() arm64: map FDT as RW for early_init_dt_scan() s390/mm: do not trigger write fault when vma does not allow VM_WRITE x86/bugs: Add "unknown" reporting for MMIO Stale Data kbuild: Fix include path in scripts/Makefile.modpost Bluetooth: L2CAP: Fix build errors in some archs media: pvrusb2: fix memory leak in pvr_probe HID: hidraw: fix memory leak in hidraw_release() fbdev: fb_pm2fb: Avoid potential divide by zero error ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse neigh: fix possible DoS due to net iface start/stop loop s390/hypfs: avoid error message under KVM netfilter: conntrack: NF_CONNTRACK_PROCFS should no longer default to y kprobes: don't call disarm_kprobe() for disabled kprobes net: neigh: don't call kfree_skb() under spin_lock_irqsave() net: Fix data-races around netdev_tstamp_prequeue. x86/unwind/orc: Unwind ftrace trampolines with correct ORC entry s390: fix double free of GS and RI CBs on fork() failure scsi: storvsc: Remove WQ_MEM_RECLAIM from storvsc_error_wq bpf: Fix the off-by-two error in range markings UBUNTU: Upstream stable to v4.14.292, v4.19.257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992112/+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 1997686] Re: Enable Intel FM350 wwan CCCI driver port logging
** Description changed: - TBD. + To enable CCCI driver Modem Logging (MDL) Port for debugging purposes: + https://patchwork.kernel.org/project/netdevbpf/patch/20221028153534.1789295-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997686 Title: Enable Intel FM350 wwan CCCI driver port logging Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: To enable CCCI driver Modem Logging (MDL) Port for debugging purposes: https://patchwork.kernel.org/project/netdevbpf/patch/20221028153534.1789295-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997686/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** Changed in: linux-firmware (Ubuntu) Status: In Progress => 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
Hi Matthias, gcc-12 looks in a wrong archive, could you help fix it? Or do you know who could fix it? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1990394] Re: Wifi and Bluetooth with rtl8852be not working
** Changed in: linux (Ubuntu) Status: Expired => 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/1990394 Title: Wifi and Bluetooth with rtl8852be not working Status in linux package in Ubuntu: Incomplete Bug description: Realtek rtl8852be Wifi and Bluetooth not working on Kubuntu 22.04 and Ubuntu 22.10 (daily, 20.9.2022). Works on 22.04 just by compiling it yourself as Kernel-Module. 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 Subsystem: Lenovo Device 4853 Flags: bus master, fast devsel, latency 0, IRQ 81, IOMMU group 14 I/O ports at 2000 [size=256] Memory at d050 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: rtl8852be Kernel modules: 8852be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990394/+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 1997763] Re: WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8
** Changed in: linux-raspi2 (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1997763 Title: WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux- raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Fix Committed Bug description: [Impact] Current 4.15 raspi2 kernel emits the following warnings when the spidev driver is loaded: kernel: [2.957689] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 kernel: [4.527294] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 kernel: [2.957668] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 kernel: [4.525991] WARNING: CPU: 3 PID: 34 at /build/linux-raspi2-xwwT5i/linux-raspi2-4.15.0/drivers/spi/spidev.c:738 spidev_probe+0x13c/0x1f8 [Test Case] Boot 4.15 raspi2 kernel on a Pi 2/3 and load the spidev modules [Fix] This warning is triggered by an upstream change that wants a compatible (HW) string which is a questionable requirement for a generic driver. Caused a lot of upstream discussion with the end result that the raspi people disabled the warning in their kernel. We do the same on our newer kernels so lets backport that fix to 4.15. [Regression Potential] Changes are confined to the spidev module and only silence a warning. No negative side-effects are expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1997763/+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 1996900] Re: display flashes
Thanks for the bug report. Next time the flashes occur, please run: journalctl -b0 > flashes.txt and attach the resulting text file here. ** Tags added: amdgpu ** Summary changed: - display flashes + [amdgpu] [KDE] Display flashes ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [amdgpu] [KDE] Display flashes + [amdgpu] [KDE] Display flashes black ** 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/1996900 Title: [amdgpu] [KDE] Display flashes black Status in linux package in Ubuntu: Incomplete Bug description: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 6.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/08/2022:br6.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996900/+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 1990394] Re: Wifi and Bluetooth with rtl8852be 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/1990394 Title: Wifi and Bluetooth with rtl8852be not working Status in linux package in Ubuntu: Expired Bug description: Realtek rtl8852be Wifi and Bluetooth not working on Kubuntu 22.04 and Ubuntu 22.10 (daily, 20.9.2022). Works on 22.04 just by compiling it yourself as Kernel-Module. 04:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 Subsystem: Lenovo Device 4853 Flags: bus master, fast devsel, latency 0, IRQ 81, IOMMU group 14 I/O ports at 2000 [size=256] Memory at d050 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: rtl8852be Kernel modules: 8852be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990394/+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 1860284]
Tested on Clevo X170KM seems to work. Attached dmesg with dock attached during boot and dock attached after boot. -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
Created attachment 303308 dmsg of experimental patch, dock attached before boot -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1996496] Re: Cannot connect to Ubuntu BLE servers
Thanks for the bug report. Unfortunately we can't support personal
builds of BlueZ here. If you experience any issues with BlueZ that you
built yourself then please report them upstream at
https://github.com/bluez/bluez/issues
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1996496
Title:
Cannot connect to Ubuntu BLE servers
Status in bluez package in Ubuntu:
Invalid
Bug description:
I'm on Ubuntu 22.04.1 LTS, using bluez 5.65 (built from sources by this
guide: https://docs.embeddedts.com/BLE_Examples), and doing the following steps:
1. Run `python3 /usr/local/lib/bluez/test/example-advertisement`
2. Run `/usr/local/lib/bluez/test/example-gatt-server`
3. Use nRF Connect app on Android 9 phone to connect to the
"TestAdvertisement" device
The outcome is that the phone app tries to connect, but fails, leaving
me with a view of the GATT services and characteristics, but with no
way of accessing (read/write/notify) it. I have tried many other BLE
server implementations, but for the bug reporting I focused on the
most trusted reference.
Full logs are attached. The relevant part of the btmon log is here:
@ MGMT Event: Device Connected (0x000b) plen 13 {0x0001} [hci0] 945.575247
LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
Flags: 0x
Data length: 0
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2 #32 [hci0]
945.575351
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
@ RAW Open: btmon (privileged) version 2.22 {0x0002} 945.575453
@ RAW Close: btmon {0x0002} 945.575462
> HCI Event: LE Meta Event (0x3e) plen 4 #33 [hci0] 945.575984
LE Channel Selection Algorithm (0x14)
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Algorithm: #1 (0x00)
> HCI Event: LE Meta Event (0x3e) plen 6 #34 [hci0] 945.576990
LE Advertising Set Terminated (0x12)
Status: Success (0x00)
Handle: 1
Connection handle: 3585
Number of completed extended advertising events: 0
> HCI Event: Command Status (0x0f) plen 4 #35 [hci0] 945.578094
LE Read Remote Used Features (0x08|0x0016) ncmd 1
Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
< HCI Command: Disconnect (0x01|0x0006) plen 3 #36 [hci0] 945.578193
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Remote User Terminated Connection (0x13)
> HCI Event: Command Status (0x0f) plen 4 #37 [hci0] 945.579984
Disconnect (0x01|0x0006) ncmd 1
Status: Success (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4 #38 [hci0] 945.652123
Status: Success (0x00)
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Connection Terminated By Local Host (0x16)
@ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0001} [hci0] 945.652224
LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Connection terminated by local host (0x02)
The Additional information:
$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: BC:6E:E2:D0:B1:27 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:3074 acl:43 sco:0 events:194 errors:0
TX bytes:7295 acl:42 sco:0 commands:125 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'epitos'
Class: 0x6c010c
Service Classes: Rendering, Capturing, Audio, Telephony
Device Class: Computer, Laptop
HCI Version: (0xc) Revision: 0x3484
LMP Version: (0xc) Subversion: 0x3484
Manufacturer: Intel Corp. (2)
$ bluetoothctl
Agent registered
[CHG] Controller BC:6E:E2:D0:B1:27 Pairable: yes
[bluetooth]# show
Controller BC:6E:E2:D0:B1:27 (public)
Name: epitos
Alias: epitos
Class: 0x006c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: Audio Sink (110b--1000-8000-00805f9b34fb)
UUID: Headset (1108--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Vendor specific (12345678-1234-5678-1234-56789abcdef0)
UUID: Device Information (180a--1000-8000-00805f9b34fb)
UUID: Battery Service (180f--1000-8000-00805f9b34fb)
UUID: Heart Rate (180d--1000-8000-00805f9b34fb)
[Kernel-packages] [Bug 1860284]
Created attachment 303309 dmsg of experimental patch, dock attached after boot -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: benoitg1182 F pulseaudio CurrentDesktop: KDE Date: Sun Jan 19 12:38:17 2020 InstallationDate: Installed on 2020-01-16 (3 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1860284/+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 1860284]
Created attachment 303314
add resource clip debug
Thank you very much, Werner! I was confused about why your machine has
DMI_BOARD_NAME "X170KM-G", but didn't match the quirk in d341838d776a
("x86/PCI: Disable E820 reserved region clipping via quirks"), but I see
that in comment #62 I suggested reverting it, so I assume that's why I
don't see "PCI: %s detected: not clipping E820 regions from _CRS" in
your logs.
So the fact that it works as expected with the comment #62 patch but
without the d341838d776a quirk is great news.
I do want to figure out the "clipped [mem size 0x 64bit] to [mem
size 0xfffa 64bit]" messages, which seem sort of bogus. Can
I trouble you to add this patch and attach the dmesg (from either dock
scenario)?
--
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/1860284
Title:
thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on
Yoga C940 unless plugged in before boot
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a
New Lenovo Yoga C940 laptop.
- The dock works fine when plugged-in before boot.
- The dock does NOT work when plugged after the system booted.
- The dock does NOT work when plugged-in at boot, subsequently unplugged and
plugged back in.
When it fails, it fails with memory allocation messages such as:
[ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20]
[ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size
0x0c20]
Things I tried:
- Kernel mainline 5.4.12, same symptoms
- Kernel mainline 5.5.-rc6,
same symptoms.
- Plugging it after powering up the laptop, but at the grub screen before
boot. In this case the dock works fine after boot.
Other potentially useful information to narrow it down:
- The tests were done with only an ethernet cable and power plugged into the
dock to minimize the number of moving parts...
- Dock and laptop both have the very latest firmware as of 2020-01-17.
- The displayport part of the dock always work, but all other ports (USB,
ethernet, card readers fail) when plugged-in after boot.
- Doesn't seem to be a thunderbolt authorization problem:
benoitg@benoitg-Yoga-C940:~$ boltctl
? Lenovo ThinkPad Thunderbolt 3 Dock
?? type: peripheral
?? name: ThinkPad Thunderbolt 3 Dock
?? vendor:Lenovo
?? uuid: 001730c5-7042-0801--
?? status:authorized
? ?? domain: c06e823d-af8a-8680--
? ?? authflags: none
?? authorized:Sun Jan 19 17:41:04 2020
?? connected: Sun Jan 19 17:41:04 2020
?? stored:Thu Jan 16 07:27:43 2020
?? policy: iommu
?? key:no
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-26-generic 5.3.0-26.28
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: benoitg1182 F pulseaudio
CurrentDesktop: KDE
Date: Sun Jan 19 12:38:17 2020
InstallationDate: Installed on 2020-01-16 (3 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 81Q9
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic
root=UUID=078b76d6-6b72-4de4-9e10-f6ea33d9bc1a ro
RelatedPackageVersions:
linux-restricted-modules-5.3.0-26-generic N/A
linux-backports-modules-5.3.0-26-generic N/A
linux-firmware1.183.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: AUCN45WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga C940-14IIL
dmi.modalias:
dmi:bvnLENOVO:bvrAUCN45WW:bd08/22/2019:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
dmi.product.family: Yoga C940-14IIL
dmi.product.name: 81Q9
dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
dmi.product.version: Lenovo Yoga C940-14IIL
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1860284/+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 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
** Tags added: nvidia suspend-resume ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
[Kernel-packages] [Bug 1998168] 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 1998168
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
Incomplete
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+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 1996068] Re: i915 0000:00:02.0: Block 42 min_size is zero | WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915]
** Summary changed: - i915 crash at boot time (probably to activate vga console) + i915 :00:02.0: Block 42 min_size is zero | WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] -- 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/1996068 Title: i915 :00:02.0: Block 42 min_size is zero | WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Status in linux package in Ubuntu: Confirmed Bug description: This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen. Nov 5 09:46:42 shusaku kernel: [2.209937] [ cut here ] Nov 5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 min_size is zero Nov 5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin ctrl_tigerlake Nov 5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu Nov 5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022 Nov 5 09:46:42 shusaku kernel: [2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915] Nov 5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 48 c7 c7 Nov 5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 EFLAGS: 00010246 Nov 5 09:46:42 shusaku kernel: [2.210170] RAX: RBX: 8ca1a1108000 RCX: Nov 5 09:46:42 shusaku kernel: [2.210171] RDX: RSI: RDI: Nov 5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: R09: Nov 5 09:46:42 shusaku kernel: [2.210173] R10: R11: R12: 002a Nov 5 09:46:42 shusaku kernel: [2.210174] R13: R14: 8ca1826ad170 R15: 8ca1a1109328 Nov 5 09:46:42 shusaku kernel: [2.210175] FS: 7f21d34178c0() GS:8ca8bf48() knlGS: Nov 5 09:46:42 shusaku kernel: [2.210176] CS: 0010 DS: ES: CR0: 80050033 Nov 5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 00011d202003 CR4: 00770ee0 Nov 5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554 Nov 5 09:46:42 shusaku kernel: [2.210179] Call Trace: Nov 5 09:46:42 shusaku kernel: [2.210181] Nov 5 09:46:42 shusaku kernel: [2.210183] intel_bios_init+0x171/0x7c0 [i915] Nov 5 09:46:42 shusaku kernel: [2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm] Nov 5 09:46:42 shusaku kernel: [2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915] Nov 5 09:46:42 shusaku kernel: [2.210594] i915_driver_probe+0x1ae/0x490 [i915] Nov 5 09:46:42 shusaku kernel: [2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm] Nov 5 09:46:42 shusaku kernel: [2.210833] ? acpi_dev_found+0x64/0x80 Nov 5 09:46:42 shusaku kernel: [2.210842] i915_pci_probe+0x56/0x150 [i915] Nov 5 09:46:42 shusaku kernel: [2.210935] local_pci_probe+0x44/0x90 Nov 5 09:46:42 shusaku kernel: [2.210939] pci_call_probe+0x55/0x190 Nov 5 09:46:42 shusaku kernel: [2.210940] pci_device_probe+0x84/0x120 Nov 5 09:46:42 shusaku kernel: [2.210941] really_probe+0x1dc/0x3b0 Nov 5 09:46:42 shusaku kernel: [2.210945] __driver_probe_device+0x12c/0x1b0 Nov 5 09:46:42 shusaku kernel: [2.210946] driver_probe_device+0x24/0xd0 Nov 5 09:46:42 shusaku kernel: [2.210948] __driver_attach+0xe0/0x210 Nov 5 09:46:42 shusaku kernel: [2.210949] ? __device_attach_driver+0x130/0x130 Nov 5 09:46:42 shusaku kernel: [2.210951] bus_for_each_dev+0x8d/0xe0 Nov 5 09:46:42 shusaku kernel: [2.210952] driver_attach+0x1e/0x30 Nov 5 09:46:42 shusaku kernel: [2.210953] bus_add_driver+0x187/0x230 Nov 5 09:46:42 shusaku kernel: [2.210955] driver_register+0x8f/0x100 Nov 5 09:46:42 shusaku kernel: [2.210956] __pci_register_driver+0x62/0x70 Nov 5
[Kernel-packages] [Bug 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
** Patch added: "suggested fix to apply in -dev and SRU so that tests will work again" https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+attachment/5633150/+files/0001-Fix-tests-to-be-compatible-to-jammy.patch ** Also affects: ubuntu-fan (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: This breaks all ubuntu-fan autopkgtest since Jammy was released in April 2022. Miriam found it while checking an autopkgtest regression in bug 1995260 Summary: - the tests in test_local_lxd hardcode to "lts" local series='lts' - due to that we always test the latest (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+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 1998184] [NEW] fanatic tests spawn latest LTS but isn't compatible with it
Public bug reported: This breaks all ubuntu-fan autopkgtest since Jammy was released in April 2022. Miriam found it while checking an autopkgtest regression in bug 1995260 Summary: - the tests in test_local_lxd hardcode to "lts" local series='lts' - due to that we always test the latest (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Focal) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: This breaks all ubuntu-fan autopkgtest since Jammy was released in April 2022. Miriam found it while checking an autopkgtest regression in bug 1995260 Summary: - the tests in test_local_lxd hardcode to "lts" local series='lts' - due to that we always test the latest (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+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 1945369] Re: memory cgroup disabled on Ubuntu Core 18
Thanks Patrick, I found that this was accessible on host as /writable/system-data/var/lib/snapd/seed/cmdline.txt and updating it there worked (after reboot). -- 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/1945369 Title: memory cgroup disabled on Ubuntu Core 18 Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu Core 18, the memory cgroup is disabled, it seems that it needs to be manually enabled. I was able to enable it by adding `cgroup_enable=memory cgroup_memory=1` to the kernel command line, but on Ubuntu I think the memory cgroup should be enabled by default shouldn't it? $ cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset2 1 1 cpu 4 100 1 cpuacct 4 100 1 blkio 5 100 1 memory0 109 0 devices 6 100 1 freezer 9 4 1 net_cls 3 1 1 perf_event10 1 1 net_prio 3 1 1 pids 8 107 1 rdma 7 1 1 I see this with Linux localhost 5.4.0-1043-raspi #47~18.04.1-Ubuntu SMP PREEMPT Mon Aug 23 14:39:46 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux on Ubuntu Core 18, but folks have informed me that the same is true on Ubuntu Core 20 as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945369/+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 1996900] [NEW] [amdgpu] [KDE] Display flashes
You have been subscribed to a public bug: During normal usage the display sometimes flashes black. In particular some websites cause intense flickering with several black frames per second. This actually seems to happen in both Wayland and xorg sessions and flashes the entire screen, so it seems more like a driver bug but I'm not sure where to file that. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 17 14:00:15 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] InstallationDate: Installed on 2022-10-30 (18 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2022 dmi.bios.release: 6.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0603 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X670E-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/08/2022:br6.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug corruption kinetic kubuntu ubuntu wayland-session -- [amdgpu] [KDE] Display flashes https://bugs.launchpad.net/bugs/1996900 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
This issue occured when server connect network and the ip can access Internet.
This issue will disappear when 1)don't plug network cable or 2)disable Network
interface->"continue without network" during installation
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
New
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: New Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: New Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+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 1998168] [NEW] System went crash during Ubuntu 20.04.5 installation
Public bug reported:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving crash
report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install: FAIL:
Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zero
exit status 100.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "sosreport"
https://bugs.launchpad.net/bugs/1998168/+attachment/5633061/+files/sosreport-ubuntu-server-2022-09-28-bjkrbsx.tar.xz
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
New
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+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 1998184] [NEW] fanatic tests spawn latest LTS but isn't compatible with it
You have been subscribed to a public bug by Christian Ehrhardt (paelzer): This breaks all ubuntu-fan autopkgtest since Jammy was released in April 2022. Miriam found it while checking an autopkgtest regression in bug 1995260 Summary: - the tests in test_local_lxd hardcode to "lts" local series='lts' - due to that we always test the latest (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New -- fanatic tests spawn latest LTS but isn't compatible with it https://bugs.launchpad.net/bugs/1998184 You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. -- 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 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
I prepared and linked a set of changes to hint the current version as badtest. Please consider merging them as this version will be broken permanently until a new upload will fix this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: This breaks all ubuntu-fan autopkgtest since Jammy was released in April 2022. Miriam found it while checking an autopkgtest regression in bug 1995260 Summary: - the tests in test_local_lxd hardcode to "lts" local series='lts' - due to that we always test the latest (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+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 1998184] Re: fanatic tests spawn latest LTS but isn't compatible with it
** Merge proposal linked: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/433767 ** Merge proposal linked: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/433768 ** Merge proposal linked: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/433769 ** Merge proposal linked: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/433770 ** Merge proposal linked: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/433771 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1998184 Title: fanatic tests spawn latest LTS but isn't compatible with it Status in ubuntu-fan package in Ubuntu: New Status in ubuntu-fan source package in Bionic: New Status in ubuntu-fan source package in Focal: New Status in ubuntu-fan source package in Jammy: New Status in ubuntu-fan source package in Kinetic: New Status in ubuntu-fan source package in Lunar: New Bug description: This breaks all ubuntu-fan autopkgtest since Jammy was released in April 2022. Miriam found it while checking an autopkgtest regression in bug 1995260 Summary: - the tests in test_local_lxd hardcode to "lts" local series='lts' - due to that we always test the latest (good) but are now incompatible :-/ - systemd renamed systemd-resolve to resolvectl in v239 and later dropped the old name - Jammy comes without systemd-resolve We now face: - bionic: systemd-resolved - focal: systemd-resolved + resolvectl - jammy: resolvectl - due to that all tests fail nowadays with: ... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... /bin/sh: 29: systemd-resolve: not found slave: waiting for systemd resolver... ... slave: systemd-resolve failure! Until this is fixed in ubuntu-fan (@Kernel team?) - according to the mapping it is kernel-packages that owns this so I'll subscribe them right away - these tests will block everything depending on it. Therefore let us mask the current version from proposed migration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1998184/+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 1990964] Re: FTBFS on kinetic
** Changed in: strace (Ubuntu) Assignee: Adrien Nader (adrien-n) => Graham Inggs (ginggs) ** Changed in: strace (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: In Progress Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+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 1995021] [NEW] Boot and shutdown take several minutes
You have been subscribed to a public bug: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment jammy -- Boot and shutdown take several minutes https://bugs.launchpad.net/bugs/1995021 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995021] Re: Boot and shutdown take several minutes
Thanks. It does seem to be a crash in the Nvidia driver. Maybe as a workaround try: * Kernel parameter "nosplash" * Nvidia-520 instead. Although the logs also mention "kernel: *BAD*gran_size" so I'm wondering if that means there is faulty RAM, which would easily explain the crashes. ** Package changed: ubuntu => nvidia-graphics-drivers-515 (Ubuntu) ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: Incomplete => New ** Summary changed: - Boot and shutdown take several minutes + Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash ** Tags added: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1995021 Title: Boot and shutdown take several minutes. "watchdog: BUG: soft lockup - CPU#0 stuck for 26s!" followed by nvidia kernel crash Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: My system has been running smoothly until Kernel 5.15.0-50 (and 5.15.0-52) was installed. Now boot and shutdown take several minutes. I have an Nvidia Gforce 1050 and Nvidia driver 515. Boot and shutdown run witout delay with the Nouveau and Nvidia 390 drivers but the OpenCl is unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1995021/+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 1993223] Re: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04
verified linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.7 ** Tags added: verification-done-jammy -- 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/1993223 Title: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Released Bug description: [SRU Justification] [Impact] Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. [Fix] 5 commits from mainline firmware repository. [Test Case] Kernel dmesg should no longer dump: amdgpu_vcn: Can't load firmware amdgpu/vcn_3_1_2.bin [Where problems could occur] New hardware support. May affect system stability. [Other Info] These firmware blobs are only referenced in linux/kinetic and linux- oem-6.0/jammy, and are already available in linux-firmware/kinetic, so only Jammy is nominated for fix here. == original bug report == Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. This firmware has been upstreamed by these commits, which are already part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1) db6db36a amdgpu: add firmware for VCN 3.1.2 IP block 3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block 639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block 76589464 amdgpu: add firmware for GC 10.3.6 IP block 427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block Matching kernel code for this processor is already upstreamed in 6.0 kernel, and so this should work with OEM-6.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993223/+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 1995749] [NEW] Maximum resolution not available after suspend / screen detach
You have been subscribed to a public bug: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 4 23:29:27 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.12.0, 5.15.0-52-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-U GT2 [UHD Graphics] [1028:0962] InstallationDate: Installed on 2022-10-21 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 13 7390
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
Shaun, that's something completely irrelevant for this bug, you're using a dkms from AMD, which we don't support -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1995749] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 4 23:29:27 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.12.0,
[Kernel-packages] [Bug 1996053] Re: No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works)
Also while using kernel 5.15 please run: journalctl -b0 > oldkernel.txt lspci -kv > lspci.txt and attach the resulting text files here. ** 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/1996053 Title: No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works) Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996053/+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 1996053] Re: No GUI after upgrade from 22.04.1 to 22.10
Thanks for the bug report. Please try using: sudo journalctl -b-1 > prevboot.txt or similar to collect a log from the failed boot with kernel 5.19. ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Tags added: kinetic regression-release ** Summary changed: - No GUI after upgrade from 22.04.1 to 22.10 + No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works) -- 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/1996053 Title: No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works) Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996053/+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 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC
A bunch of fixes for this card have gone in. I'd make sure you are using the 5.15 HWE kernel on focal if anyone has issues with this card. -- 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/1990156 Title: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC Status in linux package in Ubuntu: Expired Bug description: Hi! We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems. The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" network cards. When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) the network card is working without issues. When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) the system will only boot when the NIC has not been configured using netplan. After configuring (and therefore enabling) the NIC in netplan, the system will hang at "Wait for network to be configured". After waiting for some time other error messages also are being shown: "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 5.15.0-46-generic" Same for task systemd-network and systemd-udevd. The NIC is using "ice" kernel driver: root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - version 0.8.1-k I suspect there have been changes performed in that particular driver between 5.4 and 5.15 release. If additional information is required I am happy to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990156/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-firmware (Ubuntu) -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux-firmware source package in Kinetic: New Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1987595] Re: Support Intel IPU6 MIPI camera
verified linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.7, linux-firmware/kinetic version 20220923.gitf09bebf3-0ubuntu1.1 ** Tags added: verification-done-jammy verification-done-kinetic -- 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/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Incomplete Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justfication:linux-firmware] [Impact] Need new firmware updates for additional camera senesors. [Fix] Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for hi556/ovti02c1. [Test Case] The driver will prompt for missed firmware blobs for a given platform. [Where problems could occur] There is still no suspend support for the camera driver, and user sessions across system suspend have to be restarted. [Other Info] New sensors are introduced in Jammy oem kernels only, and kinetic is nominated for future hwe migration. = original bug report == This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+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 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach
Also newer kernels may already contain a fix. Providing you are not using secure boot you can try newer kernels like: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2022-11-18/amd64/ -- 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/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: New Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 4 23:29:27 2022 DistUpgraded: Fresh install
[Kernel-packages] [Bug 1995749] Re: Maximum resolution not available after suspend / screen detach
Sounds like either a kernel bug or a kernel feature whereby it detects which modes the attached cable actually provides enough bandwidth for, and removes the modes that probably can't be sustained reliably. If it is just a bandwidth problem then replacing the display cable might fix it. ** Tags added: i915 multimonitor ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - Maximum resolution not available after suspend / screen detach + [i915] Maximum resolution not available after suspend / screen detach -- 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/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: New Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package:
[Kernel-packages] [Bug 1996053] [NEW] No GUI after upgrade from 22.04.1 to 22.10
You have been subscribed to a public bug: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description:Ubuntu 22.10 Release:22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- No GUI after upgrade from 22.04.1 to 22.10 https://bugs.launchpad.net/bugs/1996053 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
c59a5430-676f-11ed-a93a-fa163e55efd0 is a crash in KWin: https://errors.ubuntu.com/bucket/?id=/usr/bin/kwin_x11%3A11%3AKWin%3A%3AWorkspace%3A%3AworkspaceEvent%3AQAbstractEventDispatcher%3A%3AfilterNativeEvent%3AQXcbConnection%3A%3AhandleXcbEvent%3AQXcbConnection%3A%3AprocessXcbEvents%3AQXcbUnixEventDispatcher%3A%3AprocessEvents Judging by the timestamps in comment #3 however that should be ignored (from our perspective) because Xorg crashed first. ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago)
[Kernel-packages] [Bug 1995766] Re: X server segfault when starting youtube videos
The nvidia-470 driver sounds old and NVIDIA themselves seem to recommend driver 515 instead for your GPU. Please open the Additional Drivers app and try installing a newer NVIDIA driver. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1995766 Title: X server segfault when starting youtube videos Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: This is an intermittent bug; happens perhaps 1-3 times a week. Always when just starting to play a youtube videos (I haven't seen it playing videos on other sites, or locally, but the sample size is skewed.) I'm using Nvidia drivers with a 6GB 1060 GTX running three monitors. Kubuntu 22.04, up-to-date. GPU memory is not stressed (usually around 5 or 6% usage. System RAM is 16GB, also not stressed (10-15%). Stack trace in Xorg.0.log.old is always the same: [ 1890.850] (EE) [ 1890.850] (EE) Backtrace: [ 1890.851] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x558c420666e9] [ 1890.852] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40d5da5520] [ 1890.852] (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x558c41efb1e9] [ 1890.852] (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x558c41efcc85] [ 1890.852] (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x558c41efd183] [ 1890.852] (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x558c41efe183] [ 1890.853] (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x558c41fdca7d] [ 1890.853] (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x558c42006e4c] [ 1890.853] (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x558c4121] [ 1890.853] (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x558c4200011e] [ 1890.854] (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x558c4205fc60] [ 1890.854] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x558c4205fee8] [ 1890.854] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x558c41ef0257] [ 1890.854] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x558c41ef4524] [ 1890.854] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40d5d8cd90] [ 1890.854] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40d5d8ce40] [ 1890.855] (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x558c41edd5f5] [ 1890.855] (EE) [ 1890.855] (EE) Segmentation fault at address 0x7ffec8965000 [ 1890.855] (EE) Fatal server error: [ 1890.855] (EE) Caught signal 11 (Segmentation fault). Server aborting ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.141.03 Thu Jun 30 18:45:31 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 5 10:27:18 2022 DistUpgraded: 2022-05-14 14:47:14,165 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 6GB] [1462:3281] InstallationDate: Installed on 2020-04-27 (921 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. Z87X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=30826023-39fe-4d5c-8720-a3a2d86c4839 ro enable_mtrr_cleanup
[Kernel-packages] [Bug 1996678] Re: containerd sporadic timeouts
Note that this is not limited to containerd; we're running an upstream version of the prometheus `node_exporter` on several hosts that is also seeing spurious hangs that started after upgrading to the -132 kernel. Rebooting into -131 fixes it. -- 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/1996678 Title: containerd sporadic timeouts Status in containerd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in containerd source package in Focal: Confirmed Status in linux source package in Focal: In Progress Bug description: This morning I routinely upgraded security upgrades on number of machines. Containerd has upgraded from `1.5.9-0ubuntu1~20.04.4` for me `1.5.9-0ubuntu1~20.04.5`. What happened next: at some random time on machines with new containerd something happens with containerd tasks and/or cgroups. This is how it's seen in syslog: containerd[710]: time="2022-11-16T03:21:21.004153517Z" level=error msg="get state for 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a" error="context deadline exceeded: unknown" And some ctr commands: # ctr --namespace k8s.io task ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a0 UNKNOWN See that the status of the task is UNKNOWN (!!!) # ctr --namespace k8s.io container ls|grep 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a k8s.gcr.io/pause:3.5 io.containerd.runc.v2 Cgroups: ├─kubepods-besteffort-pod3fdc0061_bbf6_47d1_97f5_b1f271b46e23.slice │ ├─cri-containerd-5f78e0cb957de97fd8465cc42c842bdd764d981ca7a903a2515bbc6bb06796a9.scope … │ │ └─2677 /csi-node-driver-registrar --v=0 --csi-address=/csi/csi.sock --k… │ ├─cri-containerd-af070f16c1f0ff22eb16661e787e85db3810727909abd23d69a6a43578c1dced.scope … │ │ └─3264 /usr/local/bin/cephcsi --type=liveness --endpoint=unix:///csi/cs… │ ├─cri-containerd-4e063ef0c8f768dbf34cf7a179bca5cc98a04fa7e00b29d20c17d3031d409f86.scope … │ │ └─2960 /usr/local/bin/cephcsi --nodeid=nas-decent-bobcat.dev-k8s-1.hq.w… │ └─cri-containerd-2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a.scope … │ └─2414 /pause # ps auxf|grep 2414 -B 2 root2279 0.1 0.0 114100 4956 ?Sl Nov15 0:42 /usr/bin/containerd-shim-runc-v2 -namespace k8s.io -id 2f5a8376b476809b1696b140ca87f91422113bb16b27a8174437cc63b48e259a -address /run/containerd/containerd.sock 65535 2414 0.0 0.0964 4 ?Ss Nov15 0:00 \_ /pause It happens not immediately - but after some random time. Sometimes it's several minutes, sometimes it's around an hour. But nonetheless - all machines with the new package get into this weird state. As long as I revert package - it all returns to run as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1996678/+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 1995320] Re: [amdgpu] intermittent green static
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995320 Title: [amdgpu] intermittent green static Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: After upgrading from 22.04 to 22.10 I've been seeing some display glitches. - green static appears, usually when scrolling, regular sized green blocks, like giant pixels - firefox not refreshing when full screen video plays (separate windows, separate screens) I would guess I probably have the wrong package here, but there's no way for me to tell if it's mesa, the kernel, gnome-shell, or something else. Radeon 6700XT Dual displays Wayland ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 21:46:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (1231 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2019-06-18 (1232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic wayland-session Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+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 1997944] Re: Soundwire support for the Intel RPL Gen platforms
** Also affects: firmware-sof (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997944 Title: Soundwire support for the Intel RPL Gen platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: New Status in firmware-sof source package in Lunar: New Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997944/+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 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
** No longer affects: linux-firmware (Ubuntu Jammy) ** No longer affects: linux-firmware (Ubuntu Kinetic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver. These commits are already in oem-6.0 and unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997200/+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 1998103] [NEW] Intel 8087:07dc Bluetooth highly unreliable
Public bug reported: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not and not from anything I count identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel logs" https://bugs.launchpad.net/bugs/1998103/+attachment/5632971/+files/bluetooth.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: New Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not and not from anything I count identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998106] [NEW] Fix AMD-PState driver for Genoa CPU
Public bug reported: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => 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/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.17 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998097] [NEW] nvidia-dkms-520-open 520.56.06-0ubuntu0.22.04.1: nvidia kernel module failed to build
Public bug reported: I downloaded the ubuntu cuda toolkit 22 520 driver - I disable the open nuoveu driver - then instlal toolkit screen is black I unistall nvidia driver I install open kernal via software updates - but no joy. crahsing. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-520-open 520.56.06-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 5.15.0-53-generic Date: Mon Nov 28 21:57:56 2022 DuplicateSignature: dkms:nvidia-dkms-520-open:520.56.06-0ubuntu0.22.04.1:gcc: error: unrecognized command line option ‘-mharden-sls=all’ InstallationDate: Installed on 2022-11-28 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageVersion: 520.56.06-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-520 Title: nvidia-dkms-520-open 520.56.06-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-520 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1998097 Title: nvidia-dkms-520-open 520.56.06-0ubuntu0.22.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-520 package in Ubuntu: New Bug description: I downloaded the ubuntu cuda toolkit 22 520 driver - I disable the open nuoveu driver - then instlal toolkit screen is black I unistall nvidia driver I install open kernal via software updates - but no joy. crahsing. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-520-open 520.56.06-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass DKMSKernelVersion: 5.15.0-53-generic Date: Mon Nov 28 21:57:56 2022 DuplicateSignature: dkms:nvidia-dkms-520-open:520.56.06-0ubuntu0.22.04.1:gcc: error: unrecognized command line option ‘-mharden-sls=all’ InstallationDate: Installed on 2022-11-28 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageVersion: 520.56.06-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-520 Title: nvidia-dkms-520-open 520.56.06-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1998097/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable
** Attachment added: "lsusb info" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+attachment/5632972/+files/intel_07dc.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: New Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not and not from anything I count identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable
Thank you for your bug report but that's the Ubuntu tracker, report Mint issues to them ** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: Invalid Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not and not from anything I count identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998106] 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 1998106 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 ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) 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/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.17 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1998103] 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 1998103 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not from anything I could identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable
Unforntunately there is no kernel core dump for this error. just the hci subsystem losing its mind, as attached in the logs. Happy to see what else I can provide -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not from anything I could identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1639924] Re: Kernel livepatch support for for s390x
** Description changed: - Kernel live-patch is afaik fully upstream and available for 'all' platforms (incl. s390x). - But the kpatch-build tool does only support amd64 as of today. + [ Impact ] + + * kpatch upstream has gained support for more architectures which we + would like to enable on LTS release. Since building livepatches using + the kpatch tooling makes the most sense on LTS kernels. + + * This SRU is to enable s390x builds of kpatch on kinetic & jammy. + + * Separately linux kernel patches for s390x will also be backported to + the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to + support livepatches. + + [ Test Plan ] + + * Attempt to run and load sample integration livepatches from the + kpatch integration source code, against v5.15 & v5.19 kernels. These + should succeed on: + + - amd64 jammy v5.15 + - amd64 & s390x jammy v5.19 + - amd64 & s390x kinetic v5.19 + + [ Where problems could occur ] + + * The newly generated livepatches produced by this kpatch may have + different content (more or less sections/sybmols/relocations/etc), but + remain compatible with all prior kernels and tool-chains. + + * This is a fairly large upstream update to the tooling. + + * One command line option to kpatch-build is no longer supported '-e', + instead long form command line option must be used '--oot-module'. And ' + --ott-module-src' becomes mandatory in such cases, previously '-- + sourcedire' was required. + + Additional command line options added '--oot-module-src, -R|--non- + replace'. + + '--skip-gcc-check' is still supported but prints warnings, it is + deprecated in favour of '--skip-compiler-check'. + + kpatch-cc utility is added, which is a toolchain wrapper. + + Thus adjustments might be needed to scripts used to invoke and create + kpatch modules. + + * Majority of non-test/non-doc changes are to do with: +- add support for s390x and 32bit powerpc +- add support for newer kernels and compilers (support & bugfixes to various sections and symbols) +- more strict checking and bugfixes w.r.t. livepatch generation +- refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. + + * Some of the fixes from these new upstream releases have already been + cherry-picked in the kpatch, but others might soon be needed on x84, + i.e. to support gcc-12 built kernels. + + $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-build/ + > shortlog.txt + + d46fea98ef kpatch-build: strengthen conditions for changed sections + 9fac261ed0 kpatch-build: rela section could disappear after patched + fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules + 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support + 07433e98c0 kpatch-cc: fix stripping of source tree prefix + 33368a88cd create-diff-object: add support for .return_sites section (x86) + e921c557f9 macros: tweak syscall patching macros + a1171b112e create-diff-object: Create missing section symbol + 0308d52bcd kpatch/s390: Enable kpatch build support + b0330ab18e kpatch/s390: Add additional bundled symbols. + eb4a85f778 kpatch/s390: Add exclusion lists + f0d00a9290 kpatch/s390: Add initial support for kpatch + 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch + c6d0b5450b lookup: fix symtab parsing + 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() + 017015a725 create-diff-object: make kpatch_check_relocations() more precise + f0e3da336c create-diff-object: fix string extraction + 86d5208b46 create-diff-object: error on symbol conversion failure + 325bccd89d create-diff-object: skip conversion for sections which never have symbols + 8508abd3b1 create-diff-object: allow converstion of empty symbols + 8d5a628bde create-diff-object: add extra check for symbol conversion edge case + 01427d50a1 create-diff-object: move addend math to a new function + bec6488af6 create-diff-object: add rela_insn() error check + 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' + bf212f7750 create-diff-object: error on unsupported rela in symbol conversion + 3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms() + 79f45d1b0a create-diff-object: fix kpatch_replace_sections_syms() for non-text + 61e46094b5 create-diff-object: convert function return types to 'bool' + c24d135f40 create-diff-object: rename "sec" -> "relasec" for rela sections + 3b63456817 kpatch-elf: convert functions to static + 0c5a1e7753 kpatch-build: make xtrace output less verbose + 2784f5056b kpatch-build: add support for openEuler + 3392049665 kpatch-build: remove duplicated use_klp_arch + e9c0b67862 macros: add syscall patching macros + c2e73c2cbc create-diff-object: ensure debug sections don't use dynrelas + 305ff8a5d8 create-diff-object: include .LCx string literal symbols + b700732f5d create-diff-object: add "_printk" to the __LINE__ detection +
[Kernel-packages] [Bug 1995749] Re: [i915] Maximum resolution not available after suspend / screen detach
Thanks Daniel, As I currently have a correct resolution setting at work (see #2) without any hardware replacement, I don't think this is a hardware (cable) problem. I'll test this evening at home again, as well as with a new kernel. -- 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/1995749 Title: [i915] Maximum resolution not available after suspend / screen detach Status in linux package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 22.04.3, using the default Wayland, on my laptop which is used at two locations: - at work I have my primary built-in 4K display and 2 additional 1920x1080 monitor connected to a HP DisplayLink docking station using DP, connected to my laptop using USB-C - at home, I have my primary built-in 4K display and an additional 4x monitor directly connected using the mini-DP After boot, everything works perfect. However, after working at work, putting the laptop into suspend (by closing the lid), attaching to my monitor at home and opening the lid again, I get my external display at a poor resolution which I cannot change to 4K in the settings menu: the 4K resolution is not available. Also in xrandr, the 4K resolution is not available. The resolution is however correctly provided by the monitor at all times: $ sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "PHL 328P6V" ModelName "PHL 328P6V" VendorName "PHL" # Monitor Manufactured week 30 of 2020 # EDID version 1.4 # Digital Display DisplaySize 700 400 Gamma 2.20 Option "DPMS" "true" Horizsync 30-160 VertRefresh 23-80 # Maximum pixel clock is 600MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1440x900, 75Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1280x720, 60Hz #Extension block found. Parsing... Modeline"Mode 12" 262.75 3840 3888 3920 4000 2160 2163 2168 2191 +hsync -vsync Modeline"Mode 0" 533.25 3840 3888 3920 4000 2160 2163 2168 +hsync -vsync Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline"Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline"Mode 10" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline"Mode 11" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline"Mode 13" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline"Mode 14" 277.25 1920 1968 2000 2080 2160 2163 2173 +hsync -vsync Modeline"Mode 15" 147.17 2048 2096 2128 2208 1080 1083 1093 +hsync -vsync Option "PreferredMode" "Mode 12" EndSection Previously, using Ubuntu 20.04, I've had the same issue using Xorg, which could easily be solved by unplugging the external monitor and plugging in back again, which worked most of the times, sometimes only after a few retries. Now, with Ubuntu 22.04.3 and Wayland, this doesn't work anymore. Logging out in this situation and logging in again in an Xorg session doesn't help either. Only a reboot seems to help. Additional debug information at a situation with wrong resolution can be provided on Monday, as I just rebooted again :-) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 4
[Kernel-packages] [Bug 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable
** Description changed: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg - * now it went ballistic and caused my UI to freeze, not and not from anything I count identify that I did. + * now it went ballistic and caused my UI to freeze, not from anything I could identify that I did. inxi -EbA System: - Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 - Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa + Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 + Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: - Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 - serial: - Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: - UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 + Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 + serial: + Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: + UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: - Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 - min/max: 800/3500 + Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 + min/max: 800/3500 Audio: - Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio - driver: snd_hda_intel - Device-2: Intel 8 Series/C220 Series High Definition Audio - driver: snd_hda_intel - Sound Server-1: ALSA v: k5.15.0-53-generic running: yes - Sound Server-2: PulseAudio v: 15.99.1 running: yes + Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio + driver: snd_hda_intel + Device-2: Intel 8 Series/C220 Series High Definition Audio + driver: snd_hda_intel + Sound Server-1: ALSA v: k5.15.0-53-generic running: yes + Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: - Device-1: Intel Bluetooth wireless interface type: USB driver: btusb - Report: hciconfig ID: hci0 rfk-id: 0 state: down - bt-service: enabled,running rfk-block: hardware: no software: yes - address: 30:3A:64:EA:9C:EA + Device-1: Intel Bluetooth wireless interface type: USB driver: btusb + Report: hciconfig ID: hci0 rfk-id: 0 state: down + bt-service: enabled,running rfk-block: hardware: no software: yes + address: 30:3A:64:EA:9C:EA attached kernel logs ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not from anything I could identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable
~seb128 I dont think thats fair, this is very likely kernel-related, and the kernel is AFAIK an ubuntu kernel. Unless I am misunderstanding something -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not from anything I could identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1639924] Re: Kernel livepatch support for for s390x
Currently libunwind-dev is not used on s390x by the kernel build, thus the runtime dep for libunwind-dev can probably be dropped, will test. Also not sure why it is at all specified. ** Description changed: [ Impact ] - * kpatch upstream has gained support for more architectures which we + * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. - * This SRU is to enable s390x builds of kpatch on kinetic & jammy. - - * Separately linux kernel patches for s390x will also be backported to + * This SRU is to enable s390x builds of kpatch on kinetic & jammy. + + * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] - * Attempt to run and load sample integration livepatches from the + * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - - amd64 jammy v5.15 - - amd64 & s390x jammy v5.19 - - amd64 & s390x kinetic v5.19 + - amd64 jammy v5.15 + - amd64 & s390x jammy v5.19 + - amd64 & s390x kinetic v5.19 [ Where problems could occur ] - * The newly generated livepatches produced by this kpatch may have + * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. - * This is a fairly large upstream update to the tooling. - - * One command line option to kpatch-build is no longer supported '-e', + * This is a fairly large upstream update to the tooling. + + * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot-module'. And ' --ott-module-src' becomes mandatory in such cases, previously '-- sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. - * Majority of non-test/non-doc changes are to do with: -- add support for s390x and 32bit powerpc -- add support for newer kernels and compilers (support & bugfixes to various sections and symbols) -- more strict checking and bugfixes w.r.t. livepatch generation -- refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. + * Majority of non-test/non-doc changes are to do with: + - add support for s390x and 32bit powerpc + - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) + - more strict checking and bugfixes w.r.t. livepatch generation + - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function
[Kernel-packages] [Bug 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989944 Title: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Fix Committed Bug description: [SRU Justification] == Impact == We applied a set of patches early as the upstreaming got delayed. The patch now is in upstream linux. Since it differs somewhat from the patch we carry and in order to get potential security and other updates right, we want to replace the SAUCE patch by its upstream counterpart. == Fix == “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” == Testcase == Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 1983143) == Regression Potential == Previously working external connections might no longer work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+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 1997994] Re: Focal update: v5.4.222 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997994 Title: Focal update: v5.4.222 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.4.222 upstream stable release from git://git.kernel.org/ once: fix section mismatch on clang builds Linux 5.4.222 UBUNTU: Upstream stable to v5.4.222 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997994/+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 1997981] Re: Jammy update: v5.15.77 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997981 Title: Jammy update: v5.15.77 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed 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.77 upstream stable release from git://git.kernel.org/ NFSv4: Fix free of uninitialized nfs4_label on referral lookup. NFSv4: Add an fattr allocation to _nfs4_discover_trunking() can: j1939: transport: j1939_session_skb_drop_old(): spin_unlock_irqrestore() before kfree_skb() can: kvaser_usb: Fix possible completions during init_completion ALSA: Use del_timer_sync() before freeing timer ALSA: usb-audio: Add quirks for M-Audio Fast Track C400/600 ALSA: au88x0: use explicitly signed char ALSA: rme9652: use explicitly signed char USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM usb: gadget: uvc: fix sg handling in error case usb: gadget: uvc: fix sg handling during video encode usb: dwc3: gadget: Stop processing more requests on IMI usb: dwc3: gadget: Don't set IMI for no_interrupt usb: bdc: change state when port disconnected usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 controller mtd: rawnand: marvell: Use correct logic for nand-keep-config xhci: Add quirk to reset host back to default state at shutdown xhci-pci: Set runtime PM as default policy on all xHC 1.2 or later devices xhci: Remove device endpoints from bandwidth list when freeing the device tools: iio: iio_utils: fix digit calculation iio: light: tsl2583: Fix module unloading iio: temperature: ltc2983: allocate iio channels once iio: adxl372: Fix unsafe buffer attributes fbdev: smscufx: Fix several use-after-free bugs cpufreq: intel_pstate: Read all MSRs on the target CPU cpufreq: intel_pstate: hybrid: Use known scaling factor for P-cores fs/binfmt_elf: Fix memory leak in load_elf_binary() exec: Copy oldsighand->action under spin-lock mac802154: Fix LQI recording scsi: qla2xxx: Use transport-defined speed mask for supported_speeds drm/amdgpu: disallow gfxoff until GC IP blocks complete s2idle resume drm/msm/dsi: fix memory corruption with too many bridges drm/msm/hdmi: fix memory corruption with too many bridges drm/msm/dp: fix IRQ lifetime coresight: cti: Fix hang in cti_disable_hw() mmc: sdhci_am654: 'select', not 'depends' REGMAP_MMIO mmc: core: Fix kernel panic when remove non-standard SDIO card mmc: sdhci-pci-core: Disable ES for ASUS BIOS on Jasper Lake mmc: sdhci-esdhc-imx: Propagate ESDHC_FLAG_HS400* only on 8bit bus counter: microchip-tcb-capture: Handle Signal1 read and Synapse kernfs: fix use-after-free in __kernfs_remove pinctrl: Ingenic: JZ4755 bug fixes ARC: mm: fix leakage of memory allocated for PTE perf auxtrace: Fix address filter symbol name match for modules s390/futex: add missing EX_TABLE entry to __futex_atomic_op() s390/pci: add missing EX_TABLE entries to __pcistg_mio_inuser()/__pcilg_mio_inuser() Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring" Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()" Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()" Revert "scsi: lpfc: SLI path split: Refactor SCSI paths" Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4" Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq" mmc: block: Remove error check of hw_reset on reset ethtool: eeprom: fix null-deref on genl_info in dump net: ieee802154: fix error return code in dgram_bind() media: v4l2: Fix v4l2_i2c_subdev_set_name function documentation media: atomisp: prevent integer overflow in sh_css_set_black_frame() drm/msm: Fix return type of mdp4_lvds_connector_mode_valid KVM: selftests: Fix number of pages for memory slot in memslot_modification_stress_test ASoC: qcom: lpass-cpu: mark HDMI TX registers as volatile perf: Fix missing SIGTRAPs sched/core: Fix comparison in sched_group_cookie_match() arc: iounmap() arg is volatile mtd: rawnand: intel: Add missing of_node_put() in ebu_nand_probe() ASoC: qcom: lpass-cpu: Mark HDMI TX parity register as volatile ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() perf/x86/intel/lbr: Use setup_clear_cpu_cap() instead of
[Kernel-packages] [Bug 1997993] Re: Focal update: v5.4.221 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997993 Title: Focal update: v5.4.221 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.4.221 upstream stable release from git://git.kernel.org/ xfs: open code insert range extent split helper xfs: rework insert range into an atomic operation xfs: rework collapse range into an atomic operation xfs: add a function to deal with corrupt buffers post-verifiers xfs: xfs_buf_corruption_error should take __this_address xfs: fix buffer corruption reporting when xfs_dir3_free_header_check fails xfs: check owner of dir3 data blocks xfs: check owner of dir3 blocks xfs: Use scnprintf() for avoiding potential buffer overflow xfs: remove the xfs_disk_dquot_t and xfs_dquot_t xfs: remove the xfs_dq_logitem_t typedef xfs: remove the xfs_qoff_logitem_t typedef xfs: Replace function declaration by actual definition xfs: factor out quotaoff intent AIL removal and memory free xfs: fix unmount hang and memory leak on shutdown during quotaoff xfs: preserve default grace interval during quotacheck xfs: Lower CIL flush limit for large logs xfs: Throttle commits on delayed background CIL push xfs: factor common AIL item deletion code xfs: tail updates only need to occur when LSN changes xfs: don't write a corrupt unmount record to force summary counter recalc xfs: trylock underlying buffer on dquot flush xfs: factor out a new xfs_log_force_inode helper xfs: reflink should force the log out if mounted with wsync xfs: move inode flush to the sync workqueue xfs: fix use-after-free on CIL context on shutdown ocfs2: clear dinode links count in case of error ocfs2: fix BUG when iput after ocfs2_mknod fails x86/microcode/AMD: Apply the patch early on every logical thread hwmon/coretemp: Handle large core ID value ata: ahci-imx: Fix MODULE_ALIAS ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS KVM: arm64: vgic: Fix exit condition in scan_its_table() media: venus: dec: Handle the case where find_format fails UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1742098 arm64: errata: Remove AES hwcap for COMPAT tasks r8152: add PID for the Lenovo OneLink+ Dock btrfs: fix processing of delayed data refs during backref walking btrfs: fix processing of delayed tree block refs during backref walking ACPI: extlog: Handle multiple records tipc: Fix recognition of trial period tipc: fix an information leak in tipc_topsrv_kern_subscr HID: magicmouse: Do not set BTN_MOUSE on double report net/atm: fix proc_mpc_write incorrect return value net: phy: dp83867: Extend RX strap quirk for SGMII mode net: sched: cake: fix null pointer access issue when cake_init() fails net: hns: fix possible memory leak in hnae_ae_register() iommu/vt-d: Clean up si_domain in the init_dmars() error path arm64: topology: move store_cpu_topology() to shared code riscv: topology: fix default topology reporting ACPI: video: Force backlight native for more TongFang devices Makefile.debug: re-enable debug info for .S files hv_netvsc: Fix race between VF offering and VF association message from host mm: /proc/pid/smaps_rollup: fix no vma's null-deref Linux 5.4.221 UBUNTU: Upstream stable to v5.4.221 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992714] Re: [SRU] SoF for RPL platform support
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998118] [NEW] connecting power freezes computer
Public bug reported: the computer has a usb-c PD port, it also do display, when connectring PD charger it freezes and dont responds to anithing, it must be forced to shut down, screen remains on, mouse not moving, and not responding to anything ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: comi 1677 F wireplumber /dev/snd/seq:comi 1674 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 12:23:37 2022 InstallationDate: Installed on 2022-11-27 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd CoreBook X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CFL_CM131_U43E_V1.0.8 dmi.board.asset.tag: Default string dmi.board.name: CM131 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 23.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCFL_CM131_U43E_V1.0.8:bd05/21/2021:br5.13:efr23.4:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBookX:pvrDefaultstring:rvnDefaultstring:rnCM131:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: CoreBook X dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1998118 Title: connecting power freezes computer Status in linux package in Ubuntu: New Bug description: the computer has a usb-c PD port, it also do display, when connectring PD charger it freezes and dont responds to anithing, it must be forced to shut down, screen remains on, mouse not moving, and not responding to anything ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: comi 1677 F wireplumber /dev/snd/seq:comi 1674 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 12:23:37 2022 InstallationDate: Installed on 2022-11-27 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd CoreBook X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CFL_CM131_U43E_V1.0.8 dmi.board.asset.tag: Default string dmi.board.name: CM131 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string
[Kernel-packages] [Bug 1996740] Re: 5.15.0-53-generic no longer boots
ok, I see. I"ll try to figure out how to report the same issue for the AMD release. -- 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/1996740 Title: 5.15.0-53-generic no longer boots Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] "UBUNTU: SAUCE: Revert "drm/amd/display: Add helper for blanking all dp displays" caused AMD Navi10 GFX to panic at boot. [Fix] Backport the revised version of "drm/amd/display: Add helper for blanking all dp displays". [Test] Users confirmed the issue went away with this fix. We also verified the original issue we fixed didn't reappear. [Where problems could occur] We didn't test all the combination of dce110/dcn10/dcn30/dcn31, so many cases are untested, hence the potential risk is there. == Original Bug Report == Running Ubuntu 22.04.1 Jammy. After kernel update from 5.15.0-52-generic to 5.15.0-53-generic the system no longer fully boots. After the normal splash screen the screen goes black and the computer is not reachable on the network. Changing to another TTY does not work. New kernel version: 5.15.0-53.59 I will attach the output of journalctl -b -1, please let me know what other info you need. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johan 2549 F pulseaudio /dev/snd/controlC0: johan 2549 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-12-01 (714 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. wgnfs no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C52 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=b2063474-5791-4f32-aa6d-88a478ae3120 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-11-16 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/23/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 3.G0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M-A PRO MAX (MS-7C52) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr3.G0:bd07/23/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450M-APROMAX(MS-7C52):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C52 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996740/+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 1998115] [NEW] Fix iosm: WWAN cannot detect insert SIM card (DW5823e) Edit
Public bug reported: [Impact] [Fix] [Test Case] [Where problems could occur] Low ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** No longer affects: linux (Ubuntu Lunar) ** No longer affects: linux-oem-6.0 (Ubuntu Lunar) -- 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/1998115 Title: Fix iosm: WWAN cannot detect insert SIM card (DW5823e) Edit Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] [Fix] [Test Case] [Where problems could occur] Low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998115/+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
Re: [Kernel-packages] [Bug 1996053] No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works)
Unfortunately I did a lot of trial and error attempts to get my GUI back. I installed linux-image-unsigned-5.19.0-21-generic, however, with same bad result. During the fight I lost the image 5.15.0. Another thing I did was upgrading TrueNas from 12.1 to 13.0-U3.1. This process clears all the ZFS caches. Whether this has any impact upon a VM, I don't know. So I did end up with the images 5.19.0-21 and 5.19.0.23 and they both boot ok. Since I have been confused and inconsequent in my testing, I think you should mark the bug as an user error. I am sorry for making this noise. > On 28 Nov 2022, at 10.59, Daniel van Vugt <1996...@bugs.launchpad.net> wrote: > > Also while using kernel 5.15 please run: > > journalctl -b0 > oldkernel.txt > lspci -kv > lspci.txt > > and attach the resulting text files here. > > > ** Changed in: linux (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1996053 > > Title: > No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works) > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I am running Ubuntu 22.04.1 on a VM under TrueNas. > After upgrade to 22.10 I just ends up with a black screen, however, > everything else like mail, dns, dhcp and apache2 works well. > > I am using x11vnc and in the 'journalctl -b' it seems that a display > cannot be achieved. > > In the boot menu I have > *Ubuntu, with Linux version 5.19.0-23-generic >Ubuntu, with Linux version 5.15.0-52-generic > > However, if I am booting 5.15.0-52 everything is OK. > - > lsb_release -rd > Description: Ubuntu 22.10 > Release: 22.10 > - > cat /proc/version_signature > Ubuntu 5.19.0-23.24-generic 5.19.7 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996053/+subscriptions > -- 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/1996053 Title: No GUI after upgrade from 22.04.1 to 22.10 (but kernel 5.15 works) Status in linux package in Ubuntu: Incomplete Bug description: I am running Ubuntu 22.04.1 on a VM under TrueNas. After upgrade to 22.10 I just ends up with a black screen, however, everything else like mail, dns, dhcp and apache2 works well. I am using x11vnc and in the 'journalctl -b' it seems that a display cannot be achieved. In the boot menu I have *Ubuntu, with Linux version 5.19.0-23-generic Ubuntu, with Linux version 5.15.0-52-generic However, if I am booting 5.15.0-52 everything is OK. - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - cat /proc/version_signature Ubuntu 5.19.0-23.24-generic 5.19.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996053/+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 1998115] Re: Fix iosm: WWAN cannot detect insert SIM card (DW5823e) Edit
** Description changed: [Impact] - + WWAN(DW5823e) can't build the connection successfully. [Fix] + With INTEL_IOMMU disable config or by forcing intel_iommu=off from + grub some of the features of IOSM driver like browsing, flashing & + coredump collection is not working. + + When driver calls DMA API - dma_map_single() for tx transfers. It is + resulting in dma mapping error. + + Set the device DMA addressing capabilities using dma_set_mask() and + remove the INTEL_IOMMU dependency in kconfig so that driver follows + the platform config either INTEL_IOMMU enable or disable. + + Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY + CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] + 1. boot up with kernel applied the FIX. + 2. check the status of wwan by "mmcli -m 0" + Status| unlock retries: sim-pin (3) +| state: ^[32mconnected^[0m +|power state: on +|access tech: lte +| signal quality: 45% (recent) + -- + 3GPP | imei: ## +| enabled locks: sim, fixed-dialing +|operator id: 46692 +| operator name: Chunghwa Telecom +| registration: home +| packet service state: attached +|pco: +| 0: (complete) [Where problems could occur] - Low + remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. ** Summary changed: - Fix iosm: WWAN cannot detect insert SIM card (DW5823e) Edit + Fix iosm: WWAN cannot detect insert SIM card (DW5823e) ** Summary changed: - Fix iosm: WWAN cannot detect insert SIM card (DW5823e) + Fix iosm: WWAN cannot build the connection (DW5823e) ** Tags added: oem-priority originate-from-1996162 somerville ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Assignee: koba (kobako) => (unassigned) -- 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/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1998103 Title: Intel 8087:07dc Bluetooth highly unreliable Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've been experiencing all sorts of strange behaviour since upgrading to linux mint 21. * adapter failing to power on after suspend/resume * random errors littering dmesg * now it went ballistic and caused my UI to freeze, not from anything I could identify that I did. inxi -EbA System: Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64 Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa Machine: Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0 serial: Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015 CPU: Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292 min/max: 800/3500 Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel Device-2: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Sound Server-1: ALSA v: k5.15.0-53-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: 30:3A:64:EA:9C:EA attached kernel logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998118] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998118 Title: connecting power freezes computer Status in linux package in Ubuntu: Confirmed Bug description: the computer has a usb-c PD port, it also do display, when connectring PD charger it freezes and dont responds to anithing, it must be forced to shut down, screen remains on, mouse not moving, and not responding to anything ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: comi 1677 F wireplumber /dev/snd/seq:comi 1674 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 28 12:23:37 2022 InstallationDate: Installed on 2022-11-27 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:6366 Microdia Webcam Vitade AF Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd CoreBook X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CFL_CM131_U43E_V1.0.8 dmi.board.asset.tag: Default string dmi.board.name: CM131 dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 23.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCFL_CM131_U43E_V1.0.8:bd05/21/2021:br5.13:efr23.4:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBookX:pvrDefaultstring:rvnDefaultstring:rnCM131:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: CoreBook X dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998118/+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 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- 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/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1998106] Re: Fix AMD-PState driver for Genoa CPU
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => 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/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Status in linux-oem-5.17 source package in Focal: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+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 1639924] Re: Kernel livepatch support for for s390x
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kpatch (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: In Progress Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Confirmed Status in linux source package in Jammy: Confirmed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Confirmed Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in symbol conversion 3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms() 79f45d1b0a create-diff-object:
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: In Progress Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Confirmed Status in linux source package in Jammy: Confirmed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Confirmed Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in symbol conversion 3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms() 79f45d1b0a create-diff-object:
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kpatch (Ubuntu Kinetic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: In Progress Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Confirmed Status in linux source package in Jammy: Confirmed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Confirmed Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in symbol conversion 3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms() 79f45d1b0a
