date:20220919

You have been subscribed to a public bug:

[Bug Description]

ADL-P platform from IOTG will have hang issue. when blacklist i915, the system 
will back to well.
but with official 5.19 kernel which support ADL-P (IOTG), we don't find this 
issue.

Canonical please check what addition patches has been included your i915
driver that cause system hang.

[HW/SW Information]
Target Kernel: 5.19
Target Release: 22.10

Alder Lake -P from Intel IOTG
[Business Justification]
Function enabling

** Affects: intel
 Importance: Critical
 Status: New

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


** Tags: adl-p intel-kernel-22.10 iotg
-- 
[ADL-P-IOTG graphics cause Ubuntu 22.10 hang
https://bugs.launchpad.net/bugs/1990212
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1988488] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl
  [vmwgfx]] *ERROR* Failed to open channel.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)

** No longer affects: linux-hwe-5.15 (Ubuntu)

** No longer affects: linux-hwe-5.15 (Ubuntu Focal)

** No longer affects: linux-oem-5.17 (Ubuntu Focal)

** No longer affects: linux (Ubuntu Focal)

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

Title:
  Fix AMDGPU: No video output and system hangs with two monitor (dGPU:
  W6400)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There's possibility that system will hang and no video output of two external 
monitor with dGPU W6400

  Monitor 1: ASUS ProArt PA238Q (FHD)
  Monitor 2: Dell P2415Q (4K)

  [Fix]
  Introduce the dmi quirk in amdgpu,
  and add dmi quirks to bypass the affected machine.

  [Test Case]
  Two ways to verify

  Method 1:
  1. Cold boot with ASUS
  2. Attach Dell monitor. ASUS is primary.
  3. Switch display mode to single ASUS
  4. Switch disaply mode back to Joing Displays. ASUS is primary

  Method 2:
  1. Cold boot with two monitors. ASUS is primary
  2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds
  3. Plug it back to DUT

  [Where problems could occur]
  Low, add a dmi quirk to bypass the target machine.

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


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

[Kernel-packages] [Bug 1988488] Re: Screen freeze at the moment of login on VirtualBox

2022-09-19 Thread Daniel van Vugt

Thanks. The only relevant problem I can see there is in the kernel
graphics driver:

[drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open channel.

** Summary changed:

- Screen freeze at the moment of login
+ Screen freeze at the moment of login on VirtualBox

** Summary changed:

- Screen freeze at the moment of login on VirtualBox
+ Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl 
[vmwgfx]] *ERROR* Failed to open channel.

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

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

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

Title:
  Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl
  [vmwgfx]] *ERROR* Failed to open channel.

Status in linux package in Ubuntu:
  New

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)

** Also affects: linux-hwe-5.15 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: linux-hwe-5.15 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-5.17 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux-hwe-5.15 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux-hwe-5.15 (Ubuntu Focal)
 Assignee: (unassigned) => koba (kobako)

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

Title:
  Fix AMDGPU: No video output and system hangs with two monitor (dGPU:
  W6400)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There's possibility that system will hang and no video output of two external 
monitor with dGPU W6400

  Monitor 1: ASUS ProArt PA238Q (FHD)
  Monitor 2: Dell P2415Q (4K)

  [Fix]
  Introduce the dmi quirk in amdgpu,
  and add dmi quirks to bypass the affected machine.

  [Test Case]
  Two ways to verify

  Method 1:
  1. Cold boot with ASUS
  2. Attach Dell monitor. ASUS is primary.
  3. Switch display mode to single ASUS
  4. Switch disaply mode back to Joing Displays. ASUS is primary

  Method 2:
  1. Cold boot with two monitors. ASUS is primary
  2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds
  3. Plug it back to DUT

  [Where problems could occur]
  Low, add a dmi quirk to bypass the target machine.

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


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

[Kernel-packages] [Bug 1988488] [NEW] Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl [vmwgfx]] ERROR Failed to open channel.

You have been subscribed to a public bug:

The problem started to appear 2 weeks ago after one of my daily updates.
It also happens after I re-install the system from a freshly downloaded
ISO file. The system freezes at the moment, it starts the gnome display
manager.

I file the bug-report after a partial upgrade just before I will reboot
the system. If needed I can reboot in recovery mode, since the gnome
display manager is not started in that case.

I tried the continue button without effect and also "apt upgrade" and
"apt dist-upgrade" do have the same effect

I run the VM from the Host-OpenZFS file system, so I can restore to
before the update. Recently I use a Virtualbox snapshot to restore the
system to before the update/upgrade.

If you need log files, let me know.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: systemd 251.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  1 19:42:04 2022
InstallationDate: Installed on 2022-05-28 (96 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug kinetic virtualbox vmwgfx wayland-session
-- 
Screen freeze at the moment of login on VirtualBox: [drm:vmw_msg_ioctl 
[vmwgfx]] *ERROR* Failed to open channel.
https://bugs.launchpad.net/bugs/1988488
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1988461] Re: intel_pmc_core not load on Raptor Lake

2022-09-19 Thread You-Sheng Yang

@timo, ok, I will add RPL-P as well in the SRU patches.

** Also affects: linux-oem-5.17 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.17 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

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

** Changed in: linux (Ubuntu Kinetic)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Kinetic)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  intel_pmc_core not load on Raptor Lake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Summary]
  intel_pmc_core not load on Raptor Lake

  [Reproduce Steps]
  1. Boot into Ubuntu desktop
  2. Check if /sys/kernel/debug/pmc_core folder exist

  [Results]
  Expected: folder /sys/kernel/debug/pmc_core folder been created
  Actual: /sys/kernel/debug/pmc_core not exist

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


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

[Kernel-packages] [Bug 1990170] Re: HDMI refresh rate at 4k 144hz cant be set

2022-09-19 Thread Daniel van Vugt

Thanks for the bug report.

This appears to be either a hardware problem or a bug in the Nvidia
driver. I think most likely it's due to insufficient HDMI cable
bandwidth. Please ensure you are using an HDMI 2.1 certified cable
capable of at least 40 Gbit/s. An HDMI 2.0 cable will not be good
enough.


** Summary changed:

- refresh rate at 4k 144hz cant be set
+ HDMI refresh rate at 4k 144hz cant be set

** Summary changed:

- HDMI refresh rate at 4k 144hz cant be set
+ HDMI refresh rate at 4K 144Hz can't be set

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

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

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

Title:
  HDMI refresh rate at 4K 144Hz can't be set

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

Bug description:
  in the setting,when i set a refresh rate>60Hz, there will be a black
  screen for about half a minute and the refresh rate is automatically
  reset to 60Hz.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-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..0d.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  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 19 23:41:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GA102 [GeForce RTX 3080 Ti] 
[1458:4081]
  InstallationDate: Installed on 2022-08-22 (27 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=UUID=00c387f2-1035-4d26-a66d-d9bcc66f1b7b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F36e
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36e:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1990170] [NEW] HDMI refresh rate at 4K 144Hz can't be set

You have been subscribed to a public bug:

in the setting,when i set a refresh rate>60Hz, there will be a black
screen for about half a minute and the refresh rate is automatically
reset to 60Hz.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-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..0d.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  515.65.01  Wed Jul 20 14:00:58 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 19 23:41:05 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GA102 [GeForce RTX 3080 Ti] [10de:2208] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GA102 [GeForce RTX 3080 Ti] 
[1458:4081]
InstallationDate: Installed on 2022-08-22 (27 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=UUID=00c387f2-1035-4d26-a66d-d9bcc66f1b7b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/12/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F36e
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF36e:bd05/12/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: nvidia-graphics-drivers-515 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy resolution ubuntu
-- 
HDMI refresh rate at 4K 144Hz can't be set
https://bugs.launchpad.net/bugs/1990170
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.

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

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

@Luke
Thanks for the link! I don't need to prepare for the SRU \o/
We're using the test from tools/testing/selftests/ for ubuntu_kernel_selftests, 
so once the patchset was applied we will get the updated test case.

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Triaged

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  Tests passed:  28
  Tests failed:  12
  Tests xfailed:   0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990124/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-package

[Kernel-packages] [Bug 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

2022-09-19 Thread Trent Lloyd

It would be great if you can do the following:
(1) Upload a copy of /etc/netplan

(2) Find out where it's stuck. Preferably generate and attach a kernel
crashdump (https://ubuntu.com/server/docs/kernel-crash-dump) or perhaps
the hung_task_panic=1 kernel option will cause it to print out where
it's stuck if you can capture the full console history?

(3) Test the v5.19.5 Mainline build to see if that works as there have
been a lot of ice driver fixes after 5.15 and would be good to know if
this one is already fixed or not

Details: https://wiki.ubuntu.com/Kernel/MainlineBuilds
Download: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/

Download and install these two files should suffice:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/linux-image-unsigned-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/linux-modules-5.19.5-051905-generic_5.19.5-051905.202208291036_amd64.deb

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

Title:
  Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.

  The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" 
network cards.
  When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) 
the network card is working without issues.

  When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) 
the system will only boot when the NIC has not been configured using netplan.
  After configuring (and therefore enabling) the NIC in netplan, the system 
will hang at "Wait for network to be configured".

  After waiting for some time other error messages also are being shown:
  "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 
5.15.0-46-generic"
  Same for task systemd-network and systemd-udevd.

  The NIC is using "ice" kernel driver:
  root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet
  [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - 
version 0.8.1-k

  I suspect there have been changes performed in that particular driver
  between 5.4 and 5.15 release.

  If additional information is required I am happy to provide.

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


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

[Kernel-packages] [Bug 1976473] Re: [Dell G15 5515] Unable to change screen brightness in ubuntu desktop

2022-09-19 Thread Silvano junior

I have the same issue. Using Ubuntu 22.04 and also other linux distros.
This guy form Nvidia says that is a a bug ... 
https://lore.kernel.org/all/v_ODhOndx3g1l-BhfKGCB6_nLY83LTc5vz1YDrVEVVF5CmgKUs1x9bmROyWXhmYkeQRVVnvfBnyrFyHaEKqtoZE5P7lKJJ1j_vE0J1Piq2Y=@protonmail.com/T/

There is a patch/workarround. But wasnt make upstream.

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

Title:
  [Dell G15 5515] Unable to change screen brightness in ubuntu desktop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Dell G15 5515 Ryzen edition. It has Nvidia 3050 graphics.

  In /sys/class/backlight directory, there are two directories
  amdgpu_bl0 and nvidia_wmi_ec_backlight.

  When I change the screen brightness via slider then it changes the
  brightness value of nvidia_wmi_ec_backlight but it doesn't work. When
  I manually changed the value of amdgpu_bl0 brightness file then my
  screen brightness changed.

  My BIOS is updated to the latest version and I have NVIDIA Driver with 
version 510.73.05.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  yorozuya   2677 F pulseaudio
   /dev/snd/controlC0:  yorozuya   2677 F pulseaudio
   /dev/snd/controlC1:  yorozuya   2677 F pulseaudio
   /dev/snd/controlC3:  yorozuya   2677 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Dell G15 5515
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=1eb57d4b-9978-4341-be1f-5e7197194361 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2022
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.asset.tag: not specified
  dmi.board.name: 0TGD6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.6.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/14/2022:br5.3:svnDellInc.:pnDellG155515:pvr1.6.0:rvnDellInc.:rn0TGD6F:rvrA04:cvnDellInc.:ct10:cvr1.6.0:sku0A6E:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5515
  dmi.product.sku: 0A6E
  dmi.product.version: 1.6.0
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1988461] Re: intel_pmc_core not load on Raptor Lake

** Tags added: originate-from-1989421

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

Title:
  intel_pmc_core not load on Raptor Lake

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Summary]
  intel_pmc_core not load on Raptor Lake

  [Reproduce Steps]
  1. Boot into Ubuntu desktop
  2. Check if /sys/kernel/debug/pmc_core folder exist

  [Results]
  Expected: folder /sys/kernel/debug/pmc_core folder been created
  Actual: /sys/kernel/debug/pmc_core not exist

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


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

[Kernel-packages] [Bug 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

2022-09-19 Thread Michael Reed

** Tags added: verification-done-focal

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

Title:
  [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  fNIC driver controls print messages based on the flag fnic_log_level. 
shost_printk is not controlled via this flag. This issue is resolved by using 
some of the print macros that have been defined in fnic. This has negligible 
impact.
  The resid was being set irrespective of whether we saw an underflow or not. 
It needs to be set only when we see an underflow. The impact here is negligible.
  When we don't receive link events, we could go into a loop before sending fw 
reset. The patch for the issue resolves this, and we break out of the loop.
  Prior to checking the remote port, fnic driver must check if the io_req is 
valid. If not, there could be a crash. The patch resolves this issue.

  [Fix]
  The following patches need to be pulled from upstream to update the fnic 
driver to 1.6.0.53:

  https://marc.info/?l=linux-scsi&m=160591061813369&w=2
  https://marc.info/?l=linux-scsi&m=160592183315837&w=2
  https://marc.info/?l=linux-scsi&m=160592283315997&w=2
  https://marc.info/?l=linux-scsi&m=160592363016122&w=2
  https://marc.info/?l=linux-scsi&m=160592616516616&w=2

  Here's a description of each issue:

  1. https://marc.info/?l=linux-scsi&m=160591061813369&w=2

  FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_fip_handler_timer with this print so that it can
  be controlled.

  2. https://marc.info/?l=linux-scsi&m=160592183315837&w=2

  When fnic is in TRANS ETH state, and when there are no link events, we
  must not loop before sending fw reset.

  3. https://marc.info/?l=linux-scsi&m=160592283315997&w=2

  FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace
  shost_printk in fnic_handle_link with this print so that it can be
  controlled.

  4. https://marc.info/?l=linux-scsi&m=160592363016122&w=2

  Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is
  set.

  5. https://marc.info/?l=linux-scsi&m=160592616516616&w=2

  Check for a valid io_req before we check other data.

  [Test Plan]

  Runnings IOs with multiple link flaps would be a good test case to
  validate all the patches above. It is suggested to run these IOs with
  a data integrity check. We do this as a standard practice.

  [Where problems could occur]

  The print messages are innocuous. It is not expected to run into any issues.
  Problems could occur with storage arrays that have a non-standard response.
  If the sanity test fails, there could be issues in the scsi midlayer or fnic 
driver.

  All the patches present low regression risk.

  [Other Info]
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/fnic_cisco_ver3

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


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

[Kernel-packages] [Bug 1990090] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed on Bionic 4.15

Comment from lukenow:
@PHLin The test case should definitely be updated for this, we want that config

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
  on Bionic 4.15

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Issue found with Bionic 4.15.0-194.205

  Test failed with:

   Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: 
'4.15.0-194.205 (Ubuntu 4.15.0-194.205-generic 4.15.18)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) ... FAIL
   
   ==
   FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest)
   Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754)
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 2976, in 
test_520_config_random_trust_cpu
   self.assertKernelConfig('RANDOM_TRUST_CPU', expected)   
 File "./test-kernel-security.py", line 233, in assertKernelConfig
   self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 224, in assertKernelConfigUnset
   '%s option was expected to be unset in the kernel config' % name)
   AssertionError: RANDOM_TRUST_CPU option was expected to be unset in the 
kernel config
   
   --
   Ran 1 test in 0.003s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1990090/+subscriptions


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

2022-09-19 Thread Badr

I have the same problem, disabling the fTPM in BIOS solved the
suspending problem.Running kernel 5.15.0-47.

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1990203] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  NMI watchdog: Watchdog detected hard LOCKUP on cpu 14

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the error message as in the title is output, the computer stops.

  After rebooting, the bug was reported through the "apport-bug linux"
  command.

  It happens about once a day, and I googled it, but couldn't find a
  suitable solution.

  Also I attach a separate log as per the linux (Ubuntu) bug reporting
  guidelines.

  Additionally, I'm sorry for not being fluent in English.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-47-generic 5.15.0-47.51
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 20 08:54:25 2022
  InstallationDate: Installed on 2022-08-09 (41 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=45ce853f-14df-460a-a7f6-eb55f3d215e6 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-47-generic N/A
   linux-backports-modules-5.15.0-47-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd04/20/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1990203] [NEW] NMI watchdog: Watchdog detected hard LOCKUP on cpu 14

2022-09-19 Thread KimEoJin

Public bug reported:

After the error message as in the title is output, the computer stops.

After rebooting, the bug was reported through the "apport-bug linux"
command.

It happens about once a day, and I googled it, but couldn't find a
suitable solution.

Also I attach a separate log as per the linux (Ubuntu) bug reporting
guidelines.

Additionally, I'm sorry for not being fluent in English.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-47-generic 5.15.0-47.51
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Sep 20 08:54:25 2022
InstallationDate: Installed on 2022-08-09 (41 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=45ce853f-14df-460a-a7f6-eb55f3d215e6 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-47-generic N/A
 linux-backports-modules-5.15.0-47-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.50
dmi.board.name: AB350 Gaming K4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd04/20/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug jammy

** Attachment added: "version.log and lspci-vnvn.log"
   https://bugs.launchpad.net/bugs/1990203/+attachment/5617231/+files/logs.zip

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

Title:
  NMI watchdog: Watchdog detected hard LOCKUP on cpu 14

Status in linux package in Ubuntu:
  New

Bug description:
  After the error message as in the title is output, the computer stops.

  After rebooting, the bug was reported through the "apport-bug linux"
  command.

  It happens about once a day, and I googled it, but couldn't find a
  suitable solution.

  Also I attach a separate log as per the linux (Ubuntu) bug reporting
  guidelines.

  Additionally, I'm sorry for not being fluent in English.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-47-generic 5.15.0-47.51
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Sep 20 08:54:25 2022
  InstallationDate: Installed on 2022-08-09 (41 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0

[Kernel-packages] [Bug 1990190] Re: Focal update: v5.4.211 upstream stable release

2022-09-19 Thread Kamal Mostafa

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.211 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.211 upstream stable release
-from git://git.kernel.org/
+ Makefile: link with -z noexecstack --no-warn-rwx-segments
+ x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
+ scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover"
+ ALSA: bcd2000: Fix a UAF bug on the error path of probing
+ igc: Remove _I_PHY_ID checking
+ wifi: mac80211_hwsim: fix race condition in pending packet
+ wifi: mac80211_hwsim: add back erroneously removed cast
+ wifi: mac80211_hwsim: use 32-bit skb cookie
+ add barriers to buffer_uptodate and set_buffer_uptodate
+ HID: wacom: Only report rotation for art pen
+ HID: wacom: Don't register pad_input for touch switch
+ KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case
+ KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case
+ KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0
+ KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value
+ KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks
+ KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP
+ mm/mremap: hold the rmap lock in write mode when moving page table entries.
+ ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model
+ ALSA: hda/cirrus - support for iMac 12,1 model
+ ALSA: hda/realtek: Add quirk for another Asus K42JZ model
+ tty: vt: initialize unicode screen buffer
+ vfs: Check the truncate maximum size in inode_newsize_ok()
+ fs: Add missing umask strip in vfs_tmpfile
+ thermal: sysfs: Fix cooling_device_stats_setup() error code path
+ fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters
+ usbnet: Fix linkwatch use-after-free on disconnect
+ ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh()
+ parisc: Fix device names in /proc/iomem
+ parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode
+ drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error
+ drm/nouveau: fix another off-by-one in nvbios_addr
+ drm/amdgpu: Check BO's requested pinning domains against its preferred_domains
+ iio: light: isl29028: Fix the warning in isl29028_remove()
+ fuse: limit nsec
+ serial: mvebu-uart: uart2 error bits clearing
+ md-raid10: fix KASAN warning
+ ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr()
+ PCI: Add defines for normal and subtractive PCI bridges
+ powerpc/fsl-pci: Fix Class Code of PCIe Root Port
+ powerpc/ptdump: Fix display of RW pages on FSL_BOOK3E
+ powerpc/powernv: Avoid crashing if rng is NULL
+ MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK
+ coresight: Clear the connection field properly
+ USB: HCD: Fix URB giveback issue in tasklet function
+ ARM: dts: uniphier: Fix USB interrupts for PXs2 SoC
+ arm64: dts: uniphier: Fix USB interrupts for PXs3 SoC
+ netfilter: nf_tables: fix null deref due to zeroed list head
+ epoll: autoremove wakers even more aggressively
+ x86: Handle idle=nomwait cmdline properly for x86_idle
+ arm64: Do not forget syscall when starting a new thread.
+ arm64: fix oops in concurrently setting insn_emulation sysctls
+ ext2: Add more validity checks for inode counts
+ genirq: Don't return error on missing optional irq_request_resources()
+ wait: Fix __wait_event_hrtimeout for RT/DL tasks
+ ARM: dts: imx6ul: add missing properties for sram
+ ARM: dts: imx6ul: change operating-points to uint32-matrix
+ ARM: dts: imx6ul: fix csi node compatible
+ ARM: dts: imx6ul: fix lcdif node compatible
+ ARM: dts: imx6ul: fix qspi node compatible
+ spi: synquacer: Add missing clk_disable_unprepare()
+ ARM: OMAP2+: display: Fix refcount leak bug
+ ACPI: EC: Remove duplicate ThinkPa

[Kernel-packages] [Bug 1990190] [NEW] Focal update: v5.4.211 upstream stable release

2022-09-19 Thread Kamal Mostafa

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.4.211 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Focal update: v5.4.211 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 v5.4.211 upstream stable release
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

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

** Changed in: apparmor (Ubuntu)
   Status: New => Confirmed

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

Title:
  unconfined profile denies userns_create for chromium based processes

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

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


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

[Kernel-packages] [Bug 1990178] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
Seemingly random (ACPI-related?) blocked tasks in the kernel causing a
variety of symptoms

Status in linux package in Ubuntu:
Confirmed

Bug description:
I'm running Ubuntu MATE 22.04.1 LTS on a ASUS Vivobook S14 (model
number M3402QA) laptop.

When I boot Ubuntu on my laptop, there is a high probability (I guess
somewhere between 80-90%) that the system "won't work properly." And
by that I mean the following symptoms:

- The boot process is slow. It takes quite a while (tens of seconds) until
the GUI starts and the login screen is visible, and after logging in, it takes
a similar amount of time until the desktop appears and can be used.
- Several features are not available. I cannot connect to a WiFi network
because NetworkManager is not running (properly). I cannot check the state of
charge of my laptop battery (presumably because UPower is hanging). I cannot
control the brightness of the screen or of the keyboard backlight using the
shortcuts on the built-in keyboard. Closing or opening the lid is not detected,
and will not suspend the computer.
- After four minutes, several messages appear in dmesg reporting blocked
tasks in the kernel. The backtraces for most affected tasks refers to functions
with "acpi" in their name, which is why I suspect this problem is related to
ACPI.
- I cannot reboot or power off the machine without using SysRq combinations
(presumably because the blocked tasks cannot be killed properly).

Interestingly, this does not happen all of the time. If I keep
restarting the machine (via SysRq), it might eventually boot up
quickly and all the things mentioned above will work fine. I wasn't
able to figure out the cause of these problems.

I'm attaching the output of `dmesg` from both a boot which exhibits
the aforementioned problems, and from a boot which works fine. Note
that the data collected by apport is from a properly working boot
(otherwise I would not be able to connect to the network to submit the
report). If you need more information, just let me know.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-47-generic 5.15.0-47.51
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: user 7584 F pulseaudio
/dev/snd/controlC0: user 7584 F pulseaudio
/dev/snd/controlC2: user 7584 F pulseaudio
CasperMD5CheckResult: pass
Date: Mon Sep 19 18:03:11 2022
InstallationDate: Installed on 2022-09-16 (3 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop M3402QA_M3402QA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic
root=UUID=fc8b9b71-f753-445d-b816-7129224c7dbb ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-47-generic N/A
linux-backports-modules-5.15.0-47-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: M3402QA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M3402QA
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.:bvrM3402QA.300:bd02/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopM3402QA_M3402QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3402QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: VivoBook_ASUSLaptop M3402QA_M3402QA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1990184] [NEW] Azure: Enable vPCI multi-MSI interrupts

2022-09-19 Thread Tim Gardner

Public bug reported:

SRU Justification

[Impact]

This is a 2nd attempt with this patch set. The first attempt [1] caused
a regression.

The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie
that supports multiple MSI interrupts (Note: MSI-X has been working
fine). Recently Jeffrey Hugo  made 4 patches to
the vPCI driver so multiple-MSI can work now. Please consider picking up
the 4 patches into the linux-azure kernels for Ubuntu LTS 18.04, 20.04
and 22.04:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08e61e861a0e47e5e1a3fb78406afd6b0cea6b6d

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=455880dfe292a2bdd3b4ad6a107299fce610e64b

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b8ecc5bfbd4e77de1b2fd5c1dd3c655f1f

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a2bad844a67b1c7740bda63e87453baf63c3a7f7

[1] https://bugs.launchpad.net/bugs/1981577

[Test Plan]

Microsoft tested: " I tested the kernel and it worked as expected, i.e.
we still have the multi-MSI capability and I no longer see the soft
lockup issue with fio + NVMe + the L64s_v2 VM size."

[Where things could go wrong]

vPCI devices may no get interrupts

[Other Info]

SF: #00339521

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: Fix Released

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

** Changed in: linux-azure (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Also affects: linux-azure (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux-azure (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: linux-azure (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux-azure (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-azure (Ubuntu Jammy)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Summary changed:

- Azure: Enable multi-vPCI MSI interrupts
+ Azure: Enable vPCI multi-MSI interrupts

** Description changed:

  SRU Justification
  
  [Impact]
  
- This is a 2nd attept with this patch set. The first attempt [1] caused a
- regression.
+ This is a 2nd attempt with this patch set. The first attempt [1] caused
+ a regression.
  
  The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie
  that supports multiple MSI interrupts (Note: MSI-X has been working
  fine). Recently Jeffrey Hugo  made 4 patches to
  the vPCI driver so multiple-MSI can work now. Please consider picking up
  the 4 patches into the linux-azure kernels for Ubuntu LTS 18.04, 20.04
  and 22.04:
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08e61e861a0e47e5e1a3fb78406afd6b0cea6b6d
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=455880dfe292a2bdd3b4ad6a107299fce610e64b
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b8ecc5bfbd4e77de1b2fd5c1dd3c655f1f
  
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a2bad844a67b1c7740bda63e87453baf63c3a7f7
  
  [1] https://bugs.launchpad.net/bugs/1981577
  
  [Test Plan]
  
  Microsoft tested: " I tested the kernel and it worked as expected, i.e.
  we still have the multi-MSI capability and I no longer see the soft
  lockup issue with fio + NVMe + the L64s_v2 VM size."
  
  [Where things could go wrong]
  
  vPCI devices may no get interrupts
  
  [Other Info]
  
  SF: #00339521

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

Title:
  Azure: Enable vPCI multi-MSI interrupts

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

Bug description:
  SRU Justification

  [Impact]

  This is a 2nd attempt with this patch set. The first attempt [1]
  caused a regression.

  The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie
  that supports multiple MSI interrupts (Note: MSI-X has been working
  fine). Recently Jeffrey Hugo  made 4 patches
  to the vPCI driver so multiple-MSI can work now. Please consider
  picking up the 4 patches into the linux-azure kernels for Ubuntu LTS
  18.04, 20.04 and 22.04:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08e61e861a0e47e5e1a3fb78406afd6b0cea6b6d

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=455880dfe292a2bdd3b4ad6a107299fce610e64b

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linu

[Kernel-packages] [Bug 1990156] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1990156

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.

  The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" 
network cards.
  When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) 
the network card is working without issues.

  When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) 
the system will only boot when the NIC has not been configured using netplan.
  After configuring (and therefore enabling) the NIC in netplan, the system 
will hang at "Wait for network to be configured".

  After waiting for some time other error messages also are being shown:
  "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 
5.15.0-46-generic"
  Same for task systemd-network and systemd-udevd.

  The NIC is using "ice" kernel driver:
  root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet
  [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - 
version 0.8.1-k

  I suspect there have been changes performed in that particular driver
  between 5.4 and 5.15 release.

  If additional information is required I am happy to provide.

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


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

[Kernel-packages] [Bug 1990156] Re: Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

2022-09-19 Thread Brian Murray

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.

  The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" 
network cards.
  When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) 
the network card is working without issues.

  When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) 
the system will only boot when the NIC has not been configured using netplan.
  After configuring (and therefore enabling) the NIC in netplan, the system 
will hang at "Wait for network to be configured".

  After waiting for some time other error messages also are being shown:
  "INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 
5.15.0-46-generic"
  Same for task systemd-network and systemd-udevd.

  The NIC is using "ice" kernel driver:
  root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet
  [5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - 
version 0.8.1-k

  I suspect there have been changes performed in that particular driver
  between 5.4 and 5.15 release.

  If additional information is required I am happy to provide.

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


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

[Kernel-packages] [Bug 1990178] Re: Seemingly random (ACPI-related?) blocked tasks in the kernel causing a variety of symptoms

2022-09-19 Thread Confusedlaptopguy

** Attachment added: "dmesg from a boot which works fine"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990178/+attachment/5617177/+files/dmesg-5.15.0-47-generic-working.txt

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

Title:
  Seemingly random (ACPI-related?) blocked tasks in the kernel causing a
  variety of symptoms

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 22.04.1 LTS on a ASUS Vivobook S14 (model
  number M3402QA) laptop.

  When I boot Ubuntu on my laptop, there is a high probability (I guess
  somewhere between 80-90%) that the system "won't work properly." And
  by that I mean the following symptoms:

  - The boot process is slow. It takes quite a while (tens of seconds) until 
the GUI starts and the login screen is visible, and after logging in, it takes 
a similar amount of time until the desktop appears and can be used.
  - Several features are not available. I cannot connect to a WiFi network 
because NetworkManager is not running (properly). I cannot check the state of 
charge of my laptop battery (presumably because UPower is hanging). I cannot 
control the brightness of the screen or of the keyboard backlight using the 
shortcuts on the built-in keyboard. Closing or opening the lid is not detected, 
and will not suspend the computer.
  - After four minutes, several messages appear in dmesg reporting blocked 
tasks in the kernel. The backtraces for most affected tasks refers to functions 
with "acpi" in their name, which is why I suspect this problem is related to 
ACPI.
  - I cannot reboot or power off the machine without using SysRq combinations 
(presumably because the blocked tasks cannot be killed properly).

  Interestingly, this does not happen all of the time. If I keep
  restarting the machine (via SysRq), it might eventually boot up
  quickly and all the things mentioned above will work fine. I wasn't
  able to figure out the cause of these problems.

  I'm attaching the output of `dmesg` from both a boot which exhibits
  the aforementioned problems, and from a boot which works fine. Note
  that the data collected by apport is from a properly working boot
  (otherwise I would not be able to connect to the network to submit the
  report). If you need more information, just let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-47-generic 5.15.0-47.51
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   7584 F pulseaudio
   /dev/snd/controlC0:  user   7584 F pulseaudio
   /dev/snd/controlC2:  user   7584 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 19 18:03:11 2022
  InstallationDate: Installed on 2022-09-16 (3 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop M3402QA_M3402QA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=fc8b9b71-f753-445d-b816-7129224c7dbb ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-47-generic N/A
   linux-backports-modules-5.15.0-47-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: M3402QA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M3402QA
  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.:bvrM3402QA.300:bd02/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopM3402QA_M3402QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3402QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: VivoBook_ASUSLaptop M3402QA_M3402QA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1990178] Re: Seemingly random (ACPI-related?) blocked tasks in the kernel causing a variety of symptoms

2022-09-19 Thread Confusedlaptopguy

** Attachment added: "dmesg from a boot exhibiting the problems mentioned in 
the bug report"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990178/+attachment/5617176/+files/dmesg-5.15.0-47-generic-task-blocked.txt

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

Title:
  Seemingly random (ACPI-related?) blocked tasks in the kernel causing a
  variety of symptoms

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 22.04.1 LTS on a ASUS Vivobook S14 (model
  number M3402QA) laptop.

  When I boot Ubuntu on my laptop, there is a high probability (I guess
  somewhere between 80-90%) that the system "won't work properly." And
  by that I mean the following symptoms:

  - The boot process is slow. It takes quite a while (tens of seconds) until 
the GUI starts and the login screen is visible, and after logging in, it takes 
a similar amount of time until the desktop appears and can be used.
  - Several features are not available. I cannot connect to a WiFi network 
because NetworkManager is not running (properly). I cannot check the state of 
charge of my laptop battery (presumably because UPower is hanging). I cannot 
control the brightness of the screen or of the keyboard backlight using the 
shortcuts on the built-in keyboard. Closing or opening the lid is not detected, 
and will not suspend the computer.
  - After four minutes, several messages appear in dmesg reporting blocked 
tasks in the kernel. The backtraces for most affected tasks refers to functions 
with "acpi" in their name, which is why I suspect this problem is related to 
ACPI.
  - I cannot reboot or power off the machine without using SysRq combinations 
(presumably because the blocked tasks cannot be killed properly).

  Interestingly, this does not happen all of the time. If I keep
  restarting the machine (via SysRq), it might eventually boot up
  quickly and all the things mentioned above will work fine. I wasn't
  able to figure out the cause of these problems.

  I'm attaching the output of `dmesg` from both a boot which exhibits
  the aforementioned problems, and from a boot which works fine. Note
  that the data collected by apport is from a properly working boot
  (otherwise I would not be able to connect to the network to submit the
  report). If you need more information, just let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-47-generic 5.15.0-47.51
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   7584 F pulseaudio
   /dev/snd/controlC0:  user   7584 F pulseaudio
   /dev/snd/controlC2:  user   7584 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Mon Sep 19 18:03:11 2022
  InstallationDate: Installed on 2022-09-16 (3 days ago)
  InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop M3402QA_M3402QA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=fc8b9b71-f753-445d-b816-7129224c7dbb ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-47-generic N/A
   linux-backports-modules-5.15.0-47-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: M3402QA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M3402QA
  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.:bvrM3402QA.300:bd02/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopM3402QA_M3402QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3402QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Vivobook
  dmi.product.name: VivoBook_ASUSLaptop M3402QA_M3402QA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1990156] [NEW] Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC

You have been subscribed to a public bug:

Hi!

We are using Ubuntu 20.04.5 LTS on 20 Dell PowerEdge R650 systems.

The systems are equipped with "Intel(R) Ethernet 25G 2P E810-XXV Adapter" 
network cards.
When using the 5.4 kernel (specifically we tested kernel 5.4.0-125-generic) the 
network card is working without issues.

When using the HWE kernel (specifically we tested kernel 5.15.0-47-generic) the 
system will only boot when the NIC has not been configured using netplan.
After configuring (and therefore enabling) the NIC in netplan, the system will 
hang at "Wait for network to be configured".

After waiting for some time other error messages also are being shown:
"INFO: task kworker xyz blocked for more than 120 seconds. Not tainted 
5.15.0-46-generic"
Same for task systemd-network and systemd-udevd.

The NIC is using "ice" kernel driver:
root@metal020:/home/philippalbrecht# dmesg | grep -i ethernet
[5.085905] ice: Intel(R) Ethernet Connection E800 Series Linux Driver - 
version 0.8.1-k

I suspect there have been changes performed in that particular driver
between 5.4 and 5.15 release.

If additional information is required I am happy to provide.

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


** Tags: bot-comment
-- 
Ubuntu 20.04 HWE Kernel refuses to boot Intel E810-XXV NIC
https://bugs.launchpad.net/bugs/1990156
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1990178] [NEW] Seemingly random (ACPI-related?) blocked tasks in the kernel causing a variety of symptoms

2022-09-19 Thread Confusedlaptopguy

Public bug reported:

I'm running Ubuntu MATE 22.04.1 LTS on a ASUS Vivobook S14 (model number
M3402QA) laptop.

When I boot Ubuntu on my laptop, there is a high probability (I guess
somewhere between 80-90%) that the system "won't work properly." And by
that I mean the following symptoms:

- The boot process is slow. It takes quite a while (tens of seconds) until the 
GUI starts and the login screen is visible, and after logging in, it takes a 
similar amount of time until the desktop appears and can be used.
- Several features are not available. I cannot connect to a WiFi network 
because NetworkManager is not running (properly). I cannot check the state of 
charge of my laptop battery (presumably because UPower is hanging). I cannot 
control the brightness of the screen or of the keyboard backlight using the 
shortcuts on the built-in keyboard. Closing or opening the lid is not detected, 
and will not suspend the computer.
- After four minutes, several messages appear in dmesg reporting blocked tasks 
in the kernel. The backtraces for most affected tasks refers to functions with 
"acpi" in their name, which is why I suspect this problem is related to ACPI.
- I cannot reboot or power off the machine without using SysRq combinations 
(presumably because the blocked tasks cannot be killed properly).

Interestingly, this does not happen all of the time. If I keep
restarting the machine (via SysRq), it might eventually boot up quickly
and all the things mentioned above will work fine. I wasn't able to
figure out the cause of these problems.

I'm attaching the output of `dmesg` from both a boot which exhibits the
aforementioned problems, and from a boot which works fine. Note that the
data collected by apport is from a properly working boot (otherwise I
would not be able to connect to the network to submit the report). If
you need more information, just let me know.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-47-generic 5.15.0-47.51
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  user   7584 F pulseaudio
 /dev/snd/controlC0:  user   7584 F pulseaudio
 /dev/snd/controlC2:  user   7584 F pulseaudio
CasperMD5CheckResult: pass
Date: Mon Sep 19 18:03:11 2022
InstallationDate: Installed on 2022-09-16 (3 days ago)
InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop M3402QA_M3402QA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=fc8b9b71-f753-445d-b816-7129224c7dbb ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-47-generic N/A
 linux-backports-modules-5.15.0-47-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: M3402QA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M3402QA
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.:bvrM3402QA.300:bd02/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopM3402QA_M3402QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3402QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: VivoBook_ASUSLaptop M3402QA_M3402QA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug 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/1990178

Title:
  Seemingly random (ACPI-related?) blocked tasks in the kernel causing a
  variety of symptoms

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu MATE 22.04.1 LTS on a ASUS Vivobook S14 (model
  number M3402QA) laptop.

  When I boot Ubuntu on my laptop, there is a high probability (I guess
  somewhere between 80-90%) that the system "won't work properly." And
  by that I mean the following symptoms:

  - The boot process is slow. It takes quite a while (tens of seconds) until 
the GUI starts and the login screen is visible, and after logging in, it takes 
a similar amount of time until the desktop appears and can be used.
  - Several features are not available. I cannot connect to a WiFi network 
because NetworkMan

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

2022-09-19 Thread Luke Nowakowski-Krijger

Ah @Po-Hsu Lin didnt see you already found the commit :) FYI the
patchset I sent here https://lists.ubuntu.com/archives/kernel-
team/2022-September/133062.html also includes a new test case for the
initial regression that that patch fixes. Don't know if you need to
update anything with testing for that or not.

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Triaged

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  Tests passed:  28
  Tests failed:  12
  Tests xfailed:   0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ke

[Kernel-packages] [Bug 1990167] [NEW] cma alloc failure in large 5.15 arm instances

2022-09-19 Thread Kyler Hornor

Public bug reported:

When launching large arm64 instances on the focal or jammy ami, cma
allocation errors appear in the dmesg out:

[0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096
pages, ret: -12

As far as I can tell, this does not impact instance launch in a
meaningful way, but I am unsure of the other implications of this. I was
able to confirm that these messages are only present in 5.15, as they do
not show up in the bionic image, and rolling back focal to linux-aws 5.4
avoids them as well.

This was present in at least 2 instance types and only appears to pop up
in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does)

This could be as simple as just disabling CMA in the linux-aws pkg, as
it appears this is already the case in linux-azure(LP:  #1949770).

Attaching dmesg out to the report.


# Replication
+ Launch a large arm64 instance (c6gn.16xlarge)
+ Observe the messages in kern.log / dmesg

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

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1990167/+attachment/5617126/+files/dmesg.txt

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

Title:
  cma alloc failure in large 5.15 arm instances

Status in linux-aws package in Ubuntu:
  New

Bug description:
  When launching large arm64 instances on the focal or jammy ami, cma
  allocation errors appear in the dmesg out:

  [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096
  pages, ret: -12

  As far as I can tell, this does not impact instance launch in a
  meaningful way, but I am unsure of the other implications of this. I
  was able to confirm that these messages are only present in 5.15, as
  they do not show up in the bionic image, and rolling back focal to
  linux-aws 5.4 avoids them as well.

  This was present in at least 2 instance types and only appears to pop
  up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge)
  does)

  This could be as simple as just disabling CMA in the linux-aws pkg, as
  it appears this is already the case in linux-azure(LP:  #1949770).

  Attaching dmesg out to the report.

  
  # Replication
  + Launch a large arm64 instance (c6gn.16xlarge)
  + Observe the messages in kern.log / dmesg

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


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

[Kernel-packages] [Bug 1990161] [NEW] Fix RPL-S support on powercap/intel_rapl

Public bug reported:

[Impact]
proc_thermal driver is not loaded

[Fix]
Add RPL-S id on device id table of powercap/intel_rapl.

[Test Case]
1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal

[Where problems could occur]
Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

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

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

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.17 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Assignee: koba (kobako)
 Status: In Progress

** Affects: linux-oem-5.17 (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu Kinetic)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1988813 originate-from-1989533 somerville

** Also affects: linux-oem-5.17 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.17 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => koba (kobako)

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

** Tags added: oem-priority originate-from-1988813 somerville

** Tags added: originate-from-1989533

** Also affects: linux-oem-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

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

Title:
  Fix RPL-S support on powercap/intel_rapl

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  New
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  [Impact]
  proc_thermal driver is not loaded

  [Fix]
  Add RPL-S id on device id table of powercap/intel_rapl.

  [Test Case]
  1. sudo checkbox-cli run com.canonical.certification::miscellanea/proc_thermal

  [Where problems could occur]
  Low, only add RPL-S id on powercap/intel_rap but may lack of RPL-S features.

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


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

[Kernel-packages] [Bug 1983656] RE: Confirm new features of Ubuntu 22.10

2022-09-19 Thread Paul Lai

Hi Jeff:
Intel Linux Virtualization is preparing to validate Intel Virtualized features 
in Ubuntu 22.10.
What kernel and qemu versions can we expect?

From: Lai, Paul C
Sent: Friday, September 16, 2022 7:48 AM
To: Fang, Xun ; Pathi, Pragyansri 
; Sethi, Puneet 
Subject: RE: Confirm new features of Ubuntu 22.10

Pragyan:
What are the expected kernel and qemu versions in Ubuntu 22.10?

From: Fang, Xun mailto:xun.f...@intel.com>>
Sent: Friday, September 16, 2022 7:01 AM
To: Lai, Paul C mailto:paul.c@intel.com>>
Subject: Confirm new features of Ubuntu 22.10

Paul,

I am drafting a test plan for ubuntu 22.10 and would like to confirm
with you about the new features: AMX and SGX, right? Thanks!

Thanks
Xun

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

Title:
  SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to 
resolve this error in some cases. It is already included in the test kernel 
v5.15.0-41 and did not resolve the issue. 

  These Virtual Machines do work with the Mainline v5.19 build on the
  host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES
  related commits that are not currently backported to v5.15 or any
  upstream stable kernel:

  6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings 
before configuring [v5.18]
  be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling 
[v5.19]

  Additionally during testing if we link down an interface and/or try to use 
netplan apply to start DHCP instead of manual configuration we triggered the 
following memory corruption bug:
  efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF 
driver [v5.19]

  It appears that this ice/iavf driver is quite immature as many significant 
SR-IOV related fixes have landed in each of the recent kernel releases and we 
may need to consider pro-actively backporting more fixes.

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

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

[Kernel-packages] [Bug 1990153] Re: package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-46-generic package post-install

2022-09-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-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1990153

Title:
  package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed
  to install/upgrade: installed linux-modules-
  nvidia-470-5.15.0-46-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules package in Ubuntu:
  New

Bug description:
  Multiple times this issue has occured

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Sep 19 12:09:55 2022
  ErrorMessage: installed linux-modules-nvidia-470-5.15.0-46-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-02-03 (228 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: linux-restricted-modules
  Title: package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed 
to install/upgrade: installed linux-modules-nvidia-470-5.15.0-46-generic 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

2022-09-19 Thread Luke Nowakowski-Krijger

We might be missing this patch "ip: fix triggering of 'icmp redirect'"
that I sent to the kt-ML as one of the backport request patchsets from
the Author of that commit that is breaking things. I think applying that
will make the behavior consistent and get those tests to pass.

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Triaged

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  Tests passed:  28
  Tests failed:  12
  Tests xfailed:   0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990124/+subscript

[Kernel-packages] [Bug 1990153] [NEW] package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed to install/upgrade: installed linux-modules-nvidia-470-5.15.0-46-generic package post-insta

2022-09-19 Thread Rishwan Reddy

Public bug reported:

Multiple times this issue has occured

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Sep 19 12:09:55 2022
ErrorMessage: installed linux-modules-nvidia-470-5.15.0-46-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-02-03 (228 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
SourcePackage: linux-restricted-modules
Title: package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed 
to install/upgrade: installed linux-modules-nvidia-470-5.15.0-46-generic 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed
  to install/upgrade: installed linux-modules-
  nvidia-470-5.15.0-46-generic package post-installation script
  subprocess returned error exit status 1

Status in linux-restricted-modules package in Ubuntu:
  New

Bug description:
  Multiple times this issue has occured

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Sep 19 12:09:55 2022
  ErrorMessage: installed linux-modules-nvidia-470-5.15.0-46-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-02-03 (228 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: linux-restricted-modules
  Title: package linux-modules-nvidia-470-5.15.0-46-generic 5.15.0-46.49 failed 
to install/upgrade: installed linux-modules-nvidia-470-5.15.0-46-generic 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1972898] Re: Kernel Bug: 22.04, EXT4, samba (smbd) on MDADM raid6: Copying large volume of files.

2022-09-19 Thread MH

Hi list,

I get this bug, too. It is not related to samba or Fedora, but the 
kernel, I assume. Something seems to have changed in the ext4 driver in 
the kernel starting with roughly 5.13.

I copy large amount of files and hardlinks onto my filesystem and 
suddenly it stops working with the kernel bug (see below). The 
filesystem seems still to be mounted, lsof shows that one process is 
working on it, but as soon as I try to access the FS my terminal session 
hangs.

I'm using opensuse leap 15.4 (5.14.21-150400.24.21-default #1 SMP 
PREEMPT_DYNAMIC Wed Sep 7 06:51:18 UTC 2022 (974d0aa) x86_64 x86_64 
x86_64 GNU/Linux). The problem was not apparent in opensuse leap 15.3 
with a kernel 15.3. The bug seems to be introduced with kernel 5.13 as 
others reported similar problems with this or newer kernel versions.


Here some more information about my system:
Ext4 FS (LVM on a hardware HP Raid (HP ProLiant ML350 Gen9)):
> #  dumpe2fs -h /dev/mapper/backup-backup 
> dumpe2fs 1.46.4 (18-Aug-2021)
> Filesystem volume name:   
> Last mounted on:  /backup
> Filesystem UUID:  1337b52d-11ee-4914-af6c-26085295f39a
> Filesystem magic number:  0xEF53
> Filesystem revision #:1 (dynamic)
> Filesystem features:  has_journal ext_attr resize_inode dir_index 
> filetype needs_recovery extent 64bit flex_bg sparse_super large_file 
> huge_file uninit_bg dir_nlink extra_isize
> Filesystem flags: signed_directory_hash 
> Default mount options:user_xattr acl
> Filesystem state: clean
> Errors behavior:  Continue
> Filesystem OS type:   Linux
> Inode count:  610463744
> Block count:  4883703808
> Reserved block count: 4883703
> Free blocks:  1201445461
> Free inodes:  455325946
> First block:  0
> Block size:   4096
> Fragment size:4096
> Group descriptor size:64
> Blocks per group: 32768
> Fragments per group:  32768
> Inodes per group: 4096
> Inode blocks per group:   256
> RAID stride:  64
> RAID stripe width:448
> Flex block group size:16
> Filesystem created:   Fri Apr  7 12:47:45 2017
> Last mount time:  Wed Sep 14 15:32:42 2022
> Last write time:  Wed Sep 14 15:32:42 2022
> Mount count:  37
> Maximum mount count:  -1
> Last checked: Wed Jan 27 12:56:16 2021
> Check interval:   0 ()
> Lifetime writes:  88 TB
> Reserved blocks uid:  0 (user root)
> Reserved blocks gid:  0 (group root)
> First inode:  11
> Inode size:   256
> Required extra isize: 28
> Desired extra isize:  28
> Journal inode:8
> Default directory hash:   half_md4
> Directory Hash Seed:  998d3208-bcb9-4a93-8f50-9e686d7ffe52
> Journal backup:   inode blocks
> Journal features: journal_incompat_revoke journal_64bit
> Total journal size:   128M
> Total journal blocks: 32768
> Max transaction length:   32768
> Fast commit length:   0
> Journal sequence: 0x00152ac7
> Journal start:3046


Kernel messages from /var/log/messages:
> 2022-09-17T00:25:23.574959+02:00 HOSTNAME kernel: [205391.151933][ T2173] 
> [ cut here ]
> 2022-09-17T00:25:23.574991+02:00 HOSTNAME kernel: [205391.151939][ T2173] 
> kernel BUG at ../fs/ext4/xattr.c:2071!
> 2022-09-17T00:25:23.574995+02:00 HOSTNAME kernel: [205391.151951][ T2173] 
> invalid opcode:  [#1] PREEMPT SMP PTI
> 2022-09-17T00:25:23.574997+02:00 HOSTNAME kernel: [205391.151963][ T2173] 
> CPU: 6 PID: 2173 Comm: rsync Tainted: GN 5.14.21-150400.2
> 4.18-default #1 SLE15-SP4 695ab7a8fc20f5ddb345280570966cd1eb06d469
> 2022-09-17T00:25:23.575006+02:00 HOSTNAME kernel: [205391.151976][ T2173] 
> Hardware name: HP ProLiant ML350 Gen9/ProLiant ML350 Gen9, BIOS P92 10/21/2019
> 2022-09-17T00:25:23.575010+02:00 HOSTNAME kernel: [205391.151982][ T2173] 
> RIP: 0010:ext4_xattr_block_set+0xd9b/0xea0 [ext4]
> 2022-09-17T00:25:23.575013+02:00 HOSTNAME kernel: [205391.152088][ T2173] 
> Code: 7c 24 30 41 b9 01 00 00 00 41 b8 01 00 00 00 4c 89 e9 31 d2 e8 f6 d6 fc 
> ff e9 ed fc ff ff e8 fc 2a 11 fb 0f 0b e9 d9 f6 ff ff <0f> 0b 48 8b 7c 24 08 
> e8 d9 9f a6 fa e9 d1 fe ff ff c7 44 24 4c f4
> 2022-09-17T00:25:23.575015+02:00 HOSTNAME kernel: [205391.152099][ T2173] 
> RSP: 0018:9705406dba20 EFLAGS: 00010212
> 2022-09-17T00:25:23.575018+02:00 HOSTNAME kernel: [205391.152107][ T2173] 
> RAX:  RBX: 0fdc0200 RCX: 
> 2022-09-17T00:25:23.575020+02:00 HOSTNAME kernel: [205391.152113][ T2173] 
> RDX: fff7e006 RSI: c0cf112c RDI: 2c02c000d410
> 2022-09-17T00:25:23.575023+02:00 HOSTNAME kernel: [205391.152119][ T2173] 
> RBP: 9705406dbbd8 R08:  R09: 
> 2022-09-17T00:25:23.575025+02:00 HOSTNAME kernel: [205391.152125][ T2173] 
> R10:  R11: 8ae4ffdc4800 R12: ff

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

2022-09-19 Thread Stefan Bader

Focal will also be affected since it contains 5.4.207 which has the
break commit and needs the related fix for it from 5.4.213.

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

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
   Status: New => Triaged

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
   Status: Incomplete => Triaged

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Triaged
Status in linux source package in Jammy:
  Triaged

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redir

[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

2022-09-19 Thread Aravind Valloor Mana

Jeff, Thanks for the quickly providing the test kernel. It passed the
sanity test.

Any ETA of the release build with integration of these patches for our
QA team to verify.

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

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [IMPACT/Justification]

  
  [FIX]

  Please integrate the latest set of bug fix patches accepted in
  mkp/scsi 5.20/scsi-staging

  b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
  71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
  b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into 
lpfc_sli_prep_abort_xri()
  ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved 
configuration
  ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
  2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF 
WQE
  0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in 
queuecommand after VMID
  35251b4d79db scsi: lpfc: Set PU field when providing D_ID in 
XMIT_ELS_RSP64_CX iocb
  f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with 
malformed user input
  4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in 
lpfc_nvme_cancel_iocb()
  1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
  2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for 
nvme_admin_async_event cmd completion
  ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for 
aborted NVMe cmds
  336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT 
topology
  b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is 
aborted
  6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after 
starget_to_rport()
  e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path 
refactoring
  24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path 
refactoring
  44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in 
lpfc_ct_reject_event()
  a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
  348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol 
independent
  ed913cf4a533 scsi: lpfc: Commonize VMID code location
  fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
  a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for 
NVMe I/O
  e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
  de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
  5099478e436f scsi: lpfc: Change VMID registration to be based on fabric 
parameters
  dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if 
lpfc_err_lost_link()
  4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in 
rscn_recovery_check()
  596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
  ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
  b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
  ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
  84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
  775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
  cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
  c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
  92bd903da12b scsi: lpfc: Fix additional reference counting in 
lpfc_bsg_rport_els()
  db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
  646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
  3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in 
lpfc_sli_prep_wqe()
  a346f28ad231 scsi: lpfc: Remove unneeded variable
  66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
  4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
  fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
  f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
  ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
  d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
  1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post 
RSCN completion
  6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in 
Fabric topology
  6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
  c364c453d30a scsi: lpfc: Revise FDMI reporting of supported port speed for 
trunk groups
  d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
  5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
  39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic 
disable
  d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assi

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

This bug was fixed in the package lttng-modules -
2.10.8-1ubuntu2~18.04.4

---
lttng-modules (2.10.8-1ubuntu2~18.04.4) bionic; urgency=medium

  * Backport upstream fix to handle removal of random tracepoints in the
kernel (LP: #1986921):
- d/p/compat-5.4/0001-support-kernels-without-random-tracepoints.patch

 -- Andrea Righi   Thu, 08 Sep 2022 08:14:15
+

** Changed in: lttng-modules (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in lttng-modules source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in lttng-modules source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions


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

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

2022-09-19 Thread Łukasz Zemczak

Okay, as this is needed for the new batch of kernels, is verified and no
errors related to the package seem to be present in errors.ubuntu.com,
let me release this earlier.

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in lttng-modules source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in lttng-modules source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions


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

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

Test kernel with commit eb55dc09b works as expected:
https://people.canonical.com/~phlin/kernel/lp-1990124-icmp-redirect/

This test is not failing anymore.

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  Tests passed:  28
  Tests failed:  12
  Tests xfailed:   0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990124/+subscriptions


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

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

** Changed in: makedumpfile (Ubuntu)
Status: New => Confirmed

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
Confirmed

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:

__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

[Kernel-packages] [Bug 1967842] Re: Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode - Wireless-AC 9260 not working

2022-09-19 Thread Stefan Schubert

I already opened a new bug for kernel 5.15.0-47-generic

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989941

The previous Kernel 5.15.0-46-generic doesn't show this issue on my
machine.

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

Title:
  Ubuntu 22.04 Beta: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode -
  Wireless-AC 9260 not working

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  Hi

  with the current Ubuntu 22.04 beta my WIFI device Intel Corporation
  Wireless-AC 9260 is not shown/working.

  If I copy/use the firmware from an current Ubuntu 20.04 system it is
  working again.

  Md5sum working from Ubuntu 20.04 linux-firmware:
  0668e93b8766bf95d6adffdb33ec7bdb  
/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode

  Md5sum not working from Ubuntu 22.04 linux-firmware:
  dcf642fd7412614e19d1d54f57147539  
/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode

  Outputs from the Ubuntu 22.04 system:

  Device Dell 7530:
  # lspci -Q -v -s 6e:00.0
  6e:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
   Subsystem: Intel Corporation Device 4010
   Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 16
   Memory at a000 (64-bit, non-prefetchable) [size=16K]
   Capabilities: [c8] Power Management version 3
   Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
   Capabilities: [40] Express Endpoint, MSI 00
   Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
   Capabilities: [100] Advanced Error Reporting
   Capabilities: [14c] Latency Tolerance Reporting
   Capabilities: [154] L1 PM Substates
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

  # dpkg -l | grep linux-firmware
  ii  linux-firmware 20220329.git681281e4-0ubuntu1

  # uname -a
  Linux hostname 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:54:05 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux

  # dmesg with broken firmware:
  [   13.690647] kernel: iwlwifi :6e:00.0: enabling device ( -> 0002)
  [   13.707780] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 0
  [   13.707784] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 1
  [   13.707786] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 2
  [   13.707787] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 3
  [   13.707788] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 4
  [   13.707790] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 6
  [   13.707791] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 8
  [   13.707792] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 9
  [   13.707793] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 10
  [   13.707795] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 11
  [   13.707796] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 15
  [   13.707797] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 16
  [   13.707798] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 18
  [   13.707800] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 19
  [   13.707801] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 20
  [   13.707802] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 21
  [   13.707804] kernel: iwlwifi :6e:00.0: WRT: Overriding region id 28
  [   13.708080] kernel: iwlwifi :6e:00.0: loaded firmware version 
46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
  [   13.954798] kernel: iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 
9260 160MHz, REV=0x324
  [   14.779900] kernel: iwlwifi :6e:00.0: RF_KILL bit toggled to disable 
radio.
  [   14.779904] kernel: iwlwifi :6e:00.0: reporting RF_KILL (radio 
disabled)
  [   15.045652] kernel: iwlwifi :6e:00.0: SecBoot CPU1 Status: 0xa5a5a5a2, 
CPU2 Status: 0xa5a5a5a2
  [   15.045657] kernel: iwlwifi :6e:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).
  [   15.293971] kernel: iwlwifi :6e:00.0: Not valid error log pointer 
0x for Init uCode
  [   15.294270] kernel: iwlwifi :6e:00.0: Hardware error detected. 
Restarting.
  [   15.294271] kernel: iwlwifi :6e:00.0: IML/ROM dump:
  [   15.294272] kernel: iwlwifi :6e:00.0: 0xA5A5 | IML/ROM SYSASSERT
  [   15.294273] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM error/state
  [   15.294420] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | IML/ROM data1
  [   15.294429] kernel: iwlwifi :6e:00.0: Fseq Registers:
  [   15.294563] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE
  [   15.294697] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | 
FSEQ_TOP_INIT_VERSION
  [   15.294831] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | 
FSEQ_CNVIO_INIT_VERSION
  [   15.294965] kernel: iwlwifi :6e:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION
  [   15.295100] kernel: iwlwifi :6e:00.0

[Kernel-packages] [Bug 1987595] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1987595

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Support Intel IPU6 MIPI camera

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  This is a follow-up for bug 1964983 but on different platforms that
  runs linux-oem-5.17 or newer.

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


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

[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera

2022-09-19 Thread You-Sheng Yang

** Also affects: linux-oem-6.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: linux-oem-5.17 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: linux-oem-5.17 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-6.0 (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
   Status: New => Invalid

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

** Tags added: oem-priority originate-from-1987726 somerville

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

Title:
  Support Intel IPU6 MIPI camera

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  This is a follow-up for bug 1964983 but on different platforms that
  runs linux-oem-5.17 or newer.

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


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

[Kernel-packages] [Bug 1990124] Re: icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55

This commit seems to be the cause, test passed by reverting it:

commit 07e4bcbce061bb58f109ed746b770adea5914d80
Author: Nicolas Dichtel 
Date:   Wed Jul 13 13:48:52 2022 +0200

ip: fix dflt addr selection for connected nexthop

BugLink: https://bugs.launchpad.net/bugs/1988351

commit 747c14307214b55dbd8250e1ab44cad8305756f1 upstream.


Now building a test kernel with possible fix: eb55dc09b (" ip: fix triggering 
of 'icmp redirect' ")

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  Tests passed:  28
  Tests failed:  12
  Te

[Kernel-packages] [Bug 1990127] Re: ubuntu_lttng_smoke_test failed with module build on J-gkeop (error: implicit declaration of function ‘kallsyms_lookup_funcptr’)

This issue can be found since J-gkeop 5.15.0-1001

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

Title:
  ubuntu_lttng_smoke_test failed with module build on J-gkeop (error:
  implicit declaration of function ‘kallsyms_lookup_funcptr’)

Status in ubuntu-kernel-tests:
  New
Status in linux-gkeop package in Ubuntu:
  New

Bug description:
  Issue found on J-gkeop 5.15.0-1003.5, and this can be reproduced with
  J-gkeop 5.15.0-1002 as well.

  Build log:
   Running 'cat /var/lib/dkms/lttng-modules/*/build/make.log'
   DKMS make.log for lttng-modules-2.13.1 for kernel 5.15.0-1003-gkeop (x86_64)
   Fri Sep  9 19:35:26 UTC 2022
   make: Entering directory '/usr/src/linux-headers-5.15.0-1003-gkeop'
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-discard.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-overwrite.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-metadata-client.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-mmap-discard.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-mmap-overwrite.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-metadata-mmap-client.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-event-notifier-client.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-counter-client-percpu-32-modular.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-counter-client-percpu-64-modular.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-clock.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lib/msgpack/msgpack.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-events.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-abi.o
   /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:62: File 
./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use 
full kernel source tree to enable it.
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/tests/probes/lttng-test.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lib/ringbuffer/ring_buffer_backend.o
   /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:166: Files 
./fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source 
tree to enable it.
   /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:177: Files 
./fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree 
to enable it.
   /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:237: 
CONFIG_KALLSYMS_ALL is disabled, therefore probe "writeback" is disabled. 
Rebuild your kernel with this configuration option enabled in order to trace 
this subsystem.
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-sched.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-string-utils.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-probes.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-pid.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-procname.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-prio.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-nice.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/tests/clock-plugin/lttng-clock-plugin-test.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vpid.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-tid.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-irq.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-timer.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vtid.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-ppid.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vppid.o
     LD [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/tests/lttng-test.o
     LD [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/tests/lttng-clock-plugin-test.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-cpu-id.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-kmem.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-uid.o
     CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lib/ringbuffer/ring_buffer_frontend.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-euid.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-suid.o
     CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-egid.o

[Kernel-packages] [Bug 1990127] Re: ubuntu_lttng_smoke_test failed with module build on J-gkeop (error: implicit declaration of function ‘kallsyms_lookup_funcptr’)

** Description changed:

  Issue found on J-gkeop 5.15.0-1003.5, and this can be reproduced with
  J-gkeop 5.15.0-1002 as well.
  
  Build log:
-  Running 'cat /var/lib/dkms/lttng-modules/*/build/make.log'
-  DKMS make.log for lttng-modules-2.13.1 for kernel 5.15.0-1003-gkeop (x86_64)
-  Fri Sep  9 19:35:26 UTC 2022
-  make: Entering directory '/usr/src/linux-headers-5.15.0-1003-gkeop'
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-discard.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-overwrite.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-metadata-client.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-mmap-discard.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-client-mmap-overwrite.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-metadata-mmap-client.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-ring-buffer-event-notifier-client.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-counter-client-percpu-32-modular.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-counter-client-percpu-64-modular.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-clock.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lib/msgpack/msgpack.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-events.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-abi.o
-  /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:62: File 
./arch/x86/kvm/lapic.h not found. Probe "kvm" x86-specific is disabled. Use 
full kernel source tree to enable it.
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/tests/probes/lttng-test.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lib/ringbuffer/ring_buffer_backend.o
-  /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:166: Files 
./fs/btrfs/*.h not found. Probe "btrfs" is disabled. Use full kernel source 
tree to enable it.
-  /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:177: Files 
./fs/ext4/*.h not found. Probe "ext4" is disabled. Use full kernel source tree 
to enable it.
-  /var/lib/dkms/lttng-modules/2.13.1/build/src/probes/Kbuild:237: 
CONFIG_KALLSYMS_ALL is disabled, therefore probe "writeback" is disabled. 
Rebuild your kernel with this configuration option enabled in order to trace 
this subsystem.
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-sched.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-string-utils.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-probes.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-pid.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-procname.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-prio.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-nice.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/tests/clock-plugin/lttng-clock-plugin-test.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vpid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-tid.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-irq.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-timer.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vtid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-ppid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vppid.o
-LD [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/tests/lttng-test.o
-LD [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/tests/lttng-clock-plugin-test.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-cpu-id.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-kmem.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-uid.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/lib/ringbuffer/ring_buffer_frontend.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-euid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-suid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-egid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-gid.o
-CC [M]  
/var/lib/dkms/lttng-modules/2.13.1/build/src/probes/lttng-probe-module.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-sgid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-vuid.o
-CC [M]  /var/lib/dkms/lttng-modules/2.13.1/build/src/lttng-context-veuid.o
-CC [M]  
/var/lib/dkms/lttng-mo

[Kernel-packages] [Bug 1990124] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1990124

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Changed in: linux (Ubuntu Jammy)
   Status: New => Incomplete

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

Title:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy
  5.15.0-49.55

  This looks like a potential regression as there is no change to the
  test script.

  Manual test show this issue does not exist on:
* J-5.15.0-47
* J-5.15.0-48

  Test log:
  ###
  Legacy routing
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Legacy routing with VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception   [ OK ]
  TEST: IPv4: mtu exception plus redirect [FAIL]
  TEST: IPv6: mtu exception plus redirect [ OK ]

  ###
  Routing with nexthop objects and VRF
  ###

  TEST: IPv4: redirect exception  [FAIL]
  TEST: IPv6: redirect exception  [ OK ]
  TEST: IPv4: redirect exception plus mtu [FAIL]
  TEST: IPv6: redirect exception plus mtu [ OK ]
  TEST: IPv4: routing reset   [ OK ]
  TEST: IPv6: routing reset   [ OK ]
  TEST: IPv4: mtu exception   [ OK ]
  TEST: IPv6: mtu exception

[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

2022-09-19 Thread Kleber Sacilotto de Souza

Confirming the fix also works with bionic/linux-hwe-5.4 which builds for
all arches:

* amd64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/lttng-modules/20220914_114635_72fb4@/log.gz
* arm64 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/lttng-modules/20220914_114634_72fb4@/log.gz
* armhf - 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/armhf/l/lttng-modules/20220914_114745_97a52@/log.gz
* i386 - 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/lttng-modules/20220914_114744_e64ab@/log.gz
* ppc64el - 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/l/lttng-modules/20220914_114632_72fb4@/log.gz
* s390x - 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/lttng-modules/20220914_114552_72fb4@/log.gz

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

Title:
  lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in lttng-modules source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Won't Fix
Status in lttng-modules source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Won't Fix
Status in lttng-modules source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  Impact: The kernel upstream changed in v5.18 and dropped tracepoints
  for random. This change was backported to 5.15/jammy in upstream
  stable 5.15.44. With that the build of lttng-modules-dkms fails.

  Fix: Backport of an upstream change which checks for the kernel header file 
which got removed in the process. Additionally the DKMS spec file has to do the 
same check to
  be aware of the missing probe module.

  Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and
  -47 or later. Currently -47 and later will fail. With the change both
  should complete.

  Regression Potential: This changes whether lttng-probe-random.ko is
  available or not (if it is available the code is unchanged). User-
  space might be affected if this module is always expected.

  ---

  This is a scripted bug report about ADT failures while running lttng-
  modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused
  by the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions


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

[Kernel-packages] [Bug 1990124] [NEW] icmp_redirect.sh in ubuntu_kernel_selftests failed on Jammy 5.15.0-49.55