[Kernel-packages] [Bug 1962356] [NEW] touchpad not detected lenovo-y9000k
Public bug reported: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=048d Product=c968 Version=0110 N: Name="ITE Tech. Inc. ITE Device(8258) Keyboard" P: Phys=usb-:00:14.0-9/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0/0003:048D:C968.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=048d Product=c968 Version=0110 N: Name="ITE Tech. Inc. ITE Device(8258) Consumer Control" P: Phys=usb-:00:14.0-9/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0/0003:048D:C968.0001/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=1f B: KEY=302ff 0 0 48317aff32d bfd6 1 130c730b17c000 267bfad9415fed 9e16804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0003 Vendor=048d Product=c968 Version=0110 N: Name="ITE Tech. Inc. ITE Device(8258) Wireless Radio Control" P: Phys=usb-:00:14.0-9/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0/0003:048D:C968.0001/input/input7 U: Uniq= H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=13 B: KEY=80 0 0 0 B: MSC=10 I: Bus=0003 Vendor=048d Product=c968 Version=0110 N: Name="ITE Tech. Inc. ITE Device(8258) System Control" P: Phys=usb-:00:14.0-9/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-9/3-9:1.0/0003:048D:C968.0001/input/input8 U: Uniq= H: Handlers=kbd event8 B: PROP=0 B: EV=13 B: KEY=c000 10 0 B: MSC=10 I: Bus=0003 Vendor=24ae Product=1813 Version=0101 N: Name="RAPOO Rapoo 2.4G Wireless Device" P: Phys=usb-:00:14.0-10/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:24AE:1813.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event9 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=24ae Product=1813 Version=0101 N: Name="RAPOO Rapoo 2.4G Wireless Device Mouse" P: Phys=usb-:00:14.0-10/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.1/0003:24AE:1813.0003/input/input10 U: Uniq= H: Handlers=mouse0 event10 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1943 B: MSC=10 I: Bus=0003 Vendor=24ae Product=1813 Version=0101 N: Name="RAPOO Rapoo 2.4G Wireless Device Consumer Control" P: Phys=usb-:00:14.0-10/input1 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.1/0003:24AE:1813.0003/input/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=1f B: KEY=3f000303ff 0 0 48317aff32d bfd6 1 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1040 B: ABS=1 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input13 U: Uniq= H: Handlers=rfkill kbd event12 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b67d Version=0407 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-6/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.0/input/input14 U: Uniq= H: Handlers=kbd event13 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA NVidia HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor=
[Kernel-packages] [Bug 1957986] Re: Recalled NFSv4 files delegations overwhelm server
= focal verification = ubuntu@client:~$ cat /proc/version_signature Ubuntu 5.4.0-102.115-generic 5.4.174 ubuntu@client:~$ ./elbencho/bin/elbencho -t 40 -r -n 10 -N 5000 -s 128k -b 128k /mnt/nfs/ubuntu OPERATION RESULT TYPEFIRST DONE LAST DONE = == = READ Elapsed ms : 470642 471169 Files/s : 4245 4244 Throughput MiB/s :530530 Total files :1998154200 Total MiB: 249770 25 --- ubuntu@client:~$ Regression: ubuntu@client:~/nfstest$ PYTHONPATH=$(pwd) ./test/nfstest_delegation --client 192.168.42.1 --server 192.168.42.2 -e /srv/nfstest --trcdelay 4 UID is: 1000 Creating: /mnt/t/nfstest_delegation_20220225_223841_f_001 UID is: 1000 Creating: /mnt/t/nfstest_delegation_20220225_223841_f_002 *** Basic READ delegation test TEST: Running test 'basic01' PASS: Open file for READ should succeed PASS: Read file should succeed PASS: Open file for READ on same process should succeed PASS: Read file on same process should succeed PASS: Open file for READ from a different process should succeed PASS: Read file from a different process should succeed FAIL: OPEN should be sent PASS: OPEN should be sent with CLAIM_NULL PASS: OPEN should be sent with the name of the file to be opened PASS: OPEN should be sent with the filehandle of the directory FAIL: READ delegation should be granted TIME: 5.113318s *** Basic WRITE delegation test TEST: Running test 'basic02' PASS: Open file for WRITE should succeed PASS: Write file should succeed PASS: Open file for READ on same process should succeed PASS: Read file on same process should succeed PASS: Open file for WRITE on same process should succeed PASS: Write file on same process should succeed PASS: Open file for READ from a different process should succeed PASS: Read file from a different process should succeed PASS: Open file for WRITE from a different process should succeed PASS: Write file from a different process should succeed FAIL: OPEN should be sent PASS: OPEN should be sent with CLAIM_NULL PASS: OPEN should be sent with the name of the file to be opened PASS: OPEN should be sent with the filehandle of the directory FAIL: WRITE delegation should be granted TIME: 4.940012s *** Basic READ delegation test with file stat TEST: Running test 'basic03' PASS: Stat file to cache file metadata should succeed PASS: Open file for READ should succeed PASS: Read file should succeed PASS: Open file for READ on same process should succeed PASS: Read file on same process should succeed PASS: Open file for READ from a different process should succeed PASS: Read file from a different process should succeed PASS: LOOKUP operation should be sent PASS: OPEN should be sent PASS: OPEN should be sent with CLAIM_FH PASS: OPEN should be sent with the filehandle of the file to be opened PASS: READ delegation should be granted PASS: OPEN should not be sent for the same file PASS: READs should be sent to the server with the DELEG stateid PASS: READs should return NFS4_OK from the server PASS: READ should not be sent when reading delegated file from a different process PASS: CLOSE should be sent to the server PASS: CLOSE should be sent with correct OPEN stateid PASS: DELEGRETURN should be sent after the close PASS: DELEGRETURN should be sent with the delegation stateid TIME: 4.757017s *** Basic WRITE delegation test with file stat TEST: Running test 'basic04' UID is: 1000 Creating: /mnt/t/nfstest_delegation_20220225_223841_f_004 PASS: Stat file to cache file metadata should succeed PASS: Open file for WRITE should succeed PASS: Write file should succeed PASS: Open file for READ on same process should succeed PASS: Read file on same process should succeed PASS: Open file for WRITE on same process should succeed PASS: Write file on same process should succeed PASS: Open file for READ from a different process should succeed PASS: Read file from a different process should succeed PASS: Open file for WRITE from a different process should succeed PASS: Write file from a different process should succeed PASS: LOOKUP operation should be sent FAIL: OPEN should be sent PASS: OPEN should be sent with CLAIM_FH FAIL: OPEN should be sent with the filehandle of the file to be opened FAIL: WRITE delegation should be granted TIME: 5.090116s *** Basic READ delegation test with file lock TEST: Running test 'basic05' PASS: Open file for READ should succeed PASS: Lock file with F_RDLCK should succeed PASS: Read file should succeed PASS: Open file for READ on same process should succeed PASS: Read file on same process should succeed
[Kernel-packages] [Bug 1941702] Re: nvidia-dkms-470 470.63.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- 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/1941702 Title: nvidia-dkms-470 470.63.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: Error! Bad return status for module build on kernel: 5.11.0-27-generic (x86_64) Consult /var/lib/dkms/nvidia/470.63.01/build/make.log for more information. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-470 470.63.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Thu Aug 26 14:30:49 2021 InstallationDate: Installed on 2021-03-20 (159 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 470.63.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: nvidia-dkms-470 470.63.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1941702/+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 1962345] [NEW] Focal update: v5.4.176 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.176 upstream stable release from git://git.kernel.org/ Bluetooth: refactor malicious adv data check s390/hypfs: include z/VM guests with access control group set scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices udf: Restore i_lenAlloc when inode expansion fails udf: Fix NULL ptr deref when converting from inline format PM: wakeup: simplify the output logic of pm_show_wakelocks() tracing/histogram: Fix a potential memory leak for kstrdup() tracing: Don't inc err_log entry count if entry allocation fails fsnotify: fix fsnotify hooks in pseudo filesystems drm/etnaviv: relax submit size limits arm64: errata: Fix exec handling in erratum 1418040 workaround netfilter: nft_payload: do not update layer 4 checksum when mangling fragments serial: 8250: of: Fix mapped region size when using reg-offset property serial: stm32: fix software flow control transfer tty: n_gsm: fix SW flow control encoding/handling tty: Add support for Brainboxes UC cards. usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge usb: common: ulpi: Fix crash in ulpi_match() usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS USB: core: Fix hang in usb_kill_urb by adding memory barriers usb: typec: tcpm: Do not disconnect while receiving VBUS off ucsi_ccg: Check DEV_INT bit only when starting CCG4 net: sfp: ignore disabled SFP node powerpc/32: Fix boot failure with GCC latent entropy plugin i40e: Increase delay to 1 s after global EMP reset i40e: Fix issue when maximum queues is exceeded i40e: Fix queues reservation for XDP i40e: fix unsigned stat widths rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() ipv6_tunnel: Rate limit warning messages net: fix information leakage in /proc/net/ptype hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649 hwmon: (lm90) Mark alert as broken for MAX6680 ping: fix the sk_bound_dev_if match in ping_lookup ipv4: avoid using shared IP generator for connected sockets hwmon: (lm90) Reduce maximum conversion rate for G781 NFSv4: Handle case where the lookup of a directory fails NFSv4: nfs_atomic_open() can race when looking up a non-regular file net-procfs: show net devices bound packet types drm/msm: Fix wrong size calculation drm/msm/dsi: Fix missing put_device() call in dsi_get_phy drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable ipv6: annotate accesses to fn->fn_sernum NFS: Ensure the server has an up to date ctime before hardlinking NFS: Ensure the server has an up to date ctime before renaming netfilter: conntrack: don't increment invalid counter on NF_REPEAT net: phy: broadcom: hook up soft_reset for BCM54616S phylib: fix potential use-after-free rxrpc: Adjust retransmission backoff hwmon: (lm90) Mark alert as broken for MAX6654 ibmvnic: init ->running_cap_crqs early ibmvnic: don't spin in tasklet drm/msm/hdmi: Fix missing put_device() call in msm_hdmi_get_phy yam: fix a memory leak in yam_siocdevprivate() net: hns3: handle empty unknown interrupt for VF ipv4: raw: lock the socket in raw_bind() ipv4: tcp: send zero IPID in SYNACK messages ipv4: remove sparse error in ip_neigh_gw4() dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config fsnotify: invalidate dcache before IN_DELETE event block: Fix wrong offset in bio_truncate() mtd: rawnand: mpc5121: Remove unused variable in ads5121_select_chip() Linux 5.4.176 UBUNTU: upstream stable to v5.4.176 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) 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 Focal) Importance: Undecided Status: New ** 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: -
[Kernel-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
This bug was fixed in the package marco - 1.26.0-1ubuntu0 --- marco (1.26.0-1ubuntu0) jammy; urgency=medium * debian/control: + Drop B-D: libxpresent-dev (LP: #1960621) -- Martin Wimpress Fri, 25 Feb 2022 11:21:33 + ** Changed in: marco (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Fix Released Status in metacity package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: In Progress Status in nvidia-graphics-drivers-510 source package in Focal: Confirmed Status in marco source package in Impish: In Progress Status in nvidia-graphics-drivers-510 source package in Impish: Confirmed Status in marco source package in Jammy: Fix Released Status in metacity source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1961121] Re: Not able to enter s2idle state on AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress 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 Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+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 1962010] Re: Cherrypick features and fixes from v5.17 for sifive dtbs
https://lists.ubuntu.com/archives/kernel-team/2022-February/128356.html ** Description changed: [Impact] - * Various features and bugs got fixed in sifive dtbs in v5.17 kernel + * Various features and bugs got fixed in sifive dtbs in v5.17 kernel - * Some versions of those features/bugs already exist in our kernels, + * Some versions of those features/bugs already exist in our kernels, and others are missing. - * Cherry-pick from upstream all new changes and fixes to bring our dtbs + * Cherry-pick from upstream all new changes and fixes to bring our dtbs in line with what's available in linus/master. - * After application of these series, the only remaining non-upstream + * After application of these series, the only remaining non-upstream dtb patches are: -- addition of PWM LEDs in unleashed and unmatched -- addition of Microsemi PCIe expansion board DT -- fu740 setting compatbile to "sifive,u74-mc" + - addition of PWM LEDs in unleashed and unmatched + - addition of Microsemi PCIe expansion board DT + - fu740 setting compatbile to "sifive,u74-mc" [Test Plan] - * Unleashed & Unmatched boot - * with full 16GB of RAM on unmatched - * without any other obvious hardware regressions w.r.t. LEDs and reboot support + * Unleashed & Unmatched boot + * with full 16GB of RAM on unmatched + * without any other obvious hardware regressions w.r.t. LEDs and poweroff support [Where problems could occur] - * the dtb updates appear to be compatible with existing v5.15 kernel + * the dtb updates appear to be compatible with existing v5.15 kernel and driver code appears to be unaffected. Future tweaks to dtbs may be required, but these changes bring everything on par with latest upstream, thus any future bugfixes should be easy to apply. -- 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/1962010 Title: Cherrypick features and fixes from v5.17 for sifive dtbs Status in linux-riscv package in Ubuntu: In Progress Bug description: [Impact] * Various features and bugs got fixed in sifive dtbs in v5.17 kernel * Some versions of those features/bugs already exist in our kernels, and others are missing. * Cherry-pick from upstream all new changes and fixes to bring our dtbs in line with what's available in linus/master. * After application of these series, the only remaining non-upstream dtb patches are: - addition of PWM LEDs in unleashed and unmatched - addition of Microsemi PCIe expansion board DT - fu740 setting compatbile to "sifive,u74-mc" [Test Plan] * Unleashed & Unmatched boot * with full 16GB of RAM on unmatched * without any other obvious hardware regressions w.r.t. LEDs and poweroff support [Where problems could occur] * the dtb updates appear to be compatible with existing v5.15 kernel and driver code appears to be unaffected. Future tweaks to dtbs may be required, but these changes bring everything on par with latest upstream, thus any future bugfixes should be easy to apply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1962010/+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 1952132] Re: [ADL] Thermal Support
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1952132 Title: [ADL] Thermal Support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable thermal supports. [Fix] Intel provides a list of patches to add new PCI driver which register a thermal zone and allows to get notification [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952132/+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 1952153] Re: [EHL][TGL][ADL] power management controller driver enabling
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1952153 Title: [EHL][TGL][ADL] power management controller driver enabling Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable power management controller supports. [Fix] The driver is the Kernel gateway to the PMC hardware for Intel processors and it provides debug hooks to developers and end-users to quickly figure out why their platform is not entering a deeper idle state such as S0ix. [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake / TigerLake / AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952153/+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 1952006] Re: [TGL][ADL] ACRN hypervisor support
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1952006 Title: [TGL][ADL] ACRN hypervisor support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The driver enables the host to run ACRN hypervisor which is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open-source platform. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable ACRN hypervisor [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel TigerLake/AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952006/+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 1952007] Re: [ADL] ITBM support for Hybrid platforms
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1952007 Title: [ADL] ITBM support for Hybrid platforms Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] Need ITBM support for Hybrid platforms. Need to change the scheduling order from Core, HT, ATOM to Core, ATOM, HT. When using ITBM on systems that has a mixture of CPUs supporting Hyper-Threading and others not supporting it (even offlining HT siblings may cause the issue to be reproducible). Hybrid topologies meet the aforementioned condition. In such cases, threads will be consolidated on CPUs of high priority using got HT siblings, while CPUs of medium priority will remain idle. https://projectacrn.org/ [Fix] Intel provides a list of patches to enable AlderLake [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel AlderLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952007/+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 1952356] Re: [EHL][TGL][ADL] PMU support
** Changed in: linux (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- 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/1952356 Title: [EHL][TGL][ADL] PMU support Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] The patches enable PMU support [Fix] Intel provides a list of patches to provide Linux perf supports [Test] This is requested by Intel. [Where problems could occur] Only applicable on Intel ElkhartLake/TigerLake/AdlerLake. Further testing will be required. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952356/+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 1961120] Re: SFH sensors are not working on some AMD platforms
** Changed in: hwe-next Status: In Progress => Fix Released ** Changed in: hwe-next Status: Fix Released => 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/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: Fix Committed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] The SRU contains two fixes: 1. increasing sensor command timeout from from 80 to 160. 2. using first valid 15 bits only ALS max illuminance values. [Test] This is requested by AMD. This was also verified by an AMD's engineer on CRB. [Where problems could occur] Low. The patches only increase timeout value and discard an invalid bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+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] Re: SBI SRST extension is missing
https://lists.ubuntu.com/archives/kernel-team/2022-February/128336.html -- 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: In Progress 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 1956461] Re: Creative HD720p webcam doesn't work
Thank you very much for the workaround! Without it, the bug is still present here, too. -- 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/1956461 Title: Creative HD720p webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen by the system. There is no /dev/vl4/ folder --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 3094 F pulseaudio /dev/snd/controlC0: piotr 3094 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-06-07 (578 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: Tags: uma Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+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 1860284] Re: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot
I'm also affected by this bug on 20.04 with the HWE 5.13 kernel (currently: 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux). My PCIe Thunderbolt card (ASUS ThunderboltEX 4, Intel JHL8540 controller) only partially works: the USB part works and USB devices plugged into the dock are recognised and functional (including the dock's built-in Ethernet interface), however there is no video signal coming from the dock's DisplayPort ports. I've tried the patch mentioned in the kernel bug tracker [1], but it doesn't fix the issue. Possibly relevant kernel messages: [0.602662] pci :38:00.0: BAR 1: assigned to efifb [0.629016] pci :02:00.0: BAR 13: no space for [io size 0x2000] [0.629017] pci :02:00.0: BAR 13: failed to assign [io size 0x2000] [0.629019] pci :02:00.0: BAR 13: no space for [io size 0x2000] [0.629020] pci :02:00.0: BAR 13: failed to assign [io size 0x2000] [0.629021] pci :03:00.0: BAR 13: no space for [io size 0x2000] [0.629022] pci :03:00.0: BAR 13: failed to assign [io size 0x2000] [0.629023] pci :03:00.0: BAR 13: no space for [io size 0x2000] [0.629024] pci :03:00.0: BAR 13: failed to assign [io size 0x2000] [0.629026] pci :04:01.0: BAR 13: no space for [io size 0x1000] [0.629027] pci :04:01.0: BAR 13: failed to assign [io size 0x1000] [0.629028] pci :04:03.0: BAR 13: no space for [io size 0x1000] [0.629029] pci :04:03.0: BAR 13: failed to assign [io size 0x1000] [0.629030] pci :04:03.0: BAR 13: no space for [io size 0x1000] [0.629031] pci :04:03.0: BAR 13: failed to assign [io size 0x1000] [0.629032] pci :04:01.0: BAR 13: no space for [io size 0x1000] [0.629033] pci :04:01.0: BAR 13: failed to assign [io size 0x1000] [4.271107] thunderbolt :05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xcb0f6500 flags=0x0020] [ 25.977578] thunderbolt :05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xcb0f6600 flags=0x0020] [ 46.457436] thunderbolt :05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xcb0f6700 flags=0x0020] [ 66.937458] thunderbolt :05:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xcb0f6800 flags=0x0020] [ 87.413107] thunderbolt :05:00.0: failed to send driver ready to ICM [ 87.414436] thunderbolt: probe of :05:00.0 failed with error -110 [1] https://lore.kernel.org/lkml/20200302141451.18983-1-mika.westerb...@linux.intel.com/ -- 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/1860284 Title: thinkpad thunderbolt 3 dock gen2 with pci memory allocation errors on Yoga C940 unless plugged in before boot Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have thinkpad thunderbolt 3 dock gen2 dock I am trying to use with a New Lenovo Yoga C940 laptop. - The dock works fine when plugged-in before boot. - The dock does NOT work when plugged after the system booted. - The dock does NOT work when plugged-in at boot, subsequently unplugged and plugged back in. When it fails, it fails with memory allocation messages such as: [ 342.507320] pci :2b:00.0: BAR 14: no space for [mem size 0x0c20] [ 342.507323] pci :2b:00.0: BAR 14: failed to assign [mem size 0x0c20] Things I tried: - Kernel mainline 5.4.12, same symptoms - Kernel mainline 5.5.-rc6, same symptoms. - Plugging it after powering up the laptop, but at the grub screen before boot. In this case the dock works fine after boot. Other potentially useful information to narrow it down: - The tests were done with only an ethernet cable and power plugged into the dock to minimize the number of moving parts... - Dock and laptop both have the very latest firmware as of 2020-01-17. - The displayport part of the dock always work, but all other ports (USB, ethernet, card readers fail) when plugged-in after boot. - Doesn't seem to be a thunderbolt authorization problem: benoitg@benoitg-Yoga-C940:~$ boltctl ? Lenovo ThinkPad Thunderbolt 3 Dock ?? type: peripheral ?? name: ThinkPad Thunderbolt 3 Dock ?? vendor:Lenovo ?? uuid: 001730c5-7042-0801-- ?? status:authorized ? ?? domain: c06e823d-af8a-8680-- ? ?? authflags: none ?? authorized:Sun Jan 19 17:41:04 2020 ?? connected: Sun Jan 19 17:41:04 2020 ?? stored:Thu Jan 16 07:27:43 2020 ?? policy: iommu ?? key:no ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-26-generic 5.3.0-26.28 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
This is clearly an endianness issue. I'll investigate whether the testcase needs to adapt to it or the sysfs interface of the netdevsim device needs to follow a pattern no matter what the system's endianness. -- 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/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+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 1960539] Re: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image
** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- 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/1960539 Title: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure blob driver adds support for accelerated access to Azure Blob storage for Azure VMs. Azure host uses its native network to perform Blob requests directly to Blob servers. [Test Case] Microsoft tested [Where things could go wrong] There should be little chance of regression since this is an elective module. [Other Info] SF: #00327792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960539/+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 1960820] Re: linux-azure: Missing ext4 commits
** 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/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+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 1960549] Re: Azure: CIFS backport request
** 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/1960549
Title:
Azure: CIFS backport request
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft is asking to have 3 CIFS patches backported to focal/linux-
azure.
506c1da44fee32ba1d3a70413289ad58c772bba6 ("cifs: use the expiry output of
dns_query to schedule next resolution")
4ac0536f8874a903a72bddc57eb88db774261e3a ("cifs: set a minimum of 120s for
next dns resolution")
7be3248f313930ff3d3436d4e9ddbe9fccc1f541 ("cifs: To match file servers, make
sure the server hostname matches")
This is a second attempt because the first backport attempt caused a
regression. This set has been thoroughly tested by Microsoft,
especially for the case that was causing the regression (DFS enabled
shares).
[Where things could go wrong]
Share connection attempts could fail. DFS shares could cause kernel
panics.
[Other Info]
SF: #00324495
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960549/+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 1960322] Re: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED
** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- 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/1960322 Title: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the addition of [1] in order to better account for dropped packets. Patch [2] is not strictly required, but will prevent context adjustments with future patches. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=e4b7621982d29f26ff4d39af389e5e675a4ffed4 [2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=68f831355052 [Test Plan] Microsoft tested [Where things could go wrong] RX dropped statistics could be in error. [Other Info] SF: #00327708 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960322/+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 1959529] Comment bridged from LTC Bugzilla
--- Comment From wint...@de.ibm.com 2022-02-25 12:03 EDT--- I installed and tested: # add-apt-repository ppa:fheimes/lp1959529 # apt install linux-image-unsigned-5.4.0-102-generic/focal-proposed (The instructions in https://wiki.ubuntu.com/Testing/EnableProposed did nor work for me) -- 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/1959529 Title: Hipersocket page allocation failure on Ubuntu 20.04 based SSC environments Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: == Comment: #0 - D. Gary Chapman - 2022-01-26 12:43:25 == ---Problem Description--- IBM IDAA customer exposes hipersocket page allocation failure on Ubuntu 20.04 based SSC Contact Information = Gary Chapman (ch...@us.ibm.com) ---uname output--- 5.4.0-73-generic #82-Ubuntu Machine Type = IBM Z in IDAA SSC-mode lpar ---Debugger--- A debugger is not configured -- IBM SSC LEVEL: 4.1.5 IBM IDAA LEVEL: 7.5.6 On a client system we are observing this: Jan 19 16:25:57 data5 kernel: kworker/u760:28: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0 Jan 19 16:25:57 data5 kernel: CPU: 20 PID: 4137988 Comm: kworker/u760:28 Kdump: loaded Tainted: G OE 5.4.0-73-generic #82-Ubuntu Jan 19 16:25:57 data5 kernel: Hardware name: IBM 8561 T01 727 (LPAR) Jan 19 16:25:57 data5 kernel: Workqueue: kcryptd/253:11 kcryptd_crypt [dm_crypt] Jan 19 16:25:57 data5 kernel: Call Trace: Jan 19 16:25:57 data5 kernel: ([<006b6d63e092>] show_stack+0x7a/0xc0) Jan 19 16:25:57 data5 kernel: [<006b6d64588a>] dump_stack+0x8a/0xb8 Jan 19 16:25:57 data5 kernel: [<006b6cfd8262>] warn_alloc+0xe2/0x160 IBM LTC Networking team has identified the upstream commit 714c9108851743bb718fbc1bfb81290f12a53854 as the root cause. This patch shows up in the Ubuntu kernel source tree: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/commit/?id=714c9108851743bb718fbc1bfb81290f12a53854 but has not been ported to Ubuntu 20.04 / kernel 5.4 IDAA on SSC requests backport to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959529/+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 1960322] Re: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED
This bug is awaiting verification that the linux-azure/5.4.0-1071.74 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1960322 Title: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the addition of [1] in order to better account for dropped packets. Patch [2] is not strictly required, but will prevent context adjustments with future patches. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=e4b7621982d29f26ff4d39af389e5e675a4ffed4 [2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=68f831355052 [Test Plan] Microsoft tested [Where things could go wrong] RX dropped statistics could be in error. [Other Info] SF: #00327708 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960322/+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 1960539] Re: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image
This bug is awaiting verification that the linux-azure/5.13.0-1015.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-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/1960539 Title: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure blob driver adds support for accelerated access to Azure Blob storage for Azure VMs. Azure host uses its native network to perform Blob requests directly to Blob servers. [Test Case] Microsoft tested [Where things could go wrong] There should be little chance of regression since this is an elective module. [Other Info] SF: #00327792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960539/+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 1925421] Re: arm64 support
This bug is awaiting verification that the linux-oracle/5.13.0-1019.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: Invalid Status in linux-oracle-5.8 package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Released Status in linux-oracle-5.4 source package in Hirsute: Invalid Status in linux-oracle-5.8 source package in Hirsute: Invalid Status in linux-oracle source package in Impish: Fix Released Status in linux-oracle-5.4 source package in Impish: Invalid Status in linux-oracle-5.8 source package in Impish: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+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 1960549] Re: Azure: CIFS backport request
This bug is awaiting verification that the linux-azure/5.4.0-1071.74
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1960549
Title:
Azure: CIFS backport request
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft is asking to have 3 CIFS patches backported to focal/linux-
azure.
506c1da44fee32ba1d3a70413289ad58c772bba6 ("cifs: use the expiry output of
dns_query to schedule next resolution")
4ac0536f8874a903a72bddc57eb88db774261e3a ("cifs: set a minimum of 120s for
next dns resolution")
7be3248f313930ff3d3436d4e9ddbe9fccc1f541 ("cifs: To match file servers, make
sure the server hostname matches")
This is a second attempt because the first backport attempt caused a
regression. This set has been thoroughly tested by Microsoft,
especially for the case that was causing the regression (DFS enabled
shares).
[Where things could go wrong]
Share connection attempts could fail. DFS shares could cause kernel
panics.
[Other Info]
SF: #00324495
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960549/+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 1960539] Re: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image
This bug is awaiting verification that the linux-azure/5.4.0-1071.74 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1960539 Title: linux-azure: Add Azure Blob driver to Ubuntu 18.04 image Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Azure blob driver adds support for accelerated access to Azure Blob storage for Azure VMs. Azure host uses its native network to perform Blob requests directly to Blob servers. [Test Case] Microsoft tested [Where things could go wrong] There should be little chance of regression since this is an elective module. [Other Info] SF: #00327792 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960539/+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 1960322] Re: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED
This bug is awaiting verification that the linux-azure/5.13.0-1015.17 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-impish ** Tags added: verification-needed-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/1960322 Title: linux-azure: net: mana: Add handling of CQE_RX_TRUNCATED Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the addition of [1] in order to better account for dropped packets. Patch [2] is not strictly required, but will prevent context adjustments with future patches. [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=e4b7621982d29f26ff4d39af389e5e675a4ffed4 [2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=68f831355052 [Test Plan] Microsoft tested [Where things could go wrong] RX dropped statistics could be in error. [Other Info] SF: #00327708 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960322/+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 1960820] Re: linux-azure: Missing ext4 commits
This bug is awaiting verification that the linux-azure/5.4.0-1071.74 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1960820 Title: linux-azure: Missing ext4 commits Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has a test that checks for missing file system commits; It has detected that these commits are not present in Azure tuned kernels: 0f2f87d51aebcf71a709b52f661d681594c7dffa ext4: prevent partial update of the extent blocks 9c6e071913792d80894cd0be98cc3c4b770e26d3 ext4: check for inconsistent extents between index and leaf block 8dd27fecede55e8a4e67eef2878040ecad0f0d33 ext4: check for out-of-order index extents in ext4_valid_extent_entries() [Test Case] Microsoft tested [Where things could go wrong] Ext4 file systems could have problems. [Other Info] SF: #00324445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1960820/+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 1962299] Re: Add missing firmware for HWE 5.14 kernel
** Description changed: firmware files required by 5.14 which are present in jammy but missing in focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin + amdgpu/aldebaran_mec.bin + amdgpu/aldebaran_mec2.bin + amdgpu/aldebaran_rlc.bin + amdgpu/aldebaran_sdma.bin + amdgpu/aldebaran_smc.bin + amdgpu/aldebaran_sos.bin + amdgpu/aldebaran_ta.bin + amdgpu/aldebaran_vcn.bin + amdgpu/arcturus_asd.bin + amdgpu/arcturus_gpu_info.bin + amdgpu/arcturus_mec.bin + amdgpu/arcturus_rlc.bin + amdgpu/arcturus_sdma.bin + amdgpu/arcturus_smc.bin + amdgpu/arcturus_sos.bin + amdgpu/arcturus_ta.bin + amdgpu/arcturus_vcn.bin + amdgpu/cyan_skillfish2_ce.bin + amdgpu/cyan_skillfish2_me.bin + amdgpu/cyan_skillfish2_mec.bin + amdgpu/cyan_skillfish2_mec2.bin + amdgpu/cyan_skillfish2_pfp.bin + amdgpu/cyan_skillfish2_rlc.bin + amdgpu/cyan_skillfish2_sdma.bin + amdgpu/cyan_skillfish2_sdma1.bin + amdgpu/navy_flounder_ce.bin + amdgpu/navy_flounder_dmcub.bin + amdgpu/navy_flounder_me.bin + amdgpu/navy_flounder_mec.bin + amdgpu/navy_flounder_mec2.bin + amdgpu/navy_flounder_pfp.bin + amdgpu/navy_flounder_rlc.bin + amdgpu/navy_flounder_sdma.bin + amdgpu/navy_flounder_smc.bin + amdgpu/navy_flounder_sos.bin + amdgpu/navy_flounder_ta.bin + amdgpu/navy_flounder_vcn.bin + amdgpu/vangogh_asd.bin + amdgpu/vangogh_ce.bin + amdgpu/vangogh_dmcub.bin + amdgpu/vangogh_me.bin + amdgpu/vangogh_mec.bin + amdgpu/vangogh_mec2.bin + amdgpu/vangogh_pfp.bin + amdgpu/vangogh_rlc.bin + amdgpu/vangogh_sdma.bin + amdgpu/vangogh_toc.bin + amdgpu/vangogh_vcn.bin + atmel/wilc1000_wifi_firmware-1.bin + brcm/brcmfmac43340-sdio.predia-basic.txt + brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt + brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt + brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt + brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt + brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt + brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt + brcm/brcmfmac43430a0-sdio.ilife-S806.txt + brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi 4 Model B.txt + brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi Compute Module 4.txt + brcm/brcmfmac43455-sdio.acepc-t8.txt + brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt + brcm/brcmfmac4356-sdio.khadas,vim2.txt + brcm/brcmfmac4356-sdio.vamrs,rock960.txt + brcm/brcmfmac43012-sdio.bin + brcm/brcmfmac43012-sdio.clm_blob + brcm/brcmfmac43430-sdio.clm_blob + brcm/brcmfmac43455-sdio.clm_blob + brcm/brcmfmac4354-sdio.clm_blob + brcm/brcmfmac4356-pcie.clm_blob + brcm/brcmfmac4356-sdio.clm_blob + brcm/brcmfmac43570-pcie.clm_blob + brcm/brcmfmac4373-sdio.clm_blob + i915/adlp_guc_62.0.3.bin + i915/bxt_guc_62.0.0.bin + i915/cml_guc_62.0.0.bin + i915/ehl_guc_62.0.0.bin + i915/glk_guc_62.0.0.bin + i915/icl_guc_62.0.0.bin + i915/kbl_guc_62.0.0.bin + i915/rkl_dmc_ver2_03.bin + i915/skl_guc_62.0.0.bin + i915/tgl_dmc_ver2_12.bin + i915/tgl_guc_62.0.0.bin + i915/tgl_huc_7.9.3.bin + iwlwifi-Qu-b0-hr-b0-66.ucode + iwlwifi-Qu-b0-jf-b0-66.ucode + iwlwifi-Qu-c0-hr-b0-66.ucode + iwlwifi-QuZ-a0-hr-b0-66.ucode + iwlwifi-QuZ-a0-jf-b0-66.ucode + iwlwifi-cc-a0-66.ucode + iwlwifi-ty-a0-gf-a0-66.ucode + mellanox/mlxsw_spectrum-13.2008.2406.mfa2 + mellanox/mlxsw_spectrum2-29.2008.2406.mfa2 + mellanox/mlxsw_spectrum3-30.2008.2406.mfa2 + nvidia/tegra194/vic.bin + rtl_bt/rtl8821a_config.bin + rtl_nic/rtl8153c-1.fw + rtl_nic/rtl8156a-2.fw + rtl_nic/rtl8156b-2.fw -- 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/1962299 Title: Add missing firmware for HWE 5.14 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Bug description: firmware files required by 5.14 which are present in jammy but missing in focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin amdgpu/aldebaran_mec.bin amdgpu/aldebaran_mec2.bin amdgpu/aldebaran_rlc.bin amdgpu/aldebaran_sdma.bin amdgpu/aldebaran_smc.bin amdgpu/aldebaran_sos.bin amdgpu/aldebaran_ta.bin amdgpu/aldebaran_vcn.bin amdgpu/arcturus_asd.bin amdgpu/arcturus_gpu_info.bin amdgpu/arcturus_mec.bin amdgpu/arcturus_rlc.bin amdgpu/arcturus_sdma.bin amdgpu/arcturus_smc.bin amdgpu/arcturus_sos.bin amdgpu/arcturus_ta.bin amdgpu/arcturus_vcn.bin amdgpu/cyan_skillfish2_ce.bin amdgpu/cyan_skillfish2_me.bin amdgpu/cyan_skillfish2_mec.bin amdgpu/cyan_skillfish2_mec2.bin amdgpu/cyan_skillfish2_pfp.bin amdgpu/cyan_skillfish2_rlc.bin amdgpu/cyan_skillfish2_sdma.bin amdgpu/cyan_skillfish2_sdma1.bin amdgpu/navy_flounder_ce.bin amdgpu/navy_flounder_dmcub.bin amdgpu/navy_flounder_me.bin amdgpu/navy_flounder_mec.bin amdgpu/navy_flounder_mec2.bin amdgpu/navy_flounder_pfp.bin amdgpu/navy_flounder_rlc.bin amdgpu/navy_flounder_sdma.bin amdgpu/navy_flounder_smc.bin amdgpu/navy_flounder_sos.bin amdgpu/navy_flounder_ta.bin
[Kernel-packages] [Bug 1962299] Re: Add missing firmware for HWE 5.14 kernel
** Summary changed: - Update/add firmware for HWE 5.14 kernel + Add missing firmware for HWE 5.14 kernel -- 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/1962299 Title: Add missing firmware for HWE 5.14 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Bug description: firmware files required by 5.14 which are present in jammy but missing in focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962299/+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 1962330] [NEW] Focal update: v5.4.175 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.175 upstream stable release from git://git.kernel.org/ rcu: Tighten rcu_advance_cbs_nowake() checks pinctrl: bcm2835: Drop unused define pinctrl: bcm2835: Refactor platform data pinctrl: bcm2835: Add support for all GPIOs on BCM2711 pinctrl: bcm2835: Match BCM7211 compatible string pinctrl: bcm2835: Add support for wake-up interrupts pinctrl: bcm2835: Change init order for gpio hogs ARM: dts: gpio-ranges property is now required mmc: sdhci-esdhc-imx: disable CMDQ support select: Fix indefinitely sleeping task in poll_schedule_timeout() Linux 5.4.175 UBUNTU: upstream stable to v5.4.175 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) 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 Focal) 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) => 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: + v5.4.175 upstream stable release + from git://git.kernel.org/ -v5.4.175 upstream stable release -from git://git.kernel.org/ + rcu: Tighten rcu_advance_cbs_nowake() checks + pinctrl: bcm2835: Drop unused define + pinctrl: bcm2835: Refactor platform data + pinctrl: bcm2835: Add support for all GPIOs on BCM2711 + pinctrl: bcm2835: Match BCM7211 compatible string + pinctrl: bcm2835: Add support for wake-up interrupts + pinctrl: bcm2835: Change init order for gpio hogs + ARM: dts: gpio-ranges property is now required + mmc: sdhci-esdhc-imx: disable CMDQ support + select: Fix indefinitely sleeping task in poll_schedule_timeout() + Linux 5.4.175 + UBUNTU: upstream stable to v5.4.175 -- 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/1962330 Title: Focal update: v5.4.175 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.175 upstream stable release from git://git.kernel.org/ rcu: Tighten rcu_advance_cbs_nowake() checks pinctrl: bcm2835: Drop unused define pinctrl: bcm2835: Refactor platform data pinctrl: bcm2835: Add support for all GPIOs on BCM2711 pinctrl: bcm2835: Match BCM7211 compatible string pinctrl: bcm2835: Add support for wake-up interrupts pinctrl: bcm2835: Change init order for gpio hogs ARM: dts: gpio-ranges property is now required mmc: sdhci-esdhc-imx: disable CMDQ support select: Fix indefinitely sleeping task in poll_schedule_timeout() Linux 5.4.175 UBUNTU: upstream stable to v5.4.175 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1959085] Re: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption
Thank you all for investigating and fixing this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1959085 Title: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption Status in Ubuntu CD Images: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h 288M 542M 156M /boot rpool 6.39G
[Kernel-packages] [Bug 1959085] Re: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption
On 21.10, zfs-linux packages 2.0.6-1ubuntu2 generate incorrect boot entries for snapshoted systems, please upgrade to 2.0.6-1ubuntu2.1. Snapshots created with the broken old version are not bootable. ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: ubuntu-cdimage Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1959085 Title: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption Status in Ubuntu CD Images: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT
[Kernel-packages] [Bug 1954998] Re: Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp
ac15e9196f35d88b4d94bbcf3a5294ebb5622eb0 is the only one missing from oem-5.14 now -- 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/1954998 Title: Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp Status in HWE Next: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: On some designs that have sensor-fusion-hub (SFH) they need to have MP2 going into proper state for suspend/resume to work properly. This requires backporting some code into amd-sfh driver from upstream. The following 4 commits from 5.15 will enable this: 3978f54817559b28535c58a00d3d31bbd5d0b65a 173709f50e98df4c49c2776834605a2f7ed3e681 ac15e9196f35d88b4d94bbcf3a5294ebb5622eb0 0873d1afacd2167e717ea751fe7274011cb4c26a To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954998/+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 1961793] Re: Focal update: upstream stable patchset 2022-02-22
** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => 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/1961793 Title: Focal update: upstream stable patchset 2022-02-22 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-02-22 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1961793/+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 1961855] Re: Fix With 20.04d kernel and WX3200, unit freezes on resume
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: New => Invalid
** 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/1961855
Title:
Fix With 20.04d kernel and WX3200, unit freezes on resume
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 Committed
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
* PPC64LE hardware does not support ASPM at a hardware level.
CONFIG_PCIEASPM is often disabled on these architectures.
* Some dGPUs on ALD platforms don't work with ASPM enabled and PCIe
subsystem disables it
Check with the PCIe subsystem to see that ASPM has been enabled
or not.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, just disable AMDGPU ASPM if system doesn't enable it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1961855/+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 1961971] Re: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently
does this affect jammy kernel? ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** 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/1961971 Title: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently 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 Committed Bug description: [Impact] Ubuntu currently doesn't support wifi 6e, but wifi 6e AP will be discovered while scanning. User can't get connected to those wifi 6e AP, so disable UHB(ultra high band) in the driver to avoid scanning those bands. [Fix] Marks all AX210 and AX211 cards to disable UHB. [Test] Verified the system with AX211 card and confirm it can't discover wifi 6e bands. [Where problems could occur] Disable non-supported bands won't introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961971/+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 1959085] Re: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption
Ubuntu 22.04 daily images testing issues have been resolved and a new image promoted, jammy installs are now working correctly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1959085 Title: Ubuntu 22.04 boot stuck in initramfs, when installed with zfs encryption Status in Ubuntu CD Images: Confirmed Status in initramfs-tools package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Incomplete Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h 288M 542M
[Kernel-packages] [Bug 1960621] Re: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers
I've built Metacity 3.42 for Ubuntu 21.10 with Xpresent support, which is behind a gsettings option that defaults to xrender. When Metacity is set as the required window manager in MATE with Xpresent set as the compositor the same failure to bring up a desktop session is encountered. I have also built Marco without Xpresent and as expected it fallsback to Xrender which works with the new NVIDIA drivers and also preserves compositor support. ** Summary changed: - Nvidia 510 drivers result in failure to start GUI on GeForce GTX 1050 Ti + MATE Desktop session fails to start with NVIDIA 495 & 510 drivers ** Also affects: metacity (Ubuntu) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: marco (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: marco (Ubuntu Jammy) Importance: High Assignee: Martin Wimpress (flexiondotorg) Status: Triaged ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Also affects: metacity (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: marco (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Impish) Importance: Undecided Status: New ** No longer affects: metacity (Ubuntu Focal) ** No longer affects: metacity (Ubuntu Impish) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: MATE Desktop session fails to start with NVIDIA 495 & 510 drivers Status in marco package in Ubuntu: Triaged Status in metacity package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in marco source package in Focal: New Status in nvidia-graphics-drivers-510 source package in Focal: New Status in marco source package in Impish: New Status in nvidia-graphics-drivers-510 source package in Impish: New Status in marco source package in Jammy: Triaged Status in metacity source package in Jammy: New Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
This is also affecting jammy/linux 5.15.0-22.22. ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+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 1959216] Re: linux-azure: CONFIG_FB_EFI=y
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959216 Title: linux-azure: CONFIG_FB_EFI=y Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure-5.13 package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux-azure-5.11 source package in Bionic: Invalid Status in linux-azure-5.13 source package in Bionic: Invalid Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Released Status in linux-azure-4.15 source package in Impish: Invalid Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure-5.13 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-4.15 source package in Jammy: Invalid Status in linux-azure-5.11 source package in Jammy: Invalid Status in linux-azure-5.13 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Secure boot instances of linux-azure require an EFI framebuffer in some cases in order for the VM to boot. The issue was noticed in Ubuntu 18.04 linux-azure kernel, but actually exists in the latest mainline kernel. The issue happens when the below conditions are met: hyperv_pci is built into the kernel and hyperv_fb is not, i.e., this means hyperv_pci loads before hyperv_fb loads. CONFIG_FB_EFI is not defined, i.e., the efifb driver is not used. Here is how the bug happens: Linux VM starts, and vmbus_reserve_fb() reserves the VRAM [base=0xf800, length=8MB]. hyper-pci loads, gets MMIO [base=0xf880, lengh=8KB] as the bridge config window, and may get some other 64-bit MMIO ranges, and some 32-bit MMIO ranges (if needed.) hyperv-fb loads, and gets MMIO [base=0xf800, lengh=8MB or a different length], and sets screen_info.lfb_base = 0. VM panics. The kdump kernel starts to run, and vmbus_reserve_fb() is not reserving [base=0xf800, length=8MB] due to the lfb_base==0. hyperv-pci loads and gets [base=0xf800, lengh=8KB] and the host PCI VSP driver rejects this address as the bridge config window. The crux of the problem is that Linux vmbus driver itself is unable to detect the VRAM base/length (it looks like a video BIOS call is needed to get this info and such a BIOS call is inappropriate or impossible in hv_vmbus) and has to rely on screen_info.lfb_base (which is set by grub or the kdump/kexec tool and can be reset to zero by hyperv_fb/drm). Solution: Enable CONFIG_FB_EFI=y [Test Case] Microsoft tested. This config is also enabled on the master branch. [Where things could go wrong] VMs on certain instance types could fail to boot. [Other Info] SF: #00327005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1959216/+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 1912773] Re: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not working, cpu/agpu performance dropped considerably
This issue still exists, when trying to figure out why bug #1962308 was
happening, this exact same problem still happens on 5.8.0-63 (originally
reported on 5.8.0-40).
--
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/1912773
Title:
[MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
display not working, cpu/agpu performance dropped considerably
Status in Linux Firmware:
New
Status in Mutter:
New
Status in linux package in Ubuntu:
Invalid
Bug description:
After a recent update, I now have a system that can no longer play
audio (via HDMI), my second monitor (DVI) is no longer being picked
up, and CPU/AGPU usage has lost a lot of performance (OBS is basically
unusable at this point).
Whatever has happened with the recent updates has caused the AMD
drivers (presumably?) to not work correctly - because it is an AMD
Ryzen 5 3400g (with no dedicated graphics card).
1) The release of Ubuntu you are using, via 'lsb_release -rd' or
System -> About Ubuntu
```
$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
```
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
Not sure which package would be the cause, however these were the
version that were working prior to the update:
```
libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3
libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3
udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3
systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3
systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3
libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2
apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2
ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29
update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1
python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1
update-notifier=3.192.30.3 update-notifier-common=3.192.30.3
libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3
mutter-common=3.36.6-1ubuntu0.20.04.2
gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2
libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1
linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23
linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70
mutter=3.36.6-1ubuntu0.20.04.2
```
This list was generated with the command:
`awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) {
start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)(
]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`
3) What you expected to happen
Sound and video working via HDMI on primary monitor, second monitor
displaying (extended) video via DVI. CPU and AGPU being able to render
via OBS.
4) What happened instead
No sound. No second display. Any CPU or AGPU tasks running slower than
normal.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: hazrpg 3344 F pulseaudio
/dev/snd/controlC2: hazrpg 3344 F pulseaudio
/dev/snd/controlC0: hazrpg 3344 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 22 11:51:14 2021
InstallationDate: Installed on 2020-05-22 (244 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Raven/Raven2/Fenghuang HDMI/DP Audio Controller - HD-Audio
Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.20
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A320M-A PRO MAX (MS-7C52)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias:
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
Also found with impish/linux 5.13.0-32.35. ** Tags added: 5.13 impish sru-20220221 -- 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/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Won't Fix Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+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 1933179] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2022-02-25 07:32 EDT---
Capability number will be 211, see this merge
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
--
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/1933179
Title:
[22.04 FEAT] KVM: Enable storage key checking for intercepted
instruction handled by userspace
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Bug description:
KVM uses lazy storage key enablement as Linux does no longer make use of the
storage keys. When the guest enters keyed mode, then KVM will save/restore the
key during paging, provide change/reference tracking for guest and host and for
all interpreted instructions will do key protection.
If an instruction is intercepted and passed along to userspace (like QEMU) no
storage key protection is checked, though. This is in violation of the
architecture and it can result in misbehaving guests that rely on key
protection for all instructions.
This item will improve the MEMOP ioctl to also add key checking. In case of a
key protection the right fault is injected in the guest.
Value: Interoperability
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1933179/+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 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
Also found with impish/linux 5.13.0-32.35. ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Tags added: sru-20220221 -- 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/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Confirmed Bug description: Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+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 1928890] Re: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
** Changed in: linux-oem-5.10 (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928890 Title: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.10 source package in Hirsute: Won't Fix Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh 00:09:30 DEBUG| [stdout] # 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup ping 00:09:30 DEBUG| [stdout] # ### 00:09:30 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup traceroute 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:32 DEBUG| [stdout] # 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error route lookup ping 00:09:32 DEBUG| [stdout] # ### 00:09:32 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed [ OK ] 00:09:34 DEBUG| [stdout] # 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup ping 00:09:34 DEBUG| [stdout] # ### 00:09:34 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity [ OK ] 00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded [ OK ] 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup traceroute 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute 00:09:36 DEBUG| [stdout] # 00:09:36 DEBUG| [stdout] # ### 00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup ping 00:09:36 DEBUG| [stdout] #
[Kernel-packages] [Bug 1948724] Re: udpgro_fwd from selftests/net fails ADT test failure with impish
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Tags added: 5.13 sru-20220221 -- 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/1948724 Title: udpgro_fwd from selftests/net fails ADT test failure with impish Status in linux package in Ubuntu: Expired Status in linux source package in Impish: Confirmed Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.13.0-21.21 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. This is not a regression; found previously on 5.13.0-19.19 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/l/linux/20211021_221027_e5903@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/l/linux/20211023_154712_826b9@/log.gz 21:21:14 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 21:21:14 DEBUG| [stdout] # IPv4 21:21:14 DEBUG| [stdout] # No GRO ok 21:21:14 DEBUG| [stdout] # GRO frag listok 21:21:15 DEBUG| [stdout] # GRO fwd ok 21:21:16 DEBUG| [stdout] # UDP fwd perfudp rx: 219 MB/s 178766 calls/s 21:21:16 DEBUG| [stdout] # udp tx:290 MB/s 4927 calls/s 4927 msg/s 21:21:17 DEBUG| [stdout] # udp rx:280 MB/s 228627 calls/s 21:21:17 DEBUG| [stdout] # udp tx:284 MB/s 4828 calls/s 4828 msg/s 21:21:18 DEBUG| [stdout] # udp rx:263 MB/s 214183 calls/s 21:21:18 DEBUG| [stdout] # udp tx:281 MB/s 4775 calls/s 4775 msg/s 21:21:19 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 238 MB/s 194146 calls/s 21:21:19 DEBUG| [stdout] # udp tx:271 MB/s 4598 calls/s 4598 msg/s 21:21:20 DEBUG| [stdout] # ./udpgso_bench_tx: sendmsg: Connection refused 21:21:20 DEBUG| [stdout] # fail client exit code 1, server 0 21:21:20 DEBUG| [stdout] # GRO frag list over UDP tunnelok 21:21:21 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 21:21:22 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 122 MB/s99319 calls/s 21:21:22 DEBUG| [stdout] # udp tx:222 MB/s 3782 calls/s 3782 msg/s 21:21:23 DEBUG| [stdout] # udp rx:161 MB/s 131528 calls/s 21:21:23 DEBUG| [stdout] # udp tx:228 MB/s 3868 calls/s 3868 msg/s 21:21:24 DEBUG| [stdout] # udp rx:197 MB/s 160785 calls/s 21:21:24 DEBUG| [stdout] # udp tx:218 MB/s 3698 calls/s 3698 msg/s 21:21:25 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 200 MB/s 163194 calls/s 21:21:25 DEBUG| [stdout] # udp tx:231 MB/s 3921 calls/s 3921 msg/s 21:21:26 DEBUG| [stdout] # udp rx:193 MB/s 157637 calls/s 21:21:26 DEBUG| [stdout] # udp tx:220 MB/s 3744 calls/s 3744 msg/s 21:21:27 DEBUG| [stdout] # udp rx:226 MB/s 184120 calls/s 21:21:27 DEBUG| [stdout] # udp tx:240 MB/s 4073 calls/s 4073 msg/s 21:21:27 DEBUG| [stdout] # IPv6 21:21:28 DEBUG| [stdout] # No GRO ok 21:21:28 DEBUG| [stdout] # GRO frag listok 21:21:28 DEBUG| [stdout] # GRO fwd ok 21:21:30 DEBUG| [stdout] # UDP fwd perfudp rx: 174 MB/s 142456 calls/s 21:21:30 DEBUG| [stdout] # udp tx:299 MB/s 5076 calls/s 5076 msg/s 21:21:31 DEBUG| [stdout] # udp rx:239 MB/s 195356 calls/s 21:21:31 DEBUG| [stdout] # udp tx:311 MB/s 5276 calls/s 5276 msg/s 21:21:32 DEBUG| [stdout] # udp rx:301 MB/s 245849 calls/s 21:21:32 DEBUG| [stdout] # udp tx:307 MB/s 5213 calls/s 5213 msg/s 21:21:33 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 196 MB/s 160372 calls/s 21:21:33 DEBUG| [stdout] # udp tx:228 MB/s 3876 calls/s 3876 msg/s 21:21:34 DEBUG| [stdout] # udp rx:341 MB/s 278286 calls/s 21:21:34 DEBUG| [stdout] # udp tx:339 MB/s 5760 calls/s 5760 msg/s 21:21:35 DEBUG| [stdout] # udp rx:272 MB/s 221441 calls/s 21:21:35 DEBUG| [stdout] # udp tx:304 MB/s 5160 calls/s 5160 msg/s 21:21:35 DEBUG| [stdout] # GRO frag list over UDP tunnelok 21:21:36 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 21:21:37 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 21:21:37 DEBUG| [stdout] # fail client exit code 1, server 0 21:21:38 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 201 MB/s 164027 calls/s 21:21:38 DEBUG| [stdout] # udp tx:234 MB/s
[Kernel-packages] [Bug 1962308] [NEW] Video captures (e.g. webcam, capture card) are being displayed as "Video Capture 3"
Public bug reported: This issue seems to have been introduced in 5.13 somewhere, I only had 5.13.0-30 and 5.13.0-28 available in grub on the 5.13 branch to test against, but in both instances all capture devices are labelled as "Video Capture 3" where previously it would show the device's actual name. I do still have 5.8 branch and 5.4 branch, and when testing against 5.8.0-63 it showed the names correctly everywhere, and likewise with 5.4.0-64. The number at the end seems to be the number of devices, even though it is getting the counted digit and repeating it for all of them. If I run: $ v4l2-ctl --list-devices I get: Video Capture 3 (usb-:08:00.3-3): /dev/video2 /dev/video3 /dev/media1 Video Capture 3 (usb-:08:00.3-4): /dev/video4 /dev/video5 /dev/media2 Video Capture 3 (usb-:08:00.4-1): /dev/video0 /dev/video1 /dev/media0 The devices I have (from lsusb) are: Bus 003 Device 004: ID 534d:2109 MACROSILICON Bus 003 Device 003: ID 298f:1996 MACROSILICON ShadowCast Bus 005 Device 002: ID 0458:6006 KYE Systems Corp. (Mouse Systems) AUKEY PC-LM1E Camera Previously the devices would be labelled as: MACROSILICON MACROSILICON ShadowCast AUKEY PC-LM1E Camera There appears to be a mismatch in the usb bus numbers too. You'll notice in v4l2-ctl 2 of them are correctly identified as Bus 003 and Device 003 andd 004 respectively (outlined as 00.3-3 and 00.3-4), however the last device shows 00.4-1 but in lsusb this is received as Bus 005 Device 002 - so it should be 00.5-2 if I'm right in the naming conventions that should be used. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu 20.04.4 LTS Release:20.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy linux-image-5.13.0-30-generic linux-image-5.13.0-30-generic: Installed: 5.13.0-30.33~20.04.1 Candidate: 5.13.0-30.33~20.04.1 Version table: *** 5.13.0-30.33~20.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen The labels of the USB devices to show up correctly in Zoom, OBS, Microsoft Teams, Skype, Cheese, etc so that I can identify which device to use. 4) What happened instead The labels are wrong and given a generic "Video Camera 3" label for all of them - where 3 is the number of devices I have connected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 12:07:37 2022 InstallationDate: Installed on 2020-05-22 (643 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (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.13 in Ubuntu. https://bugs.launchpad.net/bugs/1962308 Title: Video captures (e.g. webcam, capture card) are being displayed as "Video Capture 3" Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: This issue seems to have been introduced in 5.13 somewhere, I only had 5.13.0-30 and 5.13.0-28 available in grub on the 5.13 branch to test against, but in both instances all capture devices are labelled as "Video Capture 3" where previously it would show the device's actual name. I do still have 5.8 branch and 5.4 branch, and when testing against 5.8.0-63 it showed the names correctly everywhere, and likewise with 5.4.0-64. The number at the end seems to be the number of devices, even though it is getting the counted digit and repeating it for all of them. If I run: $ v4l2-ctl --list-devices I get: Video Capture 3 (usb-:08:00.3-3): /dev/video2 /dev/video3 /dev/media1 Video Capture 3 (usb-:08:00.3-4): /dev/video4 /dev/video5 /dev/media2 Video Capture 3 (usb-:08:00.4-1): /dev/video0 /dev/video1 /dev/media0 The devices I have (from lsusb) are: Bus 003 Device 004: ID 534d:2109 MACROSILICON Bus 003 Device 003: ID 298f:1996 MACROSILICON ShadowCast Bus 005 Device 002: ID 0458:6006 KYE Systems Corp. (Mouse Systems) AUKEY PC-LM1E Camera Previously the devices would be labelled as:
[Kernel-packages] [Bug 1962299] Re: Update/add firmware for HWE 5.14 kernel
** Description changed: firmware files required by 5.14 which are present in jammy but missing in focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin - cmmb_vega_12mhz.inp - cmmb_venice_12mhz.inp - dvb_nova_12mhz.inp - dvb_nova_12mhz_b0.inp - isdbt_nova_12mhz.inp - isdbt_nova_12mhz_b0.inp - isdbt_rio.inp - sms1xxx-hcw-55xxx-dvbt-02.fw - sms1xxx-hcw-55xxx-isdbt-02.fw - sms1xxx-nova-a-dvbt-01.fw - sms1xxx-nova-b-dvbt-01.fw - sms1xxx-stellar-dvbt-01.fw - tdmb_nova_12mhz.inp -- 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/1962299 Title: Update/add firmware for HWE 5.14 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Bug description: firmware files required by 5.14 which are present in jammy but missing in focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962299/+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 1962299] Re: Update/add firmware for HWE 5.14 kernel
** Description changed: - TBD + firmware files required by 5.14 which are present in jammy but missing + in focal: + + amd/amd_sev_fam17h_model3xh.sbin + amd/amd_sev_fam19h_model0xh.sbin + cmmb_vega_12mhz.inp + cmmb_venice_12mhz.inp + dvb_nova_12mhz.inp + dvb_nova_12mhz_b0.inp + isdbt_nova_12mhz.inp + isdbt_nova_12mhz_b0.inp + isdbt_rio.inp + sms1xxx-hcw-55xxx-dvbt-02.fw + sms1xxx-hcw-55xxx-isdbt-02.fw + sms1xxx-nova-a-dvbt-01.fw + sms1xxx-nova-b-dvbt-01.fw + sms1xxx-stellar-dvbt-01.fw + tdmb_nova_12mhz.inp -- 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/1962299 Title: Update/add firmware for HWE 5.14 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Bug description: firmware files required by 5.14 which are present in jammy but missing in focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962299/+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 1960621] Re: Nvidia 510 drivers result in failure to start GUI on GeForce GTX 1050 Ti
** Also affects: marco (Ubuntu) Importance: Undecided Status: New ** Changed in: marco (Ubuntu) Status: New => Triaged ** Changed in: marco (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: marco (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1960621 Title: Nvidia 510 drivers result in failure to start GUI on GeForce GTX 1050 Ti Status in marco package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Bug description: I have been using nvidia-graphics-drivers-470 for a while. In January, I tried the 495 drivers, but this resulted in failing to start the GUI when booting: the mouse cursor would appear, but then the screen would clear and the switch to graphics would be attempted again. This would repeat until restarted, so I used recovery mode to test that a) it still happened with that (yes) and b) to go back to the 470 drivers via the root terminal. For some reason, yesterday xscreensaver had a problem getting the right GLcontext. I noticed that the 510 drivers were available, so used Software & Updates's Additional Drivers to install those. Exactly the same issue as with the 495 drivers: the mouse cursor appears for a second, then disappears, and reappears, and.. until I reboot and go back to 470. I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card. $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1960621/+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 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Hi, sorry for the delay. I checked test kernel and it works as expected. I think you can submit it. Thanks, Kinga Tanska -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+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 1962301] [NEW] Ubuntu MATE wont boot after driver-510 is installed.
Public bug reported: Fails to boot with both kernel 5.13.0-28-generic and the xanmod kernel 16.8.1. Mint users with MATE desktop are reporting the issue as well here: https://forums.linuxmint.com/viewtopic.php?f=59=367590=e1d3fd68daf901fa83b69f3597eb1682=20 And there's a nvidia thread here: https://forums.developer.nvidia.com/t/cant-boot-after-upgrading- to-510-driver-on-ubuntu-20-04/202625/18 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-510 (not installed) Uname: Linux 5.16.11-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Feb 25 11:40:34 2022 InstallationDate: Installed on 2021-08-08 (200 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to impish on 2022-02-14 (10 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1962301 Title: Ubuntu MATE wont boot after driver-510 is installed. Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Fails to boot with both kernel 5.13.0-28-generic and the xanmod kernel 16.8.1. Mint users with MATE desktop are reporting the issue as well here: https://forums.linuxmint.com/viewtopic.php?f=59=367590=e1d3fd68daf901fa83b69f3597eb1682=20 And there's a nvidia thread here: https://forums.developer.nvidia.com/t/cant-boot-after-upgrading- to-510-driver-on-ubuntu-20-04/202625/18 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nvidia-driver-510 (not installed) Uname: Linux 5.16.11-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Feb 25 11:40:34 2022 InstallationDate: Installed on 2021-08-08 (200 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to impish on 2022-02-14 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1962301/+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 1962299] [NEW] Update/add firmware for HWE 5.14 kernel
Public bug reported: TBD ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Summary changed: - Update firmware for HWE 5.14 + Update firmware for HWE 5.14 kernel ** Summary changed: - Update firmware for HWE 5.14 kernel + Update/add firmware for HWE 5.14 kernel -- 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/1962299 Title: Update/add firmware for HWE 5.14 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Bug description: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962299/+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 1961968] Re: Broken network on some AWS instances with focal/impish kernels
Confirmed that impish/linux 5.13.0-32.35 and focal/linux 5.4.0-102.115 are not failing to boot on any AWS instance. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** 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/1961968 Title: Broken network on some AWS instances with focal/impish kernels Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] With the latest focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels built for SRU cycle 2022.02.21 some AWS instances fail to boot. This impacts mostly the instance types: c4.large, c3.xlarge and x1e.xlarge. However, not all instances deployed on those types will fail. This is affecting mostly c4.large which fails about 80-90% of all deployments. This was traced to be caused by the network interface failing to come up. The following console log snippets from 5.4.0-101-generic on a c4.large show some hints of what's going on: [...] [3.990368] unchecked MSR access error: RDMSR from 0xc90 at rIP: 0x8ea733c8 (native_read_msr+0x8/0x40) [3.998463] Call Trace: [4.001164] ? set_rdt_options+0x91/0x91 [4.004864] resctrl_late_init+0x592/0x63c [4.008711] ? set_rdt_options+0x91/0x91 [4.012452] do_one_initcall+0x4a/0x200 [4.016115] kernel_init_freeable+0x1c0/0x263 [4.020402] ? rest_init+0xb0/0xb0 [4.024889] kernel_init+0xe/0x110 [4.029245] ret_from_fork+0x35/0x40 [...] [7.718268] ena: The ena device sent a completion but the driver didn't receive a MSI-X interrupt (cmd 8), autopolling mode is OFF [7.727036] ena: Failed to submit get_feature command 12 error: -62 [7.731691] ena :00:03.0: Cannot init indirect table [7.735636] ena :00:03.0: Cannot init RSS rc: -62 [7.740700] ena: probe of :00:03.0 failed with error -62 [...] [Fix] Reverting the following upstream stable commit fixes the issue: 83dbf898a2d4 PCI/MSI: Mask MSI-X vectors only on success [Test Case] Boot an affected AWS instance type with focal/linux (5.4.0-101.114) and impish/linux (5.13.0-31.34) kernels with the mentioned patch reverted. Then boot with the original kernels. It should boot successfully with the reverted patch but fail with the original kernels. [Regression Potential] The patch description mentions fixing a MSI-X issue with a Marvell NVME device, which doesn't seem to be following the PCI-E specification. Reverting this commit will keep the issue on systems with that particular NVME device unfixed. As of now there is no follow-up fix for this commit upstream, we might need to keep an eye on any change and re-apply it in case a fix is found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961968/+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 1961468] Re: amdgpu creates UBSAN: invalid-load in /display/amdgpu_dm/amdgpu_dm.c:6044:84
I've updated today to Linux PC1-Linux 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux and I got on boot UBSAN: invalid-load in /build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:6044:84 load of value 192 is not a valid value for type '_Bool' Have to crtl+d to go ahead booting ** Attachment added: "IMG_20220225_082917.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961468/+attachment/5563666/+files/IMG_20220225_082917.jpg -- 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/1961468 Title: amdgpu creates UBSAN: invalid-load in /display/amdgpu_dm/amdgpu_dm.c:6044:84 Status in linux package in Ubuntu: Confirmed Bug description: System works relatively stable, am mainly seeing issues when resuming from standby. But I cannot say whether it is related to this report in dmesg [4.258606] amdgpu :03:00.0: amdgpu: RAS: optional ras ta ucode is not available [4.268193] amdgpu :03:00.0: amdgpu: RAP: optional rap ta ucode is not available [4.268197] amdgpu :03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [4.268801] amdgpu :03:00.0: amdgpu: SMU is initialized successfully! [4.270242] [drm] kiq ring mec 2 pipe 1 q 0 [4.270945] [drm] Display Core initialized with v3.2.149! [4.271480] [drm] DMUB hardware initialized: version=0x0101001C [4.289069] snd_hda_intel :03:00.1: bound :03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [4.313490] input: HD-Audio Generic Mic as /devices/pci:00/:00:08.1/:03:00.6/sound/card1/input22 [4.313564] input: HD-Audio Generic Headphone as /devices/pci:00/:00:08.1/:03:00.6/sound/card1/input23 [4.313806] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [4.313809] Bluetooth: BNEP filters: protocol multicast [4.313813] Bluetooth: BNEP socket layer initialized [4.477199] [drm] VCN decode and encode initialized successfully(under DPG Mode). [4.477218] [drm] JPEG decode initialized successfully. [4.478487] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [4.512435] memmap_init_zone_device initialised 524288 pages in 4ms [4.512440] amdgpu: HMM registered 2048MB device memory [4.512477] amdgpu: SRAT table not found [4.512478] amdgpu: Virtual CRAT table created for GPU [4.513372] amdgpu: Topology: Add dGPU node [0x1638:0x1002] [4.513380] kfd kfd: amdgpu: added device 1002:1638 [4.513507] amdgpu :03:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 18, active_cu_number 28 [4.515763] [drm] fb mappable at 0x3B0CD3000 [4.515766] [drm] vram apper at 0x3B000 [4.515767] [drm] size 8294400 [4.515768] [drm] fb depth is 24 [4.515768] [drm]pitch is 7680 [4.515870] fbcon: amdgpudrmfb (fb0) is primary device [4.515945] [4.515945] UBSAN: invalid-load in /build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:6044:84 [4.515947] load of value 192 is not a valid value for type '_Bool' [4.515948] CPU: 0 PID: 497 Comm: systemd-udevd Not tainted 5.15.0-18-generic #18-Ubuntu [4.515950] Hardware name: LENOVO 82N7/LNVNB161216, BIOS H9CN25WW 11/12/2021 [4.515951] Call Trace: [4.515952] [4.515954] show_stack+0x52/0x58 [4.515959] dump_stack_lvl+0x4a/0x5f [4.515963] dump_stack+0x10/0x12 [4.515964] ubsan_epilogue+0x9/0x45 [4.515965] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [4.515967] create_stream_for_sink.cold+0x5d/0xbb [amdgpu] [4.516166] create_validate_stream_for_sink+0x59/0x150 [amdgpu] [4.516346] dm_update_crtc_state+0x235/0x7b0 [amdgpu] [4.516517] amdgpu_dm_atomic_check+0x596/0xcd0 [amdgpu] [4.516721] ? ww_mutex_lock+0x83/0x90 [4.516730] ? dm_plane_format_mod_supported+0x1f/0x100 [amdgpu] [4.516939] ? drm_plane_check_pixel_format+0x45/0x90 [drm] [4.516966] ? drm_atomic_plane_check+0x12f/0x360 [drm] [4.516982] drm_atomic_check_only+0x253/0x4b0 [drm] [4.516998] drm_atomic_commit+0x18/0x50 [drm] [4.517012] drm_client_modeset_commit_atomic+0x1df/0x220 [drm] [4.517029] drm_client_modeset_commit_locked+0x5b/0x160 [drm] [4.517044] ? mutex_lock+0x13/0x40 [4.517048] drm_client_modeset_commit+0x27/0x50 [drm] [4.517066] __drm_fb_helper_restore_fbdev_mode_unlocked+0xc2/0xf0 [drm_kms_helper] [4.517082] drm_fb_helper_set_par+0x40/0x60 [drm_kms_helper] [4.517095] fbcon_init+0x2bf/0x650 [4.517099] visual_init+0xf1/0x180 [4.517102] do_bind_con_driver.isra.0+0x1f9/0x370 [4.517104] do_take_over_console+0x3b/0x50 [
