date:20230228

** Description changed:

  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.
  
  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue
  
  [Test]
  Verified with the WD22TB + 2 4k DP monitors.
  
  [Where problems could occur]
- Actually, there is no functional changes with default RR sched policy, but it 
accidentialy fixes the blank screen issue.
+ Actually, there is no functional changes with default RR sched policy, but it 
accidentially fixes the blank screen issue.

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

Title:
  The external monitor is blank if plug in the dock cable to power up
  the machine

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

Bug description:
  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.

  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue

  [Test]
  Verified with the WD22TB + 2 4k DP monitors.

  [Where problems could occur]
  Actually, there is no functional changes with default RR sched policy, but it 
accidentially fixes the blank screen issue.

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


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

[Kernel-packages] [Bug 2008860] Re: The external monitor is blank if plug in the dock cable to power up the machine

** Description changed:

  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.
  
  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue
  
  [Test]
  Verified with the WD22TB + 2 4k DP monitors.
  
  [Where problems could occur]
+ Actually, there is no functional changes with default RR sched policy, but it 
accidentialy fixes the blank screen issue.

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

Title:
  The external monitor is blank if plug in the dock cable to power up
  the machine

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

Bug description:
  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.

  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue

  [Test]
  Verified with the WD22TB + 2 4k DP monitors.

  [Where problems could occur]
  Actually, there is no functional changes with default RR sched policy, but it 
accidentially fixes the blank screen issue.

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


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

[Kernel-packages] [Bug 2008860] Re: The external monitor is blank if plug in the dock cable to power up the machine

** Tags added: civet-cat oem-priority originate-from-2000198

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

Title:
  The external monitor is blank if plug in the dock cable to power up
  the machine

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

Bug description:
  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.

  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue

  [Test]
  Verified with the WD22TB + 2 4k DP monitors.

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 2008860] [NEW] The external monitor is blank if plug in the dock cable to power up the machine

Public bug reported:

[Impact]
There are one or more monitors connect to the dock and then plug the dock cable 
to power up the Dell machine, the external monitors keeps blank.

[Fix]
The issue has been fixed in v6.2-rc1 and the first bad commit is
08fb97de03aa drm/sched: Add FIFO sched policy to run queue

[Test]
Verified with the WD22TB + 2 4k DP monitors.

[Where problems could occur]

** Affects: linux-oem-6.1 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.1 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

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

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

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

** Description changed:

  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.
  
  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue
  
  [Test]
- Verified with the WD22TB + 2 DP monitors.
+ Verified with the WD22TB + 2 4k DP monitors.
  
  [Where problems could occur]

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

Title:
  The external monitor is blank if plug in the dock cable to power up
  the machine

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There are one or more monitors connect to the dock and then plug the dock 
cable to power up the Dell machine, the external monitors keeps blank.

  [Fix]
  The issue has been fixed in v6.2-rc1 and the first bad commit is
  08fb97de03aa drm/sched: Add FIFO sched policy to run queue

  [Test]
  Verified with the WD22TB + 2 4k DP monitors.

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

Colin, can you please give this test kernel a try:
https://people.canonical.com/~khfeng/jammy-5.19-fast-wake/

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

Before biseciton, please also give latest mainline kernel a try:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/

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

Title:
  Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just yesterday and the day before made some benchmark tests for a
  comparison between ext4 and zfs. I ran repeated builds of a large
  software package and it always came out to 45s. Now today I ran the
  same test a few times and it was always 60s. I noticed that today an
  update ran and that kernel 5.19.0-32 was installed. So just now I
  booted back to 5.15.0-60-generic:amd64 and ran the test again: back to
  45s.

  I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM
  otherwise there is nothing very special going on. I ran the tests on
  ZFS and ext4, it makes no difference.

  To reproduce, I would think that compiling any decent sized software package 
one on 5.15 and then on 5.19 whould yield the same results.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-07-15 (217 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  wayland-session jammy
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: TRX40 Taichi
  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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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/2007717/+subscriptions


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

[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

Sounds like a kernel bisection is needed:
https://wiki.ubuntu.com/Kernel/KernelBisection

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

Title:
  Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just yesterday and the day before made some benchmark tests for a
  comparison between ext4 and zfs. I ran repeated builds of a large
  software package and it always came out to 45s. Now today I ran the
  same test a few times and it was always 60s. I noticed that today an
  update ran and that kernel 5.19.0-32 was installed. So just now I
  booted back to 5.15.0-60-generic:amd64 and ran the test again: back to
  45s.

  I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM
  otherwise there is nothing very special going on. I ran the tests on
  ZFS and ext4, it makes no difference.

  To reproduce, I would think that compiling any decent sized software package 
one on 5.15 and then on 5.19 whould yield the same results.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-07-15 (217 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  wayland-session jammy
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: TRX40 Taichi
  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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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/2007717/+subscriptions


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

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

This bug was fixed in the package libqmi - 1.32.0-1ubuntu0.22.04.1

---
libqmi (1.32.0-1ubuntu0.22.04.1) jammy; urgency=medium

  * Backport the newer modemmanager stack to the LTS as part of
new hardware enablement including FM350 modems
(lp: #1950282)

 -- Sebastien Bacher   Tue, 22 Nov 2022 13:17:29
+0100

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Jammy:
  Fix Released
Status in libqmi source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  New
Status in modemmanager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

This bug was fixed in the package modemmanager - 1.20.0-1~ubuntu22.04.1

---
modemmanager (1.20.0-1~ubuntu22.04.1) jammy; urgency=medium

  * Backport the newer modemmanager stack to the LTS as part of
new hardware enablement including FM350 modems
(lp: #1950282)

 -- Sebastien Bacher   Tue, 13 Dec 2022 13:38:07
+0100

** Changed in: libqmi (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Jammy:
  Fix Released
Status in libqmi source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  New
Status in modemmanager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

This bug was fixed in the package libmbim - 1.28.0-1~ubuntu20.04.1

---
libmbim (1.28.0-1~ubuntu20.04.1) jammy; urgency=medium

  * Backport the newer modemmanager stack to the LTS as part of
new hardware enablement including FM350 modems
(lp: #1950282)

 -- Sebastien Bacher   Tue, 13 Dec 2022 13:35:17
+0100

** Changed in: libmbim (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: modemmanager (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Jammy:
  Fix Released
Status in libqmi source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  New
Status in modemmanager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 2000802] Re: network

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  network

Status in linux package in Ubuntu:
  Expired

Bug description:
  network-manager not working in mint vera with kernel 5.15.0-56

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

So far the artifact has _not_ returned running:
6.2.0-060200rc2drmintelnext20230228-generic

I'm seeing overall good behavior with this kernel.


I will need more information/assistance on how to apply the quirk. Do I 
download the patch files and execute them, or do I edit the grub file as 
described here:

https://askubuntu.com/questions/1455653/horizontal-colored-lines-
appearing-on-display-ubuntu-22-04

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

lspci dump file

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007516/+attachment/5650605/+files/lspci.txt

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

eDP dump file

** Attachment added: "eDP_PSR_status_dump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007516/+attachment/5650604/+files/eDP_PSR_status_dump.txt

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 1950282] Update Released

2023-02-28 Thread Chris Halse Rogers

The verification of the Stable Release Update for libmbim has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Jammy:
  Fix Committed
Status in libqmi source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  New
Status in modemmanager source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  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.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules

2023-02-28 Thread Chris Halse Rogers

Has lttng-smoke-test been run against the packages from -proposed? It's
not *entirely* clear to me, but that looked to be a part of the test-
case, and the autopkgtests don't (appear?) to run the smoke test?

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

Title:
  Incompatible jbd2 format between kernel and lttng-modules

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in lttng-modules package in Ubuntu:
  Fix Committed
Status in lttng-modules source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in lttng-modules source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Incomplete
Status in lttng-modules source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Incomplete
Status in lttng-modules source package in Kinetic:
  Fix Committed
Status in linux source package in Lunar:
  Incomplete
Status in lttng-modules source package in Lunar:
  Fix Committed

Bug description:
  [SRU Justification]

  Impact:
  Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 
6.1.3.
  This is incompatible with the current changes in the lttng-module for 
bionic-5.4 backports, focal, jammy, and kinetic.

  Focal and bionic updates are needed for the current sru kernel release 
(2023.01.30). Both adt and rt fail during compilation of the module.
  Jammy and kinetic updates are not needed for this cycle because patches from 
upstream stable are not applied yet but it will be needed for the next 
release(s).

  Correct changes are already in lttng-modules:master and in 2.13.8-1
  version.

  Fix(es):
  1. focal and bionic: Picking 4 patches from upstream lttng-modules which 
handle the changed interface as well as add the required code to enable that 
change for other versions as well:
  LTTNG_KERNEL_RANGE(5,4,229, 5,5,0)
  LTTNG_KERNEL_RANGE(5,10,163, 5,11,0)
  LTTNG_KERNEL_RANGE(5,15,87, 5,16,0)
  LTTNG_KERNEL_RANGE(6,0,18, 6,1,0)
  LTTNG_KERNEL_RANGE(6,1,4, 6,2,0)

  2. Jammy and kinetic: backport 2.13.8-1

  Tescase(s) for focal:
  1. lttng-smoke-test fail to compile with the error from below.
  2. adt lttng-module fail to compile with same error

  Regression potential:
  We may notice new failures in ubuntu_lttng_smoke_test once this will compile 
and run. But it was tested locally and results were good, so probablity is very 
very low.

  760 21:14:39 DEBUG| [stdout] In file included from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87,
761 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177,
762 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29:
763 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6:
 error: conflicting types for ‘trace_jbd2_run_stats’
764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto);
765 21:14:39 DEBUG| [stdout] | ^~
766 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
767 21:14:39 DEBUG| [stdout] 43 | 
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
768 21:14:39 DEBUG| [stdout] | ^~~
769 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, 
name, \
771 21:14:39 DEBUG| [stdout] | ^~
772 21:14:39 DEBUG| [stdout] 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1:
 note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
773 21:14:39 DEBUG| [stdout] 104 | 
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
774 21:14:39 DEBUG| [stdout] | ^~
775 21:14:39 DEBUG| [stdout] In file included from 
./include/trace/events/jbd2.h:9,
776 21:14:39 DEBUG| [stdout] from 
/var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18:
777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: 
previous definition of ‘trace_jbd2_run_stats’ was here
778 21:14:39 DEBUG| [stdout] 243 | static inline void 
trace_##name(proto) \
779 21:14:39 DEBUG| [stdout] | ^~
780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: 
in expansion of macro ‘__DECLARE_TRACE’
781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto),

[Kernel-packages] [Bug 2007579] Re: Raptor Lake Thermald ITMT version 2 support

2023-02-28 Thread koba

@Colin, i could help to verify on the target.

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

Title:
  Raptor Lake Thermald ITMT version 2 support

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Bionic:
  Won't Fix
Status in thermald source package in Focal:
  Won't Fix
Status in thermald source package in Jammy:
  In Progress
Status in thermald source package in Kinetic:
  Fix Committed
Status in thermald source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification Kinetic ==

  Raptor Lake system uses ITMT v2 instead of V1 for thermal
  configuration via GDDV.

  This was observed on Dell XPS 9320 system.
  Because thermald can't parse V2 table, it is not getting correct thermal 
threshold temperature and power limits.

  == The Fix ==

  This is fixed in upstream thermald by the patch:
  
https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774
  This fix is part of Thermald 2.5.2 release.

  The fix applies cleanly and this is already in Ubuntu Lunar in
  thermald 2.5.2.  The fix checks for illegal ITMT version and handles
  version 2 as a specific exceptional case.

  == Regression Risks ==

  For systems that do not used ITMT, no change in behaviour will occur.
  Systems with versions > 2 (currently not valid) will not have ITMT
  parsed anymore; this will avoid misinterpreting unsupported ITMT data.
  Finally, version 2 of ITMT will be now parsed differently and
  additional fields will be parsed and these will be ignored as
  intended.

  == Test Plan ==

  Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. 
The thermald log should indicate version 2 is being used with the message: 
  "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 
values that are parsed and ignored.

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

In addition to that, please test the following kernel _without_ any kernel 
parameter:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/amd64/

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2008797] 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/2008797

Title:
  USB mouse doesn't work after resuming from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Basic problem is that the usb mouse connects at the start, but after
  sleep, suddenly stops.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.78.01  Mon Dec 26 
05:58:42 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 28 20:56:40 2023
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] 
[103c:88ec]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Cezanne [103c:88ec]
  InstallationDate: Installed on 2023-02-28 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  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/2p, 1M
   /:  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/2p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
  MachineType: HP Victus by HP Laptop 16-e0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic 
root=UUID=42da8321-31cc-4d70-aeb1-d0e0f86cc2f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2021
  dmi.bios.release: 15.4
  dmi.bios.vendor: AMI
  dmi.bios.version: F.04
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 88EC
  dmi.board.vendor: HP
  dmi.board.version: 80.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 80.22
  dmi.modalias: 
dmi:bvnAMI:bvrF.04:bd06/17/2021:br15.4:efr80.22:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EC:rvr80.22:cvnHP:ct10:cvrChassisVersion:sku494P3PA#ACJ:
  dmi.product.family: 103C_5335M7 HP VICTUS
  dmi.product.name: Victus by HP Laptop 16-e0xxx
  dmi.product.sku: 494P3PA#ACJ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.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.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1998722] Re: kernel update 5.19.0-1013-oracle breaks my system

2023-02-28 Thread Aroun

Seems to be fixed, I could delete linux-modules-5.19.0-1015-lowlatency
linux-image-5.19.0-1015-lowlatency linux-objects-
nvidia-525-5.19.0-1015-oracle linux-image-5.19.0-1015-oracle linux-
signatures-nvidia-5.19.0-1015-oracle while keeping nvidia-driver-525

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

Title:
  kernel update 5.19.0-1013-oracle breaks my system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This update over the weekend caused by stsem to fail to boot
  In recovery mode my networking, and video configuration was broken
  Booting the alternate(backup) kernel image worked fine 

  I was able to recover by removing the new oracle kernel
  sudo apt purge linux-image-5.19.0-1013-oracle

  After rebooting I then ran
  sudo apt autoremove
  to remove the other compoments that where installed with the oracle kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-26-generic 5.19.0-26.27
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  5 10:06:52 2022
  InstallationDate: Installed on 2022-04-05 (243 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Dell Inc. Precision T1700
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=896ec6e0-7230-417f-a041-5588c627727c 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.19.0-26-generic N/A
   linux-backports-modules-5.19.0-26-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (45 days ago)
  dmi.bios.date: 05/30/2019
  dmi.bios.release: 65.28
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A28
  dmi.board.name: 04JGCK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr:sku05A6:
  dmi.product.name: Precision T1700
  dmi.product.sku: 05A6
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group

2023-02-28 Thread ChengEn, Du

The focal-proposed kernel has been tested in linux/5.4.0-144.161.

** Tags removed: verification-needed-focal
** 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/2003053

Title:
  NFS: client permission error after adding user to permissible group

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

Bug description:
  [Impact]
  The NFS client's access cache becomes stale due to the user's group 
membership changing on the server after the user has already logged in on the 
client.
  The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or 
timeout (without delegation).
  Adding a user to a group in the NFS server will not cause any file attributes 
to change.
  The client will encounter permission errors until other file attributes are 
changed or the memory cache is dropped.

  [Fix]

  The access cache shall be cleared once the user logs out and logs back
  in again.

  0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache 
upon login
  029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's 
timestamp in rcu path
  5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning

  [Test Plan]
  1.[client side] testuser is not part of testgroup
testuser@kinetic:~$ ls -ld /mnt/private/
drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied
  2.[server side] add testuser into testgroup, which has access to folder
root@kinetic:~$ usermod -aG testgroup testuser &&
echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush
  3.[client side] create a file again but still fail
testuser@kinetic:~$ mktemp -p /mnt/private/
mktemp: failed to create file via template
‘/mnt/private/tmp.XX’: Permission denied

  [Where problems could occur]
  The fix will apply upstream commits, so the regression can be considered as 
low.

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


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

[Kernel-packages] [Bug 2008797] Re: Mouse problems

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

** Summary changed:

- Mouse problems
+ USB mouse doesn't work after resuming from sleep

** Tags added: suspend-resume

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

Title:
  USB mouse doesn't work after resuming from sleep

Status in linux package in Ubuntu:
  New

Bug description:
  Basic problem is that the usb mouse connects at the start, but after
  sleep, suddenly stops.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.78.01  Mon Dec 26 
05:58:42 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 28 20:56:40 2023
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] 
[103c:88ec]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Cezanne [103c:88ec]
  InstallationDate: Installed on 2023-02-28 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  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/2p, 1M
   /:  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/2p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
  MachineType: HP Victus by HP Laptop 16-e0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic 
root=UUID=42da8321-31cc-4d70-aeb1-d0e0f86cc2f9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2021
  dmi.bios.release: 15.4
  dmi.bios.vendor: AMI
  dmi.bios.version: F.04
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 88EC
  dmi.board.vendor: HP
  dmi.board.version: 80.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 80.22
  dmi.modalias: 
dmi:bvnAMI:bvrF.04:bd06/17/2021:br15.4:efr80.22:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EC:rvr80.22:cvnHP:ct10:cvrChassisVersion:sku494P3PA#ACJ:
  dmi.product.family: 103C_5335M7 HP VICTUS
  dmi.product.name: Victus by HP Laptop 16-e0xxx
  dmi.product.sku: 494P3PA#ACJ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.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.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

2023-02-28 Thread Kai-Chuan Hsieh

reply #8,

Could you dump the eDP PSR status?
# cat /sys/kernel/debug/dri/0/i915_edp_psr_status

Have you tried the driver parameter "options i915
enable_psr2_sel_fetch=0"? Does it work for you?

The patch is created by applying quirk for Dell machine [1], I'd like to check 
if it indeed take effect on your platform, could you dump lspci output by
$ lspci -nnvv

[1] https://patchwork.freedesktop.org/patch/524182/?series=114400=1

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs

Adrian, please open a separate bug from your machine by running:

  ubuntu-bug linux


** Package changed: linux-meta-hwe-5.19 (Ubuntu) => linux-hwe-5.19 (Ubuntu)

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

Title:
  HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen CPUs

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

Bug description:
  After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32
  (from 5.15.0.60) suspend/wake up is broken on my laptop.

  The system refuses to wake up in about 50% of the cases, seemingly
  random. The only "solution" is a forced system power down.

  Reverting back to 5.15.0.60 resolves this issue immediately.

  I suspect some patch was not re-applied to 5.19, since there are many
  postings on Reddit (for instance) about sleep problems with newer AMD
  CPUs, but 5.15 was running beautifully.

  My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU.

  UPDATE:

  See attached log. This may not be a case of the laptop failing to
  resume, but a case of the laptop not suspending properly!

  What happened was the following. When packing in my things,  I closed
  the laptop and put it in my bag. At home I picked it up again, and
  immediately noticed how unusually hot it was. The laptop didn't resume
  properly on opening the lid, but was frozen as before.

  So this might actually be a case of the laptop FAILING TO SUSPEND
  properly, instead of failing to wake up.

  UPDATE:

  I just noticed the battery was down to the low 40% from at least 80%.
  Given the temperature on opening the laption I suspect the CPU has
  been working hard during "sleep time".

  EDIT:

  Changed title after confirmation for earlier Ryzen 5000 CPU.

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


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

[Kernel-packages] [Bug 2008797] [NEW] Mouse problems

You have been subscribed to a public bug:

Basic problem is that the usb mouse connects at the start, but after
sleep, suddenly stops.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.78.01  Mon Dec 26 05:58:42 
UTC 2022
 GCC version:
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 28 20:56:40 2023
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company GA107M [GeForce RTX 3050 Mobile] 
[103c:88ec]
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Cezanne [103c:88ec]
InstallationDate: Installed on 2023-02-28 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
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/2p, 1M
 /:  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/2p, 1M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
MachineType: HP Victus by HP Laptop 16-e0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic 
root=UUID=42da8321-31cc-4d70-aeb1-d0e0f86cc2f9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2021
dmi.bios.release: 15.4
dmi.bios.vendor: AMI
dmi.bios.version: F.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 88EC
dmi.board.vendor: HP
dmi.board.version: 80.22
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 80.22
dmi.modalias: 
dmi:bvnAMI:bvrF.04:bd06/17/2021:br15.4:efr80.22:svnHP:pnVictusbyHPLaptop16-e0xxx:pvr:rvnHP:rn88EC:rvr80.22:cvnHP:ct10:cvrChassisVersion:sku494P3PA#ACJ:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Laptop 16-e0xxx
dmi.product.sku: 494P3PA#ACJ
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.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.4-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug kinetic ubuntu
-- 
Mouse problems
https://bugs.launchpad.net/bugs/2008797
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 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

** Summary changed:

- amdgpu no-retry page fault in Kinetic Kudu
+ amdgpu no-retry page fault resulting in black screen and unresponsive system

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

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

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0

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

2023-02-28 Thread Michael Reed

I have created an arm64 test kernel at the following link:

https://people.canonical.com/~mreed/hpe/lp_2008751_hpwdt/

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

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

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

Bug description:
  SRU Justification:

  [Impact]

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

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

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

  [Test Plan]

  [Where Problems Could Occur]

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

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


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

[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

2023-02-28 Thread Nat!

To quote myself from the original bug report: "I ran the tests on ZFS
and ext4, it makes no difference."

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

Title:
  Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just yesterday and the day before made some benchmark tests for a
  comparison between ext4 and zfs. I ran repeated builds of a large
  software package and it always came out to 45s. Now today I ran the
  same test a few times and it was always 60s. I noticed that today an
  update ran and that kernel 5.19.0-32 was installed. So just now I
  booted back to 5.15.0-60-generic:amd64 and ran the test again: back to
  45s.

  I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM
  otherwise there is nothing very special going on. I ran the tests on
  ZFS and ext4, it makes no difference.

  To reproduce, I would think that compiling any decent sized software package 
one on 5.15 and then on 5.19 whould yield the same results.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-07-15 (217 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  wayland-session jammy
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: TRX40 Taichi
  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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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/2007717/+subscriptions


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

[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

So is this ZFS specific? From the description it sounds like the slow
down happens to ext4 too?

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

Title:
  Kernel linux-image-5.19.0-32 regression, compile speed down by 33%

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just yesterday and the day before made some benchmark tests for a
  comparison between ext4 and zfs. I ran repeated builds of a large
  software package and it always came out to 45s. Now today I ran the
  same test a few times and it was always 60s. I noticed that today an
  update ran and that kernel 5.19.0-32 was installed. So just now I
  booted back to 5.15.0-60-generic:amd64 and ran the test again: back to
  45s.

  I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM
  otherwise there is nothing very special going on. I ran the tests on
  ZFS and ext4, it makes no difference.

  To reproduce, I would think that compiling any decent sized software package 
one on 5.15 and then on 5.19 whould yield the same results.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-07-15 (217 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  wayland-session jammy
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: TRX40 Taichi
  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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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/2007717/+subscriptions


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

[Kernel-packages] [Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend

2023-02-28 Thread rdz

This same problem affects me.

Ubuntu 22.04
Thinkpad T14s Gen 3
Linux: 6.1.0-1006-oem

When 'Linux S3' is configured in UEFI BIOS as suspend mode, touchpad is
laggy after resume and one of the CPU cores shows high load.

When setting 'Windows and Linux' as suspend mode in the UEFI BIOS (which
apparently is s2idle), touchpad works normally after resume from
suspend. However, the power drain during s2idle is significant. Battery
level drops by more than 30% when idling overnight.

The trick with removing/inserting the module psmouse doesn't help here.
When I rmmod i2c_hid_acpi, the high CPU load disappears, but comes back
when loading i2c_hid_acpi again.

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

Title:
  [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after
  resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Thinkpad X1 Carbon, 9th generation
  Touchpad: SYNA8009:00 06CB:CE57

  Right after a clean reboot, the touchpad works fine. No issues
  whatsoever. But after resuming from even its first suspend after a
  clean boot, the touchpad feels less responsive, choppy or even laggy.

  I have tried removing and re-inserting some HID kernel modules,
  "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't
  found anything that fixes it yet. The trackpoint works flawlessly all
  the time, so that is the current backup when I don't have an external
  mouse connected.

  My installed OS is Pop!_Os 21.04, but I have tested and confirmed this
  on a live USB with Ubuntu 21.04 as well.

  I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels
  from the mainline PPA, and tried bumping the libinput10 to 1.18.0 from
  the impish repos.

  To recreate:
  1. Reboot a X1C9 machine and see that the touchpad works fine
  2. Suspend it (to RAM, need to change a BiOS setting so it doesn't do a 
software suspend)
  3. Resume from suspend and see that touchpad acts differently and less 
responsive than right after a clean boot

  What is expected:
  1. Same responsive touchpad experience after resuming from suspend as right 
after a clean boot.

  
  ---

  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: pop:GNOME
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroRelease: Pop!_OS 21.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Iris Xe Graphics [17aa:22d5]
  MachineType: LENOVO 20XW005PMX
  Package: libinput10 1.18.0-1 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-e5934199-eb91-4da9-9e38-0ad1de1baeb2\initrd.img 
root=UUID=e5934199-eb91-4da9-9e38-0ad1de1baeb2 ro quiet 
systemd.show_status=false loglevel=0 splash
  Tags: hirsute third-party-packages ubuntu
  Uname: Linux 5.13.5-051305-generic x86_64
  UnreportableReason: This does not seem to be an official Pop!_OS package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.42
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET66W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XW005PMX
  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.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET66W(1.42):bd06/15/2021:br1.42:efr1.26:svnLENOVO:pn20XW005PMX:pvrThinkPadX1CarbonGen9:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:rvnLENOVO:rn20XW005PMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XW005PMX
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2pop0~1624392450~21.04~6fbdfd2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1

[Kernel-packages] [Bug 2008832] Re: Kinetic update: upstream stable patchset 2023-02-28

2023-02-28 Thread Kamal Mostafa

** 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:
+    upstream stable patchset 2023-02-28
  
-upstream stable patchset 2023-02-28
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v5.15.86, v6.0.16
+ 
+    from git://git.kernel.org/
+ 
+ [Massive list of 883 included patches is Comment #1 below.]

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

Title:
  Kinetic update: upstream stable patchset 2023-02-28

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  In Progress

Bug description:
  SRU Justification

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

     upstream stable patchset 2023-02-28

  Ported from the following upstream stable releases:
  v5.15.86, v6.0.16

     from git://git.kernel.org/

  [Massive list of 883 included patches is Comment #1 below.]

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


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

[Kernel-packages] [Bug 2008832] Re: Kinetic update: upstream stable patchset 2023-02-28

2023-02-28 Thread Kamal Mostafa

usb: musb: remove extra check in musb_gadget_vbus_draw
arm64: dts: qcom: ipq6018-cp01-c1: use BLSPI1 pins
arm64: dts: qcom: sm8250-sony-xperia-edo: fix touchscreen bias-disable
arm64: dts: qcom: msm8996: Add MSM8996 Pro support
arm64: dts: qcom: msm8996: fix supported-hw in cpufreq OPP tables
arm64: dts: qcom: msm8996: fix GPU OPP table
ARM: dts: qcom: apq8064: fix coresight compatible
arm64: dts: qcom: sdm630: fix UART1 pin bias
arm64: dts: qcom: sdm845-cheza: fix AP suspend pin bias
arm64: dts: qcom: msm8916: Drop MSS fallback compatible
objtool, kcsan: Add volatile read/write instrumentation to whitelist
ARM: dts: stm32: Drop stm32mp15xc.dtsi from Avenger96
ARM: dts: stm32: Fix AV96 WLAN regulator gpio property
drivers: soc: ti: knav_qmss_queue: Mark knav_acc_firmwares as static
arm64: dts: qcom: pm660: Use unique ADC5_VCOIN address in node name
arm64: dts: qcom: sm8250: correct LPASS pin pull down
soc: qcom: llcc: make irq truly optional
arm64: dts: qcom: sm8150: fix UFS PHY registers
arm64: dts: qcom: sm8250: fix UFS PHY registers
arm64: dts: qcom: sm8350: fix UFS PHY registers
arm64: dts: qcom: sm8250: drop bogus DP PHY clock
soc: qcom: apr: Add check for idr_alloc and of_property_read_string_index
arm64: dts: qcom: sm6125: fix SDHCI CQE reg names
arm: dts: spear600: Fix clcd interrupt
soc: ti: knav_qmss_queue: Fix PM disable depth imbalance in knav_queue_probe
soc: ti: smartreflex: Fix PM disable depth imbalance in omap_sr_probe
arm64: mm: kfence: only handle translation faults
perf: arm_dsu: Fix hotplug callback leak in dsu_pmu_init()
perf/arm_dmc620: Fix hotplug callback leak in dmc620_pmu_init()
perf/smmuv3: Fix hotplug callback leak in arm_smmu_pmu_init()
arm64: dts: ti: k3-am65-main: Drop dma-coherent in crypto node
arm64: dts: ti: k3-j721e-main: Drop dma-coherent in crypto node
ARM: dts: nuvoton: Remove bogus unit addresses from fixed-partition nodes
arm64: dts: mt6779: Fix devicetree build warnings
arm64: dts: mt2712e: Fix unit_address_vs_reg warning for oscillators
arm64: dts: mt2712e: Fix unit address for pinctrl node
arm64: dts: mt2712-evb: Fix vproc fixed regulators unit names
arm64: dts: mt2712-evb: Fix usb vbus regulators unit names
arm64: dts: mediatek: pumpkin-common: Fix devicetree warnings
arm64: dts: mediatek: mt6797: Fix 26M oscillator unit name
ARM: dts: dove: Fix assigned-addresses for every PCIe Root Port
ARM: dts: armada-370: Fix assigned-addresses for every PCIe Root Port
ARM: dts: armada-xp: Fix assigned-addresses for every PCIe Root Port
ARM: dts: armada-375: Fix assigned-addresses for every PCIe Root Port
ARM: dts: armada-38x: Fix assigned-addresses for every PCIe Root Port
ARM: dts: armada-39x: Fix assigned-addresses for every PCIe Root Port
ARM: dts: turris-omnia: Add ethernet aliases
ARM: dts: turris-omnia: Add switch port 6 node
arm64: dts: armada-3720-turris-mox: Add missing interrupt for RTC
seccomp: Move copy_seccomp() to no failure path.
pstore/ram: Fix error return code in ramoops_probe()
ARM: mmp: fix timer_read delay
pstore: Avoid kcore oops by vmap()ing with VM_IOREMAP
tpm/tpm_ftpm_tee: Fix error handling in ftpm_mod_init()
tpm/tpm_crb: Fix error message in __crb_relinquish_locality()
ovl: remove privs in ovl_copyfile()
ovl: remove privs in ovl_fallocate()
sched/uclamp: Fix relationship between uclamp and migration margin
sched/uclamp: Make task_fits_capacity() use util_fits_cpu()
sched/uclamp: Make select_idle_capacity() use util_fits_cpu()
sched/core: Introduce sched_asym_cpucap_active()
sched/uclamp: Make asym_fits_capacity() use util_fits_cpu()
cpuidle: dt: Return the correct numbers of parsed idle states
alpha: fix TIF_NOTIFY_SIGNAL handling
alpha: fix syscall entry in !AUDUT_SYSCALL case
x86/sgx: Reduce delay and interference of enclave release
PM: hibernate: Fix mistake in kerneldoc comment
fs: don't audit the capability check in simple_xattr_list()
cpufreq: qcom-hw: Fix memory leak in qcom_cpufreq_hw_read_lut()
selftests/ftrace: event_triggers: wait longer for test_event_enable
perf: Fix possible memleak in pmu_dev_alloc()
lib/debugobjects: fix stat count and optimize debug_objects_mem_init
platform/x86: huawei-wmi: fix return value calculation
timerqueue: Use rb_entry_safe() in timerqueue_getnext()
proc: fixup uptime selftest
lib/fonts: fix undefined behavior in bit shift for get_default_font
ocfs2: fix memory leak in ocfs2_stack_glue_init()
MIPS: vpe-mt: fix possible memory leak while module exiting
MIPS: vpe-cmp: fix possible memory leak while module exiting
selftests/efivarfs: Add checking of the test return value
PNP: fix name memory leak in pnp_alloc_dev()
perf/x86/intel/uncore: Fix reference count leak in sad_cfg_iio_topology()
perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()
perf/x86/intel/uncore: Fix reference count leak in snr_uncore_mmio_map()
perf/x86/intel/uncore: Fix reference count leak in __uncore_imc_init_box()
platform/chrome: cros_usbpd_notify: Fix error handling in 
cros_usbpd_notify_init()
thermal: core:

[Kernel-packages] [Bug 2008833] [NEW] mlxbf-gige: Fix intermittent no ip issue

2023-02-28 Thread Asmaa Mnebhi

Public bug reported:

SRU Justification:

[Impact]

Although the link is up, and the PHY interrupt is cleared, there is no
ip assigned. Nothing is being transmitted, and nothing is received. The
RX error count keeps on increasing (check ifconfig oob_net0). After
several minutes, the RX error count stagnates and the oob finally gets
an ip and is pingable.

[Fix]

The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is 
enabled,
the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't 
decrease
since the code hasn't ran phy_start yet. The solution is to move the rx init 
after phy_start.
This fix applies to both 5.4 and 5.15.

[Test Case]

* Check if the gige driver is loaded
* Check that the oob_net0 interface is up and pingable from an external host
* Do at ~1000 resets and powercycles and check the oon_net0 interface again

[Regression Potential]

* No known regressions.

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

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

Title:
  mlxbf-gige: Fix intermittent no ip issue

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]

  Although the link is up, and the PHY interrupt is cleared, there is no
  ip assigned. Nothing is being transmitted, and nothing is received.
  The RX error count keeps on increasing (check ifconfig oob_net0).
  After several minutes, the RX error count stagnates and the oob
  finally gets an ip and is pingable.

  [Fix]

  The issue is in the mlxbf_gige_rx_init function. As soon as the RX DMA is 
enabled,
  the RX CI reaches the max 128, it becomes equal to RX PI. And RX CI doesn't 
decrease
  since the code hasn't ran phy_start yet. The solution is to move the rx init 
after phy_start.
  This fix applies to both 5.4 and 5.15.

  [Test Case]

  * Check if the gige driver is loaded
  * Check that the oob_net0 interface is up and pingable from an external host
  * Do at ~1000 resets and powercycles and check the oon_net0 interface again

  [Regression Potential]

  * No known regressions.

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


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

[Kernel-packages] [Bug 2008832] [NEW] Kinetic update: upstream stable patchset 2023-02-28

2023-02-28 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:

   upstream stable patchset 2023-02-28
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Kinetic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Kinetic)
   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/2008832

Title:
  Kinetic update: upstream stable patchset 2023-02-28

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  In Progress

Bug description:
  
  SRU Justification

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

 upstream stable patchset 2023-02-28
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 2006624] Re: Multiple Kernel Ooopses with my Asus ROG Strix X670E-E and Ryzen 9 7950X

2023-02-28 Thread Michael Matera

Hello again. After upgrading to the latest Ubuntu kernel
(5.19.0-32-generic #33~22.04.1-Ubuntu) the problem still exists. Here's
the latest trace:

Feb 28 13:22:58 phoenix kernel: [16506.753694] igc :0a:00.0 eno1: PCIe link 
lost, device now detached
Feb 28 13:22:58 phoenix kernel: [16506.753707] [ cut here 
]
Feb 28 13:22:58 phoenix kernel: [16506.753707] igc: Failed to read reg 0xc030!
Feb 28 13:22:58 phoenix kernel: [16506.753751] WARNING: CPU: 8 PID: 48219 at 
drivers/net/ethernet/intel/igc/igc_main.c:6186 igc_rd32+0xaf/0xc0 [igc]
Feb 28 13:22:58 phoenix kernel: [16506.753760] Modules linked in: rfcomm 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter 
vboxnetadp(OE) vboxnetflt(OE) xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink vboxdrv(OE) bridge 
stp llc cmac algif_hash algif_skcipher af_alg bnep overlay binfmt_misc dm_crypt 
nvidia_uvm(POE) intel_rapl_msr intel_rapl_common edac_mce_amd nvidia_drm(POE) 
kvm_amd nvidia_modeset(POE) iwlmvm uvcvideo kvm videobuf2_vmalloc 
snd_hda_codec_hdmi btusb crct10dif_pclmul mac80211 ghash_clmulni_intel btrtl 
snd_hda_intel videobuf2_memops aesni_intel btbcm snd_usb_audio btintel 
videobuf2_v4l2 snd_intel_dspcfg crypto_simd videobuf2_common snd_intel_sdw_acpi 
cryptd btmtk nvidia(POE) nls_iso8859_1 input_leds snd_seq_midi libarc4 videodev 
snd_usbmidi_lib snd_seq_midi_event snd_hda_codec bluetooth iwlwifi snd_rawmidi 
snd_hda_core snd_se
 q mc snd_hwdep ecdh_generic rapl ecc
Feb 28 13:22:58 phoenix kernel: [16506.753795]  snd_seq_device eeepc_wmi 
asus_nb_wmi wmi_bmof snd_pcm ccp cfg80211 snd_timer snd soundcore mac_hid 
sch_fq_codel msr parport_pc ppdev lp parport ramoops reed_solomon pstore_blk 
pstore_zone efi_pstore ip_tables x_tables autofs4 hid_generic usbhid hid 
ib_uverbs ib_core amdgpu(OE) amddrm_ttm_helper(OE) amdttm(OE) iommu_v2 
amd_sched(OE) amdkcl(OE) drm_display_helper drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm mfd_aaeon asus_wmi cec sparse_keymap 
platform_profile crc32_pclmul rc_core ahci i2c_piix4 i2c_algo_bit nvme xhci_pci 
igc libahci xhci_pci_renesas nvme_core wmi video gpio_amdpt
Feb 28 13:22:58 phoenix kernel: [16506.753819] CPU: 8 PID: 48219 Comm: Qt 
bearer threa Tainted: P   OE 5.19.0-32-generic #33~22.04.1-Ubuntu
Feb 28 13:22:58 phoenix kernel: [16506.753822] Hardware name: ASUS System 
Product Name/ROG STRIX X670E-E GAMING WIFI, BIOS 0805 11/04/2022
Feb 28 13:22:58 phoenix kernel: [16506.753823] RIP: 0010:igc_rd32+0xaf/0xc0 
[igc]
Feb 28 13:22:58 phoenix kernel: [16506.753828] Code: c7 c6 10 55 24 c0 e8 27 9d 
cc c4 48 8b bb 28 ff ff ff e8 94 6e 58 c4 84 c0 74 ae 44 89 ee 48 c7 c7 38 55 
24 c0 e8 19 c6 c1 c4 <0f> 0b e9 74 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 
44 00 00
Feb 28 13:22:58 phoenix kernel: [16506.753829] RSP: 0018:aea41c2fb588 
EFLAGS: 00010246
Feb 28 13:22:58 phoenix kernel: [16506.753831] RAX:  RBX: 
9f79e12d0c58 RCX: 
Feb 28 13:22:58 phoenix kernel: [16506.753832] RDX:  RSI: 
 RDI: 
Feb 28 13:22:58 phoenix kernel: [16506.753833] RBP: aea41c2fb5a8 R08: 
 R09: 
Feb 28 13:22:58 phoenix kernel: [16506.753834] R10:  R11: 
 R12: 
Feb 28 13:22:58 phoenix kernel: [16506.753835] R13: c030 R14: 
9f79e12d R15: 9f79c1813d80
Feb 28 13:22:58 phoenix kernel: [16506.753836] FS:  7fed773fe640() 
GS:9f88d840() knlGS:
Feb 28 13:22:58 phoenix kernel: [16506.753837] CS:  0010 DS:  ES:  CR0: 
80050033
Feb 28 13:22:58 phoenix kernel: [16506.753838] CR2: 2ff953b71000 CR3: 
0002c24b8000 CR4: 00750ee0
Feb 28 13:22:58 phoenix kernel: [16506.753839] PKRU: 5554
Feb 28 13:22:58 phoenix kernel: [16506.753839] Call Trace:
Feb 28 13:22:58 phoenix kernel: [16506.753841]  
Feb 28 13:22:58 phoenix kernel: [16506.753843]  igc_update_stats+0xa5/0x740 
[igc]
Feb 28 13:22:58 phoenix kernel: [16506.753847]  igc_get_stats64+0x95/0xa0 [igc]
Feb 28 13:22:58 phoenix kernel: [16506.753851]  dev_get_stats+0x6a/0x150
Feb 28 13:22:58 phoenix kernel: [16506.753855]  rtnl_fill_stats+0x40/0x140
Feb 28 13:22:58 phoenix kernel: [16506.753857]  rtnl_fill_ifinfo+0x80f/0x1090
Feb 28 13:22:58 phoenix kernel: [16506.753859]  rtnl_dump_ifinfo+0x5c9/0x760
Feb 28 13:22:58 phoenix kernel: [16506.753862]  ? __nla_put+0x20/0x40
Feb 28 13:22:58 phoenix kernel: [16506.753866]  ? __alloc_skb+0xee/0x1e0
Feb 28 13:22:58 phoenix kernel: [16506.753869]  netlink_dump+0x1bb/0x350
Feb 28 13:22:58 phoenix kernel: [16506.753871]  __netlink_dump_start+0x1e1/0x310
Feb 28 13:22:58 phoenix kernel: [16506.753873]  ? rtnl_getlink+0x430/0x430
Feb 28 13:22:58 phoenix kernel: [16506.753874]  rtnetlink_rcv_msg+0x2b8/0x440
Feb 28

[Kernel-packages] [Bug 2008111] Re: mt9m114 webcam sensor power-up failed

2023-02-28 Thread Luca Leonardo Scorcia

After further investigation, it seems the message is partially
misleading. Power management for mt9m114 on ASUS T100 is indeed not
implemented yet, but not because of a missing define - the necessary
define is actually active in the kernel config. It is a kernel issue
instead - apparently fixed by commit
https://github.com/torvalds/linux/commit/73d15a7c13bfe1292db85ed3de8dfa711291819d
which is not yet present in any mainline kernel (should be present in
the next 6.3 release).

As a cautionary warning though audio is broken in mainline kernel 6.2.1
so the whack-a-mole game for Bay Trail devices may continue even with
the next kernel :-)

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

Title:
  mt9m114 webcam sensor power-up failed

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

Bug description:
  On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the
  last non-working piece of hardware. The following dmesg snippet seems
  to suggest that the kernel needs a special config flag:

  [   25.478178] atomisp_gmin_platform: module is from the staging directory, 
the quality is unknown, you have been warned.
  [   25.478274] atomisp_gmin_platform: module verification failed: signature 
and/or required key missing - tainting kernel
  [   25.508617] atomisp_mt9m114: module is from the staging directory, the 
quality is unknown, you have been warned.
  [   25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via 
Crystal Cove PMIC (i2c addr 0x6e)
  [   25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is 
\_SB.I2C4.CAM0
  [   25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable 
INT33F0:00_ClkSrc
  [   25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1)
  [   25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 
'INT33F0:00_CsiPort'
  [   25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 
'INT33F0:00_CsiLanes'
  [   25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI
  [   25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI
  [   25.651241] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable 
gmin_V1P8GPIO
  [   25.651247] mt9m114 i2c-INT33F0:00: V1P8GPIO: using default (-1)
  [   25.651440] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable 
gmin_V2P8GPIO
  [   25.651445] mt9m114 i2c-INT33F0:00: V2P8GPIO: using default (-1)
  [   25.651457] mt9m114 i2c-INT33F0:00: Will use CLK1 (pmc_plt_clk_1)
  [   25.651472] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented
  [   25.651475] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e 
reg-addr 0x5d value 0x63 mask 0xff
  [   25.651480] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed 
to access I2C address 0x6e.
 Need to compile the kernel using CONFIG_*_PMIC_OPREGION 
settings
  [   25.651572] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented
  [   25.651575] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e 
reg-addr 0x5d value 0x62 mask 0xff
  [   25.651579] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed 
to access I2C address 0x6e.
 Need to compile the kernel using CONFIG_*_PMIC_OPREGION 
settings
  [   25.651659] mt9m114 i2c-INT33F0:00: sensor power-up failed
  [   25.651691] INT33F0:00: mt9m114 power-up err

  Is this something that could be considered for the next kernels? Can I
  preview test it somehow? Keep in mind that this laptop is pretty
  slow...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 10:56:28 2023
  InstallationDate: Installed on 2023-02-12 (9 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2008824] 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 2008824

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

Title:
  sched: cpumask: improve on cpumask_local_spread() locality

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A patch series landed upstream during the v6.3 merge window that shows 
impressive performance improvements in iperf3 multi-stream performance on NUMA 
based systems w/ Mellanox network controllers:
https://www.spinics.net/lists/linux-rdma/msg115357.html

  It would be valuable to land those in lunar, allowing our LTS users to
  adopt them more quickly starting with the HWE kernel in 22.04.3.

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


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

[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize

2023-02-28 Thread Khaled El Mously

Verified the issue is no longer reproducible on linux-aws Ubuntu-
aws-5.15.0-1031.35

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

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

Title:
  Regression in ext4 during online resize

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  Issue

  resize2fs utility is used to resize the filesystem and is idempotent
  in nature. But in the 5.15 kernel, successive execution of resize2fs
  is returning error.

  Reproduction step (on AWS):

  Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 
5.15.0-1022-aws) in us-west-2 region and attach an EBS volume.
  Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p 
/mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0
  Increase the size of EBS volume.
  Run sudo resize2fs /dev/xvdb multiple times.

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  The filesystem is already 5242880 (4k) blocks long.  Nothing to do!

  When you run the same step on the latest image ami-0a1d6d351894df6cc
  (Linux 5.15.0-1026-aws).

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/xvdb
  Couldn't find valid filesystem superblock.


  FIX:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b

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


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

[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep

2023-02-28 Thread isotope

My issue is now resolved. Not sure, but I think it was broken GRUB
somehow in my case. Right after issue started manifesting itself, I
noticed every time update shows up, any GRUB related items are
deselected and could not be selected in Software Updater GUI. Tried
terminal and those same packages showed as "kept back" and would not
update. After quick search, I tried to apt install those packages and it
did work! All of the sudden, my laptop started coming alive after
suspend instead of becoming zombie. Hope this helps someone.

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

Title:
Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on
after waking up from sleep

Status in linux package in Ubuntu:
Confirmed

Bug description:
Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on
after waking up from sleep

Scenario:

Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring
nomodeset kernel boot option to be added in GRUB at boot time when
booting from USB stick. This can be achieved by following instructions
from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual-
nomodeset-kernel-boot-line-option-for-linux-booting

Then, nomodeset needs to be permanently added to /etc/default/grub
Followed instructions from
https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu

If nomodeset is not added, Dell Latitude 7390 will freeze at one point
or another, either before reaching the Gnome desktop, either little
after. This is the case with both, installing Ubuntu 22.10 from Live
USB and running Ubuntu 22.10 after install the install (and having the
USB stick disconnected).

The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and
having nomodeset permanently added to GRUB for each boot is:

If by chance the system goes into sleep, after waking up, there is a
totally pitch-black screen; nothing shows up, no screen backlight
either. However, caps-lock works and I am able to log in to the system
via ssh and can see the system is up an running well. I can even issue
a request to send the system to sleep by “sudo systemctl suspend” and
then wake the the system up several times without loosing ssh access,
however, the screen will remain pitch-black.

Other tries to troubleshoot and see if the system can be brought back with a
working display (while nomodeset kernel option is being used):

1. sudo systemctl suspend -i
>>> this will result in an unusable system after waking up, again, with a
pitch-black screen; moreover, the caps-lock would not work, the keyboard
backlight won’t work, ssh won’t work; I need a hard reset to get the system
back up.

2. start the system in single user mode by inserting “single” in GRUB at boot
time;
>>> the system will be unusable after waking up, same as in try 1.

3. after a normal boot into the GNOME desktop with kernel nomodeset
option and investigating the dmesg for any acpi, no error could be
found.

Tried to read up on other possible solutions, while stumbled upon the ubuntu
wiki page below:
https://wiki.ubuntu.com/UnderstandingSuspend
Unfortunately, to not much help so far.

Other notes:
N1. All the above were done by having the latest BIOS v1.30.0
N2. This laptop came with Windows 10 Pro which works fine: goes into suspend
and wakes up fine, with working screen and display.

N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source:
https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984
) and the user manual states it has support for Ubuntu. Therefore, other older
and major Ubuntu versions were given a try, along with a new version of Fedora:
N3.1 – Ubuntu 22.04
N3.2 – Ubuntu 18.04.6
N3.3 – Ubuntu 16.04.7
N3.4 – Fedora-Workstation-Live-x86_64-37-1.7
Each of the above will freeze at one point or another if nomodeset is not
used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and
install well from the USB Live stick and will also run fine after the install,
until the system goes into sleep, after which, when the system is awake, the
screen is black and will have nothing displayed.

Any advice will be appreciated. Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-31-generic 5.19.0-31.32
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tuser 2832 F wireplumber
/dev/snd/seq:tuser 2829 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 11 13:37:59 2023
InstallationDate: Installed on 2023-01-15 (27 days

[Kernel-packages] [Bug 2008824] [NEW] sched: cpumask: improve on cpumask_local_spread() locality

2023-02-28 Thread dann frazier

Public bug reported:

A patch series landed upstream during the v6.3 merge window that shows 
impressive performance improvements in iperf3 multi-stream performance on NUMA 
based systems w/ Mellanox network controllers:
  https://www.spinics.net/lists/linux-rdma/msg115357.html

It would be valuable to land those in lunar, allowing our LTS users to
adopt them more quickly starting with the HWE kernel in 22.04.3.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: Incomplete

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  sched: cpumask: improve on cpumask_local_spread() locality

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A patch series landed upstream during the v6.3 merge window that shows 
impressive performance improvements in iperf3 multi-stream performance on NUMA 
based systems w/ Mellanox network controllers:
https://www.spinics.net/lists/linux-rdma/msg115357.html

  It would be valuable to land those in lunar, allowing our LTS users to
  adopt them more quickly starting with the HWE kernel in 22.04.3.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop/5.15.0.1016.15)

2023-02-28 Thread Ubuntu SRU Bot

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

snapd/2.58+22.04 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packaging resyncs.

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


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

[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend

2023-02-28 Thread Kristian Lange

The ctrl+alt+F2 trick didn't work with me. My keyboard seems to be not
working after suspend.

But I stumbled over this Reddit post:
https://www.reddit.com/r/thinkpad/comments/lnyrt6/til_i_learn_newer_thinkpads_have_a_setting_for.
There is a "Sleep State" switch in the BIOS of some Thinkpads (Config ➜
Power ➜ Sleep State ➜ “Linux” / “Windows 10”). I just turned it from
"Windows" to "Linux" and it seems to work now. But I'm not sure yet. I
will test more.

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

Title:
  Ubuntu 22.04 not waking up after second suspend

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

Bug description:
  After the first suspend it wakes up just fine - it's the second
  suspend after which the screen stays blank and keyboard doesn't react
  (although the power LED starts glowing). It happens if I close the
  laptop's lid or do a manual suspend via the system menu. It happens
  only recently (I think after some kernel update, but I'm not sure
  about this) - before it worked fine for month (since I installed
  Ubuntu).

  I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the
  only OS (if that's important).

  What I tried:

  * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896)
  * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896)
  * I looked through the logs in /var/log but couldn't find anything obvious to 
me (but I'm not a Linux guru).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 28 11:02:36 2023
  InstallationDate: Installed on 2022-06-14 (258 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2008231] Re: ubuntu freezes randomly

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

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

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

Title:
  ubuntu freezes randomly

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

Bug description:
  When opening a random app the screen going to blink and then freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 23 14:33:27 2023
  InstallationDate: Installed on 2022-07-03 (235 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400

(End User: https://askubuntu.com/questions/1455925/dell-
xps-13-plus-9320-horizontal-lines-static-after-installing-latest-
release)

Test kernel did not correct the issue on my machine.
https://people.canonical.com/~khfeng/lp2007516/jammy-5.19/

  OPERATING SYSTEM:   Ubuntu 22.04
Kernel:   5.19.0-1035-generic (x86_64)  

 GRAPHICS:   Intel ADL GT2 31GB
Frequency:1400MHz  
OpenGL:   4.6 Mesa 22.2.5  
Vulkan:   1.3.224  
Screen:   1920x1200  

  MOTHERBOARD:Dell 0CW9KM
BIOS Version: 1.11.0

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

Title:
  XPS 9320 screen flicker on UHD panel 3840x2400

Status in HWE Next:
  New
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Confirmed
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  The screen flicker after ubuntu jammy upgrade kernel to 5.19.

  The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in
  5.19 kernel.

  I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config
  can omit the issue.

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


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

[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

2023-02-28 Thread Jeff Lane 

** Description changed:

  [Impact]
  Currently Ubuntu kernel has this kernel config disabled.
  But in some case, Intel's SPR-HBM needs this.
  
  Please search the keyword "fake numa" in
  https://community.intel.com/t5/Blogs/Products-and-
  Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-
  Applications-for/post/1335100
  
  [Fix]
  
+ Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later
+ 
  [Test Plan]
  
  [Where problems could occur]
  
  The regression risk is low
  
  [Other Info]

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

Title:
  [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Incomplete

Bug description:
  [Impact]
  Currently Ubuntu kernel has this kernel config disabled.
  But in some case, Intel's SPR-HBM needs this.

  Please search the keyword "fake numa" in
  https://community.intel.com/t5/Blogs/Products-and-
  Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI-
  Applications-for/post/1335100

  [Fix]

  Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later

  [Test Plan]

  [Where problems could occur]

  The regression risk is low

  [Other Info]

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


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

[Kernel-packages] [Bug 1999554] Re: LTP uevent01 will fail on GCP n2d-standard-64

2023-02-28 Thread Thadeu Lima de Souza Cascardo

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

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

Title:
  LTP uevent01 will fail on GCP n2d-standard-64

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Because udev takes too long to release the loop device, LTP test
  uevent01 (and some other tests) may warn about not being able to
  detach the loop device. This is identified as a failure.

  
  ubuntu@selfprovisioned-cascardo-n2d:~$ sudo ./uevent01 
  tst_test.c:1423: TINFO: Timeout per run is 0h 05m 00s
  tst_device.c:88: TINFO: Found free device 6 '/dev/loop6'
  uevent01.c:24: TINFO: Attaching device /dev/loop6
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: DISK_MEDIA_CHANGE=1
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2959
  uevent.h:140: TPASS: Got expected UEVENT
  uevent.h:49: TINFO: Got uevent:
  uevent.h:52: TINFO: change@/devices/virtual/block/loop6
  uevent.h:52: TINFO: ACTION=change
  uevent.h:52: TINFO: DEVPATH=/devices/virtual/block/loop6
  uevent.h:52: TINFO: SUBSYSTEM=block
  uevent.h:52: TINFO: MAJOR=7
  uevent.h:52: TINFO: MINOR=6
  uevent.h:52: TINFO: DEVNAME=loop6
  uevent.h:52: TINFO: DEVTYPE=disk
  uevent.h:52: TINFO: DISKSEQ=7
  uevent.h:52: TINFO: SEQNUM=2960
  uevent.h:140: TPASS: Got expected UEVENT
  uevent01.c:26: TINFO: Detaching device /dev/loop6
  tst_device.c:254: TWARN: ioctl(/dev/loop6, LOOP_CLR_FD, 0) no ENXIO for too 
long

  Summary:
  passed   2
  failed   0
  broken   0
  skipped  0
  warnings 1

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


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

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault in Kinetic Kudu

2023-02-28 Thread Allard Pruim

Here the same issue. After I got the update to 5.19 my laptop froze when
I opened or used Spotify. I also had to install the linux-oem-22.04c
kernel.

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

Title:
  amdgpu no-retry page fault in Kinetic Kudu

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
  Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin!
  Nov 03 16:35:55 laptop kernel: [drm] free PSP TMR buffer
  Nov 03 16:35:55

[Kernel-packages] [Bug 1930783] Re: integrity: Problem loading X.509 certificate

2023-02-28 Thread Fernando Barbosa Ferreira Lopes

Hello there, i have seen this exact problem on my Acer Aspire A515-52G
as well, so decided to come here and confirm the issue.

Currently running: Ubuntu 22.04.2 LTS
- Kernel 5.19.0-32-generic

>From what i recall, the issue persisted through Ubuntu 22.10 as well.

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

Title:
  integrity: Problem loading X.509 certificate

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following error shows on Acer machines while booting when UEFI boot is
  enabled.

  integrity: Problem loading X.509 certificate -65

  The issue is discussed at
  https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is
  available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch
  is not included in Ubuntu as I'm still getting this error.

  I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error
  comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also.

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


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

[Kernel-packages] [Bug 2007579] Re: Raptor Lake Thermald ITMT version 2 support

2023-02-28 Thread Colin Ian King

I've been exercising the existing code paths of thermald for several
days now with no observable regression in behaviour. I cannot test the
new code path change for this fix as I don't have the exact same system
as that reported in the bug.

For what I can see, there is no regression on this single change for
Kinetic.

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

Title:
  Raptor Lake Thermald ITMT version 2 support

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Bionic:
  Won't Fix
Status in thermald source package in Focal:
  Won't Fix
Status in thermald source package in Jammy:
  In Progress
Status in thermald source package in Kinetic:
  Fix Committed
Status in thermald source package in Lunar:
  Fix Released

Bug description:
  == SRU Justification Kinetic ==

  Raptor Lake system uses ITMT v2 instead of V1 for thermal
  configuration via GDDV.

  This was observed on Dell XPS 9320 system.
  Because thermald can't parse V2 table, it is not getting correct thermal 
threshold temperature and power limits.

  == The Fix ==

  This is fixed in upstream thermald by the patch:
  
https://github.com/intel/thermal_daemon/commit/90d56bc06cdcf78e7398ea7da389401516591774
  This fix is part of Thermald 2.5.2 release.

  The fix applies cleanly and this is already in Ubuntu Lunar in
  thermald 2.5.2.  The fix checks for illegal ITMT version and handles
  version 2 as a specific exceptional case.

  == Regression Risks ==

  For systems that do not used ITMT, no change in behaviour will occur.
  Systems with versions > 2 (currently not valid) will not have ITMT
  parsed anymore; this will avoid misinterpreting unsupported ITMT data.
  Finally, version 2 of ITMT will be now parsed differently and
  additional fields will be parsed and these will be ignored as
  intended.

  == Test Plan ==

  Test against a Dell XPS 9320 system. See if it handles the ITMT correctly. 
The thermald log should indicate version 2 is being used with the message: 
  "ignore dummy_str: ds d1 d2 d3 " where ds = a string, d1 .. d3 are uint64 
values that are parsed and ignored.

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


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

[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend

2023-02-28 Thread Formula Ron

There's many other screen related issues like this with 5.19.0-32 and
with RYZEN processors with integrated graphics too.

My desktop is a RYZEN 5 2400G and I have the same issue with resuming
from suspend or hibernation. I have a workaround though.

Once the monitor is blank but processor appears running, I do
ctrl+alt+F2 to get to the console. The screen then flickers into life
and then ctrl+alt+F7 to get back the the monitor. And all appears OK on
the display again.

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

Title:
  Ubuntu 22.04 not waking up after second suspend

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

Bug description:
  After the first suspend it wakes up just fine - it's the second
  suspend after which the screen stays blank and keyboard doesn't react
  (although the power LED starts glowing). It happens if I close the
  laptop's lid or do a manual suspend via the system menu. It happens
  only recently (I think after some kernel update, but I'm not sure
  about this) - before it worked fine for month (since I installed
  Ubuntu).

  I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the
  only OS (if that's important).

  What I tried:

  * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896)
  * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896)
  * I looked through the logs in /var/log but couldn't find anything obvious to 
me (but I'm not a Linux guru).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 28 11:02:36 2023
  InstallationDate: Installed on 2022-06-14 (258 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2008795] [NEW] Please apply yet another set of Orin, platform enablement patches

2023-02-28 Thread Brad Figg

Public bug reported:

 [Impact]
Adding these patches enables additional functionality and addresses bugs 
related to the Ubuntu kernel on Orin reference HW.

 [Fix]
These patches do not constitute a single fix or a set of fixes for bugs but 
instead enable kernel functionality as well as fix kernel bugs related to 
Nvidia HW.

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

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

Title:
  Please apply yet another set of Orin, platform enablement patches

Status in linux-nvidia package in Ubuntu:
  New

Bug description:
   [Impact]
  Adding these patches enables additional functionality and addresses bugs 
related to the Ubuntu kernel on Orin reference HW.

   [Fix]
  These patches do not constitute a single fix or a set of fixes for bugs 
but instead enable kernel functionality as well as fix kernel bugs related to 
Nvidia HW.

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


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

[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests

2023-02-28 Thread Stefan Bader

** Summary changed:

- Fix selftests/ftracetests/Meta-selftests in Focal
+ Fix selftests/ftracetests/Meta-selftests

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

Title:
  Fix selftests/ftracetests/Meta-selftests

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  == Impact ==
  This subtest checks for bashisms in the test scripts of ftracetests. A recent 
stable change added such a case. This is harmless but causes the Meta-selftests 
to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer 
for test_event_enable" which adds:
  +   if [ "$e" == $val ]; then

  == Fix ==
  Replace the test with
  +   if [ "$e" = $val ]; then

  == Testcase ==
  Running the kernel selftests/ftracetest (done in ADT and RT) should no longer 
show "Meta-selftests" as FAILed.

  == Regression Potential ==
  This affects only the selftest suite and only ftrace subtests. Any change 
would only be observable there.

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


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

[Kernel-packages] [Bug 2008781] 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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root audio 116, 33 Feb 27 13:33 timer
  AplayDevices:

[Kernel-packages] [Bug 2008785] Comment bridged from LTC Bugzilla

2023-02-28 Thread bugproxy

--- Comment From boris.m...@de.ibm.com 2023-02-28 09:24 EDT---
This feature is included in s390-tools v2.26 which is available here:
https://github.com/ibm-s390-linux/s390-tools/releases/tag/v2.26.0

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

Title:
  [23.04 FEAT] [KRN1902] vmconvert and zgetdump consolidation
  (s390-tools)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Feature Description:

  Integrate the existing s390-tools vmconvert tool into zgetdump. 
  With that, we remove the confusion for users about which tool has to be used.

  This feature requires a description of the changes in the Release
  Notes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2008785/+subscriptions


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

[Kernel-packages] [Bug 2008785] Re: [23.04 FEAT] [KRN1902] vmconvert and zgetdump consolidation (s390-tools)

2023-02-28 Thread Frank Heimes

Aligning to LP#2003284 status ...

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: ubuntu-z-systems
   Status: New => Fix Committed

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

** Information type changed from Private to Public

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

Title:
  [23.04 FEAT] [KRN1902] vmconvert and zgetdump consolidation
  (s390-tools)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Feature Description:

  Integrate the existing s390-tools vmconvert tool into zgetdump. 
  With that, we remove the confusion for users about which tool has to be used.

  This feature requires a description of the changes in the Release
  Notes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2008785/+subscriptions


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

[Kernel-packages] [Bug 2003637] Re: [23.04 FEAT] zcrypt DD: AP command filtering

2023-02-28 Thread Frank Heimes

Patch request submitted:
https://lists.ubuntu.com/archives/kernel-team/2023-February/thread.html#137396
Updating status to 'In Progress'.

In addition test builds in PPA were done for all major architectures with the 
unstable kernel
that incl. the patches mentioned above.
https://launchpad.net/~fheimes/+archive/ubuntu/lp2003637


** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
Team (canonical-kernel-team)

** Information type changed from Private to Public

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

Title:
  [23.04 FEAT] zcrypt DD: AP command filtering

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Feature Description:

  Support Stateless AP Commands.
  This will mainly affect error processing and recognizing new error types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003637/+subscriptions


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

[Kernel-packages] [Bug 1982378] Re: [23.04 FEAT] Support for new IBM Z Hardware (IBM z16) - Reset DAT-Protection facility support

2023-02-28 Thread Frank Heimes

Patch request submitted:
https://lists.ubuntu.com/archives/kernel-team/2023-February/thread.html#137395
Updating status to 'In Progress'.

In addition test builds in PPA were done for all major architectures with the 
unstable kernel
that incl. the patches mentioned above.
https://launchpad.net/~fheimes/+archive/ubuntu/lp1982378

** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

** Information type changed from Private to Public

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
Team (canonical-kernel-team)

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

Title:
  [23.04 FEAT] Support for new IBM Z Hardware (IBM z16) - Reset DAT-
  Protection facility support

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Support for new IBM Z Hardware.

  Target public release: kernel 5.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982378/+subscriptions


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

[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card

** 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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root audio 116, 33 Feb 27 13:33 timer
  AplayDevices: Error: [Errno 2] No such file or

[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize

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

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

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


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

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

Title:
  Regression in ext4 during online resize

Status in linux package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gcp source package in Jammy:
  Fix Committed

Bug description:
  Issue

  resize2fs utility is used to resize the filesystem and is idempotent
  in nature. But in the 5.15 kernel, successive execution of resize2fs
  is returning error.

  Reproduction step (on AWS):

  Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 
5.15.0-1022-aws) in us-west-2 region and attach an EBS volume.
  Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p 
/mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0
  Increase the size of EBS volume.
  Run sudo resize2fs /dev/xvdb multiple times.

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  The filesystem is already 5242880 (4k) blocks long.  Nothing to do!

  When you run the same step on the latest image ami-0a1d6d351894df6cc
  (Linux 5.15.0-1026-aws).

  The first execution returns -

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required
  old_desc_blocks = 2, new_desc_blocks = 3
  The filesystem on /dev/xvdb is now 5242880 (4k) blocks long.

  The following execution returns

  $ sudo resize2fs /dev/xvdb
  resize2fs 1.45.5 (07-Jan-2020)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/xvdb
  Couldn't find valid filesystem superblock.


  FIX:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b

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


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

[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card

** Attachment added: "sosreport-compute-05-2004262-2023-02-28-wubkvmj.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008781/+attachment/5650469/+files/sosreport-compute-05-2004262-2023-02-28-wubkvmj.tar.xz

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

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:

[Kernel-packages] [Bug 2008781] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650468/+files/acpidump.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root

[Kernel-packages] [Bug 2008781] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650467/+files/WifiSyslog.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1

[Kernel-packages] [Bug 2008781] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2008781/+attachment/5650466/+files/UdevDb.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root audio

[Kernel-packages] [Bug 2008781] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650465/+files/ProcModules.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1

[Kernel-packages] [Bug 2008781] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650464/+files/ProcInterrupts.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq

[Kernel-packages] [Bug 2008781] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650463/+files/ProcEnviron.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1

[Kernel-packages] [Bug 2008781] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650462/+files/ProcCpuinfoMinimal.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq

[Kernel-packages] [Bug 2008781] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650461/+files/ProcCpuinfo.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1

[Kernel-packages] [Bug 2008781] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650460/+files/Lsusb-v.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root

[Kernel-packages] [Bug 2008781] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650459/+files/Lspci-vt.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root

[Kernel-packages] [Bug 2008781] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2008781/+attachment/5650457/+files/CurrentDmesg.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1

[Kernel-packages] [Bug 2008781] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2008781/+attachment/5650458/+files/Lspci.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root audio

[Kernel-packages] [Bug 2008781] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/2008781/+attachment/5650456/+files/CRDA.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/2008781

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms

  Now I can ping both ways

  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
   crw-rw 1 root audio 116,

[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card

apport information

** Tags added: apport-collected focal uec-images

** Description changed:

  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
  
  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  
  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1
  
  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms
  
  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely
  
  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0
  
  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device
  
  Another thing I tried was to install the HWE kernel
  
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  
  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from 10.99.0.213: icmp_seq=6 ttl=62 time=1.05 ms
  
  Now I can ping both ways
  
  However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
  Here's the bug I am referring to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Feb 27 13:33 seq
+  crw-rw 1 root audio 116, 33 Feb 27 13:33 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu27.25
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'

[Kernel-packages] [Bug 1989941] Re: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again

Is this still an issue with updated kernel & firmware?

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

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

Title:
  Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode
  5.15.0-47-generic - Wifi broken again

Status in kernel-package package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  Hi

  same bug as https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1967842 reappeared with the latest Kernel update
  5.15.0-47-generic on same machine.

  Previous Kernel 5.15.0-46-generic is working.

  md5sum broken firmware from linux-firmware (Jammy Repo)
  dcf642fd7412614e19d1d54f57147539  
/usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode

  Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is 
working again.
  md5sum from Ubuntu 20.04 firmware:
  0668e93b8766bf95d6adffdb33ec7bdb  
/usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode

  The older firmware was already a workaround for the older bugreport.
  Should maybe the newer firmware reverted for jammy?

  dmesg with not working configuration:
  - Kernel 5.15.0-47-generic
  - linux-firmware 20220329.git681281e4-0ubuntu3.5

  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002)
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28
  [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 
46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 
9260 160MHz, REV=0x324
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 
58:a0:23:cf:1e:8f
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to 
disable radio.
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio 
disabled)
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 
'MCC_UPDATE_CMD'
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 
9260 160MHz, REV=0x324
  [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 
58:a0:23:cf:1e:8f
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT 
calibrations: -110
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump:
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, 
valid: 6
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 
46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | 
NMI_INTERRUPT_UNKNOWN
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3
  [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | beacon

[Kernel-packages] [Bug 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  iwlwifi Not valid error log pointer 0x causes WiFi to not work
  but bluetooth works

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  For some reason, Ubuntu gets glitched where the Bluetooth works but
  WiFi does not even show up. If I reboot into Windows, it is a similar
  issue (wifi does not show up, but device manager shows Code 10. If I
  disable and enable the adaptor Intel Wireless AC 9560, it sometimes
  works and most times does not). After a few days, the issue goes away.

  Relevent info:
  Laptop: Asus ROG Strig-G 531GT
  Using newest bios 308
  WiFi Adaptor: Intel Wireless AC 9560
  As for wifi connection, usually wifi icon does not even show and stays that 
way throughout the whole uptime. If I reboot a couple of times, this may 
change. However, the wifi I connect to usually is WiFi 5 on 5G channel running 
WPA2. If I use my laptop outside my home, it connects to enterprise WiFi
  Here is the Intel firmware version 
  [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 
46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm


  Here is the relevent Dmesg output 
  [code]
  [   10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   10.909348] iwlwifi :00:14.3: IML/ROM dump:
  [   10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   10.909397] iwlwifi :00:14.3: Fseq Registers:
  [   10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   10.909494] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110
  [   14.101296] iwlwifi :00:14.3: retry init count 1
  [   14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x318
  [   14.112168] thermal thermal_zone6: failed to read out thermal zone (-61)
  [   15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   15.390284] iwlwifi :00:14.3: IML/ROM dump:
  [   15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   15.390332] iwlwifi :00:14.3: Fseq Registers:
  [   15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   15.390428] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [/code]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04

[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card

Also checked the correct ovn trace

As the packets should reach the destination if driver was behaving
correctly

ubuntu@juju-7639a4-3-lxd-6:~$ network="provider1-net-external" 
inport="4679fbb8-3d4d-4dcd-b986-4ec4c0fb9000" ip4_src="10.99.0.88" 
ip4_dst="10.99.0.254" eth_src="fa:16:3e:ab:87:ad"
ubuntu@juju-7639a4-3-lxd-6:~$ sudo ovn-trace "$network" "inport == \"$inport\" 
&& ip4.src == "$ip4_src" && ip4.dst == "$ip4_dst" && eth.src == "$eth_src" && 
ip.ttl == 64 && icmp4.type == 8"
# 
icmp,reg14=0x3,vlan_tci=0x,dl_src=fa:16:3e:ab:87:ad,dl_dst=00:00:00:00:00:00,nw_src=10.99.0.88,nw_dst=10.99.0.254,nw_tos=0,nw_ecn=0,nw_ttl=64,icmp_type=8,icmp_code=0

ingress(dp="provider1-net-external", inport="4679fb")
---
 0. ls_in_port_sec_l2 (northd.c:5516): inport == "4679fb", priority 50, uuid 
03e0a90b
next;
 6. ls_in_pre_lb (northd.c:5663): ip && inport == "4679fb", priority 110, uuid 
f5e890b2
next;
24. ls_in_l2_lkup (northd.c:7577): 1, priority 0, uuid 3aba4e5b
outport = get_fdb(eth.dst);
next;
25. ls_in_l2_unknown (northd.c:7581): outport == "none", priority 50, uuid 
0bf357af
outport = "_MC_unknown";
output;

multicast(dp="provider1-net-external", mcgroup="_MC_unknown")
---

egress(dp="provider1-net-external", inport="4679fb", 
outport="provnet-8d6ece")


0. ls_out_pre_lb (northd.c:5666): ip && outport == "provnet-8d6ece", 
priority 110, uuid ddd2f5b5
next;
9. ls_out_port_sec_l2 (northd.c:5613): outport == "provnet-8d6ece", 
priority 50, uuid 966e0b90
output;
/* output to "provnet-8d6ece", type "localnet" */

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

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan

[Kernel-packages] [Bug 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works

Is this still an issue with the latest kernel 5.15.0-60.66?

You could also try the dkms iwlwifi driver, maybe it behaves better:
$ apt install backport-iwlwifi-dkms

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

Title:
  iwlwifi Not valid error log pointer 0x causes WiFi to not work
  but bluetooth works

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  For some reason, Ubuntu gets glitched where the Bluetooth works but
  WiFi does not even show up. If I reboot into Windows, it is a similar
  issue (wifi does not show up, but device manager shows Code 10. If I
  disable and enable the adaptor Intel Wireless AC 9560, it sometimes
  works and most times does not). After a few days, the issue goes away.

  Relevent info:
  Laptop: Asus ROG Strig-G 531GT
  Using newest bios 308
  WiFi Adaptor: Intel Wireless AC 9560
  As for wifi connection, usually wifi icon does not even show and stays that 
way throughout the whole uptime. If I reboot a couple of times, this may 
change. However, the wifi I connect to usually is WiFi 5 on 5G channel running 
WPA2. If I use my laptop outside my home, it connects to enterprise WiFi
  Here is the Intel firmware version 
  [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 
46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm


  Here is the relevent Dmesg output 
  [code]
  [   10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   10.909348] iwlwifi :00:14.3: IML/ROM dump:
  [   10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   10.909397] iwlwifi :00:14.3: Fseq Registers:
  [   10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   10.909494] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110
  [   14.101296] iwlwifi :00:14.3: retry init count 1
  [   14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 
160MHz, REV=0x318
  [   14.112168] thermal thermal_zone6: failed to read out thermal zone (-61)
  [   15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 
0x234c
  [   15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 
fired (delay=0ms).
  [   15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x 
for Init uCode
  [   15.390284] iwlwifi :00:14.3: IML/ROM dump:
  [   15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state
  [   15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1
  [   15.390332] iwlwifi :00:14.3: Fseq Registers:
  [   15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE
  [   15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION
  [   15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION
  [   15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION
  [   15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION
  [   15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN
  [   15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID
  [   15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID
  [   15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
  [   15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
  [   15.390428] iwlwifi :00:14.3: 0x485B | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
  [   15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
  [   15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110
  [   15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger

[Kernel-packages] [Bug 2008781] 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 2008781

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

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)

  The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
  openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1

  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
  ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
  --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms

  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
  tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely

  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
   tx_errors: 12
   tx_errors.nic: 0
   rx_length_errors.nic: 0
   rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
  ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
  RX packets 53784  bytes 22064970 (22.0 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 52163  bytes 18393142 (18.3 MB)
  TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
  so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device

  Another thing I tried was to install the HWE kernel

  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  Fortunately traffic was still going out from compute-09 after reboot,
  that fixed the issue
  so we have WORKAROUND 2
  ubuntu@ubuntu-provider2:~$ ping 10.99.0.254
  PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  64 bytes from 10.99.0.254: icmp_seq=1 ttl=63 time=2.15 ms
  64 bytes from 10.99.0.254: icmp_seq=2 ttl=63 time=0.896 ms
  64 bytes from 10.99.0.254: icmp_seq=3 ttl=63 time=1.12 ms
  ^C
  ubuntu@infra-1:~$ ping 10.99.0.213
  PING 10.99.0.213 (10.99.0.213) 56(84) bytes of data.
  64 bytes from 10.99.0.213: icmp_seq=1 ttl=62 time=5.12 ms
  64 bytes from 10.99.0.213: icmp_seq=2 ttl=62 time=2.17 ms
  64 bytes from 10.99.0.213: icmp_seq=3 ttl=62 time=0.948 ms
  64 bytes from 10.99.0.213: icmp_seq=4 ttl=62 time=1.00 ms
  64 bytes from 10.99.0.213: icmp_seq=5 ttl=62 time=0.891 ms
  64 bytes from

[Kernel-packages] [Bug 2008781] Re: OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card

** Description changed:

  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux
  
  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
  31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV 
for SFP (rev 02)
  
- 
- The test instance with provider network floating ip 10.40.0.213 cannot reach 
the provider network gateway
- openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net analyse-private-net ubuntu-analyse
+ The test instance with provider network floating ip 10.99.0.213 cannot reach 
the provider network gateway
+ openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net provider1-private-net ubuntu-provider1
  
  ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
- ubuntu@ubuntu-analyse:~$ ping 10.40.0.254
- PING 10.40.0.254 (10.40.0.254) 56(84) bytes of data.
+ ubuntu@ubuntu-provider1:~$ ping 10.99.0.254
+ PING 10.99.0.254 (10.99.0.254) 56(84) bytes of data.
  ^C
- --- 10.40.0.254 ping statistics ---
+ --- 10.99.0.254 ping statistics ---
  419 packets transmitted, 0 received, 100% packet loss, time 428035ms
- 
  
  I found the compute from which the outside traffic is going out
  and I see ARP requests with no response
  compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
- tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.40.0.254 tell 10.40.0.88, length 28
- fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.40.0.254 tell 10.40.0.88, length 28
- fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.40.0.254 tell 10.40.0.88, length 28
+ tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.99.0.254 tell 10.99.0.88, length 28
+ fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
+ fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.99.0.254 tell 10.99.0.88, length 28
  For the test you may ping .254 indifenetely
- 
  
  The error count grows on tx packets on bond1 and the card ens2f0 (which 
happens to push the traffic)
  ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
-  tx_errors: 12
-  tx_errors.nic: 0
-  rx_length_errors.nic: 0
-  rx_crc_errors.nic: 0
+  tx_errors: 12
+  tx_errors.nic: 0
+  rx_length_errors.nic: 0
+  rx_crc_errors.nic: 0
  ubuntu@compute-09:~$ ifconfig ens2f0
  ens2f0: flags=6211  mtu 9000
- ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
- RX packets 53784  bytes 22064970 (22.0 MB)
- RX errors 0  dropped 0  overruns 0  frame 0
- TX packets 52163  bytes 18393142 (18.3 MB)
- TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0
+ ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
+ RX packets 53784  bytes 22064970 (22.0 MB)
+ RX errors 0  dropped 0  overruns 0  frame 0
+ TX packets 52163  bytes 18393142 (18.3 MB)
+ TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0
  
  If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
- so that creates opportunity for 
+ so that creates opportunity for
  WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device
  
- 
- Anonother thing I tried was to install the HWE kernel
+ Another thing I tried was to install the HWE kernel
  
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  
- Fortunately traffic was still going out from compute-09 after reboot, 
+ Fortunately traffic was still

[Kernel-packages] [Bug 1993071] Re: dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430

Can you try downgrading the FW to see if things behave better?

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

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

Title:
  dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  lots of iwlwifi errors in dmesg.

  loaded firmware version 73.35c0a2c6.0 so-a0-jf-b0-73.ucode op_mode
  iwlmvm

  firmware didn't ACK the reset - continue anyway

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.50.50
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kimathi1734 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 16 19:29:23 2022
  InstallationDate: Installed on 2022-07-26 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   wlo1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1934:5168 Feature Integration Technology Inc. 
(Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiver
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. Wireless keyboard 
(All-in-One-Media)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUS System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=ab6e73ff-42d6-40bd-b4e1-617afcbabcf8 ro quiet splash loglevel=3 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2022
  dmi.bios.release: 16.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1620
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H610I-PLUS D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1620:bd08/12/2022:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610I-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1993071] Re: dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430

Where'd you get that fw from? 73.35c0a2c6.0 so-a0-jf-b0-73.ucode
It's not provided by the linux-firmware package.

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

Title:
  dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  lots of iwlwifi errors in dmesg.

  loaded firmware version 73.35c0a2c6.0 so-a0-jf-b0-73.ucode op_mode
  iwlmvm

  firmware didn't ACK the reset - continue anyway

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-iwlwifi-generic 5.15.0.50.50
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kimathi1734 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 16 19:29:23 2022
  InstallationDate: Installed on 2022-07-26 (82 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
   
   wlo1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1934:5168 Feature Integration Technology Inc. 
(Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiver
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. Wireless keyboard 
(All-in-One-Media)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUS System Product Name
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=ab6e73ff-42d6-40bd-b4e1-617afcbabcf8 ro quiet splash loglevel=3 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2022
  dmi.bios.release: 16.20
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1620
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H610I-PLUS D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1620:bd08/12/2022:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610I-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 2008781] [NEW] OVN provider network type vlan packets cannot go outside the bond on Intel E810-XXV card

Public bug reported:

Ubuntu 20.04.5 LTS
ubuntu@compute-09:~$ uname -a
Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@compute-09:~$ sudo update-pciids
ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether
31:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for 
SFP (rev 02)
31:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for 
SFP (rev 02)
ca:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for 
SFP (rev 02)
ca:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for 
SFP (rev 02)


The test instance with provider network floating ip 10.40.0.213 cannot reach 
the provider network gateway
openstack server create --key-name ubuntu-keypair --image 
auto-sync/ubuntu-jammy-22.04-amd64-server-20230210-disk1.img --flavor m1.small 
--net analyse-private-net ubuntu-analyse

ubuntu@compute-05:~$ sudo -E ip netns exec 
ovnmeta-fcd1b354-6f41-42dc-ae73-87df28856ee5 ssh ubuntu@192.168.100.123
ubuntu@ubuntu-analyse:~$ ping 10.40.0.254
PING 10.40.0.254 (10.40.0.254) 56(84) bytes of data.
^C
--- 10.40.0.254 ping statistics ---
419 packets transmitted, 0 received, 100% packet loss, time 428035ms


I found the compute from which the outside traffic is going out
and I see ARP requests with no response
compute-09:~$ sudo tcpdump -vteni bond1 '(vlan 300)'
tcpdump: listening on bond1, link-type EN10MB (Ethernet), capture size 262144 
bytes fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 
46: vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request 
who-has 10.40.0.254 tell 10.40.0.88, length 28
fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.40.0.254 tell 10.40.0.88, length 28
fa:16:3e:ab:87:ad > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: 
vlan 300, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 
10.40.0.254 tell 10.40.0.88, length 28
For the test you may ping .254 indifenetely


The error count grows on tx packets on bond1 and the card ens2f0 (which happens 
to push the traffic)
ubuntu@compute-09:~$ sudo ethtool -S ens2f0|grep error
 tx_errors: 12
 tx_errors.nic: 0
 rx_length_errors.nic: 0
 rx_crc_errors.nic: 0
ubuntu@compute-09:~$ ifconfig ens2f0
ens2f0: flags=6211  mtu 9000
ether b4:83:51:00:83:d1  txqueuelen 1000  (Ethernet)
RX packets 53784  bytes 22064970 (22.0 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 52163  bytes 18393142 (18.3 MB)
TX errors 12  dropped 0 overruns 0  carrier 0  collisions 0

If I create vlan interface directly on bond1 I can ping the gateway with no 
problem
so that creates opportunity for 
WORKAROUND 1: set the network to flat and push traffic on vlan interfaces on 
computes as for physnet device


Anonother thing I tried was to install the HWE kernel

ubuntu@compute-09:~$ uname -a
Linux compute-09 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Fortunately traffic was still going out from compute-09 after reboot, 
that fixed the issue
so we have WORKAROUND 2
ubuntu@ubuntu-analyse:~$ ping 10.40.0.254
PING 10.40.0.254 (10.40.0.254) 56(84) bytes of data.
64 bytes from 10.40.0.254: icmp_seq=1 ttl=63 time=2.15 ms
64 bytes from 10.40.0.254: icmp_seq=2 ttl=63 time=0.896 ms
64 bytes from 10.40.0.254: icmp_seq=3 ttl=63 time=1.12 ms
^C
ubuntu@infra-1:~$ ping 10.40.0.213
PING 10.40.0.213 (10.40.0.213) 56(84) bytes of data.
64 bytes from 10.40.0.213: icmp_seq=1 ttl=62 time=5.12 ms
64 bytes from 10.40.0.213: icmp_seq=2 ttl=62 time=2.17 ms
64 bytes from 10.40.0.213: icmp_seq=3 ttl=62 time=0.948 ms
64 bytes from 10.40.0.213: icmp_seq=4 ttl=62 time=1.00 ms
64 bytes from 10.40.0.213: icmp_seq=5 ttl=62 time=0.891 ms
64 bytes from 10.40.0.213: icmp_seq=6 ttl=62 time=1.05 ms

Now I can ping both ways

However I am afraid that we may encounter same issue like for Jammy for the 
cards when booting, as it happens randomly for the kernel with the same number 
5.15.0-60
Here's the bug I am reffering
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262

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


** Tags: kernel-bug openstack ovn vlan

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

Title:
  OVN provider network type vlan packets cannot go outside the bond on
  Intel E810-XXV card

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.5 LTS
  ubuntu@compute-09:~$ uname -a
  Linux compute-09 5.4.0-139-generic #156-Ubuntu SMP Fri Jan 20 17:27:18 UTC 
2023 x86_64 x86_64 x86_64 GNU/Linux

  ubuntu@compute-09:~$ sudo update-pciids
  ubuntu@compute-09:~$ lspci |grep Intel|grep -i Ether

[Kernel-packages] [Bug 1874241] Re: iwlwifi intel ax201 crashing on intel nuc10i7fnh

2023-02-28 Thread David Roche

Can we get a confirmation if this issue will be fixed at some point or
can we get a workaround ?

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

Title:
  iwlwifi intel ax201 crashing on intel nuc10i7fnh

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  The intel iwlwifi firmware will crash when you insert a device into
  the thunderbolt3 port, and this will be trigger probabilistically.

  wifi card model:Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354
  Firmware version: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
  Linux-firmware version: 1.187
  thunderbolt3 chip model: Intel Corporation JHL7540 Thunderbolt 3 Bridge 
[Titan Ridge 2C 2018] (rev 06)

  dmesg output:
  [  103.777908] pcieport :00:1c.0: PME: Spurious native interrupt!
  [  103.777918] pcieport :00:1c.0: PME: Spurious native interrupt!
  [  104.118148] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using 
xhci_hcd
  [  104.147184] usb 4-1: New USB device found, idVendor=05e3, idProduct=0749, 
bcdDevice=15.32
  [  104.147190] usb 4-1: New USB device strings: Mfr=3, Product=4, 
SerialNumber=2
  [  104.147194] usb 4-1: Product: USB3.0 Card Reader
  [  104.147197] usb 4-1: Manufacturer: Generic
  [  104.147199] usb 4-1: SerialNumber: 1532
  [  104.183374] usb-storage 4-1:1.0: USB Mass Storage device detected
  [  104.183952] scsi host3: usb-storage 4-1:1.0
  [  104.184172] usbcore: registered new interface driver usb-storage
  [  104.187897] usbcore: registered new interface driver uas
  [  105.217035] scsi 3:0:0:0: Direct-Access Generic  STORAGE DEVICE   1532 
PQ: 0 ANSI: 6
  [  105.217792] sd 3:0:0:0: Attached scsi generic sg1 type 0
  [  105.233978] sd 3:0:0:0: [sdb] Attached SCSI removable disk
  [  109.998995] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [  109.999102] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [  109.999111] iwlwifi :00:14.3: Status: 0x0040, count: 6
  [  109.999119] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
  [  109.999128] iwlwifi :00:14.3: 0x4435 | ADVANCED_SYSASSERT  
  [  109.999135] iwlwifi :00:14.3: 0x008026F4 | trm_hw_status0
  [  109.999142] iwlwifi :00:14.3: 0x | trm_hw_status1
  [  109.999148] iwlwifi :00:14.3: 0x004CA228 | branchlink2
  [  109.999154] iwlwifi :00:14.3: 0x0E26 | interruptlink1
  [  109.999161] iwlwifi :00:14.3: 0x0E26 | interruptlink2
  [  109.999168] iwlwifi :00:14.3: 0x000161A0 | data1
  [  109.999174] iwlwifi :00:14.3: 0xDEADBEEF | data2
  [  109.999180] iwlwifi :00:14.3: 0xDEADBEEF | data3
  [  109.999186] iwlwifi :00:14.3: 0xF90167B5 | beacon time
  [  109.999192] iwlwifi :00:14.3: 0x51938809 | tsf low
  [  109.999199] iwlwifi :00:14.3: 0x0010 | tsf hi
  [  109.999205] iwlwifi :00:14.3: 0x | time gp1
  [  109.999211] iwlwifi :00:14.3: 0x064A1430 | time gp2
  [  109.999217] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [  109.999224] iwlwifi :00:14.3: 0x0030 | uCode version major
  [  109.999231] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
  [  109.999239] iwlwifi :00:14.3: 0x0351 | hw version
  [  109.999245] iwlwifi :00:14.3: 0x00C89004 | board version
  [  109.999252] iwlwifi :00:14.3: 0x069E001C | hcmd
  [  109.999259] iwlwifi :00:14.3: 0x8002 | isr0
  [  109.999265] iwlwifi :00:14.3: 0x0100 | isr1
  [  109.999271] iwlwifi :00:14.3: 0x08F2 | isr2
  [  109.999278] iwlwifi :00:14.3: 0x04C1FFCC | isr3
  [  109.999284] iwlwifi :00:14.3: 0x | isr4
  [  109.999290] iwlwifi :00:14.3: 0x069D001C | last cmd Id
  [  109.999297] iwlwifi :00:14.3: 0x8B70 | wait_event
  [  109.999304] iwlwifi :00:14.3: 0x4208 | l2p_control
  [  109.999310] iwlwifi :00:14.3: 0x2020 | l2p_duration
  [  109.999317] iwlwifi :00:14.3: 0x033F | l2p_mhvalid
  [  109.999324] iwlwifi :00:14.3: 0x00E6 | l2p_addr_match
  [  109.999331] iwlwifi :00:14.3: 0x0009 | lmpm_pmg_sel
  [  109.999337] iwlwifi :00:14.3: 0x | timestamp
  [  109.999344] iwlwifi :00:14.3: 0xB8DC | flow_handler
  [  109.999391] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [  109.999398] iwlwifi :00:14.3: Status: 0x0040, count: 7
  [  109.999406] iwlwifi :00:14.3: 0x2070 | NMI_INTERRUPT_LMAC_FATAL
  [  109.999413] iwlwifi :00:14.3: 0x | umac branchlink1
  [  109.999420] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
  [  109.999427] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink1
  [  109.999434] iwlwifi :00:14.3: 0x8048DBD2 | umac interruptlink2
  [  109.999441] iwlwifi :00:14.3: 0x0400 | umac data1
  [  109.999447] iwlwifi :00:14.3: 0x8048DBD2 | umac data2
  [  109.999454] iwlwifi :00:14.3: 0x | umac data3
  [

[Kernel-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly