[Kernel-packages] [Bug 1980374] Re: Fix AMDGPU probe failure
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980374 Title: Fix AMDGPU probe failure Status in HWE Next: Fix Released 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: New Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] AMDGPU probe fails on v5.17 based kernel. [Fix] Replace the 'else if' statement to 'if' statement so the logic can be checked and run. [Test] The AMDGPU driver always succesfully probe the device with the patch. [Where problems could occur] The logic had been working for sometime but code refactoring messed it up. This brings back the old behavior so the surprise should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980374/+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 1980374] Re: Fix AMDGPU probe failure
included in 5.19 ** Changed in: hwe-next 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/1980374 Title: Fix AMDGPU probe failure Status in HWE Next: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] AMDGPU probe fails on v5.17 based kernel. [Fix] Replace the 'else if' statement to 'if' statement so the logic can be checked and run. [Test] The AMDGPU driver always succesfully probe the device with the patch. [Where problems could occur] The logic had been working for sometime but code refactoring messed it up. This brings back the old behavior so the surprise should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980374/+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 1980374] Re: Fix AMDGPU probe failure
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1013.14 --- linux-oem-5.17 (5.17.0-1013.14) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1013.14 -proposed tracker (LP: #1979417) * Fix AMDGPU probe failure (LP: #1980374) - drm/amdgpu: enable amdgpu_dc module parameter * Enable WiFi hotspot feature for MediaTek MT7921 (LP: #1979173) - mt76: mt7921: Add AP mode support - SAUCE: mt76: mt7921: not support beacon offload disable command - SAUCE: mt76: mt7921: fix command timeout in AP stop period * Suppress harmless warning from hp-wmi (LP: #1980307) - platform/x86: hp-wmi: Ignore Sanitization Mode event * CVE-2022-1679 - SAUCE: ath9k: fix use-after-free in ath9k_hif_usb_rx_cb * Fix WD22TB4 suspend and resume, two external monitor can not output (LP: #1979267) - drm/dp/mst: Read the extended DPCD capabilities during system resume * Intel iwlwifi AX211: WRT: Failed to set DRAM buffer for alloc id 1, ret=-1 (LP: #1979182) - iwlwifi: yoyo: fix DBGC allocation flow - iwlwifi: dbg-tlv: clean up iwl_dbg_tlv_update_drams() * CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166 - Documentation: Add documentation for Processor MMIO Stale Data - x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug - x86/speculation: Add a common function for MD_CLEAR mitigation update - x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data - x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations - x86/speculation/mmio: Enable CPU Fill buffer clearing on idle - x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data - x86/speculation/srbds: Update SRBDS mitigation selection - x86/speculation/mmio: Reuse SRBDS mitigation for SBDS - KVM: x86/speculation: Disable Fill buffer clear within guests - x86/speculation/mmio: Print SMT warning * Add support for Raptor Lake (LP: #1978794) - x86/cpu: Add new Alderlake and Raptorlake CPU model numbers - powercap: intel_rapl: add support for RaptorLake - perf/x86: Add new Alder Lake and Raptor Lake support - perf/x86/msr: Add new Alder Lake and Raptor Lake support - perf/x86/cstate: Add new Alder Lake and Raptor Lake support - perf/x86/uncore: Clean up uncore_pci_ids[] - perf/x86/uncore: Add new Alder Lake and Raptor Lake support - i2c: i801: Add support for Intel Raptor Lake PCH-S - spi: pxa2xx: Add support for Intel Raptor Lake PCH-S - pinctrl: alderlake: Add Raptor Lake-S ACPI ID - mfd: intel-lpss: Add Intel Raptor Lake PCH-S PCI IDs - HID: intel-ish-hid: ipc: add ADL and RPL device id - spi: intel: Add support for Raptor Lake-S SPI serial flash * Miscellaneous Ubuntu changes - [Config] Adjust annotation - [Config] Update config after rebase [ Ubuntu: 5.17.0-8.8~22.04.6 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.6 -proposed tracker (LP: #1980479) * Jammy update: v5.17.15 upstream stable release (LP: #1980389) - pcmcia: db1xxx_ss: restrict to MIPS_DB1XXX boards - staging: greybus: codecs: fix type confusion of list iterator variable - iio: adc: ad7124: Remove shift from scan_type - lkdtm/bugs: Check for the NULL pointer after calling kmalloc - lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP - tty: goldfish: Use tty_port_destroy() to destroy port - tty: serial: owl: Fix missing clk_disable_unprepare() in owl_uart_probe - tty: n_tty: Restore EOF push handling behavior - serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe - tty: serial: fsl_lpuart: fix potential bug when using both of_alias_get_id and ida_simple_get - remoteproc: imx_rproc: Ignore create mem entry for resource table - phy: rockchip-inno-usb2: Fix muxed interrupt support - usb: usbip: fix a refcount leak in stub_probe() - usb: usbip: add missing device lock on tweak configuration cmd - USB: storage: karma: fix rio_karma_init return - usb: musb: Fix missing of_node_put() in omap2430_probe - staging: fieldbus: Fix the error handling path in anybuss_host_common_probe() - pwm: lp3943: Fix duty calculation in case period was clamped - pwm: raspberrypi-poe: Fix endianness in firmware struct - rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value - usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback - usb: dwc3: pci: Fix pm_runtime_get_sync() error checking - scripts/get_abi: Fix wrong script file name in the help message - misc: fastrpc: fix an incorrect NULL check on list iterator - firmware: stratix10-svc: fix a missing check on list iterator - usb: typec: mux: Check dev_set_name() return value - rpmsg: virtio: Fix possible double free in rpmsg_probe() - rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev() - rpmsg: virtio: Fix the unregistration of the device
[Kernel-packages] [Bug 1980374] Re: Fix AMDGPU probe failure
This bug is awaiting verification that the linux-oem-5.17/5.17.0-1013.14 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! ** Tags added: verification-needed-jammy -- 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/1980374 Title: Fix AMDGPU probe failure Status in HWE Next: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] AMDGPU probe fails on v5.17 based kernel. [Fix] Replace the 'else if' statement to 'if' statement so the logic can be checked and run. [Test] The AMDGPU driver always succesfully probe the device with the patch. [Where problems could occur] The logic had been working for sometime but code refactoring messed it up. This brings back the old behavior so the surprise should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980374/+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 1980374] Re: Fix AMDGPU probe failure
** Changed in: linux-oem-5.17 (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/1980374 Title: Fix AMDGPU probe failure Status in HWE Next: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] AMDGPU probe fails on v5.17 based kernel. [Fix] Replace the 'else if' statement to 'if' statement so the logic can be checked and run. [Test] The AMDGPU driver always succesfully probe the device with the patch. [Where problems could occur] The logic had been working for sometime but code refactoring messed it up. This brings back the old behavior so the surprise should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980374/+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
