[Kernel-packages] [Bug 1987249] Re: Asus ROG Zephyrus GX701L sound problem
Hello team, Any update? -- 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/1987249 Title: Asus ROG Zephyrus GX701L sound problem Status in linux package in Ubuntu: Confirmed Bug description: Hello, Please, can someone add a kernel fix for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01? ``` [codec] 0x10ec0294 0x10431f01 0 [pincfg] 0x19 0x03A11050 0x1a 0x03A11C30 ``` This is what a quirk should look like: +SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK) [2.396344] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [2.396348] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.396349] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.396350] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.396351] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.396352] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [2.396353] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 If you need any more data, or smth just say so. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rakic 1415 F pulseaudio /dev/snd/controlC1: rakic 1415 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus S17 GX701LWS_GX701LWS NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=cba43497-441a-4919-8141-a95a789a9239 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 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 Tags: jammy Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX701LWS.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX701LWS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX701LWS.310:bd04/19/2021:br5.17:efr3.7:svnASUSTeKCOMPUTERINC.:pnROGZephyrusS17GX701LWS_GX701LWS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX701LWS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus S17 dmi.product.name: ROG Zephyrus S17 GX701LWS_GX701LWS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987249/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Changed in: hwe-next Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Lunar, $ git push l_cbd Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 8 threads Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done. Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-915de03d6ecf-V1nm remote: * 9/9 workers busy, 0 builds queued remote: 2023-11-20 16:00:11 kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK remote: 2023-11-20 15:59:57 kobako-lunar-915de03d6ecf-V1nm/arm64/BUILD-OK remote: 2023-11-20 15:55:14 kobako-lunar-915de03d6ecf-V1nm/armhf/BUILD-OK remote: 2023-11-20 15:55:26 kobako-lunar-915de03d6ecf-V1nm/ppc64el/BUILD-OK remote: 2023-11-20 15:47:17 kobako-lunar-915de03d6ecf-V1nm/s390x/BUILD-OK remote: To cbd.kernel:lunar.git * [new branch]ubuntu_lunar_next -> ubuntu_lunar_next Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency-hwe-5.15/5.15.0.91.101~20.04.45)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15 (5.15.0.91.101~20.04.45) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-lowlatency-hwe-5.15/5.15.0-91.101~20.04.1 (amd64, 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/focal/update_excuses.html#linux-meta-lowlatency-hwe-5.15 [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 packaging 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 2042569] Re: Jammy update: v6.1.58 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2042569 Title: Jammy update: v6.1.58 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.58 upstream stable release from git://git.kernel.org/ Linux 6.1.58 lib/test_meminit: fix off-by-one error in test_pages() Revert "NFS: Fix error handling for O_DIRECT write scheduling" Revert "NFS: Fix O_DIRECT locking issues" Revert "NFS: More O_DIRECT accounting fixes for error paths" Revert "NFS: Use the correct commit info in nfs_join_page_group()" Revert "NFS: More fixes for nfs_direct_write_reschedule_io()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2042569/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Changed in: linux-oem-6.1 (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-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2042572] Re: Jammy update: v6.1.59 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2042572 Title: Jammy update: v6.1.59 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.59 upstream stable release from git://git.kernel.org/ Linux 6.1.59 ALSA: hda/realtek - Fixed two speaker platform powerpc/64e: Fix wrong test in __ptep_test_and_clear_young() powerpc/8xx: Fix pte_access_permitted() for PAGE_NONE dmaengine: mediatek: Fix deadlock caused by synchronize_irq() dmaengine: idxd: use spin_lock_irqsave before wait_event_lock_irq x86/alternatives: Disable KASAN in apply_alternatives() usb: cdnsp: Fixes issue with dequeuing not queued requests usb: gadget: ncm: Handle decoding of multiple NTB's in unwrap call usb: gadget: udc-xilinx: replace memcpy with memcpy_toio usb: typec: ucsi: Clear EVENT_PENDING bit if ucsi_send_command fails usb: typec: altmodes/displayport: Signal hpd low when exiting mode counter: microchip-tcb-capture: Fix the use of internal GCLK logic counter: chrdev: fix getting array extensions scsi: ufs: core: Correct clear TM error log pinctrl: avoid unsafe code pattern in find_pinctrl() dma-buf: add dma_fence_timestamp helper cgroup: Remove duplicates in cgroup v1 tasks file usb: typec: ucsi: Use GET_CAPABILITY attributes data to set power supply scope nfp: flower: avoid rmmod nfp crash issues mctp: perform route lookups under a RCU read-side lock tee: amdtee: fix use-after-free vulnerability in amdtee_close_session Input: goodix - ensure int GPIO is in input for gpio_count == 1 && gpio_int_idx == 0 case Input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table Input: xpad - add PXN V900 support Input: psmouse - fix fast_reconnect function for PS/2 mode Input: powermate - fix use-after-free in powermate_config_complete ceph: fix type promotion bug on 32bit systems ceph: fix incorrect revoked caps assert in ceph_fill_file_size() libceph: use kernel_connect() powerpc/47x: Fix 47x syscall return crash thunderbolt: Restart XDomain discovery handshake after failure thunderbolt: Check that lane 1 is in CL0 before enabling lane bonding thunderbolt: Workaround an IOMMU fault on certain systems with Intel Maple Ridge mcb: remove is_added flag from mcb_device struct x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs perf/x86/lbr: Filter vsyscall addresses ksmbd: not allow to open file if delelete on close bit is set ACPI: EC: Add quirk for the HP Pavilion Gaming 15-dk1xxx ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CBA drm/amd/display: Don't set dpms_off for seamless boot drm/amdgpu: add missing NULL check drm/atomic-helper: relax unregistered connector check arm64: dts: mediatek: mt8195-demo: update and reorder reserved memory regions arm64: dts: mediatek: mt8195-demo: fix the memory size to 8GB iio: addac: Kconfig: update ad74413r selections iio: pressure: ms5611: ms5611_prom_is_valid false negative bug iio: pressure: dps310: Adjust Timeout Settings iio: admv1013: add mixer_vgate corner cases iio: dac: ad3552r: Correct device IDs iio: adc: imx8qxp: Fix address for command buffer registers iio: imu: bno055: Fix missing Kconfig dependencies iio: pressure: bmp280: Fix NULL pointer exception usb: musb: Modify the "HWVers" register address usb: musb: Get the musb_qh poniter after musb_giveback usb: hub: Guard against accesses to uninitialized BOS descriptors usb: cdns3: Modify the return value of cdns_set_active () to void when CONFIG_PM_SLEEP is disabled usb: dwc3: Soft reset phy on probe for host net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer dmaengine: stm32-mdma: set in_flight_bytes in case CRQA flag is set dmaengine: stm32-mdma: use Link Address Register to compute residue dmaengine: stm32-dma: fix residue in case of MDMA chaining dmaengine: stm32-dma: fix stm32_dma_prep_slave_sg in case of MDMA chaining dmaengine: stm32-mdma: abort resume if no ongoing transfer tcp: enforce receive buffer memory limits by allowing the tcp window to
[Kernel-packages] [Bug 2042577] Re: Jammy update: v6.1.60 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2042577 Title: Jammy update: v6.1.60 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.60 upstream stable release from git://git.kernel.org/ Linux 6.1.60 selftests: mptcp: join: no RST when rm subflow/addr selftests: mptcp: join: correctly check for no RST mptcp: avoid sending RST when closing the initial subflow Bluetooth: hci_sock: Correctly bounds check and pad HCI_MON_NEW_INDEX name Bluetooth: hci_sock: fix slab oob read in create_monitor_event net: move altnames together with the netdevice phy: mapphone-mdm6600: Fix pinctrl_pm handling for sleep pins phy: mapphone-mdm6600: Fix runtime PM for remove phy: mapphone-mdm6600: Fix runtime disable on probe gpio: vf610: mask the gpio irq in system suspend and support wakeup gpio: vf610: make irq_chip immutable tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols kallsyms: Add helper kallsyms_on_each_match_symbol() kallsyms: Reduce the memory occupied by kallsyms_seqs_of_names[] serial: 8250: omap: convert to modern PM ops serial: 8250: omap: Move uart_write() inside PM section drm/bridge: ti-sn65dsi86: Associate DSI device lifetime with auxiliary device ASoC: pxa: fix a memory leak in probe() gpio: vf610: set value before the direction to avoid a glitch platform/x86: asus-wmi: Map 0x2a code, Ignore 0x2b and 0x2c events platform/x86: asus-wmi: Only map brightness codes when using asus-wmi backlight control platform/x86: asus-wmi: Change ASUS_WMI_BRN_DOWN code from 0x20 to 0x2e platform/x86: intel-uncore-freq: Conditionally create attribute for read frequency platform/surface: platform_profile: Propagate error if profile registration fails s390/cio: fix a memleak in css_alloc_subchannel selftests/ftrace: Add new test case which checks non unique symbol s390/pci: fix iommu bitmap allocation perf: Disallow mis-matched inherited group reads USB: serial: option: add Fibocom to DELL custom modem FM101R-GL USB: serial: option: add entry for Sierra EM9191 with new firmware USB: serial: option: add Telit LE910C4-WWX 0x1035 composition HID: input: map battery system charging KVM: x86/mmu: Stop zapping invalidated TDP MMU roots asynchronously nvme-rdma: do not try to stop unallocated queues nvmet-auth: complete a request only after freeing the dhchap pointers nvme-pci: add BOGUS_NID for Intel 0a54 device nvme: sanitize metadata bounce buffer for reads nfs42: client needs to strip file mode's suid/sgid bit after ALLOCATE op ACPI: irq: Fix incorrect return value in acpi_register_gsi() NFSv4.1: fixup use EXCHGID4_FLAG_USE_PNFS_DS for DS server pNFS/flexfiles: Check the layout validity in ff_layout_mirror_prepare_stats pNFS: Fix a hang in nfs4_evict_inode() Revert "pinctrl: avoid unsafe code pattern in find_pinctrl()" mmc: core: Capture correct oemid-bits for eMMC cards mmc: core: sdio: hold retuning if sdio in 1-bit mode mmc: mtk-sd: Use readl_poll_timeout_atomic in msdc_reset_hw mmc: sdhci-pci-gli: fix LPM negotiation so x86/S0ix SoCs can suspend dt-bindings: mmc: sdhci-msm: correct minimum number of clocks mtd: physmap-core: Restore map_rom fallback mtd: spinand: micron: correct bitmask for ecc status mtd: rawnand: arasan: Ensure program page operations are successful mtd: rawnand: marvell: Ensure program page operations are successful mtd: rawnand: pl353: Ensure program page operations are successful mtd: rawnand: qcom: Unmap the right resource upon probe failure net/smc: fix smc clc failed issue when netdevice not in init_net tcp_bpf: properly release resources on error paths selftests: openvswitch: Add version check for pyroute2 Bluetooth: hci_event: Fix using memcmp when comparing keys ice: Remove redundant pci_enable_pcie_error_reporting() tcp: allow again tcp_disconnect() when threads are waiting net/tls: split tls_rx_reader_lock net/mlx5e: Don't offload internal port if filter device is out device net/mlx5: Handle fw tracer change ownership event based on MTRC net/mlx5: E-switch, register
[Kernel-packages] [Bug 2042580] Re: Jammy update: v6.1.61 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2042580 Title: Jammy update: v6.1.61 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.61 upstream stable release from git://git.kernel.org/ Linux 6.1.61 objtool/x86: add missing embedded_insn check ext4: avoid overlapping preallocations due to overflow ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow ext4: add two helper functions extent_logical_end() and pa_logical_end() platform/x86: Add s2idle quirk for more Lenovo laptops clk: Sanitize possible_parent_show to Handle Return Value of of_clk_get_parent_name sparc32: fix a braino in fault handling in csum_and_copy_..._user() perf/core: Fix potential NULL deref x86/cpu: Add model number for Intel Arrow Lake mobile processor x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility nvmem: imx: correct nregs for i.MX6UL nvmem: imx: correct nregs for i.MX6SLL nvmem: imx: correct nregs for i.MX6ULL misc: fastrpc: Unmap only if buffer is unmapped from DSP misc: fastrpc: Clean buffers on remote invocation failures misc: fastrpc: Free DMA handles for RPC calls with no arguments misc: fastrpc: Reset metadata buffer to avoid incorrect free tracing/kprobes: Fix the description of variable length arguments i2c: aspeed: Fix i2c bus hang in slave read i2c: stm32f7: Fix PEC handling in case of SMBUS transfers i2c: muxes: i2c-demux-pinctrl: Use of_get_i2c_adapter_by_node() i2c: muxes: i2c-mux-gpmux: Use of_get_i2c_adapter_by_node() i2c: muxes: i2c-mux-pinctrl: Use of_get_i2c_adapter_by_node() iio: adc: xilinx-xadc: Correct temperature offset/scale for UltraScale iio: adc: xilinx-xadc: Don't clobber preset voltage/temperature thresholds iio: exynos-adc: request second interupt only when touchscreen mode is used iio: afe: rescale: Accept only offset channels io_uring/fdinfo: lock SQ thread while retrieving thread cpu/pid kasan: print the original fault addr when access invalid shadow blk-throttle: check for overflow in calculate_bytes_allowed scsi: sd: Introduce manage_shutdown device flag iavf: in iavf_down, disable queues when removing the driver drm/logicvc: Kconfig: select REGMAP and REGMAP_MMIO i40e: Fix wrong check for I40E_TXR_FLAGS_WB_ON_ITR gtp: fix fragmentation needed check with gso gtp: uapi: fix GTPA_MAX tcp: fix wrong RTO timeout when received SACK reneging r8152: Release firmware if we have an error in probe r8152: Cancel hw_phy_work if we have an error in probe r8152: Run the unload routine if we have errors during probe r8152: Increase USB control msg timeout to 5000ms as per spec net: usb: smsc95xx: Fix uninit-value access in smsc95xx_read_reg net: ieee802154: adf7242: Fix some potential buffer overflow in adf7242_stats_show() net: ethernet: adi: adin1110: Fix uninitialized variable igc: Fix ambiguity in the ethtool advertising neighbour: fix various data-races igb: Fix potential memory leak in igb_add_ethtool_nfc_entry treewide: Spelling fix in comment i40e: Fix I40E_FLAG_VF_VLAN_PRUNING value iavf: initialize waitqueues before starting watchdog_task r8169: fix the KCSAN reported data race in rtl_rx while reading desc->opts1 r8169: fix the KCSAN reported data-race in rtl_tx while reading TxDescArray[entry].opts1 r8169: fix the KCSAN reported data-race in rtl_tx() while reading tp->cur_tx clk: ti: Fix missing omap5 mcbsp functional clock and aliases clk: ti: Fix missing omap4 mcbsp functional clock and aliases firmware/imx-dsp: Fix use_after_free in imx_dsp_setup_channels() ARM: OMAP: timer32K: fix all kernel-doc warnings drm/dp_mst: Fix NULL deref in get_mst_branch_device_by_guid_helper() drm/amd: Disable ASPM for VI w/ all Intel systems drm/i915/pmu: Check if pmu is closed before stopping event nfsd: lock_rename() needs both directories to live on the same fs maple_tree: add GFP_KERNEL to allocations in mas_expected_entries() hugetlbfs: extend hugetlb_vma_lock to private VMAs mm/migrate: fix do_pages_move for compat pointers mm/page_alloc: correct start page when guard page
[Kernel-packages] [Bug 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
** Changed in: linux-oem-6.1 (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-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html which is included in v6.7-rc1 7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2044003] Re: Don't produce linux-*-tools-{common, host} binary packages
** Description changed:
+ [Impact]
+
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these.
+
+ [Test Case]
+
+ Check list of built binary packages in LP.
+
+ [Where Problems Could Occur]
+
+ Already installed packages won't upgrade and become stale and their
+ contents have namespace collisions with the generic/main linux-
+ tools-{common,host} packages.
** Description changed:
[Impact]
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
- source package should produce these.
+ source package should produce these. These packages result in install
+ failures of the regular linux-tools-{common,host} packages.
[Test Case]
Check list of built binary packages in LP.
[Where Problems Could Occur]
- Already installed packages won't upgrade and become stale and their
- contents have namespace collisions with the generic/main linux-
- tools-{common,host} packages.
+ Already installed packages won't upgrade and become stale.
** Description changed:
[Impact]
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these. These packages result in install
failures of the regular linux-tools-{common,host} packages.
[Test Case]
- Check list of built binary packages in LP.
+ Check list of built binary packages in LP and verify the packages are
+ not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-laptop in Ubuntu.
https://bugs.launchpad.net/bugs/2044003
Title:
Don't produce linux-*-tools-{common,host} binary packages
Status in linux-laptop package in Ubuntu:
New
Bug description:
[Impact]
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these. These packages result in install
failures of the regular linux-tools-{common,host} packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2044003/+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 2043981] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post-installation installé a renvo
/usr/sbin/update-initramfs: 175: awk: not found That's a basic utility. How did you end up not having this installed? ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2043981 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post- installation installé a renvoyé un état de sortie d'erreur 127 Status in linux-firmware package in Ubuntu: Invalid Bug description: le package ne s'installe pas ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.22 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 AlsaInfo: Error: command ['/usr/sbin/alsa-info', '--stdout', '--no-upload'] failed with exit code 1: This script requires awk utility to continue. ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guigrehi 1608 F pulseaudio /dev/snd/controlC0: guigrehi 1608 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Nov 20 11:36:50 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.2 ErrorMessage: le sous-processus paquet linux-firmware script post-installation installé a renvoyé un état de sortie d'erreur 127 InstallationDate: Installed on 2023-07-26 (116 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Latitude E7250 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=9e893492-0bb7-4770-ae1a-e11afb05f869 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. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post-installation installé a renvoyé un état de sortie d'erreur 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2015 dmi.bios.release: 65.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0TVD2T dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/19/2015:br65.8:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0TVD2T:rvrA01:cvnDellInc.:ct9:cvr:sku062D: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2043981/+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 2044061] Re: Vertical and horizontal lines appearing since update
** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Summary changed: - Vertical and horizontal lines appearing since update + [amdgpu] Green vertical and horizontal lines appearing since update ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags added: amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2044061 Title: [amdgpu] Green vertical and horizontal lines appearing since update Status in linux-hwe-6.2 package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Did sudo apt update && upgrade, now getting vertical and horizontal visual artifacts -Tried installing amd drivers -Tried using an older kernel Still no luck; definitely 100% not a hardware issue, machine is dual boot and they do not appear on the windows side. It's related to the update. It occurs particularly frequently if I'm writing code or moving windows around. Attaching a picture to try and show it (it's hard to catch on pictures and I don't think it shows up in a screen shot). It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 21:30:01 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: amdgpu/6.2.4-1683306.22.04, 6.2.0-36-generic, x86_64: installed amdgpu/6.2.4-1683306.22.04, 6.2.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 Armor 4G OC [1462:3418] InstallationDate: Installed on 2023-10-30 (21 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=6628c08f-0884-4517-a532-a5ba1ff5653e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M.70 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450-A PRO MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 4.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: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM.70:bd06/17/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr4.0:rvnMicro-StarInternationalCo.,Ltd:rnB450-APROMAX(MS-7B86):rvr4.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr4.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 4.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2044061/+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 2044027] Re: keyboard , mouse and black screen after rebooting on ubuntu os only
Please ignore "ACPI Error: ..." because it's really just a warning about
a BIOS bug, which is very common and not really a problem to Ubuntu.
Please also describe in more detail what the remaining problem is, and
run:
apport-collect 2044027
to automatically provide system information.
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
** 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/2044027
Title:
keyboard , mouse and black screen after rebooting on ubuntu os only
Status in linux package in Ubuntu:
Incomplete
Bug description:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell
desktop environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond
end of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with
the issue above , at the end when performing a reboot process after rebooting
my device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard
are working fine on ubuntu systems with all versions and all other os
including windows os
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044027/+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 2044027] [NEW] keyboard , mouse and black screen after rebooting on ubuntu os only
You have been subscribed to a public bug:
For input devices : gnome-shell
For rebooting process : init system
the following is what appears on my screen when i login to gnome-shell desktop
environment (ubuntu-desktop) the below message appears twice times
("ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error
(AE_AML_PACKAGE_LIMIT) (20210331/psparse-529)
ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x00066) is beyond end
of object (length 0xA) (20210331/exoparg2-393)
__common_interrupt: 1.55 No irq handler for vector")
At the start process : both keyboard and mouse internal doesnot work with the
issue above , at the end when performing a reboot process after rebooting my
device it appears on my screen a black screen resulting to turning off from
the btn on my laptop. always this incident happens with me and only on ubuntu
16.04 and later systems the problem occurs while on other oses the problem
does not occur any more (rebooting keyboard and mouse "internal")
note : secondary storage ,optical disks external devices like keyboard
are working fine on ubuntu systems with all versions and all other os
including windows os
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
keyboard , mouse and black screen after rebooting on ubuntu os only
https://bugs.launchpad.net/bugs/2044027
You received this bug notification because you are a member of Kernel Packages,
which is subscribed to linux in Ubuntu.
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
** Changed in: bluez (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
Confirmed
Status in bluez package in Debian:
New
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 2044047] Re: 8BitDo Ultimate Wired Controller new USB device found, USB disconnect
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: kernel-input -- 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/2044047 Title: 8BitDo Ultimate Wired Controller new USB device found, USB disconnect Status in linux package in Ubuntu: New Bug description: Ubuntu 23.10 with Kernel 6.5.0-10-generic x86_64 x86_64 Processor 13th Gen Intel® Core™ i5-13500H × 16 While having an 8BitDo Ultimate Wired Controller connected and checking dmesg I see notices of: [ 265.056852] input: 8BitDo 8BitDo Ultimate Wired Controller as /devices/pci:00/:00:14.0/usb3/3-3/3-3.2/3-3.2.3/3-3.2.3:1.0/0003:2DC8:3011.0038/input/input81 [ 265.057126] hid-generic 0003:2DC8:3011.0038: input,hidraw11: USB HID v1.11 Gamepad [8BitDo 8BitDo Ultimate Wired Controller] on usb-:00:14.0-3.2.3/input0 [ 270.500065] usb 3-3.2.3: USB disconnect, device number 58 [ 270.823357] usb 3-3.2.3: new full-speed USB device number 59 using xhci_hcd [ 270.934625] usb 3-3.2.3: New USB device found, idVendor=2dc8, idProduct=3011, bcdDevice= 2.00 [ 270.934630] usb 3-3.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 270.934632] usb 3-3.2.3: Product: 8BitDo Ultimate Wired Controller [ 270.934633] usb 3-3.2.3: Manufacturer: 8BitDo [ 270.934634] usb 3-3.2.3: SerialNumber: 2102E14AB302 This message is been sent nearly every 1 second, slowing the system down causing micro stuttering. This only happens while the controller is connected. The controller is connected to a Sabrent USB 2.0 hub, Bus 003 Device 006: ID 14cd:8601 Super Top 4-Port hub. Note that the issue is still present while the controller is connected directly to the Laptop USB port. I haven't tested with a different Kernel version to determine if only 6.5.0-10 is affected - I was hoping someone with more experience could look at this issue. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044047/+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 2044047] [NEW] 8BitDo Ultimate Wired Controller new USB device found, USB disconnect
You have been subscribed to a public bug: Ubuntu 23.10 with Kernel 6.5.0-10-generic x86_64 x86_64 Processor 13th Gen Intel® Core™ i5-13500H × 16 While having an 8BitDo Ultimate Wired Controller connected and checking dmesg I see notices of: [ 265.056852] input: 8BitDo 8BitDo Ultimate Wired Controller as /devices/pci:00/:00:14.0/usb3/3-3/3-3.2/3-3.2.3/3-3.2.3:1.0/0003:2DC8:3011.0038/input/input81 [ 265.057126] hid-generic 0003:2DC8:3011.0038: input,hidraw11: USB HID v1.11 Gamepad [8BitDo 8BitDo Ultimate Wired Controller] on usb-:00:14.0-3.2.3/input0 [ 270.500065] usb 3-3.2.3: USB disconnect, device number 58 [ 270.823357] usb 3-3.2.3: new full-speed USB device number 59 using xhci_hcd [ 270.934625] usb 3-3.2.3: New USB device found, idVendor=2dc8, idProduct=3011, bcdDevice= 2.00 [ 270.934630] usb 3-3.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 270.934632] usb 3-3.2.3: Product: 8BitDo Ultimate Wired Controller [ 270.934633] usb 3-3.2.3: Manufacturer: 8BitDo [ 270.934634] usb 3-3.2.3: SerialNumber: 2102E14AB302 This message is been sent nearly every 1 second, slowing the system down causing micro stuttering. This only happens while the controller is connected. The controller is connected to a Sabrent USB 2.0 hub, Bus 003 Device 006: ID 14cd:8601 Super Top 4-Port hub. Note that the issue is still present while the controller is connected directly to the Laptop USB port. I haven't tested with a different Kernel version to determine if only 6.5.0-10 is affected - I was hoping someone with more experience could look at this issue. Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kernel-bug -- 8BitDo Ultimate Wired Controller new USB device found, USB disconnect https://bugs.launchpad.net/bugs/2044047 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950792] Re: No boot possible - Cannot open root device
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Expired Status in linux package in Ubuntu: Expired Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 1950792] Re: No boot possible - Cannot open root device
[Expired for MAAS because there has been no activity for 60 days.] ** Changed in: maas Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Expired Status in linux package in Ubuntu: Expired Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+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 2038837] Re: kernel: evict_inodes inode 000000006048f67c, i_count = 1, was skipped!
Another data point.
This is only happenning on upgrade to mantic / kernel 6.5.0
Root filesystem on btrfs. fstab line:
UID=7ab3704a-006c-4cc2-b93b-fb8c4bb4768e / btrfs
subvol=@,ssd,compress=zstd:9,relatime 0 1
Galago Ultra Pro (Clevo W740SU) Laptop. intel i7-4750HQ, 16G, SSD:
TS256GMSA230S (sata)
Let me know if any extra info needed.
** Attachment added: "Screenshot_20231121_121245.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038837/+attachment/5721489/+files/Screenshot_20231121_121245.png
--
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/2038837
Title:
kernel: evict_inodes inode 6048f67c, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Bug description:
This gets spammed after I shutdown, though the inode values are
different for each line. Had to phyically reboot to get it to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: yamiyuki 6735 F wireplumber
/dev/snd/controlC0: yamiyuki 6735 F wireplumber
/dev/snd/controlC1: yamiyuki 6735 F wireplumber
/dev/snd/seq:yamiyuki 6731 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Oct 9 11:32:47 2023
InstallationDate: Installed on 2022-01-14 (634 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.5.0-9-generic
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-30 (9 days ago)
dmi.bios.date: 02/08/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F5a
dmi.board.asset.tag: Default string
dmi.board.name: X570S AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570S AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038837/+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 2039925] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721484/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721481/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721485/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721483/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721486/+files/acpidump.txt
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
+ [Fix]
+
+ V4 patchset under review:
+
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
+
+ [Test Case]
+
+ With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
+ ```
+ rtsx_pci :56:00.0: enabling device ( -> 0002)
+ ```
+
+ [Where problems could occur]
+
+ New hardware, expecting all possible way to go wrong.
+
+ [Other Info]
+
+ Nominated for oem-6.5 and Noble.
+
+ == original bug report ==
+
+ Missing Realtek RTS5264 SD 7.0 cardreader support:
+ ```
+ $ lspci -nnnk
+ :56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
+ Subsystem: Dell Device [1028:0cc8]
+ Kernel driver in use: rtsx_pci
+ Kernel modules: rtsx_pci
+ ```
+
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
- {
-"result": "skip"
- }
+ {
+ "result": "skip"
+ }
DistributionChannelDescriptor:
- # This is the distribution channel descriptor for the OEM CDs
- # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
- canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
+ # This is the distribution channel descriptor for the OEM CDs
+ # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
+ canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
- lono wireless extensions.
-
- enx00e04c691040 no wireless extensions.
-
- wlp1s0f0 no wireless extensions.
+ lono wireless extensions.
+
+ enx00e04c691040 no wireless extensions.
+
+ wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
- linux-restricted-modules-6.5.0-9008-oem N/A
- linux-backports-modules-6.5.0-9008-oem N/A
- linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
+ linux-restricted-modules-6.5.0-9008-oem N/A
+ linux-backports-modules-6.5.0-9008-oem N/A
+ linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
[Kernel-packages] [Bug 2039925] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721482/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721480/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721479/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721477/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721478/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721476/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721475/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721474/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721473/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] HookError_ubuntu.txt
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721471/+files/HookError_ubuntu.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721472/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721470/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721469/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] AlsaInfo.txt
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2039925/+attachment/5721468/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-11-15 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enx00e04c691040 no wireless extensions.
wlp1s0f0 no wireless extensions.
MachineType: Dell Inc. Precision 5690
Package: linux-oem-6.5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9008-oem N/A
linux-backports-modules-6.5.0-9008-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
Tags: jammy
Uname: Linux 6.5.0-9008-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/26/2023
dmi.bios.release: 0.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.2.12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
dmi.product.family: Precision
dmi.product.name: Precision 5690
dmi.product.sku: 0CC8
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2039925] Re: Realtek RTS5264 SD 7.0 cardreader support
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-November/147060.html
(unstable, noble)
* http://10.131.201.69/kernel/jammy-linux-oem/pulls/89 (oem-6.5)
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux (Ubuntu Mantic)
Status: Triaged => Won't Fix
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Tags added: apport-collected jammy
** Description changed:
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
- V4 patchset: https://patchwork.kernel.org/project/linux-
- mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
+ V4 patchset:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CasperMD5json:
+ {
+"result": "skip"
+ }
+ DistributionChannelDescriptor:
+ # This is the distribution channel descriptor for the OEM CDs
+ # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
+ canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-magmar+X114
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2023-11-15 (5 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
+ IwConfig:
+ lono wireless extensions.
+
+ enx00e04c691040 no wireless extensions.
+
+ wlp1s0f0 no wireless extensions.
+ MachineType: Dell Inc. Precision 5690
+ Package: linux-oem-6.5
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9008-oem
root=UUID=b6f2aa0f-7cf0-4307-a7ff-d6af8316c896 ro automatic-oem-config quiet
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-9008.8+exp.31-oem 6.5.3
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+ linux-restricted-modules-6.5.0-9008-oem N/A
+ linux-backports-modules-6.5.0-9008-oem N/A
+ linux-firmware
20220329.git681281e4-0ubuntu3.22+exp.90
+ Tags: jammy
+ Uname: Linux 6.5.0-9008-oem x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 10/26/2023
+ dmi.bios.release: 0.2
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 0.2.12
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.ec.firmware.release: 0.0
+ dmi.modalias:
dmi:bvnDellInc.:bvr0.2.12:bd10/26/2023:br0.2:efr0.0:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0CC8:
+ dmi.product.family: Precision
+ dmi.product.name: Precision 5690
+ dmi.product.sku: 0CC8
+ dmi.sys.vendor: Dell Inc.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039925
Title:
Realtek RTS5264 SD 7.0 cardreader support
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
```
[Fix]
V4 patchset under review:
https://patchwork.kernel.org/project/linux-mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/
[Test Case]
With kernel driver probed and loaded successfully, there should be a line in
the dmesg:
```
rtsx_pci :56:00.0: enabling device ( -> 0002)
```
[Where problems could occur]
New hardware, expecting all possible way to go wrong.
[Other Info]
Nominated for oem-6.5 and Noble.
== original bug report ==
Missing Realtek RTS5264 SD 7.0 cardreader support:
```
$ lspci -nnnk
:56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device
[10ec:5264] (rev 01)
Subsystem: Dell Device [1028:0cc8]
Kernel driver in use:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oracle/6.2.0.1017.17)
All autopkgtests for the newly accepted linux-meta-oracle (6.2.0.1017.17) for lunar have finished running. The following regressions have been reported in tests triggered by the package: systemd/252.5-2ubuntu3.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/lunar/update_excuses.html#linux-meta-oracle [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 packaging 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 2039925] Re: Realtek RTS5264 SD 7.0 cardreader support
** Summary changed: - Include SD 7.0 card Realtek RTS5264 support + Realtek RTS5264 SD 7.0 cardreader support ** Description changed: - Here is upstream submit link from Realtek: + Missing Realtek RTS5264 SD 7.0 cardreader support: + ``` + $ lspci -nnnk + :56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5264] (rev 01) + Subsystem: Dell Device [1028:0cc8] + Kernel driver in use: rtsx_pci + Kernel modules: rtsx_pci + ``` - https://www.spinics.net/lists/kernel/msg4973332.html - https://www.spinics.net/lists/kernel/msg4973328.html + V4 patchset: https://patchwork.kernel.org/project/linux- + mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039925 Title: Realtek RTS5264 SD 7.0 cardreader support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Triaged Status in linux source package in Mantic: Triaged Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: Missing Realtek RTS5264 SD 7.0 cardreader support: ``` $ lspci -nnnk :56:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5264] (rev 01) Subsystem: Dell Device [1028:0cc8] Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci ``` V4 patchset: https://patchwork.kernel.org/project/linux- mmc/patch/bf45a73f01cc43669dc3796ccff25...@realtek.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039925/+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 2043542] Re: Add MT7925 WiFi/BT support
Just a note the firmware for MT7925 is here https://launchpad.net/bugs/2042496 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043542 Title: Add MT7925 WiFi/BT support Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Incomplete Bug description: * WiFi - https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/ * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs * 3c1199134874 wifi: mt76: connac: add more unified command IDs * 473f26fb167e wifi: mt76: connac: add data field in struct tlv * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925 * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset * Bluetooth - https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1027.27
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-linux-oem-6.1' to 'verification-done-
jammy-linux-oem-6.1'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy-
linux-oem-6.1'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2
verification-needed-jammy-linux-oem-6.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1027.27 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-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html which is included in v6.7-rc1 7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter rules to enable features. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042912/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1027.27 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-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2037212] Re: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
Confirmed
Status in bluez package in Debian:
New
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037212/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
I tested it again, and at the moment I reproduce this issue with a
xwayland window (in this case, Discord app), but all gnome was stable,
which is strange (but good). See screenshot attached.
** Attachment added: "Captura desde 2023-11-21 00-42-42.png"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2038998/+attachment/5721350/+files/Captura%20desde%202023-11-21%2000-42-42.png
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 2042546] Re: Include cifs.ko in linux-modules package
This bug is awaiting verification that the linux- starfive-6.2/6.2.0-1009.10~22.04.1 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-linux- starfive-6.2' to 'verification-done-jammy-linux-starfive-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux- starfive-6.2' to 'verification-failed-jammy-linux-starfive-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-starfive-6.2-v2 verification-needed-jammy-linux-starfive-6.2 -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2042573] Re: arm64 atomic issues cause disk corruption
This bug is awaiting verification that the linux-gcp/6.5.0-1009.9 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-mantic-linux-gcp' to 'verification-done-mantic- linux-gcp'. If the problem still exists, change the tag 'verification- needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-gcp-v2 verification-needed-mantic-linux-gcp -- 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/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+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 2042573] Re: arm64 atomic issues cause disk corruption
This bug is awaiting verification that the linux-gcp/6.5.0-1009.9 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-mantic-linux-gcp' to 'verification-done-mantic- linux-gcp'. If the problem still exists, change the tag 'verification- needed-mantic-linux-gcp' to 'verification-failed-mantic-linux-gcp'. 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/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+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 2042573] Re: arm64 atomic issues cause disk corruption
This bug is awaiting verification that the linux-azure/6.5.0-1009.9 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-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1008.8 --- linux-oem-6.5 (6.5.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1008.8 -proposed tracker (LP: #2041878) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper * System hang after unplug/plug DP monitor with AMD W7500 card (LP: #2042912) - SAUCE: drm/amd/pm: Fix error of MACO flag setting code * Fix after-suspend-mediacard/sdhc-insert test failed (LP: #2042500) - SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on (LP: #2042385) - SAUCE: r8169: Add quirks to enable ASPM on Dell platforms * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Miscellaneous Ubuntu changes - [Packaging] Add ppa2 to getabis [ Ubuntu: 6.5.0-13.13 ] * mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652) * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery [ Ubuntu: 6.5.0-11.11 ] * mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879) * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Timo Aaltonen Fri, 10 Nov 2023 13:04:39 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package:
[Kernel-packages] [Bug 2039151] Re: Support speaker mute hotkey for Cirrus CS35L41 HDA codec
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1026.26 --- linux-oem-6.1 (6.1.0-1026.26) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1026.26 -proposed tracker (LP: #2041950) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - [Packaging] update helper scripts * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151) - ALSA: hda: cs35l41: Support systems with missing _DSD properties - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties - ALSA: hda: cs35l41: Add notification support into component binding - ALSA: hda/realtek: Support ACPI Notification framework via component binding - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-5178 - nvmet-tcp: Fix a possible UAF in queue intialization setup * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * CVE-2023-5717 - perf: Disallow mis-matched inherited group reads -- Timo Aaltonen Wed, 01 Nov 2023 14:45:18 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5178 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5717 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2039151 Title: Support speaker mute hotkey for Cirrus CS35L41 HDA codec Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Some systems use a special hotkey to mute speaker audio. On systems using CS35L41 HDA which have this hotkey, add a mechanism which uses ACPI notifications to detect whether the hotkey is triggered to switch the mute state. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/alsa-devel/87fs36egnv.wl-ti...@suse.de/T/#t. [Test Case] 1. Power on the machine with CS35L41 HDA and the speaker mute hotkey. 2. Verify the audio functions 3. Verify if the speaker can be mute/unmute by the hotkey. [Where problems could occur] Only affect specific laptops with the CS35L41 HDA and the speaker mute hotkey on keyboard. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2039151/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1026.26 --- linux-oem-6.1 (6.1.0-1026.26) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1026.26 -proposed tracker (LP: #2041950) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - [Packaging] update helper scripts * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151) - ALSA: hda: cs35l41: Support systems with missing _DSD properties - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties - ALSA: hda: cs35l41: Add notification support into component binding - ALSA: hda/realtek: Support ACPI Notification framework via component binding - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-5178 - nvmet-tcp: Fix a possible UAF in queue intialization setup * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * CVE-2023-5717 - perf: Disallow mis-matched inherited group reads -- Timo Aaltonen Wed, 01 Nov 2023 14:45:18 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5178 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5717 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5633 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw
[Kernel-packages] [Bug 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
This bug was fixed in the package linux-aws - 6.2.0-1016.16 --- linux-aws (6.2.0-1016.16) lunar; urgency=medium * lunar/linux-aws: 6.2.0-1016.16 -proposed tracker (LP: #2041881) * Include cifs.ko in linux-modules package (LP: #2042546) - [Packaging] Replace fs/cifs with fs/smb/client in inclusion list * Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization (LP: #2039191) - x86/boot: Move x86_cache_alignment initialization to correct spot [ Ubuntu: 6.2.0-37.38 ] * lunar/linux: 6.2.0-37.38 -proposed tracker (LP: #2041899) * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-25775 - RDMA/irdma: Prevent zero-length STAG registration * CVE-2023-45871 - igb: set max size RX buffer when store bad packet is enabled * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Tim Gardner Fri, 03 Nov 2023 01:41:32 -0600 ** Changed in: linux-aws (Ubuntu Lunar) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-25775 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45871 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Fix Released Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2039437] Re: linux-tools- should provide linux-tools
This bug was fixed in the package linux-meta-raspi - 6.2.0.1017.20
---
linux-meta-raspi (6.2.0.1017.20) lunar; urgency=medium
* Bump ABI 6.2.0-1017
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* linux-tools- should provide linux-tools (LP: #2039437)
- [Packaging] Add Provides: linux-{cloud-,}tools
-- Juerg Haefliger Mon, 13 Nov 2023
13:28:28 +0100
** Changed in: linux-meta-raspi (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2039437
Title:
linux-tools- should provide linux-tools
Status in linux-meta-raspi package in Ubuntu:
Invalid
Status in linux-meta-raspi source package in Focal:
Fix Released
Status in linux-meta-raspi source package in Jammy:
Fix Released
Status in linux-meta-raspi source package in Lunar:
Fix Released
Status in linux-meta-raspi source package in Mantic:
Fix Released
Bug description:
[Impact]
Missing 'Provides: linux-tools', results in:
$ sudo apt install linux-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-tools is a virtual package provided by:
linux-tools-virtual-hwe-22.04-edge 6.5.0.9.11
linux-tools-virtual-hwe-22.04 6.5.0.9.11
linux-tools-virtual 6.5.0.9.11
linux-tools-generic-hwe-22.04-edge 6.5.0.9.11
linux-tools-generic-hwe-22.04 6.5.0.9.11
linux-tools-generic 6.5.0.9.11
You should explicitly select one to install.
E: Package 'linux-tools' has no installation candidate
The above should list linux-tools-raspi on ARM.
[Fix]
Add 'Provides: linux-tools' and 'Provides: linux-cloud-tools' to all
meta packages that are missing them.
[Test Case]
See [Impact] above. The list of installation candidates should show
the fixed meta package name.
[Regression Potential]
Can't think of any problems this might cause. Most meta packages are
correct and we would have noticed issues by now (I hope).
[Additional Notes]
Affected series/metas:
focal/linux-meta-azure-5.15
focal/linux-meta-azure-fde-5.15
focal/linux-meta-azure
focal/linux-meta-denver
focal/linux-meta-kvm
focal/linux-meta-raspi
jammy/linux-meta-azure-6.2
jammy/linux-meta-azure-6.5
jammy/linux-meta-azure-fde-6.2
jammy/linux-meta-azure-fde
jammy/linux-meta-azure
jammy/linux-meta-kvm
jammy/linux-meta-raspi
lunar/linux-meta-azure
lunar/linux-meta-kvm
lunar/linux-meta-raspi
mantic/linux-meta-azure
mantic/linux-meta-raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/2039437/+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 2039437] Re: linux-tools- should provide linux-tools
This bug was fixed in the package linux-meta-raspi - 5.4.0.1098.128
---
linux-meta-raspi (5.4.0.1098.128) focal; urgency=medium
* Bump ABI 5.4.0-1098
* linux-tools- should provide linux-tools (LP: #2039437)
- [Packaging] Add Provides: linux-{cloud-,}tools
-- Manuel Diewald Thu, 02 Nov 2023
22:36:40 +0100
** Changed in: linux-meta-raspi (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux-meta-raspi (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2039437
Title:
linux-tools- should provide linux-tools
Status in linux-meta-raspi package in Ubuntu:
Invalid
Status in linux-meta-raspi source package in Focal:
Fix Released
Status in linux-meta-raspi source package in Jammy:
Fix Released
Status in linux-meta-raspi source package in Lunar:
Fix Released
Status in linux-meta-raspi source package in Mantic:
Fix Released
Bug description:
[Impact]
Missing 'Provides: linux-tools', results in:
$ sudo apt install linux-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-tools is a virtual package provided by:
linux-tools-virtual-hwe-22.04-edge 6.5.0.9.11
linux-tools-virtual-hwe-22.04 6.5.0.9.11
linux-tools-virtual 6.5.0.9.11
linux-tools-generic-hwe-22.04-edge 6.5.0.9.11
linux-tools-generic-hwe-22.04 6.5.0.9.11
linux-tools-generic 6.5.0.9.11
You should explicitly select one to install.
E: Package 'linux-tools' has no installation candidate
The above should list linux-tools-raspi on ARM.
[Fix]
Add 'Provides: linux-tools' and 'Provides: linux-cloud-tools' to all
meta packages that are missing them.
[Test Case]
See [Impact] above. The list of installation candidates should show
the fixed meta package name.
[Regression Potential]
Can't think of any problems this might cause. Most meta packages are
correct and we would have noticed issues by now (I hope).
[Additional Notes]
Affected series/metas:
focal/linux-meta-azure-5.15
focal/linux-meta-azure-fde-5.15
focal/linux-meta-azure
focal/linux-meta-denver
focal/linux-meta-kvm
focal/linux-meta-raspi
jammy/linux-meta-azure-6.2
jammy/linux-meta-azure-6.5
jammy/linux-meta-azure-fde-6.2
jammy/linux-meta-azure-fde
jammy/linux-meta-azure
jammy/linux-meta-kvm
jammy/linux-meta-raspi
lunar/linux-meta-azure
lunar/linux-meta-kvm
lunar/linux-meta-raspi
mantic/linux-meta-azure
mantic/linux-meta-raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/2039437/+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 2039437] Re: linux-tools- should provide linux-tools
This bug was fixed in the package linux-meta-raspi - 5.15.0.1043.41
---
linux-meta-raspi (5.15.0.1043.41) jammy; urgency=medium
* Bump ABI 5.15.0-1043
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
* linux-tools- should provide linux-tools (LP: #2039437)
- [Packaging] Add Provides: linux-{cloud-,}tools
-- Juerg Haefliger Mon, 13 Nov 2023
15:39:15 +0100
** Changed in: linux-meta-raspi (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2039437
Title:
linux-tools- should provide linux-tools
Status in linux-meta-raspi package in Ubuntu:
Invalid
Status in linux-meta-raspi source package in Focal:
Fix Released
Status in linux-meta-raspi source package in Jammy:
Fix Released
Status in linux-meta-raspi source package in Lunar:
Fix Released
Status in linux-meta-raspi source package in Mantic:
Fix Released
Bug description:
[Impact]
Missing 'Provides: linux-tools', results in:
$ sudo apt install linux-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-tools is a virtual package provided by:
linux-tools-virtual-hwe-22.04-edge 6.5.0.9.11
linux-tools-virtual-hwe-22.04 6.5.0.9.11
linux-tools-virtual 6.5.0.9.11
linux-tools-generic-hwe-22.04-edge 6.5.0.9.11
linux-tools-generic-hwe-22.04 6.5.0.9.11
linux-tools-generic 6.5.0.9.11
You should explicitly select one to install.
E: Package 'linux-tools' has no installation candidate
The above should list linux-tools-raspi on ARM.
[Fix]
Add 'Provides: linux-tools' and 'Provides: linux-cloud-tools' to all
meta packages that are missing them.
[Test Case]
See [Impact] above. The list of installation candidates should show
the fixed meta package name.
[Regression Potential]
Can't think of any problems this might cause. Most meta packages are
correct and we would have noticed issues by now (I hope).
[Additional Notes]
Affected series/metas:
focal/linux-meta-azure-5.15
focal/linux-meta-azure-fde-5.15
focal/linux-meta-azure
focal/linux-meta-denver
focal/linux-meta-kvm
focal/linux-meta-raspi
jammy/linux-meta-azure-6.2
jammy/linux-meta-azure-6.5
jammy/linux-meta-azure-fde-6.2
jammy/linux-meta-azure-fde
jammy/linux-meta-azure
jammy/linux-meta-kvm
jammy/linux-meta-raspi
lunar/linux-meta-azure
lunar/linux-meta-kvm
lunar/linux-meta-raspi
mantic/linux-meta-azure
mantic/linux-meta-raspi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/2039437/+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 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1008.8 --- linux-oem-6.5 (6.5.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1008.8 -proposed tracker (LP: #2041878) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper * System hang after unplug/plug DP monitor with AMD W7500 card (LP: #2042912) - SAUCE: drm/amd/pm: Fix error of MACO flag setting code * Fix after-suspend-mediacard/sdhc-insert test failed (LP: #2042500) - SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on (LP: #2042385) - SAUCE: r8169: Add quirks to enable ASPM on Dell platforms * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Miscellaneous Ubuntu changes - [Packaging] Add ppa2 to getabis [ Ubuntu: 6.5.0-13.13 ] * mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652) * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery [ Ubuntu: 6.5.0-11.11 ] * mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879) * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Timo Aaltonen Fri, 10 Nov 2023 13:04:39 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042060 Title: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume from suspend. The audio play and capture functions are not working after resume from S3. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/. [Test Case] 1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA . 2. Perform system suspend/resume at least 3 times. 3. Verify the audio functions, including playback and capture [Where problems could occur] Only affect specific laptops with the CS35L41 HDA. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042060/+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 2042060] Re: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1026.26 --- linux-oem-6.1 (6.1.0-1026.26) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1026.26 -proposed tracker (LP: #2041950) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - [Packaging] update helper scripts * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Support speaker mute hotkey for Cirrus CS35L41 HDA codec (LP: #2039151) - ALSA: hda: cs35l41: Support systems with missing _DSD properties - ALSA: hda: cs35l41: Fix the loop check in cs35l41_add_dsd_properties - ALSA: hda: cs35l41: Add notification support into component binding - ALSA: hda/realtek: Support ACPI Notification framework via component binding - ALSA: hda: cs35l41: Support mute notifications for CS35L41 HDA - ALSA: hda: cs35l41: Add read-only ALSA control for forced mute * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-5178 - nvmet-tcp: Fix a possible UAF in queue intialization setup * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * CVE-2023-5717 - perf: Disallow mis-matched inherited group reads -- Timo Aaltonen Wed, 01 Nov 2023 14:45:18 +0200 ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5178 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5717 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5633 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042060 Title: Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Few HP ZBook Fury 16 G9 laptops suffers audio problems after system resume from suspend. The audio play and capture functions are not working after resume from S3. [Fix] Backport the fix from Cirrus on linux-next https://lore.kernel.org/all/20231026150558.2105827-1-sbind...@opensource.cirrus.com/. [Test Case] 1. Power on the HP ZBook Fury 16 G9 machine with CS35L41 HDA . 2. Perform system suspend/resume at least 3 times. 3. Verify the audio functions, including playback and capture [Where problems could occur] Only affect specific laptops with the CS35L41 HDA. The impact is restricted. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042060/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1008.8 --- linux-oem-6.5 (6.5.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1008.8 -proposed tracker (LP: #2041878) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper * System hang after unplug/plug DP monitor with AMD W7500 card (LP: #2042912) - SAUCE: drm/amd/pm: Fix error of MACO flag setting code * Fix after-suspend-mediacard/sdhc-insert test failed (LP: #2042500) - SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on (LP: #2042385) - SAUCE: r8169: Add quirks to enable ASPM on Dell platforms * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Miscellaneous Ubuntu changes - [Packaging] Add ppa2 to getabis [ Ubuntu: 6.5.0-13.13 ] * mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652) * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery [ Ubuntu: 6.5.0-11.11 ] * mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879) * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Timo Aaltonen Fri, 10 Nov 2023 13:04:39 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5633 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. [Misc] For Unstable, built with mantic configuration ~~~ $ git push m_cbd remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx remote: * 1/9 workers busy, 0 builds queued remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK remote: 2023-11-20 16:14:16
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1008.8
---
linux-oem-6.5 (6.5.0-1008.8) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1008.8 -proposed tracker (LP: #2041878)
* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
* System hang after unplug/plug DP monitor with AMD W7500 card (LP: #2042912)
- SAUCE: drm/amd/pm: Fix error of MACO flag setting code
* Fix after-suspend-mediacard/sdhc-insert test failed (LP: #2042500)
- SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore
* Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
(LP: #2034477)
- x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility
- platform/x86: Add s2idle quirk for more Lenovo laptops
* Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen
on (LP: #2042385)
- SAUCE: r8169: Add quirks to enable ASPM on Dell platforms
* Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16
G9 (LP: #2042060)
- ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct
boost type
- ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9
- ALSA: hda: cs35l41: Assert reset before system suspend
- ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system
resume
- ALSA: hda: cs35l41: Run boot process during resume callbacks
- ALSA: hda: cs35l41: Force a software reset after hardware reset
- ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend
- ALSA: hda: cs35l41: Check CSPL state after loading firmware
- ASoC: cs35l41: Detect CSPL errors when sending CSPL commands
* Miscellaneous Ubuntu changes
- [Packaging] Add ppa2 to getabis
[ Ubuntu: 6.5.0-13.13 ]
* mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652)
* arm64 atomic issues cause disk corruption (LP: #2042573)
- locking/atomic: scripts: fix fallback ifdeffery
[ Ubuntu: 6.5.0-11.11 ]
* mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879)
* CVE-2023-31085
- ubi: Refuse attaching if mtd's erasesize is 0
* CVE-2023-4244
- netfilter: nft_set_rbtree: skip sync GC for new elements in this
transaction
* CVE-2023-5633
- drm/vmwgfx: Keep a gem reference to user bos in surfaces
* CVE-2023-5345
- fs/smb/client: Reset password pointer to NULL
* CVE-2023-5090
- x86: KVM: SVM: always update the x2avic msr interception
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
-- Timo Aaltonen Fri, 10 Nov 2023
13:04:39 +0200
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5633
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
[Kernel-packages] [Bug 2042573] Re: arm64 atomic issues cause disk corruption
This bug was fixed in the package linux - 6.5.0-13.13 --- linux (6.5.0-13.13) mantic; urgency=medium * mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652) * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery linux (6.5.0-11.11) mantic; urgency=medium * mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879) * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Roxana Nicolescu Fri, 03 Nov 2023 10:41:58 +0100 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5633 -- 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/2042573 Title: arm64 atomic issues cause disk corruption Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Released Bug description: SRU Justification: [Impact] The mantic kernel introduced a regression in atomic operations on arm64 which causes all kinds of problems including file system corruptions, since commit "locking/atomic: scripts: restructure fallback ifdeffery". An example report of people encountering this in UTM with a arm64 generic kernel: https://github.com/utmapp/UTM/issues/4840 [Fix] Cherry-pick commit "locking/atomic: scripts: fix fallback ifdeffery" from linux-stable v6.5.6 [Test Plan] Boot test on an arm64 vm. [Where problems could occur] Since this is touching atomic operations, this has a wide impact on the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042573/+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 2042912] Re: System hang after unplug/plug DP monitor with AMD W7500 card
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1008.8 --- linux-oem-6.5 (6.5.0-1008.8) jammy; urgency=medium * jammy/linux-oem-6.5: 6.5.0-1008.8 -proposed tracker (LP: #2041878) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper * System hang after unplug/plug DP monitor with AMD W7500 card (LP: #2042912) - SAUCE: drm/amd/pm: Fix error of MACO flag setting code * Fix after-suspend-mediacard/sdhc-insert test failed (LP: #2042500) - SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore * Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop (LP: #2034477) - x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility - platform/x86: Add s2idle quirk for more Lenovo laptops * Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on (LP: #2042385) - SAUCE: r8169: Add quirks to enable ASPM on Dell platforms * Fix system suspend problem for Cirrus CS35L41 HDA codec on HP ZBook Fury 16 G9 (LP: #2042060) - ALSA: hda: cs35l41: Override the _DSD for HP Zbook Fury 17 G9 to correct boost type - ALSA: hda: cs35l41: Use reset label to get GPIO for HP Zbook Fury 17 G9 - ALSA: hda: cs35l41: Assert reset before system suspend - ALSA: hda: cs35l41: Assert Reset prior to de-asserting in probe and system resume - ALSA: hda: cs35l41: Run boot process during resume callbacks - ALSA: hda: cs35l41: Force a software reset after hardware reset - ALSA: hda: cs35l41: Do not unload firmware before reset in system suspend - ALSA: hda: cs35l41: Check CSPL state after loading firmware - ASoC: cs35l41: Detect CSPL errors when sending CSPL commands * Miscellaneous Ubuntu changes - [Packaging] Add ppa2 to getabis [ Ubuntu: 6.5.0-13.13 ] * mantic/linux: 6.5.0-13.13 -proposed tracker (LP: #2042652) * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery [ Ubuntu: 6.5.0-11.11 ] * mantic/linux: 6.5.0-11.11 -proposed tracker (LP: #2041879) * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Timo Aaltonen Fri, 10 Nov 2023 13:04:39 +0200 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-31085 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4244 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5090 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5345 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-5633 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042912 Title: System hang after unplug/plug DP monitor with AMD W7500 card Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System hangs and no external output after unplug/plug DP monitor. (AMD Radeon Pro W7500) Observed a bunch of [Hardware Error] messages and finally amdgpu crashed. [Fix] AMD provides a patch to fix the issue https://www.spinics.net/lists/amd-gfx/msg99737.html which is included in v6.7-rc1 7f3e6b840fa8 drm/amd/pm: Fix error of MACO flag setting code [Testcase] 1. Connect the DUT to an external DP monitor via one of the ports on the AMD graphics card 2. Boot into Ubuntu 3. Unplug the DP cable from the DUT 4. Wait for 30 seconds 5. Replug in the DP cable 6. Make sure the system doesn't hang and the external DP monitor works [Where probles could occur] The patch make sure MACO is supported only if BACO is supported. It creates a stricter rule for MACO to avoid MACO is enabled with BACO supports. It should be safe to apply stricter
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
I found a solution for this, at least for my case! I traced the CPU pinning to ACPI GPE11 (corresponding to IRQ9 in my Mac Pro 1,1) being hit constantly. This can be killed permanently by passing "acpi_mask_gpe=0x11" to the kernel at boot. I still believe this was first triggered for 20.04 first during the generic 5.11-5.13 transition and then later during the low-latency 5.13-5.15 transition using the official Ubuntu kernels. I still haven't been able to pinpoint if this was a config change's fault, or perhaps whether a microcode error crept in. Suggest people give this a go. It clearly works for some others. For more background see here: https://unix.stackexchange.com/questions/588018/kworker-thread-kacpid-notify-kacpid-hogging-60-70-of-cpu Also a couple of posts here: https://mattgadient.com/linux-dvd-images-and-how-to-for-32-bit-efi-macs-late-2006-models/ -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
[Kernel-packages] [Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
** Changed in: linux
Status: Unknown => 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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2044023] [NEW] Jammy update: v5.15.134 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.134 upstream stable release
from git://git.kernel.org/
NFS: Use the correct commit info in nfs_join_page_group()
NFS: More fixes for nfs_direct_write_reschedule_io()
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
NFSv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server
NFSv4.1: fix pnfs MDS=DS session trunking
tracing: Make trace_marker{,_raw} stream-like
tracing: Increase trace array ref count on enable and filter files
ata: ahci: Drop pointless VPRINTK() calls and convert the remaining ones
ata: libahci: clear pending interrupt status
ext4: scope ret locally in ext4_try_to_trim_range()
ext4: change s_last_trim_minblks type to unsigned long
ext4: replace the traditional ternary conditional operator with with max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
tracing: Have event inject files inc the trace array ref count
netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention
netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC
netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails
netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration
netfilter: nf_tables: fix memleak when more than 255 elements expired
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
selftests: tls: swap the TX and RX sockets in some tests
net/core: Fix ETH_P_1588 flow dissector
ASoC: imx-audmix: Fix return error with devm_clk_get()
iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set
i40e: Add VF VLAN pruning
i40e: Fix VF VLAN offloading when port VLAN is configured
ionic: fix 16bit math issue when PAGE_SIZE >= 64KB
igc: Fix infinite initialization loop with early XDP redirect
powerpc/perf/hv-24x7: Update domain value check
dccp: fix dccp_v4_err()/dccp_v6_err() again
platform/x86: intel_scu_ipc: Check status after timeout in busy_loop()
platform/x86: intel_scu_ipc: Check status upon timeout in
ipc_wait_for_interrupt()
platform/x86: intel_scu_ipc: Don't override scu in
intel_scu_ipc_dev_simple_command()
platform/x86: intel_scu_ipc: Fail IPC send if still busy
x86/srso: Fix srso_show_state() side effect
x86/srso: Fix SBPB enablement for spec_rstack_overflow=off
net: hns3: fix GRE checksum offload issue
net: hns3: only enable unicast promisc when mac table full
net: hns3: fix fail to delete tc flower rules during reset issue
net: hns3: add 5ms delay before clear firmware reset irq source
net: bridge: use DEV_STATS_INC()
team: fix null-ptr-deref when team device type is changed
net: rds: Fix possible NULL-pointer dereference
netfilter: nf_tables: disable toggling dormant table state more than once
locking/seqlock: Do the lockdep annotation before locking in
do_write_seqcount_begin_nested()
net: ena: Flush XDP packets on error.
bnxt_en: Flush XDP for bnxt_poll_nitroa0()'s NAPI
igc: Expose tx-usecs coalesce setting to user
Fix up backport of 136191703038 ("interconnect: Teach lockdep about icc_bw_lock
order")
gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
i2c: mux: gpio: Replace custom acpi_get_local_address()
i2c: mux: gpio: Add missing fwnode_handle_put()
xfs: bound maximum wait time for inodegc work
xfs: introduce xfs_inodegc_push()
xfs: explicitly specify cpu when forcing inodegc delayed work to run immediately
xfs: check that per-cpu inodegc workers actually run on that cpu
xfs: disable reaping in fscounters scrub
xfs: fix xfs_inodegc_stop racing with mod_delayed_work
Input: i8042 - rename i8042-x86ia64io.h to i8042-acpipnpio.h
Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
netfilter: exthdr: add support for tcp option removal
netfilter: nft_exthdr: Fix non-linear header modification
ata: libata: Rename link flag ATA_LFLAG_NO_DB_DELAY
ata: ahci: Add support for AMD A85 FCH (Hudson D4)
ata: ahci: Rename board_ahci_mobile
ata: ahci: Add Elkhart Lake AHCI controller
scsi: qla2xxx: Select qpair depending on which CPU post_cmd() gets called
scsi: qla2xxx: Use raw_smp_processor_id() instead of smp_processor_id()
btrfs: reset destination buffer when read_extent_buffer() gets invalid range
MIPS: Alchemy: only build mmc support helpers if au1xmmc is enabled
drm/bridge: ti-sn65dsi83: Do not generate HFP/HBP/HSA and
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/6.2.0-1017.18)
All autopkgtests for the newly accepted linux-restricted-modules-oracle (6.2.0-1017.18) for lunar have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525/525.147.05-0ubuntu0.23.04.1 (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/lunar/update_excuses.html#linux-restricted-modules-oracle [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 packaging 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 1786013] Autopkgtest regression report (linux-restricted-modules-aws/6.5.0-1011.11)
All autopkgtests for the newly accepted linux-restricted-modules-aws (6.5.0-1011.11) for mantic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525-server/525.147.05-0ubuntu0.23.10.1 (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/mantic/update_excuses.html#linux-restricted-modules-aws [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 packaging 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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Here, there's an issue opened in Gitlab Gnome about mutter that could be
related to this issue (thanks again to Michel Dänzer):
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3036
https://gitlab.gnome.org/GNOME/mutter/-/issues/3036
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2043905] Re: VT6307 IEEE1394 card causes reboot loop
I do have an old system (Phenom 1090T CPU) on a motherboard that has a 1394a controller built in that the 6.5.0-10 kernel works properly on... would some sort of system report from that machine help in tracking down the issue? or even a report from the system with the issue with an earlier kernel (6.2.0-36) with the card installed?? I know the phenom is a pre-ryzen so it may be totally missing a CPU command structure that is possibly effected, and the Lunar kernel which isn't effected may also be missing something even though the rest of the system is with the up to date 23.10 build.. would be interesting if somehow could run a 6.5 kernel under the 6.2 kernel to get a log of some sort. I have VirtualBox installed but that provides its own "box" and doesn't really use the current hardware... -- 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/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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 2038248] Update Released
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Jammy:
Fix Released
Status in makedumpfile source package in Lunar:
Fix Released
Bug description:
[Impact]
The kernel crashdumps generated by makedumpfile on kernel 6.2
(affects Lunar, and Jammy with the HWE kernel) might not open
on crash, due to kernel changes not reflected in makedumpfile.
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900
[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==
[Test Plan]
1. Install the required packages and then proceed to reboot the machine.
# sudo apt install crash linux-crashdump -y
# reboot
2. To check the status of kdump, use the `kdump-config show` command.
# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x6400
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-6.2.0-33-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
3. To trigger a crash dump forcefully, execute the `echo c | sudo tee
/proc/sysrq-trigger` command.
4. Download the kernel .ddeb file, which will be used for analyzing the dump
file.
# sudo -i
# cd /var/crash
# pull-lp-ddebs linux-image-unsigned-$(uname -r)
# dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
5. Utilize the "crash" utility to parse and analyze the dump file.
# crash dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash" utility is
unable to parse it in the worst-case scenario.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+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 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1
This bug was fixed in the package makedumpfile - 1:1.7.0-1ubuntu0.1
---
makedumpfile (1:1.7.0-1ubuntu0.1) jammy; urgency=medium
* d/p/lp2038248-fix-wrong-exclusion-of-slab-pages-on-Linux-6.2.patch:
When using the "makedumpfile -d 8" command,
exclude user data rather than other slab pages (LP: #2038248)
-- Chengen Du Tue, 10 Oct 2023 13:52:06
+
** Changed in: makedumpfile (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Jammy:
Fix Released
Status in makedumpfile source package in Lunar:
Fix Released
Bug description:
[Impact]
The kernel crashdumps generated by makedumpfile on kernel 6.2
(affects Lunar, and Jammy with the HWE kernel) might not open
on crash, due to kernel changes not reflected in makedumpfile.
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900
[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==
[Test Plan]
1. Install the required packages and then proceed to reboot the machine.
# sudo apt install crash linux-crashdump -y
# reboot
2. To check the status of kdump, use the `kdump-config show` command.
# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x6400
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-6.2.0-33-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
3. To trigger a crash dump forcefully, execute the `echo c | sudo tee
/proc/sysrq-trigger` command.
4. Download the kernel .ddeb file, which will be used for analyzing the dump
file.
# sudo -i
# cd /var/crash
# pull-lp-ddebs linux-image-unsigned-$(uname -r)
# dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
5. Utilize the "crash" utility to parse and analyze the dump file.
# crash dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash" utility is
unable to parse it in the worst-case scenario.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+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 2038248] Re: Slab page exclusion issue on Linux 6.2-rc1
This bug was fixed in the package makedumpfile - 1:1.7.2-1ubuntu0.1
---
makedumpfile (1:1.7.2-1ubuntu0.1) lunar; urgency=medium
* d/p/lp2038248-fix-wrong-exclusion-of-slab-pages-on-Linux-6.2.patch:
When using the "makedumpfile -d 8" command,
exclude user data rather than other slab pages (LP: #2038248)
-- Chengen Du Tue, 03 Oct 2023 06:26:06
+
** Changed in: makedumpfile (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/2038248
Title:
Slab page exclusion issue on Linux 6.2-rc1
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Jammy:
Fix Released
Status in makedumpfile source package in Lunar:
Fix Released
Bug description:
[Impact]
The kernel crashdumps generated by makedumpfile on kernel 6.2
(affects Lunar, and Jammy with the HWE kernel) might not open
on crash, due to kernel changes not reflected in makedumpfile.
The Kernel commit 130d4df57390 ("mm/sl[au]b: rearrange struct slab fields to
allow larger rcu_head"), included in Linux 6.2-rc1 and later versions,
introduced a change that aligns the offset of slab.slabs with that of
page.mapping.
However, this modification unintentionally causes the makedumpfile command
with the -d 8 option, meant to exclude user data, to incorrectly exclude
certain slab pages.
Consequently, when utilizing dumpfiles generated in this manner, the "crash"
utility may encounter an error when attempting to initiate a session:
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Fix]
An upstream fix is available.
==
commit 5f17bdd2128998a3eeeb4521d136a19fadb6
Author: Kazuhito Hagio
Date: Wed Dec 21 11:06:39 2022 +0900
[PATCH] Fix wrong exclusion of slab pages on Linux 6.2-rc1
==
[Test Plan]
1. Install the required packages and then proceed to reboot the machine.
# sudo apt install crash linux-crashdump -y
# reboot
2. To check the status of kdump, use the `kdump-config show` command.
# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x6400
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.2.0-33-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to
/var/lib/kdump/initrd.img-6.2.0-33-generic
current state:ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic
root=UUID=3e72f5d5-870b-4b8e-9a0d-8ba920391379 ro console=tty1 console=ttyS0
reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll
usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
3. To trigger a crash dump forcefully, execute the `echo c | sudo tee
/proc/sysrq-trigger` command.
4. Download the kernel .ddeb file, which will be used for analyzing the dump
file.
# sudo -i
# cd /var/crash
# pull-lp-ddebs linux-image-unsigned-$(uname -r)
# dpkg-deb -x linux-image-unsigned-$(uname -r)-*.ddeb dbgsym-$(uname -r)
5. Utilize the "crash" utility to parse and analyze the dump file.
# crash dbgsym-$(uname -r)/usr/lib/debug/boot/vmlinux-$(uname -r)
/dump.
...
please wait... (gathering task table data)
crash: page excluded: kernel virtual address: e269d428 type:
"xa_node shift"
[Where problems could occur]
The patch has altered the method for excluding slab pages, aligning with the
structural changes introduced in Linux 6.2-rc1.
This modification is essential for Linux kernel 6.2.
However, it's crucial to note that this change may impact the content of the
dump file, potentially leading to a situation where the "crash" utility is
unable to parse it in the worst-case scenario.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/2038248/+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 2044003] [NEW] Don't produce linux-*-tools-{common, host} binary packages
Public bug reported:
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these.
** Affects: linux-laptop (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Don't produce linux-*-tools-{commont,host} binary packages
+ Don't produce linux-*-tools-{common,host} binary packages
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-laptop in Ubuntu.
https://bugs.launchpad.net/bugs/2044003
Title:
Don't produce linux-*-tools-{common,host} binary packages
Status in linux-laptop package in Ubuntu:
New
Bug description:
Some kernels produce linux-*-tools-common and/or linux-*-tools-host
binary deb packages. That is all wrong, only the primary/main linux
source package should produce these.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2044003/+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 2043994] Re: Don't produce linux-source binary package
** No longer affects: 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/2043994 Title: Don't produce linux-source binary package Status in linux-gkeop package in Ubuntu: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-ibm-5.15 package in Ubuntu: New Bug description: Some kernels produce a linux-source- binary deb package or even linux--source-. That is all wrong, only the primary/main linux source package should produce that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gkeop/+bug/2043994/+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 2042385] Re: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on
SRUed for Unstable, https://lists.ubuntu.com/archives/kernel-team/2023-November/147039.html ** Description changed: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. + + [Misc] + For Unstable, built with mantic configuration + ~~~ + $ git push m_cbd + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx + remote: * 1/9 workers busy, 0 builds queued + remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK + remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK + remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK + remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK + remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK + remote: + To cbd.kernel:mantic.git + * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next + ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042385 Title: Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. [Misc] For Unstable, built with mantic configuration ~~~ $ git push m_cbd remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx remote: * 1/9 workers busy, 0 builds queued remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Description changed: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ + + Lunar, + $ git push l_cbd + Enumerating objects: 9, done. + Counting objects: 100% (9/9), done. + Delta compression using up to 8 threads + Compressing objects: 100% (5/5), done. + Writing objects: 100% (5/5), 784 bytes | 65.00 KiB/s, done. + Total 5 (delta 4), reused 0 (delta 0), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_lunar_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-lunar-915de03d6ecf-V1nm + remote: * 9/9 workers busy, 0 builds queued + remote: 2023-11-20 16:00:11 kobako-lunar-915de03d6ecf-V1nm/amd64/BUILD-OK + remote: 2023-11-20 15:59:57 kobako-lunar-915de03d6ecf-V1nm/arm64/BUILD-OK + remote: 2023-11-20 15:55:14 kobako-lunar-915de03d6ecf-V1nm/armhf/BUILD-OK + remote: 2023-11-20 15:55:26 kobako-lunar-915de03d6ecf-V1nm/ppc64el/BUILD-OK + remote: 2023-11-20 15:47:17 kobako-lunar-915de03d6ecf-V1nm/s390x/BUILD-OK + remote: + To cbd.kernel:lunar.git + * [new branch]ubuntu_lunar_next -> ubuntu_lunar_next + Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next ~~~ For Unstable, successfully compiled with the Mantic configuration and without dkms. ~~~ Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
Can confirm.
I am seeing the same "evict_inodes" messages, whenever am inserting or removing
the USB drive.
As well as when I boot up my laptop (Lenovo X1 Carbon gen10)
```
[Mon Nov 20 16:39:27 2023] usb 3-9: USB disconnect, device number 18
[Mon Nov 20 16:39:27 2023] evict_inodes inode aee04a8d, i_count = 1,
was skipped!
```
Ubuntu 23.10 on 6.5.0-10-generic Linux kernel.
(Haven't seen these in Ubuntu 23.04 with older Linux kernel 6.2)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 1979631] Re: Orico Switch5.0 Bluetooth adapter doesn't work
Not a bug, explained in comment ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979631 Title: Orico Switch5.0 Bluetooth adapter doesn't work Status in linux package in Ubuntu: Invalid Bug description: I bought Switch5.0 Bluetooth adapter (https://www.orico.cc/us/product/detail/7400/BK.html) which identifies under lsusb as: 10d6:dd00 Actions Semiconductor Co., Ltd BT90 It doesn't work under Ubuntu 22.04. The Bluetooth icon doesn't show up and when I try to run blueman-adapters it shows: > blueman-adapters blueman-adapters 11.38.00 ERRORAdapter:54 __init__ : No adapter(s) found The weird thing is, that it creates new audio device BT90 in Pulse settings. (I think, that the device might share same identification codes as different audio device: https://linux-hardware.org/?id=usb:10d6-dd00) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: petr 1703 F pulseaudio /dev/snd/pcmC0D0p: petr 1703 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Jun 23 11:33:41 2022 InstallationDate: Installed on 2017-05-29 (1850 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: HP HP Z240 Tower Workstation ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=d1e354f4-cbcc-4f35-b360-8e2f15dca61e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-02 (51 days ago) dmi.bios.date: 12/15/2020 dmi.bios.release: 1.81 dmi.bios.vendor: HP dmi.bios.version: N51 Ver. 01.81 dmi.board.name: 802F dmi.board.vendor: HP dmi.chassis.asset.tag: CZC710BW19 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.56 dmi.modalias: dmi:bvnHP:bvrN51Ver.01.81:bd12/15/2020:br1.81:efr5.56:svnHP:pnHPZ240TowerWorkstation:pvr:rvnHP:rn802F:rvr:cvnHP:ct3:cvr:skuT4L18ES#ARL: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z240 Tower Workstation dmi.product.sku: T4L18ES#ARL dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979631/+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 2043994] Re: Don't produce linux-source binary package
** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu) Importance: Undecided Status: New ** Description changed: - TBD + Some kernels produce a linux-source- binary deb package or even + linux--source- binary deb package or even - linux--source--source-. That is all wrong, only the primary/main linux source package should produce that. -- 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/2043994 Title: Don't produce linux-source binary package Status in linux package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-ibm-5.15 package in Ubuntu: New Bug description: Some kernels produce a linux-source- binary deb package or even linux--source-. That is all wrong, only the primary/main linux source package should produce that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043994/+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 2043994] [NEW] Don't produce linux-source binary package
Public bug reported: Some kernels produce a linux-source- binary deb package or even linux--source-. That is all wrong, only the primary/main linux source package should produce that. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gkeop (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ibm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ibm-5.15 (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/2043994 Title: Don't produce linux-source binary package Status in linux package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-ibm-5.15 package in Ubuntu: New Bug description: Some kernels produce a linux-source- binary deb package or even linux--source-. That is all wrong, only the primary/main linux source package should produce that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043994/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
Tested with COGL_DEBUG parameter added and at the moment, I can't
reproduce these artifacts. I will keep trying it today.
--
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/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2042546] Re: Include cifs.ko in linux-modules package
Installed lunar/linux-gcp-6.2.0-1019 from -proposed in a vm running a lunar cloudimg server image (amd64) and successfully loaded module cifs without needing to install modules-extra. ** Tags removed: verification-needed-lunar-linux-gcp ** Tags added: verification-done-lunar-linux-gcp -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 1946303] Re: No video after wake from S3 due to Nvidia driver crash
ust wanted to confirm that this also affects me: * Ubuntu 23.10 and 23.04 LTS * GTX970 graphic card, both under wayland and X11 * nvidia-driiver 545 that is 545.29.02, but it did not work in 535, 515 or 495 either * Kernel 6.5.0-10-generic The error messages are exactly the same as per: https://forums.developer.nvidia.com/t/not-coming-back-from-suspend/176446 using /usr/bin/nvidia-sleep.sh suspend /usr/bin/nvidia-sleep.sh resume from terminal from another machine turns off and back on the graphics (and reduces power drain accoring to my power meter) but: /usr/bin/nvidia-sleep.sh suspend pm-suspend /usr/bin/nvidia-sleep.sh resume results in the black screen (computer available from network). The dmesg messages are identical as above, the same procedure fail in nv.c, but in a different line of (different driver version). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1946303 Title: No video after wake from S3 due to Nvidia driver crash Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Bug description: Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake from suspend. It does start running again, but there is no video output. I'm attaching text for two crashes from kernel log output. First is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 nv_restore_user_channels+0xce/0xe0 [nvidia] Second is: /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 nv_set_system_power_state+0x2c8/0x3d0 [nvidia] Apparently I'm not the only one having this problem with 470 drivers. https://forums.linuxmint.com/viewtopic.php?t=354445 https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150 Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system- sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu 21.04 and sleep was reliable then. Right now I'm going back to driver 460. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-470 470.63.01-0ubuntu4 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 6 23:24:02 2021 SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Changed in: linux (Ubuntu Lunar) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next ~~~ For Unstable, successfully compiled with the Mantic configuration and without dkms. ~~~
[Kernel-packages] [Bug 2040081] Re: package firmware-b43-installer 1:019-8 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit s
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: b43-fwcutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/2040081 Title: package firmware-b43-installer 1:019-8 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 Status in b43-fwcutter package in Ubuntu: Confirmed Bug description: b43-installer failed while upgrading. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: firmware-b43-installer 1:019-8 ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Oct 22 08:00:48 2023 ErrorMessage: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-10-21 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) PackageArchitecture: all Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-8 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-10-22 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2040081/+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 2043962] Re: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP
** Description changed: [SRU Justification] [Impact] emmc storage is not usable after booting. [Fix] CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP need to be built-in to supply clock and power as early as possible, in order to have the emmc storage for further installation. + both of the modules were in initramfs already but still not be able to bring up the emmc. according to mediatek, these two drivers should be built-in for further peripherals usage. [Test Case] 1. build test. 2. testing on the target device, mediatek g1200 evk board, and check the emmc storage could be recognize and mountable after booting. [Where problems could occur] the risk would be low because both drivers are only used on mediatek platform. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. -- 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/2043962 Title: [Mediatek] mt8195-demo: enable CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [SRU Justification] [Impact] emmc storage is not usable after booting. [Fix] CONFIG_COMMON_CLK_MT8188 and CONFIG_MTK_PMIC_WRAP need to be built-in to supply clock and power as early as possible, in order to have the emmc storage for further installation. both of the modules were in initramfs already but still not be able to bring up the emmc. according to mediatek, these two drivers should be built-in for further peripherals usage. [Test Case] 1. build test. 2. testing on the target device, mediatek g1200 evk board, and check the emmc storage could be recognize and mountable after booting. [Where problems could occur] the risk would be low because both drivers are only used on mediatek platform. [Other info] the purpose of this is to make ubuntu as an arm systemready ir distribution for mediatek platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043962/+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 2043905] Re: VT6307 IEEE1394 card causes reboot loop
Hi Bevil, I'm a maintainer of Linux FireWire subsystem, and I apologize to trouble you. Indeed, we can see unexpected system reboot in the following combination: * Linux kernel version 6.5 or later * Any kind of AMD Ryzen machines * A kind of IEEE 1394 host controller which consists of: ** Asmedia ASM1083 (PCI/PCIe bridge) ** VIA VT6306/6307/6308 (1394 OHCI host controller) You can see my short description about the issue in my PR to Linus for version 6.7 kernel. * https://lore.kernel.org/all/20231105144852.GA165906@workstation.local/ The host controller card brings some kind of hardware trouble to the machine of AMD Ryzen architecture as a result of change added to 1394 OHCI driver (firewire-ohci), while I never figure out the mechanism yet, since the system reboots without any kind of information in console output. I continue to investigate further by every single way I can think of... At present, no workaround found. I confirm that some portion to exclude the above condition enable system work again; e.g. usage of IEEE 1394 host controller with VIA6315 or VIA6305 connected with PCI bus without the bridge chip. Regards -- 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/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: In Progress Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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 2036382] Re: System cannot start after installation
NVIDIA GF108GLM [NVS 5200M] on Dell Latitude 6430 was also affected. Nouveau works. -- 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/2036382 Title: System cannot start after installation Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When restarting after installation, the system cannot start, but 22.04.3 LTS environment or Nouveau driver can be used normally. Graphics Card: GeForce GT 610 (1GB/Colorful) Main Board: Lenovo Erazer D215 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 13:14:35 2023 InstallationDate: Installed on 2023-09-18 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-390 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/2036382/+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 2036382] Re: System cannot start after installation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- 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/2036382 Title: System cannot start after installation Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: When restarting after installation, the system cannot start, but 22.04.3 LTS environment or Nouveau driver can be used normally. Graphics Card: GeForce GT 610 (1GB/Colorful) Main Board: Lenovo Erazer D215 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-390 (not installed) ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 13:14:35 2023 InstallationDate: Installed on 2023-09-18 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-390 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/2036382/+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 2043981] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post-installation installé a ren
Public bug reported: le package ne s'installe pas ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.22 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 AlsaInfo: Error: command ['/usr/sbin/alsa-info', '--stdout', '--no-upload'] failed with exit code 1: This script requires awk utility to continue. ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guigrehi 1608 F pulseaudio /dev/snd/controlC0: guigrehi 1608 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Nov 20 11:36:50 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.2 ErrorMessage: le sous-processus paquet linux-firmware script post-installation installé a renvoyé un état de sortie d'erreur 127 InstallationDate: Installed on 2023-07-26 (116 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Latitude E7250 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=9e893492-0bb7-4770-ae1a-e11afb05f869 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. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post-installation installé a renvoyé un état de sortie d'erreur 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2015 dmi.bios.release: 65.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0TVD2T dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/19/2015:br65.8:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0TVD2T:rvrA01:cvnDellInc.:ct9:cvr:sku062D: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. ** Affects: linux-firmware (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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2043981 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post- installation installé a renvoyé un état de sortie d'erreur 127 Status in linux-firmware package in Ubuntu: New Bug description: le package ne s'installe pas ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.22 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 AlsaInfo: Error: command ['/usr/sbin/alsa-info', '--stdout', '--no-upload'] failed with exit code 1: This script requires awk utility to continue. ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: guigrehi 1608 F pulseaudio /dev/snd/controlC0: guigrehi 1608 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Mon Nov 20 11:36:50 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.2 ErrorMessage: le sous-processus paquet linux-firmware script post-installation installé a renvoyé un état de sortie d'erreur 127 InstallationDate: Installed on 2023-07-26 (116 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Latitude E7250 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=9e893492-0bb7-4770-ae1a-e11afb05f869 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. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu3.22 failed to install/upgrade: le sous-processus paquet linux-firmware script post-installation installé a renvoyé un état de sortie d'erreur 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2015 dmi.bios.release: 65.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0TVD2T dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 2043905] Re: VT6307 IEEE1394 card causes reboot loop
Launchpad has imported 14 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=217993. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2023-10-10T21:00:25+00:00 matthias.schrumpf wrote: Kernel 6.5 causes a crash immediately after selecting it in GRUB or trying to boot with it via other means. This crash always leads into a bootloop if no other kernel is selected. A successful boot with kernel 6.5 is impossible, so no log data could be collected. This error can be reproduced on many distros including Arch, Endeavour OS, Manjaro, Fedora and OpenSuse. The computer is working perfectly fine with older kernels up to and including 6.4. CPU, RAM and hard drives have all been checked thoroughly and no errors could be found. Current OS: Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.4.15-200.fc38.x86_64 (64-bit) Graphics Platform: X11 Hardware: Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C91 System Version: 1.0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/0 On 2023-10-11T14:41:55+00:00 aros wrote: Could you please bisect? https://docs.kernel.org/admin-guide/bug-bisect.html Otherwise this bug report has very slim chances of being fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/1 On 2023-10-12T09:39:15+00:00 bagasdotme wrote: Do you have any out-of-tree modules that may cause this regression? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/2 On 2023-10-16T21:01:04+00:00 matthias.schrumpf wrote: (In reply to Artem S. Tashkinov from comment #1) > Could you please bisect? > > https://docs.kernel.org/admin-guide/bug-bisect.html > > Otherwise this bug report has very slim chances of being fixed. I'm sorry, I don't have the basic knowledge necessary for performing a bisection. (In reply to Bagas Sanjaya from comment #2) > Do you have any out-of-tree modules that may cause this regression? No, not to my knowledge. I tried this with live images or fresh installs of Arch, Endeavour OS, Manjaro, Fedora and OpenSuse and I didn't change anything beyond the settings and customizations that these distros do by default. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/3 On 2023-10-16T23:55:15+00:00 bagasdotme wrote: On 17/10/2023 04:01, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=217993 > > --- Comment #3 from matthias.schru...@freenet.de --- > (In reply to Artem S. Tashkinov from comment #1) >> Could you please bisect? >> >> https://docs.kernel.org/admin-guide/bug-bisect.html >> >> Otherwise this bug report has very slim chances of being fixed. > I'm sorry, I don't have the basic knowledge necessary for performing a > bisection. > Then refer to Documentation/admin-guide/bug-bisect.rst in the kernel sources for instructions. > (In reply to Bagas Sanjaya from comment #2) >> Do you have any out-of-tree modules that may cause this regression? > No, not to my knowledge. I tried this with live images or fresh installs of > Arch, Endeavour OS, Manjaro, Fedora and OpenSuse and I didn't change anything > beyond the settings and customizations that these distros do by default. > So you have this regression there? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/4 On 2023-10-18T21:36:42+00:00 matthias.schrumpf wrote: (In reply to Bagas Sanjaya from comment #4) > So you have this regression there? What do you mean? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/comments/5 On 2023-10-24T14:54:14+00:00 aros wrote: Given that seemingly you're the only Linux user who has this issue, your only bet of fixing it is performing regression testing. The URL provided above has enough information to do so. If that's not enough, you may simply Google the appropriate questions, e.g. 1) How to compile and install the Linux kernel 2) How to install GCC in Distro_X It's all quite easy if you get down to it. No one but you can do it unfortunately. Reply at:
[Kernel-packages] [Bug 2042107] Re: Focal update: v5.4.258 upstream stable release
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.258 upstream stable release
from git://git.kernel.org/
NFS/pNFS: Report EINVAL errors from connect() to the server
SUNRPC: Mark the cred for revalidation if the server rejects it
tracing: Increase trace array ref count on enable and filter files
ata: libahci: clear pending interrupt status
ext4: remove the 'group' parameter of ext4_trim_extent
ext4: add new helper interface ext4_try_to_trim_range()
ext4: scope ret locally in ext4_try_to_trim_range()
ext4: change s_last_trim_minblks type to unsigned long
ext4: mark group as trimmed only if it was fully scanned
ext4: replace the traditional ternary conditional operator with with
max()/min()
ext4: move setting of trimmed bit into ext4_try_to_trim_range()
ext4: do not let fstrim block system suspend
ASoC: meson: spdifin: start hw on dai probe
netfilter: nf_tables: disallow element removal on anonymous sets
bpf: Avoid deadlock when using queue and stack maps from NMI
selftests/tls: Add {} to avoid static checker warning
selftests: tls: swap the TX and RX sockets in some tests
ASoC: imx-audmix: Fix return error with devm_clk_get()
i40e: Fix for persistent lldp support
UBUNTU: SAUCE: Revert "UBUNTU: SAUCE: i40e Fix GPF when deleting VMs"
i40e: Remove scheduling while atomic possibility
i40e: Fix warning message and call stack during rmmod i40e driver
i40e: Fix VF VLAN offloading when port VLAN is configured
powerpc/perf/hv-24x7: Update domain value check
dccp: fix dccp_v4_err()/dccp_v6_err() again
net: hns3: add 5ms delay before clear firmware reset irq source
net: bridge: use DEV_STATS_INC()
team: fix null-ptr-deref when team device type is changed
net: rds: Fix possible NULL-pointer dereference
gpio: tb10x: Fix an error handling path in tb10x_gpio_probe()
i2c: mux: demux-pinctrl: check the return value of devm_kstrdup()
Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
scsi: qla2xxx: Fix update_fcport for current_topology
scsi: qla2xxx: Fix deletion race condition
drm/amd/display: Reinstate LFC optimization
drm/amd/display: Fix LFC multiplier changing erratically
drm/amd/display: prevent potential division by zero errors
ata: libata: disallow dev-initiated LPM transitions to unsupported states
MIPS: Alchemy: only build mmc support helpers if au1xmmc is enabled
clk: tegra: fix error return case for recalc_rate
ARM: dts: ti: omap: motorola-mapphone: Fix abe_clkctrl warning on boot
bus: ti-sysc: Fix SYSC_QUIRK_SWSUP_SIDLE_ACT handling for uart wake-up
xtensa: add default definition for XCHAL_HAVE_DIV32
xtensa: iss/network: make functions static
xtensa: boot: don't add include-dirs
xtensa: boot/lib: fix function prototypes
gpio: pmic-eic-sprd: Add can_sleep flag for PMIC EIC chip
parisc: sba: Fix compile warning wrt list of SBA devices
parisc: iosapic.c: Fix sparse warnings
parisc: drivers: Fix sparse warning
parisc: irq: Make irq_stack_union static to avoid sparse warning
selftests/ftrace: Correctly enable event in instance-event.tc
ring-buffer: Avoid softlockup in ring_buffer_resize()
ata: libata-eh: do not clear ATA_PFLAG_EH_PENDING in ata_eh_reset()
spi: nxp-fspi: reset the FLSHxCR1 registers
bpf: Clarify error expectations from bpf_clone_redirect
powerpc/watchpoints: Annotate atomic context in more places
ncsi: Propagate carrier gain/loss events to the NCSI controller
fbdev/sh7760fb: Depend on FB=y
nvme-pci: do not set the NUMA node of device if it has none
watchdog: iTCO_wdt: No need to stop the timer in probe
watchdog: iTCO_wdt: Set NO_REBOOT if the watchdog is not already running
i40e: improve locking of mac_filter_hash
i40e: always propagate error value in i40e_set_vsi_promisc()
i40e: fix return of uninitialized aq_ret in i40e_set_vsi_promisc
smack: Record transmuting in smk_transmuted
smack: Retrieve transmuting information in smack_inode_getsecurity()
Smack:- Use overlay inode label in smack_inode_copy_up()
serial: 8250_port: Check IRQ data before use
nilfs2: fix potential use after free in nilfs_gccache_submit_read_data()
ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q
ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES
i2c: i801: unregister tco_pdev in i801_probe() error path
ring-buffer: Update "shortest_full" in polling
btrfs: properly report 0 avail for very full file systems
net: thunderbolt: Fix TCPv6 GSO checksum
[Kernel-packages] [Bug 2043331] Re: Mouse pointer bug on Intel N2600 (Cedarview)
** Summary changed:
- Mouse pointer bug on Intel Corporation Atom Processor D2xxx/N2xxx Integrated
Graphics Controller
+ Mouse pointer bug on Intel N2600 (Cedarview)
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Mouse pointer bug on Intel N2600 (Cedarview)
+ [gma500] Mouse pointer bug on Intel N2600 (Cedarview)
--
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/2043331
Title:
[gma500] Mouse pointer bug on Intel N2600 (Cedarview)
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
If you press a button in a window that doesn't close the window and
doesn't change the area under the button, you get half an fake mouse
pointer on the area of the mouse pointer that was clicked. If you move
the correct mouse pointer over the fake mouse pointer, it disappears.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 20:31:10 2023
DistUpgraded: 2023-11-12 20:22:28,705 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus:
broadcom-sta/6.30.223.271, 6.5.0-10-generic, x86_64: installed
broadcom-sta/6.30.223.271, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller
[8086:0be1] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Atom Processor D2xxx/N2xxx Integrated
Graphics Controller [1025:0624]
InstallationDate: Installed on 2023-11-12 (0 days ago)
InstallationMedia: Ubuntu Legacy 23.10 "Mantic Minotaur" - Release amd64
(20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=b67dae3e-d7cf-4a05-a809-18bc61b127ea ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2023-11-12 (0 days ago)
dmi.bios.date: 07/23/2013
dmi.bios.release: 10.240
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJE01_CT
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.10:bd07/23/2013:br10.240:svnPackardBell:pndots:pvrV1.10:rvnPackardBell:rnSJE01_CT:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:skuType1Sku0:
dmi.product.family: Type1Family
dmi.product.name: dot s
dmi.product.sku: Type1Sku0
dmi.product.version: V1.10
dmi.sys.vendor: Packard Bell
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.116-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043331/+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 2043264] Re: External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) + [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) -- 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/2043264 Title: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: --- en Always, almost every time I turn on my notebook, my LG external monitor keeps blinking and it takes a while to actually connect to the notebook and the external monitor screen to turn on. For the external monitor to work I change the video settings using Ctrl + P and turn the monitor off/on several times. In Kubuntu it is recognized but when it blinks the system thinks the monitor is off. I'm using Kubuntu 23.04, I've used other distributions on the same hardware and this problem hasn't happened. I believe it's something with KDE. --- pt-br Sempre, quase toda vez que ligo meu notebook, meu monitor externo LG fica piscando e demora para realmente conectar ao notebook e a tela do monitor externo ligar. Para o monitor externo funcionar eu mudo as configurações de vídeo usando Ctrl + P e desligo/ligo o monitor várias vezes. No Kubuntu ele é reconhecido mas quando fica piscando o sistema acha que o monitor está desligado. Estou usando o Kubuntu 23.04, já usei outras distribuições no mesmo hardware e esse problema não aconteceu. Eu acredito que seja algo com o KDE. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 11 07:52:24 2023 DistUpgraded: 2023-11-02 07:28:00,578 DEBUG /openCache(), new cache size 78921 DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3804] InstallationDate: Installed on 2022-10-23 (383 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 81V7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=d72b8a6b-953f-4b38-8b0a-d1e9b6899ad2 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-11-02 (9 days ago) dmi.bios.date: 05/19/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: BUCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15API dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrBUCN25WW:bd05/19/2020:br1.25:efr1.25:svnLENOVO:pn81V7:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81V7_BU_idea_FM_IdeaPadS145-15API: dmi.product.family: IdeaPad S145-15API dmi.product.name: 81V7 dmi.product.sku: LENOVO_MT_81V7_BU_idea_FM_IdeaPad S145-15API dmi.product.version: Lenovo IdeaPad S145-15API dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043264/+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 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043964 Title: New China SRRC compliance readiness check for Realtek WLAN Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Triaged Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: New China SRRC compliance readiness check Proposed Change: - China SRRC updates the testing requirement for 2.4/5GHz, the major changes are the in-band RSE limit, and EIRP limits. - The SRRC updates impact both WLAN modules and platforms. The WLAN modules need to complete the new SRRC testing then platform can start to apply / renew the new SRRC cert. If platform took several WLAN modules but not all of the modules have completed the new SRRC testing updates, platform cannot renew/apply the new SRRC cert. - The platforms which apply/renew SRRC new standards need to ensure the TX power can meet the new RSE/EIRP limits. IHV confirmed below driver version can support these requirements. Realtek: The upstream driver can support SRRC compliance. https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340 [lore.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043964/+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 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland
Please try adding COGL_DEBUG=disable-batching to /etc/environment and
then reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038998
Title:
[amdgpu] Screen artifacts/UI oddities on Wayland
Status in GNOME Shell:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
Ryzen 7 PRO 5850U
with Radeon (RX Vega 8?) integrated graphics
16 GB RAM
Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
2023 from a daily-live/current .iso generated on October 4, 2023.
Wayland
Kernel 6.5.0-9-generic
* * * * *
Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
day, was going through setting up and testing the usual programs.
Installed Steam through apt from the 'mantic' repositories. Installed
Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
compatible titles.
Screen corruption (white and grey streaks) present in-game when GNOME
UI elements appeared on-screen (e.g., volume, brightness, and keyboard
backlight indicators) and omnipresent after closing either game.
Artifacts remain on screen until log-out or reboot. Artifacts were not
present beforehand.
Artifacts only appeared in Wayland session; not X11/Xorg.
I previously had been running the same games on Ubuntu 22.04 LTS
(GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
computer without issue (kernel 6.2).
* * * * *
Please see subsequent posts for video/images.
Happy to provide any other information as needed. Thanks!
* * * * *
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 11 01:17:43 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series]
[17aa:509b]
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A00068US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A00068US
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2038998/+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 2043208] Re: Headset microphone not properly recognized after 23.10 upgrade
** Tags added: mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043208 Title: Headset microphone not properly recognized after 23.10 upgrade Status in linux package in Ubuntu: New Bug description: [description] My wired headset (hyperx cloud 2) has a built in microphone that was working perfectly fine in 22.10 and 23.04 on my system. But after upgrading to 23.10 most of the time when plugging it into the headphone jack of my machine, audio output works perfectly fine however the microphone is often not recognized. Running "systemctl --user restart pipewire pipewire-pulse wireplumber" a few times often causes the microphone to be recognized by the system but applications such as firefox wouldn't recognize it. Restarting the machine usually would make applications able to detect and use the microphone. [possible solution] I have found a few reports of people having similar issues as me after upgrading to 23.10 and I was even able to find on the french ubuntu forums a possible fix where manually installing kernel 6.6rc5 or above has fixed the issue: https://forum.ubuntu-fr.org/viewtopic.php?id=2081994 I couldn't verify this solution for myself since I an still running the default 6.5 kernel that came with Mantic but I did find another user on askubuntu who upgraded to the 6.6rc5 kernel and had his microphone issues resolved: https://askubuntu.com/questions/1490935/built-in-microphone-not-detected-after-installing-ubuntu-23-10 This thread also referenced the "forum.ubuntu-fr.org" forum. My specific issue might be pipewire related and not kernel related but based on the number of reports I've seen that 6.6rc5 fixes the issue (6.6rc1 did not based on the reports) the issue is also kernel related to some extent. [system] Dell XPS 17 9720, intel core i9 12900HK, RTX 3060 6GB + intel iris Xe Kubuntu 23.10 using wayland with plasma 5.27.8 nvidia driver: 545.29.02 (proprietary). I also had the same issue on 535 driver Headset: Hyperx cloud II with the default microphone that came with the headset (microphone is detachable) uname -r: 6.5.0-10-generic Headset and microphone work perfectly fine on other systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043208/+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
