[Kernel-packages] [Bug 1952403] Re: Realtek 8822CE wireless card fails to work after laptop discharge in sleep
I can confirm now that this isn't only an issue of the wireless card.
USB type C doesn't work as well, unless I enter the BIOS on boot. I
will document the error messages I get and return with more data on USB
type C as well
** Summary changed:
- Realtek 8822CE wireless card fails to work after laptop discharge in sleep
+ Laptop discharged while in sleep breaks Realtek 8822CE wireless card and USB
type C on Asus TUF FA506IV
--
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/1952403
Title:
Laptop discharged while in sleep breaks Realtek 8822CE wireless card
and USB type C on Asus TUF FA506IV
Status in linux package in Ubuntu:
Incomplete
Bug description:
I own an Asus TUF A15 FA506IV laptop with Ubuntu 21.10. After putting
it to sleep it discharged. Turning it back on the Wireless cards
doesn't work.
This is what I found in the logs that could help:
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:311] info: Store:
POWER_RESUMED
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:312] info: Store:
SET_SUSPEND_STATUS true
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:313] info:
[DESKTOP-SIDE-EFFECT] Update from desktop for keys ["app"]
Nov 24 15:25:56 Zveri2 kernel: [21587.358139] rtw_8822ce :03:00.0: start
vif 80:30:49:cc:98:0f on port 0
Nov 24 15:25:56 Zveri2 charon: 01[KNL] interface wlp3s0 activated
Nov 24 15:25:56 Zveri2 NetworkManager[1059]: [1637760356.4839]
manager: NetworkManager state is now CONNECTED_LOCAL
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:489] info:
NetworkStatus: Network check failed {
Nov 24 15:25:56 Zveri2 krunner[16146]: "error": "Failed to fetch"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
Nov 24 15:25:56 Zveri2 krunner[16146]: [11/24/21, 15:25:56:490] info: Network
status check {
Nov 24 15:25:56 Zveri2 krunner[16146]: "elapsed_time_ms": 999784,
Nov 24 15:25:56 Zveri2 krunner[16146]: "navigator_online": false,
Nov 24 15:25:56 Zveri2 krunner[16146]: "api_test": "offline"
Nov 24 15:25:56 Zveri2 krunner[16146]: }
After this I am getting the following trace:
Nov 24 15:26:05 Zveri2 kernel: [21596.291200] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[0]
Nov 24 15:26:05 Zveri2 kernel: [21596.291287] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[1]
Nov 24 15:26:05 Zveri2 kernel: [21596.291365] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[2]
Nov 24 15:26:05 Zveri2 kernel: [21596.291484] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[3]
Nov 24 15:26:05 Zveri2 kernel: [21596.291570] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[5]
Nov 24 15:26:05 Zveri2 kernel: [21596.291651] rtw_8822ce :03:00.0: timed
out to flush pci tx ring[6]
Nov 24 15:26:06 Zveri2 krunner[16146]: [11/24/21, 15:26:06:125] info:
[NETWORK-CONNECTIVITY] Failed to establish a connection after 10 attempt(s).
Nov 24 15:26:07 Zveri2 kernel: [21598.291806] rtw_8822ce :03:00.0: failed
to poll offset=0x5 mask=0x2 value=0x0
Nov 24 15:26:07 Zveri2 kernel: [21598.292047] [ cut here
]
Nov 24 15:26:07 Zveri2 kernel: [21598.292049] failed to read DBI register,
addr=0x0719
Nov 24 15:26:07 Zveri2 kernel: [21598.292082] WARNING: CPU: 2 PID: 17826 at
drivers/net/wireless/realtek/rtw88/pci.c:1310 rtw_dbi_read8.constprop.0+0x
aa/0xc0 [rtw88_pci]
Nov 24 15:26:07 Zveri2 kernel: [21598.292096] Modules linked in:
nf_conntrack_netlink xt_addrtype br_netfilter vboxnetadp(OE) vboxnetflt(OE)
xfrm_user
xfrm_algo vboxdrv(OE) rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack
ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink bridge stp llc
cmac algif_hash algif_skcipher overlay af_alg bnep binfmt_misc zfs(PO) zu
nicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O)
intel_rapl_msr intel_rapl_common joydev snd_hda_codec_realtek snd_hda_code
c_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel edac_mce_amd
snd_intel_dspcfg snd_intel_sdw_acpi uvcvideo snd_hda_codec rtw88_8822ce rtw88_88
22c videobuf2_vmalloc snd_hda_core kvm_amd snd_hwdep rtw88_pci btusb
videobuf2_memops snd_pcm btrtl rtw88_core videobuf2_v4l2 btbcm videobuf2_common
k
vm btintel snd_seq_midi bluetooth videodev snd_seq_midi_event ecdh_generic
nls_iso8859_1 mc mac80211 rapl ecc snd_rawmidi input_leds
Nov 24 15:26:07 Zveri2 kernel: [21598.292174] serio_raw efi_pstore wmi_bmof
hid_multitouch snd_seq k10temp snd_seq_device cfg80211 snd_timer ucsi_ccg
snd snd_rn_pci_acp3x libarc4 ccp snd_pci_acp3x soundcore ucsi_acpi
typec_ucsi typec asus_wireless mac_hid nvidia_uvm(POE) sch_fq_codel msr
parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs blake2b_generic
xor zstd_compress raid6_pq libcrc32c dm_crypt
[Kernel-packages] [Bug 1947484] Re: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged
It took me 9 years to fix my binary on my personal pc and 3 years to extensivly test so its not completely done but is exact once I map it in the way I would like to power it on as. from Sys_IO_src_map to and from Memory anf Afic or APic as to fifo and API source to C and Renderer/Compiler. Most people use whole numbers as I prefered to Start with decimals to new base that will be perment as to Exact entries in a database = 8it as 32 or 64 or 912 for nano Technology advances or 838 -- 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/1947484 Title: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged Status in linux package in Ubuntu: Expired Bug description: I'm using KDE Plasma on Ubuntu 21.10 with kernel 5.13.0-19. Recently, my laptop has been freezing upon unplugging the power cord. The sysrq keys do not work when this occurs. Previously, the problem appeared to resolve when switching kernels. However, when I tried to obtain logs, the problem began to occur on all installed kernels (5.14.12, 5.13.19, and 5.13.18 from https://kernel.ubuntu.com/~kernel-ppa/mainline/). Logs cannot be obtained because none appear to be saved to disk during the crash. (journalctl -k -b -1) Since the problem appears kernel related, I tried removing potentially problematic kernel options from /etc/default/grub. After removing all acpi and i915 options (which I had enabled because they had previously been needed to make the backlight work and reduce gpu crashes), the problem again *appears* to have resolved with all of the aforementioned kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947484/+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 1947484] Re: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged
Im on my Own Web Source Directly to and from Dom Exceptions from The Internets Host where the internet has to gather its own sources from me as to the large injunction in the USAhttps://bugs.launchpad.net/bugs/1947484 Title: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged Status in linux package in Ubuntu: Expired Bug description: I'm using KDE Plasma on Ubuntu 21.10 with kernel 5.13.0-19. Recently, my laptop has been freezing upon unplugging the power cord. The sysrq keys do not work when this occurs. Previously, the problem appeared to resolve when switching kernels. However, when I tried to obtain logs, the problem began to occur on all installed kernels (5.14.12, 5.13.19, and 5.13.18 from https://kernel.ubuntu.com/~kernel-ppa/mainline/). Logs cannot be obtained because none appear to be saved to disk during the crash. (journalctl -k -b -1) Since the problem appears kernel related, I tried removing potentially problematic kernel options from /etc/default/grub. After removing all acpi and i915 options (which I had enabled because they had previously been needed to make the backlight work and reduce gpu crashes), the problem again *appears* to have resolved with all of the aforementioned kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947484/+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 1947484] Re: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged
Your Problems rely on Ubuntu and its Base from the PCs Manufactored Pre- set Binary as to errors with Ubuntu as I have copied the origin repo on Github and placed it in a private Collection as to Creation of a new Software Around Ubiquity from Ubuntu Utilizing a Hybrid Image from Cinamon from Ubuntus Power Module at Screen Login integrated to Linux Mint back to Cinamon while molding scripts to form src from all 3 oss' Where Ubuntu Powers on my Preboot through Cache to a Home Dirctory where Mint was installed on Cinamons Base untill I had revised a Over Time to Utiliz mint in Place of Cinamon as OS at Desktop to Mint While Home was Cinamons Base Install to form a new Dynamic Cache base at PCs Ctl back to Processor to .disk then reversed the Origin State of In Which I had installed the New Hybrid Image to Ubuntu being installed onto the OS's desktop Enviornment after boot Where Cinamon is Built-in to KDE from wine back to its origining state but installed as boot trajectory only to mount Modules for Ubuntu to Oem as OS at root and mint being Unnamed as Cache to and from Disk at Power on configuring Disk as .disk to Swap a Timeshift for Working Enviornments to and From PC Components to reform its composure of Binary from its initalized starting state at 0 to reform a new Private Source for source mappings at Development to utilize Timeshift for Quick Testing before Finalizing Hardware firmware to Software installing Firmware for drivers to efficiently Handle the Components in a virtual Runtime without affecting the Base of the Drivers where Damages to the COmponent could occur as to my Runtime Directly Affecting the Components ran from software to hardware mount points with or without a virtual runtime to the Components Directly for Revisions in Firmware on Software or for Revisions on the Drivers installed from Software While Booted in TimeShift to test. Where efi is essentially Fifo or file in file object. Over 4 years I have revised installation of Oem Linux and Cinamon to Form a New Source to revise a New OS Utilizing all three to Create a New Staged Platform Source that I can Boot from Efi or Without an Efi tht utilizes Efi alternativly other than Filesystem or Sbin Home Methods of Distro to Installation of OS while Reformating my PC to Reprogram itself or any PC I May purchase in the Future as My Hybrid would Install to another Pc but not all Functions would Work the Same at the Moment as I have Worked with the my Countries main Injunction as the First problem. I have remapped the SOurce from Components to Ld.S while from a new Module To connect A button on my Pc to My Source collection of my Project and Prevented Updates to and from Sources of Current CopyWritten OSs' Source Distro while repopulating the Same source for Variants and Building Structure of Similarities for storage by utilizing Debian from install from my Casper Variant of Piping Debian from My Sys Source Map to Io from Installation to Reformat the Installation from pluggin a Usb into my Usb Hub from Power on Selecting Usb from boot to New Installation after reconfiguring my Mounts to load my PC from the .disk from defragmntation to installation at format for a new Binary structure of Reverse-byte induction to repopulated each cylinder and head to a allow for compression of anything installed and a new kernel Offset to support a Solution prevent a -binary injuntion from occuring or reoccuring Utilizng a mathmatical Number in the forum of a squar root of a Radicals radical to be exact as to a Mathmatical equation I have mapped to form a Whole number = to a decimal from a preatomic scale that creates a centrifuge of a distance between 1 and -1 as an imaganiary number that counts by metrics untill powered on utilizing hex or color as to prevention of missuse while mapping it to and from .1 as .01 before it is 1 starting a .1s radical from imaginary number counting of placing metrics back to whole numbers as halfs then adding and subtracting the lengths of the origing metrics from total imaginary numbers used from both differences of 1 and -1 to be the metrics conversion to and from hex = to decimal and exact to whole numbers at my Mathmatical Forum equation creating two variants of +1 and -1 until my Binary maps in that -1 is memory or runtime enviornment as I have remapped my binary to be = to -0 as 0 = 21 as 32 or 64 supporting a new Kernel Offset to be formed at 537 and 838 where 537 is the inital script or first ran process to numanode on call from ld.s Script. As I have fomated New objects in a new format from an object while utilizing a simple function of 1 =1 == 1=2==2=3==3=4== 5 if New Object = to [Systmem].New Object format which creates a new Extension to all Known Extensions as the Extensions in the reg. As I have also Created a New String and Reformated a Known Script to reform any Object or call to remap a new Var function similar to a log file to only run what is called while Keeping in locked from exceptions by utilzing a
[Kernel-packages] [Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
** Tags added: originate-from-1955059 stella -- 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/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] On ADL platform, I+N sku, get the cpufreq errors during boot-up, [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) The commit has been landed on mainline since v5.15-rc1. [Test Case] 1. boot-up the machine. 2. check dmesg if the cpufreq error is presented. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+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 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
I don't know what happened, but apparently my system doesn't want the 5.13 kernel installed anymore. I just managed to remove it (and the related NVidia kernel module packages) without causing any conflicts or triggering any meta-package complaints... Which is great, because it means I don't have to hack grub into booting the 5.11 kernel now :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1952674/+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 1947484] Re: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged
[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/1947484 Title: Ubuntu 21.10, 5.13.0-19. System freeze when power cable unplugged Status in linux package in Ubuntu: Expired Bug description: I'm using KDE Plasma on Ubuntu 21.10 with kernel 5.13.0-19. Recently, my laptop has been freezing upon unplugging the power cord. The sysrq keys do not work when this occurs. Previously, the problem appeared to resolve when switching kernels. However, when I tried to obtain logs, the problem began to occur on all installed kernels (5.14.12, 5.13.19, and 5.13.18 from https://kernel.ubuntu.com/~kernel-ppa/mainline/). Logs cannot be obtained because none appear to be saved to disk during the crash. (journalctl -k -b -1) Since the problem appears kernel related, I tried removing potentially problematic kernel options from /etc/default/grub. After removing all acpi and i915 options (which I had enabled because they had previously been needed to make the backlight work and reduce gpu crashes), the problem again *appears* to have resolved with all of the aforementioned kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947484/+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 1908800] Re: Wireless card crashes daily on my XPS 13 9380
I updated the firmware for this card from the 00157 to the 00288 version of firmware: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 and it seems to have fixed it but still I get: ath10k_pci :3a:00.0: failed to install key for vdev 0 peer MY_AP_MAC_ADDRESS: -110 in my journal and on dmesg. but things seem to not disconnect for me. -- 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/1908800 Title: Wireless card crashes daily on my XPS 13 9380 Status in linux-firmware package in Ubuntu: New Bug description: Hello all, Daily, or multiple times per day, the wireless card on my XPS 13 9380 crashes, forcing me to shutdown my computer and then boot it back up. I am on Ubuntu 20.04, and here is the results from dmesg -T right after such a crash happens: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware crashed! (guid 170ee3ba-1809-4276-9b34-9d4e37da0937) [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 29eb8ca1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 4ac0889b [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to get memcpy hi address for firmware address 4: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read firmware dump area: -16 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: Copy Engine register dump: [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [00]: 0x00034400 11 11 3 3 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [01]: 0x00034800 23 23 164 165 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [02]: 0x00034c00 31 30 93 94 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [03]: 0x00035000 20 20 22 20 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [04]: 0x00035400 4711 4707 114 50 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [06]: 0x00035c00 7 7 12 12 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: [07]: 0x00036000 1 0 1 0 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: failed to read hi_board_data address: -28 [Sat Dec 19 15:08:59 2020] ieee80211 phy0: Hardware restart was requested [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: unsupported HTC service id: 1536 [Sat Dec 19 15:08:59 2020] ath10k_pci :02:00.0: device successfully recovered lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.187.6 Candidate: 1.187.6 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bsbrom 3384 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 19 15:21:02 2020 Dependencies: InstallationDate: Installed on 2020-09-05 (105 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 13 9380 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wxgq6h@/vmlinuz-5.4.0-58-generic root=ZFS=rpool/ROOT/ubuntu_wxgq6h ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd07/06/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
Verified this on the Impish kernel on my laptop with ~40 minutes of
testing. Looks OK to me, no regressions noted.
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 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.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+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 1955087] [NEW] bluetooth cannot transfer files to phone although connected
Public bug reported: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth focal -- 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/1955087 Title: bluetooth cannot transfer files to phone although connected Status in bluez package in Ubuntu: New Bug description: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1955087/+subscriptions -- Mailing
[Kernel-packages] [Bug 1951424] Re: No audio after install ubuntu 21.10 on Acer swift 3
** 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/1951424 Title: No audio after install ubuntu 21.10 on Acer swift 3 Status in linux package in Ubuntu: Invalid Bug description: dmesg shows below errors: (see intel-sdw lines) [3.428920] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [3.461588] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [3.482055] sof-audio-pci-intel-tgl :00:1f.3: No SoundWire machine driver found [3.482059] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 5 [3.482061] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.482066] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [3.584389] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 1:6:0-18fab [3.584392] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [3.586144] intel-sdw intel-sdw.0: Bus clash for control word [3.586147] intel-sdw intel-sdw.0: Bus clash for data word [3.586169] intel-sdw intel-sdw.1: Bus clash for control word [3.586171] intel-sdw intel-sdw.1: Bus clash for data word [3.586227] intel-sdw intel-sdw.0: Bus clash for control word [3.586230] intel-sdw intel-sdw.1: Bus clash for control word [3.586275] intel-sdw intel-sdw.0: Bus clash for control word [3.586279] intel-sdw intel-sdw.1: Bus clash for control word [3.586342] intel-sdw intel-sdw.0: Bus clash for control word [3.586346] intel-sdw intel-sdw.1: Bus clash for control word [3.586395] intel-sdw intel-sdw.0: Bus clash for control word [3.586398] intel-sdw intel-sdw.1: Bus clash for control word [3.593087] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [3.610615] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [3.640221] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.640226] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.640228] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.640229] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [3.640230] snd_hda_codec_realtek ehdaudio0D0:inputs: [3.688338] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten [3.688344] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten [3.688440] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten [3.688444] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten [3.688447] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten [3.688450] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten [3.688452] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten [3.688456] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten [3.688460] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten [3.688463] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten [3.688468] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten [3.688471] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten [3.688475] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten [3.688482] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3 [3.688483] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4 [3.688484] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 5 [3.688485] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 6 [3.688486] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 7 [3.688487] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8 [3.707637] input: sof-hda-dsp Front Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [3.707683] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input18 [3.707715] input:
[Kernel-packages] [Bug 1954815] Re: Support newer kernels
So it looks like the proposal here is to backport the impish version of crash back through focal, which means an upstream version bump. Resolving the issue in this way normally requires a documented special case to the SRU process[*], and I don't see one that includes the crash package. I'd be supportive of such a special case for crash as this package usually needs updates to support new HWE kernels (same w/ makedumpfile) but, unless an ubuntu-sru-team members says differently, I think we need to go through that process first. Cascardo: would you mind drafting a special case page? Alternatively, we could investigate if there's a more surgical way to add support for the desired kernels to the crash version already in focal. [*] https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1954815 Title: Support newer kernels Status in crash package in Ubuntu: Invalid Status in crash source package in Focal: In Progress Status in crash source package in Hirsute: In Progress Status in crash source package in Impish: Fix Released Bug description: [Impact] Kernels newer than 5.4 cannot be analyzed using the crash tool from Focal. [Test case] Install a linux dbgsym package and run the command below, replacing vmlinux-5.11.0-1023-azure by the appropriate kernel debug file. crash /usr/lib/debug/boot/vmlinux-5.11.0-1023-azure /proc/kcore [Potential regression] crash might fail to work with older kernels, or some of its commands might not work anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1954815/+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 1946672] Re: Enable multicast in the "kvm" kernels
verified CONFIG_IP_MULTICAST is enabled on focal/kvm in proposed. switching verification testing to done. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1946672 Title: Enable multicast in the "kvm" kernels Status in cloud-images: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Focal: Fix Committed Bug description: I work in the OpenStack Neutron project and recently I wanted to optimize our CI scenario jobs by using Ubuntu minimal image as guest image for some tests (see patch https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813195) Unfortunately it seems that there is problem with one multicast scenario test while using ubuntu-minimal image (https://cloud-images.ubuntu.com/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img). The problem is that VM booted from that image don't subscribes properly to the IGMP multicast group thus test is failing. All works fine when image https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img is used in the same test. The problem is that in the minimal image kernel linux-image-kvm (vs. linux-image-generic in the "regular" cloud image) and that "-kvm" image has disabled MULTICAST: # CONFIG_IP_MULTICAST is not set Would it be maybe possible to enable this option in the kernel used in the "minimal" cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1946672/+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 1955083] [NEW] Hirsute update: upstream stable patchset 2021-12-16
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-16 Ported from the following upstream stable releases: v5.10.81, v5.14.21, v5.15.4 from git://git.kernel.org/ Note: upstream stable v5.14 has now reached EOL, as of v5.14.21. fortify: Explicitly disable Clang support block: Add a helper to validate the block size loop: Use blk_validate_block_size() to validate block size bootconfig: init: Fix memblock leak in xbc_make_cmdline() net: stmmac: add clocks management for gmac driver net: stmmac: platform: fix build error with !CONFIG_PM_SLEEP net: stmmac: fix missing unlock on error in stmmac_suspend() net: stmmac: fix system hang if change mac address after interface ifdown net: stmmac: fix issue where clk is being unprepared twice net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings x86/iopl: Fake iopl(3) CLI/STI usage parisc/entry: fix trace test in syscall exit path PCI/MSI: Destroy sysfs before freeing entries PCI/MSI: Deal with devices lying about their MSI mask capability PCI: Add MSI masking quirk for Nvidia ION AHCI erofs: remove the occupied parameter from z_erofs_pagevec_enqueue() erofs: fix unsafe pagevec reuse of hooked pclusters scripts/lld-version.sh: Rewrite based on upstream ld-version.sh perf/core: Avoid put_page() when GUP fails thermal: Fix NULL pointer dereferences in of_thermal_ functions selftests/x86/iopl: Adjust to the faked iopl CLI/STI usage Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. Bluetooth: btusb: Add support for TP-Link UB500 Adapter string: uninline memcpy_and_pad btrfs: introduce btrfs_is_data_reloc_root btrfs: zoned: only allow one process to add pages to a relocation inode UBUNTU: upstream stable to v5.10.81, v5.14.21, v5.15.4 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-12-16 -upstream stable patchset 2021-12-16 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.81, v5.14.21, v5.15.4 + + from git://git.kernel.org/ + +Note: upstream stable v5.14 has now reached EOL, as of v5.14.21. + + fortify: Explicitly disable Clang support + block: Add a helper to validate the block size + loop: Use blk_validate_block_size() to validate block size + bootconfig: init: Fix memblock leak in xbc_make_cmdline() + net: stmmac: add clocks management for gmac driver + net: stmmac: platform: fix build error with !CONFIG_PM_SLEEP + net: stmmac: fix missing unlock on error in stmmac_suspend() + net: stmmac: fix system hang if change mac address after interface ifdown + net: stmmac: fix issue where clk is being unprepared twice + net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings + x86/iopl: Fake iopl(3) CLI/STI usage + parisc/entry: fix trace test in
[Kernel-packages] [Bug 1953689] Re: smartpqi: Update 20.04.4 to latest kernel.org patch level
I updated the SRU Justification ** Description changed: SRU Justification: Impact: - + Update the smartpqi driver with latest kernel.org patches from git repo: + git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git + + These patches will align the Canonical smartpqi driver with kernel.org + Fix: This is targeted at 5.13 for 20.04.4 HWE Here is a list of patches that need applied to 20.04.4 to bring the smartpqi up to date with kernel.org. - 64fc9015fbeb scsi: smartpqi: Switch to attribute groups - 0ca190805784 scsi: smartpqi: Call scsi_done() directly + 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 80982656b78e scsi: smartpqi: Add 3252-8i PCI id d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump 819225b03dc7 scsi: smartpqi: Update device removal management 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array member These patches should all be upstream as of 5.16. Testcase: - + kdump tests. + fio performance testing to demonstrate no performance regressions. -- 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/1953689 Title: smartpqi: Update 20.04.4 to latest kernel.org patch level Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: Update the smartpqi driver with latest kernel.org patches from git repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git These patches will align the Canonical smartpqi driver with kernel.org Fix: This is targeted at 5.13 for 20.04.4 HWE Here is a list of patches that need applied to 20.04.4 to bring the smartpqi up to date with kernel.org. 605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055 80982656b78e scsi: smartpqi: Add 3252-8i PCI id d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers 987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild 28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs 4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation 6ce1ddf53252 scsi: smartpqi: Update LUN reset handler 5d1f03e6f49a scsi: smartpqi: Capture controller reason codes 9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump 819225b03dc7 scsi: smartpqi: Update device removal management 5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array member These patches should all be upstream as of 5.16. Testcase: kdump tests. fio performance testing to demonstrate no performance regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953689/+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 1955075] [NEW] Touchpad not found at all
Public bug reported: Dear Ubuntu Pros, after 33 years of using MS products I am now trying to get familiar with Linux. I've installed it on a notebook which previously ran a W10 (with working touchpad, wlan, and sounds). The hardware is listed here: https://linux-hardware.org/?probe=9e28b4c911 Ubuntu didn't recognise the WLan radio, I manually installed the driver, it runs now. I've tried to find out why can't the touchpad be recognised, without any results until now. The sounds are not working on the built-in speakers, but it goes through a Bluetooth device. Thanks you and best regards, Balazs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 21:17:16 2021 InstallationDate: Installed on 2021-12-14 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1955075 Title: Touchpad not found at all Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Dear Ubuntu Pros, after 33 years of using MS products I am now trying to get familiar with Linux. I've installed it on a notebook which previously ran a W10 (with working touchpad, wlan, and sounds). The hardware is listed here: https://linux-hardware.org/?probe=9e28b4c911 Ubuntu didn't recognise the WLan radio, I manually installed the driver, it runs now. I've tried to find out why can't the touchpad be recognised, without any results until now. The sounds are not working on the built-in speakers, but it goes through a Bluetooth device. Thanks you and best regards, Balazs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 21:17:16 2021 InstallationDate: Installed on 2021-12-14 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1955075/+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 1954300] Re: mt7921e: Failed to start WM firmware
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1022.26
---
linux-oem-5.13 (5.13.0-1022.26) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1022.26 -proposed tracker (LP:
#1954685)
* Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
* mt7921e: Failed to start WM firmware (LP: #1954300)
- SAUCE: Bluetooth: btusb: Handle download_firmware failure cases
- SAUCE: Bluetooth: btusb: Return error code when getting patch status
failed
* s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
(LP: #1954633)
- platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops
-- Timo Aaltonen Tue, 14 Dec 2021
08:19:59 +0200
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+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 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1022.26
---
linux-oem-5.13 (5.13.0-1022.26) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1022.26 -proposed tracker (LP:
#1954685)
* Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
* mt7921e: Failed to start WM firmware (LP: #1954300)
- SAUCE: Bluetooth: btusb: Handle download_firmware failure cases
- SAUCE: Bluetooth: btusb: Return error code when getting patch status
failed
* s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
(LP: #1954633)
- platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops
-- Timo Aaltonen Tue, 14 Dec 2021
08:19:59 +0200
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+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 1955070] [NEW] Impish update: upstream stable patchset 2021-12-16
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-12-16 Ported from the following upstream stable releases: v5.10.81, v5.14.21, v5.15.4 from git://git.kernel.org/ Note: upstream stable v5.14 has now reached EOL, as of v5.14.21. fortify: Explicitly disable Clang support block: Add a helper to validate the block size loop: Use blk_validate_block_size() to validate block size bootconfig: init: Fix memblock leak in xbc_make_cmdline() net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings parisc/entry: fix trace test in syscall exit path PCI/MSI: Destroy sysfs before freeing entries PCI/MSI: Deal with devices lying about their MSI mask capability PCI: Add MSI masking quirk for Nvidia ION AHCI erofs: remove the occupied parameter from z_erofs_pagevec_enqueue() erofs: fix unsafe pagevec reuse of hooked pclusters perf/core: Avoid put_page() when GUP fails thermal: Fix NULL pointer dereferences in of_thermal_ functions selftests/x86/iopl: Adjust to the faked iopl CLI/STI usage KVM: Fix steal time asm constraints Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. Bluetooth: btusb: Add support for TP-Link UB500 Adapter string: uninline memcpy_and_pad btrfs: introduce btrfs_is_data_reloc_root btrfs: zoned: add a dedicated data relocation block group btrfs: zoned: only allow one process to add pages to a relocation inode btrfs: zoned: use regular writes for relocation btrfs: check for relocation inodes on zoned btrfs in should_nocow btrfs: zoned: allow preallocation for relocation inodes UBUNTU: upstream stable to v5.10.81, v5.14.21, v5.15.4 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - 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: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-12-16 -upstream stable patchset 2021-12-16 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.81, v5.14.21, v5.15.4 + + from git://git.kernel.org/ + +Note: upstream stable v5.14 has now reached EOL, as of v5.14.21. + + fortify: Explicitly disable Clang support + block: Add a helper to validate the block size + loop: Use blk_validate_block_size() to validate block size + bootconfig: init: Fix memblock leak in xbc_make_cmdline() + net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings + parisc/entry: fix trace test in syscall exit path + PCI/MSI: Destroy sysfs before freeing entries + PCI/MSI: Deal with devices lying about their MSI mask capability + PCI: Add MSI masking quirk for Nvidia ION AHCI + erofs: remove the occupied parameter from z_erofs_pagevec_enqueue() + erofs: fix unsafe pagevec reuse of hooked pclusters + perf/core: Avoid put_page() when GUP fails + thermal: Fix NULL pointer dereferences in of_thermal_ functions + selftests/x86/iopl: Adjust to the faked iopl CLI/STI usage + KVM: Fix steal time asm
[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+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 1955066] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955066 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: I recently updated from Ubuntu 18.04 to Ubuntu 20.04. During the process I had a blank screen but solves the issue. However on starting the system, it did not detect the touchpad. I had my mouse connected to the laptop in the process which I think must have affected the process as it only recognizes my mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rosy 2981 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 19:44:05 2021 InstallationDate: Installed on 2021-10-08 (69 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 008: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81F4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e4124910-eddf-4ef6-b72d-9552b1931219 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.173.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7SCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76440 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7SCN27WW:bd11/28/2018:svnLENOVO:pn81F4:pvrLenovoideapad330S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0T76440WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-14IKB: dmi.product.family: ideapad 330S-14IKB dmi.product.name: 81F4 dmi.product.sku: LENOVO_MT_81F4_BU_idea_FM_ideapad 330S-14IKB dmi.product.version: Lenovo ideapad 330S-14IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955066/+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 1897764] Re: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM
Observed also on 2021.11.29/focal/linux-gcp/5.4.0-1059.63 on f1-micro and g1-small instances -- 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/1897764 Title: mem-on-off-test.sh from memory-hotplug in ubuntu_kernel_selftests failed on X-gcp-4.15 / F-5.4 zVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Groovy: Invalid Bug description: Issue found on Focal 5.4.0-49.53 zVM kernel04 Test failed with: # selftests: memory-hotplug: mem-on-off-test.sh # Test scope: 2% hotplug memory # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # offline 2% hot-pluggable memory in online state # trying to offline 1 out of 16 memory block(s): # online->offline memory0 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 0: unexpected fail # online->offline memory1 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 1: unexpected fail # online->offline memory10 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 10: unexpected fail # online->offline memory11 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 11: unexpected fail # online->offline memory12 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 12: unexpected fail # online->offline memory13 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 13: unexpected fail # online->offline memory14 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 14: unexpected fail # online->offline memory15 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 15: unexpected fail # online->offline memory2 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 2: unexpected fail # online->offline memory3 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 3: unexpected fail # online->offline memory4 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 4: unexpected fail # online->offline memory5 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 5: unexpected fail # online->offline memory6 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 6: unexpected fail # online->offline memory7 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 7: unexpected fail # online->offline memory8 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 8: unexpected fail # online->offline memory9 # ./mem-on-off-test.sh: line 78: echo: write error: Device or resource busy # offline_memory_expect_success 9: unexpected fail # FAILED - unable to offline some memory blocks, device busy? # online all hot-pluggable memory in offline state: # SKIPPED - no hot-pluggable memory in offline state # Test with memory notifier error injection not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # exit=1 This issue can be found on 5.4.0-46.50, 5.4.0-45.49 zVM as well. Passed with 5.4.0-44.48 Passed with 5.4.0-43.47 Failed with 5.4.0-42.46 Looks like it's not very stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1897764/+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 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 / F-GKE 5.4
Observed also on 2021.11.29/focal/linux-gcp/5.4.0-1059.63 -- 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/1851619 Title: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 / F-GKE 5.4 Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: The test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp) # selftests: net: test_blackhole_dev.sh # test_blackhole_dev: [FAIL] not ok 13 selftests: net: test_blackhole_dev.sh Need to run this manually to see what's going on there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851619/+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 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels
Observed also on 2021.11.29/focal/linux-gcp/5.4.0-1059.63 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on cloud kernels Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-gke package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle package in Ubuntu: New Bug description: This test will attempt to insert the test_bpf module, but this module does not exist in KVM kernels: $ sudo modprobe test_bpf modprobe: FATAL: Module test_bpf not found in directory /lib/modules/4.15.0-1028-kvm The script: $ sudo ./test_bpf.sh test_bpf: [FAIL] $ cat test_bpf.sh #!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Runs bpf test using test_bpf kernel module if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi This test_bpf module will need the CONFIG_TEST_BPF to be enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 08:29:29 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+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 1955066] [NEW] Touchpad not working
Public bug reported: I recently updated from Ubuntu 18.04 to Ubuntu 20.04. During the process I had a blank screen but solves the issue. However on starting the system, it did not detect the touchpad. I had my mouse connected to the laptop in the process which I think must have affected the process as it only recognizes my mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rosy 2981 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 19:44:05 2021 InstallationDate: Installed on 2021-10-08 (69 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 008: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81F4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e4124910-eddf-4ef6-b72d-9552b1931219 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.173.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7SCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76440 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7SCN27WW:bd11/28/2018:svnLENOVO:pn81F4:pvrLenovoideapad330S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0T76440WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-14IKB: dmi.product.family: ideapad 330S-14IKB dmi.product.name: 81F4 dmi.product.sku: LENOVO_MT_81F4_BU_idea_FM_ideapad 330S-14IKB dmi.product.version: Lenovo ideapad 330S-14IKB dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1955066 Title: Touchpad not working Status in linux package in Ubuntu: New Bug description: I recently updated from Ubuntu 18.04 to Ubuntu 20.04. During the process I had a blank screen but solves the issue. However on starting the system, it did not detect the touchpad. I had my mouse connected to the laptop in the process which I think must have affected the process as it only recognizes my mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rosy 2981 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 19:44:05 2021 InstallationDate: Installed on 2021-10-08 (69 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b61e Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 008: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81F4 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e4124910-eddf-4ef6-b72d-9552b1931219 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.173.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7SCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76440 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr7SCN27WW:bd11/28/2018:svnLENOVO:pn81F4:pvrLenovoideapad330S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0T76440WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-14IKB: dmi.product.family: ideapad 330S-14IKB dmi.product.name: 81F4 dmi.product.sku:
[Kernel-packages] [Bug 1954369] Re: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1954369 Title: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] xHCI driver's runtime resume routine tries to reset USB controller with XHCI_RESET_ON_RESUME flag. That causes USB devices connect to the xHCI fail to work. [Fix] Disable runtime power management regardless of CONFIG_USB_DEFAULT_PERSIST option. [Test] USB devices which connect to the xHCI controller can work normally. [Where problems could occur] USB_DEFAULT_PERSIST is a config for system-wide PM to speed up resume time, so it shouldn't be applied to runtime PM at first place. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954369/+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 1953249] Please test proposed package
Hello Ivo, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.24 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Committed Bug description: [ Impact ] AMD GPU not functional on Focal with HWE kernel. [ Test Case ] See original description below. [ Fix ] Cherry-pick relevant commit from upstream linux-firmware. [ Where Problems Could Occur ] Broken graphics with AMD GPUs. [ Original Description ] Release: up-to-date Focal LTS (20.04.3) Package-version: linux-firmware 1.187.20 Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M] With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly), my laptop's discrete graphics stopped working. Looking at the logs, I found these messages: -- snippet -- kernel: [1.492908] [drm] amdgpu: dpm initialized kernel: [1.492932] [drm] AMDGPU Display Connectors kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for amdgpu/verde_uvd.bin failed with error -2 kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load firmware "amdgpu/verde_uvd.bin" kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing. Running '$ dpkg -L linux-firmware | sort' gives this: -- snippet -- /lib/firmware/amdgpu/vegam_uvd.bin /lib/firmware/amdgpu/vegam_vce.bin /lib/firmware/amdgpu/verde_ce.bin /lib/firmware/amdgpu/verde_k_smc.bin /lib/firmware/amdgpu/verde_mc.bin /lib/firmware/amdgpu/verde_me.bin /lib/firmware/amdgpu/verde_pfp.bin /lib/firmware/amdgpu/verde_rlc.bin /lib/firmware/amdgpu/verde_smc.bin /lib/firmware/amdgpu/yellow_carp_asd.bin /lib/firmware/amdgpu/yellow_carp_ce.bin -- snippet -- Copying the file from upstream (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system, probably because I use UEFI and the module wasn't signed (error below): -- snippet -- kernel: [ 502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't validate firmware "amdgpu/verde_uvd.bin" kernel: [ 502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -22 kernel: [ 502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [ 502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [ 502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- I can confirm that reverting kernel driver to 'radeonsi' makes the device usable again, but at the expense of Vulkan APIs (not supported by this driver). Could you, please, fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249/+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 1954300] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.24 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
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/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1917709] Re: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error
I'm having this issue when launching a game using steam proton. When launching the Stationeers game it wants to read from dvd-rw drive and once every 3-4 launches the game will also freeze the whole system. I'm guessing this is the reason for the freeze since this would be the last error in logs. Ubuntu 21.10, kernel 5.14.21-051421-generic, amdgpu and -force-opengl in launch options. dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 0, async page read dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 1, async page read dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 2, async page read dec 16 05:12:11 H-Linux kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 dec 16 05:12:11 H-Linux kernel: Buffer I/O error on dev sr0, logical block 3, async page read -- 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/1917709 Title: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error Status in linux package in Ubuntu: Fix Released Bug description: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron:
[Kernel-packages] [Bug 1917709] Re: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917709 Title: Ubuntu tries to read blu-ray when boot from ssd and gives I/O error Status in linux package in Ubuntu: Fix Released Bug description: kernel: sd 14:0:0:0: [sdd] No Caching mode page found kernel: sd 14:0:0:0: [sdd] Assuming drive cache: write through kernel: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295100, async page read kernel: Buffer I/O error on dev sr0, logical block 2295101, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179392 op 0x0:(READ) flags 0x80700 phys_seg 17 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179904 op 0x0:(READ) flags 0x80700 phys_seg 13 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9180096 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295024, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180100 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295025, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295098, async page read kernel: Buffer I/O error on dev sr0, logical block 2295099, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180376 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295094, async page read kernel: Buffer I/O error on dev sr0, logical block 2295095, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179648 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 kernel: blk_update_request: I/O error, dev sr0, sector 9179776 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294944, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9179780 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2294945, async page read kernel: blk_update_request: I/O error, dev sr0, sector 9180368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 2295092, async page read kernel: Buffer I/O error on dev sr0, logical block 2295093, async page read systemd[1]: Failed unmounting /cdrom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.10.0-14-generic 5.10.0-14.15 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC0: ubuntu-mate 5498 F pulseaudio /dev/snd/controlC1: ubuntu-mate 5498 F pulseaudio CasperMD5CheckResult: unknown CasperVersion: 1.458 Date: Thu Mar 4 06:07:11 2021 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hipp" - Alpha amd64 (20210304) MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.195 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to:
[Kernel-packages] [Bug 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+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 1949770] Re: Enable arm64 for Hyper-V guests
** Changed in: linux-azure (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux-meta-azure (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux-signed-azure (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-signed-azure package in Ubuntu: New Status in linux-azure source package in Hirsute: Fix Committed Status in linux-meta-azure source package in Hirsute: Fix Committed Status in linux-signed-azure source package in Hirsute: Fix Committed Status in linux-azure source package in Impish: New Status in linux-meta-azure source package in Impish: New Status in linux-signed-azure source package in Impish: New Status in linux-azure source package in Jammy: New Status in linux-meta-azure source package in Jammy: New Status in linux-signed-azure source package in Jammy: New Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. [Other info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+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 1954300] Re: mt7921e: Failed to start WM firmware
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11
---
linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker
(LP: #1954691)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
* s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
(LP: #1954633)
- platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops
* Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540)
- ACPI: Add stubs for wakeup handler functions
- pinctrl: amd: Fix wakeups when IRQ is shared with SCI
* alsa/hda: the microphone can't be detected on a couple of lenovo machines
(LP: #1954612)
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
* mt7921e: Failed to start WM firmware (LP: #1954300)
- SAUCE: Bluetooth: btusb: Handle download_firmware failure cases
- SAUCE: Bluetooth: btusb: Return error code when getting patch status
failed
* Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
(LP: #1954617)
- ACPI: CPPC: Introduce cppc_get_nominal_perf()
- ACPI: CPPC: Add NULL pointer check to cppc_get_perf()
- cpufreq: intel_pstate: hybrid: Rework HWP calibration
* Add support for NVIDIA EC backlight (LP: #1953286)
- platform/x86: Add driver for ACPI WMAA EC-based backlight control
- platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c
- platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight
- [Config] NVIDIA_WMI_EC_BACKLIGHT=m
* Let VMD follow host bridge PCIe settings (LP: #1954611)
- SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features
-- Timo Aaltonen Mon, 13 Dec 2021
19:41:56 +0200
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
[Kernel-packages] [Bug 1954612] Re: alsa/hda: the microphone can't be detected on a couple of lenovo machines
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11 --- linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker (LP: #1954691) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out (LP: #1954633) - platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops * Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540) - ACPI: Add stubs for wakeup handler functions - pinctrl: amd: Fix wakeups when IRQ is shared with SCI * alsa/hda: the microphone can't be detected on a couple of lenovo machines (LP: #1954612) - ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform * mt7921e: Failed to start WM firmware (LP: #1954300) - SAUCE: Bluetooth: btusb: Handle download_firmware failure cases - SAUCE: Bluetooth: btusb: Return error code when getting patch status failed * Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) (LP: #1954617) - ACPI: CPPC: Introduce cppc_get_nominal_perf() - ACPI: CPPC: Add NULL pointer check to cppc_get_perf() - cpufreq: intel_pstate: hybrid: Rework HWP calibration * Add support for NVIDIA EC backlight (LP: #1953286) - platform/x86: Add driver for ACPI WMAA EC-based backlight control - platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c - platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight - [Config] NVIDIA_WMI_EC_BACKLIGHT=m * Let VMD follow host bridge PCIe settings (LP: #1954611) - SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features -- Timo Aaltonen Mon, 13 Dec 2021 19:41:56 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954612 Title: alsa/hda: the microphone can't be detected on a couple of lenovo machines Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] We plug a microphone in the audio jack, but the driver can't detect the microphone and we try to record sound via this mic, can't record any sound. [Fix] Backport one patch from upstream. [Test] Booting the patched kernel, open the gnome-sound-setting, plug a microphone, we could see the system detect the microphone, and use this mic to record sound, the sound is recorded successfully. [Where problems could occur] The change only applies to the specific machines with those SSIDs, it will not introduce regression on other machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954612/+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 1954611] Re: Let VMD follow host bridge PCIe settings
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11 --- linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker (LP: #1954691) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out (LP: #1954633) - platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops * Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540) - ACPI: Add stubs for wakeup handler functions - pinctrl: amd: Fix wakeups when IRQ is shared with SCI * alsa/hda: the microphone can't be detected on a couple of lenovo machines (LP: #1954612) - ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform * mt7921e: Failed to start WM firmware (LP: #1954300) - SAUCE: Bluetooth: btusb: Handle download_firmware failure cases - SAUCE: Bluetooth: btusb: Return error code when getting patch status failed * Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) (LP: #1954617) - ACPI: CPPC: Introduce cppc_get_nominal_perf() - ACPI: CPPC: Add NULL pointer check to cppc_get_perf() - cpufreq: intel_pstate: hybrid: Rework HWP calibration * Add support for NVIDIA EC backlight (LP: #1953286) - platform/x86: Add driver for ACPI WMAA EC-based backlight control - platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c - platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight - [Config] NVIDIA_WMI_EC_BACKLIGHT=m * Let VMD follow host bridge PCIe settings (LP: #1954611) - SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features -- Timo Aaltonen Mon, 13 Dec 2021 19:41:56 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954611 Title: Let VMD follow host bridge PCIe settings Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Some platforms have endless AER message floods kernel log, slows done disk I/O. [Fix] Honor BIOS settings to disable AER for Intel VMD. [Test] Use dmesg to check kernel log, no more AER message since AER is disabled. [Where problem could occur] The patch copies PCIe settings from host bridge, so some PCIe features will be disabled as a result. This may not be desirable for some users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954611/+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 1953540] Re: Fix power button wakeup with shared IRQs on AMD platforms
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11 --- linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker (LP: #1954691) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out (LP: #1954633) - platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops * Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540) - ACPI: Add stubs for wakeup handler functions - pinctrl: amd: Fix wakeups when IRQ is shared with SCI * alsa/hda: the microphone can't be detected on a couple of lenovo machines (LP: #1954612) - ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform * mt7921e: Failed to start WM firmware (LP: #1954300) - SAUCE: Bluetooth: btusb: Handle download_firmware failure cases - SAUCE: Bluetooth: btusb: Return error code when getting patch status failed * Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) (LP: #1954617) - ACPI: CPPC: Introduce cppc_get_nominal_perf() - ACPI: CPPC: Add NULL pointer check to cppc_get_perf() - cpufreq: intel_pstate: hybrid: Rework HWP calibration * Add support for NVIDIA EC backlight (LP: #1953286) - platform/x86: Add driver for ACPI WMAA EC-based backlight control - platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c - platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight - [Config] NVIDIA_WMI_EC_BACKLIGHT=m * Let VMD follow host bridge PCIe settings (LP: #1954611) - SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features -- Timo Aaltonen Mon, 13 Dec 2021 19:41:56 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1953540 Title: Fix power button wakeup with shared IRQs on AMD platforms Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: In Progress Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] On some platform designs the the power button wakeup from s0i3 doesn't work even with the existing changes to IRQ handling for the GPIO controller. In these designs the ACPI SCI and GPIO controller share an IRQ. Due to the way the s2idle loop handles the IRQ for the ACPI SCI the GPIO controller driver doesn't get a chance to wake the system in this circumstance. [Fix] To fix this rework the existing IRQ handler function to function as a checker and an IRQ handler depending on the calling arguments. The patches were cherry-picked from 5.16rc3. [Test] This is requested by AMD. The test was done on two systems L15 AMD Gen2 and P14s AMD Gen2 and both can be waken up by power button presses. [Where problems could occur] Risk is low. This only affects AMD platforms with s0i3 enabled. Suspends/resumes are not affect. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953540/+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 1953286] Re: Add support for NVIDIA EC backlight
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11 --- linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker (LP: #1954691) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out (LP: #1954633) - platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops * Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540) - ACPI: Add stubs for wakeup handler functions - pinctrl: amd: Fix wakeups when IRQ is shared with SCI * alsa/hda: the microphone can't be detected on a couple of lenovo machines (LP: #1954612) - ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform * mt7921e: Failed to start WM firmware (LP: #1954300) - SAUCE: Bluetooth: btusb: Handle download_firmware failure cases - SAUCE: Bluetooth: btusb: Return error code when getting patch status failed * Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) (LP: #1954617) - ACPI: CPPC: Introduce cppc_get_nominal_perf() - ACPI: CPPC: Add NULL pointer check to cppc_get_perf() - cpufreq: intel_pstate: hybrid: Rework HWP calibration * Add support for NVIDIA EC backlight (LP: #1953286) - platform/x86: Add driver for ACPI WMAA EC-based backlight control - platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c - platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight - [Config] NVIDIA_WMI_EC_BACKLIGHT=m * Let VMD follow host bridge PCIe settings (LP: #1954611) - SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features -- Timo Aaltonen Mon, 13 Dec 2021 19:41:56 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1953286 Title: Add support for NVIDIA EC backlight Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] Some system equipped with NVIDIA GFX cannot change screen brightness. [Fix] Add new way to change brightness. [Test] After the fix is applied, there's a new backlight sysfs "nvidia_wmi_ec_backlight" can change the screen brightness. [Where problems could occur] The driver relies on BIOS to behave correctly. If the BIOS lies or has a bug, the new backlight interface will overtake other backlight interfaces. It's rather unlikely though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953286/+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 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11 --- linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker (LP: #1954691) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2021.11.08) * s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out (LP: #1954633) - platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops * Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540) - ACPI: Add stubs for wakeup handler functions - pinctrl: amd: Fix wakeups when IRQ is shared with SCI * alsa/hda: the microphone can't be detected on a couple of lenovo machines (LP: #1954612) - ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform * mt7921e: Failed to start WM firmware (LP: #1954300) - SAUCE: Bluetooth: btusb: Handle download_firmware failure cases - SAUCE: Bluetooth: btusb: Return error code when getting patch status failed * Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) (LP: #1954617) - ACPI: CPPC: Introduce cppc_get_nominal_perf() - ACPI: CPPC: Add NULL pointer check to cppc_get_perf() - cpufreq: intel_pstate: hybrid: Rework HWP calibration * Add support for NVIDIA EC backlight (LP: #1953286) - platform/x86: Add driver for ACPI WMAA EC-based backlight control - platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c - platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight - [Config] NVIDIA_WMI_EC_BACKLIGHT=m * Let VMD follow host bridge PCIe settings (LP: #1954611) - SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features -- Timo Aaltonen Mon, 13 Dec 2021 19:41:56 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] On ADL platform, I+N sku, get the cpufreq errors during boot-up, [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) The commit has been landed on mainline since v5.15-rc1. [Test Case] 1. boot-up the machine. 2. check dmesg if the cpufreq error is presented. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+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 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11
---
linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker
(LP: #1954691)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
* s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
(LP: #1954633)
- platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops
* Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540)
- ACPI: Add stubs for wakeup handler functions
- pinctrl: amd: Fix wakeups when IRQ is shared with SCI
* alsa/hda: the microphone can't be detected on a couple of lenovo machines
(LP: #1954612)
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
* mt7921e: Failed to start WM firmware (LP: #1954300)
- SAUCE: Bluetooth: btusb: Handle download_firmware failure cases
- SAUCE: Bluetooth: btusb: Return error code when getting patch status
failed
* Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
(LP: #1954617)
- ACPI: CPPC: Introduce cppc_get_nominal_perf()
- ACPI: CPPC: Add NULL pointer check to cppc_get_perf()
- cpufreq: intel_pstate: hybrid: Rework HWP calibration
* Add support for NVIDIA EC backlight (LP: #1953286)
- platform/x86: Add driver for ACPI WMAA EC-based backlight control
- platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c
- platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight
- [Config] NVIDIA_WMI_EC_BACKLIGHT=m
* Let VMD follow host bridge PCIe settings (LP: #1954611)
- SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features
-- Timo Aaltonen Mon, 13 Dec 2021
19:41:56 +0200
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+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 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal
** Description changed:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
- == 470 ==
+ == 470 (focal only) ==
+
+ nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
+ urgency=medium
+
+ * debian/{nvidia_supported|pm-aliases-gen}:
+ - Drop the following IDs in favour of the 495 series (LP: #1954818):
+ 1fbc, 249c, 249d, 24b6, 24b7, 24b8,
+ 25a0, 25b8.
+
+
+ == 495 (bionic, focal, hirsute, impish) ==
+
+ nvidia-graphics-drivers-495 (495.46-0ubuntu*)
+
+ * debian/additional_card_ids,
+ debian/additional_runtimepm_ids:
+ - Add the following IDs:
+ 1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8
+ * New upstream release (LP: #1954818):
+ - Added support for the GBM API. This adds the new symlink
+ nvidia-drm_gbm.so pointing to the file libnvidia-
+ allocator.so.VERSION to implement a GBM backend driver usable
+ with the GBM loader from the Mesa project version 21.2 and
+ above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
+ 15_nvidia_gbm.json, which implement EGL support for the GBM
+ platform (EGL_KHR_platform_gbm).
+ - Add indicator for Resizable BAR support on compatible systems.
+ - Fixed a bug that could cause the X server to crash when
+ starting a new server generation on PRIME configurations.
+ - Removed support for NvIFROpenGL. This functionality was
+ deprecated in the 470.xx driver release.
+ - Removed libnvidia-cbl.so from the driver package. This
+ functionality is now provided by other driver libraries.
+ - Changed the minimum required Linux kernel version from 2.6.32
+ to 3.10.
+ - Updated nvidia.ko to load even if no supported NVIDIA GPUs are
+ present when an NVIDIA NVSwitch device is detected in the
+ system. Previously, nvidia.ko would fail to load into the
+ kernel if no supported GPUs were present.
+ - Fixed a bug in the Vulkan driver where unused input attributes
+ to a vertex shader would corrupt the interpolation qualifiers
+ for the shader.
+ - Fixed a bug in the Vulkan driver where individual components of
+ barycentric inputs could not be read.
+ - Added support for the VK_KHR_present_id extension.
+ - Added support for the VK_KHR_present_wait extension.
+ - Added support for the
+ VK_KHR_shader_subgroup_uniform_control_flow extension.
+ - Fixed a bug where VK_NVX_binary_import was advertised as
+ supported on unsupported platforms. This caused calls to
+ vkCreateDevice to fail if applications attempted to enable
+ VK_NVX_binary_import on such platforms.
+ - Added a new command line option, "--no-peermem", to nvidia-
+ installer. Selecting this option prevents the installation of
+ the nvidia-peermem kernel module.
+ - Fixed a regression which prevented DisplayPort and HDMI 2.1
+ variable refresh rate (VRR) G-SYNC Compatible monitors from
+ functioning correctly in variable refresh rate mode, resulting
+ in issues such as flickering.
+ - Fixed a bug that can cause a kernel crash in SLI Mosaic
+ configurations.
+ - Added support for the EGL_NV_robustness_video_memory_purge
+ extension.
--
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/1954818
Title:
Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
and 470 in Focal
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-470 source package in Bionic:
Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
In Progress
Status in nvidia-graphics-drivers-495 source package in Focal:
In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
In Progress
Status in
[Kernel-packages] [Bug 1952621] Re: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24
Verified by Microsoft. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1952621 Title: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-5.4 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-5.4 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.4 source package in Focal: Invalid Bug description: SRU Justification [Impact] During large scale deployment testing, we found below call trace when provisioning Ubuntu 18.04 VM with size Standard_NV24. Engineer deployed instance 10 times and encountered once. It looks like a race condition when probe device, but finally all devices can be probed. [ 4.938162] sysfs: cannot create duplicate filename '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/47505500-0003--3130-444531334632/pci0003:00/0003:00:00.0/config' [ 4.944816] sr 5:0:0:0: [sr0] scsi3-mmc drive: 0x/0x tray [ 4.951818] CPU: 0 PID: 135 Comm: kworker/0:2 Not tainted 5.4.0-1061-azure #64~18.04.1-Ubuntu [ 4.951820] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 4.958943] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 4.955812] Workqueue: hv_pri_chan vmbus_add_channel_work [ 4.955812] Call Trace: [ 4.955812] dump_stack+0x57/0x6d [ 4.955812] sysfs_warn_dup+0x5b/0x70 [ 4.955812] sysfs_add_file_mode_ns+0x158/0x180 [ 4.955812] sysfs_create_bin_file+0x64/0x90 [ 4.955812] pci_create_sysfs_dev_files+0x72/0x270 [ 4.955812] pci_bus_add_device+0x30/0x80 [ 4.955812] pci_bus_add_devices+0x31/0x70 [ 4.955812] hv_pci_probe+0x48c/0x650 [ 4.955812] vmbus_probe+0x3e/0x90 [ 4.955812] really_probe+0xf5/0x440 [ 4.955812] driver_probe_device+0x11b/0x130 [ 4.955812] __device_attach_driver+0x7b/0xe0 [ 4.955812] ? driver_allows_async_probing+0x60/0x60 [ 4.955812] bus_for_each_drv+0x6e/0xb0 [ 4.955812] __device_attach+0xe4/0x160 [ 4.955812] device_initial_probe+0x13/0x20 [ 4.955812] bus_probe_device+0x92/0xa0 [ 4.955812] device_add+0x402/0x690 [ 4.955812] device_register+0x1a/0x20 [ 4.955812] vmbus_device_register+0x5e/0xf0 [ 4.955812] vmbus_add_channel_work+0x2c4/0x640 [ 4.955812] process_one_work+0x209/0x400 [ 4.955812] worker_thread+0x34/0x400 [ 4.955812] kthread+0x121/0x140 [ 4.955812] ? process_one_work+0x400/0x400 [ 4.955812] ? kthread_park+0x90/0x90 [ 4.955812] ret_from_fork+0x35/0x40 [ 5.043612] hv_pci 47505500-0004-0001-3130-444531334632: PCI VMBus probing: Using version 0x10002 [ 5.260563] hv_pci 47505500-0004-0001-3130-444531334632: PCI host bridge to bus 0004:00 Dexuan did some research and it looks like this is a longstanding race condition bug in the generic PCI subsystem (due to the timing, there can be more than 1 place where the PCI code tries to create the same ‘config’ sysfs file): https://patchwork.kernel.org/project/linux-pci/patch/20200716110423.xtfyb3n6tn5ixedh@pali/#23669641 The bug was reported on 7/16/2020, and the last reply was on 6/25/2021. It looks like this has not been fixed after 1+ year… Business Impact [Test Case] Repeated deployment on a Standard_NV24 instance. MS reported the reproduction rate is 3/551 before the patch, and 0/838 with the patch. [Where things could go wrong] Deployments could fail for other reasons. [Other info] SF: #00321027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952621/+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 1954956] Re: [amdgpu] System crash
Description:Ubuntu 21.04 Release:21.04 amended kernel info: 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954956 Title: [amdgpu] System crash Status in linux package in Ubuntu: Incomplete Bug description: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Dec 15 15:19:50 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954956/+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 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954930
Title:
AMD: Suspend not working when some cores are disabled through cpufreq
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
some cpu cores offline using cpufreq gadgets or via sysfs may hang the
system.
[Fix]
In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
dead in C3 state") fixes this issue.
[Test Case]
As stated in aforementioned bug url, setup cpufreq extention to take
down a few cpu cores, and trigger system suspend. There are ~50% chances
that networking/input/... would hang and the user can only reboot by
sysrq keys.
[Where problems could occur]
According to the patch discussion thread in
https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
not have a practical meaning, but simply C2 was the deepest supported
then.
[Other Info]
While this is currently only available in v5.16-rc1 and affects AMD
Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.
== original bug report ==
https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Reproduce steps:
1. Install cpufeq gnome extension
(https://extensions.gnome.org/extension/1082/cpufreq/)
2. Click on the cpu freq extention in the top bar
3. Slide the "cores online" from 16 to 3
4. close lid of laptop
Expected result: the laptop goes into suspend
Actual result: the laptop stay on but screen is now always black and keyboard
input is ignored
Fix committed to v5.16-rc1:
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1188 F pulseaudio
/dev/snd/controlC2: ubuntu 1188 F pulseaudio
/dev/snd/controlC0: ubuntu 1188 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-09 (97 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AMD Celadon-CZN
Package: linux-firmware 1.187.23+staging.38 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config
no_console_suspend
ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-9011-oem N/A
linux-backports-modules-5.14.0-9011-oem N/A
linux-firmware 1.187.23+staging.38
RfKill:
Tags: third-party-packages focal
Uname: Linux 5.14.0-9011-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 06/30/2021
dmi.bios.release: 19.1
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: RLD1005B_AB
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Celadon-CZN
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module
@sagigrim - CONFIG_NVME_TCP is already set in all of the kernel configs mentioned above. Have you installed linux-modules-extra-aws ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Status in linux-aws source package in Hirsute: Confirmed Status in linux-aws source package in Impish: Confirmed Status in linux-aws source package in Jammy: Confirmed Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+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 1955042] [NEW] SBI SRST extension is missing
Public bug reported: SBI SRST extension is needed for handling sifive unmatched reboot and with the reset now merged into openSBI package, enabling SRST extension finally gives us the possibility to reset the board. The patch to enable SRST extension can be found here: https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or use the attached patch. I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and it allows to successfully reboots the board. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Attachment added: "0001-RISC-V-Use-SBI-SRST-extension-when-available.patch" https://bugs.launchpad.net/bugs/1955042/+attachment/5548032/+files/0001-RISC-V-Use-SBI-SRST-extension-when-available.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1955042 Title: SBI SRST extension is missing Status in linux-riscv package in Ubuntu: New Bug description: SBI SRST extension is needed for handling sifive unmatched reboot and with the reset now merged into openSBI package, enabling SRST extension finally gives us the possibility to reset the board. The patch to enable SRST extension can be found here: https://lore.kernel.org/all/20210609121322.3058-2-anup.pa...@wdc.com/ or use the attached patch. I tested it on top of 5.13.0-1006.6+22.04.1 on the unmatched board and it allows to successfully reboots the board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1955042/+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 1954926] Re: Focal: CIFS stable updates
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux (Ubuntu) Status: New => Fix Released -- 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/1954926 Title: Focal: CIFS stable updates Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+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 1954926] Re: Focal: CIFS stable updates
** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-azure (Ubuntu) Assignee: Tim Gardner (timg-tpi) => (unassigned) -- 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/1954926 Title: Focal: CIFS stable updates Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1954926/+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 1954300] Re: mt7921e: Failed to start WM firmware
** Changed in: linux-firmware (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+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 1954300] Re: mt7921e: Failed to start WM firmware
** Changed in: linux-firmware (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+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 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing
** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1953249 Title: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Fix Committed Bug description: [ Impact ] AMD GPU not functional on Focal with HWE kernel. [ Test Case ] See original description below. [ Fix ] Cherry-pick relevant commit from upstream linux-firmware. [ Where Problems Could Occur ] Broken graphics with AMD GPUs. [ Original Description ] Release: up-to-date Focal LTS (20.04.3) Package-version: linux-firmware 1.187.20 Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M] With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly), my laptop's discrete graphics stopped working. Looking at the logs, I found these messages: -- snippet -- kernel: [1.492908] [drm] amdgpu: dpm initialized kernel: [1.492932] [drm] AMDGPU Display Connectors kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for amdgpu/verde_uvd.bin failed with error -2 kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load firmware "amdgpu/verde_uvd.bin" kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -2 kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing. Running '$ dpkg -L linux-firmware | sort' gives this: -- snippet -- /lib/firmware/amdgpu/vegam_uvd.bin /lib/firmware/amdgpu/vegam_vce.bin /lib/firmware/amdgpu/verde_ce.bin /lib/firmware/amdgpu/verde_k_smc.bin /lib/firmware/amdgpu/verde_mc.bin /lib/firmware/amdgpu/verde_me.bin /lib/firmware/amdgpu/verde_pfp.bin /lib/firmware/amdgpu/verde_rlc.bin /lib/firmware/amdgpu/verde_smc.bin /lib/firmware/amdgpu/yellow_carp_asd.bin /lib/firmware/amdgpu/yellow_carp_ce.bin -- snippet -- Copying the file from upstream (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system, probably because I use UEFI and the module wasn't signed (error below): -- snippet -- kernel: [ 502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't validate firmware "amdgpu/verde_uvd.bin" kernel: [ 502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init of IP block failed -22 kernel: [ 502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init failed kernel: [ 502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU init kernel: [ 502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device. -- snippet -- I can confirm that reverting kernel driver to 'radeonsi' makes the device usable again, but at the expense of Vulkan APIs (not supported by this driver). Could you, please, fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953249/+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 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
Trusty Azure 4.15 has this fix but still fails, so the verification fails. ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Trusty) Importance: Undecided Status: New -- 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/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in linux-azure source package in Trusty: New Status in linux-oem-5.10 source package in Trusty: New Status in linux-oem-5.13 source package in Trusty: New Status in linux-oem-5.14 source package in Trusty: New Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-azure source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-azure source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-azure source package in Jammy: New Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
Verified on: - 2021.11.29/bionic/linux-azure-fips/4.15.0-2041.45 - 2021.11.29/bionic/linux-azure-4.15/4.15.0-1129.142 ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed -- 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/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in linux-azure source package in Trusty: New Status in linux-oem-5.10 source package in Trusty: New Status in linux-oem-5.13 source package in Trusty: New Status in linux-oem-5.14 source package in Trusty: New Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-azure source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-azure source package in Impish: New Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-azure source package in Jammy: New Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+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 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-raspi (Ubuntu Impish) Status: Confirmed => Fix Committed ** Changed in: linux-raspi (Ubuntu Hirsute) Status: Confirmed => Fix Committed ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Fix Committed Status in linux-raspi2 source package in Bionic: Fix Committed Status in linux-raspi source package in Focal: Fix Committed Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-raspi source package in Impish: Fix Committed Bug description: [ Impact ] I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. [ Test Case ] $ sudo dmesg | grep -B1 -A1 'loop: module' [0.791122] cacheinfo: Unable to detect cache hierarchy for CPU 0 [4.903386] loop: module loaded [4.906092] spi-bcm2835 fe204000.spi: could not get clk: -517 [ Fix ] Set CONFIG_BLK_DEV_LOOP_MIN_COUNT to the default value (8). [ Where Problems Could Occur ] Loop devices need to be created on-demand if more than 8 are required. If that fails, user space will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+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 1954757] Re: Missing overlays/README
** Changed in: linux-raspi (Ubuntu Impish) Status: Triaged => Fix Committed ** Changed in: linux-raspi (Ubuntu Hirsute) Status: Triaged => Fix Committed ** Changed in: linux-raspi (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1954757 Title: Missing overlays/README Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: Fix Committed Status in linux-raspi source package in Hirsute: Fix Committed Status in linux-raspi source package in Impish: Fix Committed Bug description: [ Impact ] overlays/README is used by the 'dtoverlay' command to display info on available overlays and params. [ Test Case ] $ apt install libraspberrypi-bin $ dtoverlay -h uart0 * Help file not found With the README present: $ dtoverlay -h uart0 Name: uart0 Info: Change the pin usage of uart0 Usage: dtoverlay=uart0,= Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 - default 14) rxd0_pinGPIO pin for RXD0 (15, 33 or 37 - default 15) pin_funcAlternative pin function - 4(Alt0) for 14&15, 7(Alt3) for 32&33, 6(Alt2) for 36&37 [ Where Problems Could Occur ] The output of the `dtoverlay` could be wrong but it's only informational so should have no negative impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1954911] Re: Xorg freeze
Cool Thank you for the instructions. I will send you the results tomorrow. Thank you for your time. -Original Message- From: Daniel van Vugt <1954...@bugs.launchpad.net> To: mgerdes20...@aol.com Sent: Wed, Dec 15, 2021 7:57 pm Subject: [Bug 1954911] Re: Xorg freeze Thanks for the bug report. Please: 1. Reboot, plug in the monitor and reproduce the bug again; a failed boot or system freeze. 2. Wait 10 seconds while it is frozen. 3. Power off the machine. 4. Unplug the monitor. 5. Boot the machine normally. 6. Run this command: journalctl -b-1 > prevboot.txt 7. Attach the resulting text file here. ** Summary changed: - Xorg freeze + [i915] [penyrn] System freeze when HDMI is plugged in ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [i915] [penyrn] System freeze when HDMI is plugged in + [i915] [penryn] System freeze when HDMI is plugged in -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1954911 Title: [i915] [penryn] System freeze when HDMI is plugged in Status in linux package in Ubuntu: Confirmed Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954911/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954911 Title: [i915] [penryn] System freeze when HDMI is plugged in Status in linux package in Ubuntu: Confirmed Bug description: When I
[Kernel-packages] [Bug 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
This bug was fixed in the package linux-firmware - 1.187.23 --- linux-firmware (1.187.23) focal; urgency=medium * i915: Add HuC firwmare v7.5.0 for TGL (LP: #1939986) * i915: Add DG1 DMC v2.02 (LP: #1939986) * i915: Add GuC firmware v49.0.1 for all platforms (LP: #1939986) * amdgpu: update yellow carp dmcub firmware (LP: #1953008) * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - SAUCE: Remove missing firmwares from WHENCE - Fix ipu6 firmware license reference - [Packaging] Add check rule and call it in clean stage - [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Wed, 08 Dec 2021 08:11:55 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+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 1939986] Update Released
The verification of the Stable Release Update for linux-firmware 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Confirmed Status in linux-firmware source package in Focal: Fix Released Bug description: [ Impact ] The i915 driver in Focal HWE kernels (currently 5.11 and 5.13) needs new firmware blobs. Without them, some users reported display/audio issues when installing said kernel. [ Test Case ] 1) Install linux-generic-hwe-20.04 2) echo 'i915' >> /etc/initramfs-tools/modules 3) update-initramfs -u Which leads to multiple warnings: W: Possible missing firmware for module i915 [Fix ] Add missing firmware blobs from upstream linux-firmware. [ Where Problems Could Occur ] New closed-source firmware binaries, would could possibly go wrong? No display with i915, kernel crashes. [ Original Description ] Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin2021-06-29 firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1 Source: $ modprobe --show-depends --ignore-install i915 ... insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko $ modinfo -F firmware /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko ... i915/tgl_dmc_ver2_08.bin i915/tgl_guc_35.2.0.bin i915/tgl_huc_7.5.0.bin Actual result: $ sudo update-initramfs -u W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 Expected result: No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915 Info : INTEL Repository of firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.15 ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46 Uname: Linux 5.10.0-1038-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1699 F pulseaudio /dev/snd/pcmC0D0p: chris 1699 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 15 14:46:47 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54 InstallationDate: Installed on 2021-08-12 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.10.0-1038-oem N/A linux-backports-modules-5.10.0-1038-oem N/A linux-firmware 1.187.15 SourcePackage: linux-firmware
[Kernel-packages] [Bug 1953008] Update Released
The verification of the Stable Release Update for linux-firmware 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 linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1953008
Title:
Support USB4 DP alt mode for AMD Yellow Carp graphics card
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
USB4 DP alt mode not available on AMD yellow carp.
[Fix]
Several fixing commits from upstream, inclusive of one titled
"drm/amd/display: Fixup previous PSR policy commit" sauced commit to
fix backport problems for commit 9470620e99e9 ("drm/amd/display: Enable
PSR by default on newer DCN").
This also depends on the firmware updates.
[Test Case]
Plug an external monitor with USB Type-C input function to AMD RMB CRB
(which has yellow carp) usbc0 and usbc1.
[Where problems could occur]
The patches revealed multiple dmub firmware versions were skipped. This
might introduce incompatibilities between driver code and the firmware.
== linux-firmware SRU ==
[Impact]
Need new firmware to enable USB4 DP alt mode for AMD yellow carp.
[Fix]
Already-in-upstream commit 581f8a3aae02 ("amdgpu: update yellow carp
dmcub firmware") to be backported.
[Test Case]
Need also kernel driver fixes to verify.
[Where problems could occur]
This introduces new features required both kernel driver and firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Required linux-firmware:
* 581f8a3a amdgpu: update yellow carp dmcub firmware
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1304 F pulseaudio
/dev/snd/controlC0: ubuntu 1304 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X173
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-12-02 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
MachineType: AMD LilacKD-RMB
Package: linux-firmware
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1008-oem
root=UUID=82b889f1-11ce-4ecf-99e7-65c895cdc771 ro automatic-oem-config
ProcVersionSignature: Ubuntu 5.14.0-1008.8-oem 5.14.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-1008-oem N/A
linux-backports-modules-5.14.0-1008-oem N/A
linux-firmware 1.187.20+staging.35
RfKill:
Tags: third-party-packages focal
Uname: Linux 5.14.0-1008-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 190.196
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: RRL0080C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: LilacKD-RMB
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvrRRL0080C:bd09/15/2021:br190.196:svnAMD:pnLilacKD-RMB:pvr1:rvnAMD:rnLilacKD-RMB:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789:
dmi.product.family: Rembrandt
dmi.product.name: LilacKD-RMB
[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915
This bug was fixed in the package linux-firmware - 1.187.23 --- linux-firmware (1.187.23) focal; urgency=medium * i915: Add HuC firwmare v7.5.0 for TGL (LP: #1939986) * i915: Add DG1 DMC v2.02 (LP: #1939986) * i915: Add GuC firmware v49.0.1 for all platforms (LP: #1939986) * amdgpu: update yellow carp dmcub firmware (LP: #1953008) * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - SAUCE: Remove missing firmwares from WHENCE - Fix ipu6 firmware license reference - [Packaging] Add check rule and call it in clean stage - [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Wed, 08 Dec 2021 08:11:55 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1939986 Title: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Confirmed Status in linux-firmware source package in Focal: Fix Released Bug description: [ Impact ] The i915 driver in Focal HWE kernels (currently 5.11 and 5.13) needs new firmware blobs. Without them, some users reported display/audio issues when installing said kernel. [ Test Case ] 1) Install linux-generic-hwe-20.04 2) echo 'i915' >> /etc/initramfs-tools/modules 3) update-initramfs -u Which leads to multiple warnings: W: Possible missing firmware for module i915 [Fix ] Add missing firmware blobs from upstream linux-firmware. [ Where Problems Could Occur ] New closed-source firmware binaries, would could possibly go wrong? No display with i915, kernel crashes. [ Original Description ] Dear all, I can see that the linux-firmware is missing firmware files, in Ubuntu 20.04.1 LTS, for initramfs, when it loads i915. Package: linux-firmware 1.187.15 It contains the following files, for the module i915: i915/tgl_dmc_ver2_04.bin 2019-09-13 installed i915/tgl_dmc_ver2_06.bin 2020-03-04 installed i915/tgl_dmc_ver2_08.bin 2020-08-13 installed i915/tgl_guc_35.2.0.bin 2019-11-06 installed i915/tgl_huc_7.0.12.bin 2020-03-04 installed i915/tgl_huc_7.0.3.bin2019-11-06 installed Package: linux-firmware MUST at least contain the following files, for the module i915: i915/tgl_huc_7.5.0.bin2020-08-13 i915: Add HuC firwmare v7.5.0 for TGL as the module asks for it, during 'update-initramfs', to avoid: W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 But it COULD also contain : i915/tgl_dmc_ver2_12.bin 2021-07-28 i915: Add v2.12 DMC for TGL i915/tgl_guc_49.0.1.bin 2020-11-24 i915: Add GuC firmware v49.0.1 for all platforms i915/tgl_guc_62.0.0.bin 2021-06-29 firmware/i915/guc: Add GuC v62.0.0 for all platforms i915/tgl_huc_7.9.3.bin
[Kernel-packages] [Bug 1953008] Re: Support USB4 DP alt mode for AMD Yellow Carp graphics card
This bug was fixed in the package linux-firmware - 1.187.23
---
linux-firmware (1.187.23) focal; urgency=medium
* i915: Add HuC firwmare v7.5.0 for TGL (LP: #1939986)
* i915: Add DG1 DMC v2.02 (LP: #1939986)
* i915: Add GuC firmware v49.0.1 for all platforms (LP: #1939986)
* amdgpu: update yellow carp dmcub firmware (LP: #1953008)
* linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP:
#1952011)
* Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587)
- SAUCE: check_whence.py: Add python3 shebang
- SAUCE: check_whence.py: Also process WHENCE.ubuntu
- SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories
- SAUCE: check_whence.py: Ignore ea/ directory
- SAUCE: Remove obsolete bnx2x from WHENCE
- SAUCE: Remove obsolete tr_smctr from WHENCE
- SAUCE: Remove obsolete ti-connectivity from WHENCE
- SAUCE: Remove obsolete tda7706 from WHENCE
- SAUCE: Remove obsolete sxg from WHENCE
- SAUCE: Remove obsolete myricom from WHENCE
- SAUCE: Remove obsolete mwl8k from WHENCE
- SAUCE: Remove obsolete libertas from WHENCE
- SAUCE: Remove obsolete Computone from WHENCE
- SAUCE: Remove obsolete dabusb from WHENCE
- SAUCE: Remove obsolete cxgb from WHENCE
- SAUCE: Remove obsolete bnx2x from WHENCE
- SAUCE: Remove obsolete ar9170 from WHENCE
- SAUCE: Remove obsolete ar7010 from WHENCE
- SAUCE: Remove obsolete ath3k from WHENCE
- SAUCE: Remove obsolete 3com from WHENCE
- SAUCE: Remove obsolete ath6k from WHENCE
- SAUCE: Remove obsolete slicoss from WHENCE
- SAUCE: Remove obsolete ath9k from WHENCE
- SAUCE: Remove obsolete ar3k from WHENCE
- SAUCE: Remove obsolete bnx2x from WHENCE
- SAUCE: Remove obsolete files from WHENCE
- SAUCE: Remove obsolete cxgb3 from WHENCE
- SAUCE: Remove obsolete ueagle-atm from WHENCE
- Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu
- Rename LICENCE.dib0700 to LICENSE.dib0700
- Move Ubuntu check_firmware script to debian/scripts/
- Remove unnecessary symbolic links
- intel/sof: Remove symbolic links and add license to WHENCE.ubuntu
- SAUCE: Remove missing firmwares from WHENCE
- Fix ipu6 firmware license reference
- [Packaging] Add check rule and call it in clean stage
- [Packaging] close-release: Parse commit messages for Ignores and BugLinks
-- Juerg Haefliger Wed, 08 Dec 2021 08:11:55
+0100
** Changed in: linux-firmware (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1953008
Title:
Support USB4 DP alt mode for AMD Yellow Carp graphics card
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
USB4 DP alt mode not available on AMD yellow carp.
[Fix]
Several fixing commits from upstream, inclusive of one titled
"drm/amd/display: Fixup previous PSR policy commit" sauced commit to
fix backport problems for commit 9470620e99e9 ("drm/amd/display: Enable
PSR by default on newer DCN").
This also depends on the firmware updates.
[Test Case]
Plug an external monitor with USB Type-C input function to AMD RMB CRB
(which has yellow carp) usbc0 and usbc1.
[Where problems could occur]
The patches revealed multiple dmub firmware versions were skipped. This
might introduce incompatibilities between driver code and the firmware.
== linux-firmware SRU ==
[Impact]
Need new firmware to enable USB4 DP alt mode for AMD yellow carp.
[Fix]
Already-in-upstream commit 581f8a3aae02 ("amdgpu: update yellow carp
dmcub firmware") to be backported.
[Test Case]
Need also kernel driver fixes to verify.
[Where problems could occur]
This introduces new features required both kernel driver and firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Required linux-firmware:
* 581f8a3a amdgpu: update yellow carp dmcub firmware
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1304 F pulseaudio
/dev/snd/controlC0: ubuntu 1304 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
[Kernel-packages] [Bug 1953587] Re: Fix sanity checker and cleanup metadata
This bug was fixed in the package linux-firmware - 1.187.23 --- linux-firmware (1.187.23) focal; urgency=medium * i915: Add HuC firwmare v7.5.0 for TGL (LP: #1939986) * i915: Add DG1 DMC v2.02 (LP: #1939986) * i915: Add GuC firmware v49.0.1 for all platforms (LP: #1939986) * amdgpu: update yellow carp dmcub firmware (LP: #1953008) * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - SAUCE: Remove missing firmwares from WHENCE - Fix ipu6 firmware license reference - [Packaging] Add check rule and call it in clean stage - [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Wed, 08 Dec 2021 08:11:55 +0100 ** Changed in: linux-firmware (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+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 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
This bug was fixed in the package linux-firmware - 1.201.3 --- linux-firmware (1.201.3) impish; urgency=medium * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - [Packaging] Add check rule and call it in clean stage - [Packaging] Add WHENCE.ubuntu as README.ubuntu to the package - UBUNTU: [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Tue, 07 Dec 2021 09:40:38 +0100 -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+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 1952011] Re: [SRU] linux-firmware: add sof-firmware for adl platforms from sof-firmware-v1.9.2
This bug was fixed in the package linux-firmware - 1.197.5 --- linux-firmware (1.197.5) hirsute; urgency=medium * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - [Packaging] Add rebase-upstream helper script and debian rule - [Packaging] Add close-release helper script and debian rule - [Packaging] Add check rule and call it in clean stage - SAUCE: Remove missing firmwares from WHENCE - [Packaging] Add WHENCE.ubuntu as README.ubuntu to the package - [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Tue, 07 Dec 2021 13:26:28 +0100 ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Impish) Status: Fix Committed => Fix Released -- 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/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+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 1952011] Update Released
The verification of the Stable Release Update for linux-firmware 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1952011 Title: [SRU] linux-firmware: add sof-firmware for adl platforms from sof- firmware-v1.9.2 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: Because we plan to remove sof-firmware related files from linux-firmware of jammy and replace them with a debian package firmware-sof-signed, so this SRU is not applied to jammy. I will submit another SRU to firmware-sof-signed package later. [Impact] In the Dell oem project, we have many laptops which has sof dmic or sof soundwire audio design, they need to load firmware and topology files specific to ADL, otherwise the audio driver will fail to initialize and the whole audio can't work. [Fix] Integrate the firmware and topology files from sof-firmware-v1.9.2 [Test] Installed the patched linux-firmware and booting the patched kernel, the audio work well, all output and input devices work normally [Where problems could occur] This SRU introduces new firmware and topology files for adl, it has low possibility to introduce regression. If it could, it could possibilily affect the other machines which also need to load firmware and topology files, it could make the audio can't work on those machines, but this possibility is very low, we have tested the SRU on many laptops, no regression found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952011/+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 1953587] Re: Fix sanity checker and cleanup metadata
This bug was fixed in the package linux-firmware - 1.201.3 --- linux-firmware (1.201.3) impish; urgency=medium * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - [Packaging] Add check rule and call it in clean stage - [Packaging] Add WHENCE.ubuntu as README.ubuntu to the package - UBUNTU: [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Tue, 07 Dec 2021 09:40:38 +0100 -- 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/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+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 1953587] Update Released
The verification of the Stable Release Update for linux-firmware 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+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 1953587] Re: Fix sanity checker and cleanup metadata
This bug was fixed in the package linux-firmware - 1.197.5 --- linux-firmware (1.197.5) hirsute; urgency=medium * linux-firmware: add firmware for adl machines from sof-firmware-v1.9.2 (LP: #1952011) * Miscellaneous Ubuntu packaging changes and cleanups (LP: #1953587) - SAUCE: check_whence.py: Add python3 shebang - SAUCE: check_whence.py: Also process WHENCE.ubuntu - SAUCE: check_whence.py: Ignore debian/ and fw_source/ directories - SAUCE: check_whence.py: Ignore ea/ directory - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete tr_smctr from WHENCE - SAUCE: Remove obsolete ti-connectivity from WHENCE - SAUCE: Remove obsolete tda7706 from WHENCE - SAUCE: Remove obsolete sxg from WHENCE - SAUCE: Remove obsolete myricom from WHENCE - SAUCE: Remove obsolete mwl8k from WHENCE - SAUCE: Remove obsolete libertas from WHENCE - SAUCE: Remove obsolete Computone from WHENCE - SAUCE: Remove obsolete dabusb from WHENCE - SAUCE: Remove obsolete cxgb from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete ar9170 from WHENCE - SAUCE: Remove obsolete ar7010 from WHENCE - SAUCE: Remove obsolete ath3k from WHENCE - SAUCE: Remove obsolete 3com from WHENCE - SAUCE: Remove obsolete ath6k from WHENCE - SAUCE: Remove obsolete slicoss from WHENCE - SAUCE: Remove obsolete ath9k from WHENCE - SAUCE: Remove obsolete ar3k from WHENCE - SAUCE: Remove obsolete bnx2x from WHENCE - SAUCE: Remove obsolete files from WHENCE - SAUCE: Remove obsolete cxgb3 from WHENCE - SAUCE: Remove obsolete ueagle-atm from WHENCE - Add LICENCE.realtek-firmware.txt to WHENCE.ubuntu - Rename LICENCE.dib0700 to LICENSE.dib0700 - Move Ubuntu check_firmware script to debian/scripts/ - Remove unnecessary symbolic links - intel/sof: Remove symbolic links and add license to WHENCE.ubuntu - [Packaging] Add rebase-upstream helper script and debian rule - [Packaging] Add close-release helper script and debian rule - [Packaging] Add check rule and call it in clean stage - SAUCE: Remove missing firmwares from WHENCE - [Packaging] Add WHENCE.ubuntu as README.ubuntu to the package - [Packaging] close-release: Parse commit messages for Ignores and BugLinks -- Juerg Haefliger Tue, 07 Dec 2021 13:26:28 +0100 ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Impish) Status: Fix Committed => Fix Released -- 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/1953587 Title: Fix sanity checker and cleanup metadata Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Fix Released Status in linux-firmware source package in Impish: Fix Released Bug description: The repo contains a checker script check_whence.py that checks WHENCE data against present firmware files and flags missing files and missing WHENCE entries. It currently doesn't parse the downstream WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the checker. [ Impact ] None. These are packaging changes that are not visible to the end user. [ Where Problems Could Occur ] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1953587/+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 1907962] Re: The touchpad doesn't work and sometimes keyboard
The fix with the module i2c_hid does not work anymore on 21.10 with kernel 5.13.0-22-generic. -- 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/1907962 Title: The touchpad doesn't work and sometimes keyboard Status in linux package in Ubuntu: Expired Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Ubuntu 5.4.0-58.64-generic 5.4.73 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oleksandr 1379 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 13 14:13:00 2020 InstallationDate: Installed on 2020-12-11 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=be9b4d42-06a6-492c-a49c-b1f88b6c58c6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/23/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7410:pvr10601115935:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D4:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7410: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7410 dmi.product.sku: SK00 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907962/+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 1955016] [NEW] devices on thunderbolt dock are not recognized on adl-p platform
Public bug reported: [Impact] When booting up with the TBT dock is plugged, the devices(USB, Ethernet) on the dock can't be recognized. It requires to run lspci command to wake up the PCI devices to make the devices on the dock work. [Fix] The patchset fix this runtime pm issue. https://patchwork.kernel.org/project/linux-usb/cover/20211125073733.74902-1-mika.westerb...@linux.intel.com/ [Test] Verified on Dell ADL-P platform with TBT dock. [Where the problems could occur] Hard to evaluate, but after some cold boot/warm boot, plug/un-plug the devices on the dock, didn't observe any regressions. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1953036 somerville ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1953036 somerville ** Description changed: [Impact] When booting up with the TBT dock is plugged, the devices(USB, Ethernet) on the dock can't be recognized. It requires to run lspci command to wake up the PCI devices to make the devices on the dock work. [Fix] The patchset fix this runtime pm issue. https://patchwork.kernel.org/project/linux-usb/cover/20211125073733.74902-1-mika.westerb...@linux.intel.com/ [Test] Verified on Dell ADL-P platform with TBT dock. [Where the problems could occur] + Hard to evaluate, but after some cold boot/warm boot, plug/un-plug the devices on the dock, didn't observe any regressions. -- 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/1955016 Title: devices on thunderbolt dock are not recognized on adl-p platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] When booting up with the TBT dock is plugged, the devices(USB, Ethernet) on the dock can't be recognized. It requires to run lspci command to wake up the PCI devices to make the devices on the dock work. [Fix] The patchset fix this runtime pm issue. https://patchwork.kernel.org/project/linux-usb/cover/20211125073733.74902-1-mika.westerb...@linux.intel.com/ [Test] Verified on Dell ADL-P platform with TBT dock. [Where the problems could occur] Hard to evaluate, but after some cold boot/warm boot, plug/un-plug the devices on the dock, didn't observe any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955016/+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 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed -- 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/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. SRU justification: == [Impact] The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. [Fix] Ignore the buggy data reported by Elan TP firmware, make the TP usable. [Test] Tested on ThinkPad AMD X13 and users confirm on other platforms. [Where problems could occur] It's limited to specific Elan device, it may break the Elan Trackpoint. Jammy already got this commit in Ubuntu-5.15.0-12.12 Phoenix Huang (1): Input: elantench - fix misreporting trackpoint coordinates drivers/input/mouse/elantech.c | 13 + 1 file changed, 13 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+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 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
During i switched 2k to 4k multiple times, didn't get the error. after idle 2~3 hours and keep in 4k, i found the underrun error would be shown up. but 4k works well -- 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/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+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 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
Failed on T-aws-4.4 with: Running tests... tst_test.c:1313: TINFO: Timeout per run is 0h 05m 00s move_pages12.c:274: TINFO: Free RAM 525748832 kB move_pages12.c:292: TINFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:302: TINFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:218: TINFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:218: TINFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:208: TPASS: Bug not reproduced tst_test.c:1363: TBROK: Test killed by SIGBUS! move_pages12.c:142: TFAIL: move_pages failed: ESRCH (3) On: i3.metal|i3en.24xlarge|r5.metal -- 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/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Status in linux-azure source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+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 1954757] Re: Missing overlays/README
** Changed in: linux-raspi (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Triaged ** Changed in: linux-raspi (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => Triaged ** Changed in: linux-raspi (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1954757 Title: Missing overlays/README Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: Triaged Status in linux-raspi source package in Hirsute: Triaged Status in linux-raspi source package in Impish: Triaged Bug description: [ Impact ] overlays/README is used by the 'dtoverlay' command to display info on available overlays and params. [ Test Case ] $ apt install libraspberrypi-bin $ dtoverlay -h uart0 * Help file not found With the README present: $ dtoverlay -h uart0 Name: uart0 Info: Change the pin usage of uart0 Usage: dtoverlay=uart0,= Params: txd0_pinGPIO pin for TXD0 (14, 32 or 36 - default 14) rxd0_pinGPIO pin for RXD0 (15, 33 or 37 - default 15) pin_funcAlternative pin function - 4(Alt0) for 14&15, 7(Alt3) for 32&33, 6(Alt2) for 36&37 [ Where Problems Could Occur ] The output of the `dtoverlay` could be wrong but it's only informational so should have no negative impact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954757/+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 1953345] Re: memcg is disabled in v5.15 RT kernel (known issue)
** Tags added: 5.15 jammy realtime -- 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/1953345 Title: memcg is disabled in v5.15 RT kernel (known issue) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: From v5.15.2-rt20 announcement: Known issues: - The "Memory controller" (CONFIG_MEMCG) has been disabled. This might be the cause of ubuntu_ltp_controllers failure - ubuntu_ltp_controllers.pids_1_100: ## COMMAND: /opt/ltp/bin/ltp-pan -q -e -S -a 466487 -n 466487 -f /tmp/ltp-DbBcUelSWj/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... pids 1 TINFO: timeout per run is 0h 5m 0s mount: /dev/cgroup: none already mounted on /sys/fs/bpf. pids 1 TBROK: mount -t cgroup -o pids none /dev/cgroup failed pids 1 TINFO: removing created directories rmdir: failed to remove '/dev/cgroup/ltp_pids_1': No such file or directory pids 1 TINFO: Umounting pids umount: /dev/cgroup: not mounted. pids 1 TINFO: AppArmor enabled, this may affect test results pids 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) pids 1 TINFO: loaded AppArmor profiles: none ## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1953345/+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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
boot-repair-disk-32bit updated, based on 18.04.5 instead of 17.10. ** Changed in: boot-repair Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Boot-Repair: Fix Released Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Warning: 32bit iso on sourceforge for boot-repair-disk still contains unpatched Kernel. This is especially dangerous if boot-repair fails to repair the system to a bootable state, as there will be no way of applying the Fix detailed below. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la Fujitsu Q584 (unable to fix due to non booting OS on the tablet) --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16,
[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support - WIFI 6
** Tags added: kern-1746 -- 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/1954938 Title: Include the QCA WCN 6856 v2.1 support - WIFI 6 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+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 1951924] Re: linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure
** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Bionic) Assignee: (unassigned) => Bartlomiej Zolnierkiewicz (bzolnier) ** Changed in: linux-azure (Ubuntu) Status: Confirmed => Invalid -- 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/1951924 Title: linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: In Progress Bug description: To reproduce: * start a bionic VM in azure: az vm create --name bionic --resource-group test-bionic --image "Canonical:UbuntuServer:18_04-lts-gen2:latest" --size Standard_M416s_v2 --admin-username ubuntu --ssh-key-value SSH_KEY_PATH * "downgrade" the kernel to 4.15 and delete the 5.4 kernel * reboot (the machine should fail to boot) The serial console logs can be found on the azure portal (boot diagnostic needs to be enabled for the VM first). Logs: https://pastebin.ubuntu.com/p/mhKMdMJCtX/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1951924/+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 1950974] Re: Improve USB Type-C support
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950974 Title: Improve USB Type-C support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950974/+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
