[Kernel-packages] [Bug 2064514] Re: Azure: Update CIFS to 5.15-backport-1-24-24
https://lists.ubuntu.com/archives/kernel-team/2024-May/150689.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2064514 Title: Azure: Update CIFS to 5.15-backport-1-24-24 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Test Plan: Microsoft tested. Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2064514/+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 2064514] Re: Azure: Update CIFS to 5.15-backport-1-24-24
** Description changed: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. + git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 - git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 + Test Plan: + + Microsoft tested. Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2064514 Title: Azure: Update CIFS to 5.15-backport-1-24-24 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Test Plan: Microsoft tested. Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2064514/+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 2064514] [NEW] Azure: Update CIFS to 5.15-backport-1-24-24
Public bug reported: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2064514 Title: Azure: Update CIFS to 5.15-backport-1-24-24 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification Impact: Microsoft has requested that the 5.15 backport from the upstream maintainer (Steve French) be included in Jammy linux-azure. These patches upgrade CIFS to the same level as Linux v6.8. git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport-1-24-24 Regression Potential: Regressions could include failure to connect, DNS resolution failures, dropped connections, etc. However, Microsoft has tested these patches extensively since January 2024. Other Info: SF: #00383839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2064514/+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 2054855] Re: Azure: Network doesn't get configured after triggering kdump
** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2054855 Title: Azure: Network doesn't get configured after triggering kdump Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] The network doesn't get configured after a kdump on some generations of hardware. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a8a8afba0c305 [Test Plan] Microsoft tested. [[Where things could go wrong] You're already in deep doo doo if you have to run kdump. However. not having a network afterwards is a sure sign that this patch doesn't work for your hardware. [Other Info] SF: #00378199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2054855/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Good to know a new kernel is coming out soon to fix the issue. Thank you. Where is the best place to look to see when the patch is released? Many thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 1471380] Re: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access
The workaround has now landed in all currently supported linux-stable branches: linux-6.8: 6.8-rc7 (f45812cc23fb74bef62d4eb8a69fe7218f4b9f2a) linux-6.7: 6.7.9(cbf12e716a52d260fabecdca7d5f6e7cd07aed6c) linux-6.6: 6.6.21 (71da10e633a96593cf59af3f322a9c49a22cb71e) linux-6.1: 6.1.81 (249d6ca4ff0022a4b51a8eb9fac6d7bff2c94d1b) linux-5.15: 5.15.154 (9bc9c11c151ab27214cc204d954ee902e9bbe8e2) linux-5.10: 5.10.215 (f33255ccbb0f627da76364cce72cf980d027142c) linux-5.4: 5.4.274 (34b5d2ff9ed5cdea9f971f394c0d623761a4d357) linux-4.19: 4.19.312 (a7bd7dbaa2ddcf8c5ed5d96df240f1442447d252) I tested the recent Ubuntu 24.04 beta and made sure the issue is already fixed there. Sadly, we just about missed the time (by about two months) to get the fix into the ISOs for Ubuntu 22.04.4. -- 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/1471380 Title: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access Status in linux package in Ubuntu: Confirmed Bug description: I've been running pre-installed Windows 7 on a Fujitsu AH532 since 2012. Two weeks back, I installed a Live-USB with Ubuntu 14.04. All working well, but I struggled getting it persistent, so I decided to do a full Ubuntu installation to another USB-drive. Leaving my Windows hard drive untouched. What I did: 1) I entered my "BIOS" to change boot order, and booting from my Ubuntu Live-USB. 2) I tried following the installation guide https://help.ubuntu.com/community/Installation/UEFI-and-BIOS, but sizes were changed to: - 1MB BIOS Boot (pretty sure I left this unformatted,but it now reports as Ext4) - 666MB EFI System, FAT32 - 30GB Linux Filesystem, Ext4 - 999MB Linux Swap, Swap 3) I installed Ubuntu on a second USB-drive. Leaving my Windows hard- drive "intact" (?) The result: Now, I can only boot my machine by inserting my second full-installation-USB-drive. I cannot boot Windows, and I cannot boot from my LiveUSB. If I boot without inserting my full-installation-USB-drive, I get the boot screen telling me I can press F2 or F12. However, none of these have any effect, apart from making the beep. Then the computer enters the "Boot menu" (as well as the second menu "Application menu"). This bug feels very related to: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387 $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-41-generic 3.16.0-41.55~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 4 08:05:03 2015 InstallationDate: Installed on 2015-06-18 (15 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vegard 2045 F...m pulseaudio /dev/snd/controlC0: vegard 2045 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b7bfbfab-671b-471c-ba59-210445db2063 InstallationDate: Installed on 2015-06-18 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK AH532 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed root=UUID=b9d1f4be-275f-4b97-a68a-ccb2afa41781 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr:
[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 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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
** Tags removed: verification-needed-mantic-linux-azure
** Tags added: verification-done-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
** Changed in: linux-azure (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
Fix Committed
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Invalid
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2057936] Re: Azure: hv: hyperv.h: Replace one-element array with flexible-array member
https://lists.ubuntu.com/archives/kernel-team/2024-March/149567.html
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2057936] [NEW] Azure: hv: hyperv.h: Replace one-element array with flexible-array member
Public bug reported:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux-azure (Ubuntu Mantic)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv: hyperv.h: Replace one-element array with flexible-array
member
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
New
Status in linux-azure source package in Mantic:
New
Bug description:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
bb9b0e46b84c19d3dd7d453a2da71a0fdc172b31 ('hv: hyperv.h: Replace one-
element array with flexible-array member')
[Test Plan]
Microsoft tested
[Regression Potential]
This patch could cause seg faults if the logic does not correctly
accommodate a flexible array member.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2057936/+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 2056227] Re: KVM: arm64: softlockups in stage2_apply_range
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056227 Title: KVM: arm64: softlockups in stage2_apply_range Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: [Impact] Tearing down kvm VMs on arm64 can cause softlockups to appear on console. When terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times often exceed 20 seconds, which can trigger the softlockup detector. Portions of the unmap path also have interrupts disabled while tlb invalidation instructions run, which can further contribute to latency problems. My team has observed networking latency problems if the cpu where the teardown is occurring is also mapped to handle a NIC interrupt. Fortunately, a solution has been in place since Linux 6.1. A small pair of patches modify stage2_apply_range to operate on smaller memory ranges before performing a cond_resched. With these patches applied, softlockups are no longer observed when tearing down VMs with large amounts of memory. Although I also submitted the patches to 5.15 LTS (link to LTS submission in "Backport" section), I'd appreciate it if Ubuntu were willing to take this submission in parallel since the impact has left us unable to utilize arm64 for kvm until we can either migrate our hypervisors to hugepages, pick up this fix, or some combination of the two. [Backport] Backport the following fixes from linux 6.1: 3b5c082bbf KVM: arm64: Work out supported block level at compile time 5994bc9e05 KVM: arm64: Limit stage2_apply_range() batch size to largest block The fix is in 5994bc9e05 and 3b5c082bbf is a dependency that was submitted as part of the series. The original submission is here: https://lore.kernel.org/all/20221007234151.461779-1-oliver.up...@linux.dev/ I've also submitted the patches to 5.15 LTS here: https://lore.kernel.org/stable/cover.1709665227.git.k...@templeofstupid.com/ Both fixes cherry picked cleanly and there were no conflicts. [Test] Executed the test from 5994bc9e05 as well as my own run of kvm_page_table_test on a VM with 4k pages and a memory size > 100Gb. Without the patches, softlockups were observed in both tests. With the patches applied, the tests ran without incident. This was tested against both LTS 5.15.150 and linux-aws-5.15.0-1055. [Potential Regression] Regression potential is low. These patches have been present in Linux since 6.1 and appear to have needed no further maintenance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056227/+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 2054855] Re: Azure: Network doesn't get configured after triggering kdump
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2054855 Title: Azure: Network doesn't get configured after triggering kdump Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] The network doesn't get configured after a kdump on some generations of hardware. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a8a8afba0c305 [Test Plan] Microsoft tested. [[Where things could go wrong] You're already in deep doo doo if you have to run kdump. However. not having a network afterwards is a sure sign that this patch doesn't work for your hardware. [Other Info] SF: #00378199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2054855/+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 1471380] Re: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access
A workaround [1] (adapted from the respective mailing list submission [2] with minor edits) has been submitted to mainline Linux and was just released as part of Linux v6.8-rc7. Automatic backports into Linux 6.1, 6.6, and 6.7 are pending. I'll submit separate linux-stable backports for 5.15, 5.10, 5.4, and 4.19 (required due to changed paths) once we get the first stable release on 6.8, that should be ample time for figuring out whether the approach introduces any issues. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f45812cc23fb74bef62d4eb8a69fe7218f4b9f2a [2] https://lore.kernel.org/linux-efi/20240126162524.52051-1-timsch...@gmx.de/ -- 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/1471380 Title: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access Status in linux package in Ubuntu: Confirmed Bug description: I've been running pre-installed Windows 7 on a Fujitsu AH532 since 2012. Two weeks back, I installed a Live-USB with Ubuntu 14.04. All working well, but I struggled getting it persistent, so I decided to do a full Ubuntu installation to another USB-drive. Leaving my Windows hard drive untouched. What I did: 1) I entered my "BIOS" to change boot order, and booting from my Ubuntu Live-USB. 2) I tried following the installation guide https://help.ubuntu.com/community/Installation/UEFI-and-BIOS, but sizes were changed to: - 1MB BIOS Boot (pretty sure I left this unformatted,but it now reports as Ext4) - 666MB EFI System, FAT32 - 30GB Linux Filesystem, Ext4 - 999MB Linux Swap, Swap 3) I installed Ubuntu on a second USB-drive. Leaving my Windows hard- drive "intact" (?) The result: Now, I can only boot my machine by inserting my second full-installation-USB-drive. I cannot boot Windows, and I cannot boot from my LiveUSB. If I boot without inserting my full-installation-USB-drive, I get the boot screen telling me I can press F2 or F12. However, none of these have any effect, apart from making the beep. Then the computer enters the "Boot menu" (as well as the second menu "Application menu"). This bug feels very related to: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387 $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-41-generic 3.16.0-41.55~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 4 08:05:03 2015 InstallationDate: Installed on 2015-06-18 (15 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vegard 2045 F...m pulseaudio /dev/snd/controlC0: vegard 2045 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b7bfbfab-671b-471c-ba59-210445db2063 InstallationDate: Installed on 2015-06-18 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK AH532 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed root=UUID=b9d1f4be-275f-4b97-a68a-ccb2afa41781 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to:
[Kernel-packages] [Bug 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052980] Re: Azure: cifs modules missing from the linux-modules package
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052980 Title: Azure: cifs modules missing from the linux-modules package Status in linux-azure package in Ubuntu: Fix Released Bug description: SRU Justification [Impact] The source layout of cifs has changed from fs/cifs to fs/smb/client. Therefore the modules has gone missing from linux-modules, but can be found in linux-modules-extra. [Fix] Add fs/smb/* to the inclusion list (debian.azure/control.d/azure.inclusion-list). [Test Plan] List files in the linux-modules package and verify that cifs.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052980/+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 2054855] [NEW] Azure: Network doesn't get configured after triggering kdump
Public bug reported: SRU Justification [Impact] The network doesn't get configured after a kdump on some generations of hardware. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a8a8afba0c305 [Test Plan] Microsoft tested. [[Where things could go wrong] You're already in deep doo doo if you have to run kdump. However. not having a network afterwards is a sure sign that this patch doesn't work for your hardware. [Other Info] SF: #00378199 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2054855 Title: Azure: Network doesn't get configured after triggering kdump Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] The network doesn't get configured after a kdump on some generations of hardware. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a8a8afba0c305 [Test Plan] Microsoft tested. [[Where things could go wrong] You're already in deep doo doo if you have to run kdump. However. not having a network afterwards is a sure sign that this patch doesn't work for your hardware. [Other Info] SF: #00378199 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2054855/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2027615] Re: Azure: MANA: Fix doorbell access for receives
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+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 2052519] Re: Azure: Fix TDX regressions in Azure 6.5
** Tags removed: verification-needed-mantic-linux-azure ** Tags added: verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052519 Title: Azure: Fix TDX regressions in Azure 6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052519/+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 2036600] Re: Azure: Fix Azure vendor ID
** Tags removed: verification-needed-jammy-linux-aws-6.5
verification-needed-jammy-linux-gcp-6.5
** Tags added: verification-done-jammy-linux-aws-6.5
verification-done-jammy-linux-gcp-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Fix Released
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
VMs could be misclassified.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
** Tags removed: verification-needed-jammy-linux-aws-6.5
** Tags added: verification-done-jammy-linux-aws-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
Fix Committed
Status in linux-aws source package in Mantic:
Fix Released
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2052453] Re: Azure: Fix regression introduced in LP: #2045069
** Tags removed: verification-needed-jammy-linux-azure verification-needed-mantic-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052453 Title: Azure: Fix regression introduced in LP: #2045069 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052453/+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] [NEW] Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
Public bug reported: 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) ** Affects: linux-signed-gcp-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-hook-error focal uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp-5.15 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-signed-gcp-5.15 package in Ubuntu: New 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
[Kernel-packages] [Bug 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052980] [NEW] Azure: cifs modules missing from the linux-modules package
Public bug reported: SRU Justification [Impact] The source layout of cifs has changed from fs/cifs to fs/smb/client. Therefore the modules has gone missing from linux-modules, but can be found in linux-modules-extra. [Fix] Add fs/smb/* to the inclusion list (debian.azure/control.d/azure.inclusion-list). [Test Plan] List files in the linux-modules package and verify that cifs.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052980 Title: Azure: cifs modules missing from the linux-modules package Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] The source layout of cifs has changed from fs/cifs to fs/smb/client. Therefore the modules has gone missing from linux-modules, but can be found in linux-modules-extra. [Fix] Add fs/smb/* to the inclusion list (debian.azure/control.d/azure.inclusion-list). [Test Plan] List files in the linux-modules package and verify that cifs.ko is there. [Regression potential] The regression potential is very low since we are provably moving a module to its original package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052980/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
https://lists.ubuntu.com/archives/kernel-team/2024-February/148724.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] Re: Azure: Enable CONFIG_TEST_LOCKUP
** Changed in: linux-azure (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052723] [NEW] Azure: Enable CONFIG_TEST_LOCKUP
Public bug reported: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Mantic) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Noble) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Noble) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052723 Title: Azure: Enable CONFIG_TEST_LOCKUP Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Status in linux-azure source package in Noble: In Progress Bug description: SRU Justification [Impact] Microsoft has requested that CONFIG_TEST_LOCKUP be enabled in order to assist with testing watchdogs and lockup detectors when troubleshooting these issues with customers. [Test Plan] insmod test_lockup.ko [Regression Potential] This module does not stay installed, but could leave orphaned memory or other bad states. [Other Info] SF: #00378840 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052723/+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 2052519] Re: Azure: Fix TDX regressions in Azure 6.5
** Changed in: linux-azure (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052519 Title: Azure: Fix TDX regressions in Azure 6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052519/+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 2052519] Re: Azure: Fix TDX regressions in Azure 6.5
https://lists.ubuntu.com/archives/kernel-team/2024-February/148660.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052519 Title: Azure: Fix TDX regressions in Azure 6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052519/+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 2052519] [NEW] Azure: Fix TDX regressions in Azure 6.5
Public bug reported: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Mantic) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052519 Title: Azure: Fix TDX regressions in Azure 6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] TDX support in Microsoft Azure kernels based on 6.5 has regressed from 6.2. Microsoft has provided a backport that brings TDX functionality back to that of Azure 6.2. [Test Case] Microsoft tested [Regression Potential] TDX support has been backported from Linux v6.6, so there could be some lingering issues. [Other Information] SF: #00378027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052519/+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 2052453] Re: Azure: Fix regression introduced in LP: #2045069
** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-azure (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052453 Title: Azure: Fix regression introduced in LP: #2045069 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052453/+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 2052453] [NEW] Azure: Fix regression introduced in LP: #2045069
Public bug reported: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2052453 Title: Azure: Fix regression introduced in LP: #2045069 Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] Microsoft requested the addition of 3 patches in LP: #2045069. A regression was discovered in Focal. [Fix] hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove [Test Case] Microsoft tested [Regression Potential] hv_netvsc could still have a modprobe race. [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2052453/+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 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2039208 Title: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
** Tags removed: verification-needed-jammy-linux-azure verification-needed-mantic-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
** Tags removed: verification-needed-mantic-linux-aws
** Tags added: verification-done-mantic-linux-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
Fix Committed
Status in linux-aws source package in Mantic:
Fix Committed
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Changed in: linux (Ubuntu Mantic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+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 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
** Changed in: linux (Ubuntu) Status: Expired => 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/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access Status in linux package in Ubuntu: Confirmed Bug description: :~$ apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-22 Candidate: 2.00-22 EFI installation of Ubuntu clears out the boot entries in firmware leaving user with no option but boot Ubuntu. Pressing (F2) to enter BIOS Setup has no effect as does pressing (F12) for Boot Order. The only way to get back firmware access is to flash the bios using manufacturer provided utilities. Unfortunately Fujitsu doesn't provide a BIOS flash utility for Linux/Ubuntu. It is to be noted that installed Windows in EFI mode on the same system does not clear out firmware access but just adds the 'Windows Boot Loader' entry at the top of the boot sequence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: satish 1852 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 27 11:06:37 2014 HibernationDevice: RESUME=UUID=c73dc7d0-4253-44fa-9589-d8c91c9cac13 InstallationDate: Installed on 2014-01-26 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) MachineType: FUJITSU LIFEBOOK LH532 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=efd53305-1eac-42ba-b3f9-828b72cb5560 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1E dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+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 1471380] Re: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access
I tracked this down to a bunch of edge-cases in Fujitsu's UEFI implementation, the Linux kernel, and efibootmgr. The method of restoring access by doing a CMOS-reset (shorting the CL1_CL2 test point) and flashing the BIOS [1] was already known, but I also created a tool [2] that is supposed to restore all relevant settings from within a running Linux installation. Please do make note of the list of supported configurations and of the disclaimer. A proper kernel-side fix is pending, but it will take some time to land in mainline Linux, linux-stable and the Ubuntu kernel tree respectively. [1] https://support.ts.fujitsu.com/ [2] https://github.com/timschumi/ah532-biostools/ -- 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/1471380 Title: [Fujitsu Lifebook AH532] Installing Ubuntu on a USB-drive locks out firmware access Status in linux package in Ubuntu: Expired Bug description: I've been running pre-installed Windows 7 on a Fujitsu AH532 since 2012. Two weeks back, I installed a Live-USB with Ubuntu 14.04. All working well, but I struggled getting it persistent, so I decided to do a full Ubuntu installation to another USB-drive. Leaving my Windows hard drive untouched. What I did: 1) I entered my "BIOS" to change boot order, and booting from my Ubuntu Live-USB. 2) I tried following the installation guide https://help.ubuntu.com/community/Installation/UEFI-and-BIOS, but sizes were changed to: - 1MB BIOS Boot (pretty sure I left this unformatted,but it now reports as Ext4) - 666MB EFI System, FAT32 - 30GB Linux Filesystem, Ext4 - 999MB Linux Swap, Swap 3) I installed Ubuntu on a second USB-drive. Leaving my Windows hard- drive "intact" (?) The result: Now, I can only boot my machine by inserting my second full-installation-USB-drive. I cannot boot Windows, and I cannot boot from my LiveUSB. If I boot without inserting my full-installation-USB-drive, I get the boot screen telling me I can press F2 or F12. However, none of these have any effect, apart from making the beep. Then the computer enters the "Boot menu" (as well as the second menu "Application menu"). This bug feels very related to: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060 - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1451387 $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-41-generic 3.16.0-41.55~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 4 08:05:03 2015 InstallationDate: Installed on 2015-06-18 (15 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vegard 2045 F...m pulseaudio /dev/snd/controlC0: vegard 2045 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=b7bfbfab-671b-471c-ba59-210445db2063 InstallationDate: Installed on 2015-06-18 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK AH532 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed root=UUID=b9d1f4be-275f-4b97-a68a-ccb2afa41781 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-41-generic N/A linux-backports-modules-3.16.0-41-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.16.0-41-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to:
[Kernel-packages] [Bug 1451387] Re: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode
I tracked this down to a bunch of edge-cases in Fujitsu's UEFI implementation, the Linux kernel, and efibootmgr. The method of restoring access by doing a CMOS-reset (shorting the CL1_CL2 test point) and flashing the BIOS [1] was already known, but I also created a tool [2] that is supposed to restore all relevant settings from within a running Linux installation. Please do make note of the list of supported configurations and of the disclaimer. A proper kernel-side fix is pending, but it will take some time to land in mainline Linux, linux-stable and the Ubuntu kernel tree respectively. [1] https://support.ts.fujitsu.com/ [2] https://github.com/timschumi/ah532-biostools/ -- 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/1451387 Title: [Fujitsu LIFEBOOK LH532] UEFI firmware becomes locked after installing Ubuntu in UEFI mode Status in linux package in Ubuntu: Confirmed Bug description: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418/comments/74 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 4 16:57:39 2015 InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut1480 F pulseaudio rut7079 F pulseaudio DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=d4bb392e-90ed-41a3-9d30-fa457fefb25b InstallationDate: Installed on 2010-01-01 (1949 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed root=UUID=e8258103-326b-4708-b64f-6306d0eb0a01 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-30-generic N/A linux-backports-modules-3.16.0-30-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.16.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1F dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1F:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rut2207 F pulseaudio DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=8fd2670c-4060-4d14-8f27-b9f806fe2ce7 InstallationDate: Installed on 2015-05-06 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: FUJITSU LIFEBOOK LH532 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=3129a485-81a2-48ef-be95-ef9c9a57be3e ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/24/2012
[Kernel-packages] [Bug 1273060] Re: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
I tracked this down to a bunch of edge-cases in Fujitsu's UEFI implementation, the Linux kernel, and efibootmgr. The method of restoring access by doing a CMOS-reset (shorting the CL1_CL2 test point) and flashing the BIOS [1] was already known, but I also created a tool [2] that is supposed to restore all relevant settings from within a running Linux installation. Please do make note of the list of supported configurations and of the disclaimer. A proper kernel-side fix is pending, but it will take some time to land in mainline Linux, linux-stable and the Ubuntu kernel tree respectively. [1] https://support.ts.fujitsu.com/ [2] https://github.com/timschumi/ah532-biostools/ -- 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/1273060 Title: [Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access Status in linux package in Ubuntu: Expired Bug description: :~$ apt-cache policy grub-efi-amd64 grub-efi-amd64: Installed: 2.00-22 Candidate: 2.00-22 EFI installation of Ubuntu clears out the boot entries in firmware leaving user with no option but boot Ubuntu. Pressing (F2) to enter BIOS Setup has no effect as does pressing (F12) for Boot Order. The only way to get back firmware access is to flash the bios using manufacturer provided utilities. Unfortunately Fujitsu doesn't provide a BIOS flash utility for Linux/Ubuntu. It is to be noted that installed Windows in EFI mode on the same system does not clear out firmware access but just adds the 'Windows Boot Loader' entry at the top of the boot sequence. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-5-generic 3.13.0-5.20 [modified: boot/vmlinuz-3.13.0-5-generic] ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: satish 1852 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 27 11:06:37 2014 HibernationDevice: RESUME=UUID=c73dc7d0-4253-44fa-9589-d8c91c9cac13 InstallationDate: Installed on 2014-01-26 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) MachineType: FUJITSU LIFEBOOK LH532 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=efd53305-1eac-42ba-b3f9-828b72cb5560 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-5-generic N/A linux-backports-modules-3.13.0-5-generic N/A linux-firmware1.122 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.10 dmi.board.name: FJNBB1E dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.10:bd05/24/2012:svnFUJITSU:pnLIFEBOOKLH532:pvr:rvnFUJITSU:rnFJNBB1E:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK LH532 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060/+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 2050885] [NEW] hd will not mount
Public bug reported:
I now have two hd that will not work on linux but work on window 11 .
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tlr2004 F wireplumber
/dev/snd/seq:tlr1987 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 06:03:16 2024
HotplugNewDevices:
HotplugNewMounts:
InstallationDate: Installed on 2023-11-13 (71 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=88481562-dc81-4d92-bc63-a1c80eeb6605 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
Symptom: storage
UdisksMonitorLog:
Monitoring the udisks daemon. Press Ctrl+C to exit.
06:03:39.779: The udisks-daemon is running (name-owner :1.8).
UpgradeStatus: Upgraded to mantic on 2024-01-22 (1 days ago)
dmi.bios.date: 07/03/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: JB20B001
dmi.board.asset.tag: Default string
dmi.board.name: JB20B
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB20B001:bd07/03/2023:br5.19:efr1.2:svnDefaultstring:pnJB20B:pvrDefaultstring:rvnDefaultstring:rnJB20B:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU1:
dmi.product.family: MiniPC
dmi.product.name: JB20B
dmi.product.sku: SKU1
dmi.product.version: Default string
dmi.sys.vendor: Default string
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
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/2050885
Title:
hd will not mount
Status in linux package in Ubuntu:
New
Bug description:
I now have two hd that will not work on linux but work on window 11 .
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tlr2004 F wireplumber
/dev/snd/seq:tlr1987 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 06:03:16 2024
HotplugNewDevices:
HotplugNewMounts:
InstallationDate: Installed on 2023-11-13 (71 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=88481562-dc81-4d92-bc63-a1c80eeb6605 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-14-generic N/A
linux-backports-modules-6.5.0-14-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
Symptom: storage
UdisksMonitorLog:
Monitoring the udisks daemon. Press Ctrl+C to exit.
06:03:39.779: The udisks-daemon is running (name-owner :1.8).
UpgradeStatus: Upgraded to mantic on 2024-01-22 (1 days ago)
dmi.bios.date: 07/03/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: JB20B001
dmi.board.asset.tag: Default string
dmi.board.name: JB20B
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrJB20B001:bd07/03/2023:br5.19:efr1.2:svnDefaultstring:pnJB20B:pvrDefaultstring:rvnDefaultstring:rnJB20B:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU1:
dmi.product.family: MiniPC
dmi.product.name: JB20B
dmi.product.sku: SKU1
[Kernel-packages] [Bug 2041668] Re: Memory leak in 23.10 kernel (6.5.0-10)
** Also affects: linux-meta-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041668 Title: Memory leak in 23.10 kernel (6.5.0-10) Status in linux package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: There appears to be a memory 'leak' in the kernel of the latest Ubuntu release (Mantic Minotaur, kernel version 6.5.0-10). I put 'leak' in quotes because this memory appears to be allocated but never used. The kernel's memory over-commit mechanism seems to prevent this leak from manifesting in OOM killer triggers or other failures. The primary symptom is a steady increase in the value reported as 'Committed_AS' in '/proc/meminfo'. The other memory stats reported there remain reasonable, though. I've observed this problem on a fairly diverse set of machines (both VMs and physical machines) with a variety of workloads. Busier machines seem to have a faster leak rate. I've tried to narrow down the issue by rebooting into single user mode, killing all userspace processes (except the systemd processes) and removing as many kernel models as possible. The problem continues in that state. I didn't see any obvious culprits in /proc/slabinfo nor /proc/vmallocinfo. So far, the only way I've been able to remediate this issue is to reboot back into the Lunar Lobster kernel (6.2.0-35). I think this fact alone rules out any triggers that may be part of the 23.10 userspace environment. I've attached the generic debug info requested by this component's bug template from an example machine. Please let me know if there is any more information I can provide. It seems to be pretty trivial to reproduce though, and I'm guessing it has not been reported yet because the leak doesn't actually manifest in an out-of-memory situation. At least, I haven't observed that yet. The worst case I've observed was 150 GB of memory committed on a machine with 16 GB of physical RAM after about 24 hours. Moving back to the previous kernel version, the committed memory statistic holds fairly steady around 7 GB on that machine and workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041668/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
** Changed in: linux-aws (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
Fix Committed
Status in linux-aws source package in Mantic:
Fix Committed
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2048404] Re: Don't WARN_ON_ONCE() for a broken discovery table
https://lists.ubuntu.com/archives/kernel-team/2024-January/147974.html
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/2048404
Title:
Don't WARN_ON_ONCE() for a broken discovery table
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Bug description:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore:
Don't WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has
been changed.
[Other Info]
SF: #00347830
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048404/+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 2048404] [NEW] Don't WARN_ON_ONCE() for a broken discovery table
Public bug reported:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore: Don't
WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has been
changed.
[Other Info]
SF: #00347830
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Description changed:
SRU Justification
- [Impacy]
+ [Impact]
- perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
-
- The kernel warning message is triggered, when SPR MCC is used.
-
- [ 17.945331] [ cut here ]
- [ 17.946305] WARNING: CPU: 65 PID: 1 at
- arch/x86/events/intel/uncore_discovery.c:184
- intel_uncore_has_discovery_tables+0x4c0/0x65c
- [ 17.946305] Modules linked in:
- [ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
- 5.4.17-2136.313.1-X10-2c+ #4
-
- It's caused by the broken discovery table of UPI.
-
- The discovery tables are from hardware. Except for dropping the broken
- information, there is nothing Linux can do. Using WARN_ON_ONCE() is
- overkilled.
-
- Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
- is dropped and the reason.
+ perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
+
+ The kernel warning message is triggered, when SPR MCC is used.
+
+ [ 17.945331] [ cut here ]
+ [ 17.946305] WARNING: CPU: 65 PID: 1 at
+ arch/x86/events/intel/uncore_discovery.c:184
+ intel_uncore_has_discovery_tables+0x4c0/0x65c
+ [ 17.946305] Modules linked in:
+ [ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
+ 5.4.17-2136.313.1-X10-2c+ #4
+
+ It's caused by the broken discovery table of UPI.
+
+ The discovery tables are from hardware. Except for dropping the broken
+ information, there is nothing Linux can do. Using WARN_ON_ONCE() is
+ overkilled.
+
+ Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
+ is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore: Don't
WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has been
changed.
[Other Info]
SF: #00347830
--
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/2048404
Title:
Don't WARN_ON_ONCE() for a broken discovery table
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Bug description:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit
[Kernel-packages] [Bug 2030978] Re: kernel 6.5 changes cause UBSAN errors (patch included)
I build me own kernel now and removed all UBSAN-stuff. This helped.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2030978
Title:
kernel 6.5 changes cause UBSAN errors (patch included)
Status in broadcom-sta package in Ubuntu:
Confirmed
Bug description:
"On Linux 6.5, due to commit 2d47c6956ab3 ("ubsan: Tighten UBSAN_BOUNDS
on GCC"), flexible trailing arrays declared like `whatever_t foo[1];`
will generate warnings when CONFIG_UBSAN & co. is enabled."
Due to changes in kernel 6.5, we get this error in dmesg:
[ 28.818756]
[ 28.822952] UBSAN: array-index-out-of-bounds in
/var/lib/dkms/broadcom-wl/6.30.223.271/build/src/wl/sys/wl_linux.c:1938:4
[ 28.82] index 2 is out of range for type 'ether_addr [1]'
[ 28.832900] CPU: 1 PID: 1232 Comm: avahi-daemon Tainted: P OE
6.5.0-rc4 #1
[ 28.836452] Hardware name: Apple Inc. MacBookPro11,3/Mac-2BD1B31983FE1663,
BIOS 432.60.3.0.0 10/27/2021
[ 28.839806] Call Trace:
[ 28.843091]
[ 28.846387] dump_stack_lvl+0x48/0x60
[ 28.849692] dump_stack+0x10/0x20
[ 28.852965] __ubsan_handle_out_of_bounds+0xc6/0x100
[ 28.856251] _wl_set_multicast_list+0x1fd/0x220 [wl]
[ 28.859191] wl_set_multicast_list+0x3a/0x80 [wl]
[ 28.861879] __dev_set_rx_mode+0x6a/0xc0
[ 28.864237] __dev_mc_add+0x82/0x90
[ 28.866587] dev_mc_add+0x10/0x20
[ 28.868920] igmp_group_added+0x198/0x1d0
[ 28.871102] ip_mc_inc_group+0x185/0x2b0
[ 28.873231] __ip_mc_join_group+0x108/0x170
[ 28.875170] ip_mc_join_group+0x10/0x20
[ 28.877111] do_ip_setsockopt+0x104d/0x1160
[ 28.878894] ? __sys_setsockopt+0xeb/0x1c0
[ 28.880657] ip_setsockopt+0x30/0xb0
[ 28.882326] udp_setsockopt+0x22/0x40
[ 28.883949] sock_common_setsockopt+0x14/0x20
[ 28.885554] __sys_setsockopt+0xde/0x1c0
[ 28.887063] __x64_sys_setsockopt+0x1f/0x30
[ 28.888564] do_syscall_64+0x55/0x80
[ 28.889952] ? syscall_exit_to_user_mode+0x26/0x40
[ 28.891226] ? __x64_sys_recvmsg+0x1d/0x20
[ 28.892450] ? do_syscall_64+0x61/0x80
[ 28.893651] ? do_syscall_64+0x61/0x80
[ 28.894796] entry_SYSCALL_64_after_hwframe+0x46/0xb0
[ 28.895942] RIP: 0033:0x7f0a97a7ddae
[ 28.897100] Code: 0f 1f 40 00 48 8b 15 69 60 0d 00 f7 d8 64 89 02 48 c7 c0
ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 49 89 ca b8 36 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 31
[ 28.898270] RSP: 002b:7fffb7b1b3f8 EFLAGS: 0246 ORIG_RAX:
0036
[ 28.899449] RAX: ffda RBX: 000c RCX:
7f0a97a7ddae
[ 28.900623] RDX: 0023 RSI: RDI:
000c
[ 28.901784] RBP: 0001 R08: 000c R09:
0004
[ 28.902895] R10: 7fffb7b1b404 R11: 0246 R12:
7fffb7b1b404
[ 28.904011] R13: 0014 R14: 55cc506ee078 R15:
55cc506eaf60
[ 28.905149]
[ 28.906228]
A patch is however available for this issue:
https://gist.github.com/joanbm/9cd5fda1dcfab9a67b42cc6195b7b269
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: bcmwl-kernel-source (not installed)
Uname: Linux 6.5.0-rc4 x86_64
NonfreeKernelModules: wl zfs
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Aug 10 10:40:27 2023
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: broadcom-sta
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2030978/+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 2042568] Re: Azure - Kernel crashes when removing gpu from pci
** Changed in: linux-azure (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: Confirmed => Fix Committed ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2042568 Title: Azure - Kernel crashes when removing gpu from pci Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: [Description] On a VM on Azure with a Tesla gpu it was noticed that when removing the gpu from the pci the vm would crash. In case the nvidia drivers are loaded, the machine won't crash. Instead the removing process will hang and the machine will crash on reboot. This is related to bug [1]. The bug reported in [1] regards another driver but the root cause is the same. It is still investigated whether this is a bug in pci, or it is a bug of various drivers on how they use pci. For this case we have identified that removing commit [2] prevents the kernel crashes. Azure has requested to revert this commit, at least for the time being. This commit is not in upstream, so it just need to be reverted from Ubuntu kernels. [Test Case] On an Azure vm with a gpu : # echo '1' > /sys/bus/pci/devices/0001:00:00.0/remove where '0001:00:00.0' the pci address of the gpu. The vm will crash. [Where things could go wrong] The commit to be reverted was included in a patchset to address lp bugs https://bugs.launchpad.net/bugs/2023071 and https://bugs.launchpad.net/bugs/2023594 However this commit just reduces boot time and removing shall not introduce any regressions. Side effects will be increase in the boot time. [Other] Only Ubuntu azure kernels are affected : - Jammy 5.15 - Lunar 6.2 Focal is also affected since it's using 5.15 kernel. This commit does not appear in Mantic 6.5 kernel. [1] https://bugzilla.kernel.org/show_bug.cgi?id=215515 [2] https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/jammy/commit/?h=Ubuntu-azure-5.15.0-1043.50=75af0c10b3703400890d314d1d91d25294234a81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042568/+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 2042546] Re: Include cifs.ko in linux-modules package
** Tags removed: verification-needed-lunar-linux-aws verification-needed-lunar-linux-azure ** Tags added: verification-done-lunar-linux-aws verification-done-lunar-linux-azure -- 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/2042546 Title: Include cifs.ko in linux-modules package Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: [Impact] Commit: "smb: move client and server files to common directory fs/smb" introduced in 2023.09.04 moved the fs/cifs directory to fs/sb/client. The inclusion list for linux-modules was not updated, it still contains the old path. This means that the cifs.ko module cannot be loaded if only linux-modules package is installed, now being part of linux-modules-extra. For lunar:main this is not a problem because linux-modules-extra is always installed, but for derivatives like aws, azure etc, this module cannot be loaded without explicitly installing linux-modules-extra. [How to reproduce it]: 1. Install the latest azure kernel 6.2.0-1016.16 2. Load cifs module $ modprobe cifs modprobe: FATAL: Module cifs not found in directory /lib/modules/6.2.0-1016-azure If modules-extra is installed, this works. [Fix] Replace fs/cifs/* with fs/smb/client/* in debian./control.d/.inclusiojn-list This is going to be done in s2023.10.02 cycle for derivatives. [Test Plan] 1. Apply the fix to one of the derivative (azure), build a new kernel and install it 2. Load cifs module $ modprobe cifs It should work without installing modules-extra. [Regression potential] Very low, it's a straightforward fix. [Other Info] Sending a patch for every derivative takes time and each derivative will be fixed once this proposal is acked. There is also the possibility to do it via cranky fix, but owners may omit it during security updates and it's hard to enforce it. Plus, it is a one-time change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042546/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
https://lists.ubuntu.com/archives/kernel-team/2023-December/147391.html
** Description changed:
SRU Justification
[Impact]
- A stable update from LP: #1853180 was carried forward to the Lunar 6.2
- and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
+ An update from LP: #1853180 was carried forward to the Lunar 6.2 and
+ Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
** Changed in: linux-aws (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
In Progress
Status in linux-aws source package in Mantic:
In Progress
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2045428] [NEW] AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Public bug reported:
SRU Justification
[Impact]
A stable update from LP: #1853180 was carried forward to the Lunar 6.2
and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
** Affects: linux-aws (Ubuntu)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Lunar)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Mantic)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Noble)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Package changed: linux (Ubuntu) => linux-aws (Ubuntu)
** Description changed:
SRU Justification
[Impact]
A stable update from LP: #1853180 was carried forward to the Lunar 6.2
- kernel. As it did not cause a conflict it likely escaped notice when the
- Jammy AWS kernel was forward ported. Commit
+ and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
+ notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
** Also affects: linux-aws (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Noble)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-aws source package in Lunar:
In Progress
Status in linux-aws source package in Mantic:
In Progress
Status in linux-aws source package in Noble:
In Progress
Bug description:
SRU Justification
[Impact]
A stable update from LP: #1853180 was carried forward to the Lunar 6.2
and Mantic 6.5 kernels. As it did not cause a conflict it likely
escaped notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2039208 Title: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2044192] Re: Patches needed for AmpereOne (arm64)
** Changed in: linux-gcp (Ubuntu)
Status: New => Fix Released
** Changed in: linux-gcp (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu Focal)
Assignee: (unassigned) => John Cabaj (john-cabaj)
** Changed in: linux-gcp (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu Jammy)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
In Progress
Status in linux-gcp source package in Jammy:
In Progress
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 and Focal 5.4 for now
* Cherry-picks from upstream
0e5d5ae837c8 ("arm64: Add AMPERE1 to the Spectre-BHB affected list")
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested
* To be tested by Google
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2044192/+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 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: Fix Committed Status in linux-kvm package in Ubuntu: Invalid Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: Fix Committed Status in linux-kvm source package in Mantic: Invalid Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_INTEGRITY_MACHINE_KEYRING CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring implementation is patched to skip the check enabled by this kconfig) (The latter two are needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To verify whether this works, add a certificate to MOK, boot and check the content of the secondary keyring. The machine keyring should show up under it, and it should show the certificates loaded in MOK. E.g.: $ sudo keyctl show %:.secondary_trusted_keys Keyring 159454604 ---lswrv 0 0 keyring: .secondary_trusted_keys 88754641 ---lswrv 0 0 \_ keyring: .builtin_trusted_keys 889010778 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 799434660 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f 541326986 ---lswrv 0 0 \_ keyring: .machine 188508854 ---lswrv 0 0 \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 475039424 ---lswrv 0 0 \_ asymmetric: sb-bluca: Secure Boot Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479 [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2019040] Re: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2019040 Title: linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images Status in linux package in Ubuntu: Fix Committed Status in linux-kvm package in Ubuntu: Invalid Status in linux-meta-azure package in Ubuntu: Invalid Status in linux-meta-kvm package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Status in linux-meta-azure source package in Jammy: Invalid Status in linux-meta-kvm source package in Jammy: New Status in linux source package in Kinetic: Fix Committed Status in linux-kvm source package in Kinetic: In Progress Status in linux-meta-azure source package in Kinetic: Invalid Status in linux-meta-kvm source package in Kinetic: New Status in linux source package in Lunar: Fix Released Status in linux-kvm source package in Lunar: Fix Released Status in linux-meta-azure source package in Lunar: New Status in linux-meta-kvm source package in Lunar: New Status in linux source package in Mantic: Fix Committed Status in linux-kvm source package in Mantic: Invalid Status in linux-meta-azure source package in Mantic: Invalid Status in linux-meta-kvm source package in Mantic: Invalid Bug description: SRU Justification [Impact] The kvm flavours currently do not enable dm-verity. This stops us from using integrity protected and verified images in VMs using this kernel flavour. [Fix] Please consider enabling the following kconfigs: CONFIG_DM_VERITY CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING CONFIG_INTEGRITY_MACHINE_KEYRING CONFIG_IMA_ARCH_POLICY (this might not be necessary if the machine keyring implementation is patched to skip the check enabled by this kconfig) (The latter two are needed to ensure that MoK keys can be used to verify dm-verity images too, via the machine keyring linked to the secondary keyring) These are already enabled in the 'main' kernel config, and in other distros. As a specific and explicit use case, in the systemd project we want to test functionality provided by systemd that needs these kconfigs on Ubuntu machines running the kvm flavour kernel. To verify whether this works, add a certificate to MOK, boot and check the content of the secondary keyring. The machine keyring should show up under it, and it should show the certificates loaded in MOK. E.g.: $ sudo keyctl show %:.secondary_trusted_keys Keyring 159454604 ---lswrv 0 0 keyring: .secondary_trusted_keys 88754641 ---lswrv 0 0 \_ keyring: .builtin_trusted_keys 889010778 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 799434660 ---lswrv 0 0 | \_ asymmetric: Debian Secure Boot Signer 2022 - linux: 14011249c2675ea8e5148542202005810584b25f 541326986 ---lswrv 0 0 \_ keyring: .machine 188508854 ---lswrv 0 0 \_ asymmetric: Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1 475039424 ---lswrv 0 0 \_ asymmetric: sb-bluca: Secure Boot Signing: 9a61c52d07d78a76935e67bdbe3f5e6968d62479 [Regression Potential] MOK keys may not be correctly read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019040/+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 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
https://lists.ubuntu.com/archives/kernel-team/2023-November/147282.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2045069 Title: Azure: Deprecate Netvsc and implement MANA direct Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked for the inclusion of 3 patches that deprecate the use of netvsc in favor of MANA direct. hv_netvsc: Mark VF as slave before exposing it to user-mode: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8 hv_netvsc: Fix race of register_netdevice_notifier and VF register: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db hv_netvsc: fix race of netvsc and VF register_netdevice: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837 [Test Plan] Microsoft tested [Regression potential] User space that relies on netvsc will likely fail [Other Info] SF: #00374570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2045069] [NEW] Azure: Deprecate Netvsc and implement MANA direct
Public bug reported:
SRU Justification
[Impact]
Microsoft has asked for the inclusion of 3 patches that deprecate the
use of netvsc in favor of MANA direct.
hv_netvsc: Mark VF as slave before exposing it to user-mode:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8
hv_netvsc: Fix race of register_netdevice_notifier and VF register:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db
hv_netvsc: fix race of netvsc and VF register_netdevice:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837
[Test Plan]
Microsoft tested
[Regression potential]
User space that relies on netvsc will likely fail
[Other Info]
SF: #00374570
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-azure (Ubuntu Jammy)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-azure (Ubuntu Lunar)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-azure (Ubuntu Mantic)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2045069
Title:
Azure: Deprecate Netvsc and implement MANA direct
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Status in linux-azure source package in Lunar:
In Progress
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
Microsoft has asked for the inclusion of 3 patches that deprecate the
use of netvsc in favor of MANA direct.
hv_netvsc: Mark VF as slave before exposing it to user-mode:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=c807d6cd089d2f4951baa838081ec5ae3e2360f8
hv_netvsc: Fix race of register_netdevice_notifier and VF register:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=85520856466ed6bc3b1ccb013cddac70ceb437db
hv_netvsc: fix race of netvsc and VF register_netdevice:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/hyperv?id=d30fb712e52964f2cf9a9c14cf67078394044837
[Test Plan]
Microsoft tested
[Regression potential]
User space that relies on netvsc will likely fail
[Other Info]
SF: #00374570
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2045069/+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 2043841] Re: kernel BUG: io_uring openat triggers audit reference count underflow
** Package changed: linux-azure-6.2 (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/2043841
Title:
kernel BUG: io_uring openat triggers audit reference count underflow
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
In Progress
Bug description:
I first encountered a bug in 6.2.0-1012-azure #12~22.04.1-Ubuntu that
occurs during io_uring openat audit processing. I have a kernel patch
that was accepted into the upstream kernel as well as the v6.6,
v6.5.9, and v6.1.60 releases. The bug was first introduced in the
upstream v5.16 kernel.
I do not see the change yet in:
* The Ubuntu-azure-6.2-6.2.0-1017.17_22.04.1 tag in the jammy kernel
repository.
* The Ubuntu-azure-6.5.0-1009.9 tag in the mantic kernel repository.
Can this upstream commit be cherry picked?
The upstream commit is:
03adc61edad49e1bbecfb53f7ea5d78f398fe368
The upstream patch thread is:
https://lore.kernel.org/audit/20231012215518.ga4...@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#u
The maintainer pull request thread is:
https://lore.kernel.org/lkml/20231019-kampfsport-
metapher-e5211d7be247@brauner
The pre-patch discussion thread is:
https://lore.kernel.org/io-
uring/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/T/#u
The commit log message is:
commit 03adc61edad49e1bbecfb53f7ea5d78f398fe368
Author: Dan Clash
Date: Thu Oct 12 14:55:18 2023 -0700
audit,io_uring: io_uring openat triggers audit reference count
underflow
An io_uring openat operation can update an audit reference count
from multiple threads resulting in the call trace below.
A call to io_uring_submit() with a single openat op with a flag of
IOSQE_ASYNC results in the following reference count updates.
These first part of the system call performs two increments that
do not race.
do_syscall_64()
__do_sys_io_uring_enter()
io_submit_sqes()
io_openat_prep()
__io_openat_prep()
getname()
getname_flags() /* update 1 (increment) */
__audit_getname() /* update 2 (increment) */
The openat op is queued to an io_uring worker thread which starts the
opportunity for a race. The system call exit performs one decrement.
do_syscall_64()
syscall_exit_to_user_mode()
syscall_exit_to_user_mode_prepare()
__audit_syscall_exit()
audit_reset_context()
putname() /* update 3 (decrement) */
The io_uring worker thread performs one increment and two decrements.
These updates can race with the system call decrement.
io_wqe_worker()
io_worker_handle_work()
io_wq_submit_work()
io_issue_sqe()
io_openat()
io_openat2()
do_filp_open()
path_openat()
__audit_inode() /* update 4 (increment) */
putname() /* update 5 (decrement) */
__audit_uring_exit()
audit_reset_context()
putname() /* update 6 (decrement) */
The fix is to change the refcnt member of struct audit_names
from int to atomic_t.
kernel BUG at fs/namei.c:262!
Call Trace:
...
? putname+0x68/0x70
audit_reset_context.part.0.constprop.0+0xe1/0x300
__audit_uring_exit+0xda/0x1c0
io_issue_sqe+0x1f3/0x450
? lock_timer_base+0x3b/0xd0
io_wq_submit_work+0x8d/0x2b0
? __try_to_del_timer_sync+0x67/0xa0
io_worker_handle_work+0x17c/0x2b0
io_wqe_worker+0x10a/0x350
Cc: sta...@vger.kernel.org
Link:
https://lore.kernel.org/lkml/mw2pr2101mb1033fff044a258f84aeaa584f1...@mw2pr2101mb1033.namprd21.prod.outlook.com/
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support
to io_uring")
Si
[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency
** Tags removed: verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure verification-needed-mantic-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-lunar-linux-azure verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2040300 Title: Azure: Improve SQL DB latency Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TCP pingpong threshold is 1 by default. But some applications, like SQL DB may prefer a higher pingpong threshold to activate delayed acks in quick ack mode for better performance. There is no single value that fits all applications. Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for optimal performance based on the application needs. [Test Case] Microsoft tested [Regression Potential] Should be zero since default behavior is unchanged. [Other Info] SF: #00357415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2040300/+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 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
** Tags removed: verification-needed-lunar-linux-azure verification-needed-mantic-linux-azure ** Tags added: verification-done-lunar-linux-azure verification-done-mantic-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2038675 Title: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2038675/+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 2040300] Re: Azure: Improve SQL DB latency
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2040300 Title: Azure: Improve SQL DB latency Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] TCP pingpong threshold is 1 by default. But some applications, like SQL DB may prefer a higher pingpong threshold to activate delayed acks in quick ack mode for better performance. There is no single value that fits all applications. Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for optimal performance based on the application needs. [Test Case] Microsoft tested [Regression Potential] Should be zero since default behavior is unchanged. [Other Info] SF: #00357415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2040300/+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 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
** Changed in: linux-azure (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2038675 Title: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2038675/+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 2042096] Re: Azure: Update TDX with HCL support
** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2042096 Title: Azure: Update TDX with HCL support Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV VM support with HCL. The refreshed patches will fix 2 bugs for future Hyper-V versions: 1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a host bug. The guest bug is fixed in the mainline version of the TDX patches. 2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the Hyper-V while it should pass a private input page; as a result, the hypercall always fails and Linux now falls back to the legacy native method of flusing TLB. This slows down the flush-TLB operation . The mainline version doesn't have the bug. [Test Plan] Microsoft tested. [Regression Potential] Azure instances with TDX on HCL hypervisors may not work correctly. [Other Info] SF: #00364214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042096/+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 2043811] Re: AWS: arm64: pauth: don't sign leaf functions
** Package changed: linux (Ubuntu) => linux-aws (Ubuntu) ** Also affects: linux-aws (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2043811 Title: AWS: arm64: pauth: don't sign leaf functions Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Lunar: In Progress Bug description: SRU Justification [Impact] From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+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 2043811] [NEW] AWS: arm64: pauth: don't sign leaf functions
Public bug reported: SRU Justification [Impact] >From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043811 Title: AWS: arm64: pauth: don't sign leaf functions Status in linux package in Ubuntu: New Bug description: SRU Justification [Impact] From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043811/+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 2036600] Re: Azure: Fix Azure vendor ID
** Tags removed: verification-needed-lunar-linux-azure
verification-needed-mantic-linux-azure
** Tags added: verification-done-lunar-linux-azure
verification-done-mantic-linux-azure
--
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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
VMs could be misclassified.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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 2042096] [NEW] Azure: Update TDX with HCL support
Public bug reported: SRU Justification [Impact] Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV VM support with HCL. The refreshed patches will fix 2 bugs for future Hyper-V versions: 1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a host bug. The guest bug is fixed in the mainline version of the TDX patches. 2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the Hyper-V while it should pass a private input page; as a result, the hypercall always fails and Linux now falls back to the legacy native method of flusing TLB. This slows down the flush-TLB operation . The mainline version doesn't have the bug. [Test Plan] Microsoft tested. [Regression Potential] Azure instances with TDX on HCL hypervisors may not work correctly. [Other Info] SF: #00364214 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Lunar) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2042096 Title: Azure: Update TDX with HCL support Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Lunar: In Progress Bug description: SRU Justification [Impact] Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV VM support with HCL. The refreshed patches will fix 2 bugs for future Hyper-V versions: 1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a host bug. The guest bug is fixed in the mainline version of the TDX patches. 2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the Hyper-V while it should pass a private input page; as a result, the hypercall always fails and Linux now falls back to the legacy native method of flusing TLB. This slows down the flush-TLB operation . The mainline version doesn't have the bug. [Test Plan] Microsoft tested. [Regression Potential] Azure instances with TDX on HCL hypervisors may not work correctly. [Other Info] SF: #00364214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042096/+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 2042096] Re: Azure: Update TDX with HCL support
https://lists.ubuntu.com/archives/kernel-team/2023-October/146654.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2042096 Title: Azure: Update TDX with HCL support Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Lunar: In Progress Bug description: SRU Justification [Impact] Microsoft has asked for the addition of 2 patches for TDX and SNP-SEV VM support with HCL. The refreshed patches will fix 2 bugs for future Hyper-V versions: 1) PCI DDA for Linux TDX VMs with HCL is not working due to a guest bug and a host bug. The guest bug is fixed in the mainline version of the TDX patches. 2) On a recent Hyper-V dev build that advertises the Hyper-V TLB flushing hypercalls, the current Ubuntu 6.2 kernel passes a shared input page to the Hyper-V while it should pass a private input page; as a result, the hypercall always fails and Linux now falls back to the legacy native method of flusing TLB. This slows down the flush-TLB operation . The mainline version doesn't have the bug. [Test Plan] Microsoft tested. [Regression Potential] Azure instances with TDX on HCL hypervisors may not work correctly. [Other Info] SF: #00364214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2042096/+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 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
** Tags removed: verification-needed-jammy-linux-azure-6.5 verification-needed-lunar-linux-azure ** Tags added: verification-done-jammy-linux-azure-6.5 verification-done-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Released Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+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 2040300] Re: Azure: Improve SQL DB latency
https://lists.ubuntu.com/archives/kernel-team/2023-October/146418.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2040300 Title: Azure: Improve SQL DB latency Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] TCP pingpong threshold is 1 by default. But some applications, like SQL DB may prefer a higher pingpong threshold to activate delayed acks in quick ack mode for better performance. There is no single value that fits all applications. Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for optimal performance based on the application needs. [Test Case] Microsoft tested [Regression Potential] Should be zero since default behavior is unchanged. [Other Info] SF: #00357415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2040300/+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 2040300] [NEW] Azure: Improve SQL DB latency
Public bug reported:
SRU Justification
[Impact]
TCP pingpong threshold is 1 by default. But some applications, like SQL DB
may prefer a higher pingpong threshold to activate delayed acks in quick
ack mode for better performance.
There is no single value that fits all applications.
Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for
optimal performance based on the application needs.
[Test Case]
Microsoft tested
[Regression Potential]
Should be zero since default behavior is unchanged.
[Other Info]
SF: #00357415
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-azure (Ubuntu Jammy)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-azure (Ubuntu Lunar)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-azure (Ubuntu Mantic)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/2040300
Title:
Azure: Improve SQL DB latency
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Status in linux-azure source package in Lunar:
In Progress
Status in linux-azure source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
TCP pingpong threshold is 1 by default. But some applications, like SQL DB
may prefer a higher pingpong threshold to activate delayed acks in quick
ack mode for better performance.
There is no single value that fits all applications.
Add net.ipv4.tcp_pingpong_thresh sysctl tunable, so it can be tuned for
optimal performance based on the application needs.
[Test Case]
Microsoft tested
[Regression Potential]
Should be zero since default behavior is unchanged.
[Other Info]
SF: #00357415
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2040300/+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 2036450] Re: Azure: Update CIFS to v6.5
** Tags removed: verification-needed-jammy-linux-azure ** Tags added: verification-done-jammy-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036450 Title: Azure: Update CIFS to v6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested this patch set to update CIFS and smbfs to the Linux kernel version 6.5. [Test Plan] Microsoft has tested with positive results. [Regression Potential] This is a huge patch set. The potential exists for corruption, connection instabilities, or other cifs related maladies. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036450/+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 2040163] [NEW] Azure: Update TDX support
Public bug reported:
SRU Justification
[Impact]
Refresh the TDX support and support DDA for a TDX VM with paravisor.
Ideally we would revert
commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest support on
hyperv" [1]
and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V specific
part)" [2]
(Note: [2] depends on [1]), but that would introduce too many changes, and
actually "AMD sev-snp enlightened guest support on hyperv" still needs some
extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
interrupt injection patch [3] is not in the upstream yet.
So I think a better way to have [2] is to make a patch that adds the missing
part of [2] for the 6.2-based linux-azure kernel, hence I made this patch.
This patch mainly does the below two things:
a) Add commit 23378295042a ("Drivers: hv: vmbus: Bring the post_msg_page back
for TDX VMs with the paravisor") [4]
This fixes a bug in the hv_pci driver for device assignment (DDA) for a TDX
VM with the paravisor: in such a VM, the hyperv_pcpu_input_arg must be
private (i.e. encrypted), otherwise the hypercalls in hv_pci fail since the
hypercalls in such a VM is handled by the paravisor rather than by the
hypervisor.
b) Undo some hack code introduced by
commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"),
e.g. in hyperv_init(), this patch moves the below code to its original place:
cpuhp_setup_state(CPUHP_AP_HYPERV_ONLINE, "x86/hyperv_init:online",
hv_cpu_init, hv_cpu_die);
With this patch, now hyperv_init() in this 6.2 linux-azure kernel is
exactly the same as the version in the mainline kernel.
References:
[1] https://lwn.net/ml/linux-kernel/ZOQMiLEdPsD+pF8q@liuwe-devbox-debian-v2/
[2] https://lwn.net/ml/linux-kernel/ZOfwSDjW0wlHozYV@liuwe-devbox-debian-v2/
[3]
https://lwn.net/ml/linux-kernel/20230515165917.1306922-3-ltyker...@gmail.com/
[4]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23378295042a4bcaeec350733a4771678e7a1f3a
[Test Plan]
Microsoft tested.
I tested the patch for a TDX VM without and with paravisor, a VBS VM,
a SNP VM with paravisor, and a regular VM. All the VMs have 128 vCPUs
and 20 GB of memory. All worked as expected.
[Regression potential]
Azure TDX enabled VMs could misbehave.
[Other Info]
SF: #00364214
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Description changed:
SRU Justification
[Impact]
Refresh the TDX support and support DDA for a TDX VM with paravisor.
Ideally we would revert
- commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
- apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest
support on hyperv" [1]
- and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V
specific part)" [2]
- (Note: [2] depends on [1]), but that would introduce too many changes, and
- actually "AMD sev-snp enlightened guest support on hyperv" still needs
some
- extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
- interrupt injection patch [3] is not in the upstream yet.
-
- So I think a better way to have [2] is to make a patch that adds the
missing
- part of [2] for the 6.2-based linux-azure kernel, hence I made this patch.
-
- This patch mainly does the below two things:
-
- a) Add commit 23378295042a ("Drivers: hv: vmbus: Bring the post_msg_page
back for TDX VMs with the paravisor") [4]
- This fixes a bug in the hv_pci driver for device assignment (DDA) for a
TDX
- VM with the paravisor: in such a VM, the hyperv_pcpu_input_arg must be
- private (i.e. encrypted), otherwise the hypercalls in hv_pci fail since
the
- hypercalls in such a VM is handled by the paravisor rather than by the
- hypervisor.
-
- b) Undo some hack code introduced by
- commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"),
- e.g. in hyperv_init(), this patch moves the below code to its original
place:
-
- cpuhp_setup_state(CPUHP_AP_HYPERV_ONLINE, "x86/hyperv_init:online",
- hv_cpu_init, hv_cpu_die);
-
- With this patch, now hyperv_init() in this 6.2 linux-azure kernel is
- exactly the same as the version in the mainline kernel.
+ commit b8b46adebbd8 ("UBUNTU: SAUCE: Support TDX+HCL (July 9, 2023)"), and
+ apply "[PATCH v7 0/8] x86/hyperv: Add AMD sev-snp enlightened guest support
on hyperv" [1]
+ and apply "[PATCH v3 00/10] Support TDX guests on Hyper-V (the Hyper-V
specific part)" [2]
+ (Note: [2] depends on [1]), but that would introduce too many changes, and
+ actually "AMD sev-snp enlightened guest support on hyperv" still needs some
+ extra patches that are not in the upstream yet, e.g. Tianyu Lan's #HV
+ interrupt injection patch [3] is not in the
[Kernel-packages] [Bug 2029916] Re: Problem with fscrypt
The problem still exists, but xfce-errors appeared every time before a fscrypt error. -- 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/2029916 Title: Problem with fscrypt Status in linux package in Ubuntu: Confirmed Bug description: I am using Xubuntu 23.04 with Kernel 6.2.0-26 and X is crashing several times a week. X is reloading then and I can login again. xsession-erros shows this last lines: (xfce4-power-manager:1713980): libxfce4ui-WARNING **: 10:21:31.890: ICE I/O Error connection to :0.0 broken (explicit kill or server shutdown).^M parcellite: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0. Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0. Exiting due to channel error. But I think, the real problem is a kernel bug. Kernel logs shows: [Fr Aug 4 10:21:22 2023] traps: xfce4-session[1712867] general protection fault ip:55a4f65925c9 sp:7ffd2ec21ee0 error:0 in xfce4-session[55a4f657a000+1c000] [Fr Aug 4 10:21:28 2023] VBoxDrvLinuxIOCtl: copy_to_user(0x7fe3609fed80,,0x18); uCmd=0xc0305698! [Fr Aug 4 10:21:28 2023] VBoxDrvLinuxIOCtl: copy_to_user(0x7f4d2c15bd10,,0x30); uCmd=0xc0305687! [Fr Aug 4 10:21:28 2023] device enp9s0 left promiscuous mode [Fr Aug 4 10:21:28 2023] vboxnetflt: 0 out of 50995150 packets were not sent (directed to host) [Fr Aug 4 10:21:30 2023] fscrypt: md0: 826 inode(s) still busy after removing key with identifier 49350b594674f1c69710b91f9fef9eb9, including ino 43915491 This fscrypt error appeared every crash! Maby it is related to this: https://www.spinics.net/lists/linux-btrfs/msg137421.html I don't use btrfs, but ext4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029916/+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 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
https://lists.ubuntu.com/archives/kernel-team/2023-October/146153.html ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2039208 Title: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Bug description: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2039208] [NEW] Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
Public bug reported: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Description changed: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. + + [Fix] + + [1] + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 + + [2] + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 + + [3] + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 + + [4] + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2039208 Title: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Lunar: New Bug description: SRU Justification [Impact] On Azure, the VM SKU Standard_NC64as_T4_v3's bandwidth is 30 Gbps, but we can only reach 15~20 Gbps with the 5.15.0-1049-azure kernel in Ubuntu 20.04 or the 6.2.0-1014-azure kernel in Ubuntu 22.04. After I pick up the upstream patch(es) to enable PCI relaxed ordering (RO) for the Mellanox VF NIC, the throughput goes up to 30.4 Gbps. [Fix] [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17347d5430c4e4e1a3c58ffa2732746bd26a9c02 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2351e517068718724f1d3b4010e2a41ec91fa76 [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77528e2aed9246cf8017b8a6f1b658a264d6f2b2 [4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed4b0661cce119870edb1994fd06c9cbc1dc05c3 [Test Plan] Microsoft tested [Regression Potential] Mellanox connections could be corrupted or run slower. [Other Info] SF: #00370735 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2039208/+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 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
Patches submitted for review: https://lists.ubuntu.com/archives/kernel- team/2023-October/146007.html ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2038675 Title: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Lunar: New Status in linux-azure source package in Mantic: New Bug description: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2038675/+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 2038675] [NEW] mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
Public bug reported: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2038675 Title: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Mantic: New Bug description: SRU Justification [Impact] The Microsoft MANA network driver does not accurately report some statistics and does not correctly handle some error conditions. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=b2b69a4c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7a54de926574 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a43e8e9ffa0d [Test Plan] Microsoft tested. [Regression Potential] GSO packets may not be correctly reported. Some error conditions may cause incorrect statistics to be recorded, or flood the kernel log with error messages. [Other Info] SF: 00370665 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2038675/+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 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+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 2036450] Re: Azure: Update CIFS to v6.5
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036450 Title: Azure: Update CIFS to v6.5 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested this patch set to update CIFS and smbfs to the Linux kernel version 6.5. [Test Plan] Microsoft has tested with positive results. [Regression Potential] This is a huge patch set. The potential exists for corruption, connection instabilities, or other cifs related maladies. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036450/+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 2037316] Re: SEV_SNP failure to init
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Mantic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2037316 Title: SEV_SNP failure to init Status in linux-aws package in Ubuntu: Fix Committed Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Jammy: Invalid Status in linux-gcp source package in Jammy: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Kernel fails to boot on SEV-SNP instances when compiled with GCC 12.3.0 [Fix] * https://lore.kernel.org/lkml/20230912002703.3924521-1-acdun...@google.com/ [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Patches relatively isolated and maintain similar checking functionality, just earlier in boot. Likely a low chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2037316/+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 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-azure verification-needed-focal-linux-bluefield verification-needed-focal-linux-ibm verification-needed-jammy-linux-aws verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure verification-needed-lunar-linux-riscv verification-needed-lunar-linux-starfive ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-azure verification-done-focal-linux-bluefield verification-done-focal-linux-ibm verification-done-jammy-linux-aws verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-lunar-linux-azure verification-done-lunar-linux-riscv verification-done-lunar-linux-starfive ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+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 2034747] Re: Azure: Fix Infiniband identifier order
** Tags removed: verification-needed-jammy-linux-azure
** Tags added: verification-done-jammy-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2034747
Title:
Azure: Fix Infiniband identifier order
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
In Progress
Bug description:
SRU Justification
[Impact]
Commit ad95515bf1d391326b362d8b0c1e6e3bd74046b6 ('RDMA/mana_ib: Add a
driver for Microsoft Azure Network Adapter') is part of the MANA
Infiniband backport. However, a commit was missed that updated the
'enum rdma_driver_id' list of identifiers. Since these are order and
value specific user space applications are not able to correctly
identify the MANA RDMA driver.
[Test Plan]
MSFT tested.
[Regression Potential]
Existing applications don't work with MANA RDMA anyway, so there is no
regression potential.
[Other Info]
SF: #00368017
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034747/+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 2034277] Re: Azure: net: mana: Add page pool for RX buffers
** Tags removed: verification-needed-jammy-linux-azure verification-needed-lunar-linux-azure ** Tags added: verification-done-jammy-linux-azure verification-done-lunar-linux-azure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2034277 Title: Azure: net: mana: Add page pool for RX buffers Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Status in linux-azure source package in Mantic: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested this path be added to the 5.15 and 6.2 Azure kernels. Add page pool for RX buffers for faster buffer cycle and reduce CPU usage. [Test Plan] MSFT tested. [Regression Potential] Could cause receive packet corruption. [Other Info] SF: #00365760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2034277/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
Here's an MP for ubuntu-manual-tests with this new testcase for the legacy image: https://code.launchpad.net/~ubuntu-testcase/ubuntu-manual- tests/+git/ubuntu-manual-tests/+merge/451989 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: Triaged Status in Release Notes for Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
No just one external monitor attached. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+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 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
I see hehe, sorry here it comes! ** Attachment added: "connections.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+attachment/5703223/+files/connections.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: mutter (Ubuntu Mantic) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags removed: rls-mm-incoming -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in Linux: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2036802] Re: HDMI not detected on HP Zbook Power 15 G9
Command grep . /sys/class/drm/*/status > connections.txt returns nothing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036802 Title: HDMI not detected on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: Incomplete Bug description: As discussed in this thread: https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811 On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected. According to the discussion a fix has been implemented in kernel v6.6-rc1. If it's possible for Ubuntu to implement some fix in the current LTS version that would be MUCH helpful and appreciated for me and all other ubuntu users on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.104.05 Sat Aug 19 01:15:15 UTC 2023 GCC version: gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 19:25:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: evdi/1.14.1, 6.2.0-32-generic, x86_64: installed evdi/1.14.1, 6.2.0-33-generic, x86_64: installed nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:89c0] Subsystem: Hewlett-Packard Company Device [103c:89c1] InstallationDate: Installed on 2023-08-21 (29 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: U97 Ver. 01.08.00 dmi.board.name: 89C0 dmi.board.vendor: HP dmi.board.version: KBC Version 11.63.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 17.99 dmi.modalias: dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC dmi.product.sku: 6B867EA#UUW dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2036802/+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 2036600] Re: Azure: Fix Azure vendor ID
Reissued the patch for just Lunar/Mantic:
https://lists.ubuntu.com/archives/kernel-team/2023-September/143053.html
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Invalid
** Description changed:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit (https://git.launchpad.net/~canonical-
kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8) :
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1. I'll
post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal is
0 (unhealthy): some users rely on the info to manage their VMs, e.g. if
the VM is erroneously reported "unhealthy", the VM may be killed and re-
created, and the new VM is still "unhealthy", and the VM may be killed
and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
- This (incorrect) patch has been in place for 10 years. Its possible that
- some consumers have come to rely on this VM identifier.
+ VMs could be misclassified.
[Other Info]
SF: #00368936
--
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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
VMs could be misclassified.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2029138] Re: cifs: fix mid leak during reconnection after timeout threshold
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-6.2 verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx verification-needed-jammy-linux-raspi verification-needed-lunar-linux verification-needed-lunar-linux-azure verification-needed-lunar-linux-starfive ** Tags added: verification-done-focal-linux-nvidia-tegra-5.15 verification-done-focal-linux-riscv-5.15 verification-done-jammy-linux verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-6.2 verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-nvidia-tegra-igx verification-done-jammy-linux-raspi verification-done-lunar-linux verification-done-lunar-linux-azure verification-done-lunar-linux-starfive -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2029138 Title: cifs: fix mid leak during reconnection after timeout threshold Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] A regression in the Ubuntu 5.15 kernel has been causing problems for multiple customers on Azure. This bug has been fixed in the mainline kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=69cba9d3c1284e0838ae408830a02c4a063104bc [Test Plan] Microsoft tested [Regression Potential] Reconnections could fail. [Other Info] SF: #00365185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029138/+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 2036627] Re: Azure: net: mana: Configure hwc timeout from hardware
Patch submitted for review: https://lists.ubuntu.com/archives/kernel- team/2023-September/143017.html ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Mantic) Status: Fix Released => In Progress ** Changed in: linux-azure (Ubuntu Mantic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: In Progress Status in linux-azure source package in Mantic: In Progress Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+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 2036600] Re: Azure: Fix Azure vendor ID
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
In Progress
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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 2036627] [NEW] Azure: net: mana: Configure hwc timeout from hardware
Public bug reported: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Jammy) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Also affects: linux-azure (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: linux-azure (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2036627 Title: Azure: net: mana: Configure hwc timeout from hardware Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Lunar: New Status in linux-azure source package in Mantic: Fix Released Bug description: SRU Justification [Impact] At present hwc timeout value is a fixed value. This patch sets the hwc timeout from the hardware. It now uses a new hardware capability GDMA_DRV_CAP_FLAG_1_HWC_TIMEOUT_RECONFIG to query and set the value in hwc_timeout. [Test Plan] Microsoft tested and approved. [Regression Potential] Timeouts could get mis-configured. [Other Info] SF: #00365762 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2036627/+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 2036600] Re: Azure: Fix Azure vendor ID
Patch submitted for review: https://lists.ubuntu.com/archives/kernel-
team/2023-September/143008.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/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
Incomplete
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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 2036600] Re: Azure: Fix Azure vendor ID
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036600
Title:
Azure: Fix Azure vendor ID
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
Incomplete
Bug description:
SRU Justification
[Impact]
The linux-azure 6.2 kernel doesn't report a correct GUEST_ID
There is a mistake in the commit
(https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
azure/+git/jammy/commit/?id=5dd24f2df3280d4354641f4687dbb36e418e7de8)
:
Before the commit, the good guest_id is 0x81860210.
With the commit, the generated guest_id is incorrect:
0x00860210, i.e. the 0x81 from bit 56~63 are dropped.
See "include/asm-generic/hyperv-tlfs.h" for the definition of the bits:
* Bit(s)
* 63 - Indicates if the OS is Open Source or not; 1 is Open Source
* 62:56 - Os Type; Linux is 0x100 ! Dexuan: this should be 0x1.
I'll post a patch to LKML to fix this typo.
* 55:48 - Distro specific identification
* 47:16 - Linux kernel version number
* 15:0 - Distro specific identification
See https://learn.microsoft.com/en-us/virtualization/hyper-v-on-
windows/tlfs/tlfs ("February, 2020: Released Version 6.0b", page 15)
As a result, the host thinks that the VM is not an open-source OS, and
it's not Linux. Consequently, the "VM Availability" fron Azure portal
is 0 (unhealthy): some users rely on the info to manage their VMs,
e.g. if the VM is erroneously reported "unhealthy", the VM may be
killed and re-created, and the new VM is still "unhealthy", and the VM
may be killed and re-created again...
Please consider integrating the below fix ASAP. This affects regular
VMs, and I think this affects CVMs as well.
The fix should be:
diff --git a/include/asm-generic/hyperv-tlfs.h
b/include/asm-generic/hyperv-tlfs.h
@@ -135,7 +135,7 @@ union hv_reference_tsc_msr {
*
*/
-#define HV_LINUX_VENDOR_ID 0x80 /* Canonical */
+#define HV_LINUX_VENDOR_ID 0x8180 /* Canonical */
[Test Plan]
Microsoft tested
[Regression Potential]
This (incorrect) patch has been in place for 10 years. Its possible
that some consumers have come to rely on this VM identifier.
[Other Info]
SF: #00368936
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036600/+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
