[Kernel-packages] [Bug 1117804] Re: ausearch doesn't show AppArmor denial messages
responding to @intrigeri (sorry this got lost some how). tldr: yes we are basically on the same page. AppArmor does not fit into the 1400 range formats, every one of our messages have some custom fields. Some of them could be reformated/reworked to share more, but we would still need custom fields. Our message fields are in the common name=value format. So in that sense they do fit in. Kernel side this is fairly easy, we use common lsm_audit for the messages we share in common, the code provides a callback to add your own fields. Basically all that is needed is patch to allow different number ranges to be used. Userspace there needs to be some patching so LSM specific fields are known about. Whether is best to allocate new fields in a single number (say 1500), with no fixed number of fields to output or it better to split into a range of based on message type, I am not picky. When 1500 was taken away from us I think it was 1500-1505 that we used, but expect we wouldn't use the same mappings today if we had a choice. so we have the generic audit type that is carried { audit, allowed, denied, killed, prompt, hint, status, error } this could carried as a common field, or we could use an allocated block for we have rule class, which is another way things are broken down, its things like { file, cap, network, dbus, ...} there are currently about 25 of them currently. common fields that can occur within apparmor messages { operation, info, error, namespace, profile, label }, some fields aren't output if not needed. Eg. we are auditing an access to say /etc/shadow that is allowed but we want an audit trail for error won't be output, if its a system status message that is not generated by a profiles rule set, profile= won't be used. This set does not lend itself to an audit range as they each take on basically a string value. Then within a given class there are set of fields, some of them are shared by several classes, but not all, and there are some that are only used by a single class. Some examples would be, most mediation class share requested= and denied= the values are class depended even those may be shared by a subset of classes. -- 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/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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 2042877] Re: kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
[Expired for linux-signed-hwe-6.2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042877 Title: kernel: r8169 :0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). Status in linux-signed-hwe-6.2 package in Ubuntu: Expired Bug description: I tried everything. Manually installed the latest kernel, no luck. Updated the driver, also no luck. Here is my lshw output: id: network description: Ethernet interface product: RTL8125 2.5GbE Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:0d:00.0 logical name: enp13s0 version: 05 serial: XXX size: 1Gbit/s capacity: 1Gbit/s width:64 bits clock:33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation = on broadcast = yes driver= r8169 driverversion = 6.2.0-36-generic duplex= full firmware = rtl8125b-2_0.0.2 07/13/20 ip= 192.168.0.228 latency = 0 link = yes multicast = yes port = twisted pair speed = 1Gbit/s resources: irq : 34 ioport: f000(size=256) memory: fc70-fc70 memory: fc71-fc713fff ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 6 22:37:44 2023 InstallationDate: Installed on 2023-06-01 (158 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2042877/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
Robie, good idea, I've added a note about pptpd and bcrelay being removed, with a link back here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751 Thanks -- 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/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I'm getting the same results as Max Power. My `dpkg --list` output shows that I have version 20220329.git681281e4-0ubuntu3.28 of linux-firmware installed. After rebooting, the dmesg logs from mt7921e show the same build times as before---not the expected new build times. My wireless card seems to be behaving the same as before. As far as I know, I restored /lib/firmware to its original state (before I ever touched its contents) before upgrading linux-firmware. The files in /lib/firmware/mediatek all show the same modification time: Feb 9 09:26 (presumably in my time zone, New York City). I've attached the output of `tree /lib/firmware`, as Mario Limonciello suggested. ** Attachment added: "The output of `tree /lib/firmware`" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+attachment/5745520/+files/firmware-tree -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 1117804] Re: ausearch doesn't show AppArmor denial messages
As far as I know, no one has made an effort to try to improve the situation lately. There's some discussion at https://lists.ubuntu.com/archives/apparmor/2024-February/013091.html that may be enlightening, if not encouraging. Thanks -- 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/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
This bug is awaiting verification that the linux-gcp/5.15.0-1052.60 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-gcp' to 'verification-done-jammy- linux-gcp'. If the problem still exists, change the tag 'verification- needed-jammy-linux-gcp' to 'verification-failed-jammy-linux-gcp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-gcp-v2 verification-needed-jammy-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
If those patches are all in 6.7 mainline, then yes, they are already included for 24.04. There is a 6.7 kernel in noble-proposed for 24.04 that could technically be installed now. And thanks for the new bug. We added that to the stuff to work on this next cycle (The next two weeks) -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Did you put any other files in /lib/firmware? Maybe the output of $tree /lib/firmware Would explain what is going on. -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
It happen again in second boot for `20230919.git3672ccab-0ubuntu2.1` *ERROR* hw_init of IP block failed -62 -- 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/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
I just tried `20230919.git3672ccab-0ubuntu2.1` which resolve the issue? (idk yet but the system boot from first try) -- 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/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
I just downgraded to 20230323.gitbcdcfbcf-0ubuntu1.2 and received different error message that resolve SMU issue but still cannot boot because system freeze after ``` [5.165679] kernel: [drm] try to fall back to amdgpu/gc_11_0_0_mes.bin ``` ** Attachment added: "dmesg.1.gz" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+attachment/5745482/+files/dmesg.1.gz -- 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/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2052662] Re: move_mount mediation does not detect if source is detached
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052662 Title: move_mount mediation does not detect if source is detached Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Bug description: Impact: In AppArmor mediation, detached mounts are appearing as / when applying mount mediation, which is incorrect and leads to bad AppArmor policy being generated. In addition, the move_mount mediation is not being advertised to userspace, which denies the applications the possibility to respond accordingly. Fix: Fixed upstream by commit 8026e40608b4d552216d2a818ca7080a4264bb44 by preventing move_mont from applying the attach_disconnected flag. Testcase: Check if move_mount file is available in securityfs: $ cat /sys/kernel/security/apparmor/features/mount/move_mount detached Run upstream AppArmor mount tests, which include move_mount mediation. https://gitlab.com/apparmor/apparmor/-/blob/master/tests/regression/apparmor/mount.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052662/+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 2052842] [NEW] Regression in partition table management in kernel 5.15.0-94.104
Public bug reported: There is a regression in partition table management in the latest jammy kernel which can be reproduced with this simple script: fallocate -l 32M /tmp/blob LOOPDEV=$(losetup -f) sudo losetup $LOOPDEV /tmp/blob sudo /usr/sbin/parted -s -m $LOOPDEV -- "mklabel gpt" Expected result: Partition table is created successfully, exit code is 0, no output. Actual result: Partition table is created successfully, but exit code is 1 and output is: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/loop3 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Packaging information: Description:Ubuntu 22.04.3 LTS Release:22.04 Affected kernel version: Ubuntu 5.15.0-94.104-generic 5.15.136 Last working kernel version: Ubuntu 5.15.0-92.102-generic 5.15.131 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2052842/+attachment/5745481/+files/lspci-vnvn.log ** Summary changed: - Regression in partition table management + Regression in partition table management in kernel 5.15.0-94.104 ** Description changed: There is a regression in partition table management in the latest jammy kernel which can be reproduced with this simple script: fallocate -l 32M /tmp/blob LOOPDEV=$(losetup -f) sudo losetup $LOOPDEV /tmp/blob sudo /usr/sbin/parted -s -m $LOOPDEV -- "mklabel gpt" Expected result: - No output, partition table gets created successfully. + Partition table is created successfully, exit code is 0, no output. Actual result: + + Partition table is created successfully, but exit code is 1 and output + is: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/loop3 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Packaging information: Description: Ubuntu 22.04.3 LTS Release: 22.04 Affected kernel version: Ubuntu 5.15.0-94.104-generic 5.15.136 Last working kernel version: Ubuntu 5.15.0-92.102-generic 5.15.131 -- 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/2052842 Title: Regression in partition table management in kernel 5.15.0-94.104 Status in linux package in Ubuntu: New Bug description: There is a regression in partition table management in the latest jammy kernel which can be reproduced with this simple script: fallocate -l 32M /tmp/blob LOOPDEV=$(losetup -f) sudo losetup $LOOPDEV /tmp/blob sudo /usr/sbin/parted -s -m $LOOPDEV -- "mklabel gpt" Expected result: Partition table is created successfully, exit code is 0, no output. Actual result: Partition table is created successfully, but exit code is 1 and output is: Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/loop3 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes. Packaging infor
[Kernel-packages] [Bug 2052840] Re: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
Screenshot of the error in the logs ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+attachment/5745480/+files/screenshot -- 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/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2052840] [NEW] Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62
Public bug reported: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: mantic ** Attachment added: "dmesg logs" https://bugs.launchpad.net/bugs/2052840/+attachment/5745479/+files/dmesg.1.gz -- 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/2052840 Title: Cannot boot with RX 7900 XTX: *ERROR* hw_init of IP block failed -62 Status in linux-firmware package in Ubuntu: New Bug description: Hello, I'm facing this issue before few months after software upgrade, Distro: Kubuntu 23.10 Kernel: Linux kernel 6.5.0-17-generic Linux Firmware: 20230919.git3672ccab-0ubuntu2.5 My Specs: CPU: Ryzen 9 7950X RAM: 64GB = 16GB × 4 5200/MT DDR5 GPU: Radeon RX 7900 XTX (Founder Edition from Sapphire) Motherboard: Gigabyte B650M GAMING X AX NOTICE: I can boot after 10-20 tries and sometimes I cannot boot at all there other users faced same issue (look like because linux-firmware): https://ubuntuforums.org/showthread.php?t=2489556 My dmesg logs attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2052840/+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 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)
okay installed kernel 6.8.0-7 from noble-proposed and bluetooth issue is gone with this version.. no drops so this appears fixed ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038539 Title: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC) Status in linux package in Ubuntu: Fix Released Bug description: Seems some random network activity regularly breaks bluetooth connections.. headphones connect and reconnect or suffer breaks in sound etc. Started with this kernel version linux-image-6.5.0-7 .. previous kernel linux-image-6.5.0-5 works perfectly Booting into the older kernel restores bluetooth stability. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-7-generic 6.5.0-7.7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1690 F wireplumber /dev/snd/controlC0: derk 1690 F wireplumber /dev/snd/seq:derk 1687 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Oct 5 08:33:01 2023 InstallationDate: Installed on 2023-10-04 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8: dmi.product.family: IdeaPad Slim 5 16ABR8 dmi.product.name: 82XG dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8 dmi.product.version: IdeaPad Slim 5 16ABR8 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: derk 1691 F wireplumber /dev/snd/controlC0: derk 1691 F wireplumber /dev/snd/seq:derk 1688 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-10-04 (12 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux (not installed) ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9-generic N/A linux-backports-modules-6.5.0-9-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2.1 Tags: mantic Uname: Linux 6.5.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/13/2023 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: L9CN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 5 16ABR8 dmi.ec.firmware.release:
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
That might be the case, from my previous attempts to manually update it. Could you tell me how to remove them, without breaking anything? I'd really appreciate it. -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I'm glad to hear you are seeing an improvement! The current implementation is still racy as mentioned in Comment #22. I did a search of the logs I downloaded, and I believe this one shows that the mount_partition() race isn't just theoretical: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/l/livecd-rootfs/20230928_132941_a6800@/log.gz So my suggestion is that we: 1) wait for systemd 255.3 to be merged in noble to fix the issue w/ `udevadm lock` 2) convert livecd-rootfs to use udevadm lock in noble, addressing the remaining known races. 3) backport `udevadm lock` to jammy (likely as a low-priority SRU) 4) backport the`udevadm lock` support to livecd-rootfs I realize that'll take some time, so if you want to SRU the partial fix as a stop-gap, feel free. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2052835] [NEW] Error running program on cifs filesystem
Public bug reported: Hi When I try and run a shell script which is on a cifs mounted system I get an error. This is on a 22.04 system - Linux bicr-compression 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux nkhan@bicr-compression:/mnt/cephfs/home/users/nkhan$ ~/data/NKHAN/linux-home/date.sh bash: /nfs/home/users/nkhan/data/NKHAN/linux-home/date.sh: /usr/bin/bash: bad interpreter: Input/output error In the kernel log there is: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014745] [ cut here ] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014761] WARNING: CPU: 16 PID: 5834 at fs/smb/client/file.c:3341 cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014849] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 nfsv3 nfs_acl nfs lockd grace fscache netfs vsock_loopback vmw_vsock_virtio_transport_common intel_rapl_msr vmw_vsock_vmci_transport intel_rapl_common vsock intel_uncore_frequency_common binfmt_misc coretemp rapl nls_iso8859_1 vmw_balloon input_leds joydev serio_raw vmw_vmci mac_hid sch_fq_codel msr parport_pc auth_rpcgss ppdev lp parport efi_pstore sunrpc ip_tables x_tables autofs4 vmwgfx crct10dif_pclmul drm_ttm_helper crc32_pclmul polyval_clmulni ttm polyval_generic ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd mptspi mptscsih cryptd mptbase ahci drm psmouse libahci vmxnet3 scsi_transport_spi i2c_piix4 pata_acpi Feb 9 20:10:01 bicr-compression kernel: [ 1421.014910] CPU: 16 PID: 5834 Comm: bash Tainted: GW 6.5.0-17-generic #17~22.04.1-Ubuntu Feb 9 20:10:01 bicr-compression kernel: [ 1421.014914] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014916] RIP: 0010:cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014969] Code: c0 48 29 c2 75 c4 41 89 0b 4c 89 c0 48 8b 5d f8 c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db c3 cc cc cc cc <0f> 0b 45 31 c0 4c 89 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014971] RSP: 0018:b4ee07117b90 EFLAGS: 00010297 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014974] RAX: 9de487836418 RBX: 9de4878363c0 RCX: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014975] RDX: b4ee07117bdc RSI: 0100 RDI: 9de487836418 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014977] RBP: b4ee07117c18 R08: 0100 R09: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014978] R10: R11: R12: 9de48f998000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014979] R13: 9de48f982400 R14: 0100 R15: 9de49ba32000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014981] FS: 7f8f2ae67740() GS:9dfb5e20() knlGS: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014982] CS: 0010 DS: ES: CR0: 80050033 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014984] CR2: 558a1cb1bf98 CR3: 0001abfd4001 CR4: 003706e0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015030] DR0: DR1: DR2: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015033] DR3: DR6: fffe0ff0 DR7: 0400 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015034] Call Trace: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015036] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015040] ? show_regs+0x6d/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015116] ? __warn+0x89/0x160 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015127] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015181] ? report_bug+0x17e/0x1b0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015198] ? handle_bug+0x46/0x90 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015212] ? exc_invalid_op+0x18/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015215] ? asm_exc_invalid_op+0x1b/0x20 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015226] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015277] ? cifs_send_async_read+0x11f/0x510 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015330] __cifs_readv+0x271/0x480 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015383] cifs_strict_readv+0x173/0x180 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015436] __kernel_read+0x132/0x2f0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015449] kernel_read+0x58/0xb0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015451] search_binary_handler+0x75/0x260 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015458] exec_binp
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Do you perhaps have the older version in /lib/firmware/updates? -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I enabled jammy-proposed and installed the firmware update, but unfortunately the update still didn’t load as indicated by the build times. I tried re-installing, but got this output linux-firmware is already the newest version (20220329.git681281e4-0ubuntu3.28). Selected version '20220329.git681281e4-0ubuntu3.28' (Ubuntu:22.04/jammy-proposed [all]) for 'linux-firmware' I don’t really understand, why I still don’t have the updated firmware. Does anyone here have an idea or can try installing the firmware update via jammy-proposed themselves? -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Rudi Daemen, thanks for the procedure! I just tried it, and the new firmware still isn't running. That's not surprising, because your procedure seems functionally identical to the one I described on Ask Ubuntu, except that it updates all installed kernels instead of just the latest one (which is the one I'm running). I'd love to know why this procedure isn't behaving as expected for me, but maybe it doesn't matter anymore, since the fix is available in jammy-proposed now. I'll try to install it from jammy-proposed and report back. -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
Hi Jeff, We have created one more BZ for similar patches for our other storage controller (mpt3sas). Which are very important. So Could you please look into it. Below is the BZ link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046875 -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
Thank you, Jeff. These patches are very important so if you need any support from our end please let us know. Btw, when will this point kernel be released? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046722 Title: [22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
Hi Jeff, These patches are available in the 6.7 mainline kernel. does it mean the patches are already included? -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I have manually downloaded and installed the updated package and can confirm the new package contains the correct firmware and the issue is resolved now. IPv6 Multicast is working and IPv6 address autoconfiguration is working as expected. Some output: fludizz@pauwel:~$ dpkg --list | grep linux-firmware ii linux-firmware 20220329.git681281e4-0ubuntu3.28 all Firmware for Linux kernel drivers fludizz@pauwel:~$ sudo dmesg | grep mt7921e [8.912585] mt7921e :05:00.0: enabling device ( -> 0002) [8.918209] mt7921e :05:00.0: ASIC revision: 79610010 [9.53] mt7921e :05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a [9.012216] mt7921e :05:00.0: WM Firmware Version: 01, Build Time: 20231109190959 [9.846373] mt7921e :05:00.0 wlp5s0: renamed from wlan0 fludizz@pauwel:~$ ip -6 addr show 1: lo: mtu 65536 state UNKNOWN qlen 1000 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: wlp5s0: mtu 1500 state UP qlen 1000 inet6 2a10:3781:3fbd:::::/64 scope global temporary dynamic valid_lft 86395sec preferred_lft 14395sec inet6 2a10:3781:3fbd:::::/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 86395sec preferred_lft 14395sec inet6 fe80:::::/64 scope link noprefixroute valid_lft forever preferred_lft forever fludizz@pauwel:~$ ip -6 route | grep ra 2a10:3781:3fbd::/64 dev wlp5s0 proto ra metric 600 pref medium default via fe80::::: dev wlp5s0 proto ra metric 600 pref medium -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2052827] [NEW] performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- 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/2052827 Title: performance: mm/memcontrol.c: remove the redundant updating of stats_flush_threshold Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034981 Backport upstream commit: 873f64b791a2 mm/memcontrol.c: remove the redundant updating of stats_flush_threshold to jammy. [Impact] Remove the redundant updating of stats_flush_threshold. If the global var stats_flush_threshold has exceeded the trigger value for __mem_cgroup_flush_stats, further increment is unnecessary. This is targeting Sapphire Rapids platforms. [Fix] Upstream commit 873f64b791a2 fixes this issue. The fix involves not updating the status after a certain threshold has been hit as it is unnecessary. [Test Plan] I have tested the changes, and hit no regressions. [Where problems could occur] As the change has been upstream since 6.0-rc1, and is reducing a stats update which isn't needed, the change for regressions should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052827/+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 2052817] Re: cpufreq: intel_pstate: Enable HWP IO boost for all servers
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- 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/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+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 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Jammy) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2034103 Title: Missing firmware for AMD GPU GC 11.0.3 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux-firmware source package in Lunar: Won't Fix Bug description: [Impact] linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for Navi32 hardware. Of the original list below, only VCN fw update is missing still. [Test case] Install the update Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. [Where problems could happen] This is new hw, where the current fw isn't fresh enough. It can't regress other hw. -- Add new FWs for GPU with GC 11.0.3: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21 ("amdgpu: add initial GC 11.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c ("amdgpu: add initial PSP 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f ("amdgpu: add initial SDMA 6.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897 ("amdgpu: add initial SMU 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c ("amdgpu: update VCN 4.0.0 firmware") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034103/+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 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
We will work on these this next week and shoot for the next SRU for 6.5. -- 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/2046722 Title: [22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
Additionally, this says 24.04... is that the correct target? Your email to me says otherwise. -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
24.04 only recently rolled the kernel tree to 6.7, and we are planning on 6.8. Where are these upstream currently? If they are in 6.8 there is nothing to do here until we roll the kernel tree to 6.8 later this cycle. Can you tell me which mainline version these exist in currently? -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2048853] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2048853 Title: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Triaged Bug description: [SRU Justification] [Impact] Within stress reboot tests, iwlwifi may fail to load firmware, triggers retries, and finally makes wifi operative. iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL iwlwifi :05:00.0: 0x02F0 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C27F2 | branchlink2 iwlwifi :05:00.0: 0x002B79AE | interruptlink1 .. iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0 iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0 iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0 iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0 iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0 iwlwifi :05:00.0: Function Scratch status: iwlwifi :05:00.0: 0x01010101 | Func Scratch iwlwifi :05:00.0: Failed to start RT ucode: -110 iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fix] Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for core80-165 release"). While the iwlwifi firmware updates come with a sequential manner, it pulls a few more: * 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic * a07fd0b96 ("iwlwifi: add new FWs from core83-55 release") * f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release") These contain firmware blob for ucore 84/86, and are not used by kernels < v6.7. [Test Case] Use checkbox reboot stress test case to observe iwlwifi dmesg logs: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] Opaque firmware update. No known issue found yet after the update. [Other Info] This affects series with kernels that load iwlwifi ucode 83 firmware, namely Noble, Mantic, and for oem-6.5, Jammy. == original bug report == Within stress reboot tests, iwlwifi may fail to load firmware and triggers retry, and finally makes wifi operative. Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0 gl-c0-fm-c0-83.ucode Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 | trm_hw_status0 Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x | trm_hw_status1 Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2 Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE | interruptlink1 .. Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0 Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0 Oct 12 0
[Kernel-packages] [Bug 2048977] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2048977 Title: WCN6856 Wi-FI Unavailable and no function during suspend stress Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2048977 [Impact] Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 'hot reset' assert 2nd PCIe reset' assert Asmedia 'hot reset' deassert PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. [Fix] Upstream commits: 5217b76bed90 ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37") 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin") And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0: update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git history dependency. And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble has not yet accept the PR for bug 2042534, it has no such problem at this moment. [Test Case] This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Opaque firmware update. No known issue found yet after the update. [Other Info] This affects all series with WCN6855/WCN6856 support, Noble/Mantic and Jammy for oem-6.5 included. == original bug report == Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 1. 'hot reset' assert 2. 2nd PCIe reset' assert 3. Asmedia 'hot reset' deassert 4. PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated The proposed fixes are: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199 - This FW include this LP ticket issue fix * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe - The FW is to support new China regulatory support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
should be in noble via the latest upstream rebase ** Changed in: linux-firmware (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2048977 Title: WCN6856 Wi-FI Unavailable and no function during suspend stress Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2048977 [Impact] Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 'hot reset' assert 2nd PCIe reset' assert Asmedia 'hot reset' deassert PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. [Fix] Upstream commits: 5217b76bed90 ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37") 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin") And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0: update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git history dependency. And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble has not yet accept the PR for bug 2042534, it has no such problem at this moment. [Test Case] This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Opaque firmware update. No known issue found yet after the update. [Other Info] This affects all series with WCN6855/WCN6856 support, Noble/Mantic and Jammy for oem-6.5 included. == original bug report == Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 1. 'hot reset' assert 2. 2nd PCIe reset' assert 3. Asmedia 'hot reset' deassert 4. PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated The proposed fixes are: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199 - This FW include this LP ticket issue fix * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe - The FW is to support new China regulatory support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048977] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2048977 Title: WCN6856 Wi-FI Unavailable and no function during suspend stress Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2048977 [Impact] Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 'hot reset' assert 2nd PCIe reset' assert Asmedia 'hot reset' deassert PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. [Fix] Upstream commits: 5217b76bed90 ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37") 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin") And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0: update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git history dependency. And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble has not yet accept the PR for bug 2042534, it has no such problem at this moment. [Test Case] This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Opaque firmware update. No known issue found yet after the update. [Other Info] This affects all series with WCN6855/WCN6856 support, Noble/Mantic and Jammy for oem-6.5 included. == original bug report == Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 1. 'hot reset' assert 2. 2nd PCIe reset' assert 3. Asmedia 'hot reset' deassert 4. PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated The proposed fixes are: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199 - This FW include this LP ticket issue fix * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe - The FW is to support new China regulatory support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2049220] Please test proposed package
Hello Ciaby, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Hello Ciaby, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049758] Please test proposed package
Hello Anson, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2049758] Please test proposed package
Hello Anson, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
or maybe we'll just submit it there too.. ** Changed in: linux-firmware (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
how is this supposed to be verified in mantic, if it won't get the kernel changes? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2051636] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.28 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2051636 Title: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker [Fix] Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and other prerequisites: * amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1 firmware") * amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4 firmware") * amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2 firmware") * amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4 firmware") * amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11 firmware") [Test Case] Run stress tool like 3DMark or GravityMark. [Where problems could occur] Binary firmware update recommended by chip vendor. No known issue so far. [Other Info] Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy is also nominated for fix. == original bug report == With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker. Also using mantic + v6.7 hit the hang, so need to update new FWs to fix this issue. PHX series https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85 [ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=27035, emitted seq=27037 [ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421 [ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin! [ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.464226] [dr
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2051636 Title: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker [Fix] Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and other prerequisites: * amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1 firmware") * amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4 firmware") * amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2 firmware") * amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4 firmware") * amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11 firmware") [Test Case] Run stress tool like 3DMark or GravityMark. [Where problems could occur] Binary firmware update recommended by chip vendor. No known issue so far. [Other Info] Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy is also nominated for fix. == original bug report == With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker. Also using mantic + v6.7 hit the hang, so need to update new FWs to fix this issue. PHX series https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85 [ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=27035, emitted seq=27037 [ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421 [ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin! [ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_compl
[Kernel-packages] [Bug 2052817] [NEW] cpufreq: intel_pstate: Enable HWP IO boost for all servers
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Description changed: + + This is a public version of https://bugs.launchpad.net/bugs/2009321 + Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. - [Impact] - - Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. + Currently there is a CPU model check for Skylake desktop and server + along with the ACPI PM profile for performance and enterprise servers to + enable IO boost. Patch removes the CPU model check, so that all current + server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ - [Fix] Upstream patch: - cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 + cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. - [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. -- 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/2052817 Title: cpufreq: intel_pstate: Enable HWP IO boost for all servers Status in linux package in Ubuntu: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2009321 Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers [upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to jammy. [Impact] Currently there is a CPU model check for Skylake desktop and server along with the ACPI PM profile for performance and enterprise servers to enable IO boost. Patch removes the CPU model check, so that all current server models enable HWP IO boost by default. The HWP IO boost results in improvements for IO performance on both Ice Lake and Sapphire Rapid servers. Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf- Boost Upstream review Link: https://lore.kernel.org/linux- pm/20230303041411.3161780-1-srinivas.pandruv...@linux.intel.com/ [Fix] Upstream patch: cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 was merged to fix this. This will be back porting it to jammy. [Test Plan] I have tested this code, as has Intel. [Where problems could occur] The risk for regression is low. The change is fairly narrow, and has been upstreamed for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+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 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
Patch sent to the kernel team mailing list for review: https://lists.ubuntu.com/archives/kernel-team/2024-January/148256.html ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- 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/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: In Progress Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+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 2038587] Re: Turning COMPAT_32BIT_TIME off on ppc64el
Confirmed the fix has been applied to 24.04 Noble linux 6.8 repository: "UBUNTU: [Config] y2038: Disable COMPAT and COMPAT_32BIT_TIME on ppc64le" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=master- next&id=e1075f183b5fef4b05abf515fa1b4e1d26057e5a As soon as the kernel is promoted to the noble-release pocket the bug report will be updated automatically. -- 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/2038587 Title: Turning COMPAT_32BIT_TIME off on ppc64el Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: This will prevent existing 32-bit powerpcle binaries to operate correctly, if they are still using 32bit time. And even exists? 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2038587/+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 2042853] Re: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough
Confirmed the fix has been applied to 24.04 Noble linux 6.8 repository: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/?h=master- next&id=3842f676a88b7c4b2063987beaae37f80505d841 As soon as the kernel is promoted to the noble-release pocket the bug report will be updated automatically. -- 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/2042853 Title: [UBUNTU 23.04] Kernel config option missing for s390x PCI passthrough Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] * Today no s390x-specific vfio-pci devices (zPCI) can be passed from a KVM host to a KVM guest (incl. secure execution guests in the context of confidential computing). * s390x PCI passthrough needs various changes in the s390x kernel zPCI code (incl. the new s390x-specific Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM') that were introduced with kernel 6.0 and got backported to 22.04/jammy as part of LP: #1853306. * Lunar an newer Ubuntu releases have the code already included from upstream (incl. the Kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'), but the config option is not set, hence zPCI pass-through is still not possible. [Fix] * To be able to make use of VFIO zPCI pass-through on s390x running newer Ubuntu releases (especially needed in the context of secure execution) the (s390x-specific) Kernel config option 'CONFIG_VFIO_PCI_ZDEV_KVM' needs to be enabled and set to 'y'. [Test Case] * Hardware used: z14 or greater LPAR, PCI-attached devices (RoCE VFs, ISM devices, NVMe drive) * Setup: Both the kernel and QEMU features are needed for the feature to function (an upstream QEMU can be used to verify the kernel early), and the facility is only available on z14 or newer. When any of those pieces is missing, the interpretation facility will not be used. When both the kernel and QEMU features are included in their respective packages, and running in an LPAR on a z14 or newer machine, this feature will be enabled automatically. Existing supported devices should behave as before with no changes required by an end-user (e.g. no changes to libvirt domain definitions) -- but will now make use of the interpretation facility. Additionally, ISM devices will now be eligible for vfio-pci passthrough (where before QEMU would exit on error if attempting to provide an ISM device for vfio-pci passthrough, preventing the guest from starting) * Testing will include the following scenarios, repeated each for RoCE, ISM and NVMe: 1) Testing of basic device passthrough (create a VM with a vfio-pci device as part of the libvirt domain definition, passing through a RoCE VF, an ISM device, or an NVMe drive. Verify that the device is available in the guest and functioning) 2) Testing of device hotplug/unplug (create a VM with a vfio-pci device, virsh detach-device to remove the device from the running guest, verify the device is removed from the guest, then virsh attach-device to hotplug the device to the guest again, verify the device functions in the guest) 3) Host power off testing: Power off the device from the host, verify that the device is unplugged from the guest as part of the poweroff 4) Guest power off testing: Power off the device from within the guest, verify that the device is unusable in the guest, power the device back on within the guest and verify that the device is once again usable. 5) Guest reboot testing: (create a VM with a vfio-pci device, verify the device is in working condition, reboot the guest, verify that the device is still usable after reboot) [Regression Potential] * The regression potential is moderate, since the code is upstream for quite a while and already enabled in jammy. * The general way on using passthrough has not changed, with this change (config option) it's now just possible to passthrough zPCI on top. * CCW devices are not affected. * And this is s390x-specific anyway, so no other architectures are affected. [Other] * The enabling of the kernel config option is exactly the same for L, M and U/N, but I submitted separate patches due to slightly different context and offsets. __ === Description by mjros...@us.ibm.com === LP#1853306 / IBM bug 182254 backported the necessary kernel pieces to enable enhanced interpretation of PCI passthrough on s390. It also i
[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
Same problem here, (Lenovo ideapad Flex 5 -14ARE05, Ubuntu 22.04.3 LTS), although it did work JUST ONCE, randomly, in ~two years of ownership, about a couple of months ago. The "i8042.nopnp=1 pci=nocrs" solution broke my wifi (?) and didn't fix the problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I've been seeing this bug as far back as losetup is used (jammy) and the previously merged fix has a significant improvement on successful builds (0/3 succeeded without the patch applied vs 5/5 succeeded with the patch applied this week) in jammy. Is someone already looking to SRU that patch back to mantic and jammy or should I work on it? Even if it's not perfectly, I think it would be extremely benefitial. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: New Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2046875] Re: [22.04.04]: mpt3sas: Critical Bug Fixes
We noticed that this commit- "4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0" is picked in ubuntu 22.04.4, but remaining patches are missing. Please pick all these patches as they are very critical. -- 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/2046875 Title: [22.04.04]: mpt3sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046875/+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 2051703] Re: Kernel 6.5.0-15-generic: HDMI Screen detected but stays black at 60 Hz on HP Notebook
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051703 Title: Kernel 6.5.0-15-generic: HDMI Screen detected but stays black at 60 Hz on HP Notebook Status in linux-hwe-6.5 package in Ubuntu: Confirmed Bug description: When booting with kernel 6.5.0-15-generic, the screen stays black, but it is properly detected since I can move the mouse to it. Moreover, if I reduce the framerate to 30Hz (it normally is at 60Hz) the screen is visible again. The HDMI screen works fine at 60 Hz using kernel 6.2.0-39. I'm running Linux Mint 21.2, based on ubuntu 22.04. I'm reporting the bug here since it really seems like a kernel issue. $ cat /proc/version_signature Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 System: Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.8.4 tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId serial: Chassis: type: 10 serial: Mobo: HP model: 81F9 v: 67.43 serial: UEFI: Insyde v: F.35 date: 05/27/2019 Battery: ID-1: BAT1 charge: 11.2 Wh (100.0%) condition: 11.2/31.1 Wh (35.9%) volts: 12.3 min: 11.1 model: Hewlett-Packard PABAS0241231 serial: status: Full CPU: Info: quad core model: AMD A10-9600P RADEON R5 10 COMPUTE CORES 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2526 high: 2585 min/max: 1200/2400 boost: enabled cores: 1: 2585 2: 2584 3: 2551 4: 2387 bogomips: 19163 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard driver: amdgpu v: kernel ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: Chicony HP TrueVision HD type: USB driver: uvcvideo bus-ID: 2-1:2 chip-ID: 04f2:b56c Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 101 diag: 394mm (15.5") OpenGL: renderer: CARRIZO (carrizo LLVM 15.0.7 DRM 3.54 6.5.0-15-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes Audio: Device-1: AMD Kabini HDMI/DP Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:9840 Device-2: AMD Family 15h Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:09.2 chip-ID: 1022:157a Device-3: GN Netcom Jabra EVOLVE LINK type: USB driver: jabra,snd-usb-audio,usbhid bus-ID: 1-1.1:3 chip-ID: 0b0e:0306 Sound Server-1: ALSA v: k6.5.0-15-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8136 IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtl8723be v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:b723 IF: wlo1 state: up mac: IF-ID-1: br-ba7391f263ca state: down mac: IF-ID-2: docker0 state: down mac: Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-1.4:5 chip-ID: 0bda:b008 Report: hciconfig ID: hci0 rfk-id: 0 state: up address: bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 Drives: Local Storage: total: 953.87 GiB used: 368.09 GiB (38.6%) ID-1: /dev/sda vendor: Lexar model: SSD NS100 1TB size: 953.87 GiB speed: 6.0 Gb/s serial: Partition: ID-1: / size: 233.62 GiB used: 66.13 GiB (28.3%) fs: ext4 dev: /dev/sda3 ID-2: /boot/efi size: 486 MiB used: 7 MiB (1.4%) fs: vfat dev: /dev/sda1 ID-3: /home size: 687.66 GiB used: 301.96 GiB (43.9%) fs: ext4 dev: /dev/sda4 Swap: ID-1: swap-1 type: partition size: 15.26 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 Sensors: System Temperatures: cpu: 52.0 C mobo: 20.0 C gpu: amdgpu temp: 51.0 C Fan Speeds (RPM): N/A Repos: Packages: 2537 apt: 2530 flatpak: 7 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/docker.list 1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https: //download.docker.com/linux/ubuntu jammy stable Active apt repos in: /etc/apt/sources.list.d/google-chrome
[Kernel-packages] [Bug 2046726] Re: [24.04 LTS]: megaraid_sas driver update
Hi Jeff and Roxana, These bugs are critical for us, and I don't see any update here. I would like to know where are we on this. will these patches be included in this point kernel? -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+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 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
Hi Jeff and Roxana, These bugs are critical for us, and I don't see any update here. I would like to know where are we on this. will these patches be included in this point kernel? -- 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/2046722 Title: [22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+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 2052792] Re: Mantic update: upstream stable patchset 2024-02-09
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Manuel Diewald (diewald) ** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-09 + + Ported from the following upstream stable releases: + v6.1.71, v6.6.10 + from git://git.kernel.org/ + + ksmbd: switch to use kmemdup_nul() helper + ksmbd: add support for read compound + ksmbd: fix wrong interim response on compound + ksmbd: fix `force create mode' and `force directory mode' + ksmbd: Fix one kernel-doc comment + ksmbd: add missing calling smb2_set_err_rsp() on error + ksmbd: remove experimental warning + ksmbd: remove unneeded mark_inode_dirty in set_info_sec() + ksmbd: fix passing freed memory 'aux_payload_buf' + ksmbd: return invalid parameter error response if smb2 request is invalid + ksmbd: check iov vector index in ksmbd_conn_write() + ksmbd: fix race condition with fp + ksmbd: fix race condition from parallel smb2 logoff requests + ksmbd: fix race condition between tree conn lookup and disconnect + ksmbd: fix wrong error response status by using set_smb2_rsp_status() + ksmbd: fix Null pointer dereferences in ksmbd_update_fstate() + ksmbd: fix potential double free on smb2_read_pipe() error path + ksmbd: Remove unused field in ksmbd_user struct + ksmbd: reorganize ksmbd_iov_pin_rsp() + ksmbd: fix kernel-doc comment of ksmbd_vfs_setxattr() + ksmbd: fix missing RDMA-capable flag for IPoIB device in ksmbd_rdma_capable_netdev() + ksmbd: add support for surrogate pair conversion + ksmbd: no need to wait for binded connection termination at logoff + ksmbd: fix kernel-doc comment of ksmbd_vfs_kern_path_locked() + ksmbd: prevent memory leak on error return + ksmbd: separately allocate ci per dentry + ksmbd: move oplock handling after unlock parent dir + ksmbd: release interim response after sending status pending response + ksmbd: move setting SMB2_FLAGS_ASYNC_COMMAND and AsyncId + ksmbd: don't update ->op_state as OPLOCK_STATE_NONE on error + ksmbd: set epoch in create context v2 lease + ksmbd: set v2 lease capability + ksmbd: downgrade RWH lease caching state to RH for directory + ksmbd: send v2 lease break notification for directory + ksmbd: lazy v2 lease break on smb2_write() + ksmbd: avoid duplicate opinfo_put() call on error of smb21_lease_break_ack() + ksmbd: fix wrong allocation size update in smb2_open() + linux/export: Ensure natural alignment of kcrctab array + block: renumber QUEUE_FLAG_HW_WC + ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16() + platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe + mm/filemap: avoid buffered read/write race to read inconsistent data + mm: migrate high-order folios in swap cache correctly + mm/memory-failure: cast index to loff_t before shifting it + mm/memory-failure: check the mapcount of the precise page + ring-buffer: Fix wake ups when buffer_percent is set to 100 + tracing: Fix blocked reader of snapshot buffer + NFSD: fix possible oops when nfsd/pool_stats is closed. + Revert "platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe" + fs: cifs: Fix atime update check + linux/export: Fix alignment for 64-bit ksymtab entries + mptcp: refactor sndbuf auto-tuning + mptcp: fix possible NULL pointer dereference on close + mptcp: fix inconsistent state on fastopen race + platform/x86/intel/pmc: Add suspend callback + platform/x86/intel/pmc: Allow reenabling LTRs + platform/x86/intel/pmc: Move GBE LTR ignore to suspend callback + selftests: secretmem: floor the memory size to the multiple of page_size + Revert "nvme-fc: fix race between error recovery and creating association" + ftrace: Fix modification of direct_function hash while in use + UBUNTU: Upstream stable to v6.1.71, v6.6.10 -- 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/2052792 Title: Mantic update: upstream stable patchset 2024-02-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: 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 fi
[Kernel-packages] [Bug 2052792] [NEW] Mantic update: upstream stable patchset 2024-02-09
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-02-09 Ported from the following upstream stable releases: v6.1.71, v6.6.10 from git://git.kernel.org/ ksmbd: switch to use kmemdup_nul() helper ksmbd: add support for read compound ksmbd: fix wrong interim response on compound ksmbd: fix `force create mode' and `force directory mode' ksmbd: Fix one kernel-doc comment ksmbd: add missing calling smb2_set_err_rsp() on error ksmbd: remove experimental warning ksmbd: remove unneeded mark_inode_dirty in set_info_sec() ksmbd: fix passing freed memory 'aux_payload_buf' ksmbd: return invalid parameter error response if smb2 request is invalid ksmbd: check iov vector index in ksmbd_conn_write() ksmbd: fix race condition with fp ksmbd: fix race condition from parallel smb2 logoff requests ksmbd: fix race condition between tree conn lookup and disconnect ksmbd: fix wrong error response status by using set_smb2_rsp_status() ksmbd: fix Null pointer dereferences in ksmbd_update_fstate() ksmbd: fix potential double free on smb2_read_pipe() error path ksmbd: Remove unused field in ksmbd_user struct ksmbd: reorganize ksmbd_iov_pin_rsp() ksmbd: fix kernel-doc comment of ksmbd_vfs_setxattr() ksmbd: fix missing RDMA-capable flag for IPoIB device in ksmbd_rdma_capable_netdev() ksmbd: add support for surrogate pair conversion ksmbd: no need to wait for binded connection termination at logoff ksmbd: fix kernel-doc comment of ksmbd_vfs_kern_path_locked() ksmbd: prevent memory leak on error return ksmbd: separately allocate ci per dentry ksmbd: move oplock handling after unlock parent dir ksmbd: release interim response after sending status pending response ksmbd: move setting SMB2_FLAGS_ASYNC_COMMAND and AsyncId ksmbd: don't update ->op_state as OPLOCK_STATE_NONE on error ksmbd: set epoch in create context v2 lease ksmbd: set v2 lease capability ksmbd: downgrade RWH lease caching state to RH for directory ksmbd: send v2 lease break notification for directory ksmbd: lazy v2 lease break on smb2_write() ksmbd: avoid duplicate opinfo_put() call on error of smb21_lease_break_ack() ksmbd: fix wrong allocation size update in smb2_open() linux/export: Ensure natural alignment of kcrctab array block: renumber QUEUE_FLAG_HW_WC ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16() platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe mm/filemap: avoid buffered read/write race to read inconsistent data mm: migrate high-order folios in swap cache correctly mm/memory-failure: cast index to loff_t before shifting it mm/memory-failure: check the mapcount of the precise page ring-buffer: Fix wake ups when buffer_percent is set to 100 tracing: Fix blocked reader of snapshot buffer NFSD: fix possible oops when nfsd/pool_stats is closed. Revert "platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe" fs: cifs: Fix atime update check linux/export: Fix alignment for 64-bit ksymtab entries mptcp: refactor sndbuf auto-tuning mptcp: fix possible NULL pointer dereference on close mptcp: fix inconsistent state on fastopen race platform/x86/intel/pmc: Add suspend callback platform/x86/intel/pmc: Allow reenabling LTRs platform/x86/intel/pmc: Move GBE LTR ignore to suspend callback selftests: secretmem: floor the memory size to the multiple of page_size Revert "nvme-fc: fix race between error recovery and creating association" ftrace: Fix modification of direct_function hash while in use UBUNTU: Upstream stable to v6.1.71, v6.6.10 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Medium Assignee: Manuel Diewald (diewald) 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 Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052792 Title: Mantic update: upstream stable patchset 2024-02-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: 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 vett
[Kernel-packages] [Bug 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
This issue affects the Linux 6.7 series as well as from 6.7.3. I have met this issue on mantic as I was trying to install the vanilla 6.7.3 kernel on a system with the nvidia 545 driver. -- 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/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2003374] Re: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2204 -- 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/2003374 Title: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols Status in dh-kpatches: Unknown Status in Ubuntu on IBM z Systems: Fix Committed Status in kpatch package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in kpatch source package in Jammy: In Progress Status in linux source package in Jammy: Fix Released Status in kpatch source package in Kinetic: Won't Fix Bug description: [ Impact ] * When UBSAN is enabled in an s390x kernel configuration, kpatch- build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log). * Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality. [ Test Plan ] * Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful. [ Where problems could occur ] * A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. To manage notifications about this bug go to: https://bugs.launchpad.net/dh-kpatches/+bug/2003374/+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 2052710] Re: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subp
/etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.5.0-17-generic Error! Could not locate dkms.conf file. File: /var/lib/dkms/amdgpu/6.2.4-1652687.22.04/source/dkms.conf does not exist. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 dpkg: error processing package linux-headers-6.5.0-17-generic (--configure): installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052710 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: Invalid Bug description: I do not know any other details about the issue. I was away from my computer. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 8 06:44:58 2024 ErrorMessage: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-04 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2052710/+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 2052710] Re: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subp
You have a broken/unsupported DKMS installed that breaks the header installation. Please remove it: $ dkms remove amdgpu/6.2.4-1652687.22.04 ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052710 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: Invalid Bug description: I do not know any other details about the issue. I was away from my computer. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 8 06:44:58 2024 ErrorMessage: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-04 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-17-generic 6.5.0-17.17~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2052710/+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 2052783] [NEW] Cannot detect external storage with Ubuntu Core 20 on CM4
Public bug reported: External USB storage is not detected when running the beta Ubuntu Core 20 image [0] on CM4. Same happens with the armhf image. The issue has been discovered using Checkbox - the failing test is usb/storage-detect [1]. Step to reproduce: - Provision the CM4 with [0] - Plug a USB storage device - Check such device is recognized and listed under /dev/sd* The issue is not present when running Core 22 [2] instead. [0] http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-stable/current/ubuntu-core-20-arm64+raspi.img.xz [1] https://github.com/canonical/checkbox/blob/d070c640bccf664c0882583c1dc0d3a0d1fdb7b8/providers/base/units/usb/usb.pxu#L311 [2] http://cdimage.ubuntu.com/ubuntu-core/22/dangerous-stable/pending/ubuntu-core-22-arm64+raspi.img.xz ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2052783 Title: Cannot detect external storage with Ubuntu Core 20 on CM4 Status in linux-raspi package in Ubuntu: New Bug description: External USB storage is not detected when running the beta Ubuntu Core 20 image [0] on CM4. Same happens with the armhf image. The issue has been discovered using Checkbox - the failing test is usb/storage-detect [1]. Step to reproduce: - Provision the CM4 with [0] - Plug a USB storage device - Check such device is recognized and listed under /dev/sd* The issue is not present when running Core 22 [2] instead. [0] http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-stable/current/ubuntu-core-20-arm64+raspi.img.xz [1] https://github.com/canonical/checkbox/blob/d070c640bccf664c0882583c1dc0d3a0d1fdb7b8/providers/base/units/usb/usb.pxu#L311 [2] http://cdimage.ubuntu.com/ubuntu-core/22/dangerous-stable/pending/ubuntu-core-22-arm64+raspi.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2052783/+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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
Thanks, I'll test the new kernel over the weekend. -- 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/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize set will see data destruction when copying files from their systems onto a cifs smb 1.0 mount. wsize defaults to 65535 bytes, but when set to smaller values, like 16850, users will see blocks of 16850 bytes copied over, followed by 3900 binary zeros, followed by the next block of data followed by more binary zeros. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [Testcase] Start two VMs, one for the server, and the other, the client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf server min protocol = NT1 [sambashare] comment = Samba on Ubuntu path = /home/ubuntu/sambashare read only = no browsable = yes $ mkdir ~/sambashare $ sudo smbpasswd -a ubuntu Client -- $ sudo apt update $ sudo apt install cifs-utils $ mkdir ~/share $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) $ sha256sum testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt Now copy the file to the share. Client -- $ cp testdata.txt share/ Server -- $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt The SHA256 hash is different. If you view the file with less, you will find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, followed by another wsize=16850 bytes, then 3900 bytes of binary zeros, etc. An example of a broken file is: https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt [Where problems could occur] [Other info] Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline 6.8-rc3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
Hi R. Diez, You have probably been following the chatter on the upstream mailing list discussion. I initially thought the patch didn't fix the issue, as when I mount with wsize=16850, the issue still occurs [1], but it seems that the intent of the patch is to only correct when the server specifies an incorrect wsize, and to correct that instead [2]. [1] https://lore.kernel.org/linux-cifs/CAKAwkKuJvFDFG7=bcymj0jdmmhytlunygdueaubtoctbnqt...@mail.gmail.com/ [2] https://lore.kernel.org/linux-cifs/CAH2r5mt9gPhUSka56yk28+nksw7=LPuS4VAMzGQyJEOfcpOc=g...@mail.gmail.com/ Anyway, I have built you a test kernel that includes the patch, not from today, but yesterday's corrected one [3] ontop of 6.5.0-15-generic for Jammy HWE. [3] https://lore.kernel.org/linux- cifs/cah2r5mvzyxp7vhqvct6iep4nmxdaz2uqtt7g4yrxcvobkv_...@mail.gmail.com/ If you want to try it out on your system before it gets merged upstream, please do, since your SMB server sends a incorrect wsize. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to install (On a Jammy system): 1) sudo add-apt-repository ppa:mruffell/lp2049634-test 2) sudo apt update 3) sudo apt install linux-image-unsigned-6.5.0-15-generic linux-modules-6.5.0-15-generic linux-modules-extra-6.5.0-15-generic linux-headers-6.5.0-15-generic 4) sudo reboot 5) uname -rv 6.5.0-15-generic #15~22.04.1+TEST2049634v20240208b1-Ubuntu SMP PREEMPT_DYNAMIC Th Perform your smb1 mount but without any wsize set, and then run: $ sudo dmesg | tail or just look at the end of dmesg in journalctl, and could you please 1) send the output of the lines with "CIFS:" at the start. I just want to see if the strings "CIFS: VFS: wsize should be a multiple of 4096 (PAGE_SIZE)" and "CIFS: VFS: wsize too small, reset to minimum ie PAGE_SIZE, usually 4096" are there. and: 2) see if the issue is actually fixed by doing a test copy and looking with less. In the meantime I will ask Steve if its worth just setting all wsize to multiples of PAGE_SIZE regardless how it is set, since a partial one on the mount command line will destroy your data anyway, and thats not useful. Thanks! Matthew -- 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/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize set will see data destruction when copying files from their systems onto a cifs smb 1.0 mount. wsize defaults to 65535 bytes, but when set to smaller values, like 16850, users will see blocks of 16850 bytes copied over, followed by 3900 binary zeros, followed by the next block of data followed by more binary zeros. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [Testcase] Start two VMs, one for the server, and the other, the client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf server min protocol = NT1 [sambashare] comment = Samba on Ubuntu path = /home/ubuntu/sambashare read only = no browsable = yes $ mkdir ~/sambashare $ sudo smbpasswd -a ubuntu Client -- $ sudo apt update $ sudo apt install cifs-utils $ mkdir ~/share $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) $ sha256sum testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt Now copy the file to the share. Client -- $ cp testdata.txt share/ Server -- $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt The SHA256 hash is different. If you view the file with less, you will find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, followed by another wsize=16850 bytes, then 3900 bytes of binary zeros, etc. An example of a broken file is: https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt [Where problems could occur] [Other info] Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline 6.8-rc3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
For Morgan le Fay: Open a terminal, and type the following commands: cd /lib/firmware/mediatek sudo mv WIFI_MT7961_patch_mcu_1_2_hdr.bin WIFI_MT7961_patch_mcu_1_2_hdr.bin.orig sudo mv WIFI_RAM_CODE_MT7961_1.bin WIFI_RAM_CODE_MT7961_1.bin.orig sudo https://gitlab.com/kernel-firmware/linux-firmware/-/raw/0a18a7292a66532633d9586521f0b954c68a9fbc/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin sudo wget https://gitlab.com/kernel-firmware/linux-firmware/-/raw/0a18a7292a66532633d9586521f0b954c68a9fbc/mediatek/WIFI_RAM_CODE_MT7961_1.bin sudo update-initramfs Reboot the system. To verify which firmware version is active: sudo dmesg | grep mt7921 Look for the "Build Time" to validate, with above files, it should be: [ 9.120620] mt7921e :05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20231109190918a [ 9.132797] mt7921e :05:00.0: WM Firmware Version: 01, Build Time: 20231109190959 Do keep in mind, if the linux-firmware package is updated before a fix is released, you will need to redo these steps until this bug is fixed in the repositories. -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
That's actually the wrong firmware commit, upstream main has this now: commit 8b82ff279f1e04a72a51b4c5e5801c571f356617 Author: Rodrigo Siqueira Date: Mon Jan 8 07:26:59 2024 -0700 amdgpu: DMCUB updates for DCN312 DMCUB updates for DCN312. From internal git commit cc6d1d24518bfde45c01acfc760b3be5e1112d24. Firmware release 0.0.199.0 Tested with DC 3.2.266 Release notes: Address DP connection swap(DP0-->HDMI & DP1-->eDP) issue caused by: * Fn key failed to control brightness * eDP remains black screen during S0i3 cycle Signed-off-by: Rodrigo Siqueira which fixes that it is for DCN312/YC only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
** Description changed: + [Impact] + + linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for Navi32 + hardware. + + Of the original list below, only VCN fw update is missing still. + + [Test case] + + Install the update + Validate brightness control works. + Validate that PSR works. + Validate that eDP works after suspend/resume. + Validate that external display works. + + [Where problems could happen] + + This is new hw, where the current fw isn't fresh enough. It can't + regress other hw. + + -- + Add new FWs for GPU with GC 11.0.3: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21 ("amdgpu: add initial GC 11.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c ("amdgpu: add initial PSP 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f ("amdgpu: add initial SDMA 6.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897 ("amdgpu: add initial SMU 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c ("amdgpu: update VCN 4.0.0 firmware") ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2034103 Title: Missing firmware for AMD GPU GC 11.0.3 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux-firmware source package in Lunar: Won't Fix Bug description: [Impact] linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for Navi32 hardware. Of the original list below, only VCN fw update is missing still. [Test case] Install the update Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. [Where problems could happen] This is new hw, where the current fw isn't fresh enough. It can't regress other hw. -- Add new FWs for GPU with GC 11.0.3: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21 ("amdgpu: add initial GC 11.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c ("amdgpu: add initial PSP 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f ("amdgpu: add initial SDMA 6.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897 ("amdgpu: add initial SMU 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c ("amdgpu: update VCN 4.0.0 firmware") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034103/+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 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
Hi Jeff, Roxana, Could we please get the test kernel for driver validation? -- 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/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044589/+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