[Kernel-packages] [Bug 2060189] Re: "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken
Ubuntu noble repositories are broken atm. This is related to recent cve related to the backdoor in xz (liblzma) package. The cve number is CVE-2024-3094, many packages might be broken as they're being rebuilt during this time. Meanwhile you can add an override to apt configuration so all proper dependency versions would be selected properly as w/o that there might be some incompatibilities. Add a file to /etc/apt/preferences.d with contents like below then run 'apt clean' and 'apt update'. The example below is if you're using only noble and noble-updates archives, customize it for your needs if any, check your /etc/apt/sources.list for what archives you have enabled. Package: * Pin: release a=noble-updates Pin-Priority: 1002 Package: * Pin: release a=noble Pin-Priority: 1001 Don't forget to add a newline between each override rule group or the override might not work properly. Also you should add a rule for each archive and set priority to -1 for noble-proposed archive so packages from it would be downgraded or uninstalled if you have one. I also wouldn't recommend running apt dist-upgrade on graphical interface if the driver is buggy. Run it from text mode instead (e.g. enter ctrl-alt-f1 and log in). Also post what driver, graphics card and desktop you have. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094 -- 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/2060189 Title: "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken Status in linux package in Ubuntu: New Bug description: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060189/+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 2059279] Re: mlxbf_gige: replace SAUCE patch for pause frame counters
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059279 Title: mlxbf_gige: replace SAUCE patch for pause frame counters Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The support for mlxbf_gige pause frame counters was added to Jammy via a SAUCE patch. After upstream review, a small issue was fixed that makes the SAUCE patch different from the upstream commit. [Fix] The fix is to replace the SAUCE patch in the Jammy repo with the upstream equivalent. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Execute the command "ethtool -I -a oob_net0" to get baseline stats * Send heavy traffic into "oob_net0" interface * Re-run the above ethtool command, noting the pause frame counters [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2057960] Re: Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4
Hello, Kleber. Thank you for the instructions for installing the proposed kernel packages. Unfortunately, booting the system with the kernel 5.15.0-102.112 resulted in the same behavior, fcoe interfaces offline and reporting the FC-IDs as 0x. If you need further information, please let me know. Best regards, Anderson Soares Ferreira - anderson.soa...@embrapa.br Núcleo de Tecnologia da Informação - NTI Embrapa Territorial Tel.: (19) 3211-6200 Em qua., 3 de abr. de 2024 às 09:49, Kleber Sacilotto de Souza < 2057...@bugs.launchpad.net> escreveu: > Hello Anderson, > > Thank you for reporting the issue. We have a new kernel for 22.04 > (version 5.15.0-102.112) that is about to be released in the next few > days. Could you please test it again with this kernel and report the > results? You can either enable -proposed in your system and update the > kernel, or wait until it gets promoted to -updates and a simple dist- > upgrate will update the kernel. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2057960 > > Title: > Problems on Fibre Channel over Ethernet on Ubuntu 22.04.4 > > Status in linux package in Ubuntu: > New > > Bug description: > Since I've upgraded my server's to Ubuntu 22.04.4 I'm facing problems > to make my fcoe setup to work correctly. > Firstly, some context. We have a HPE Synergy appliance with a bunch of > Synergy 480 Gen10 servers still running Ubuntu 20.04. > Each 480 server has 4 QLogic BCM57840 NetXtreme II Ethernet Multi > Function network adapters with two of them dedicated to storage > communication through FCoE. > > Recently, I've upgraded one of them to Ubuntu 22.04 and realized that > after the upgrade, all the Fibre Channel LUNs have disappeared. During the > diagnostic process I noticed that both network (bnx2x) and fcoe (fcoe, > bnx2fc) kernel drivers have been loaded properly, FCoE vlans were correctly > detected by fcoe-utils, but there was no connection between the server and > the storage and the server could not detect any LUN. > I also noticed that fcoeadm was reporting the following status: > > # fcoeadm -i > Description: BCM57840 NetXtreme II Ethernet Multi Function > Revision: 11 > Manufacturer: Broadcom Inc. and subsidiaries > Serial Number:9440C953B7F0 > > Driver: bnx2x Unknown > Number of Ports: 1 > > Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over > ens3f2.4093-fco > OS Device Name:host2 > Node Name: 0x1a3d2725 > Port Name: 0x1a3d2724 > Fabric Name: 0x0 > Speed: 20 Gbit > Supported Speed: 1 Gbit, 10 Gbit > MaxFrameSize: 2048 bytes > FC-ID (Port ID): 0x > State: Offline > Description: BCM57840 NetXtreme II Ethernet Multi Function > Revision: 11 > Manufacturer: Broadcom Inc. and subsidiaries > Serial Number:9440C953B7F0 > > Driver: bnx2x Unknown > Number of Ports: 1 > > Symbolic Name: bnx2fc (QLogic BCM57840) v2.12.13 over > ens3f3.4094-fco > OS Device Name:host3 > Node Name: 0x1a3d2727 > Port Name: 0x1a3d2726 > Fabric Name: 0x0 > Speed: 20 Gbit > Supported Speed: 1 Gbit, 10 Gbit > MaxFrameSize: 2048 bytes > FC-ID (Port ID): 0x > State: Offline > > Although most of information displayed was correct, the port state was > always offline (what explains no storage connectivity) and the FC-ID > reported was 0x for both interfaces. > > Supposing that something went wrong during the upgrade process, I > decided to make a fresh install of the server and, for my surprise, the > fcoe ports went online and all luns were detected correctly. > Unfortunately, the ports went offline again after a dist-upgrade. > Trying to understand what was happening I performed another fresh > install of the Ubuntu 22.04, but this time collecting some information > about kernel and packages versions from before and after dist-upgrade. > What I discovered was that all packages related (fcoe-utils, lldpad) had > the same versions before and after, the only exception was the kernel > itself. Before the dist-upgrade the kernel in use was 5.15.0-25-generic and > after dist-upgrade the kernel was 5.15.0-100-generic. > Suspecting a kernel problem I installed and booted different kernel > versions from 5.15.0-25 and 5.15.0-100 and discovered that the problem > probably was introduced with kernel 5.15.0-94, since it is the first > version showing the describe behavior. > Looking at the changelog of linux-modules package, I noticed some > changes on fcoe and
[Kernel-packages] [Bug 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
@paride: Yes, I've seen this with other kernels, mostly with the nvidia drivers. I think all of the runs of the following since March 20 show this problem: https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-510-server/focal/amd64 https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-515/focal/amd64 https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-460-server/focal/amd64 As mentioned in MM, all of these started failing between March 11 and March 20. All of these drivers are transitional packages (they don't really do anything other then depend on the next driver in the series to keep users on a supported driver), but I don't know if this is of interest to the problem as I've seen this with other packages too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: Invalid Status in autopkgtest package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+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 2055052] Re: net/sched: flower: Add lock protection when remove filter handle
** Tags removed: verification-needed-jammy-linux-bluefield ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2055052 Title: net/sched: flower: Add lock protection when remove filter handle Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * intro As IDR can't protect itself from the concurrent modification, place idr_remove() under the protection of tp->lock. * how to fix need to backport the patch from Jianbo "net/sched: flower: Add lock protection when remove filter handle" https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=1fde0ca3a0de7e9f917668941156959dd5e9108b * reproduce and verification It's hard to reproduce because it is a race condition we found in k8s+ovn deployment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2055052/+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 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
This also happens with linux-aws-6.5 on jammy amd64. Sorry for the bad formatting: 767s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 768s autopkgtest [15:06:12]: rebooting testbed after setup commands that affected boot 784s autopkgtest [15:06:28]: testbed running kernel: Linux 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 785s autopkgtest [15:06:29]: apt-source linux-aws-6.5 786s blame: linux-aws-6.5 786s badpkg: rules extract failed with exit code 1 786s autopkgtest [15:06:30]: ERROR: erroneous package: rules extract failed with exit code 1 796s Creating nova instance adt-jammy-amd64-linux-aws-6.5-20240404-145324-juju-7f2275-prod-proposed-migration-environment-2-e4e1e79e-1749-4ae4-8386-7f19e3be6982 from image adt/ubuntu-jammy-amd64-server-20240404.img (UUID dc235da2-b119-4ee4-b09e-7c7ec6013d48) -- 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/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: New Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.147.05-0ubuntu2.22.04.1 --- nvidia-graphics-drivers-525 (525.147.05-0ubuntu2.22.04.1) jammy; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Bartlomiej Zolnierkiewicz Tue, 26 Mar 2024 11:59:27 +0100 ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
Patch submitted for review: https://lists.ubuntu.com/archives/kernel- team/2024-April/149922.html -- 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/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2060193] [NEW] iwlwifi microcode crash when using wrong password to join a WPA3 access point
Public bug reported: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x | timestamp Apr 3 22:13:57 waplinuc kernel: [1158487.457016] iwlwifi :00:14.3: 0x88D4 | flow_handler Apr 3 22:13:57 waplinuc kernel: [1158487.457058] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.457059] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7 Apr 3 22:13:57 waplinuc kernel: [1158487.457061] iwlwifi :00:14.3: 0x20003336 | ADVANCED_SYSASSERT Apr 3 22:13:57 waplinuc kernel: [1158487.457063] iwlwifi :00:14.3: 0x | umac branchlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.457064] iwlwifi :00:14.3: 0x804539C6 | umac branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.457066] iwlwifi :00:14.3: 0xC0081614 | umac interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.457067] iwlwifi :00:14.3:
[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.147.05-0ubuntu2.23.10.1 --- nvidia-graphics-drivers-525 (525.147.05-0ubuntu2.23.10.1) mantic; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Bartlomiej Zolnierkiewicz Mon, 25 Mar 2024 16:28:47 +0100 ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package libnvidia-nscq-525 - 525.147.05-0ubuntu2.20.04.1 --- libnvidia-nscq-525 (525.147.05-0ubuntu2.20.04.1) focal; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Mon, 25 Mar 2024 15:30:35 +0100 ** Changed in: libnvidia-nscq-525 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package fabric-manager-525 - 525.147.05-0ubuntu2.20.04.2 --- fabric-manager-525 (525.147.05-0ubuntu2.20.04.2) focal; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Mon, 25 Mar 2024 16:07:24 +0100 ** Changed in: fabric-manager-525 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package nvidia-graphics-drivers-525-server - 525.147.05-0ubuntu2.22.04.1 --- nvidia-graphics-drivers-525-server (525.147.05-0ubuntu2.22.04.1) jammy; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Fri, 22 Mar 2024 16:13:23 +0100 ** Changed in: libnvidia-nscq-525 (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2059310] Re: mlxbf_gige: call request_irq() after NAPI initialized
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059310 Title: mlxbf_gige: call request_irq() after NAPI initialized Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The exception happens because there is a pending RX interrupt before the call to request_irq(RX IRQ) executes. Then, the RX IRQ handler fires immediately after this request_irq() completes. The RX IRQ handler runs "napi_schedule()" before NAPI is fully initialized via "netif_napi_add()" and "napi_enable()", both which happen later in the open() logic. [Fix] The logic in mlxbf_gige_open() must fully initialize NAPI before any calls to request_irq() execute. [Test Case] * Boot BF platform and bring up "oob_net0" interface * Enable kdump completely * Trigger kdump via "echo c > /proc/sysrq-trigger" * There should be no exceptions from mlxbf_gige driver [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059310/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package nvidia-graphics-drivers-525-server - 525.147.05-0ubuntu2.20.04.1 --- nvidia-graphics-drivers-525-server (525.147.05-0ubuntu2.20.04.1) focal; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Fri, 22 Mar 2024 16:31:56 +0100 ** Changed in: libnvidia-nscq-525 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2060189] [NEW] "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken
Public bug reported: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - apt-get dist-upgrade break graphics display from Ubuntu Noble + "apt-get dist-upgrade" command causes the display to stop working - OS is broken ** Summary changed: - "apt-get dist-upgrade" command causes the display to stop working - OS is broken + "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken ** Package changed: irqbalance (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060189 Title: "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken Status in linux package in Ubuntu: New Bug description: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060189/+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 2054845] Re: mlxbf-gige: support fixed phy for Bobcat
** Tags removed: verification-done-jammy ** Tags added: verification-done-jammy-linux-bluefield -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2054845 Title: mlxbf-gige: support fixed phy for Bobcat Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Bobcat is a new board which doesn't have an external PHY connected to the OOB. There are no MDIO busses involved and no PHY involved. The OOB is directly connected to the switch (MAC to MAC). SO we need to use the linux fixed phy to be able to emulate the mdio behavior and load the ethernet driver. [Fix] * Register the fixed-phy register in the case of the bobcat. [Test Case] * Important: For testing on the bobcat board, make sure the corresponding UEFI image is also loaded, otherwise, the oob driver will fail to load. For other board, it is backward compatible. * Check if the mlxbf-gige is loaded on bobcat * Check that it is using the fixed-phy via dmesg | grep PHY * check that the oob interface is pingable * check that files can be copied over via oob interface * rmmod/modprobe * ifconfig up/down * reboot test [Regression Potential] * Redo all the OOB testing on other boards (moonraker) and make sure the bobcat changes dont trigger any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2054845/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.147.05-0ubuntu2.20.04.1 --- nvidia-graphics-drivers-525 (525.147.05-0ubuntu2.20.04.1) focal; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Bartlomiej Zolnierkiewicz Tue, 26 Mar 2024 13:18:11 +0100 ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
** Changed in: autopkgtest (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: Invalid Status in autopkgtest package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+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 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
As a general rule, the kernel internal interface changes all the time and it cannot take into account out of tree module. It's the responsibility of the maintainers of these modules to keep up with upstream changes. -- 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/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules Status in linux package in Ubuntu: Won't Fix Status in linux source package in Jammy: Won't Fix Bug description: 3rd party kernel modules for Ubuntu 20.04 break due to the recently backported change of renaming GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART linux-gcp-5.15-headers-5.15.0-1049 still uses GENHD_FL_NO_PART_SCAN which the 3rd party kernel modules use, while linux- gcp-5.15-headers-5.15.0-1051 has brought the rename to GENHD_FL_NO_PART in. This is a breaking change and should not have been backported. The 3rd party modules have been updated for newer kernels on 22.04, but can't be updated on 20.04 with this breaking change. $ grep GENHD_FL_NO_PART /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN`` (0x0200): partition scanning is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN``. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h:#define GENHD_FL_NO_PART_SCAN 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: !(disk->flags & GENHD_FL_NO_PART_SCAN); /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART`` (0x0200): partition support is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART``. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h:#define GENHD_FL_NO_PART 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: return disk_max_parts(disk) > 1 && !(disk->flags & GENHD_FL_NO_PART); $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt policy linux-image-5.15.0-1051-gcp linux-image-5.15.0-1051-gcp: Installed: 5.15.0-1051.59~20.04.1 Candidate: 5.15.0-1051.59~20.04.1 Version table: *** 5.15.0-1051.59~20.04.1 500 500 http://australia-southeast1.gce.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-1051-gcp 5.15.0-1051.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-1051.59~20.04.1-gcp 5.15.136 Uname: Linux 5.15.0-1051-gcp x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 14 12:07:11 2024 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-gcp-5.15 UpgradeStatus: Upgraded to focal on 2023-05-07 (282 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053101/+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 2059978] Re: linux-aws-5.15 ADT test MISS because it's unable to find package
I now have an idea of where the problem is. This will be an interesting one. @ubuntu-qa people: this may be related to the changes in 30d5aa7bd48ac15141f106dafb5930a1b5ac942f which we put in production with the switch to 5.32ish. So I expect this issue to be "new" but not super new (i.e. fist hit in the past month or so). I hope this matches observations. @fginther: IIRC you also hit this, right? MM is down so I can't check the backlog. ** Also affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Changed in: auto-package-testing Status: New => Invalid ** Changed in: autopkgtest (Ubuntu) Assignee: (unassigned) => Paride Legovini (paride) -- 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/2059978 Title: linux-aws-5.15 ADT test MISS because it's unable to find package Status in Auto Package Testing: Invalid Status in autopkgtest package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: SRU cycle 2024.03.04 Focal aws-5.15 ADT test linux-aws-5.15 for both amd64 and arm64 results in a MISS with the error message below. It seems like the test was unable to locate the kernel-testing--linux- aws-5.15--modules-extra--preferred$ package which led to other missing packages and the test erroring out with exit code 1. This test has been SKIPPED before but with seemingly different reasons. I have also attached the whole log amd64 output to this bug report. "339s Reading state information... 339s E: Unable to locate package ^kernel-testing--linux-aws-5.15--modules-extra--preferred$ 339s E: Couldn't find any package by glob '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s E: Couldn't find any package by regex '^kernel-testing--linux-aws-5.15--modules-extra--preferred$' 339s Reading package lists... 339s Building dependency tree... 339s Reading state information... 339s E: Unable to locate package ^linux-modules-extra-aws-5.15$ 339s E: Couldn't find any package by glob '^linux-modules-extra-aws-5.15$' 339s E: Couldn't find any package by regex '^linux-modules-extra-aws-5.15$' 339s autopkgtest [16:53:45]: rebooting testbed after setup commands that affected boot 363s autopkgtest [16:54:09]: testbed running kernel: Linux 5.15.0-1057-aws #63~20.04.1-Ubuntu SMP Mon Mar 25 10:28:36 UTC 2024 363s autopkgtest [16:54:09]: apt-source linux-aws-5.15 364s blame: linux-aws-5.15 364s badpkg: rules extract failed with exit code 1 364s autopkgtest [16:54:10]: ERROR: erroneous package: rules extract failed with exit code 1" To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2059978/+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 2060209] [NEW] Jammy update: v5.15.151 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.151 upstream stable release from git://git.kernel.org/ netfilter: nf_tables: disallow timeout for anonymous sets mtd: spinand: gigadevice: Fix the get ecc status issue netlink: Fix kernel-infoleak-after-free in __skb_datagram_iter net: ip_tunnel: prevent perpetual headroom growth tun: Fix xdp_rxq_info's queue_index when detaching cpufreq: intel_pstate: fix pstate limits enforcement for adjust_perf call back net: veth: clear GRO when clearing XDP even when down ipv6: fix potential "struct net" leak in inet6_rtm_getaddr() lan78xx: enable auto speed configuration for LAN7850 if no EEPROM is detected net: enable memcg accounting for veth queues veth: try harder when allocating queue memory net: usb: dm9601: fix wrong return value in dm9601_mdio_read uapi: in6: replace temporary label with rfc9486 stmmac: Clear variable when destroying workqueue Bluetooth: Avoid potential use-after-free in hci_error_reset Bluetooth: hci_event: Fix wrongly recorded wakeup BD_ADDR Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST netfilter: nf_tables: allow NFPROTO_INET in nft_(match/target)_validate() netfilter: nfnetlink_queue: silence bogus compiler warning netfilter: core: move ip_ct_attach indirection to struct nf_ct_hook netfilter: make function op structures const netfilter: let reset rules clean out conntrack entries netfilter: bridge: confirm multicast packets before passing them up the stack rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back igb: extend PTP timestamp adjustments to i211 tls: rx: don't store the record type in socket context tls: rx: don't store the decryption status in socket context tls: rx: don't issue wake ups when data is decrypted tls: rx: refactor decrypt_skb_update() tls: hw: rx: use return value of tls_device_decrypted() to carry status tls: rx: drop unnecessary arguments from tls_setup_from_iter() tls: rx: don't report text length from the bowels of decrypt tls: rx: wrap decryption arguments in a structure tls: rx: factor out writing ContentType to cmsg tls: rx: don't track the async count tls: rx: move counting TlsDecryptErrors for sync tls: rx: assume crypto always calls our callback tls: rx: use async as an in-out argument tls: decrement decrypt_pending if no async completion will be called efi/capsule-loader: fix incorrect allocation size power: supply: bq27xxx-i2c: Do not free non existing IRQ ALSA: Drop leftover snd-rtctimer stuff from Makefile fbcon: always restore the old font data in fbcon_do_set_font() afs: Fix endless loop in directory parsing riscv: Sparse-Memory/vmemmap out-of-bounds fix tomoyo: fix UAF write bug in tomoyo_write_control() ALSA: firewire-lib: fix to check cycle continuity gtp: fix use-after-free and null-ptr-deref in gtp_newlink() wifi: nl80211: reject iftype change with mesh ID change btrfs: dev-replace: properly validate device names dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read dmaengine: ptdma: use consistent DMA masks dmaengine: fsl-qdma: init irq after reg initialization mmc: core: Fix eMMC initialization with 1-bit bus connection mmc: sdhci-xenon: add timeout for PHY init complete mmc: sdhci-xenon: fix PHY init clock stability pmdomain: qcom: rpmhpd: Fix enabled_corner aggregation x86/cpu/intel: Detect TME keyid bits before setting MTRR mask registers mptcp: move __mptcp_error_report in protocol.c mptcp: process pending subflow error on close mptcp: rename timer related helper to less confusing names selftests: mptcp: add missing kconfig for NF Filter selftests: mptcp: add missing kconfig for NF Filter in v6 mptcp: clean up harmless false expressions mptcp: add needs_id for netlink appending addr mptcp: push at DSS boundaries mptcp: fix possible deadlock in subflow diag cachefiles: fix memory leak in cachefiles_add_cache() fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super Revert "drm/bridge: lt8912b: Register and attach our DSI device at probe" af_unix: Drop oob_skb ref before purging queue in GC. gpio: 74x164: Enable output pins after registers are reset gpiolib: Fix the error path order in gpiochip_add_data_with_key() gpio: fix resource unwinding order in error path Revert "interconnect: Fix locking for runpm vs reclaim" Revert "interconnect: Teach lockdep about icc_bw_lock order" bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup bpf: Add table ID to bpf_fib_lookup BPF helper bpf: Derive source IP addr via bpf_*_fib_lookup() net: tls: fix async vs NIC crypto offload Revert "tls: rx: move counting TlsDecryptErrors
[Kernel-packages] [Bug 2059951] Re: mlxbf_gige: stop interface during shutdown
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059951 Title: mlxbf_gige: stop interface during shutdown Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] The mlxbf_gige driver shutdown() is invoked during reboot processing, but the stop() logic is not guaranteed to execute on all distros. If stop() does not execute NAPI remains enabled during system shutdown and can cause an exception if NAPI is scheduled when interface is shutdown but not stopped. [Fix] The networking interface managed by the mlxbf_gige driver must be stopped during reboot processing so that it is put into a clean state and driver callbacks won't be called. [Test Case] * Put BF platform into a reboot loop * Ensure that BF platform brings up "oob_net0" interface each reboot, and that no mlxbf_gige driver exceptions occur [Regression Potential] There is low potential for regression as this brings in upstream content. [Other] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2059951/+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 2038777] Re: UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
*** This bug is a duplicate of bug 2058477 ***
https://bugs.launchpad.net/bugs/2058477
** This bug has been marked a duplicate of bug 2058477
[Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN:
array-index-out-of-bounds in
/build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41"
multiple times, especially during boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-azure-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038777
Title:
UBSAN: array-index-out-of-bounds (drivers/net/hyperv/netvsc.c)
Status in linux package in Ubuntu:
Expired
Status in linux-meta-azure-6.5 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
New
Status in linux-meta-azure-6.5 source package in Jammy:
Confirmed
Bug description:
HiperV VM network problems
[ 19.259297]
[ 19.259536] UBSAN: array-index-out-of-bounds in
/build/linux-7dWMY3/linux-6.5.0/drivers/net/hyperv/netvsc.c:1445:41
[ 19.259715] index 1 is out of range for type 'vmtransfer_page_range [1]'
[ 19.259896] CPU: 1 PID: 1306 Comm: (udev-worker) Not tainted
6.5.0-7-generic #7-Ubuntu
[ 19.259898] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022
[ 19.259899] Call Trace:
[ 19.259901]
[ 19.259902] dump_stack_lvl+0x48/0x70
[ 19.259908] dump_stack+0x10/0x20
[ 19.259909] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 19.259912] netvsc_receive+0x437/0x490 [hv_netvsc]
[ 19.259917] netvsc_poll+0x176/0x4b0 [hv_netvsc]
[ 19.259921] __napi_poll+0x30/0x1f0
[ 19.259924] net_rx_action+0x181/0x2e0
[ 19.259925] __do_softirq+0xd6/0x346
[ 19.259927] ? _raw_spin_unlock+0xe/0x40
[ 19.259929] __irq_exit_rcu+0x75/0xa0
[ 19.259932] irq_exit_rcu+0xe/0x20
[ 19.259933] sysvec_hyperv_callback+0x92/0xd0
[ 19.259935]
[ 19.259935]
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.8
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CrashDB: ubuntu
Date: Sun Oct 8 23:09:45 2023
InstallationDate: Installed on 2021-03-07 (945 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64
(20210201.2)
PackageArchitecture: all
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to mantic on 2023-10-08 (0 days ago)
VarLogDistupgradeLspcitxt:
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 oct 9 20:46 seq
crw-rw 1 root audio 116, 33 oct 9 20:46 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-03-07 (948 days ago)
InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64
(20210201.2)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci:
Lspci-vt:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
ProcFB: 0 hyperv_drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro mitigations=off iommu=pt
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
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: mantic
Uname: Linux
[Kernel-packages] [Bug 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package libnvidia-nscq-525 - 525.147.05-0ubuntu2.22.04.1 --- libnvidia-nscq-525 (525.147.05-0ubuntu2.22.04.1) jammy; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Mon, 25 Mar 2024 15:14:20 +0100 ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Also affects: linux-oem-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.8 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-6.8 (Ubuntu Mantic)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042500
Title:
Fix after-suspend-mediacard/sdhc-insert test failed
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
New
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in linux-oem-6.8 source package in Mantic:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.1 source package in Noble:
Invalid
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
New
Bug description:
[Impact]
checkbox test case, after-suspend-mediacard/sdhc-insert, failed.
[Fix]
Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability
for suspend/resume"") reverted saving and restoring of ASPM L1 Substates
due to a regression that caused resume from suspend to fail on certain
systems. However, we never added this capability back and this is now
causing systems fail to enter low power CPU states, drawing more power
from the battery.
The original revert mentioned that we restore L1 PM substate configuration
even though ASPM L1 may already be enabled. This is due the fact that
the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state().
Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4
more closely by:
1) Do not restore ASPM configuration in pci_restore_pcie_state() but
do that after PCIe capability is restored in pci_restore_aspm_state()
following PCIe r6.0, sec 5.5.4.
2) ASPM is first enabled on the upstream component and then downstream
(this is already forced by the parent-child ordering of Linux
Device Power Management framework).
3) Program ASPM L1 PM substate configuration before L1 enables.
4) Program ASPM L1 PM substate enables last after rest of the fields
in the capability are programmed.
5) Add denylist that skips restoring on the ASUS and TUXEDO systems
where these regressions happened, just in case. For the TUXEDO case
we only skip restore if the BIOS is involved in system suspend
(that's forcing "mem_sleep=deep" in the command line). This is to
avoid possible power regression when the default suspend to idle is
used, and at the same time make sure the devices continue working
after resume when the BIOS is involved.
[Test Case]
1. suspend and resume.
2. check if the error appears in dmesg
~~~
pcieport :00:1c.0: pciehp: Slot(5): Card not present
rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device
inaccessible
rtsx_pci :05:00.0: Unable to change power state from D3cold to D0,
device inaccessible
~~~
[where the issue could happen]
low, the patch works well on the reported malfunctioned ASUS platform too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042500/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Mantic: Confirmed Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2059961] Re: genetlink: fix single op policy dump when do is present
** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2059961 Title: genetlink: fix single op policy dump when do is present Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: intro - Our internal test triggers a kernel crash dump below [ 888.690348] Sun Mar 24 23:51:59 2024: DriVerTest - Start Test [ 888.691834] [ 888.983912] mlx5_core :08:00.1 eth3: Link up [ 888.987644] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready [ 889.336577] mlx5_core :08:00.0 eth2: Link up [ 894.635836] Sun Mar 24 11:52:04 PM IST 2024 - DriVerTest Debug Heartbeat [ 940.431644] general protection fault, probably for non-canonical address 0x80020014: [#1] SMP NOPTI [ 940.432866] CPU: 7 PID: 94305 Comm: ethtool Tainted: G OE 5.15.0-1039.17.g0d63875-bluefield #1 [ 940.433970] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 940.435220] RIP: 0010:netlink_policy_dump_add_policy+0x95/0x160 [ 940.435893] Code: 48 c1 e0 04 4c 8b 34 01 4d 85 f6 74 5b 31 db eb 10 4c 89 e8 83 c3 01 48 c1 e0 04 39 5c 01 08 72 3f 89 d8 48 c1 e0 04 4c 01 f0 <0f> b6 10 83 ea 08 83 fa 01 77 dc 0f b7 50 02 48 8b 70 08 48 8d 7c [ 940.437921] RSP: 0018:ffa002d37a08 EFLAGS: 00010286 [ 940.438551] RAX: 80020014 RBX: RCX: ff1100027d00 [ 940.439351] RDX: fff8 RSI: 0018 RDI: ffa002d37a10 [ 940.440131] RBP: 0003 R08: 0040 R09: ff1100027d2d0f10 [ 940.440900] R10: 0318 R11: R12: ff1100011fa59bc0 [ 940.441683] R13: 0004 R14: 80020014 R15: 83fa6540 [ 940.442459] FS: 7f4a17993740() GS:ff1100085f9c() knlGS: [ 940.443394] CS: 0010 DS: ES: CR0: 80050033 [ 940.444044] CR2: 00429f50 CR3: 00012fc2e002 CR4: 00771ee0 [ 940.444847] DR0: DR1: DR2: [ 940.445639] DR3: DR6: fffe0ff0 DR7: 0400 [ 940.446431] PKRU: 5554 [ 940.446795] Call Trace: [ 940.447144] [ 940.447444] ? __die_body+0x1b/0x60 [ 940.447880] ? die_addr+0x39/0x60 [ 940.448315] ? exc_general_protection+0x1bc/0x3c0 [ 940.448867] ? asm_exc_general_protection+0x22/0x30 [ 940.449445] ? netlink_policy_dump_add_policy+0x95/0x160 [ 940.450058] ? netlink_policy_dump_add_policy+0xb2/0x160 [ 940.450714] ? ethtool_get_phc_vclocks+0x70/0x70 [ 940.451272] ctrl_dumppolicy_start+0xc4/0x2a0 [ 940.451788] ? ethnl_reply_init+0xd0/0xd0 [ 940.452284] ? __nla_parse+0x22/0x30 [ 940.452734] ? __cond_resched+0x15/0x30 [ 940.453211] ? kmem_cache_alloc_trace+0x44/0x390 [ 940.453750] genl_start+0xc3/0x150 [ 940.454179] __netlink_dump_start+0x175/0x250 [ 940.454706] genl_family_rcv_msg_dumpit.isra.0+0x9a/0x100 [ 940.455334] ? genl_family_rcv_msg_attrs_parse.isra.0+0xe0/0xe0 [ 940.455998] ? genl_unlock+0x20/0x20 [ 940.456453] ? genl_parallel_done+0x40/0x40 [ 940.456957] genl_rcv_msg+0x11f/0x2b0 [ 940.457421] ? genl_get_cmd+0x170/0x170 [ 940.457890] ? ctrl_dumppolicy_put_op.isra.0+0x1e0/0x1e0 [ 940.458515] ? genl_lock_done+0x60/0x60 [ 940.458987] ? genl_family_rcv_msg_doit.isra.0+0x110/0x110 [ 940.459634] netlink_rcv_skb+0x54/0x100 [ 940.460107] genl_rcv+0x24/0x40 [ 940.460504] netlink_unicast+0x18d/0x230 [ 940.460983] netlink_sendmsg+0x240/0x4a0 [ 940.461472] __sock_sendmsg+0x2f/0x40 [ 940.461922] __sys_sendto+0xee/0x160 [ 940.462384] ? __sys_recvmsg+0x56/0xa0 [ 940.462854] ? exit_to_user_mode_prepare+0x35/0x170 [ 940.463439] __x64_sys_sendto+0x25/0x30 [ 940.463906] do_syscall_64+0x35/0x80 [ 940.464368] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 940.464955] RIP: 0033:0x7f4a17aa940a [ 940.465415] Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e c3 0f 1f 44 00 00 41 54 48 83 ec 30 44 89 [ 940.467418] RSP: 002b:7ffc3612cac8 EFLAGS: 0246 ORIG_RAX: 002c [ 940.468284] RAX: ffda RBX: 00c3b3b0 RCX: 7f4a17aa940a [ 940.469057] RDX: 0024 RSI: 00c3b3b0 RDI: 0003 [ 940.469852] RBP: 00c3b2a0 R08: 7f4a17ba4200 R09: 000c [ 940.470674] R10:
[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package fabric-manager-525 - 525.147.05-0ubuntu2.23.10.1 --- fabric-manager-525 (525.147.05-0ubuntu2.23.10.1) mantic; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Fri, 22 Mar 2024 17:48:00 +0100 ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Mantic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2049635] Re: Roll UDA & ERD drivers from 525 to 535
This bug was fixed in the package libnvidia-nscq-525 - 525.147.05-0ubuntu2.23.10.1 --- libnvidia-nscq-525 (525.147.05-0ubuntu2.23.10.1) mantic; urgency=medium * End of support for 525 series, transition to 535. LP: #2049635 -- Kuba Pawlak Mon, 25 Mar 2024 14:16:33 +0100 ** Changed in: fabric-manager-525 (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Committed Status in libnvidia-nscq-525 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-525 source package in Bionic: In Progress Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Committed Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Committed Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-525 source package in Mantic: Fix Released Status in libnvidia-nscq-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Status in fabric-manager-525 source package in Noble: Fix Released Status in libnvidia-nscq-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525 source package in Noble: Fix Released Status in nvidia-graphics-drivers-525-server source package in Noble: Fix Released Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+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 2058330] Re: Update amd-pmf for AMD strix series
** Package changed: linux-oem (Ubuntu Noble) => linux-oem-6.8 (Ubuntu Noble) -- 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/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+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 2058498] Re: pwr-mlxbf: support Bobcat graceful shutdown via gpio6
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2058498 Title: pwr-mlxbf: support Bobcat graceful shutdown via gpio6 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] OCP3.0 project was discontinued and canceled so all stale code related to that was removed. The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat board. On the bobcat board, the main board cpld issues the shutdown request to the dpu cpld. the dpu cpld issues that request to ARM via GPIO6 and ARM should trigger a graceful shutdown and set the ARM boot progress to 6. [Fix] The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat board. On the bobcat board, the main board cpld issues the shutdown request to the dpu cpld. the dpu cpld issues that request to ARM via GPIO6 and ARM should trigger a graceful shutdown and set the ARM boot progress to 6. [Test Case] * Test shutdown on Bobcat via CPLD command. [Regression Potential] * no known regression as the OCP3.0 board was discontinued. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2058498/+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 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
Any news? Pulling firmware from upstream is enough to solve this issue. -- 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/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update Status in Linux Firmware: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Mantic: Confirmed Status in linux-firmware source package in Noble: Fix Released Bug description: Current version of amdgpu binaries in linux-firmware shipped with ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when decoding VP9 content with the iGPU on modern AMD mobile processor (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor). The issue has been reported and solved upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044 [EDIT: fixed link] Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2058830/+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 2060130] Re: [SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel cmdline/initrd sections from EFI stub
Applied all the listed commits to noble/linux, including also:
9c55461040a9 ("x86/efistub: Remap kernel text read-only before dropping
NX attribute")
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Committed
--
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/2060130
Title:
[SPR][EMR][GNR] TDX: efi: TD Measurement support for kernel
cmdline/initrd sections from EFI stub
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Noble:
Fix Committed
Bug description:
This is a public version of https://bugs.launchpad.net/bugs/2058835
[Description]
When a TD is created, during the boot process, steps like loading the
firmware, bootloader, kernel image, etc are measured and stored in RTMR
registers to support the trusted boot model. After boot, this measured value is
used to validate the integrity of the boot process.
During the direct boot process, bootloader is responsible for
measuring the kernel image before loading the kernel. But if the
kernel is loaded from EFI bootstub, the related measurements needs to
be owned by the EFI bootstub. This support needs to be added to Linux
EFI boot stub code.
Also, as per the following discussion, the kernel command line or
initrd section measurements also needs be owned by the EFI bootsub.
https://edk2.groups.io/g/devel/topic/93737108?p=Created%2C%2C%2C20%2C2%2C0%2C0%3A%3A%2C%2C%2C0%2C0%2C0%2C93737108
[Fix]
Cherry pick cleanly:
d228814b1913 efi/libstub: Add get_event_log() support for CC platforms
ac93cbfc2a2c efi/libstub: Measure into CC protocol if TCG2 protocol is
absent
0bbe5b0ea97a efi/libstub: Add Confidential Computing (CC) measurement
typedefs
7a1381e8313f efi/tpm: Use symbolic GUID name from spec for final events
table
3e0b0f880e9e efi/libstub: Use TPM event typedefs from the TCG PC Client
spec
External Links:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=70ef654469b371d0a71bcf967fa3dcbca05d4b25
Those are all merged into upstream.
[Test Plan]
Build/sign/boot with secure boot enabled.
[Where problems could occur]
At boot time, as this is modifying the efi libstub. Could be impacting
secure boot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060130/+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 2060189] [NEW] "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken
You have been subscribed to a public bug: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken https://bugs.launchpad.net/bugs/2060189 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
