[Kernel-packages] [Bug 2046841] Re: Unable to access UART2and UART4
Confirmed, it's a bootloader issue: https://github.com/raspberrypi/rpi- eeprom/issues/514 ** Bug watch added: github.com/raspberrypi/rpi-eeprom/issues #514 https://github.com/raspberrypi/rpi-eeprom/issues/514 ** Also affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware-raspi (Ubuntu) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2046841 Title: Unable to access UART2and UART4 Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Invalid Bug description: Ubuntu 23.10 6.5.0-1008-raspi I've summarized the problem here, and asked for help: https://askubuntu.com/questions/1496927/raspberry-pi-5-uart2-and- uart4-problem This question hasn't elicited a response. I'm assuming this is a problem with 6.5.0 kernel on Pi 5 hardware. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-1008-raspi 6.5.0-1008.11 ProcVersionSignature: Ubuntu 6.5.0-1008.11-raspi 6.5.3 Uname: Linux 6.5.0-1008-raspi aarch64 ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Tue Dec 19 09:54:18 2023 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/2046841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra-5.15/5.15.0.1020.20~20.04.16)
All autopkgtests for the newly accepted linux-meta-nvidia-tegra-5.15 (5.15.0.1020.20~20.04.16) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-nvidia-tegra-5.15/5.15.0-1020.20~20.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/focal/update_excuses.html#linux-meta-nvidia-tegra-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 2047780] Re: BlueZ release 5.71
> In other words, asking an Archive Admin to build binfmt-support on i386. I have stopped short of this so far because I'm entirely unsure if we still need that build dependency in the first place. Debian doesn't have it, and I'm not sure I see rationale on our end for it. There is probably something I'm missing, but I don't have the justification myself to make such a request. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
evolution-data-server still has uninstallable binaries on i386. You can ignore bluez for the binfmt-support issue. However, for bluez, Ubuntu uses --enable-phonebook-ebook . There are other phonebook options; maybe what Debian uses works for Debian. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2048467] [NEW] intel ax200 and ax210 wifi6 card drops connection
Public bug reported: Error: In the latest linux-firmware package for Ubuntu 23.10 (linux- firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb, and maybe others are affected, kernel 6.5.0-14 and 6.6.0-14) buggy firmware files are included for intel ax200 and ax210 cards (iwlwifi) and they drop net connection without any error messages. Solution: the firmware files should be changed to newer from https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git/ (iwlwifi-fw-2023-11-16-fixed or newer). ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: ax200 ax210 firmware intel iwlwifi linux -- 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/2048467 Title: intel ax200 and ax210 wifi6 card drops connection Status in linux-firmware package in Ubuntu: New Bug description: Error: In the latest linux-firmware package for Ubuntu 23.10 (linux- firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb, and maybe others are affected, kernel 6.5.0-14 and 6.6.0-14) buggy firmware files are included for intel ax200 and ax210 cards (iwlwifi) and they drop net connection without any error messages. Solution: the firmware files should be changed to newer from https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git/ (iwlwifi-fw-2023-11-16-fixed or newer). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048467/+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 2025616] Re: kernel Firmware Bug: TSC ADJUST differs failures during suspend
I have updated Ubuntu on my Lenovo Y520 from 18.04 to 23.10 (fresh install) and I have problems with suspending (freeze on suspend or wake up). I think it may be related to Nvidia. ``` [160828.853288] PM: suspend entry (deep) [160828.854252] Filesystems sync: 0.000 seconds [160828.882275] rfkill: input handler enabled [160829.005936] Freezing user space processes [160829.008956] Freezing user space processes completed (elapsed 0.003 seconds) [160829.008962] OOM killer disabled. [160829.008963] Freezing remaining freezable tasks [160829.010721] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [160829.010770] printk: Suspending console(s) (use no_console_suspend to debug) [160829.024762] wlp3s0: deauthenticating from 6c:5a:b0:c9:b8:2f by local choice (Reason: 3=DEAUTH_LEAVING) [160829.043993] sd 2:0:0:0: [sda] Synchronizing SCSI cache [160829.044204] sd 2:0:0:0: [sda] Stopping disk [160829.996520] ACPI: EC: interrupt blocked [160830.119907] ACPI: PM: Preparing to enter system sleep state S3 [160830.120226] ACPI: EC: event blocked [160830.120227] ACPI: EC: EC stopped [160830.120227] ACPI: PM: Saving platform NVS memory [160830.120464] Disabling non-boot CPUs ... [160830.121807] smpboot: CPU 1 is now offline [160830.123807] smpboot: CPU 2 is now offline [160830.125574] smpboot: CPU 3 is now offline [160830.127657] smpboot: CPU 4 is now offline [160830.129522] smpboot: CPU 5 is now offline [160830.131306] smpboot: CPU 6 is now offline [160830.133177] smpboot: CPU 7 is now offline [148701.924908] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -500554061. Restoring [160830.137174] ACPI: PM: Low-level resume complete [160830.137234] ACPI: EC: EC started [160830.137234] ACPI: PM: Restoring platform NVS memory [160830.138184] Enabling non-boot CPUs ... [160830.138212] smpboot: Booting Node 0 Processor 1 APIC 0x2 [160830.141748] CPU1 is up [160830.141767] smpboot: Booting Node 0 Processor 2 APIC 0x4 [160830.144344] CPU2 is up [160830.144360] smpboot: Booting Node 0 Processor 3 APIC 0x6 [160830.147856] CPU3 is up [160830.147871] smpboot: Booting Node 0 Processor 4 APIC 0x1 [160830.148759] CPU4 is up [160830.148775] smpboot: Booting Node 0 Processor 5 APIC 0x3 [160830.149453] CPU5 is up [160830.149469] smpboot: Booting Node 0 Processor 6 APIC 0x5 [160830.150163] CPU6 is up [160830.150179] smpboot: Booting Node 0 Processor 7 APIC 0x7 [160830.150898] CPU7 is up [160830.154911] ACPI: PM: Waking up from system sleep state S3 [160830.160550] ACPI: EC: interrupt unblocked [160831.452670] nvidia :01:00.0: Enabling HDA controller [160831.454493] ACPI: EC: event unblocked [160831.454557] rtlwifi: rtlwifi: wireless switch is on [160831.464924] i915 :00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it [160831.464956] i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it [160831.464988] i915 :00:02.0: [drm] [ENCODER:111:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it [160831.479757] nvme nvme0: Shutdown timeout set to 10 seconds [160831.480874] nvme nvme0: 8/0/0 default/read/poll queues [160831.652005] r8169 :04:00.0 enp4s0: Link is Down [160831.728074] usb 1-6: reset high-speed USB device number 5 using xhci_hcd [160832.004190] usb 1-11: reset full-speed USB device number 8 using xhci_hcd [160832.157958] pcieport :00:1c.0: PCI bridge to [bus 02] [160832.157971] pcieport :00:1c.0: bridge window [mem 0xa430-0xa43f] [160832.158016] pcieport :00:1c.2: PCI bridge to [bus 03] [160832.158019] pcieport :00:1c.2: bridge window [io 0x4000-0x4fff] [160832.157957] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_ops [i915]) [160832.158029] pcieport :00:1c.2: bridge window [mem 0xa420-0xa42f] [160832.158063] pcieport :00:1c.3: PCI bridge to [bus 04] [160832.158066] pcieport :00:1c.3: bridge window [io 0x3000-0x3fff] [160832.158075] pcieport :00:1c.3: bridge window [mem 0xa410-0xa41f] [160832.158476] OOM killer enabled. [160832.158478] Restarting tasks ... [160832.158486] pcieport :00:1d.0: PCI bridge to [bus 05] [160832.160223] pcieport :00:1d.0: bridge window [mem 0xa400-0xa40f] [160832.166190] done. [160832.166208] random: crng reseeded on system resumption [160832.166288] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [160832.167293] Bluetooth: hci0: RTL: rom_version status=0 version=1 [160832.167300] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821a_fw.bin [160832.167628] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821a_config.bin [160832.167657] Bluetooth: hci0: RTL: cfg_sz 10, total sz 17438 [160832.280199] PM: suspend exit [160832.468071] audit: type=1400 audit(1704653481.328:624): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_m
[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71
I appreciate everyone is frustrated. BlueZ isn't really staffed, it's just something I look at once or twice a year. The diff to Debian is shrinking over the long term, but again that's something I don't look at very often. The justification for Ubuntu using a separate process for the past 6 years or so is documented in: https://wiki.ubuntu.com/DesktopTeam/Bluetooth/BluezGit If this becomes contentious then I am happy for other people to own BlueZ and remove myself from ~bluetooth. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2041219] Re: GUI Freezes Randomly
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/2041219 Title: GUI Freezes Randomly Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: Hi, So everything would be working normally and then all of a sudden the laptop would freeze and nothing works. There's nothing in /var/crash. This has been run: cd ~/.local/share/gnome-shell/ rm -rf extensions output of journalctl -b-1 > prevboot.txt is attached --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darian 2556 F pulseaudio /dev/snd/pcmC0D0p: darian 2556 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-21 (66 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: PC Specialist Limited W94_95_97JU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic root=UUID=58ffdba8-72e3-43bd-8731-be66a705f3fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-35-generic N/A linux-backports-modules-6.2.0-35-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.21 Tags: jammy Uname: Linux 6.2.0-35-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: 10/21/2015 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W94_95_97JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/21/2015:br5.11:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: W94_95_97JU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041219/+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 2039744] Re: "Wi-Fi and Bluetooth drop or become unstable after updates
[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/2039744 Title: "Wi-Fi and Bluetooth drop or become unstable after updates Status in linux package in Ubuntu: Expired Bug description: A few updates ago, the Wi-Fi and Bluetooth, which were working perfectly after previous fixes for the Realtek RTL8821CE 802.11ac, have become unstable again. Wi-Fi constantly drops, and Bluetooth has poor and choppy audio. I noticed this problem occurring after a few updates because everything was working perfectly (there were problems in the LTS version in the past, but they had been fixed, and in 23+, there were no issues until now). The process is as follows: I boot up the system, Wi-Fi works for a few minutes, then it drops, and no adapters are recognized. I reboot the system. Sometimes it works perfectly, other times the same issue repeats. Bluetooth doesn't drop, but with headphones, the audio keeps cutting out and is of low quality. I've observed this for about a month. Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:116:13148161:2023-10-14 16:11:38.138230265 -0300:2023-10-14 16:11:33.682230383 -0300:/var/crash/_opt_Mullvad VPN_mullvad-gui.1000.crash 640:1000:116:14139946:2023-10-17 20:20:44.478106198 -0300:2023-10-17 20:20:37.026158833 -0300:/var/crash/_usr_share_codium_codium.1000.crash 640:1000:116:6818241:2023-10-16 10:59:47.318844220 -0300:2023-10-16 10:59:35.422911209 -0300:/var/crash/_usr_lib_x86_64-linux-gnu_libexec_baloo_file.1000.crash CurrentDesktop: KDE Date: Wed Oct 18 19:37:32 2023 InstallationDate: Installed on 2023-10-01 (17 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) PackageArchitecture: all ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alpha-ai 4011 F wireplumber /dev/snd/seq:alpha-ai 4009 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-10-01 (27 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UAR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-35-generic N/A linux-backports-modules-6.2.0-35-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.8 Tags: wayland-session lunar Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 08/23/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540UAR.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540UAR 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540UAR.306:bd08/23/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X540UAR 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/2039744/+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 2047780] Re: BlueZ release 5.71
It looks like most of you are members of ~bluetooth already via ~ubuntu- core-dev so feel free to commit directly to https://git.launchpad.net/~bluetooth/bluez in future. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71
Thank you for working over the weekend on this. I would have resolved it myself on the Monday if someone answered the question in comment #11. Also I've sent a bug report to Debian about their orig tarball not matching the upstream release tarball. I feel that's a discussion they need to have with upstream: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1060242 -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2034491] Re: Fix blank display when Thunderbolt monitor is plugged second time
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid -- 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/2034491 Title: Fix blank display when Thunderbolt monitor is plugged second time Status in HWE Next: New Status in linux package in Ubuntu: Fix Released 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: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [Impact] When a Thunderbolt monitor gets plugged to an AMD laptop for second time, the Thunderbolt monitor remains blank. [Fix] Reinitialize TMU and perform proper Time Synchronization Handshake every time. [Test] The Thunderbolt monitor still has image after many replugging. [Where problems could occur] This change the flow on disabling TMU, which is responsible for time synchronization, so behavior of Thunderbolt docking might be affected. Per my limited test no issue has been observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034491/+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 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-440 440.100-0ubuntu1 in noble libnvidia-cfg1-430 440.100-0ubuntu1 in noble amd64 libnvidia-common-430 440.100-0ubuntu1 in noble amd64 libnvidia-common-430 440.100-0ubuntu1 in noble arm64 libnvidia-common-430 440.100-0ubuntu1 in noble armhf libnvidia-common-430 440.100-0ubuntu1 in noble i386 libnvidia-common-430 440.100-0ubuntu1 in noble ppc64el libnvidia-common-430 440.100-0ubuntu1 in noble riscv64 libnvidia-common-430 440.100-0ubuntu1 in noble s390x libnvidia-common-440 440.100-0ubuntu1 in noble amd64 libnvidia-common-440 440.100-0ubuntu1 in noble arm64 libnvidia-common-440 440.100-0ubuntu1 in noble armhf libnvidia-common-440 440.100-0ubuntu1 in noble i386 libnvidia-common-440 440.100-0ubuntu1 in noble ppc64el libnvidia-common-440 440.100-0ubuntu1 in noble riscv64 libnvidia-common-440 440.100-0ubuntu1 in noble s390x libnvidia-compute-430 440.100-0ubuntu1 in noble amd64 libnvidia-compute-430 440.100-0ubuntu1 in noble i386 libnvidia-decode-430 440.100-0ubuntu1 in noble amd64 libnvidia-decode-430 440.100-0ubuntu1 in noble i386 libnvidia-encode-430 440.100-0ubuntu1 in noble amd64 libnvidia-encode-430 440.100-0ubuntu1 in noble i386 libnvidia-fbc1-430 440.100-0ubuntu1 in noble amd64 libnvidia-fbc1-430 440.100-0ubuntu1 in noble i386 libnvidia-gl-430 440.100-0ubuntu1 in noble amd64 libnvidia-gl-430 440.100-0ubuntu1 in noble i386 libnvidia-ifr1-430 440.100-0ubuntu1 in noble amd64 libnvidia-ifr1-430 440.100-0ubuntu1 in noble i386 nvidia-compute-utils-430 440.100-0ubuntu1 in noble amd64 nvidia-dkms-430 440.100-0ubuntu1 in noble amd64 nvidia-driver-430 440.100-0ubuntu1 in noble amd64 nvidia-headless-430 440.100-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-430 440.100-0ubuntu1 in noble amd64 nvidia-kernel-common-430 440.100-0ubuntu1 in noble amd64 nvidia-kernel-source-430 440.100-0ubuntu1 in noble amd64 nvidia-utils-430 440.100-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-430 440.100-0ubuntu1 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+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 2047780] Re: BlueZ release 5.71
Daniel, I don't want you to feel burned over this. That wiki page does seem quite rational, and I appreciate that you linked it. I'm reading some mixed feelings, so let me be clear: thank you for the work you *are* able to put into this. Both Gianfranco and I are Ubuntu Core Developers but are also Debian Developers. An expectation of working with Debian is #3 of the Social Contract, "Don't Hide Problems" https://www.debian.org/social_contract If Debian has problems in their packaging that do exist, please file a bug. If the maintainer is non-responsive in Debian, there is a process for non-maintainer uploads (and I would personally help you with this). My point of disagreement is not how we are addressing the Ubuntu uploads as much as how we are working with Debian to fix them. If the Debian team is non-collaborative, that should be addressed with the appropriate governance board. Either way, there should be a clear diff, whether the community has to help or not. That being said, considerateness is part of Ubuntu's CoC. I will push my commits there in the morning. I do apologize again for any undue stress. I would rather address this head on, because it means a better Bluetooth package for our users. Jeremy, the reason evolution-data-server has uninstallable binaries is because of the binfmt-supoort i386 allowlist issue at hand. Please confirm whether you have a customer story that will be impacted by this, or if we think a user will seriously need this support on i386 in 2024. I may be an Ubuntu Core Developer, but I respect that it's not my call alone to make, and the last thing I want to do is regress something for a customer. That's why I'm being up front about these issues. -- 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/2047780 Title: BlueZ release 5.71 Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.71 to noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2011389] Re: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2011389 Title: vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid 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.0 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: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] With wwan t7xx driver patched, vmd may fail the probe process because it does not lock properly. [Fix] https://lore.kernel.org/linux- pci/20230313173733.1815277-1-vicamo.y...@canonical.com/T/#u [Test Case] Verify on platforms with FM350 wwan module with prebuilt oem-6.1 or above kernels. No vmd probe error should be found in dmesg. [Where problems could occur] This is the way it should have been done. [Other Info] This is not reproducible with v6.0 or older kernels, so only Lunar and oem-6.1 are nominated for fix. OEM-6.0 patch goes to Gerrit instead. == original bug report == vmd may fail to create sysfs entry while `pci_rescan_bus()` called in some other drivers like wwan. This happens after bug 2002089 re-added pci rescan feature back to wwan t7xx driver to support firmware updates via devlink. t7xx may call `pci_rescan_bus()` with proper locks, but vmd doesn't. sysfs: cannot create duplicate filename '/devices/.../resource0' Call Trace: sysfs_warn_dup.cold+0x17/0x34 sysfs_add_bin_file_mode_ns+0xc0/0xf0 sysfs_create_bin_file+0x6d/0xb0 pci_create_attr+0x117/0x260 pci_create_resource_files+0x6b/0x150 pci_create_sysfs_dev_files+0x18/0x30 pci_bus_add_device+0x30/0x80 pci_bus_add_devices+0x31/0x80 pci_bus_add_devices+0x5b/0x80 vmd_enable_domain.constprop.0+0x6b7/0x880 [vmd] vmd_probe+0x16d/0x193 [vmd] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2011389/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid 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: Fix Released Status in linux-oem-6.0 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: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid 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: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid 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] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
I have HAWAII (R9 290X). I get the following:
array-index-out-of-bounds in
/build/linux-7T0Dsf/linux-6.6.6/drivers/gpu/drm/radeon/radeon_atombios.c:2717:34
index 18 is out of range for type 'UCHAR [1]'
array-index-out-of-bounds in
/build/linux-7T0Dsf/linux-6.6.6/drivers/gpu/drm/radeon/radeon_atombios.c:2715:55
index 1 is out of range for type 'UCHAR [1]'
UBSAN: array-index-out-of-bounds in
/build/linux-7T0Dsf/linux-6.6.6/drivers/gpu/drm/radeon/ci_dpm.c:5588:32
index 9 is out of range for type 'UCHAR [1]'
--
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/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
Error in boot:
[8.597520] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
[8.597527] index 7 is out of range for type
'ATOM_Polaris_SCLK_Dependency_Record [1]'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-generic 6.5.0.9.11
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
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 09:28:16 2023
InstallationDate: Installed on 2022-10-12 (373 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3
sysrq_always_enabled=1 audit=0 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: Upgraded to mantic on 2023-10-13 (6 days ago)
dmi.bios.date: 07/11/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: D3EMW08.110
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: D3F3-EM
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDION
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: D3F3-EM
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MEDION
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
The final discuss and version are here
https://bugzilla.kernel.org/show_bug.cgi?id=216877
https://patchwork.kernel.org/project/linux-pci/patch/20231221011250.191599-1-david.e@linux.intel.com/
And koba has backported the old version of that commit to oem kernel
commit 16e5386dabd18bd9c507867b0df6c414783af4a8
Author: Mika Westerberg
Date: Mon Oct 2 10:00:44 2023 +0300
UBUNTU: SAUCE: PCI/ASPM: Add back L1 PM Substate save and restore
BugLink: https://bugs.launchpad.net/bugs/2042500
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.
Reported-by: Koba Ko
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217321
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216782
Link: https://bugzilla.kernel.org/show_bug.cgi?id=216877
Cc: Tasev Nikola
Cc: Mark Enriquez
Cc: Thomas Witt
Cc: Werner Sembach
Tested-by: Kai-Heng Feng
Signed-off-by: Mika Westerberg
Reviewed-by: Ilpo Järvinen
(backported from
https://lore.kernel.org/all/20231002070044.2299644-1-mika.westerb...@linux.intel.com/)
Signed-off-by: Koba Ko
Signed-off-by: Timo Aaltonen
** Bug watch added: Linux Kernel Bug Tracker #216877
https://bugzilla.kernel.org/show_bug.cgi?id=216877
** Bug watch added: Linux Kernel Bug Tracker #217321
https://bugzilla.kernel.org/show_bug.cgi?id=217321
** Bug watch added: Linux Kernel Bug Tracker #216782
https://bugzilla.kernel.org/show_bug.cgi?id=216782
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1980829
Title:
System freeze after resuming from suspend due to PCI ASPM settings
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
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 Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux-oem-6.0 source package in Focal:
Invalid
Status in linux-oem-6.1 source package in Focal:
Invalid
Status in linux-oem-6.5 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.14 source package in Kinetic:
Invalid
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Status in linux-oem-6.5 source package in Kinetic:
Invalid
Bug description:
For OEM-6.1
[Impact]
While
[Kernel-packages] [Bug 2048467] Re: intel ax200 and ax210 wifi6 card drops connection
** Tags added: kern-8847 -- 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/2048467 Title: intel ax200 and ax210 wifi6 card drops connection Status in linux-firmware package in Ubuntu: New Bug description: Error: In the latest linux-firmware package for Ubuntu 23.10 (linux- firmware_20230919.git3672ccab-0ubuntu2.1_amd64.deb, and maybe others are affected, kernel 6.5.0-14 and 6.6.0-14) buggy firmware files are included for intel ax200 and ax210 cards (iwlwifi) and they drop net connection without any error messages. Solution: the firmware files should be changed to newer from https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git/ (iwlwifi-fw-2023-11-16-fixed or newer). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid 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 Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux-oem-6.5 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux-oem-6.5 source package in Kinetic: Invalid Bug description: For OEM-6.1 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] Below commit fixed the issue, but not going to be merged into mainline. The patch is still under discussion and have other variance, and we already merged the origin patch into oem-6.0 and 5.15/5.19 for a year, so could consider it's safer for us. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ I also created a DMI quirk to make the patches only affects on listed platforms. [Test] The affected machines could suspend/resume well. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For OEM-6.0 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
