[Kernel-packages] [Bug 1990447] 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 1990447 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/1990447 Title: New linux makes wifi driver unstable again Status in linux package in Ubuntu: Incomplete Bug description: I'm new to this, sorry if I get it wrong. I'm using Mint, but the update manager links to here as kernels aren't changed by the Mint team. I'm using the rtl8821ce wifi driver which previously had trouble loading again after waking up from sleep. Not every time though and without any pattern. The recent kernel, 5.15.0.46.49~20.04.16 had fixed this problem, which had gone on for over a year before that. Just now I updated again to linux_5.15.0-48.54~20.04.18 and the problem is back. Waking up, sometimes the wifi doesn't work, NetworkManager icon says it's connected but nothing works. I have found that suspending and waking back up, then sudo modprobe -r rtl8821ce, sudo modprobe rtl8821ce will get it working again but that's the only way without shutting down. cat /proc/version_signature Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Hewlett-Packard Company Raven/Raven2 Root Complex [103c:87b7] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee0 Data: 0022 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <64us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (ok), Width x2 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible+ RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt+, EETLPPrefix+, MaxEETLPPrefixes 1 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd+ AtomicOpsCap: Routing- 32bi
[Kernel-packages] [Bug 1990447] [NEW] New linux makes wifi driver unstable again
Public bug reported: I'm new to this, sorry if I get it wrong. I'm using Mint, but the update manager links to here as kernels aren't changed by the Mint team. I'm using the rtl8821ce wifi driver which previously had trouble loading again after waking up from sleep. Not every time though and without any pattern. The recent kernel, 5.15.0.46.49~20.04.16 had fixed this problem, which had gone on for over a year before that. Just now I updated again to linux_5.15.0-48.54~20.04.18 and the problem is back. Waking up, sometimes the wifi doesn't work, NetworkManager icon says it's connected but nothing works. I have found that suspending and waking back up, then sudo modprobe -r rtl8821ce, sudo modprobe rtl8821ce will get it working again but that's the only way without shutting down. cat /proc/version_signature Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53 sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: Hewlett-Packard Company Raven/Raven2 Root Complex [103c:87b7] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee0 Data: 0022 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 8GT/s, Width x2, ASPM L1, Exit Latency L1 <64us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (ok), Width x2 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible+ RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible+ RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, NROPrPrP-, LTR+ 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt+, EETLPPrefix+, MaxEETLPPrefixes 1 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS-, LN System CLS Not Supported, TPHComp-, ExtTPHComp-, ARIFwd+ AtomicOpsCap: Routing- 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- AtomicOpsCtl: ReqEn- EgressBlck- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:1234] Capabilities: [c8] HyperTransport: MSI
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
Dear Jureg. I tested the linux-image-5.15.0-1015-raspi kernel from jammy-proposed and confirms it fixed the issue. (Version: 5.15.0-1015.17, which is based on Ubuntu kernel 5.15.0-48.54 according to changelog). Thank you very much. -- 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/1981390 Title: Mass Storage Gadget driver truncates device >2TB Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] I tried to use f_mass_storage to expose a 16TB hard drive attached to Raspberry Pi to another computer. On the remote computer the recognised drive has incorrect capacity and the data is truncated. After some debugging I noted the problem is caused by a bug in the read capacity function of f_mass_storage in kernel version prior to 5.15, which had already been fixed upstream in mainline kernel since v5.16 https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/ I tried the kernel from https://github.com/raspberrypi/linux version rpi-5.16.y and confirmed that the problem is fixed at v5.16. I wonder if the fix can be backported to the Ubuntu kernel. Thank you very much! Current kernel package version: linux-raspi (5.15.0-1011.13) jammy Hardware: Raspberry Pi 4B [Fix] Backport commit bedbac5f66bf ("usb: gadget: storage: add support for media larger than 2T") [Test case] See above. [Where problems could occur] Modifications are limited to the USB gadget mass storage driver, so problems should only be seen on a client that uses this driver to expose a USB drive to an attached USB host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+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 1786013] Autopkgtest regression report (linux-meta-snapdragon/4.15.0.1138.139)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1138.139) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-snapdragon [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1990434] [NEW] Bionic update: upstream stable patchset 2022-09-21
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 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 sysctl_tcp_adv_win_scale. tcp: Fix a data-race around sysctl_tcp_frto. tcp: Fix a data-race around sysctl_tcp_nometrics_save. scsi: ufs: host: Hold reference returned by of_parse_phandle() tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. net: ping6: Fix memleak in ipv6_renew_options(). igmp: Fix data-races around sysctl_igmp_qrv. net: sungem_phy: Add of_node_put() for reference returned by of_get_parent() tcp: Fix a data-race around sysctl_tcp_min_tso_segs. tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen. tcp: Fix a data-race around sysctl_tcp_autocorking. tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit. Documentation: fix sctp_wmem in ip-sysctl.rst i40e: Fix interface init with MSI interrupts (no MSI-X) sctp: fix sleep in atomic context bug in timer handlers perf symbol: Correct address for bss symbols scsi: core: Fix race between handling STS_RESOURCE and completion ACPI: video: Shortening quirk list by identifying Clevo by board_name only UBUNTU: Upstream stable to v4.19.255 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) I
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
I tested latest daily build https://cdimage.ubuntu.com/jammy/daily-live/20220920/jammy-desktop-amd64.iso and out of memory stil exist. I hope someone can provide an iso for download with a livesystem and install for jammy with changed compression. Ubuntu 21.10 (out of support) and Fedora 36 works fine. -- 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: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed 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 really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320 * Test source code: https://github.com/os369510/grub2/
[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1017.18 --- linux-oem-5.17 (5.17.0-1017.18) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1017.18 -proposed tracker (LP: #198) * [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD (LP: #1988721) - drm/amd/display: Refactor fixed VS logic for non-transparent mode * IWLMEI may cause device down at resuming from s2idle (LP: #1987312) - [Config] Disable IWLMEI * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 [ Ubuntu: 5.17.0-9.9~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-9.9~22.04.8 -proposed tracker (LP: #1987779) * CVE-2022-36946 - netfilter: nf_queue: do not allow packet truncation below transport header offset * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() -- Timo Aaltonen Thu, 08 Sep 2022 16:51:33 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36946 -- 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/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in OEM Priority Project: New Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1017.18 --- linux-oem-5.17 (5.17.0-1017.18) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1017.18 -proposed tracker (LP: #198) * [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD (LP: #1988721) - drm/amd/display: Refactor fixed VS logic for non-transparent mode * IWLMEI may cause device down at resuming from s2idle (LP: #1987312) - [Config] Disable IWLMEI * GPIO character device v1 API not enabled in kernel (LP: #1953613) - [Config] Enable CONFIG_GPIO_CDEV_V1 [ Ubuntu: 5.17.0-9.9~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-9.9~22.04.8 -proposed tracker (LP: #1987779) * CVE-2022-36946 - netfilter: nf_queue: do not allow packet truncation below transport header offset * CVE-2021-33655 - fbcon: Disallow setting font bigger than screen size - fbcon: Prevent that screen size is smaller than font size - fbmem: Check virtual screen sizes in fb_set_var() -- Timo Aaltonen Thu, 08 Sep 2022 16:51:33 +0300 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-33655 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-36946 -- 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/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1990425] 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 1990425 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/1990425 Title: Keyboard inoperative on Asus Vivobook S5402ZA Status in linux package in Ubuntu: Incomplete Bug description: The builtin keyboard on the Asus S5402ZA doesn't work with the 5.15 kernel in Jammy Jellyfish. Adapting the patch from https://bugzilla.kernel.org/show_bug.cgi?id=216158 and applying to the 5.15 kernel allows the keyboard to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990425/+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 1990425] [NEW] Keyboard inoperative on Asus Vivobook S5402ZA
Public bug reported: The builtin keyboard on the Asus S5402ZA doesn't work with the 5.15 kernel in Jammy Jellyfish. Adapting the patch from https://bugzilla.kernel.org/show_bug.cgi?id=216158 and applying to the 5.15 kernel allows the keyboard to work. ** 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/1990425 Title: Keyboard inoperative on Asus Vivobook S5402ZA Status in linux package in Ubuntu: New Bug description: The builtin keyboard on the Asus S5402ZA doesn't work with the 5.15 kernel in Jammy Jellyfish. Adapting the patch from https://bugzilla.kernel.org/show_bug.cgi?id=216158 and applying to the 5.15 kernel allows the keyboard to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990425/+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 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
This bug is awaiting verification that the linux-ibm/5.15.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+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 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-ibm/5.15.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1983640 Title: refactoring of overlayfs fix to properly support shiftfs Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-hwe-5.17 source package in Kinetic: Invalid Bug description: [Impact] Starting with 5.13 we've incorrectly dropped the following sauce patch: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files This patch is required to use overlayfs on top of shiftfs and without this patch we may break containers that rely on shiftfs (using zfs/ceph as storage pool w/ shiftfs enabled). However, we made this patch dependent on AUFS, starting with Jammy we're not enabling AUFS anymore, so this fix becomes a no-op. So we need to re-introduce this fix with a bit of refactoring to not depend on AUFS. [Test case] The following script can be used to trigger the issue: #!/bin/bash cat > test.py << EOF import sys f = open("/proc/self/maps") for l in f.readlines(): if "python" not in l: continue print(l) s = l.split() start, end = s[0].split("-") fname = s[-1] print(start, end, fname) break else: sys.exit(1) test_file1 = open(fname) test_file2 = open("/proc/self/map_files/%s-%s" % (start, end)) fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read() fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read() if fdinfo1 != fdinfo2: print("FAIL") print(test_file1) print(fdinfo1) print(test_file2) print(fdinfo2) sys.exit(1) print("PASS") EOF sudo docker run -it --privileged --rm -v `pwd`:/mnt python python /mnt/test.py [Fix] Import the right pieces from AUFS to properly support the fix and get rid of the AUFS dependency across all our kernels and re-apply the overlayfs fix without the AUFS dependency. [Regression potential] This patch is touching overlayfs, so we may see potential regressions in overlayfs, especially when containers are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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 1986798] Re: Remove unused variable from i915 psr
This bug is awaiting verification that the linux-ibm/5.15.0-1014.16 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1986798 Title: Remove unused variable from i915 psr Status in linux package in Ubuntu: Won't Fix Status in linux source package in Jammy: Fix Released Bug description: [Impact] Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU: SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker") [Fix] The variable is unused, remove it. [Test] Compiler no longer warns about it. [Where problems could occur] Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+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 1990417] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617913/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617912/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617911/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617910/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617907/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617908/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617909/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617906/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617905/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617902/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617897/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617904/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617900/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617901/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617903/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617898/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617899/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] Re: Bluetooth stoped working on Lenovo Yoga Slim 7
apport information ** Tags added: apport-collected una ** Description changed: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.24 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: pavel 2194 F pulseaudio + /dev/snd/controlC1: pavel 2194 F pulseaudio + /dev/snd/controlC0: pavel 2194 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.3 + EcryptfsInUse: Yes + InstallationDate: Installed on 2021-09-18 (367 days ago) + InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 + MachineType: LENOVO 82A2 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash + ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-43-generic N/A + linux-backports-modules-5.15.0-43-generic N/A + linux-firmware 1.187.33 + Tags: una + Uname: Linux 5.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/18/2020 + dmi.bios.release: 1.36 + dmi.bios.vendor: LENOVO + dmi.bios.version: DMCN36WW + dmi.board.asset.tag: ��� + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40709 WIN + dmi.chassis.asset.tag: ��� + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Yoga Slim 7 14ARE05 + dmi.ec.firmware.release: 1.28 + dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: + dmi.product.family: Yoga Slim 7 14ARE05 + dmi.product.name: 82A2 + dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 + dmi.product.version: Yoga Slim 7 14ARE05 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617895/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.
[Kernel-packages] [Bug 1990417] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1990417/+attachment/5617896/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990184] Re: Azure: Enable vPCI multi-MSI interrupts
** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1990184 Title: Azure: Enable vPCI multi-MSI interrupts Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] This is a 2nd attempt with this patch set. The first attempt [1] caused a regression. The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie that supports multiple MSI interrupts (Note: MSI-X has been working fine). Recently Jeffrey Hugo made 4 patches to the vPCI driver so multiple-MSI can work now. Please consider picking up the 4 patches into the linux-azure kernels for Ubuntu LTS 18.04, 20.04 and 22.04: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08e61e861a0e47e5e1a3fb78406afd6b0cea6b6d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=455880dfe292a2bdd3b4ad6a107299fce610e64b https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b8ecc5bfbd4e77de1b2fd5c1dd3c655f1f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a2bad844a67b1c7740bda63e87453baf63c3a7f7 [1] https://bugs.launchpad.net/bugs/1981577 [Test Plan] Microsoft tested: " I tested the kernel and it worked as expected, i.e. we still have the multi-MSI capability and I no longer see the soft lockup issue with fio + NVMe + the L64s_v2 VM size." [Where things could go wrong] vPCI devices may no get interrupts [Other Info] SF: #00339521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1990184/+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 1990399] Re: sleep and hibernate not working
I found a solution to sleep and hibernate problem. The nvidia GPR drivers were causing the problem. I simply upgraded to a newer one. But I am still getting system crashes. -- 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/1990399 Title: sleep and hibernate not working Status in linux package in Ubuntu: Confirmed Bug description: sleep and hibernate not working Also I sometimes see "system crash" messages. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: takshil 25971 F pulseaudio /dev/snd/controlC0: takshil 25971 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 21 19:54:58 2022 InstallationDate: Installed on 2022-09-19 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=e541b293-9933-4b51-bced-82eeb2424484 ro splash iommu=soft vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2403 dmi.board.asset.tag: Default string dmi.board.name: ProArt B550-CREATOR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd06/16/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProArtB550-CREATOR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990399/+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 1990420] [NEW] package libnvidia-compute-390 390.154-0ubuntu0.22.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es
Public bug reported: The graphic controllers sometimes have failures ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-390 390.154-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 20 21:03:16 2022 ErrorMessage: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:amd64 InstallationDate: Installed on 2022-05-11 (133 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.154-0ubuntu0.22.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1990420 Title: package libnvidia-compute-390 390.154-0ubuntu0.22.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: The graphic controllers sometimes have failures ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-390 390.154-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 20 21:03:16 2022 ErrorMessage: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:amd64 InstallationDate: Installed on 2022-05-11 (133 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.154-0ubuntu0.22.04.1 failed to install/upgrade: intentando sobreescribir el compartido `/etc/OpenCL/vendors/nvidia.icd', que es distinto de otras instancias del paquetes libnvidia-compute-390:amd64 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-390/+bug/1990420/+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 1990323] Re: amdgpu driver hangs periodically, causes display to permanently crash
** Description changed: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP: 0002 R08: R09: 0002 R10: 001a R11: 0246 R12: 7f06f4150441 R13: 556c9aa05fb0 R14: 556c9ab40460 R15: 556c9ab35150 It's even visible on screen before the splash screen appears. I don't remember seeing this before the motherboard/CPU upgrade. I haven't tried to trigger the issue from a bootable
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988711 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: New Status in linux source package in Kinetic: Confirmed Bug description: [IMPACT/Justification] [FIX] Please integrate the latest set of bug fix patches accepted in mkp/scsi 5.20/scsi-staging b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5 b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into lpfc_sli_prep_abort_xri() ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved configuration ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in queuecommand after VMID 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in XMIT_ELS_RSP64_CX iocb f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in lpfc_nvme_cancel_iocb() 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for aborted NVMe cmds 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after starget_to_rport() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path refactoring 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in lpfc_ct_reject_event() a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol independent ed913cf4a533 scsi: lpfc: Commonize VMID code location fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3 a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for NVMe I/O e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric parameters dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link() 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in rscn_recovery_check() 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event() ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() 775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call 92bd903da12b scsi: lpfc: Fix additional reference counting in lpfc_bsg_rport_els() db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line 646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() 3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in lpfc_sli_prep_wqe() a346f28ad231 scsi: lpfc: Remove unneeded variable 66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches 4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2 fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure 1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post RSCN completion 6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in Fabric topology 6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports c364c453d30a scsi: lpfc: Revise FDMI reporting of supported port speed for trunk groups d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled 5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats 39a1a86b9da2 scsi: lpfc: Move MI module param
[Kernel-packages] [Bug 1990009] Re: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH
** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1990009 Title: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The actual kernel used on AKS arm64 (i.e. 5.4.1089) suffers from a known problem [1]. As a consequence, opensnoop does not display PATH: # Run the following from Canonical:UbuntuServer:18_04-daily-lts-arm64:18.04.202208290 $ uname -a Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ git clone --recurse-submodules https://github.com/iovisor/bcc Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ sudo sh -c 'apt update && apt install -qy clang-10 llvm-10 make gcc pkg-config libelf-dev libz-dev' ... $ cd bcc/libbpf-tools $ CLANG=clang-10 LLVM_STRIP=llvm-strip-10 make -j opensnoop ... BINARY opensnoop $ sudo ./opensnoop PID COMM FD ERR PATH 1672 python3 3 0 9746 opensnoop 20 0 1672 python3 3 0 1672 python3 3 0 1672 python3 -1 2 1672 python3 3 0 1 systemd 18 0 1672 python3 6 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 ^C As you can see, nothing is printed for the PATH while normal behavior prints the path of the opened file: $ uname -a Linux pwmachine 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ sudo ./opensnoop PID COMM FD ERR PATH 2704 systemd 23 0 virtual 2704 systemd 22 0 misc 2704 systemd 23 0 fuse 2704 systemd 22 0 /sys/devices/virtual/misc/fuse/uevent 2704 systemd 22 0 /run/udev/data/c10:229 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status ^C This bug was fixed in upstream patch [2] Sadly, this patch was not back ported, so it is not present in stable kernels. [Test plan] Follow the above instructions [Where things could go wrong] Unknown [Other Info] Original RFC at https://lists.ubuntu.com/archives/kernel- team/2022-September/133038.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1990009/+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 1990323] Re: amdgpu driver hangs periodically, causes display to permanently crash
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Confirmed Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP: 0002 R08: R09: 000
[Kernel-packages] [Bug 1990323] Re: amdgpu driver hangs periodically, causes display to permanently crash
apport information ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990323/+attachment/5617866/+files/CurrentDmesg.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990323/+attachment/5617872/+files/PaInfo.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990323/+attachment/5617878/+files/PulseList.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990323/+attachment/5617864/+files/AlsaInfo.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990323/+attachment/5617880/+files/WifiSyslog.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990323/+attachment/5617884/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Confirmed Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_s
[Kernel-packages] [Bug 1990167] Re: cma alloc failure in large 5.15 arm instances
** Changed in: linux-aws (Ubuntu Kinetic) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1990167 Title: cma alloc failure in large 5.15 arm instances Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Invalid Bug description: When launching large arm64 instances on the focal or jammy ami, cma allocation errors appear in the dmesg out: [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 As far as I can tell, this does not impact instance launch in a meaningful way, but I am unsure of the other implications of this. I was able to confirm that these messages are only present in 5.15, as they do not show up in the bionic image, and rolling back focal to linux-aws 5.4 avoids them as well. This was present in at least 2 instance types and only appears to pop up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does) This could be as simple as just disabling CMA in the linux-aws pkg, as it appears this is already the case in linux-azure(LP: #1949770). Attaching dmesg out to the report. # Replication + Launch a large arm64 instance (c6gn.16xlarge) + Observe the messages in kern.log / dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+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 1990323] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617881/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 000
[Kernel-packages] [Bug 1990167] Re: cma alloc failure in large 5.15 arm instances
** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1990167 Title: cma alloc failure in large 5.15 arm instances Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: In Progress Bug description: When launching large arm64 instances on the focal or jammy ami, cma allocation errors appear in the dmesg out: [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 As far as I can tell, this does not impact instance launch in a meaningful way, but I am unsure of the other implications of this. I was able to confirm that these messages are only present in 5.15, as they do not show up in the bionic image, and rolling back focal to linux-aws 5.4 avoids them as well. This was present in at least 2 instance types and only appears to pop up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does) This could be as simple as just disabling CMA in the linux-aws pkg, as it appears this is already the case in linux-azure(LP: #1949770). Attaching dmesg out to the report. # Replication + Launch a large arm64 instance (c6gn.16xlarge) + Observe the messages in kern.log / dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+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 1990323] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617880/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 000
[Kernel-packages] [Bug 1990323] PulseList.txt
** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617878/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP: 0
[Kernel-packages] [Bug 1990323] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617879/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI:
[Kernel-packages] [Bug 1990323] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617871/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 0
[Kernel-packages] [Bug 1990323] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617870/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 0
[Kernel-packages] [Bug 1990323] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617877/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 0
[Kernel-packages] [Bug 1990323] PaInfo.txt
** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617872/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP:
[Kernel-packages] [Bug 1990323] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617869/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 00
[Kernel-packages] [Bug 1990323] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617876/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441
[Kernel-packages] [Bug 1990323] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617873/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 0
[Kernel-packages] [Bug 1990323] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617875/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 0
[Kernel-packages] [Bug 1990323] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617874/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f
[Kernel-packages] [Bug 1990323] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617867/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 00
[Kernel-packages] [Bug 1990323] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617868/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 000
[Kernel-packages] [Bug 1990323] CurrentDmesg.txt
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617866/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a
[Kernel-packages] [Bug 1990323] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1990323/+attachment/5617865/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a
[Kernel-packages] [Bug 1990323] Re: amdgpu driver hangs periodically, causes display to permanently crash
** Tags added: apport-collected ** Description changed: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP: 0002 R08: R09: 0002 R10: 001a R11: 0246 R12: 7f06f4150441 R13: 556c9aa05fb0 R14: 556c9ab40460 R15: 556c9ab35150 It's even visible on screen before the splash screen appears. I don't remember seeing this before the motherboard/CPU upgrade. - I haven't tried to
[Kernel-packages] [Bug 1990417] 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 1990417 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/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1990417] [NEW] Bluetooth stoped working on Lenovo Yoga Slim 7
Public bug reported: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 5.15.0-48 ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1990417/+attachment/5617862/+files/lspci-vnvn.log -- 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/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+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 1988635] Re: boot failure on ryzen 9
Closed as fix (5.15.0-48-generic kernel) given. -- 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/1988635 Title: boot failure on ryzen 9 Status in linux package in Ubuntu: Fix Released Bug description: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd01/16/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C35:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570UNIFY(MS-7C35):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C35 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.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/1988635/+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 1988635] Re: boot failure on ryzen 9
Testing a clone of this Xubuntu instance on an Intel CPU (Celeron G1620 and Core i5 8265U) showed that the problem does not occur there. So the 5.15.0-47.51-generic kernel booting problem only occurs on an AMD CPU (Ryzen 9 3900XT). To determine whether the problem is in the kernel itself or in the (my?) userland I tested this kernel with an other userland (a slackware-based live CD): the problem does not occur there. So the problem is likely to be in the (my?) userland. Today I installed the 5.15.0-48-generic kernel. And lo and behold: the problem does not occur on my AMD box (Ryzen 9 3900XT) nor on my Intel laptop (Core i5 8265U)! So the problem was something in the kernel responding badly to something in the (my?) userland. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1988635 Title: boot failure on ryzen 9 Status in linux package in Ubuntu: Fix Released Bug description: Xubuntu 22.04.1: When booting the 5.15.0-47.51 generic kernel on my AMD Ryzen 9 3900XT I see the following messages: -- [FAILED] Failed to mount /C. -- See 'systemctl status C.mount' for details. -- [DEPEND] Dependency failed for Local File Systems. -- . -- You are in emergency mode. ---. NOTE THAT I HAD TO REVERT TO KERNEL 5.15.0-46.49 TO REPORT THIS PROBLEM. A clone of the installation at hand runs without problems on an Intel Celeron G1620 box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: burdi012933 F pulseaudio /dev/snd/controlC0: burdi012933 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Sep 3 15:45:02 2022 HibernationDevice: RESUME=none IwConfig: lono wireless extensions. enp39s0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C35 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p12 ro pci=noaer RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.30 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MEG X570 UNIFY (MS-7C35) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.30:bd01/16/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C35:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGX570UNIFY(MS-7C35):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C35 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.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/1988635/+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 1990323] 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 1990323 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/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: Incomplete Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_
[Kernel-packages] [Bug 1990323] Re: amdgpu driver hangs periodically, causes display to permanently crash
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990323 Title: amdgpu driver hangs periodically, causes display to permanently crash Status in linux package in Ubuntu: New Bug description: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP: 0002 R08: R09: 0002 R10: 001a
[Kernel-packages] [Bug 1990323] [NEW] amdgpu driver hangs periodically, causes display to permanently crash
You have been subscribed to a public bug: Apologies in advance if this isn't the right place to file this bug. Please let me know if I should report this elsewhere or if there's any other info I can add. What I suspect is an amdgpu driver issue has been causing display issues and machine crashes. Once the issue starts, the display won't come back from being blank, and turning the machine off takes five minutes or longer. Additionally, executing `sensors` hangs on reading data from the gpu and can even cause 100% CPU utilization for multiple minutes. I believe this significant delays to other system calls, as the entire machine will start to behave sluggishly in spurts where every program hangs and then many things happen all at once. I can't reliably trigger the issue, although repeatedly reading `sensors` in a loop seems to be one method that eventually works. The main symptom other than the behavior described above is a cycle of messages in the journal of the form kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 145 ret is 0 kernel: amdgpu: last message was failed ret is 0 kernel: amdgpu: failed to send message 146 ret is 0 The messages sent are 145, 146, 5e, and 148. I've had this GPU for 5 years without any of these problems. However, I only recently upgraded from an older Intel CPU to a Ryzen 5600 and a ASRock B550m Pro4. I have no idea if the issues are related to the upgrade or how they could be. Some misc info. Distro: Ubuntu 22.04.1 LTS x86_64 Kernel: 5.15.0-48-generic Graphics card: Radeon R9 380X Motherboard: ASRock B550M Pro4 (P2.30 BIOS) CPU: Ryzen 5600 Desktop: i3 (with picom compositor) I'm attaching the relevant logs from my most recent boot when I was able to boot and use the machine for several hours. I left the machine to blank its screen and when I returned, I was unable to unblank the screen. The only thing I could do was press the power button and leave the machine to shutdown over the course of the next 5 or 10 minutes. The only other thing that is interesting is that on startup I'm seeing the following warning about undefined behavior. UBSAN: shift-out-of-bounds in /build/linux-kQ6jNR/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32 shift exponent 64 is too large for 64-bit type 'long long unsigned int' CPU: 10 PID: 483 Comm: systemd-udevd Not tainted 5.15.0-48-generic #54-Ubuntu Hardware name: To Be Filled By O.E.M. B550M Pro4/B550M Pro4, BIOS P2.30 02/24/2022 Call Trace: show_stack+0x52/0x5c dump_stack_lvl+0x4a/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x49 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef initialize_nocpsch.cold+0x15/0x59 [amdgpu] device_queue_manager_init+0x20b/0x3b0 [amdgpu] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu] loop33: detected capacity change from 0 to 8 amdgpu_device_init.cold+0x25b/0x7db [amdgpu] ? do_pci_enable_device+0xdb/0x110 amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] amdgpu_pci_probe+0x1ce/0x260 [amdgpu] local_pci_probe+0x4b/0x90 pci_device_probe+0x119/0x1f0 really_probe+0x222/0x420 __driver_probe_device+0x119/0x190 driver_probe_device+0x23/0xc0 __driver_attach+0xbd/0x1e0 ? __device_attach_driver+0x120/0x120 bus_for_each_dev+0x7e/0xd0 driver_attach+0x1e/0x30 bus_add_driver+0x148/0x220 driver_register+0x95/0x100 __pci_register_driver+0x68/0x70 amdgpu_init+0x7c/0x1000 [amdgpu] ? 0xc1a4 do_one_initcall+0x48/0x1e0 ? kmem_cache_alloc_trace+0x19e/0x2e0 do_init_module+0x52/0x260 load_module+0xacd/0xbc0 __do_sys_finit_module+0xbf/0x120 __x64_sys_finit_module+0x18/0x20 do_syscall_64+0x5c/0xc0 ? syscall_exit_to_user_mode+0x27/0x50 ? __x64_sys_newfstatat+0x1c/0x30 ? do_syscall_64+0x69/0xc0 ? __x64_sys_mmap+0x33/0x50 ? do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7f06f3fb9a3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7ffc7ce54ae8 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 556c9ab3e3d0 RCX: 7f06f3fb9a3d RDX: RSI: 7f06f4150441 RDI: 001a RBP: 0002 R08: R09: 0002 R10: 001a R11: 0246 R12: 7f06f4150441 R13: 556c9aa05fb0 R14: 556c9ab40460 R15: 556c9ab35150 It's even visible on screen before the splash screen appears. I don't remember seeing this before the motherboard/CPU upgrade. I haven't tried to trigger the issue from a bootable USB, but I can confirm that the warning about undefined behavior is present there as well. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment jammy -- amdgpu dr
[Kernel-packages] [Bug 1989521] Re: Ubuntu 22.04.1 CPU soft lockup occurs repeatedly
Taking a closer look at the timing behind the CPU soft lockup, turns out it happens every 21 minutes, varying between 21min33sec and 21min42sec for the times I've looked at. root@marcus-server:/var/log# cat kern.log | grep watchdog: BUG: soft lockup - (standard input):Sep 21 08:15:52 marcus-server kernel: [25828.061389] watchdog: BUG: soft lockup - CPU#8 stuck for 26s! [kworker/u64:47:2349337] (standard input):Sep 21 08:15:52 marcus-server kernel: [25856.060650] watchdog: BUG: soft lockup - CPU#8 stuck for 52s! [kworker/u64:47:2349337] (standard input):Sep 21 08:37:25 marcus-server kernel: [27118.374205] watchdog: BUG: soft lockup - CPU#10 stuck for 26s! [kworker/u64:110:2400870] (standard input):Sep 21 08:37:25 marcus-server kernel: [27146.372183] watchdog: BUG: soft lockup - CPU#10 stuck for 53s! [kworker/u64:110:2400870] (standard input):Sep 21 08:58:58 marcus-server kernel: [28408.518001] watchdog: BUG: soft lockup - CPU#7 stuck for 26s! [kworker/u64:15:2451705] (standard input):Sep 21 08:58:58 marcus-server kernel: [28436.518146] watchdog: BUG: soft lockup - CPU#7 stuck for 52s! [kworker/u64:15:2451705] (standard input):Sep 21 09:20:32 marcus-server kernel: [29698.735150] watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [kworker/u64:42:2504150] (standard input):Sep 21 09:20:32 marcus-server kernel: [29726.735261] watchdog: BUG: soft lockup - CPU#1 stuck for 52s! [kworker/u64:42:2504150] (standard input):Sep 21 09:42:05 marcus-server kernel: [30988.922555] watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [kworker/u64:17:2571505] (standard input):Sep 21 09:42:05 marcus-server kernel: [31016.924522] watchdog: BUG: soft lockup - CPU#6 stuck for 52s! [kworker/u64:17:2571505] (standard input):Sep 21 10:03:38 marcus-server kernel: [32278.634545] watchdog: BUG: soft lockup - CPU#4 stuck for 26s! [kworker/u64:107:2624962] (standard input):Sep 21 10:03:38 marcus-server kernel: [32306.631958] watchdog: BUG: soft lockup - CPU#4 stuck for 52s! [kworker/u64:107:2624962] (standard input):Sep 21 10:25:11 marcus-server kernel: [33568.843698] watchdog: BUG: soft lockup - CPU#11 stuck for 26s! [kworker/u64:50:2679696] (standard input):Sep 21 10:25:11 marcus-server kernel: [33596.841576] watchdog: BUG: soft lockup - CPU#11 stuck for 52s! [kworker/u64:50:2679696] (standard input):Sep 21 10:46:44 marcus-server kernel: [34859.443424] watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kworker/u64:38:2735876] (standard input):Sep 21 10:46:44 marcus-server kernel: [34887.443661] watchdog: BUG: soft lockup - CPU#2 stuck for 52s! [kworker/u64:38:2735876] (standard input):Sep 21 11:08:17 marcus-server kernel: [36149.446509] watchdog: BUG: soft lockup - CPU#7 stuck for 26s! [kworker/u64:102:2791856] (standard input):Sep 21 11:08:17 marcus-server kernel: [36177.444332] watchdog: BUG: soft lockup - CPU#7 stuck for 52s! [kworker/u64:102:2791856] (standard input):Sep 21 11:29:52 marcus-server kernel: [37438.207072] watchdog: BUG: soft lockup - CPU#0 stuck for 27s! [kworker/u64:99:2846490] (standard input):Sep 21 11:29:52 marcus-server kernel: [37466.204826] watchdog: BUG: soft lockup - CPU#0 stuck for 53s! [kworker/u64:99:2846490] (standard input):Sep 21 11:29:52 marcus-server kernel: [37498.202216] watchdog: BUG: soft lockup - CPU#0 stuck for 82s! [kworker/u64:99:2846490] (standard input):Sep 21 11:51:27 marcus-server kernel: [38731.780341] watchdog: BUG: soft lockup - CPU#7 stuck for 26s! [kworker/u64:27:2899692] (standard input):Sep 21 11:51:27 marcus-server kernel: [38759.780468] watchdog: BUG: soft lockup - CPU#7 stuck for 52s! [kworker/u64:27:2899692] (standard input):Sep 21 12:13:09 marcus-server kernel: [40031.224394] watchdog: BUG: soft lockup - CPU#4 stuck for 26s! [kworker/u64:112:2959948] (standard input):Sep 21 12:13:09 marcus-server kernel: [40059.224543] watchdog: BUG: soft lockup - CPU#4 stuck for 53s! [kworker/u64:112:2959948] (standard input):Sep 21 12:34:45 marcus-server kernel: [41322.879468] watchdog: BUG: soft lockup - CPU#4 stuck for 26s! [kworker/u64:16:3010254] (standard input):Sep 21 12:34:45 marcus-server kernel: [41350.876932] watchdog: BUG: soft lockup - CPU#4 stuck for 53s! [kworker/u64:16:3010254] (standard input):Sep 21 12:56:17 marcus-server kernel: [42613.149821] watchdog: BUG: soft lockup - CPU#9 stuck for 26s! [kworker/u64:110:3059593] (standard input):Sep 21 12:56:17 marcus-server kernel: [42641.147794] watchdog: BUG: soft lockup - CPU#9 stuck for 52s! [kworker/u64:110:3059593] (standard input):Sep 21 13:17:50 marcus-server kernel: [43903.557055] watchdog: BUG: soft lockup - CPU#6 stuck for 26s! [kworker/u64:30:3109619] (standard input):Sep 21 13:17:50 marcus-server kernel: [43931.557265] watchdog: BUG: soft lockup - CPU#6 stuck for 52s! [kworker/u64:30:3109619] (standard input):Sep 21 13:39:24 marcus-server kernel: [45193.795060] watchdog: BUG: soft lockup - CPU#5 stuck for 27s! [kworker/u64:110:3157668] (standard input):Sep 21 13:39:24 marcus-server kernel: [452
[Kernel-packages] [Bug 1990399] 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/1990399 Title: sleep and hibernate not working Status in linux package in Ubuntu: Confirmed Bug description: sleep and hibernate not working Also I sometimes see "system crash" messages. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: takshil 25971 F pulseaudio /dev/snd/controlC0: takshil 25971 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 21 19:54:58 2022 InstallationDate: Installed on 2022-09-19 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=e541b293-9933-4b51-bced-82eeb2424484 ro splash iommu=soft vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2403 dmi.board.asset.tag: Default string dmi.board.name: ProArt B550-CREATOR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd06/16/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProArtB550-CREATOR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990399/+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 1990399] [NEW] sleep and hibernate not working
Public bug reported: sleep and hibernate not working Also I sometimes see "system crash" messages. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: takshil 25971 F pulseaudio /dev/snd/controlC0: takshil 25971 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 21 19:54:58 2022 InstallationDate: Installed on 2022-09-19 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=e541b293-9933-4b51-bced-82eeb2424484 ro splash iommu=soft vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2403 dmi.board.asset.tag: Default string dmi.board.name: ProArt B550-CREATOR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd06/16/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProArtB550-CREATOR:rvrRevX.0x: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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- 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/1990399 Title: sleep and hibernate not working Status in linux package in Ubuntu: Confirmed Bug description: sleep and hibernate not working Also I sometimes see "system crash" messages. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: takshil 25971 F pulseaudio /dev/snd/controlC0: takshil 25971 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 21 19:54:58 2022 InstallationDate: Installed on 2022-09-19 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=e541b293-9933-4b51-bced-82eeb2424484 ro splash iommu=soft vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2403 dmi.board.asset.tag: Default string dmi.board.name: ProArt B550-CREATOR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2403:bd06/16/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProArtB550-CREATOR:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990399/+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 1982990] Re: Enable speaker and mute LEDs for HP laptops
included at least in 5.15.0-48.54 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982990 Title: Enable speaker and mute LEDs for HP laptops Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Speaker and mute LEDs are not working on two HP laptops. [Fix] Use HDA quirk to enable SPI AMP and use GPIO to control LEDs. [Test] With the fix applied, speaker and mute LEDs are working on both laptops. [Where problems could occur] The quirk use very specific, so unless some broken hardwares use the same IDs, there's no potential regression can happen. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982990/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+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 1986965] Re: 12th gen intel PC can't boot with kernel 5.15.0-46
As I just have the update for the -48 kernel, I confirm that: The newest -48 has same issu, can't boot → only the kernel from the fresh install does work (5.15.0-41) -- 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/1986965 Title: 12th gen intel PC can't boot with kernel 5.15.0-46 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu 22.04 LTS here. I don't know if it is a bug directly linked to linux kernel but: Before my July holidays, PC booted fine, in less than 3sec, when I came back in august, there were some updates to install, including new kernel 5.15.0-46. After installing, I never was able to boot on it. - PC boot - GRUB will load - default select lastest kernel (5.15.0-46) - [see 1st attached PNG] a few line of log appears (same on working boot) - [see 2nd attached PNG] then default boot screen "MSI + ubuntu logo" appears, but "long time" - [see 3rd attached PNG] then [ OK ] linux boot log got displayed and stay on same line for few moment too. I guess that's the attached image that show the most important stuff. - [see 4th attached PNG] then black screen with top left corner with the white blinky cursor - CTRL+ALT+DEL to reboot To use my PC I have to choose additional ubuntu options and select 5.15.0-41 in grub. Using this option allow to boot normaly, and got livepatch applying an update at every reboot (so if it apply the -46, it works during live patch, but sadly not on hard reboot. Do you need more info/logs ? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_15_0_41_44_generic_88 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 18 16:18:56 2022 InstallationDate: Installed on 2022-04-29 (111 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=6e1766db-1fb6-4255-9258-a7a4c4a1f70d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2021 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.00 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A DDR4(MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.00:bd09/14/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-ADDR4(MS-7D25):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string 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/1986965/+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 1827452] Re: null pointer dereference in uvcvideo
I've seen this on 5.19.9 as well (not Ubuntu, NixOS 22.05). I thought it's interesting as well. My setup is a Logitech BRIO camera connected to a USB3 hub, connected to a LG display, connected via USB-C to my laptop. The issue happened (I think) when plugging in the camera into the USB hub. [91105.117569] usb 3-6.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [91105.117574] usb 3-6.1.3: Product: USB-Serial Controller D [91105.117576] usb 3-6.1.3: Manufacturer: Prolific Technology Inc. [91105.126255] pl2303 3-6.1.3:1.0: pl2303 converter detected [91105.127474] usb 3-6.1.3: pl2303 converter now attached to ttyUSB0 [91108.797780] BUG: kernel NULL pointer dereference, address: [91108.797787] #PF: supervisor read access in kernel mode [91108.797790] #PF: error_code(0x) - not-present page [91108.797793] PGD 0 P4D 0 [91108.797797] Oops: [#1] PREEMPT SMP NOPTI [91108.797801] CPU: 6 PID: 80084 Comm: ThreadPoolSingl Tainted: G O 5.19.9 #1-NixOS [91108.797806] Hardware name: TUXEDO TUXEDO Book XP14 Gen12/NV4XMB,ME,MZ, BIOS 1.07.14RTR1 08/24/2021 [91108.797808] RIP: 0010:usb_ifnum_to_if+0x3a/0x60 [usbcore] [91108.797824] Code: 34 41 0f b6 50 04 84 d2 74 33 83 ea 01 49 8d 80 98 00 00 00 49 8d 8c d0 a0 00 00 00 eb 09 48 83 c0 08 48 39 c8 74 16 4c 8b 00 <49> 8b 10 0f b6 52 02 39 f2 75 e9 4c 89 c0 c3 cc cc cc cc 45 31 c0 [91108.797826] RSP: 0018:a54807acfbb0 EFLAGS: 00010206 [91108.797829] RAX: 92881be64c98 RBX: RCX: 92881be64cc8 [91108.797831] RDX: 0005 RSI: 0001 RDI: 9287d09c9000 [91108.797832] RBP: 92881be66920 R08: R09: 8015000c [91108.797834] R10: R11: R12: 92881be62c00 [91108.797835] R13: 92881be66920 R14: 9287d09c9000 R15: 9287c4ebe000 [91108.797836] FS: 7f444d99f640() GS:928f5158() knlGS: [91108.797838] CS: 0010 DS: ES: CR0: 80050033 [91108.797840] CR2: CR3: 00040ecc2005 CR4: 00770ee0 [91108.797842] PKRU: 5554 [91108.797843] Call Trace: [91108.797845] [91108.797847] usb_hcd_alloc_bandwidth+0x245/0x370 [usbcore] [91108.797862] usb_set_interface+0x127/0x360 [usbcore] [91108.797877] uvc_video_start_transfer+0x181/0x4d0 [uvcvideo] [91108.797883] uvc_video_start_streaming+0x7f/0xe0 [uvcvideo] [91108.797889] uvc_start_streaming+0x2d/0xe0 [uvcvideo] [91108.797895] vb2_start_streaming+0x60/0x100 [videobuf2_common] [91108.797901] vb2_core_streamon+0x5c/0xd0 [videobuf2_common] [91108.797905] uvc_queue_streamon+0x2a/0x50 [uvcvideo] [91108.797910] uvc_ioctl_streamon+0x3a/0x60 [uvcvideo] [91108.797915] __video_do_ioctl+0x19c/0x3f0 [videodev] [91108.797927] ? mmap_region+0x281/0x600 [91108.797933] video_usercopy+0x171/0x710 [videodev] [91108.797942] ? v4l_print_control+0x20/0x20 [videodev] [91108.797951] v4l2_ioctl+0x46/0x50 [videodev] [91108.797959] __x64_sys_ioctl+0x87/0xc0 [91108.797963] do_syscall_64+0x38/0x90 [91108.797968] entry_SYSCALL_64_after_hwframe+0x63/0xcd [91108.797972] RIP: 0033:0x7f44611e1e37 [91108.797975] Code: ff ff 48 89 d8 5b 5d 41 5c c3 66 0f 1f 84 00 00 00 00 00 48 89 e8 48 f7 d8 48 39 c3 0f 92 c0 eb c9 66 90 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b1 0f 0f 00 f7 d8 64 89 01 48 [91108.797977] RSP: 002b:7f444d99df38 EFLAGS: 0246 ORIG_RAX: 0010 [91108.797980] RAX: ffda RBX: 385c0021d7d0 RCX: 7f44611e1e37 [91108.797981] RDX: 7f444d99dfb4 RSI: 40045612 RDI: 0019 [91108.797982] RBP: 7f444d99df70 R08: 0019 R09: 00bdf000 [91108.797984] R10: 0001 R11: 0246 R12: 385c00353b60 [91108.797985] R13: 385c00353a00 R14: 7f444d99dfb4 R15: 40045612 [91108.797988] [91108.797988] Modules linked in: snd_usb_audio snd_usbmidi_lib snd_rawmidi sd_mod uas usb_storage scsi_mod scsi_common pl2303 usbserial cdc_acm ccm rfcomm qrtr snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_packet snd_hda_codec_hdmi snd_sof_pci_intel_tgl snd_sof_intel_hda_common snd_soc_hdac_hda soundwire_intel soundwire_generic_allocation iwlmvm soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus joydev cmac mousedev algif_hash snd_soc_core snd_hda_codec_realtek algif_skcipher af_alg snd_hda_codec_generic snd_compress iTCO_wdt ac97_bus hid_multitouch bnep cmdlinepart spi_nor ledtrig_audio mac80211 snd_pcm_dmaengine intel_rapl_msr intel_pmc_bxt mei_hdcp mei_pxp ee1004 mtd watchdog msr snd_hda_intel i2c_designware_platform pmt_telemetry snd_intel_dspcfg snd_intel_sdw_acpi i2c_designware_core pmt_class libarc4 wmi_bmof zstd intel_rapl_common zstd_compress snd_hda_codec snd_hd a_core [91108.798038] iwlwifi btusb intel_tcc_cooling x86_pkg_temp_thermal intel_powerclamp snd_hwdep coretemp
[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
This bug is awaiting verification that the linux-oracle/5.15.0-1018.23 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+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 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-oracle/5.15.0-1018.23 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1983640 Title: refactoring of overlayfs fix to properly support shiftfs Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-hwe-5.17 source package in Kinetic: Invalid Bug description: [Impact] Starting with 5.13 we've incorrectly dropped the following sauce patch: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files This patch is required to use overlayfs on top of shiftfs and without this patch we may break containers that rely on shiftfs (using zfs/ceph as storage pool w/ shiftfs enabled). However, we made this patch dependent on AUFS, starting with Jammy we're not enabling AUFS anymore, so this fix becomes a no-op. So we need to re-introduce this fix with a bit of refactoring to not depend on AUFS. [Test case] The following script can be used to trigger the issue: #!/bin/bash cat > test.py << EOF import sys f = open("/proc/self/maps") for l in f.readlines(): if "python" not in l: continue print(l) s = l.split() start, end = s[0].split("-") fname = s[-1] print(start, end, fname) break else: sys.exit(1) test_file1 = open(fname) test_file2 = open("/proc/self/map_files/%s-%s" % (start, end)) fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read() fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read() if fdinfo1 != fdinfo2: print("FAIL") print(test_file1) print(fdinfo1) print(test_file2) print(fdinfo2) sys.exit(1) print("PASS") EOF sudo docker run -it --privileged --rm -v `pwd`:/mnt python python /mnt/test.py [Fix] Import the right pieces from AUFS to properly support the fix and get rid of the AUFS dependency across all our kernels and re-apply the overlayfs fix without the AUFS dependency. [Regression potential] This patch is touching overlayfs, so we may see potential regressions in overlayfs, especially when containers are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+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 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Verification done on jammy (on a slightly different setup): root@s1lp15:~# uname -a Linux s1lp15 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:23 UTC 2022 s390x s390x s390x GNU/Linux root@s1lp15:~# ethtool encc000 | grep Duplex Duplex: Full root@s1lp15:~# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii | wc -l 3 root@s1lp15:~# grep qcrdinfo /sys/kernel/debug/s390dbf/qeth*/hex_ascii /sys/kernel/debug/s390dbf/qeth_card_0.0.c000/hex_ascii:00 01664021373:134002 2 - 0001 03ff81066676 71 63 72 64 69 6e 66 6f | qcrdinfo /sys/kernel/debug/s390dbf/qeth_card_0.0.c000/hex_ascii:00 01664021384:308308 2 - 0007 03ff81066676 71 63 72 64 69 6e 66 6f | qcrdinfo /sys/kernel/debug/s390dbf/qeth_card_0.0.c000/hex_ascii:00 01664021384:308804 2 - 0007 03ff81066676 71 63 72 64 69 6e 66 6f | qcrdinfo root@s1lp15:~# ethtool encc000 Settings for encc000: Supported ports: [ FIBRE ] Supported link modes: 1baseSR/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 1baseSR/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1Mb/s Duplex: Full Auto-negotiation: on Port: FIBRE PHYAD: 0 Transceiver: internal Link detected: yes (adjusting tags accordingly) ** Tags added: verification-done verification-done-jammy -- 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/1984103 Title: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: == SRU Justification == Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is offline") there was a timing window during recovery, that qeth_query_card_info could be sent to the card, even before it was ready for it, leading to a failing cardrecovery. There is evidence that this window was hit, as not all callers of get_link_ksettings() check for netif_device_present. This patch (Mainline commit 7a07a29e4f67) fixes the regression caused by commit e6e771b3d897. Commit 7a07a29e4f67 is in mainline as of v6.0-rc1. This patch is being requested in Jammy 5.15 and Kinetic 5.19. == Fix == 7a07a29e4f67 ("s390/qeth: cache link_info for ethtool") == Regression Potential == Low. This patch has been accepted in upstream stable and is limited to the s390/qeth card. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 == +++ This bug was initially created as a clone of Bug #199319 +++ Description: s390/qeth: cache link_info for ethtool Symptom: lost of IP connection and log entries in journalctl: kernel: qeth 0.0.0365: The qeth device driver failed to recover an error on the device Problem: Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is offline") there was a timing window during recovery, that qeth_query_card_info could be sent to the card, even before it was ready for it, leading to a failing card recovery. There is evidence that this window was hit, as not all callers of get_link_ksettings() check for netif_device_present. Solution: Use cached values in qeth_get_link_ksettings(), instead of calling qeth_query_card_info() and falling back to default values in case it fails. Link info is already updated when the card goes online, e.g. after STARTLAN (physical link up). Set the link info to default values, when the card goes offline or at STOPLAN (physical link down). A follow-on patch will improve values reported for link down. Fixes: e6e771b3d897 ("s390/qeth: detach netdevice while card is offline") Reproduction: enforce a eth device recvoery, while running ethtool multiple times in parallel and using iperf to get load on the interface. Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8 https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f applicable for most kernel > 3.14 == Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 == the inital update came in with kernel 5.1 upstream, but we found it backported in many older kernel versions == Comme
[Kernel-packages] [Bug 1986798] Re: Remove unused variable from i915 psr
This bug is awaiting verification that the linux-oracle/5.15.0-1018.23 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1986798 Title: Remove unused variable from i915 psr Status in linux package in Ubuntu: Won't Fix Status in linux source package in Jammy: Fix Released Bug description: [Impact] Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU: SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker") [Fix] The variable is unused, remove it. [Test] Compiler no longer warns about it. [Where problems could occur] Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+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 1987670] Re: Add support for AMD PMF
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (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/1987670 Title: Add support for AMD PMF Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Fix Committed Bug description: Some upcoming platforms support for AMD-PMF. This will enable ACPI platform profiles and some automatic transitions. The first 11 patches are queued up for 6.1 and also available in an immutable branch. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf Can you please merge these to OEM-6.0? We will have 3-5 more patches targeted later as well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987670/+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 1990275] Re: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04
** Changed in: ubuntu-z-systems 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/1990275 Title: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: == Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42 == ---Problem Description--- On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports connected to the a pair of TOR switches , act as entry point to cluster of compute nodes to access public network ( edge node) with following level of mlx firmware : ethtool -i p0 driver: mlx5e_rep version: 5.4.0-104.118- firmware-version: 16.27.1016 (MT_13) expansion-rom-version: bus-info: 0100:00:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to routing events and sets the LAG affinity accordingly , whereas in one of custom services has Fabcon service listens to the routing events and sets the LAG affinity in the mellanox driver accordingly. The edge node routes defined in compute nodes use both the two interfaces (port1 -P0 and port2- P1) for the LAG affinity. For instance 10.66.0.170 proto bgp src 10.66.11.43 metric 20 nexthop via 172.31.22.42 dev p0 weight 1 nexthop via 172.31.22.170 dev p1 weight 1 As an example post an edge node bootup , LAG mapping gets converged to use both port1(P0) and port2 (P1) by default root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 (<-- Both ports are equally mapped) The issue comes, when the mlx5_core driver cannot derive the LAG configuration from specific routes. For instance,an operation of disabling an interface from edge node above (10.66.0.170) or addition/removal of the interface, causes mlx5_core driver to listen on the routing change and change the LAG affinity to use a single network interface only. In the following example ,a new static route entry to a single destination (10.66.47.34) is added as below ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via 172.31.22.42 dev p0 Caused the LAG mapping change to port1(p0) as detected as following root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 [ 757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1
[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1981883 Title: amdgpu module crash after 5.15 kernel update Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [SRU Justification] Impact: The 5.15 kernel series introduced a regression compared to 5.13 related to virtual display code on AMD GPUs. This causes crashes for cloud/VM users back to Focal (using rolling cloud or HWE kernels). Fix: Upstream stable 5.15.61 contains a fix for this which is only needed there since later kernel version have that code rewritten again. This change would get picked up normally in the next stable cycle after 2022.09.19. But given the impact we would apply the following patch from 5.15.61 ahead of time: commit 27f8f5219fe4658537ba28fd01657e1062ac3960 linux-5.15.y "drm/amdgpu: fix check in fbdev init" Test case: Booting the affected kernel on a VM which passes through AMD GPU hardware. Regression potential: Worst case some driver functions will not get disabled where they did before. --- original description --- The kernel 5.15 amdgpu module crashes on load with a “BUG: kernel NULL pointer dereference” on Amazon EC2 G4ad hardware (custom AMD Radeon V520 Pro datacenter GPU) on focal (HWE) and jammy with kernel 5.15.0-1011 and possibly earlier, up through latest (revision 1015.19). This crash bug did not exist in any of the focal HWE 5.13 kernels. This is probably an upstream kernel bug, but I am also filing it here because existing focal users on EC2 will suddenly stop having access to their AMD GPUs after a reboot once the new 5.15 HWE kernel is installed. The full backtrace from dmesg is below. The offending function call which crashes in the 5.15 kernel corresponds to this source (sorry, not the right source tree, but the same driver) https://github.com/torvalds/linux/blob/8bb7eca972ad531c9b149c0a51ab43a417385813/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c#L345 A workaround that I have discovered is adding “options amdgpu virtual_display=;” to a new modprobe.d configuration file - something which shouldn’t be required, but is at least harmless. Here is the relevant BUG message and backtrace from dmesg: [ 318.111721] BUG: kernel NULL pointer dereference, address: [ 318.115443] #PF: supervisor instruction fetch in kernel mode [ 318.118443] #PF: error_code(0x0010) - not-present page [ 318.121177] PGD 0 P4D 0 [ 318.122688] Oops: 0010 [#1] SMP NOPTI [ 318.124592] CPU: 6 PID: 13667 Comm: modprobe Tainted: GW 5.15.0-1015-aws #19~20.04.1-Ubuntu [ 318.129711] Hardware name: Amazon EC2 g4ad.2xlarge/, BIOS 1.0 10/16/2017 [ 318.133167] RIP: 0010:0x0 [ 318.134704] Code: Unable to access opcode bytes at RIP 0xffd6. [ 318.138291] RSP: 0018:9841828d78e0 EFLAGS: 00010246 [ 318.140938] RAX: RBX: 8a4f16ae8000 RCX: 0001 [ 318.144604] RDX: RSI: 0003 RDI: 8a4f16ae8000 [ 318.148319] RBP: 9841828d7908 R08: 8a4f02460278 R09: 8a4f06422c40 [ 318.152151] R10: c01c42494f8a R11: 8a4f01dcb5b8 R12: 8a4f024602e8 [ 318.155929] R13: c107e4a0 R14: R15: 8a4f02460010 [ 318.159685] FS: 7f8afdc1c740() GS:8a55f098() knlGS: [ 318.163897] CS: 0010 DS: ES: CR0: 80050033 [ 318.167038] CR2: ffd6 CR3: 00011817e000 CR4: 003506e0 [ 318.170758] Call Trace: [ 318.173964] [ 318.176822] __drm_helper_disable_unused_functions+0xe7/0x100 [drm_kms_helper] [ 318.184230] drm_helper_disable_unused_functions+0x44/0x50 [drm_kms_helper] [ 318.189761] amdgpu_fbdev_init+0x104/0x110 [amdgpu] [ 318.194264] amdgpu_device_init.cold+0x7cc/0xc48 [amdgpu] [ 318.199061] ? pci_read_config_byte+0x27/0x40 [ 318.203206] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] [ 318.207901] amdgpu_pci_probe+0x1ea/0x290 [amdgpu] [ 318.212445] local_pci_probe+0x4b/0x90 [ 318.216386] pci_device_probe+0x182/0x1f0 [ 318.220407] really_probe.part.0+0xcb/0x370 [ 318.224460] really_probe+0x40/0x80 [ 318
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1984103 Title: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: == SRU Justification == Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is offline") there was a timing window during recovery, that qeth_query_card_info could be sent to the card, even before it was ready for it, leading to a failing cardrecovery. There is evidence that this window was hit, as not all callers of get_link_ksettings() check for netif_device_present. This patch (Mainline commit 7a07a29e4f67) fixes the regression caused by commit e6e771b3d897. Commit 7a07a29e4f67 is in mainline as of v6.0-rc1. This patch is being requested in Jammy 5.15 and Kinetic 5.19. == Fix == 7a07a29e4f67 ("s390/qeth: cache link_info for ethtool") == Regression Potential == Low. This patch has been accepted in upstream stable and is limited to the s390/qeth card. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 == +++ This bug was initially created as a clone of Bug #199319 +++ Description: s390/qeth: cache link_info for ethtool Symptom: lost of IP connection and log entries in journalctl: kernel: qeth 0.0.0365: The qeth device driver failed to recover an error on the device Problem: Since commit e6e771b3d897 ("s390/qeth: detach netdevice while card is offline") there was a timing window during recovery, that qeth_query_card_info could be sent to the card, even before it was ready for it, leading to a failing card recovery. There is evidence that this window was hit, as not all callers of get_link_ksettings() check for netif_device_present. Solution: Use cached values in qeth_get_link_ksettings(), instead of calling qeth_query_card_info() and falling back to default values in case it fails. Link info is already updated when the card goes online, e.g. after STARTLAN (physical link up). Set the link info to default values, when the card goes offline or at STOPLAN (physical link down). A follow-on patch will improve values reported for link down. Fixes: e6e771b3d897 ("s390/qeth: detach netdevice while card is offline") Reproduction: enforce a eth device recvoery, while running ethtool multiple times in parallel and using iperf to get load on the interface. Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8 https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f applicable for most kernel > 3.14 == Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 == the inital update came in with kernel 5.1 upstream, but we found it backported in many older kernel versions == Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 == the acceptance info of the patch can be found here: https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+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 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs: [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] p
[Kernel-packages] [Bug 1987232] Re: WARN in trace_event_dyn_put_ref
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Bug description: [SRU Justification] Impact: Some imbalanced ref-counting produces kernel warnings regularly. Since it is a warning level, this triggers system monitoring on servers which in turn causes unnecessary work for inspecting the logs. Fix: There is a fix upstream and also backported to the upstream stable branch. However we are still a bit behind catching up with the latest versions. Since this is having quite an impact and the fix is rather straight forward, we pull this in from upstream stable ahead of time. Test case: tbd Regression potential: Regressions would manifest as different errors related to ref-counting. --- I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2&id=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 22 17:32 seq crw-rw 1 root audio 116, 33 Aug 22 17:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Amazon EC2 c5d.12xlarge Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1015-aws root=PARTUUID=4986e35b-1bd5-45d3-b528-fa2edb861a38 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 ProcVersionSignature: Ubuntu 5.15.0-1015.19~20.04.1-aws 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-1015-aws N/A linux-backports-modules-5.15.0-1015-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.15.0-1015-aws x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.release: 1.0 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-03f5d8581c7ad94aa dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnc5d.12xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku: dmi.product.name: c5d.1
[Kernel-packages] [Bug 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms
** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-5.17 (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/1989046 Title: support independent clock and LED GPIOs for Intel IPU6 platforms Status in linux package in Ubuntu: In Progress 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: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] When migrated from power_ctrl_logic driver to int3472, two additional independent CLK/LED GPIOs other than powerdown/reset must be probed exceptionally. [Fix] Vendor provided patch in https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch. [Test Case] Tested on both TGL/ADL platforms against nominated kernels. [Where problems could occur] This adds exceptional cases with fallbacks to the original function. No one else is affected. [Other Info] This is an essential part for switching from power_ctrl_logic based GPIO control mechanism to the generic, upstreamed int3472 driver. Affects all IPU6 platforms that are to run new IPU6 driver dump in 202208. == original bug report == Per https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026 and https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2, additional fix for INT3472 is necessary to probe camera sensor GPIOs on Intel IPU6 platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989046/+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 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1988809 Title: ip/nexthop: fix default address selection for connected nexthop Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Packets sent by userland apps are rejected/dropped if the source address is not specified and the corresponding route is using a connected nexthop object. This bug exists since linux v5.3 and has been fixed in v5.19 by the following upstream commits: - 747c14307214 ("ip: fix dflt addr selection for connected nexthop") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214 - cd72e61bad14 ("selftests/net: test nexthop without gw") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14 - eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd The last commit (v6.0) fixes a regression introduced by the first commit. [Test Case] A detailed test case is explained in the first commit and a self-test is added in the second commit. [Regression Potential] The patch modifies some internal routing states. It has been living in the upstream trees for 2 months and the reported regression about icmp redirects has been fixed. The risk of regression should be contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+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 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55
This bug is awaiting verification that the linux/5.15.0-50.56 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-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- 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/1990124 Title: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55 This looks like a potential regression as there is no change to the test script. Manual test show this issue does not exist on: * J-5.15.0-47 * J-5.15.0-48 Test log: ### Legacy routing ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [FAIL] TEST: IPv6: mtu exception plus redirect [ OK ] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [FAIL] TEST: IPv6: mtu exception plus redirect [ OK ] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [FAIL] TEST: IPv6: mtu exception plus redirect [ OK ] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [FAIL] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [FAIL] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception
[Kernel-packages] [Bug 1990275] Re: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04
The file in question: drivers/net/ethernet/mellanox/mlx5/core/lag/mp.c does also not exist on latest 5.4 upstream: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/net/ethernet/mellanox/mlx5/core?h=v5.4.214 (but drivers/net/ethernet/mellanox/mlx5/core/lag_mp.c). Looks like the file got 'introduced' with 3d677735d3b7 in v5.16-rc1 by: " rename from drivers/net/ethernet/mellanox/mlx5/core/lag_mp.c rename to drivers/net/ethernet/mellanox/mlx5/core/lag/mp.c " So I guess there are either more commits (like this) needed or a backport(s). -- 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/1990275 Title: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04 Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: == Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42 == ---Problem Description--- On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports connected to the a pair of TOR switches , act as entry point to cluster of compute nodes to access public network ( edge node) with following level of mlx firmware : ethtool -i p0 driver: mlx5e_rep version: 5.4.0-104.118- firmware-version: 16.27.1016 (MT_13) expansion-rom-version: bus-info: 0100:00:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to routing events and sets the LAG affinity accordingly , whereas in one of custom services has Fabcon service listens to the routing events and sets the LAG affinity in the mellanox driver accordingly. The edge node routes defined in compute nodes use both the two interfaces (port1 -P0 and port2- P1) for the LAG affinity. For instance 10.66.0.170 proto bgp src 10.66.11.43 metric 20 nexthop via 172.31.22.42 dev p0 weight 1 nexthop via 172.31.22.170 dev p1 weight 1 As an example post an edge node bootup , LAG mapping gets converged to use both port1(P0) and port2 (P1) by default root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 (<-- Both ports are equally mapped) The issue comes, when the mlx5_core driver cannot derive the LAG configuration from specific routes. For instance,an operation of disabling an interface from edge node above (10.66.0.170) or addition/removal of the interface, causes mlx5_core driver to listen on the routing change and change the LAG affinity to use a single network interface only. In the following example ,a new static route entry to a single destination (10.66.47.34) is added as below ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via 172.31.22.42 dev p0 Caused the LAG mapping change to port1(p0) as detected as following root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 [ 757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1
[Kernel-packages] [Bug 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.0 (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-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990240 Title: To support Intel Maple Ridge Thunderbolt [8086:1134] Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The TBT ID[8086:1134] the new project uses is not listed in the driver. [Fix] Intel submits this as we requested which is still in linux-next https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/ [Where problems could occur] Adding only one ID, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990240/+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 1990275] Re: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04
Well, yes - I just ran into this, while I wanted to proceed on this ticket. Things definitely do not apply on focal master next (git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal --branch master-next --single-branch). Even the first commit ad11c4f1d8fd is causing a significant conflict, since file "drivers/net/ethernet/mellanox/mlx5/core/lag/mp.c" does not exist (anymore?). So I unfortunately cannot apply these commits as they are: ad11c4f1d8fd ad11c4f1d8fd1f03639460e425a36f7fd0ea83f5 "net/mlx5e: Lag, Only handle events from highest priority multipath entry" 27b0420fd959 27b0420fd959e38e3500e60b637d39dfab065645 "net/mlx5e: Lag, Fix use-after-free in fib event handler" a6589155ec98 a6589155ec9847918e00e7279b8aa6d4c272bea7 "net/mlx5e: Lag, Fix fib_info pointer assignment" 4a2a664ed879 4a2a664ed87962c4ddb806a84b5c9634820bcf55 "net/mlx5e: Lag, Don't skip fib events on current dst" I may try to have a look what's going on, but would like to ask you also to double-check if there is anything missing ... -- 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/1990275 Title: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04 Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: == Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42 == ---Problem Description--- On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports connected to the a pair of TOR switches , act as entry point to cluster of compute nodes to access public network ( edge node) with following level of mlx firmware : ethtool -i p0 driver: mlx5e_rep version: 5.4.0-104.118- firmware-version: 16.27.1016 (MT_13) expansion-rom-version: bus-info: 0100:00:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to routing events and sets the LAG affinity accordingly , whereas in one of custom services has Fabcon service listens to the routing events and sets the LAG affinity in the mellanox driver accordingly. The edge node routes defined in compute nodes use both the two interfaces (port1 -P0 and port2- P1) for the LAG affinity. For instance 10.66.0.170 proto bgp src 10.66.11.43 metric 20 nexthop via 172.31.22.42 dev p0 weight 1 nexthop via 172.31.22.170 dev p1 weight 1 As an example post an edge node bootup , LAG mapping gets converged to use both port1(P0) and port2 (P1) by default root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 (<-- Both ports are equally mapped) The issue comes, when the mlx5_core driver cannot derive the LAG configuration from specific routes. For instance,an operation of disabling an interface from edge node above (10.66.0.170) or addition/removal of the interface, causes mlx5_core driver to listen on the routing change and change the LAG affinity to use a single network interface only. In the following example ,a new static route entry to a single destination (10.66.47.34) is added as below ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via 172.31.22.42 dev p0 Caused the LAG mapping change to port1(p0) as detected as following root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 [ 757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1
[Kernel-packages] [Bug 1990275] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2022-09-21 07:02 EDT--- (In reply to comment #9) > Since kinetic/22.10 is based on 5.19 and all patches got upstream accepted > with at least v5.18 (one 5.17), everything needed is included in > kinetic/22.10. > > For jammy/22.04 I checked master-next and found all patches in > Ubuntu-5.15.0-41 or later, so jammy/22.04 incl. all the fixes and is not (or > better no longer) affected. > > But neither of these patches is incl. in focal/20.04 master-next, so only > focal is affected (and with that also bionic-hwe-5.4) > > So I'm marking this ticket as affecting focal. Thanks for investigating, this matches my understanding > (Btw. it would have been great if these patches would have been marked for > 5.4 upstream stable too, since 5.4 is upstream also a long-term kernel; in > such a case the fixes would have landed automatically in Ubuntu's > focal/20.04 - and in bionic-hwe-5.4). Yes I agree. I do wonder though, I think the stable series autoselection also triggers with Fixes tags only. If the patches apply cleanly there is usually no more interaction needed, so maybe these did not apply cleanly and the Mellanox colleagues who authored these fixes did not provide backports via the stable process. -- 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/1990275 Title: [UBUNTU 20.04] Unexpected LAG affinity behaviour with mlx5_core driver in Ubuntu 20.04 Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: == Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42 == ---Problem Description--- On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports connected to the a pair of TOR switches , act as entry point to cluster of compute nodes to access public network ( edge node) with following level of mlx firmware : ethtool -i p0 driver: mlx5e_rep version: 5.4.0-104.118- firmware-version: 16.27.1016 (MT_13) expansion-rom-version: bus-info: 0100:00:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no The LAG affinity module of mlx5_core in upstream 5.4 kernel listens to routing events and sets the LAG affinity accordingly , whereas in one of custom services has Fabcon service listens to the routing events and sets the LAG affinity in the mellanox driver accordingly. The edge node routes defined in compute nodes use both the two interfaces (port1 -P0 and port2- P1) for the LAG affinity. For instance 10.66.0.170 proto bgp src 10.66.11.43 metric 20 nexthop via 172.31.22.42 dev p0 weight 1 nexthop via 172.31.22.170 dev p1 weight 1 As an example post an edge node bootup , LAG mapping gets converged to use both port1(P0) and port2 (P1) by default root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 (<-- Both ports are equally mapped) The issue comes, when the mlx5_core driver cannot derive the LAG configuration from specific routes. For instance,an operation of disabling an interface from edge node above (10.66.0.170) or addition/removal of the interface, causes mlx5_core driver to listen on the routing change and change the LAG affinity to use a single network interface only. In the following example ,a new static route entry to a single destination (10.66.47.34) is added as below ip route add 10.66.47.34 proto static src 10.66.11.43 metric 20 via 172.31.22.42 dev p0 Caused the LAG mapping change to port1(p0) as detected as following root@pok1-qz1-sr1-rk011-s20:/# dmesg | grep lag [ 282.043011] mlx5_core 0100:00:00.0: lag map port 1:2 port 2:2 [ 282.083541] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:2 [ 757.878626] mlx5_core 0100:00:00.0: modify lag map port 1:1 port 2:1
[Kernel-packages] [Bug 1990377] Re: Night Light does not fade in/out when toggled (on some laptop displays)
** Changed in: mutter Status: Unknown => 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/1990377 Title: Night Light does not fade in/out when toggled (on some laptop displays) Status in Mutter: Fix Released Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Invalid Bug description: Starting in mutter 43.rc, night light does not fade in/out when toggled (on some laptop displays). It just toggles instantly, or in some cases only part of the screen. Workaround: Add kernel parameter: i915.enable_psr=0 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990377/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Confirmed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelC
[Kernel-packages] [Bug 1990330] Re: System hang during S3 test
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released -- 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/1990330 Title: System hang during S3 test Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R) Silver N6005 @ 2.00GHz [Fix] Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and found this below commit 567511462387 mm/memcg: protect memcg_stock with a local_lock_t For safty, I backported the series of the patch https://www.spinics.net/lists/cgroups/msg31595.html But I still can reproduce the issue after applied those patches on top of 5.17 oem kernel. So, I did a second round of bisecting and found below commit is required, too a74c6c00b1cb mm/memremap: avoid calling kasan_remove_zero_shadow() for device private memory [Test] Done the S3 test 400 times on the target and it's still working well. [Where problems could occur] Hard to evaluate the impact, but from the overnight test, the memory usage is still low, so there should be no memory leakage, and can't find any fix patch for those applied commits from upstream and linux-next trees. The patches are all from v5.18-rc1, so we only need them to be applied on oem-5.17 kernel, and will let QA to do thoroughly tests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990330/+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 1990242] Re: Intel graphic driver is not probing[8086:468b]
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.0 (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-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990242 Title: Intel graphic driver is not probing[8086:468b] Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Got blank screen after entered desktop [Fix] Below commit in linux-next fixes the issue. 6215a7c8f552 drm/i915: Add new ADL-S pci id [Test] Verified on the target machine. [Where problems could occur] It only adds an ID to the list, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990242/+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 1990161] Re: Fix RPL-S support on powercap/intel_rapl
** Changed in: linux-oem-6.0 (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-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990161 Title: Fix RPL-S support on powercap/intel_rapl Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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: In Progress Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] proc_thermal driver is not loaded [Fix] Add RPL-S id on device id table of powercap/intel_rapl. [Test Case] 1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal [Where problems could occur] Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990161/+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 1990377] 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 1990377 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/1990377 Title: Night Light does not fade in/out when toggled (on some laptop displays) Status in Mutter: Unknown Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Invalid Bug description: Starting in mutter 43.rc, night light does not fade in/out when toggled (on some laptop displays). It just toggles instantly, or in some cases only part of the screen. Workaround: Add kernel parameter: i915.enable_psr=0 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990377/+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 1989518] Re: AMD ACP 6.2 DMIC support
** Changed in: linux-oem-6.0 (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/1989518 Title: AMD ACP 6.2 DMIC support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: The patchset will be merged to upstream kernel v6.1, the unstable kernel will have the patchset automatically after the v6.1 is ready. The oem-5.17 kernel doesn't support this AMD generation platform yet, so this patchset is useless for oem-5.17 so far. [Impact] On the AMD PS platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 13 patches from linux-next kernel to fix this problem. [Test] boot the patched kernel on the machine, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic support on AMD ps machines, it will match the pci device revision and apply the driver according to match result, in theory it will not bring regression on non-amd-ps machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989518/+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 1990377] [NEW] Night Light does not fade in/out when toggled (on some laptop displays)
Public bug reported: Starting in mutter 43.rc, night light does not fade in/out when toggled (on some laptop displays). It just toggles instantly, or in some cases only part of the screen. Workaround: Add kernel parameter: i915.enable_psr=0 ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete ** Affects: mutter (Ubuntu) Importance: Low Status: Invalid ** Tags: i915 kinetic psr ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2436 https://gitlab.gnome.org/GNOME/mutter/-/issues/2436 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2436 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: Triaged => Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Description changed: - Night Light does not fade in/out when toggled (on some laptop displays). - It just toggles instantly, or in some cases only part of the screen. + Starting in mutter 43.rc, night Light does not fade in/out when toggled + (on some laptop displays). It just toggles instantly, or in some cases + only part of the screen. Workaround: Add kernel parameter: i915.enable_psr=0 ** Description changed: - Starting in mutter 43.rc, night Light does not fade in/out when toggled + Starting in mutter 43.rc, night light does not fade in/out when toggled (on some laptop displays). It just toggles instantly, or in some cases only part of the screen. Workaround: Add kernel parameter: i915.enable_psr=0 -- 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/1990377 Title: Night Light does not fade in/out when toggled (on some laptop displays) Status in Mutter: Unknown Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Invalid Bug description: Starting in mutter 43.rc, night light does not fade in/out when toggled (on some laptop displays). It just toggles instantly, or in some cases only part of the screen. Workaround: Add kernel parameter: i915.enable_psr=0 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990377/+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