date:20230719

See also bug 2028199.

-- 
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/2023585

Title:
  [nvidia] GPU has fallen off the bus

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  New

Bug description:
  When playing Assassins Creed Unity through Steam, the game will run
  fine for a short period and then pretty quickly in my experience the
  screen will go blank, lights on the GPU will turn off and GPU fans
  will spin at max RPM.

  I checked the dmesg logs from that session and saw at the bottom:

  ```
  Jun 12 19:25:09 pikachu kernel: NVRM: GPU at PCI::0b:00: 
GPU-f888943b-327b-82af-03dd-7c4213dc4788
  Jun 12 19:25:09 pikachu kernel: NVRM: Xid (PCI::0b:00): 79, 
pid='', name=, GPU has fallen off the bus.
  Jun 12 19:25:09 pikachu kernel: NVRM: GPU :0b:00.0: GPU has fallen off 
the bus.
  Jun 12 19:25:09 pikachu kernel: nvidia-gpu :0b:00.3: Unable to change 
power state from D3hot to D0, device inaccessible
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power 
state from D3hot to D0, device inaccessible
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Unable to change power 
state from D3cold to D0, device inaccessible
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: Controller not ready 
at resume -19
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: PCI post-resume error 
-19!
  Jun 12 19:25:09 pikachu kernel: xhci_hcd :0b:00.2: HC died; cleaning up
  Jun 12 19:25:09 pikachu kernel: audit: type=1400 audit(1686594309.980:429): 
apparmor="DENIED" operation="open" class="file" 
profile="snap.keepassxc.keepassxc" name="/sys/devices/pci00>
  Jun 12 19:25:10 pikachu kernel: nvidia-gpu :0b:00.3: i2c timeout error 

  Jun 12 19:25:10 pikachu kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
  ```

  Further up in the logs I also see the following (in case it's
  related):

  ```
  [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0b00] 
Failed to grab modeset ownership
  ```

  I am using an RTX 2080Ti on driver version 525.105.17.

  I have attached the full dmesg log

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nvidia-driver-525 525.105.17-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 12 19:35:37 2023
  InstallationDate: Installed on 2022-12-06 (187 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nvidia-graphics-drivers-525
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023585/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028199] Re: GPU disconnect, then minutes later Xorg display lockup

It sounds like you've hit the problem Nvidia mentions in their
documentation:

http://us.download.nvidia.com/XFree86/Linux-x86_64/535.54.03/README/egpu.html

so I guess falling off the bus is just as bad as being unplugged.

Can you provide logs mentioning falling off the bus? I only recall a
different user mentioning it recently in bug 2023585.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2028199

Title:
  GPU disconnect, then minutes later Xorg display lockup

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete

Bug description:
  It appears that occassionally my external GPU 'falls off' the bus,
  it's listed as not primary, so should not be an issue.

  However, a few minutes (usually) after this occurs, the Xorg server or
  window manager completely locks up in strange ways.  For example - the
  mouse can move across the multiple monitors, but no clicks are
  registered.  similarly, no keyboard keypresses result in any change in
  the UI.

  However, applications happily run in the background - videoconference
  meetings using the audio mic and speakers continue to operate , and
  the machine stays online.  This leads me to believe there is some
  problem with Xorg capturing the Human interface devices and passing
  these to the correct applications, and then updating the displays.

  I don't know how to trigger this behavior reliably, but I am getting
  closer to tracking down how it occurs.  I hoped you might be able to
  shed some light as to why this might be happening and how to resolve
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-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..52.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.54.03  Tue Jun  6 
22:20:39 UTC 2023
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1)
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 19 14:33:01 2023
  DistUpgraded: 2023-04-26 15:38:23,675 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257]
  InstallationDate: Installed on 2023-01-09 (191 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 20XY0027US
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (84 days ago)
  dmi.bios.date: 06/12/2023
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET85W (1.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.34
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx:

[Kernel-packages] [Bug 2028193] Re: Machine doesn't resume after sleep

** Tags added: amdgpu resume suspend-resume

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2028193

Title:
  Machine doesn't resume after sleep

Status in linux package in Ubuntu:
  New

Bug description:
  When machine resumes after having been in sleep mode the screen is
  corrupted. Hard reboot required.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 19 16:12:01 2023
  DistUpgraded: 2023-07-11 13:24:17,567 DEBUG icon theme changed, re-reading
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon Vega 8 Mobile [103c:83c6]
  InstallationDate: Installed on 2018-05-14 (1892 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   LANG=en_CA.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=30332ede-31ab-439d-a665-2d2c504399cb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-07-11 (8 days ago)
  dmi.bios.date: 08/12/2021
  dmi.bios.release: 15.23
  dmi.bios.vendor: AMI
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 63.18
  dmi.modalias: 
dmi:bvnAMI:bvrF.23:bd08/12/2021:br15.23:efr63.18:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:sku1UG91UA#ABL:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.product.sku: 1UG91UA#ABL
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/+bug/2028193/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1689448] Re: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch

** Tags removed: kinetic
** Tags added: lunar mantic

** Summary changed:

- bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb 
accept_cb g_main_dispatch g_main_context_dispatch
+ bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport() from 
transport_cb() from accept_cb() from g_main_dispatch() from 
g_main_context_dispatch()

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1689448

Title:
  bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport() from
  transport_cb() from accept_cb() from g_main_dispatch() from
  g_main_context_dispatch()

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.43-0ubuntu1, 
the problem page at 
https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689448/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028186] Re: zfs with encryption: sluggish resume from suspend, intermittent freezes

Thanks for the bug report. When the problem is happening, please open a
terminal and run:

  journalctl -b0 > journal.txt
  lspci -k > lspci.txt
  dconf dump /org/gnome/shell/ > shellsettings.txt

and attach the resulting text files here. If you couldn't run those
while the problem is happening then reboot and use this instead:

  journalctl -b-1 > prevboot.txt
  lspci -k > lspci.txt
  dconf dump /org/gnome/shell/ > shellsettings.txt


** Changed in: linux-signed-hwe-5.19 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2028186

Title:
  zfs with encryption: sluggish resume from suspend, intermittent
  freezes

Status in linux-signed-hwe-5.19 package in Ubuntu:
  Incomplete

Bug description:
  I had been using Jammy on a Thinkpad T470 for months without problems.

  I decided to try a fresh Ubuntu Desktop install using ZFS, using the
  install-time option for full-disk encryption.

  After using the fresh install for a little while, I noticed that the
  system was "more sluggish" in the ZFS configuration (which was
  disappointing, but tolerable).

  The "sluggishness" is especially noticeable when resuming from
  suspend. Typically, I'll look at the system clock and notice that it
  does not change for ~tens of seconds. On some occasions, it will
  freeze completely (even after waiting many minutes) and require a
  reboot.

  Given that this the only difference between a "perfectly working
  system" and "problematic system" was the filesystem change, I strongly
  suspect ZFS as the cause (and/or perhaps enabling the full-disk
  encryption option for it during the install).

  Any advice on how to further triage this and narrow down the issue
  would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 19 10:03:03 2023
  InstallationDate: Installed on 2023-03-22 (119 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2028186/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028096] Re: Blank screen when using GDM

*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887

When the bug is happening just switch to a VT (like Ctrl+Alt+F4) and
run:

  journalctl -b0 > journal.txt

then attach the resulting text file here.

To add to /etc/environment you need to edit the file as super user and
add a new line.

If you update the kernel, yes that is reversible. You probably wouldn't
need to reverse it since that's the stable kernel for our long term
stable release in use by probably most Ubuntu users.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2028096

Title:
  Blank screen when using GDM

Status in gdm:
  Unknown
Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  Refer to this issue that I created for the GDM developers:
  https://gitlab.gnome.org/GNOME/gdm/-/issues/860

  They have indicated that they will not fix this bug.

  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  gnome-shell:
Installed: 42.9-0ubuntu2
Candidate: 42.9-0ubuntu2
Version table:
   *** 42.9-0ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  I am expecting not to have pipe errors between my integrated graphics
  card and GDM and for the login screen to appear.

  I got a pixelated screen and then a blank, black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1034.35-oem 5.17.15
  Uname: Linux 5.17.0-1034-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Jul 18 18:12:57 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2023-06-14 (34 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu1
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/2028096/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028205] [NEW] package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut

2023-07-19 Thread Kristofer Rickheden Gustavsson

Public bug reported:

Fresh install, first login.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
Uname: Linux 6.2.0-25-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
AptOrdering:
 linux-firmware:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hackan 1964 F wireplumber
 /dev/snd/seq:hackan 1952 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jul 19 23:10:46 2023
Dependencies: firmware-sof-signed 2.2.4-1
ErrorMessage: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut
InstallationDate: Installed on 2023-07-19 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
IwConfig:
 lono wireless extensions.
 
 enp2s0f0  no wireless extensions.
MachineType: Apple Inc. Macmini5,1
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux-firmware
Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to 
install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/13/2019
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 135.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias: 
dmi:bvnAppleInc.:bvr135.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:skuSystemSKU#:
dmi.product.family: Macmini
dmi.product.name: Macmini5,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2028205

Title:
  package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to
  install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2
  vid avslut

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Fresh install, first login.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  AptOrdering:
   linux-firmware:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hackan 1964 F wireplumber
   /dev/snd/seq:hackan 1952 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Jul 19 23:10:46 2023
  Dependencies: firmware-sof-signed 2.2.4-1
  ErrorMessage: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut
  InstallationDate: Installed on 2023-07-19 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  IwConfig:
   lono wireless extensions.
   
   enp2s0f0  no wireless extensions.
  MachineType: Apple Inc. Macmini5,1
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-firmware
  Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to 
install/upgrade: underprocessen dpkg-deb --fsys-tarfile gav felkod 2 vid avslut
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 135.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version:

[Kernel-packages] [Bug 2027785] Re: NBS: RM: Jammy: Please remove NBS of an incorrect old variant

2023-07-19 Thread Steve Langasek

Removing packages from jammy-updates:
linux-meta-azure-fde-5.19 5.19.0.1025.28~22.04.1.7 in jammy
linux-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 in jammy 
amd64
linux-cloud-tools-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 
in jammy amd64
linux-headers-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 in 
jammy amd64
linux-image-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 in 
jammy amd64
linux-modules-extra-azure-fde-5.19-edge 
5.19.0.1025.28~22.04.1.7 in jammy amd64
linux-tools-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 in 
jammy amd64
Comment: NBS
1 package successfully removed.


** Changed in: linux-meta-azure-fde-5.19 (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-azure-fde-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2027785

Title:
  NBS: RM: Jammy: Please remove NBS of an incorrect old variant

Status in linux-meta-azure-fde-5.19 package in Ubuntu:
  Fix Released

Bug description:
  This was the last upload:
  
https://launchpad.net/ubuntu/+source/linux-meta-azure-fde-5.19/5.19.0.1025.28~22.04.1.7

  that used incorrect variant name '5.19-edge', instead of just 'edge',
  and produced the below metapackages:

  linux-azure-fde-5.19-edge/jammy-updates,jammy-security 
5.19.0.1025.28~22.04.1.7 amd64
  linux-cloud-tools-azure-fde-5.19-edge/jammy-updates,jammy-security 
5.19.0.1025.28~22.04.1.7 amd64
  linux-headers-azure-fde-5.19-edge/jammy-updates,jammy-security 
5.19.0.1025.28~22.04.1.7 amd64
  linux-image-azure-fde-5.19-edge/jammy-updates,jammy-security 
5.19.0.1025.28~22.04.1.7 amd64
  linux-modules-extra-azure-fde-5.19-edge/jammy-updates,jammy-security 
5.19.0.1025.28~22.04.1.7 amd64
  linux-tools-azure-fde-5.19-edge/jammy-updates,jammy-security 
5.19.0.1025.28~22.04.1.7 amd64

  and are now NBS, since upload:
  
https://launchpad.net/ubuntu/+source/linux-meta-azure-fde-5.19/5.19.0.1026.29~22.04.1.8

  that uses correct variant 'edge'.

  Please remove from jammy-updates and jammy-security the below packages as NBS:
  linux-azure-fde-5.19-edge
  linux-cloud-tools-azure-fde-5.19-edge
  linux-headers-azure-fde-5.19-edge
  linux-image-azure-fde-5.19-edge
  linux-modules-extra-azure-fde-5.19-edge
  linux-tools-azure-fde-5.19-edge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure-fde-5.19/+bug/2027785/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake

2023-07-19 Thread Eli

I will grep that for you, here is the reference information just after
boot when everything works. I have to wait for the bug to kick in (and
woke up to blinking cursor in the upper left corner, funnn).

reference:
/sys/devices/system/cpu/intel_pstate/hwp_dynamic_boost:0
/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:10
/sys/devices/system/cpu/intel_pstate/no_turbo:0
/sys/devices/system/cpu/intel_pstate/status:active

-- 
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/2026658

Title:
  CPU frequency governor broken after upgrading from 22.10 to 23.04,
  stuck at 400Mhz on Alder Lake

Status in linux package in Ubuntu:
  New

Bug description:
  I've tried to include as much detail as possible in this bug report, I
  originally assembled it just after the release of ubuntu 23.04.  There
  has been no change since then.

  
  I have had substantial performance problems since updating from ubuntu 22.10 
to 23.04.
  The computer in question is the 17 inch Razer Blade laptop from 2022 with an 
intel i7-12800H.
  Current kernel is 6.2.0-20-generic.  (now I'm on 6.2.0-24-generic and nothing 
has changed.)
  This issue occurs regardless of whether the OpenRazer 
(https://openrazer.github.io/) drivers etc are installed.

  
  Description of problem:
  I have discovered what may be two separate bugs involving low level power 
management details on the cpu, they involve the cpu entering different types of 
throttled states and never recovering. These issues appeared immediately after 
upgrading from ubuntu 22.10.  The computer is a large ~gaming laptop with 
plenty of thermal headroom, cpu temperatures cannot reach concerning values 
except when using stress testing tools.

  (I don't know how to propery untangle these two issues, so I'm posting
  them as one. I apologize for the review complexity this causes, but I
  think posting the information all in one spot is more constructive
  here.)

  
  High level testing notes:
  - This issue occurs with use of both the intel_pstate driver and the cpufreq 
driver. (I don't have the same level of detail for cpufreq, but the issue still 
occurs.)
  - I have additionally tested a handful of intel_pstate parameters (and 
others) via grub kernel command line arguments to no effect. All testing 
reported here was done with:
GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau"
GRUB_CMDLINE_LINUX=""
(loading nouveau caused problems for me on 22.10, I have not bothered 
reinvestigating it on 23.04)
  - There is a firmware update available from the manufacture when I boot into 
Windows, I have not installed it (yet).
  - - Update: I installed it. No change.
  - Changing the cpu governor setting from "powersave" to "performance" using 
`cpupower frequency-set -g performance` has no effect. (Note: this action is 
separate from the intel_pstate's power-saver/balanced/performance setting 
visible with the `powerprofilesctl` utility. It doesn't seem to be a governor 
bug.
  - - (There is a tertiary issue where I also see substantial (+50%) 
performance degredation using the "performance" profile in a test suite I run 
constantly for my job; that is clearly a problem but it is an unrelated bug 
that has existed for quite some time.)

  
  Summary and my own conclusions:
  These are my takeaways, the ~raw data is in the followup section.

  
  Bug 1)
  The reported cpu power limits are progressively constrained over time. Once 
this failure mode starts the performance never recovers.
- As this situation progresses the observed cpu speeds (I'm using htop) 
list as 2800Mhz at idle, but the instant any load at all is placed on a cpu 
core that core immediately drops to exactly 400Mhz.
- This situation occurs quite quickly in human terms, frequently within 20 
minutes of normal usage after a boot, but it will also occur when the computer 
is just sitting there unused for a handful of hours.
- This occurs when using the cpufreq gevernor (by including 
"intel_pstate=disable" on the grub command line args.)
- At boot the default value for short_term_time looks wrong to me. This is 
the duration of higher thermal targets in seconds, ~0.002 seconds seems 
extremely short. A normal value would be a handful of seconds.
- This situation can be remedied by running the following python script. It 
uses the undervolt package (pip install undervolt==0.3.0) to force particular 
power limits (the provided values are intentional overkill):
   1   │ from undervolt import read_power_limit, set_power_limit, 
PowerLimit, ADDRESSES
   2   │ from pprint import pprint
   3   │ 
   4   │ limits = read_power_limit(ADDRESSES)
   5   │ pprint(vars(limits))  # print current values before setting them
   6   │ 
   7   │ POWER_LIMITS = PowerLimit()
   8   │ POWER_LIMITS.locked = True  # lock

[Kernel-packages] [Bug 2028200] [NEW] Include out-of-tree IGX modules in kernel build

2023-07-19 Thread Jacob Martin

Public bug reported:

[Impact]
Many components of the IGX system rely on out-of-tree kernel modules for full 
functionality. 

[Fix]
These modules should be included in the kernel build via dkms-versions. 
Additionally, modify configs to disable conflicting in-tree modules.

** Affects: linux-nvidia-tegra-igx (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu.
https://bugs.launchpad.net/bugs/2028200

Title:
  Include out-of-tree IGX modules in kernel build

Status in linux-nvidia-tegra-igx package in Ubuntu:
  New

Bug description:
  [Impact]
  Many components of the IGX system rely on out-of-tree kernel modules for full 
functionality. 

  [Fix]
  These modules should be included in the kernel build via dkms-versions. 
Additionally, modify configs to disable conflicting in-tree modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2028200/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028197] [NEW] rshim console truncates dmesg output due to tmfifo issue

2023-07-19 Thread Shih-Yi Chen

Public bug reported:

SRU Justification:

[Impact]

mlxbf_tmfifo driver does not always schedule work for VIRTIO CONSOLE
nottification. The result is with rshim console, the dmesg output would
be cut off or simply cat a big text file to stdout.

[Fix]

* Make sure TM_TX_LWM_IRQ bit is set when there is a notification of
virtio console event.

[Test Case]

* Compare the output of dmesg from rshim console and ssh session. Make sure 
both are the same.
* Issue is reproduced w/o fix and compare the same dmesg output from the same 
as above.

[Regression Potential]

The changes affect only virtio console event handling only and been
tested fully.

[Others]
This issue is the same on focal and Jammy.

** Affects: linux-bluefield (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  SRU Justification:
  
  [Impact]
  
  mlxbf_tmfifo driver does not always schedule work for VIRTIO CONSOLE
  nottification. The result is with rshim console, the dmesg output would
  be cut off or simply cat a big text file to stdout.
  
  [Fix]
  
  * Make sure TM_TX_LWM_IRQ bit is set when there is a notification of
  virtio console event.
  
  [Test Case]
  
  * Compare the output of dmesg from rshim console and ssh session. Make sure 
both are the same.
- * Issue is reproduced w/o fix and compare the same dmesg output from the same 
as above. 
+ * Issue is reproduced w/o fix and compare the same dmesg output from the same 
as above.
  
  [Regression Potential]
  
  The changes affect only virtio console event handling only and been
  tested fully.
+ 
+ [Others]
+ This issue is the same on focal and Jammy.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2028197

Title:
  rshim console truncates dmesg output due to tmfifo issue

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  mlxbf_tmfifo driver does not always schedule work for VIRTIO CONSOLE
  nottification. The result is with rshim console, the dmesg output
  would be cut off or simply cat a big text file to stdout.

  [Fix]

  * Make sure TM_TX_LWM_IRQ bit is set when there is a notification of
  virtio console event.

  [Test Case]

  * Compare the output of dmesg from rshim console and ssh session. Make sure 
both are the same.
  * Issue is reproduced w/o fix and compare the same dmesg output from the same 
as above.

  [Regression Potential]

  The changes affect only virtio console event handling only and been
  tested fully.

  [Others]
  This issue is the same on focal and Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028197/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2026776] Re: arm64+ast2600: No Output from BMC's VGA port

2023-07-19 Thread Ian May

With Kinetic going EOL, there will be no further SRU updates for linux-
hwe-5.19

** Description changed:

+ SRU Justification:
+ 
+ [ Impact ]
+ 
+ On systems that have the following combination of hardware
+ 
+ 1) arm64 CPU 
+ 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/
+ 
+ No output when connecting a display to the BMC's VGA port.
+ 
+ [ Fix ]
+ 
+ For AST2500+ MMIO should be enabled by default.
+ 
+ [ Test Plan ]
+ 
+ Test on targeted hardware to make sure BMC is displaying output.
+ 
+ [ Where problems could occur ]
+ 
+ Not aware of any potential problems, but any should be confined to
+ ASPEED AST2500+ hardware.
+ 
+ [ Other Info ]
+ 
+ Patch is already in jammy/nvidia-5.19 and jammy/nvidia-6.2 and has been
+ tested with affected BMC.
+ 
+ 
+ 
  [Issue]
  
  On systems that have the following combination of hardware...:
  
  1) arm64 CPU
  2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/
  
  .. we see no output when connecting a display to the BMC's VGA port.
  
  Upon further investigation, we see that applying the following patch
  fixes this issue:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6=4327a6137ed43a091d900b1ac833345d60f32228
  
  [Action]
  
  Please apply the following two backports to the appropriate Ubuntu HWE
  kernels:
  
  
https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560
  
https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7

** Changed in: linux-hwe-5.19 (Ubuntu)
   Status: New => Won't Fix

-- 
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/2026776

Title:
  arm64+ast2600: No Output from BMC's VGA port

Status in linux package in Ubuntu:
  New
Status in linux-hwe-5.19 package in Ubuntu:
  Won't Fix
Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [ Impact ]

  On systems that have the following combination of hardware

  1) arm64 CPU 
  2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/

  No output when connecting a display to the BMC's VGA port.

  [ Fix ]

  For AST2500+ MMIO should be enabled by default.

  [ Test Plan ]

  Test on targeted hardware to make sure BMC is displaying output.

  [ Where problems could occur ]

  Not aware of any potential problems, but any should be confined to
  ASPEED AST2500+ hardware.

  [ Other Info ]

  Patch is already in jammy/nvidia-5.19 and jammy/nvidia-6.2 and has
  been tested with affected BMC.


  
  [Issue]

  On systems that have the following combination of hardware...:

  1) arm64 CPU
  2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/

  .. we see no output when connecting a display to the BMC's VGA port.

  Upon further investigation, we see that applying the following patch
  fixes this issue:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6=4327a6137ed43a091d900b1ac833345d60f32228

  [Action]

  Please apply the following two backports to the appropriate Ubuntu HWE
  kernels:

  
https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560
  
https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"

2023-07-19 Thread dann frazier

** Changed in: linux-nvidia-6.2 (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2026891

Title:
  linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at
  init/main.c:1065 start_kernel+0x4da/0x540"

Status in linux-nvidia-6.2 package in Ubuntu:
  In Progress

Bug description:
  We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia
  servers (DGX-1/DGX-2/H100) and hit the following warning during boot:

  [7.690486] [ cut here ]
  [7.690487] Interrupts were enabled early
  [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 
start_kernel+0x4da/0x540
  [7.690498] Modules linked in:
  [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia 
#4~22.04.1-Ubuntu
  [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 
06/07/2021
  [7.690505] RIP: 0010:start_kernel+0x4da/0x540
  [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff 
ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 
ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff
  [7.690510] RSP: :98803f08 EFLAGS: 00010246
  [7.690512] RAX:  RBX:  RCX: 

  [7.690513] RDX:  RSI:  RDI: 

  [7.690514] RBP: 98803f20 R08:  R09: 

  [7.690515] R10:  R11:  R12: 
00e0
  [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 
5a1d7ee0
  [7.690518] FS:  () GS:96490060() 
knlGS:
  [7.690520] CS:  0010 DS:  ES:  CR0: 80050033
  [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 
000606f0
  [7.690522] DR0:  DR1:  DR2: 

  [7.690523] DR3:  DR6: fffe0ff0 DR7: 
0400
  [7.690524] Call Trace:
  [7.690526]  
  [7.690529]  x86_64_start_kernel+0x102/0x180
  [7.690536]  secondary_startup_64_no_verify+0xe5/0xeb
  [7.690544]  
  [7.690544] ---[ end trace  ]---

  I also see pretty much the same thing on some Ampere based arm64
  servers:

  [0.000519] [ cut here ]
  [0.000521] Interrupts were enabled early
  [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 
start_kernel+0x3ac/0x514
  [0.000531] Modules linked in:
  [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia 
#4~22.04.1-Ubuntu
  [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  [0.000540] pc : start_kernel+0x3ac/0x514
  [0.000543] lr : start_kernel+0x3ac/0x514
  [0.000545] sp : dec5ff733e60
  [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 
403ffdd124e0
  [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 
001dba7b
  [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: 
dec5ff749140
  [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: 
dec5ff74a1c8
  [0.000558] x17:  x16:  x15: 

  [0.000560] x14:  x13: 0a796c7261652064 x12: 
656c62616e652065
  [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : 

  [0.000565] x8 :  x7 :  x6 : 

  [0.000568] x5 :  x4 :  x3 : 

  [0.000571] x2 :  x1 :  x0 : 

  [0.000573] Call trace:
  [0.000574]  start_kernel+0x3ac/0x514
  [0.000577]  __primary_switched+0xc0/0xc8
  [0.000580] ---[ end trace  ]---

  The warning does not appear on an older thunderx2 server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028195] [NEW] Apply additional high priority patches from NVIDIA patch list

2023-07-19 Thread Jacob Martin

Public bug reported:

[Impact]
This change includes the application of two patches meant to resolve a crash in 
the tegra-xudc driver, and to implement thermal zone support for mlx5-based 
hardware.

This consists of the following upstream patches:
5629d31 usb: gadget: tegra-xudc: Fix crash in vbus_draw 
c1fef61 net/mlx5: Implement thermal zone

** Affects: linux-nvidia-tegra-igx (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu.
https://bugs.launchpad.net/bugs/2028195

Title:
  Apply additional high priority patches from NVIDIA patch list

Status in linux-nvidia-tegra-igx package in Ubuntu:
  New

Bug description:
  [Impact]
  This change includes the application of two patches meant to resolve a crash 
in the tegra-xudc driver, and to implement thermal zone support for mlx5-based 
hardware.

  This consists of the following upstream patches:
  5629d31 usb: gadget: tegra-xudc: Fix crash in vbus_draw 
  c1fef61 net/mlx5: Implement thermal zone

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2028195/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1041.40)

2023-07-19 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1041.40) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

dm-writeboost/2.2.13-1ubuntu3 (amd64, arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64)
glibc/2.35-0ubuntu3.1 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.1 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT

2023-07-19 Thread Joseph Salisbury

** Tags removed: verification-needed-jammy verification-needed-lunar
** Tags added: verification-done-jammy verification-done-lunar

-- 
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/2018591

Title:
  Enable Tracing Configs for OSNOISE and TIMERLAT

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  In Progress

Bug description:
  == SRU Justification ==
  These config changes will allow tracing with the OSNOISE and TIMERLAT tracing 
tools.

  These tracers can be enabled at run-time and should not affect
  performance or add any additional overhead.

  == Fix ==
  UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs

  == Regression Potential ==
  Low.  These config changes will just allow the use of tracing tools.

  == Test Case ==
  Test build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028174] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r

*** This bug is a duplicate of bug 2017227 ***
https://bugs.launchpad.net/bugs/2017227

As far as I am able to determine, this has been resolved for me by
following the steps in the comments of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017227 .

** This bug has been marked a duplicate of bug 2017227
   package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: »installiertes post-installation-Skript des Paketes 
linux-headers-6.2.0-20-generic«-Unterprozess gab den Fehlerwert 1 zurück

-- 
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/2028174

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: installed linux-headers-6.2.0-25-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Tried upgrading to 23.04 from 22.10, and received this error regarding
  the core update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  governor   1996 F wireplumber
   /dev/snd/controlC0:  governor   1996 F wireplumber
   /dev/snd/seq:governor   1993 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 09:52:40 2023
  ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-07 (467 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515UA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515UA.305:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515UA_M515UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515UA_M515UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2019072] Re: 600+ duplicate or duplicated firmware files exist.

2023-07-19 Thread wontfix

** Description changed:

  Over 600 duplicate or duplicated firmware files exist. Less than two
  years ago it was 650~MB on disk. Three years ago it was 500~MB. Today it
- hovers around 900MB.
- 
- find /lib/firmware/ ! -empty -type f -exec md5sum {} + | sort | uniq
- -w32 -dD && du -sh /lib/firmware
+ hovers around 900MB

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2019072

Title:
  600+ duplicate or duplicated firmware files exist.

Status in Linux Firmware:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Triaged
Status in linux-firmware source package in Focal:
  Triaged
Status in linux-firmware source package in Jammy:
  Triaged
Status in linux-firmware source package in Lunar:
  Triaged
Status in linux-firmware source package in Mantic:
  Fix Released

Bug description:
  Over 600 duplicate or duplicated firmware files exist. Less than two
  years ago it was 650~MB on disk. Three years ago it was 500~MB. Today
  it hovers around 900MB

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2019072/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/6.2.0.1009.9)

2023-07-19 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-azure (6.2.0.1009.9) for 
lunar have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-525/525.125.06-0ubuntu0.23.04.1 (amd64, arm64)
rtpengine/unknown (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2026652] Re: Suspend Broken

2023-07-19 Thread Marlen T. B.

After updating and restarting I can again use the hacky script I was
using before. I wish sleep just worked normally :(

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/2026652

Title:
Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
New

Bug description:
When I go to suspend my system via the UI "Suspend" option, the system
fails to suspend. Instead it looks like its going to suspend, and then
wakes up but with a locked screen.

When I use `pm-suspend` from the command line, it suspends the system,
but does not lock the screen. I have the Settings -> Privacy -> Screen
Lock -> "Lock Screen on Suspend" setting enabled.

I am using the Nouveau driver, with Wayland, using GNOME 44.2.
This bug only started when I switched away from using any of the NVIDIA
drivers, so its probably partially Nouveau related. Switching back to the
NVIDIA drivers (I tried them all) isn't an option, because they break:
1. External monitor connectivity
2. VMWare Horizon

Debug info:

1. `lsb_release -rd`
Description: Ubuntu 23.04
Release: 23.04

2. `uname -srm`
Linux 6.2.0-1007-lowlatency x86_64

Please let me know of any other information needed to debug this.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
Uname: Linux 6.2.0-1007-lowlatency x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 9 10:26:06 2023
InstallationDate: Installed on 2021-12-18 (567 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: linux-signed-lowlatency
UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+subscriptions

--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028190] [NEW] kernel panic when using conntrack tcp pedit

2023-07-19 Thread William Tu

Public bug reported:

* Explain the bug(s)

when setting up conntrack offload with tcp pedit (test-ct-tcp-pedit.sh),
encounter kernel panic.

* brief explanation of fixes

In tc_setup_flow_action, need to properly assign action.
Which fixes previous commit ("UBUNTU: SAUCE: net/sched: Provide act to offload 
action")

* Kernel log

[  226.156222] Unable to handle kernel access to user memory outside uaccess 
routines at
[  226.177783] Mem abort info:
[  226.183408]   ESR = 0x9604
[  226.190953]   EC = 0x25: DABT (current EL), IL = 32 bits
[  226.201641]   SET = 0, FnV = 0
[  226.207786]   EA = 0, S1PTW = 0
[  226.214095]   FSC = 0x04: level 0 translation fault
[  226.223906] Data abort info:
[  226.229695]   ISV = 0, ISS = 0x0004
[  226.237410]   CM = 0, WnR = 0
[  226.243372] user pgtable: 4k pages, 48-bit VAs, pgdp=000123f25000
[  226.256328] [0090] pgd=, p4d=
[  226.269984] Internal error: Oops: 9604 [#1] SMP
[  226.279779] Modules linked in: act_pedit act_ct nf_flow_table iptable_raw 
xt_CT xt_tcpudp bpfilter xt_comment xt_mark
[  226.279938]  async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
xor_neon raid6_pq raid1 raid0 multipath
[  226.544260] CPU: 2 PID: 4293 Comm: handler3 Tainted: G
[  226.565581] Hardware name: https://www.mellanox.com BlueField SoC/BlueField 
SoC, BIOS 4.2.0.12795 Jun 30 2023
[  226.585497] pstate: a045 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[  226.599481] pc : tcf_action_update_stats+0x8/0xc4
[  226.608933] lr : mlx5e_tc_act_stats_fill_stats+0xf8/0x19c [mlx5_core]
[  226.622089] sp : 8e073130
[  226.628735] x29: 8e073130 x28: 0008 x27: 0020
[  226.643067] x26: ffe0 x25: 5913c62dfe71 x24: 5913c62dfe00
[  226.657398] x23:  x22:  x21: 5913c62dfe70
[  226.671730] x20: 5913c2fc3b00 x19: 5913f0058000 x18: 0014
[  226.686059] x17: b96d1a87 x16: c6320acb93e0 x15: 
[  226.700390] x14: 0001 x13:  x12: 0002
[  226.714720] x11: 7f7f7f7f7f7f7f7f x10:  x9 : c631ce0b66ac
[  226.729052] x8 : 8e073130 x7 :  x6 : 000d
[  226.743384] x5 : 0c62 x4 : 0001 x3 : 
[  226.757715] x2 :  x1 :  x0 : 
[  226.772047] Call trace:
[  226.776947]  tcf_action_update_stats+0x8/0xc4
[  226.785695]  mlx5e_tc_act_stats_fill_stats_flow+0x78/0xc0 [mlx5_core]
[  226.798833]  mlx5e_stats_flower+0x394/0x3c0 [mlx5_core]
[  226.809502]  mlx5e_rep_setup_tc_cls_flower+0x8c/0xa0 [mlx5_core]
[  226.821732]  mlx5e_rep_setup_tc_cb+0x74/0xb0 [mlx5_core]
[  226.832549]  tc_setup_cb_call+0xa4/0x160
[  226.840426]  fl_hw_update_stats+0x98/0x164 [cls_flower]
[  226.850927]  fl_dump.part.0+0x224/0x260 [cls_flower]
[  226.860891]  fl_dump+0x20/0x34 [cls_flower]
[  226.869284]  tcf_fill_node+0x164/0x244
[  226.876803]  tfilter_notify+0xc0/0x140
[  226.884323]  tc_new_tfilter+0x454/0x8bc
[  226.892018]  rtnetlink_rcv_msg+0x2e8/0x3cc
[  226.900245]  netlink_rcv_skb+0x64/0x130
[  226.907942]  rtnetlink_rcv+0x20/0x30
[  226.915110]  netlink_unicast+0x2ec/0x360
[  226.922977]  netlink_sendmsg+0x278/0x490
[  226.930846]  sock_sendmsg+0x5c/0x6c
[  226.937845]  sys_sendmsg+0x290/0x2d4
[  226.945712]  ___sys_sendmsg+0x84/0xd0
[  226.953059]  __sys_sendmsg+0x70/0xd0
[  226.960229]  __arm64_sys_sendmsg+0x2c/0x40
[  226.968447]  invoke_syscall+0x78/0x100
[  226.975974]  el0_svc_common.constprop.0+0x54/0x184
[  226.985587]  do_el0_svc+0x30/0xac
[  226.992231]  el0_svc+0x48/0x160
[  226.998528]  el0t_64_sync_handler+0xa4/0x130
[  227.007094]  el0t_64_sync+0x1a4/0x1a8
[  227.01] Code: 9407cf7e d503201f aa1e03e9 d503201f (f9404805)
[  227.026679] ---[ end trace 2aa44f8c6701f98e ]---
[  236.273308] Kernel panic - not syncing: Oops: Fatal exception
[  236.284885] SMP: stopping secondary CPUs
[  236.292761] Kernel Offset: 0x463201de from 0x8800
[  236.304996] PHYS_OFFSET: 0xa6ed4000
[  236.313387] CPU features: 0x800804a1,2846
[  236.322129] Memory Limit: none
[  273.872736] Rebooting in 10 seconds..

** Affects: linux-bluefield (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2028190

Title:
  kernel panic when using conntrack tcp pedit

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Explain the bug(s)

  when setting up conntrack offload with tcp pedit (test-ct-tcp-
  pedit.sh), encounter kernel panic.

  * brief explanation of fixes

  In tc_setup_flow_action, need to properly assign action.
  Which fixes previous commit ("UBUNTU: SAUCE: net/sched: Provide act to 
offload action")

  * Kernel log

  [

[Kernel-packages] [Bug 2025396] Re: kdump/kexec does not work when UEFI secureboot and kernel lockdown enabled

2023-07-19 Thread dann frazier

It seems like this would impact the generic kernel as well, in which
case, it would be nice to fix it there and let the -bluefield kernel
inherit it via rebase.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2025396

Title:
  kdump/kexec does not work when UEFI secureboot and kernel lockdown
  enabled

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Explain the bug(s)

  We've found that for Jammy 5.15 and also 5.4.0-1049 kernel running on
  Bluefield, the kdump doesn't work when enabling secure boot[1].

  * How to test
  Make sure kernel config: 
  CONFIG_SECURITY_LOCKDOWN_LSM=y
  CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y
  CONFIG_LOCK_DOWN_IN_SECURE_BOOT=y

  The kdump kernel we use is actually signed correctly 
  # file /boot/vmlinuz-5.15.0-1015-bluefield
  /boot/vmlinuz-5.15.0-1015-bluefield: gzip compressed data, was 
"vmlinuz-5.15.0 1015-bluefield.efi.signed",

  # kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0xcfe0
     /boot/vmlinuz-5.4.0-1049-bluefield
  kdump initrd:
     /boot/initrd.img-5.4.0-1049-bluefield
  current state:Not ready to kdump

  kdump-tools.service - Kernel crash dump capture service
   Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Thu 2023-04-13 19:21:01 UTC; 4 days ago
  Process: 1975 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/SUCCESS)
     Main PID: 1975 (code=exited, status=0/SUCCESS)
  Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net systemd[1]: Starting 
Kernel crash dump capture serv>
  Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[1975]: 
Starting kdump-tools:
  Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2184]:  * 
Creating symlink /var/lib/kdu>
  Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2184]:  * 
Creating symlink /var/lib/kdu>
  Apr 13 19:21:01 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2525]: syscall 
kexec_file_load not avai>
  Apr 13 19:21:01 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2184]:  * 
failed to load kdump kernel

  * Possible reason
  Currently, a problem faced by arm64 is if a kernel image is signed by a MOK 
key, loading it via the kexec_file_load() system call would be rejected with 
the error in dmesg
  "Lockdown: kexec: kexec of unsigned images is restricted; see man 
kernel_lockdown.7".

  I backported the two below [2]:
  0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel 
image signature
  c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic

  However still kdump/kexec fails due to lockdown
  [ 353.298348] Lockdown: kexec: kexec of unsigned images is restricted; see 
man kernel_lockdown.7
  [ 364.833004] audit: type=1400 audit(1686619435.331:16): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="cri-containerd.apparmor.d" 
pid=15407 comm="apparmor_parser"

  If I disable kernel lockdown (CONFIG_SECURITY_LOCKDOWN_LSM=n), then
  kexec works ok. But this is not an acceptable workaround.

  * How to fix
  I got it working (secure boot + lockdown config enabled + kdump/kexec) using 
kernel v6.4 on bluefield, which means if we backport properly, mostly missing 
some arch/arm64/ patches, to BlueField 5.15 kernel, we can get it working.

  Reference
  1. 
https://docs.nvidia.com/networking/display/BlueFieldDPUOSv392/UEFI%20Secure%20Boot
  2. https://www.spinics.net/lists/arm-kernel/msg979554.html
  3. https://mjg59.dreamwidth.org/50577.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2025396/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2027567] Re: No more HDMI

2023-07-19 Thread Laurent Lyaudet

Hello,
I just tested latest kernel proposed in
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed
6.2.0-27.28 solves my problem :)
Thank you very much :)
Best regards,
   Laurent Lyaudet

** Changed in: linux (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2027567

Title:
  No more HDMI

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hello,
  Thanks for your hard work :)
  I just upgraded to kernel 6.2.0-25.
  There is no more HDMI and my external screen can not be used.
  Moreover, when I stop my laptop, it takes 30s.
  If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop 
takes a few seconds.
  I'll join screenshots of command:
  ls /sys/class/drm/*

  Thanks, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5201 F wireplumber
   /dev/snd/controlC1:  laurent5201 F wireplumber
   /dev/snd/seq:laurent5192 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 11:34:15 2023
  InstallationDate: Installed on 2020-07-01 (1105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-25-generic N/A
   linux-backports-modules-6.2.0-25-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)

2023-07-19 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe-5.19 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2020656

Title:
  system freeze (cpu fan goes high)

Status in linux-signed-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  More than once a day the system totally freeze.

  CPU fan then goes higher and higher.

  Does not seem to be related to system load as yesterday it happend
  during lunch break.

  Today's journalctl -b -1 last message is 
  mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 
stuck for 167s! [opt ax7ixzwwoey:158586]

  There are many more of the same kind just before

  
  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  $ apt-cache policy linux-image-5.19.0-42-generic
  linux-image-5.19.0-42-generic:
Installé : 5.19.0-42.43~22.04.1
Candidat : 5.19.0-42.43~22.04.1
   Table de version :
   *** 5.19.0-42.43~22.04.1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  Note this problem was present before last kernel updates

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 24 12:00:08 2023
  InstallationDate: Installed on 2023-03-25 (59 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=alacritty
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020656/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1973827] Re: Laptop freezes when recovering from suspend / sleep mode

2023-07-19 Thread Mike Pontillo

ack; filed bug 2028186.

-- 
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/1973827

Title:
  Laptop freezes when recovering from suspend / sleep mode

Status in gnome-shell package in Ubuntu:
  Expired
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  When I lock the laptop and unlock it - I have no issues.

  If I allow it to lock and then sleep, or close the lid and suspend -
  when I open it again, I get the login prompt but cannot use mouse /
  keyboard.

  The only solution I have is to press and hold the power button and
  force shutdown and then boot back up

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  No particular package being used.

  I would expect the system to recover from suspend / sleep and allow me
  to enter password.

  The laptop froze completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 17 21:45:17 2022
  InstallationDate: Installed on 2022-04-22 (25 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973827/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028186] [NEW] zfs with encryption: sluggish resume from suspend, intermittent freezes

2023-07-19 Thread Mike Pontillo

Public bug reported:

I had been using Jammy on a Thinkpad T470 for months without problems.

I decided to try a fresh Ubuntu Desktop install using ZFS, using the
install-time option for full-disk encryption.

After using the fresh install for a little while, I noticed that the
system was "more sluggish" in the ZFS configuration (which was
disappointing, but tolerable).

The "sluggishness" is especially noticeable when resuming from suspend.
Typically, I'll look at the system clock and notice that it does not
change for ~tens of seconds. On some occasions, it will freeze
completely (even after waiting many minutes) and require a reboot.

Given that this the only difference between a "perfectly working system"
and "problematic system" was the filesystem change, I strongly suspect
ZFS as the cause (and/or perhaps enabling the full-disk encryption
option for it during the install).

Any advice on how to further triage this and narrow down the issue would
be appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 19 10:03:03 2023
InstallationDate: Installed on 2023-03-22 (119 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.19 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

** Description changed:

  I had been using Jammy on a Thinkpad T470 for months without problems.
  
  I decided to try a fresh Ubuntu Desktop install using ZFS, using the
  install-time option for full-disk encryption.
  
  After using the fresh install for a little while, I noticed that the
  system was "more sluggish" in the ZFS configuration (which was
  disappointing, but tolerable).
  
  The "sluggishness" is especially noticeable when resuming from suspend.
  Typically, I'll look at the system clock and notice that it does not
  change for ~tens of seconds. On some occasions, it will freeze
  completely (even after waiting many minutes) and require a reboot.
  
  Given that this the only difference between a "perfectly working system"
- and "problematic system" was enabling the ZFS option, I strongly suspect
+ and "problematic system" was the filesystem change, I strongly suspect
  ZFS as the cause (and/or perhaps enabling the full-disk encryption
  option for it during the install).
  
  Any advice on how to further triage this and narrow down the issue would
  be appreciated.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 19 10:03:03 2023
  InstallationDate: Installed on 2023-03-22 (119 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2028186

Title:
  zfs with encryption: sluggish resume from suspend, intermittent
  freezes

Status in linux-signed-hwe-5.19 package in Ubuntu:
  New

Bug description:
  I had been using Jammy on a Thinkpad T470 for months without problems.

  I decided to try a fresh Ubuntu Desktop install using ZFS, using the
  install-time option for full-disk encryption.

  After using the fresh install for a little while, I noticed that the
  system was "more sluggish" in the ZFS configuration (which was
  disappointing, but tolerable).

  The "sluggishness" is especially noticeable when resuming from
  suspend. Typically, I'll look at the system clock and notice that it
  does not change for ~tens of seconds. On some occasions, it will
  freeze completely (even after waiting many minutes) and require a
  reboot.

  Given that this the only difference between a "perfectly working
  system" and "problematic system"

[Kernel-packages] [Bug 2028122] Re: Fix unreliable ethernet cable detection on I219 NIC

2023-07-19 Thread Anthony Wong

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.1 (Ubuntu Mantic)
   Importance: Undecided
   Status: Invalid

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: linux-oem-6.1 (Ubuntu Lunar)
   Status: Won't Fix => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2028122

Title:
  Fix unreliable ethernet cable detection on I219 NIC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  New
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Hotplugging RJ45 ethernet cable only works for one time because ACPI GPE
  wake doesn't working properly anymore.

  [Fix]
  Always use PME poll to read PCI PME to know if there's wake event.

  [Test]
  With the patch applied, ethernet cable can always be detected.

  [Where problems could occur]
  PME poll mechanism periodically reads the PMCTRL register, so the power
  consumption can be slightly higher. The increase will be very low,
  probably won't be noticeable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2028122/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028182] Re: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-07-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2028182

Title:
  package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  While updating from the software manager this popped up

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tarik  1401 F pipewire
tarik  1404 F wireplumber
   /dev/snd/seq:tarik  1401 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 19:12:47 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-06-23 (25 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Micro-Star International Co., Ltd. Modern 14 B11MOL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic 
root=UUID=01345a2f-0db8-464d-b6ac-3f613eac78d6 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E14D3IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14D3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE14D3IMS.113:bd12/30/2021:br1.19:svnMicro-StarInternationalCo.,Ltd.:pnModern14B11MOL:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku14D3.1:
  dmi.product.family: Modern
  dmi.product.name: Modern 14 B11MOL
  dmi.product.sku: 14D3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028182/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

2023-07-19 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2028165

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028182] [NEW] package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-07-19 Thread Tarık Kum

Public bug reported:

While updating from the software manager this popped up

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-25-generic 6.2.0-25.25
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tarik  1401 F pipewire
  tarik  1404 F wireplumber
 /dev/snd/seq:tarik  1401 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Wed Jul 19 19:12:47 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2023-06-23 (25 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: Micro-Star International Co., Ltd. Modern 14 B11MOL
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic 
root=UUID=01345a2f-0db8-464d-b6ac-3f613eac78d6 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: dkms
Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2021
dmi.bios.release: 1.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E14D3IMS.113
dmi.board.asset.tag: Default string
dmi.board.name: MS-14D3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE14D3IMS.113:bd12/30/2021:br1.19:svnMicro-StarInternationalCo.,Ltd.:pnModern14B11MOL:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku14D3.1:
dmi.product.family: Modern
dmi.product.name: Modern 14 B11MOL
dmi.product.sku: 14D3.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

** Affects: dkms (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2028182

Title:
  package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 11

Status in dkms package in Ubuntu:
  New

Bug description:
  While updating from the software manager this popped up

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tarik  1401 F pipewire
tarik  1404 F wireplumber
   /dev/snd/seq:tarik  1401 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 19:12:47 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-06-23 (25 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Micro-Star International Co., Ltd. Modern 14 B11MOL
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic 
root=UUID=01345a2f-0db8-464d-b6ac-3f613eac78d6 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: E14D3IMS.113
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-14D3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE14D3IMS.113:bd12/30/2021:br1.19:svnMicro-StarInternationalCo.,Ltd.:pnModern14B11MOL:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku14D3.1:
  dmi.product.family: Modern
  dmi.product.name: Modern

[Kernel-packages] [Bug 2028174] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r

Found the issue in `DpkgTerminalLog.txt`, same as in the comment for
previous report of same issue here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017610/comments/4

Will run `apt install evdi-dkms` per comment, and update with result.

-- 
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/2028174

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: installed linux-headers-6.2.0-25-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Tried upgrading to 23.04 from 22.10, and received this error regarding
  the core update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  governor   1996 F wireplumber
   /dev/snd/controlC0:  governor   1996 F wireplumber
   /dev/snd/seq:governor   1993 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 09:52:40 2023
  ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-07 (467 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515UA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515UA.305:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515UA_M515UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515UA_M515UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028174] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r

Attaching `lspci-vnvn.log` file.

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+attachment/5687176/+files/lspci-vnvn.log

-- 
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/2028174

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: installed linux-headers-6.2.0-25-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Tried upgrading to 23.04 from 22.10, and received this error regarding
  the core update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  governor   1996 F wireplumber
   /dev/snd/controlC0:  governor   1996 F wireplumber
   /dev/snd/seq:governor   1993 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 09:52:40 2023
  ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-07 (467 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515UA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515UA.305:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515UA_M515UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515UA_M515UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028174] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r

2023-07-19 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
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/2028174

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: installed linux-headers-6.2.0-25-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Tried upgrading to 23.04 from 22.10, and received this error regarding
  the core update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  governor   1996 F wireplumber
   /dev/snd/controlC0:  governor   1996 F wireplumber
   /dev/snd/seq:governor   1993 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 09:52:40 2023
  ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-07 (467 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515UA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515UA.305:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515UA_M515UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515UA_M515UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028174] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r

Attaching `version.log` file

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+attachment/5687175/+files/version.log

-- 
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/2028174

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: installed linux-headers-6.2.0-25-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Tried upgrading to 23.04 from 22.10, and received this error regarding
  the core update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  governor   1996 F wireplumber
   /dev/snd/controlC0:  governor   1996 F wireplumber
   /dev/snd/seq:governor   1993 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 09:52:40 2023
  ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-07 (467 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: X515UA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X515UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515UA.305:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515UA_M515UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUSLaptop
  dmi.product.name: VivoBook_ASUSLaptop X515UA_M515UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028174/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2028174] [NEW] package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess

Public bug reported:

Tried upgrading to 23.04 from 22.10, and received this error regarding
the core update.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  governor   1996 F wireplumber
 /dev/snd/controlC0:  governor   1996 F wireplumber
 /dev/snd/seq:governor   1993 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Wed Jul 19 09:52:40 2023
ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-04-07 (467 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
dmi.bios.date: 10/21/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: X515UA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X515UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrX515UA.305:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515UA_M515UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUSLaptop
dmi.product.name: VivoBook_ASUSLaptop X515UA_M515UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

-- 
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/2028174

Title:
  package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to
  install/upgrade: installed linux-headers-6.2.0-25-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Tried upgrading to 23.04 from 22.10, and received this error regarding
  the core update.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-25-generic 6.2.0-25.25
  ProcVersionSignature: Ubuntu 5.19.0-46.47-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  governor   1996 F wireplumber
   /dev/snd/controlC0:  governor   1996 F wireplumber
   /dev/snd/seq:governor   1993 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Wed Jul 19 09:52:40 2023
  ErrorMessage: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-07 (467 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515UA_M515UA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=dd6e3788-00b0-48a8-8dbf-8d1899565da0 ro pcie_aspm=off
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to 
install/upgrade: installed linux-headers-6.2.0-25-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-07-19 (0 days ago)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends

[Kernel-packages] [Bug 2028096] Re: Blank screen when using GDM

2023-07-19 Thread Mahyar Mirrashed

*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887

What kind of logs can I provide to assist? I was thinking of maybe
sharing the pipe errors but, that was literally the only thing out of
the ordinary that I was seeing in the system journal.

For your workarounds. For the first option, how do I add the environment
variable to `/etc/environment`? All that I see in the file so far is my
PATH declaration in BaSH syntax in there. For the second option, if I
update the kernel, is that a reversible change?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2028096

Title:
  Blank screen when using GDM

Status in gdm:
  Unknown
Status in linux-oem-5.17 package in Ubuntu:
  New

Bug description:
  Refer to this issue that I created for the GDM developers:
  https://gitlab.gnome.org/GNOME/gdm/-/issues/860

  They have indicated that they will not fix this bug.

  Description:Ubuntu 22.04.2 LTS
  Release:22.04

  gnome-shell:
Installed: 42.9-0ubuntu2
Candidate: 42.9-0ubuntu2
Version table:
   *** 42.9-0ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  I am expecting not to have pipe errors between my integrated graphics
  card and GDM and for the login screen to appear.

  I got a pixelated screen and then a blank, black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1034.35-oem 5.17.15
  Uname: Linux 5.17.0-1034-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Jul 18 18:12:57 2023
  DisplayManager: sddm
  InstallationDate: Installed on 2023-06-14 (34 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu1
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/2028096/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1043.39)

2023-07-19 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1043.39) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

digimend-dkms/10-4 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2003714] Re: Azure: TDX enabled hyper-visors cause segfault

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2003714

Title:
  Azure: TDX enabled hyper-visors cause segfault

Status in linux-azure package in Ubuntu:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Microsoft TDX enabled hyper visors cause a segfault due to an upstream
  glibc bug. This can be worked around with a kernel patch.

  Issue Description:

  When I start an Intel TDX Ubuntu 22.04 (or RHEL 9.0) guest on Hyper-V,
  the guest always hits segfaults and can’t boot up. Here the kernel
  running in the guest is the upstream kernel + my TDX patchset, or the
  5.19.0-azure kernel + the same TDX patchset:

  [Fix]

  We confirmed the segfault also happens to TDX guests on the KVM
  hypervisor. After I checked with more Intel folks, it turns out this
  is indeed a glibc bug
  (https://sourceware.org/bugzilla/show_bug.cgi?id=28784), which has
  been fixed in the upsteram glibc, but Ubuntu 22.04 and newer haven’t
  picked up the glibc fix yet.

  I got a kernel side temporary workarouond from Intel:
  https://github.com/dcui/tdx/commit/16218cf73491e867fd39c16c9e4b8aa926cbda68,
  which is on the same existing branch “decui/upstream-
  kinetic-22.10/master-next/1209”.

  [   21.081453] Run /inits init process
  [   21.086896]   with arguments:
  [   21.095790] /init
  [   21.100982]   with environment:
  [   21.106611] HOME=/
  [   21.112463] TERM=linux
  [   21.119850] BOOT_IMAGE=/boot/vmlinuz-6.1.0-rc7-decui+

  Loading, please wait...

  Starting version 249.11-0ubuntu3.6

  [   21.253908] udevadm[144]: segfault at 56538d61e0c0 ip 7f8f5899efeb sp 
7ffd08fb7648 error 6 in libc.so.6[7f8f5882+195000] likely on CPU 0 
(core 0, socket 0)
  [   21.316549] Code: 07 62 e1 7d 48 e7 4f 01 62 e1 7d 48 e7 67 40 62 e1 7d 48 
e7 6f 41 62 61 7d 48 e7 87 00 20 00 00 62 61 7d 48 e7 8f 40 20 00 00 <62> 61 7d 
48 e7 a7 00 30 00 00 62 61 7d 48 e7 af 40 30 00 00 48 83

  Segmentation fault

  [   22.499317] setfont[153]: segfault at 55ef3b91b000 ip 7f5899899fa4 sp 
7ffc8008f628 error 4 in libc.so.6[7f589971b000+195000] likely on CPU 0 
(core 0, socket 0)
  [   22.602677] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1 fe 48 
6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00 00 <62> 61 fe 
48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83
  [   22.732413] loadkeys[156]: segfault at 563ffe292000 ip 7fbff957afa4 sp 
7ffe31453808 error 4 in libc.so.6[7fbff93fc000+195000] likely on CPU 0 
(core 0, socket 0)
  [   22.833061] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1 fe 48 
6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00 00 <62> 61 fe 
48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83

  The segfault only happens to recent glibc versions (e.g. v2.35 in
  Ubuntu 22.04, and v2.34 in RHEL 9.0). It doesn’t happens to v2.31 in
  Ubuntu 20.04, or v2.32 in Ubuntu 20.10. So something in glibc must
  have changed between v2.32 (good) and 2.34+ (not working for TDX). The
  oddity is: when I run the same Ubuntu 22.04/RHEL 9.0 image as a
  regular non-TDX guest, the segfault never happens.

  If I boot up a Ubuntu 20.04 TDX guest (which works fine), mount a
  Ubuntu 22.04 VHD image (“mount /dev/sdd1 /mnt”) and try to run “chroot
  /mnt”, I hit the same segfault:

  [  109.478556] EXT4-fs (sdd1): mounted filesystem with ordered data mode. 
Quota mode: none.
  [  129.22] bash[2112]: segfault at 556987854000 ip 7f88468c4ea4 sp 
7ffc22ecf158 error 6 in libc.so.6[7f8846828000+195000] likely on CPU 48 
(core 0, socket 48)
  [  129.242434] Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 
8f 10 20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f 
e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7

  It looks like the application is referencing a memory location that
  somehow triggers a page fault, which is converted to a sigal SIGSEGV,
  which causes a segfault and terminates the application (I’m not sure
  where the below “movntdq” instructions come from):

  root@decui-u2004-u28:/opt/linus-0824# echo 'Code: e7 bf 30 10 00 00 66
  44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20 00 00 66 44 0f e7 97 20
  20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f e7 a7 00 30 00 00 66 44
  0f e7 af 10 30 00 00 66 44 0f e7' | scripts/decodecode

  Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10
  20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44
  0f e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7

  All code
  
     0:   e7 bf   out%eax,$0xbf
     2:   30 10   xor%dl,(%rax)
     4:   00 00   add%al,(%rax)
     6:   66 44 0f e7 87 00 20movntdq %xmm8,0x2000(%rdi)

[Kernel-packages] [Bug 1972017] Re: Jammy/linux-azure: CONFIG_BLK_DEV_FD=n

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/1972017

Title:
  Jammy/linux-azure: CONFIG_BLK_DEV_FD=n

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  CONFIG_BLK_DEV_FD should be disabled, consistent with Focal and Impish
  kernel configurations. this config is also considered a security risk
  on cloud platforms.

  [Test Case]

  Look for floppy.ko in either of the modules packages.

  [Where things could go wrong]

  There should be no regression due to the removal of this module.

  [Other Info]

  SF: #00336330

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972017/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2002658] Re: Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2002658

Title:
  Kinetic linux-azure - Enable TDX guest driver w/MSFT Hyper-v

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Support for Intel TDX guest driver is just now appearing upstream.
  This patch set is a backport of the patches essential to enabling TDX
  guest support on the Microsoft hypervisor.

  Most of these patches are not yet upstream, but are considered benign
  with respect to MSFT hypervisors that do not yet have support for TDX.
  I have boot tested on an existing Hyper-v hypervisor to ensure
  backwards compatibility.

  This patch set will eventually be replaced by upstream patches.

  [Test Plan]

  Boot on a TDX enabled Hyper-v instance.

  [Where things could go wrong]

  Existing Azure instances could have boot issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2002658/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2004087] Re: Azure: Fix TDX backport

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2004087

Title:
  Azure: Fix TDX backport

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  A backport caused by a stable updates rebase was not performed
  correctly. The symptom is a failure to boot on TDX enabled
  hypervisors.

  [Fix]

  Make sure the sources match those of 'https://github.com/dcui/tdx.git
  decui/upstream-kinetic-22.10/master-next/1209'.

  [Test Plan]

  Boot on a TDX enabled hypervisor. Tested by Gauthier Jolly.

  [Where things could go wrong]

  This is a new feature isolated to TDX, so there is little chance of
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2004087/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2004090] Re: Azure: Performance improvement for TDX

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2004090

Title:
  Azure: Performance improvement for TDX

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  ms_hyperv_init_platform() hides HV_MSR_REFERENCE_TSC_AVAILABLE for TDX
  guests in favor of Invariant-TSC. In this case, we should also
  downgrade the rating of hyperv_cs_msr.rating, so Invariant-TSC can be
  used by default.

  [Fix]

  https://github.com/dcui/tdx.git
  367f18c06ac999c2822b0c24f50a87994635d4bd

  [Where things could go wrong]

  TDX guests may perform worse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2004090/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2014015] Re: Azure: Add new MANA VF performance counters for easier troubleshooting

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2014015

Title:
  Azure: Add new MANA VF performance counters for easier troubleshooting

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Won't Fix
Status in linux-azure source package in Kinetic:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Add new MANA VF performance counters for easier troubleshooting.

  [Regression potential]

  Regression potential is low given that this a new feature.

  [Test Plan]

  Microsoft tested.

  [Other Info]

  SF: #00357417

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2014015/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2007654] Re: enable Rust support in the kernel

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2007654

Title:
  enable Rust support in the kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Rust support has been merged starting with linux 6.1.

  This support allows to write external kernel modules using the Rust
  language. Modules written in this way are linked against the linux
  kernel and can be loaded/unloaded like any other .ko module.

  Main advantages of writing modules in Rust are:
   - memory safety:
     - no out of bounds accesses
     - no use after free
     - data race safety
   - strongly typed and statically typed
   - code extremely compact

  Roughly 70% of the security issues that the MSRC assigns a CVE to are memory 
safety issues:
   - Rust allows to write more secure and robust kernel code (reduce kernel 
CVEs)

  We should provide a Rust-enabled kernel so that people have the
  possibility to implement their own external kernel modules in Rust.

  [Test case]

  Build the following "hello world" test module:

  == hello_rust.rs ==

  // SPDX-License-Identifier: GPL-2.0

  //! Rust hello world example.

  use kernel::prelude::*;

  module! {
  type: HelloRust,
  name: "hello_rust",
  author: "Andrea Righi ",
  description: "Rust hello world example",
  license: "GPL",
  }

  struct HelloRust {
  }

  impl kernel::Module for HelloRust {
  fn init(_module: &'static ThisModule) -> Result {
  pr_info!("Hello from Rust\n");

  Ok(HelloRust { })
  }
  }

  impl Drop for HelloRust {
  fn drop( self) {
  pr_info!("Goodbye from Rust\n");
  }
  }

  == Makefile ==

  NAME=hello_rust

  ifndef KERNELRELEASE
  ifndef KDIR
  KDIR:=/lib/modules/`uname -r`/build
  endif
  PWD := $(shell pwd)

  all:
   $(MAKE) -C $(KDIR) M=$(PWD) modules
  install:
   $(MAKE) -C $(KDIR) M=$(PWD) modules_install
  clean:
   rm -f *.o *.ko *.mod* .*.cmd *.d Module.symvers modules.order
   rm -rf .tmp_versions
  else
   obj-m := $(NAME).o
  endif

  [Fix]

  Building the Rust support in the kernel requires specific versions of the 
Rust compiler and bindgen utility, same to build the external modules in Rust):
     - rustc 1.62.0
     - bindgen 0.56.0
     - clang/llvm (already required by BPF)

  Archive should provide these versions (ideally with a version suffix
  to avoid conflicting with the stock versions, e.g., rustc-1.62 and
  bindgen-0.56).

  In addition to that the kernel needs some packaging adjustments to use
  these special toolchain binaries and some special (not yet upstream)
  patches that would allow to enable mandatory features required in our
  generic kernel, such as:

   UBUNTU: SAUCE: allows to enable Rust with modversions
   UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion
   UBUNTU: SAUCE: scripts: Exclude Rust CUs with pahole
   UBUNTU: SAUCE: rust: allow to use INIT_STACK_ALL_ZERO

  With all of the above we can enable CONFIG_RUST in the kernel and
  provide support to build external modules (.ko) using Rust.

  [Regression potential]

  We may see build regressions due to the inavailability of the proper
  toolchain versions. Moreover these toolchain dependencies need to be
  maintained, making sure to be always aligned with upstream
  requirements, when stable updates are applied to the kernel.

  Moreover, hwe kernels require special attention, since this feature
  won't be available in old releases (unless the proper toolchain
  requirements are met).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007654/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2016995] Re: Azure: Build-in TDX guest driver

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2016995

Title:
  Azure: Build-in TDX guest driver

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure-5.19 package in Ubuntu:
  Invalid
Status in linux-azure source package in Jammy:
  Invalid
Status in linux-azure-5.19 source package in Jammy:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released
Status in linux-azure-5.19 source package in Kinetic:
  Invalid
Status in linux-azure source package in Lunar:
  Fix Released
Status in linux-azure-5.19 source package in Lunar:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  The TDX guest driver is currently packaged in linux-modules-extra.
  This is a non-optimal experience for users of the Azure image that is
  focused on TDX encryption and security.

  [Fix]

  Build in the TDX guest driver

  [Test Plan]

  Check that the TDX guest driver no longer appears in linux-modules-extra
  Microsoft tested as well.

  [Regression potential]

  There should be no regression potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2016995/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2013349] Re: Azure: smb3: allow deferred close timeout to be configurable

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2013349

Title:
  Azure: smb3: allow deferred close timeout to be configurable

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the ability to set a deferred close timeout to
  SMB3 connections.

  Upstream commit 5efdd9122eff772eae2feae9f0fc0ec02d4846a3 ('smb3: allow 
deferred close timeout to be configurable')
  commit 7e0e76d99079be13c9961dde7c93b2d1ee665af4 ('smb3: lower default 
deferred close timeout to address perf regression')
  commit 47f9e4c924025c5be87959d3335e66fcbb7f6b5c ('keys: Do not cache key in 
task struct if key is requested from kernel thread')

  [ Regression Potential ]

  This patch was committed to 6.0. Possible regressions include
  connections not closing, or closing later then the timeout would
  indicate.

  [ Test Plan ]

  Microsoft tested.

  [ Other Info ]

  SF: #00357322

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2013349/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015369] Re: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs

** Tags removed: verification-needed-kinetic verification-needed-lunar
** Tags added: verification-done-kinetic verification-done-lunar

-- 
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/2015369

Title:
  Azure: Add PCI pass-thru support to Hyper-V Confidential VMs

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Won't Fix
Status in linux-azure source package in Kinetic:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the inclusion of this patch set:

  https://lore.kernel.org/linux-hyperv/1679838727-87310-1-git-send-
  email-mikel...@microsoft.com/T/

  [Regression Potential]

  Private memory mappings could be incorrect.

  [Test Plan]

  Microsoft tested.

  [Other Info]

  SF: #00355859

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2015369/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2016898] Re: Azure: Enable MANA Jumbo Frame Support

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2016898

Title:
  Azure: Enable MANA Jumbo Frame Support

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  The MANA driver does not support jumbo frames

  [Fix]
  net: mana: Add support for jumbo frame
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=80f6215b450eb8e92d8b1f117abf5ecf867f963e

  net: mana: Enable RX path to handle various MTU sizes
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=2fbbd712baf1c60996554326728bbdbef5616e12

  net: mana: Refactor RX buffer allocation code to prepare for various MTU
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=a2917b23497e4205db32271e4e06e142a9f8a6aa

  net: mana: Use napi_build_skb in RX path
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=ce518bc3e9ca342309995c9270c3ec4892963695

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Regular frames could be discarded.

  [Other Info]

  SF: #00358566

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016898/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2018593] Re: Azure: Enable MANA Jumbo Frame Support reprise

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

-- 
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/2018593

Title:
  Azure: Enable MANA Jumbo Frame Support reprise

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-azure source package in Kinetic:
  Fix Released
Status in linux-azure source package in Lunar:
  Fix Released

Bug description:
  SRU Justification

  [Impact]

  The MANA driver is missing 2 commits in support of jumbo frames.

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/microsoft/mana?id=df18f2da302f169e1a29098c6ca3b474f1b0269e

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/microsoft/mana?id=5c74064f43c291d9add2b436a2d70205b71a7cc7

  [Test Plan]

  Microsoft tested

  [Regression Potential]

  Regular frames could be discarded.

  [Other Info]

  SF: #00358566

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2018593/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2022887] Re: add Fintek F81604 can controller support

2023-07-19 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-intel-iotg - 5.15.0-1035.40

---
linux-intel-iotg (5.15.0-1035.40) jammy; urgency=medium

  * jammy/linux-intel-iotg: 5.15.0-1035.40 -proposed tracker (LP:
#2027684)

  * add Fintek F81604 can controller support (LP: #2022887)
- can: skb: move can_dropped_invalid_skb() and can_skb_headroom_valid() to
  skb.c
- can: skb: drop tx skb if in listen only mode
- can: skb: unify skb CAN frame identification helpers
- can: dev: fix skb drop check
- can: usb: f81604: add Fintek F81604 support
- [Config]: updateconfigs for CONFIG_CAN_F81604

 -- Jian Hui Lee   Fri, 14 Jul 2023 00:29:07
+0800

** Changed in: linux-intel-iotg (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/2022887

Title:
  add Fintek F81604 can controller support

Status in linux-intel-iotg package in Ubuntu:
  Invalid
Status in linux-intel-iotg source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  add Fintek F81604 can controller support

  [Test Plan]
  1. compile test.
  2. check f81604 can controller functionalities on the hardware.
  3. test kernel is provided to the customer.

  [Regression potential]
  Low. one new driver is backported. the others are code revised and bug
  fixed, although they touch all the existent can drivers.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2022887/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package

** Tags removed: verification-needed-jammy verification-needed-lunar
** Tags added: verification-done-jammy verification-done-lunar

-- 
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/2021605

Title:
  introduce do_lib_rust=true|false to enable/disable linux-lib-rust
  package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-aws source package in Mantic:
  New

Bug description:
  [Impact]

  Provide a variable do_lib_rust=true|false in the kernel build system
  to selectively enable the Rust packaging (linux-lib-rust) with
  specific kernels and specific architectures.

  Right now Rust should be enabled only in lunar and mantic and only on
  amd64.

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

  Introduce a do_lib_rust=true variable that will be defined only in
  debian.master/rules.d/amd64.mk for now.

  [Regression potential]

  Kernels may need to set this variables if they want to enable the Rust
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2022940] Re: Azure: Fix perf regression: remove rx_cqes, tx_cqes counters for MANA

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

--
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/2022940

Title:
Azure: Fix perf regression: remove rx_cqes, tx_cqes counters for MANA

Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Lunar:
Fix Committed

Bug description:
SRU Justification

[Impact]

net: mana: Fix perf regression: remove rx_cqes, tx_cqes counters

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=1919b39fc6eabb9a6f9a51706ff6d03865f5df29

It resolves a big perf regression.

More details:
The apc->eth_stats.rx_cqes is one per NIC (vport), and it's on the
frequent and parallel code path of all queues. So, r/w into this
single shared variable by many threads on different CPUs creates a
lot caching and memory overhead, hence perf regression. And, it's
not accurate due to the high volume concurrent r/w.

For example, a workload is iperf with 128 threads, and with RPS
enabled. We saw perf regression of 25% with the previous patch
adding the counters. And this patch eliminates the regression.

Since the error path of mana_poll_rx_cq() already has warnings, so
keeping the counter and convert it to a per-queue variable is not
necessary. So, just remove this counter from this high frequency
code path.

Also, remove the tx_cqes counter for the same reason. We have
warnings & other counters for errors on that path, and don't need
to count every normal cqe processing.

[Test Plan]

MSFT tested

[Regression potential]

Counters are disappearing that may be in use by user space programs.

[Other Info]

SF: #00361807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2022940/+subscriptions

[Kernel-packages] [Bug 2023071] Re: [Azure] Fix VM crash/hang issues due to fast VF add/remove events

** Tags removed: verification-needed-jammy verification-needed-lunar
** Tags added: verification-done-jammy verification-done-lunar

-- 
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/2023071

Title:
  [Azure] Fix VM crash/hang issues due to fast VF add/remove events

Status in linux-azure package in Ubuntu:
  New
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]

  A Linux guest on Hyper-V/Azure can occasionally crash during early Linux 
kernel boot due to a strange host behavior:
  1. The host assigns a VF to the guest;
  2. The host immediately unassigns the VF from the guest; //Dexuan: due to 
some race conditions bug in Linux vPCI driver, Linux can crash.
  3. The host assigns the VF to the guest again.
  I'm asking the Hyper-V team to investigate the host behavior, but I'm not 
sure when they'll get that fixed.

  Starting late 2022 (around Nov 2022), Linux guests on Azure started to
  crash more frequently due to a host side update at that time: a new
  host/hypervisor feature of handling "correctable memory errors" can
  cause a lot of successive VF remove/add events, so the race conditions
  bug in Linux vPCI driver can surface much more easily. The Hyper-V
  team is implementing a batching mechanism so that the guest will get
  much less VF remove/add events (ETA: June 2023), but meanwhile we
  should also get the Linux race condition bugs fixed so that Linux
  guests won't crash even if it receives the successive VF remove/add
  events.

  [Test Plan]

  MSFT tested

  [Regression potential]

  Guests may continue to crash.

  [Other Info]

  SF: #00349076

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2023071/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels

2023-07-19 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-hwe-6.2 - 6.2.0-25.25~22.04.2

---
linux-hwe-6.2 (6.2.0-25.25~22.04.2) jammy; urgency=medium

  * jammy/linux-hwe-6.2: 6.2.0-25.25~22.04.2 -proposed tracker (LP:
#2024539)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper

  [ Ubuntu: 6.2.0-25.25 ]

  * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167)
  * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are
caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827)
- SAUCE: selftests/ftrace: Add test dependency
  * Add microphone support of the front headphone port on P3 Tower
(LP: #2023650)
- ALSA: hda/realtek: Add Lenovo P3 Tower platform
  * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539)
- ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6
  * Fix Disable thunderbolt clx make edp-monitor garbage while moving the
touchpad (LP: #2023004)
- drm/i915: Use 18 fast wake AUX sync len
  * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C
dongle (LP: #2021949)
- thunderbolt: Increase timeout of DP OUT adapter handshake
- thunderbolt: Do not touch CL state configuration during discovery
- thunderbolt: Increase DisplayPort Connection Manager handshake timeout
  * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591)
- [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs
  * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433)
- r8169: use spinlock to protect mac ocp register access
- r8169: use spinlock to protect access to registers Config2 and Config5
- r8169: enable cfg9346 config register access in atomic context
- r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context
- r8169: disable ASPM during NAPI poll
- r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll
  * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
(LP: #2021605)
- [Packaging] introduce do_lib_rust and enable it only on generic amd64
  * System either hang with black screen or rebooted on entering suspend on AMD
Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685)
- drm/amdgpu: refine get gpu clock counter method
- drm/amdgpu/gfx11: update gpu_clock_counter logic
  * generate linux-lib-rust only on amd64 (LP: #2020356)
- [Packaging] generate linux-lib-rust only on amd64
  * No  HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062)
- ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table
  * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
(LP: #1988806)
- SAUCE: Add mdev_set_iommu_device() kABI.
  * Enable audio LEDs on HP laptops (LP: #2019915)
- ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop
- ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop
  * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root
images (LP: #2019040)
- [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y
  * Lunar update: v6.2.13 upstream stable release (LP: #2023929)
- ARM: dts: rockchip: fix a typo error for rk3288 spdif node
- arm64: dts: rockchip: Lower sd speed on rk3566-soquartz
- arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node
- arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node
- arm64: dts: meson-g12-common: specify full DMC range
- arm64: dts: meson-g12-common: resolve conflict between canvas & pmu
- perf/amlogic: adjust register offsets
- arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers
- arm64: dts: imx8mm-evk: correct pmic clock source
- arm64: dts: imx8mm-verdin: correct off-on-delay
- arm64: dts: imx8mp-verdin: correct off-on-delay
- netfilter: br_netfilter: fix recent physdev match breakage
- netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT
- rust: str: fix requierments->requirements typo
- regulator: fan53555: Explicitly include bits header
- regulator: fan53555: Fix wrong TCS_SLEW_MASK
- virtio_net: bugfix overflow inside xdp_linearize_page()
- sfc: Fix use-after-free due to selftest_work
- netfilter: nf_tables: fix ifdef to also consider nf_tables=m
- i40e: fix accessing vsi->active_filters without holding lock
- i40e: fix i40e_setup_misc_vector() error handling
- netfilter: nf_tables: validate catch-all set elements
- cxgb4: fix use after free bugs caused by circular dependency problem
- netfilter: nf_tables: tighten netlink attribute requirements for catch-all
  elements
- bnxt_en: Do not initialize PTP on older P3/P4 chips
- mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next()
- LoongArch: Fix build error if CONFIG_SUSPEND is not set
- bonding: Fix memory leak when changing bond type to Ethernet
- net: rpl: fix rpl header size calculation
-

[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5

2023-07-19 Thread Paolo Pisati

** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu8.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+attachment/5687148/+files/nvidia-graphics-drivers-390_390.157-0ubuntu8.debdiff

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2028165

Title:
  nvidia-dkms-* FTBS with linux 6.5

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 source package in Mantic:
  New

Bug description:
  [Impact]

  ...
  In file included from 
/var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21,
   from 
/var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function 
‘NV_GET_USER_PAGES_REMOTE’:
  /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing 
argument 1 of ‘get_user_pages_remote’ from incompatible pointer type 
[-Werror=incompatible-pointer-types]
    164 |return get_user_pages_remote(tsk, mm, start, nr_pages, 
flags,
    | ^~~
    | |
    | struct task_struct *
  ...

  
  [Fix]

  Apply the attached fix.

  [How to test]

  Install (and build) the patched packet.

  [Regression potential]

  The fix is composed of two patches:

  1) the first patch simply garbage collect a reference to a function
  that was never used but that had the API changed in Linux 6.5 - so,
  it's a trivial change.

  2) the second patch actually reimplement part of the vma scanning that was 
removed in __get_user_pages_locked() in upstream commit 
b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas
  array from internal GUP functions" - here is where most likely any regression 
could be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1946433] Re: Fix only reach PC3 when ethernet is plugged r8169

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1946433

Title:
  Fix only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Triaged
Status in linux-oem-5.13 source package in Kinetic:
  Invalid
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.13 source package in Lunar:
  Invalid
Status in linux-oem-5.14 source package in Lunar:
  Invalid
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-5.13 source package in Mantic:
  Invalid
Status in linux-oem-5.14 source package in Mantic:
  Invalid
Status in linux-oem-5.17 source package in Mantic:
  Invalid
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  System only can reach PC3, and it affects power consumption alot.

  [Fix]
  Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state 
issue, but also fixes network speed issue.
  V7:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/
  V6:
  
https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/

  
  [Test]
  Verified on 2 different systems which has PC state issue and has network 
speed issue, these patches fix both issues.

  [Where problems could occur]
  It toggles ASPM on and off depends on the network traffic during runtime, I 
don't think it'll lead to any regressions. Some potential issues have been 
addressed during the patch submitting. It's v6 now and accepted by upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1946433/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-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/1977827

Title:
  ftrace in ubuntu_kernel_selftests failed with "check if duplicate
  events are caught" on J-5.15 P9 / J-kvm / L-kvm

Status in ubuntu-kernel-tests:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  Issue found on Jammy 5.15.0-36.37 with Power9 node baltar

  Test failed with:
  # [15] Generic dynamic event - check if duplicate events are caught [FAIL]

  Test Log:
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
   TAP version 13
   1..1
   # selftests: ftrace: ftracetest
   # === Ftrace unit tests ===
   # [1] Basic trace file check [PASS]
   # [2] Basic test for tracers [PASS]
   # [3] Basic trace clock test [PASS]
   # [4] Basic event tracing check  [PASS]
   # [5] Change the ringbuffer size [PASS]
   # [6] Snapshot and tracing setting   [PASS]
   # [7] trace_pipe and trace_marker[PASS]
   # [8] Test ftrace direct functions against tracers   [UNRESOLVED]
   # [9] Test ftrace direct functions against kprobes   [UNRESOLVED]
   # [10] Generic dynamic event - add/remove eprobe events  [PASS]
   # [11] Generic dynamic event - add/remove kprobe events  [PASS]
   # [12] Generic dynamic event - add/remove synthetic events   [PASS]
   # [13] Generic dynamic event - selective clear (compatibility)   [PASS]
   # [14] Generic dynamic event - generic clear event   [PASS]
   # [15] Generic dynamic event - check if duplicate events are caught  [FAIL]
   # [16] event tracing - enable/disable with event level files [PASS]
   # [17] event tracing - restricts events based on pid notrace filtering   
[PASS]
   # [18] event tracing - restricts events based on pid [PASS]
   # [19] event tracing - enable/disable with subsystem level files [PASS]
   # [20] event tracing - enable/disable with top level files   [PASS]
   # [21] Test trace_printk from module [PASS]
   # [22] ftrace - function graph filters with stack tracer [PASS]
   # [23] ftrace - function graph filters   [PASS]
   # [24] ftrace - function pid notrace filters [PASS]
   # [25] ftrace - function pid filters [PASS]
   # [26] ftrace - stacktrace filter command[PASS]
   # [27] ftrace - function trace with cpumask  [PASS]
   # [28] ftrace - test for function event triggers [PASS]
   # [29] ftrace - function trace on module [PASS]
   # [30] ftrace - function profiling   [PASS]
   # [31] ftrace - function profiler with function tracing  [PASS]
   # [32] ftrace - test reading of set_ftrace_filter[PASS]
   # [33] ftrace - test for function traceon/off triggers   [PASS]
   # [34] ftrace - test tracing error log support   [PASS]
   # [35] Test creation and deletion of trace instances while setting an event  
[PASS]
   # [36] Test creation and deletion of trace instances [PASS]
   # [37] Kprobe dynamic event - adding and removing[PASS]
   # [38] Kprobe dynamic event - busy event check   [PASS]
   # [39] Kprobe dynamic event with arguments   [PASS]
   # [40] Kprobe event with comm arguments  [PASS]
   # [41] Kprobe event string type argument [PASS]
   # [42] Kprobe event symbol argument  [PASS]
   # [43] Kprobe event argument syntax  [PASS]
   # [44] Kprobes event arguments with types[PASS]
   # [45] Kprobe event user-memory access   [UNSUPPORTED]
   # [46] Kprobe event auto/manual naming   [PASS]
   # [47] Kprobe dynamic event with function tracer [PASS]
   # [48] Create/delete multiprobe on kprobe event  [PASS]
   # [49] Kprobe event parser error log check   [PASS]
   # [50] Kretprobe dynamic event with arguments[PASS]
   # [51] Kretprobe dynamic event with maxactive[PASS]
   # [52] Kretprobe %return suffix test [PASS]
   # [53] Register/unregister many kprobe events[PASS]
   # [54] Kprobe profile[PASS]
   # [55] Uprobe event parser error log check

[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/1988806

Title:
  Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-5.19 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-hwe-5.19 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Triaged
Status in linux-hwe-5.19 source package in Mantic:
  Invalid

Bug description:
  With below commit in 5.16 upstream kernel, support for
  mdev_set_iommu_device() kABI was removed from kernel as there were no
  in-tree drivers making use of the kABI.

  fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")

  This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
  (SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
  kABI to pin all guest memory during VM boot.

  As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
  it will not include this kABI and as a result will break SRIOV based
  Nvidia vGPU. So, filing this bug to request to have a custom patch in
  HWE kernel which doesn't remove the support for
  mdev_set_iommu_device() kABI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988806/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/1998643

Title:
  smartpqi: Update 22.04 driver to include recent bug fixes and support
  current generation devices

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  These patches provide bug fixes and add support for the latest generation of 
OEM PCI devices to ensure customers are able to use Jammy on the recent 
generations of server hardware. This will bring us in line with the other major 
linux distros.

  [Fix]
  There are some outstanding patches already in Linus's tree that can be 
applied to 22.04.
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  The following patches apply to
  https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy

  f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
  e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
  6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
  2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
  cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
  6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
  69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
  85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
  2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
  44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
  331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
  904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
  297bdc540f0e scsi: smartpqi: Close write read holes
  dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
  1d393227fc76 scsi: smartpqi: Add controller fw version to console log
  4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
  8946ea283808 scsi: smartpqi: Fix typo in comment
  c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
  31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
  62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
  291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
  c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
  5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
  c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
  00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
  5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
  27655e9db479 scsi: smartpqi: Update volume size after expansion
  b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
  42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
  9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
  b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
  94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
  70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
  2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
  c57ee4ccb358 scsi: smartpqi: Add PCI IDs
  c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
  64fc9015fbeb scsi: smartpqi: Switch to attribute groups
  0ca190805784 scsi: smartpqi: Call scsi_done() directly

  I added the above SHA1 IDs to a file called:
  backport_linus_6.1_into_22.04

  git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
  git am -s /tmp/patches/*.diff

  All patches applied without any conflicts.

  [Test Plan]
  The upstream driver has undergone extensive testing by Microchip's test team 
before submitting those patches to the upstream kernel. All patches are tested 
and accepted in the upstream kernel at this time.

  One should be able to load the smartpqi driver and verify the version
  is at 2.1.18-045

  [Other Info]

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 2007745] Re: [SRU][Jammy] CONFIG_PCI_MESON is not enabled

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2007745

Title:
  [SRU][Jammy] CONFIG_PCI_MESON is not enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  SRU justification:

  [ Impact ]

  The PCI driver for the amlogic-based Meson platforms
  (CONFIG_PCI_MESON) is not enabled as a module in the kernel
  configuration: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=master#n7036

  [ Test Plan ]

  Check if pci_meson.ko is compiled and present in the linux-modules
  package.

  [ Where problems could occur ]

  * Enabling the driver could enable undesired dependencies 
  * Kernel module does not compile and breaks the build

  [ Other Info ]

  This driver is important for systems like the ODROID HC4, which uses a
  PCIE-SATA bridge to provide a storage interface. This system is fully
  supported by the kernel (including a device tree), except for the fact
  that this PCI driver is disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2008751

Title:
  [SRU] Backport request for hpwdt from upstream 6.1 to Jammy

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Please pick up the latest hpwdt from the upstream 6.1 kernel for
  Jammy. This version enables hpwdt on RL300 aarch64.

  [Fix]
  ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING

  891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems.

  [Test Plan]
  Boot system with the hpwdt enabled on an arm64 system

  [Where Problems Could Occur]

  Regression Risk is Low

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1

  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2008527

Title:
  [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup
  time is taking longer than expected

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  A Dell system that has a profile setting of "Performance Per Watt
  (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot
  into OS as quickly as expected.

  How reproducible:

  Steps to Reproduce:

  1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS.
  2. Install Ubuntu-22.04
  3. Boot into OS
  4. Check the bootup time

  Expected results:
  OS should boot normally and need to consume less bootup time

  [Fix]

  13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs

  [Test Plan]

  1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting
  2. Install Ubuntu-22.04
  3. Boot into OS
  4. Check the bootup time

  [Where problems could occur]

  Regression risk: low to medium.

  [Other Info]
  Jammy
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc

  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2012335

Title:
  Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores
  (256)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  There is a user reporting errors in setup with their Intel E810 NIC with
  error messages saying that the driver cannot allocate enough MSI-X vectors
  on their 256 cpu-count system.

  It seems the ICE ethernet driver has an all or nothing approach to
  allocating MSI-X vectors and could request more MSI-X vectors than it
  finds available, which could lead to the driver failing to initialize and
  start.

  [Fix]

  The patch that fixes this allocates as many MSI-X vectors as it can to 
continue
  functionality by reducing the number of requested MSI-X vectors if it does
  not have enough to do full allocation.

  [Backport]

  In Jammy we do not carry patches for switchdev support in the driver so do not
  allocate the switchdev MSI-X vector for it. Also in Jammy use the older
  way of checking RDMA support by testing the RDMA bit is set as opposed to the 
newer
  ice_is_rdma_ena that the patch uses.

  [Test Plan]

  Install and startup Ice driver with an Intel 800 series NIC and check that we
  do not have the failure:

  Not enough device MSI-X vectors, requested = 260, available = 253

  and check that everything works as expected.

  The backported patch for Jammy has been tested by the original user who
  submited the bug report with their high cpu count system and confirmed no 
errors.

  [Where problems could occur]

  There could be problems with the logic of reducing the MSI-X vector
  usage leading to more errors in the driver, but otherwise minimal
  regression potential as the code is mostly refactoring initial MSI-X
  setup.

  
  --

  System Configuration
  OS: Ubuntu 22.04 LTS
  Kernel: 5.15.0-25-generic
  CPUs: 256
  NIC: Intel E810 NIC with 512 MSIx vectors each function

  Errors
  Not enough device MSI-X vectors, requested = 260, available = 253

  Findings
  (1) the current ice kernel driver (ice_main.c) will pre-allocate all 
required number of msix (even it's not enough for big core CPUs)
  (2) the commit 
https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99
 has improved this logic, and it seems merged into kernel version from v6.1

  So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu
  kernel backport above patch to the current kernel (v5.15) ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012335/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2015972] Re: Dell: Enable speaker mute hotkey LED indicator

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2015972

Title:
  Dell: Enable speaker mute hotkey LED indicator

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in alsa-ucm-conf source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in alsa-ucm-conf source package in Kinetic:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in alsa-ucm-conf source package in Lunar:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Feature Description]
  When users press the speaker mute hotkey and the speaker is muted, 
  the speaker mute LED indicator will light up. 
  When the speaker is not muted, 
  the speaker mute LED indicator will light out.

  [Test Case]
  1. run G16 with target kernel.
  2. press the mute hotkey
  3. check if speaker mute led can be switched.

  [Where problems could occur]
  Low, just register a speaker mute led control for dell-laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2015972/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2016269] Re: conntrack mark is not advertised via netlink

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2016269

Title:
  conntrack mark is not advertised via netlink

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU justification sent to ML:

  [Impact]
  There was a commit 95fcb42e5f20
  ("netfilter: ctnetlink: fix compilation warning after data race fixes in ct 
mark")
  that introduces a regression where the "mark" variable is no longer
  dumped in netlink netfilter conntrack messages, which userspace tools use
  to mark and track connections.

  [Fix]
  Introduce the upstream fix 9f7dd42f0db1
  ("netfilter: ctnetlink: revert to dumping mark regardless of event type")
  that always dumps the 'mark' variable for conntrack entries.
  This fix has also landed in 5.15 upstream stable.

  [Test]
  Run 'conntrack -E' and check the output of connection entries.

  The 'mark' variable should now be present in connection entries after
  the fix.

  before fix:
  > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345 
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
  after fix:
  > tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345 
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1

  [Where problems could occur]
  The fixes are pretty straight forward so regression potential should be
  minimal. 


  
  

  [Impact]

  The last merge of the v5.15 stable (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
  introduced a bug on netlink netfilter conntrack messages.

  The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix 
compilation warning after data race fixes in ct mark"):
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20

  This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter: 
ctnetlink: revert to dumping mark regardless of event type"):
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1

  which has been backported in v5.15.103:
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c

  [Test Case]

  Run 'conntrack -E' and check the output.

  Before the problematic commit:
  > tcp  6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] 
mark=0 use=1

  'mark=' is seen on connrtack event

  after:
  > tcp  6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1

  => 'mark=' is not seen.

  [Regression Potential]

  The patch is quite simple. It has been backported in the official 5.15
  stable. The risk of regression should be contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2018591] Re: Enable Tracing Configs for OSNOISE and TIMERLAT

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-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/2018591

Title:
  Enable Tracing Configs for OSNOISE and TIMERLAT

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  In Progress

Bug description:
  == SRU Justification ==
  These config changes will allow tracing with the OSNOISE and TIMERLAT tracing 
tools.

  These tracers can be enabled at run-time and should not affect
  performance or add any additional overhead.

  == Fix ==
  UBUNTU: [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs

  == Regression Potential ==
  Low.  These config changes will just allow the use of tracing tools.

  == Test Case ==
  Test build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018591/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2019000] Re: Use new annotations model

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2019000

Title:
  Use new annotations model

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  New
Status in linux source package in Focal:
  Triaged
Status in linux-gcp source package in Focal:
  New
Status in linux source package in Jammy:
  Fix Released
Status in linux-gcp source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Confirmed
Status in linux-gcp source package in Kinetic:
  Invalid

Bug description:
  [Impact]

  Starting with lunar we have introduced a new way to manage kernel
  configs, unifying the duplicated information defined in the
  annotations file + config chunks into an annotations-only model.

  [Test case]

  A kernel build can be considered a valid test case, in particular the
  specific command that is used to update the .config's for all the
  supported architectures and flavours:

   $ fakeroot debian/rules updateconfigs

  [Fix]

  Import the required changes in debian/ from lunar (with the required
  adjustments) to support the annotations-only model also in all the
  previous releases.

  [Regression potential]

  We may experience regressions during the updateconfigs step,
  especially with derivatives. Moreover, derivatives that want to
  transition to the new annotations model require to adjust the header
  in the annotations file as following (make sure to define the
  corresponding architectures and flavours):

  # FORMAT: 4
  # ARCH: amd64 arm64 armhf ppc64el s390x
  # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k 
arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae 
ppc64el-generic s390x-generic

  After adjusting the header a special command is provided to transition
  to the new annotations-only model:

   $ fakeroot debian/rules migrateconfigs

  This command should automatically import the old configs into the new
  annotations file.

  A kernel with this change applied can still support the old
  annotations+configs model, the transition to the new model is not
  mandatory.

  Basically without using `fakeroot debian/rules migrateconfigs` the
  updateconfigs step will continue to use the old model and the old
  scripts (that is the safest approach to avoid potential unexpected
  .config changes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-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

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
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:
  In Progress
Status in linux-kvm package in Ubuntu:
  In Progress
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 Committed
Status in linux-kvm source package in Jammy:
  In Progress
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:
  In Progress
Status in linux-kvm source package in Mantic:
  In Progress
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_IMA_ARCH_POLICY

  (The latter is 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.

  [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 2019131] Re: Add PPIN support for Intel EMR cpu

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-aws verification-needed-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/2019131

Title:
  Add  PPIN support for Intel EMR cpu

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification
  [Impact]
  Intel has introduced support for their new Emerald Rapids CPU.
  It was backported to Jammy in #lp2015372 and in #lp2015855.

  The remaining feature needed to fully support EMR is PPIN (the Protected 
Processor Inventory/Identification Number).
  This was recently pushed to upstream in 6.4 in commit 
36168bc061b4368ad19e82b06a6463c95d3bb9a7.
  The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X 
in the cpuids table where cpus that support ppin are listed. The table is then 
used in `ppin_init`.

  In Jammy, this implementation is missing. Both Amd and Intel have their own 
implementation which is doing pretty much the same. Instead of a list of cpus 
supported, a switch case is used instead in their init functions 
(amd_detect_ppin and intel_ppin_init).
  To reduce duplication of code and to help backport smoothly the new addition 
of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918
  “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too.

  Thus commits: 
  - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD 
ppin_init() functions"
  - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids 
to list of CPUs that support PPIN"
  are needed to support PPIN for EMR.

  [Testing]
   Kernel was built on cbd and boot tested on a VM.

  [Regression potential]
   Very low, it is a small refactor that removes duplication and it should not 
affect the functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2019915] Re: Enable audio LEDs on HP laptops

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2019915

Title:
  Enable audio LEDs on HP laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Audio LEDs are not working on some new HP laptops.

  [Fix]
  Use Realtek codec specific method, VREF, to enable audio LEDs.

  [Test]
  With the fix applied, audio LEDs function correctly.

  [Where problems could occur]
  The fix only applies to two hardwares, so other hardwares are
  unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2019915/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2020356] Re: generate linux-lib-rust only on amd64

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-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/2020356

Title:
  generate linux-lib-rust only on amd64

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  Rust is only supported by amd64 at the moment, so there is no reason
  to generate linux-lib-rust packages on the other architectures.

  [Test case]

  Simply build the kernel, generating all the deb packages.

  [Fix]

  Produce linux-lib-rust only on amd64.

  [Regression potential]

  If Rust will be enabled on other architectures we need to remember to
  undo this change, or selectively enable the packaging on the
  architectures that will get the Rust support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020356/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2020062

Title:
  No  HDMI/DP audio output on dock(Nvidia GPU)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  In Progress
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When the machine is docked with an external monitor, it is able to output 
display, but the HDMI/DP audio output option is lost in DGFF Hybrid 
Discrete/Discrete mode(Nvidia GPU).

  [Fix]
  Nvidia provides a patch to fix it
  
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/

  in 6.4-rc3
  dc4f2ccaeddd ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table

  [Test]
  Verified on the target machine.

  {Where problems could occur]
  The patch just adds IDs, and won't lead to any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020062/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-hwe-6.2

-- 
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/2020531

Title:
  support python < 3.9 with annotations

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  At the moment we can't use the annotations scripts in focal, because
  we are using the'|=' update operator for merging dicts, that has been
  introduced with python 3.9.

  Rewrite the code that is using this operator in a more portable way
  and apply this change everywhere, so that annotations will work on any
  backport/derivative kernels.

  [Test case]

  Run `fakeroot debian/rules updateconfigs` in focal (using the new
  annotations model).

  [Fix]

  Try to use the '|=' operator in a try/except block, if it fails
  fallback to a more portable way.

  [Regression potential]

  With this change applied we may experience regressions during the
  updateconfigs phase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2020627] Please test proposed package

2023-07-19 Thread Robie Basak

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2020627

Title:
  upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia
  and Morocco

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
  Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*),
  AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).

  [Fix]

  pnvm along with the ucode firmware from upstream commit 5bc279fb161d
  ("iwlwifi:  update core69 and core72 firmwares for So device") are
  required. While the pnvm and ucode blobs may not be upgraded
  simultaneously in one single commit, those involved in the upgrade
  path are also pulled.

  [Test Case]

  Use `iw` to enumerate supported WiFi 6E band:

  $ iw reg get
  global
  country : DFS-FCC
  ...
  (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN

  [Where problems could occur]

  Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
  linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
  will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
  linux-oem-6.1, linux-5.15.

  [Other Info]

  Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
  referenced in oem-6.5 if planned.

  These commits have been included in linux-firmware/lunar, so only
  Jammy is nominated for fix.

  == original bug report ==

  AX210:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  AX211:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81

  AX411:
  -72 ucode: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
  pnvm: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020627/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2020685

Title:
  System either hang with black screen or rebooted on entering suspend
  on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [SRU Justfication]

  [Impact]

  On AMD Phoenix platforms, system may hang, or reboot while resuming from
  suspend.

  [Fix]

  Two patches in v6.4-rc3 for amdgpu. The first one is pulled for
  dependency.

  [Test Case]

  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  $ checkbox-cli run 
com.canonical.certification::power-management/suspend_30_cycles_with_reboots

  [Where problems could occur]

  The fix is to safely guard register access as it should be. No potential
  problem identified so far.

  [Other Info]

  This should affects v6.1 or above as which AMD Phoenix are supported,
  and has been included in mantic-6.3 through stable-6.3.4 and in oem-6.1
  through stable-6.1.30, leaving lunar-6.2 unfixed only.

  == original bug report ==

  To reproduce:

  ```
  $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto
  # or
  $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30
  ```

  Proposed fixes from AMD:
  * 
https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b
  * 
https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1277 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1277 F pulseaudio
  CasperMD5CheckMismatches: ./preseed/project.cfg
  CasperMD5CheckResult: fail
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-jammy-amd64-20230421-366
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-04-21 (38 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
pc-stella-jammy-amd64-20230421-366
  MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem 
root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29
  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.1.0-1014-oem N/A
   linux-backports-modules-6.1.0-1014-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.13
  Tags:  jammy
  Uname: Linux 6.1.0-1014-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 05/08/2023
  dmi.bios.release: 30.1
  dmi.bios.vendor: HP
  dmi.bios.version: V85 Ver.

[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
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/2021605

Title:
  introduce do_lib_rust=true|false to enable/disable linux-lib-rust
  package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-aws source package in Mantic:
  New

Bug description:
  [Impact]

  Provide a variable do_lib_rust=true|false in the kernel build system
  to selectively enable the Rust packaging (linux-lib-rust) with
  specific kernels and specific architectures.

  Right now Rust should be enabled only in lunar and mantic and only on
  amd64.

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

  Introduce a do_lib_rust=true variable that will be defined only in
  debian.master/rules.d/amd64.mk for now.

  [Regression potential]

  Kernels may need to set this variables if they want to enable the Rust
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-lunar
** Tags added: kernel-spammed-lunar-linux-azure verification-needed-lunar

-- 
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/2021605

Title:
  introduce do_lib_rust=true|false to enable/disable linux-lib-rust
  package

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Lunar:
  Fix Released
Status in linux-aws source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Committed
Status in linux-aws source package in Mantic:
  New

Bug description:
  [Impact]

  Provide a variable do_lib_rust=true|false in the kernel build system
  to selectively enable the Rust packaging (linux-lib-rust) with
  specific kernels and specific architectures.

  Right now Rust should be enabled only in lunar and mantic and only on
  amd64.

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

  Introduce a do_lib_rust=true variable that will be defined only in
  debian.master/rules.d/amd64.mk for now.

  [Regression potential]

  Kernels may need to set this variables if they want to enable the Rust
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949

Title:
  Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
  type-C dongle

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Enabling CL1 (Controller Low Power) states during discovery of existing 
tunnels established by the system firmware can interfere with the operation of 
those tunnels.
  The DisplayPort tunnel establishment timeout of 1.5 seconds can be 
insufficient for some docking stations, leading to blank displays.

  [Fix]
  CL1 states are now not enabled during discovery of existing tunnels. The TMU 
settings also remain unchanged.
  The timeout is increased to 3 seconds to allow more time for the DisplayPort 
connection manager handshake, fixing the issue of displays remaining blank.

  [Test Cases]
  1. plug docking station on the host
  2. bring up the host and get into desktop.
  3. flip docking station's cable.
  4. check if the external monitor works well

  [Where problems could occur]
  Low, If the handshake actually requires even more than 3 seconds in some 
cases, the timeout may still need to be increased further.

  [Misc]
  Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a 
huge,  
  so skip Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2021949/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2021949] Re: Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-lunar-linux-azure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2021949

Title:
  Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to
  type-C dongle

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.0 source package in Mantic:
  Invalid
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Enabling CL1 (Controller Low Power) states during discovery of existing 
tunnels established by the system firmware can interfere with the operation of 
those tunnels.
  The DisplayPort tunnel establishment timeout of 1.5 seconds can be 
insufficient for some docking stations, leading to blank displays.

  [Fix]
  CL1 states are now not enabled during discovery of existing tunnels. The TMU 
settings also remain unchanged.
  The timeout is increased to 3 seconds to allow more time for the DisplayPort 
connection manager handshake, fixing the issue of displays remaining blank.

  [Test Cases]
  1. plug docking station on the host
  2. bring up the host and get into desktop.
  3. flip docking station's cable.
  4. check if the external monitor works well

  [Where problems could occur]
  Low, If the handshake actually requires even more than 3 seconds in some 
cases, the timeout may still need to be increased further.

  [Misc]
  Jammy needs more patches to enable the thunderbolt CLx and the SRU will be a 
huge,  
  so skip Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2021949/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2022940] Re: Azure: Fix perf regression: remove rx_cqes, tx_cqes counters for MANA

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

** Tags added: kernel-spammed-lunar-linux-azure verification-needed-lunar

--
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/2022940

Title:
Azure: Fix perf regression: remove rx_cqes, tx_cqes counters for MANA

Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Lunar:
Fix Committed

Bug description:
SRU Justification

[Impact]

net: mana: Fix perf regression: remove rx_cqes, tx_cqes counters

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=1919b39fc6eabb9a6f9a51706ff6d03865f5df29

It resolves a big perf regression.

For example, a workload is iperf with 128 threads, and with RPS
enabled. We saw perf regression of 25% with the previous patch
adding the counters. And this patch eliminates the regression.

Also, remove the tx_cqes counter for the same reason. We have
warnings & other counters for errors on that path, and don't need
to count every normal cqe processing.

[Test Plan]

MSFT tested

[Regression potential]

Counters are disappearing that may be in use by user space programs.

[Other Info]

SF: #00361807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2022940/+subscriptions

[Kernel-packages] [Bug 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023004

Title:
  Fix Disable thunderbolt clx make edp-monitor garbage while moving the
  touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [impact]
  The default sync pulse length for fast wake AUX transactions was changed from 
18 to 10, which was causing issues with some eDP panels.

  [fix]
  Revert the sync pulse length for fast wake AUX transactions back to the 
hardware default of 18 (10 precharge + 8 preamble).

  [test cases]
  1. configure with thunderbolt.clx=0.
  2. check edp's behavior and it should work well and there's no garbage.

  [where the issue could happen]
  low, By reverting this setting back to the default, this commit restores 
stability for configurations using fast wake AUX transactions, especially those 
involving eDP panels that were incompatible with the shorter sync pulse length. 
The longer, hardware-default sync pulse length is compatible with more use 
cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023004/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023193] Please test proposed package

2023-07-19 Thread Robie Basak

Hello Chris, or anyone else affected,

Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2023193

Title:
  Add firmware files for HP G10 series laptops

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Won't Fix
Status in linux-firmware source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The firmware files are released by Cirrus codec for particular HP series 
laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023193/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023071] Re: [Azure] Fix VM crash/hang issues due to fast VF add/remove events

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-lunar-linux-azure verification-needed-lunar

-- 
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/2023071

Title:
  [Azure] Fix VM crash/hang issues due to fast VF add/remove events

Status in linux-azure package in Ubuntu:
  New
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]

  A Linux guest on Hyper-V/Azure can occasionally crash during early Linux 
kernel boot due to a strange host behavior:
  1. The host assigns a VF to the guest;
  2. The host immediately unassigns the VF from the guest; //Dexuan: due to 
some race conditions bug in Linux vPCI driver, Linux can crash.
  3. The host assigns the VF to the guest again.
  I'm asking the Hyper-V team to investigate the host behavior, but I'm not 
sure when they'll get that fixed.

  Starting late 2022 (around Nov 2022), Linux guests on Azure started to
  crash more frequently due to a host side update at that time: a new
  host/hypervisor feature of handling "correctable memory errors" can
  cause a lot of successive VF remove/add events, so the race conditions
  bug in Linux vPCI driver can surface much more easily. The Hyper-V
  team is implementing a batching mechanism so that the guest will get
  much less VF remove/add events (ETA: June 2023), but meanwhile we
  should also get the Linux race condition bugs fixed so that Linux
  guests won't crash even if it receives the successive VF remove/add
  events.

  [Test Plan]

  MSFT tested

  [Regression potential]

  Guests may continue to crash.

  [Other Info]

  SF: #00349076

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2023071/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023004] Re: Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-lunar-linux-azure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023004

Title:
  Fix Disable thunderbolt clx make edp-monitor garbage while moving the
  touchpad

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [impact]
  The default sync pulse length for fast wake AUX transactions was changed from 
18 to 10, which was causing issues with some eDP panels.

  [fix]
  Revert the sync pulse length for fast wake AUX transactions back to the 
hardware default of 18 (10 precharge + 8 preamble).

  [test cases]
  1. configure with thunderbolt.clx=0.
  2. check edp's behavior and it should work well and there's no garbage.

  [where the issue could happen]
  low, By reverting this setting back to the default, this commit restores 
stability for configurations using fast wake AUX transactions, especially those 
involving eDP panels that were incompatible with the shorter sync pulse length. 
The longer, hardware-default sync pulse length is compatible with more use 
cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023004/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023193] Please test proposed package

2023-07-19 Thread Robie Basak

Hello Chris, or anyone else affected,

Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2023193

Title:
  Add firmware files for HP G10 series laptops

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Kinetic:
  Won't Fix
Status in linux-firmware source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The firmware files are released by Cirrus codec for particular HP series 
laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023193/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-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/2023539

Title:
  Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2

  [Fix]
  Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

  These 2 patches are already in Unstable and OEM-6.1 already got them
  via stable updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023539/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023539] Re: Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-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/2023539

Title:
  Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  No sound output or sound output is too low on ThinkPad P1 Gen 6 and Z16 Gen 2

  [Fix]
  Add quirk for ThinkPad P1 Gen 6 and Z16 Gen 2.

  [Test]
  Tested with alsa audio, audio works fine.

  [Where problems could occur]
  Risk low due to specific hardware.

  These 2 patches are already in Unstable and OEM-6.1 already got them
  via stable updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023539/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023220

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-lunar-linux-azure

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023220

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-hwe-6.2

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023220

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-26.26~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-hwe-6.2

-- 
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/2023577

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  Incomplete
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:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

This bug is awaiting verification that the linux-aws/5.15.0-1041.46
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-aws

-- 
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/2023577

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  Incomplete
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:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

This bug is awaiting verification that the linux-azure/6.2.0-1009.9
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-lunar' to 'verification-done-lunar'. If the
problem still exists, change the tag 'verification-needed-lunar' to
'verification-failed-lunar'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-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/2023577

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  Incomplete
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:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2023594] Re: Case [Azure] Fix VM crash/hang issues due to fast VF add/remove events