date:20230614

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 2023925

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

Title:
  SQUASHFS error: squashfs_read_data failed to read block

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We've had system relying on reading data from squashfs that's been
  stable for a number of years. We've recently noticed that when running
  on machines that include the patch set from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015511 that we
  start to see error messages of the following shape:

  SQUASHFS error: squashfs_read_data failed to read block

  Machines showing the problem are all running kernel 5.4.0-150-generic

  Machines NOT having any problems with the SAME workloads are running a
  mix of the following kernels:

  5.15.0-52-generic
  5.15.0-53-generic
  5.4.0-100-generic
  5.4.0-104-generic
  5.4.0-105-generic
  5.4.0-125-generic
  5.4.0-137-generic
  5.4.0-147-generic

  I'm not able to reproduce the failure on demand.

  What is suspicious to me from that change set is that the following 2
  patches are applied:

  squashfs: harden sanity check in squashfs_read_xattr_id_table
  Squashfs: fix handling and sanity checking of xattr_ids count

  and then only 1 of them is reverted, although the patches in question
  appear to be related:

  revert "squashfs: harden sanity check in squashfs_read_xattr_id_table"

  In addition to 5.4.0-149.166, it appears the same surviving patch was
  also pulled into the following Ubuntu kernel builds:

  5.15.0-72.79
  5.19.0-42.43

  
  Additional data from one of the problem machines:

  # lsb_release -rd
  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  # cat /proc/version_signature
  Ubuntu 5.4.0-150.167-generic 5.4.233

  Relevant lines from dmesg:

  [964961.979932] SQUASHFS error: squashfs_read_data failed to read block 
0x52ca3e42
  [964961.987247] SQUASHFS error: Unable to read data cache entry [52ca3e42]
  [964961.993872] SQUASHFS error: Unable to read page, block 52ca3e42, size d674
  [1051130.734432] SQUASHFS error: squashfs_read_data failed to read block 
0xdd6d9c3
  [1100614.200893] SQUASHFS error: squashfs_read_data failed to read block 
0x239673b7
  [1100614.208305] SQUASHFS error: Unable to read data cache entry [239673b7]
  [1100614.215017] SQUASHFS error: Unable to read page, block 239673b7, size 
12fba
  [1100614.222170] SQUASHFS error: Unable to read data cache entry [239673b7]
  [1100614.228870] SQUASHFS error: Unable to read page, block 239673b7, size 
12fba
  [1100614.236007] SQUASHFS error: Unable to read data cache entry [239673b7]
  [1100614.242711] SQUASHFS error: Unable to read page, block 239673b7, size 
12fba
  [1100634.392881] SQUASHFS error: squashfs_read_data failed to read block 
0x1746ee61
  [1100634.400287] SQUASHFS error: Unable to read data cache entry [1746ee61]
  [1100634.406994] SQUASHFS error: Unable to read page, block 1746ee61, size 
111f3
  [1100634.414163] SQUASHFS error: Unable to read data cache entry [1746ee61]
  [1100634.420867] SQUASHFS error: Unable to read page, block 1746ee61, size 
111f3
  [1100634.428044] SQUASHFS error: Unable to read data cache entry [1746ee61]
  [1100634.434757] SQUASHFS error: Unable to read page, block 1746ee61, size 
111f3
  [1100634.647016] SQUASHFS error: squashfs_read_data failed to read block 
0x3afd7129

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


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

[Kernel-packages] [Bug 2017444] Re: Computer with Intel Atom CPU will not boot with Kernel 6.2.0-20

2023-06-14 Thread Jan Saarinen

** 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2017444

Title:
  Computer with Intel Atom CPU will  not boot with Kernel 6.2.0-20

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Invalid

Bug description:
  == SRU Justification ==
  [Impact]
  Some Atom based system cannot boot on kernel 6.2 because of atomisp
  driver.

  [Fix]
  Disable the driver via config, suggested by the driver dev.

  [Test]
  Users confirmed disabling the config works.
   
  [Where problems could occur]
  The ISP camera dever worked on Linux. So disabling it shouldn't
  introduce any surprise.

  
  == Original Bug Report ==
  Computers with Intel Atom CPU will not boot with Kernel 6.2.0-20 OR any other 
Kernel in 6.2 series or Kernel 6.3.0.

  This bug affects all Intel Atom CPU computers in all Linux
  distributions making impossible to install or boot to OS with kernel
  6.2 or higher.

  The bug is caused by Intel atomisp camera driver module which has
  firmware missing: shisp_2401a_v21.bin. Missing firmware causes a
  watchdog bug notice and Soft Lockup of boot sequence.

  NEW SOLUTION AND NOTICE TO UBUNTU KERNEL MAINTAINERS, April 29th:
  The following persons are in charge of atomisp kernel development:

  Hans de Goede  (maintainer:STAGING - ATOMISP DRIVER)
  Mauro Carvalho Chehab  (maintainer:STAGING - ATOMISP 
DRIVER)
  Sakari Ailus  (reviewer:STAGING - ATOMISP 
DRIVER)
  Greg Kroah-Hartman  (supporter:STAGING SUBSYSTEM)
  linux-me...@vger.kernel.org (open list:STAGING - ATOMISP DRIVER)
  linux-stag...@lists.linux.dev (open list:STAGING SUBSYSTEM)
  linux-ker...@vger.kernel.org (open list)

  April 29th Hans de Goede adviced me personally(
  https://github.com/linux-surface/linux-surface/issues/1095 ), that
  atomisp driver is still in development and should be disabled. By
  disabling driver he meant disabling atomisp modules in kernel.

  OLD SOLUTION FOR THIS BUG:

  Copying (installing) firmware shisp_2401a0_v21.bin from:

  https://github.com/intel-aero/meta-intel-aero-
  base/blob/master/recipes-kernel/linux/linux-yocto/shisp_2401a0_v21.bin

  to /lib/firmware will solve the bug (partially - it still gives error
  messages - but at least the computer boots).**

  (dmesg.log with shisp-file with kernel 6.2.0-06 and 6.3.0-06 as
  attachments 9. and 10.)

  (Another solution - which Manjaro kernel maintainer did - was to
  disable atomisp and related modules).

  Afterwards Intel Atom CPU computer will be able to boot with kernel
  6.2.

  DMESG.LOG OF KUBUNTU 23.04 LIVE USB AND MORE INFORMATION IN:
  https://askubuntu.com/questions/1464926/not-able-to-boot-
  kubuntu-23-04-with-kernel-6-2-and-intel-atom-cpu

  The last stable Ubuntu Kernel Intel Atom CPU computer will boot with
  is 6.1.25.

  This bug was already in 5.19, as you can see from dmesg.logs. It
  appears that atomisp failes to launch in both 5.19.0-40 and 6.1.25 but
  still the computer boots.

  This bug is also reported in Manjaro ( " https://github.com/linux-
  surface/linux-surface/issues/1095 ")and Arch Linux ("
  https://bbs.archlinux.org/viewtopic.php?id=283920 ") so it is not
  limited to Ubuntu Kernels.

  This bug has already been reported for Ubuntu 23.04 Beta in Ubuntu
  bugtracking system (" https://www.mail-archive.com/kernel-
  packa...@lists.launchpad.net/msg501664.html ") with Bug number
  #2015794.

  Attachments:
  1. Picture of stuck boot sequence of HP x2 210 G2 with Intel Atom CPU trying 
to boot in to Kubuntu 23.04 with Kernel 6.2.0-20.

  2. dmesg.log of the computer with Ubuntu Kernel 6.1.25.
  3. xsession-errors of the computer with Ubuntu Kernel 6.1.25.
  4. dmesg.log of the computer with Ubuntu Kernel 5.19.0-40.
  5. Video of boot sequence with Kernel 6.2.0-20.
  6. uname-a.log of Kernel 6.1.25.
  7. lspci-vvnn.log of Kernel 6.1.25.
  8. version.log of Kernel 5.19.0-40.
  9. dmesg.log with shisp-file with ubuntu kernel 6.2.0-06.**
  10. dmesg.log with shisp-file with ubuntu kernel 6.3.0-06**

  P.S. The apport-collect data is from Kernel 5.19.0-40.
  P.S.P.S I had difficulty determining Tags so they are to be changed by you.

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


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

[Kernel-packages] [Bug 2023925] [NEW] SQUASHFS error: squashfs_read_data failed to read block

2023-06-14 Thread Chris Read

Public bug reported:

We've had system relying on reading data from squashfs that's been
stable for a number of years. We've recently noticed that when running
on machines that include the patch set from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015511 that we
start to see error messages of the following shape:

SQUASHFS error: squashfs_read_data failed to read block

Machines showing the problem are all running kernel 5.4.0-150-generic

Machines NOT having any problems with the SAME workloads are running a
mix of the following kernels:

5.15.0-52-generic
5.15.0-53-generic
5.4.0-100-generic
5.4.0-104-generic
5.4.0-105-generic
5.4.0-125-generic
5.4.0-137-generic
5.4.0-147-generic

I'm not able to reproduce the failure on demand.

What is suspicious to me from that change set is that the following 2
patches are applied:

squashfs: harden sanity check in squashfs_read_xattr_id_table
Squashfs: fix handling and sanity checking of xattr_ids count

and then only 1 of them is reverted, although the patches in question
appear to be related:

revert "squashfs: harden sanity check in squashfs_read_xattr_id_table"

In addition to 5.4.0-149.166, it appears the same surviving patch was
also pulled into the following Ubuntu kernel builds:

5.15.0-72.79
5.19.0-42.43


Additional data from one of the problem machines:

# lsb_release -rd
Description:Ubuntu 20.04.6 LTS
Release:20.04

# cat /proc/version_signature
Ubuntu 5.4.0-150.167-generic 5.4.233

Relevant lines from dmesg:

[964961.979932] SQUASHFS error: squashfs_read_data failed to read block 
0x52ca3e42
[964961.987247] SQUASHFS error: Unable to read data cache entry [52ca3e42]
[964961.993872] SQUASHFS error: Unable to read page, block 52ca3e42, size d674
[1051130.734432] SQUASHFS error: squashfs_read_data failed to read block 
0xdd6d9c3
[1100614.200893] SQUASHFS error: squashfs_read_data failed to read block 
0x239673b7
[1100614.208305] SQUASHFS error: Unable to read data cache entry [239673b7]
[1100614.215017] SQUASHFS error: Unable to read page, block 239673b7, size 12fba
[1100614.222170] SQUASHFS error: Unable to read data cache entry [239673b7]
[1100614.228870] SQUASHFS error: Unable to read page, block 239673b7, size 12fba
[1100614.236007] SQUASHFS error: Unable to read data cache entry [239673b7]
[1100614.242711] SQUASHFS error: Unable to read page, block 239673b7, size 12fba
[1100634.392881] SQUASHFS error: squashfs_read_data failed to read block 
0x1746ee61
[1100634.400287] SQUASHFS error: Unable to read data cache entry [1746ee61]
[1100634.406994] SQUASHFS error: Unable to read page, block 1746ee61, size 111f3
[1100634.414163] SQUASHFS error: Unable to read data cache entry [1746ee61]
[1100634.420867] SQUASHFS error: Unable to read page, block 1746ee61, size 111f3
[1100634.428044] SQUASHFS error: Unable to read data cache entry [1746ee61]
[1100634.434757] SQUASHFS error: Unable to read page, block 1746ee61, size 111f3
[1100634.647016] SQUASHFS error: squashfs_read_data failed to read block 
0x3afd7129

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

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

Title:
  SQUASHFS error: squashfs_read_data failed to read block

Status in linux package in Ubuntu:
  New

Bug description:
  We've had system relying on reading data from squashfs that's been
  stable for a number of years. We've recently noticed that when running
  on machines that include the patch set from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015511 that we
  start to see error messages of the following shape:

  SQUASHFS error: squashfs_read_data failed to read block

  Machines showing the problem are all running kernel 5.4.0-150-generic

  Machines NOT having any problems with the SAME workloads are running a
  mix of the following kernels:

  5.15.0-52-generic
  5.15.0-53-generic
  5.4.0-100-generic
  5.4.0-104-generic
  5.4.0-105-generic
  5.4.0-125-generic
  5.4.0-137-generic
  5.4.0-147-generic

  I'm not able to reproduce the failure on demand.

  What is suspicious to me from that change set is that the following 2
  patches are applied:

  squashfs: harden sanity check in squashfs_read_xattr_id_table
  Squashfs: fix handling and sanity checking of xattr_ids count

  and then only 1 of them is reverted, although the patches in question
  appear to be related:

  revert "squashfs: harden sanity check in squashfs_read_xattr_id_table"

  In addition to 5.4.0-149.166, it appears the same surviving patch was
  also pulled into the following Ubuntu kernel builds:

  5.15.0-72.79
  5.19.0-42.43

  
  Additional data from one of the problem machines:

  # lsb_release -rd
  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  # cat /proc/version_signature
  Ubuntu 5.4.0-150.167-generic 5.4.233

  Relevant lines from dmesg:

  [964961.979932] SQUASHFS error:

[Kernel-packages] [Bug 2023920] Re: cheese doesn't open after upgrade to 22.04

2023-06-14 Thread themusicgod1

how did this get assigned to "linux"? might be an apport bug

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

Title:
  cheese doesn't open after upgrade to 22.04

Status in cheese package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  current behaviour: when 'cheese' is run either via commandline or by
  search, either with -f or without, with webcam plugged in or not, it
  fails to bring up a cheese window

  this is what id displayed on the console:
  themusicgod1@eva1:~$ cheese -f

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  expected behavior: cheese should load as it did in 20.04

  what should happen: cheese runs

  ubuntu: 22.04 LTS
  Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion
  themusicgod1@eva1:~$ apt-cache policy cheese
  cheese:
Installed: 41.1-1build1
Candidate: 41.1-1build1
Version table:
   *** 41.1-1build1 500
  500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome 42.5
  windowing system: wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 13:40:09 2023
  InstallationDate: Installed on 2017-04-18 (2248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Kernel-packages] [Bug 2018979] Re: Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic, Lunar

2023-06-14 Thread Launchpad Bug Tracker

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.116.04-0ubuntu0.22.10.1

---
nvidia-graphics-drivers-525 (525.116.04-0ubuntu0.22.10.1) kinetic; 
urgency=medium

  * New upstream release (LP: #2018979).

 -- Alberto Milone   Thu, 11 May 2023
09:16:49 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic,
  Lunar

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2018979] Re: Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic, Lunar

2023-06-14 Thread Launchpad Bug Tracker

This bug was fixed in the package nvidia-graphics-drivers-525 -
525.116.04-0ubuntu0.23.04.1

---
nvidia-graphics-drivers-525 (525.116.04-0ubuntu0.23.04.1) lunar; urgency=medium

  * New upstream release (LP: #2018979).

 -- Alberto Milone   Tue, 09 May 2023
08:44:37 +

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Lunar)
   Status: In Progress => Fix Released

** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic)
   Status: In Progress => Fix Released

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

Title:
  Update the 525 UDA NVIDIA driver series in Bionic, Focal, and Kinetic,
  Lunar

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Jammy:
  In Progress
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Fix Released
Status in nvidia-graphics-drivers-525 source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

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


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

[Kernel-packages] [Bug 2023920] Re: cheese doesn't open after upgrade to 22.04

2023-06-14 Thread themusicgod1

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

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

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

Title:
  cheese doesn't open after upgrade to 22.04

Status in cheese package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  current behaviour: when 'cheese' is run either via commandline or by
  search, either with -f or without, with webcam plugged in or not, it
  fails to bring up a cheese window

  this is what id displayed on the console:
  themusicgod1@eva1:~$ cheese -f

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  expected behavior: cheese should load as it did in 20.04

  what should happen: cheese runs

  ubuntu: 22.04 LTS
  Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion
  themusicgod1@eva1:~$ apt-cache policy cheese
  cheese:
Installed: 41.1-1build1
Candidate: 41.1-1build1
Version table:
   *** 41.1-1build1 500
  500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome 42.5
  windowing system: wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  Uname: Linux 6.0.7-gnulibre-squashfix x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 13:40:09 2023
  InstallationDate: Installed on 2017-04-18 (2248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7994
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago)
  dmi.bios.date: 12/16/2016
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.80
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M GAMING (MS-7994)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7994
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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


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

[Kernel-packages] [Bug 2023920] [NEW] cheese doesn't open after upgrade to 22.04

2023-06-14 Thread themusicgod1

Public bug reported:

current behaviour: when 'cheese' is run either via commandline or by
search, either with -f or without, with webcam plugged in or not, it
fails to bring up a cheese window

this is what id displayed on the console:
themusicgod1@eva1:~$ cheese -f

** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
'image-loading' not present in theme Yaru

expected behavior: cheese should load as it did in 20.04

what should happen: cheese runs

ubuntu: 22.04 LTS
Bus 001 Device 005: ID 046d:08c1 Logitech, Inc. QuickCam Fusion
themusicgod1@eva1:~$ apt-cache policy cheese
cheese:
  Installed: 41.1-1build1
  Candidate: 41.1-1build1
  Version table:
 *** 41.1-1build1 500
500 http://muug.ca/mirror/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
gnome 42.5
windowing system: wayland

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cheese 41.1-1build1
Uname: Linux 6.0.7-gnulibre-squashfix x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 13:40:09 2023
InstallationDate: Installed on 2017-04-18 (2248 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
RelatedPackageVersions:
 cheese41.1-1build1
 cheese-common 41.1-1build1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2023-06-14 (0 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404

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

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


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

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

Title:
  cheese doesn't open after upgrade to 22.04

Status in cheese package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  current behaviour: when 'cheese' is run either via commandline or by
  search, either with -f or without, with webcam plugged in or not, it
  fails to bring up a cheese window

  this is what id displayed on the console:
  themusicgod1@eva1:~$ cheese -f

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.833: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834: Couldn't load icon: Icon
  'image-loading' not present in theme Yaru

  ** (cheese:9307): WARNING **: 13:42:43.834:

[Kernel-packages] [Bug 2023042] Re: "couldn't communicate with the NVIDIA driver" when installing open dkms and LRM drivers concurrently

2023-06-14 Thread Francis Ginther

I've found a flaw in the test script in which it was installing the
wrong LRM modules for the running kernel. It was installing the generic
modules for a gcp kernel. Once I corrected this to install the gcp
modules, it now passes.

Attached are the logs with the addition of `lsmod` and `modinfo nvidia`

I think this can now be closed as a test error.

** Attachment added: "lunar-525-open-to-lrm-PASSED.txt"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2023042/+attachment/5679750/+files/lunar-525-open-to-lrm-PASSED.txt

** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
   Status: New => Invalid

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

Title:
  "couldn't communicate with the NVIDIA driver" when installing open
  dkms and LRM drivers concurrently

Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Invalid

Bug description:
  Installing "nvidia-driver-525-open" followed by "nvidia-headless-no-
  dkms-525 linux-modules-nvidia-525-gcp nvidia-utils-525" led to a
  system which complained about a "Driver/library version mismatch".
  Specifically what was done is:

  Deploy a clean google VM with:

  gcloud compute instances create fginther-kinetic-gpgpu-525 --image-
  project ubuntu-os-cloud --image-family ubuntu-2210-amd64 --machine-
  type n1-standard-4 --boot-disk-size=32GB --accelerator type=nvidia-
  tesla-t4,count=1 --maintenance-policy TERMINATE --restart-on-failure

  Enable kinetic-proposed (this was done with the
  525.116.04-0ubuntu0.22.10.1 driver package).

  Install the 525-open driver first:

  apt-get install -y nvidia-driver-525-open

  Then install the proprietary driver:

  apt-get install nvidia-headless-no-dkms-525 linux-modules-
  nvidia-525-gcp nvidia-utils-525

  After rebooting, "nvidia-smi" complained of the driver/library
  mismatch:

  ubuntu@fginther-kinetic-gpgpu-525:~$ nvidia-smi
  NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. 
Make sure that the latest NVIDIA driver is installed and running.

  The /var/log/apt/history.log is attached which details the packages
  installed and removed.

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


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

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

Title:
  Different colors in image since kernel 6.2.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Software in Ubuntu shows two different types of colors on the same
  image depending of the software you use. Let's call both types: pale
  and saturated, because of how they look like.

  Since kernel 6.2.0 pale colors are displayed in RawTherapee, Darktable, Gimp, 
ImageMagic.
  Saturated colors are displayed in Chromium, Chrome, gThumb, ImageViewr, 
Firefox.

  When I switched to kernel 5.19.0 everything looked the same, in every
  software (pale version from 6.2.0).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  as 6048 F wireplumber
   /dev/snd/controlC1:  as 6048 F wireplumber
   /dev/snd/controlC0:  as 6048 F wireplumber
   /dev/snd/seq:as 6044 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 20:22:59 2023
  InstallationDate: Installed on 2020-12-06 (920 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20T6000TPB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (51 days ago)
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET44W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6000TPB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET44W(1.20):bd08/08/2022:br1.20:efr1.20:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T6000TPB
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2023910] Re: Different colors in image since kernel 6.2.0

2023-06-14 Thread as

** Attachment added: "Test image which I used"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023910/+attachment/5679738/+files/P1093533_01.png

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

Title:
  Different colors in image since kernel 6.2.0

Status in linux package in Ubuntu:
  New

Bug description:
  Software in Ubuntu shows two different types of colors on the same
  image depending of the software you use. Let's call both types: pale
  and saturated, because of how they look like.

  Since kernel 6.2.0 pale colors are displayed in RawTherapee, Darktable, Gimp, 
ImageMagic.
  Saturated colors are displayed in Chromium, Chrome, gThumb, ImageViewr, 
Firefox.

  When I switched to kernel 5.19.0 everything looked the same, in every
  software (pale version from 6.2.0).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  as 6048 F wireplumber
   /dev/snd/controlC1:  as 6048 F wireplumber
   /dev/snd/controlC0:  as 6048 F wireplumber
   /dev/snd/seq:as 6044 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 20:22:59 2023
  InstallationDate: Installed on 2020-12-06 (920 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20T6000TPB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (51 days ago)
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET44W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6000TPB
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET44W(1.20):bd08/08/2022:br1.20:efr1.20:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20T6000TPB
  dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2023910] [NEW] Different colors in image since kernel 6.2.0

2023-06-14 Thread as

Public bug reported:

Software in Ubuntu shows two different types of colors on the same image
depending of the software you use. Let's call both types: pale and
saturated, because of how they look like.

Since kernel 6.2.0 pale colors are displayed in RawTherapee, Darktable, Gimp, 
ImageMagic.
Saturated colors are displayed in Chromium, Chrome, gThumb, ImageViewr, Firefox.

When I switched to kernel 5.19.0 everything looked the same, in every
software (pale version from 6.2.0).

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  as 6048 F wireplumber
 /dev/snd/controlC1:  as 6048 F wireplumber
 /dev/snd/controlC0:  as 6048 F wireplumber
 /dev/snd/seq:as 6044 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 14 20:22:59 2023
InstallationDate: Installed on 2020-12-06 (920 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 20T6000TPB
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-20-generic N/A
 linux-backports-modules-6.2.0-20-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
SourcePackage: linux
UpgradeStatus: Upgraded to lunar on 2023-04-23 (51 days ago)
dmi.bios.date: 08/08/2022
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: R1AET44W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20T6000TPB
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrR1AET44W(1.20):bd08/08/2022:br1.20:efr1.20:svnLENOVO:pn20T6000TPB:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000TPB:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20T6000TPB
dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug lunar

** Attachment added: "Screenshot from two different types of colors"
   
https://bugs.launchpad.net/bugs/2023910/+attachment/5679718/+files/linux%20colors%20bug%206.2.0.png

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

Title:
  Different colors in image since kernel 6.2.0

Status in linux package in Ubuntu:
  New

Bug description:
  Software in Ubuntu shows two different types of colors on the same
  image depending of the software you use. Let's call both types: pale
  and saturated, because of how they look like.

  Since kernel 6.2.0 pale colors are displayed in RawTherapee, Darktable, Gimp, 
ImageMagic.
  Saturated colors are displayed in Chromium, Chrome, gThumb, ImageViewr, 
Firefox.

  When I switched to kernel 5.19.0 everything looked the same, in every
  software (pale version from 6.2.0).

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  as 6048 F wireplumber
   /dev/snd/controlC1:  as 6048 F wireplumber
   /dev/snd/controlC0:  as 6048 F wireplumber
   /dev/snd/seq:as 6044 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 14 20:22:59 2023
  InstallationDate: Installed on 2020-12-06 (920 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20T6000TPB
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=a5796f3d-37a8-428b-aa28-c160ea77bc9b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (51 days ago)
  dmi.bios.date: 08/08/2022
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1AET44W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20T6000TPB
  dmi.board.vendor: LENOVO

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

2023-06-14 Thread Michael Reed

** Description changed:

  [Impact]
  
  Currently Ubuntu kernel has this kernel config disabled.
  But in some cases, Intel's Sapphire Rapids High Bandwith
  Memory (SPR-HBM) needs this option.
  
  Memory bandwidth has been a bottleneck of increasingly memory bound
  workloads. Sapphire Rapids plus HBM is specifically targeted to
  cater to these workloads, traditionally served using overprovisioning
  of memory devices.
  
  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]
   Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no 
fake NUMA, 2U fake NUMA and 4U fake NUMA).
  
  * 
https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html
  ** 
https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html
  
  An improvement to performance on a Sapphire Rapids CPU with HBM should
  be observed
  
  [Where problems could occur]
  
  The regression risk is low
  
  [Other Info]
  Jammy
- 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2
  
  Kinetic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic
  
  Lunar
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2

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

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

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

Bug description:
  [Impact]

  Currently Ubuntu kernel has this kernel config disabled.
  But in some cases, Intel's Sapphire Rapids High Bandwith
  Memory (SPR-HBM) needs this option.

  Memory bandwidth has been a bottleneck of increasingly memory bound
  workloads. Sapphire Rapids plus HBM is specifically targeted to
  cater to these workloads, traditionally served using overprovisioning
  of memory devices.

  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]
   Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no 
fake NUMA, 2U fake NUMA and 4U fake NUMA).

  * 
https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html
  ** 
https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html

  An improvement to performance on a Sapphire Rapids CPU with HBM should
  be observed

  [Where problems could occur]

  The regression risk is low

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

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

  Lunar
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2

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 2023691] 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 2023691

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

Title:
  Unable to boot into linux image 5.15 in Ubuntu 22.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot linux-image-5.15.0-73-generic on Ubuntu 22.04.  The
  attached image shows what happens.

  * The initial grub boot screen appears, "Advanced options for Ubuntu" is 
selected
  * On the next screen, "Ubuntu. with Linux 5.15.0-73-generic" is selected
  * The next screen shows that initial ramdisk is being loaded for Linux 
5.15.0-73-generic
  * The last screen shows the boot has failed, and the user is dropped into the 
ramdisk with an (initramfs) command prompt.

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


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

All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1088.85) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

acpi-call/unknown (arm64)
adv-17v35x/unknown (arm64)
asic0x/unknown (arm64)
bbswitch/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
dm-writeboost/unknown (arm64)
dpdk/unknown (arm64)
fwts/unknown (arm64)
glibc/2.27-3ubuntu1.6 (armhf)
ktap/unknown (arm64)
langford/unknown (arm64)
linux-raspi-5.4/blacklisted (arm64, armhf)
lttng-modules/unknown (arm64)
lxc/3.0.3-0ubuntu1~18.04.3 (arm64)
lxd/unknown (arm64)
nat-rtsp/unknown (arm64)
rtl8812au/unknown (arm64)
spl-linux/unknown (arm64)
systemd/unknown (arm64)
v4l2loopback/unknown (arm64)
west-chamber/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
xtables-addons/unknown (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi-5.4

[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 2023691] Re: Unable to boot into linux image 5.15 in Ubuntu 22.04

2023-06-14 Thread Paul White

** Tags added: jammy

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

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

Title:
  Unable to boot into linux image 5.15 in Ubuntu 22.04

Status in linux package in Ubuntu:
  New

Bug description:
  I cannot boot linux-image-5.15.0-73-generic on Ubuntu 22.04.  The
  attached image shows what happens.

  * The initial grub boot screen appears, "Advanced options for Ubuntu" is 
selected
  * On the next screen, "Ubuntu. with Linux 5.15.0-73-generic" is selected
  * The next screen shows that initial ramdisk is being loaded for Linux 
5.15.0-73-generic
  * The last screen shows the boot has failed, and the user is dropped into the 
ramdisk with an (initramfs) command prompt.

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


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

[Kernel-packages] [Bug 2023674] Re: E810 Ubuntu 20.04 LTS - Crash - Device is in unrecoverable state

2023-06-14 Thread A. Saber Shenouda

I can't run this command right now as it's currently in production. Will
try to run it soon.

System is a Dell R7515, AMD Epyc 7543P, 256GB RAM

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

Title:
  E810 Ubuntu 20.04 LTS - Crash - Device is in unrecoverable state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  On intensive load, the interface goes in "unrecoverable state". We
  already using the latest firmware from Dell
  https://www.dell.com/support/home/en-
  ca/drivers/driversdetails?driverid=25ffj which is supposed to prevent
  that issue

  "- Resolved an issue with E810 adapters where the queues are not freed up 
properly and causes
  kernel issues under heavy traffic. {208689}"

  
  Here are the syslog when the bug appears:

  
  @timestamptypemessage program
  2023-04-11T23:34:01.406Z  syslog  [6833005.040087] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:34:01.406Z  syslog  [6833005.040086] ice :c4:00.3 
ens3f3: tx_timeout recovery level 911, hung_queue 22  kernel
  2023-04-11T23:34:01.406Z  syslog  [6833005.040085] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924350] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924349] ice :c4:00.3 
ens3f3: tx_timeout recovery level 910, hung_queue 22  kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924347] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936862] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936864] ice :c4:00.3 
ens3f3: tx_timeout recovery level 909, hung_queue 22  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936864] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049162] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049164] ice :c4:00.3 
ens3f3: tx_timeout recovery level 908, hung_queue 22  kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049165] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:35.323Z  syslog  [6832978.929427] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:35.322Z  syslog  [6832978.929426] ice :c4:00.3 
ens3f3: tx_timeout recovery level 907, hung_queue 22  kernel
  2023-04-11T23:33:35.322Z  syslog  [6832978.929424] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:29.487Z  syslog  [6832973.041730] ice :c4:00.3 
ens3f3: tx_timeout recovery level 906, hung_queue 22  kernel
  2023-04-11T23:33:29.487Z  syslog  [6832973.041731] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:29.486Z  syslog  [6832973.041729] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:24.327Z  syslog  [6832967.921995] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:24.326Z  syslog  [6832967.921993] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:24.326Z  syslog  [6832967.921994] ice :c4:00.3 
ens3f3: tx_timeout recovery level 905, hung_queue 22  kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942505] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942502] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942504] ice :c4:00.3 
ens3f3: tx_timeout recovery level 904, hung_queue 22  kernel
  2023-04-11T23:33:08.414Z  syslog  [6832952.050807] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:08.414Z  syslog  [6832952.050809] ice :c4:00.3 
ens3f3: tx_timeout recovery level 903, hung_queue 22  kernel
  2023-04-11T23:33:08.414Z

[Kernel-packages] [Bug 2023807] [NEW] Initialize linux-nvidia-tegra-igx with patch list from NVIDIA

Public bug reported:

[Impact]
This change reflects the creation and initialization of a new kernel, 
linux-nvidia-tegra-igx. This kernel will be initialized with the patches 
already in linux-nvidia-tegra, and be maintained as a sibling to 
linux-nvidia-tegra. A patch list containing patches required to enable the IGX 
platform has been provided by NVIDIA, and these patches have been integrated 
into the new kernel.

[Other Info]
The following patches are contained in the NVIDIA-provided list, but need 
backporting to v5.15.

8681e3663411 drm/simpledrm: Support the XB24/AB24 format
9abecb1d338c drm/format-helper: Support the XB24 format
9a10c7e6519b drm/simpledrm: Add support for system memory framebuffers
fa904b4cbc60 drm/simpledrm: Use struct iosys_map consistently

Hence, these will be addressed in a separate change.

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

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

Title:
  Initialize linux-nvidia-tegra-igx with patch list from NVIDIA

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

Bug description:
  [Impact]
  This change reflects the creation and initialization of a new kernel, 
linux-nvidia-tegra-igx. This kernel will be initialized with the patches 
already in linux-nvidia-tegra, and be maintained as a sibling to 
linux-nvidia-tegra. A patch list containing patches required to enable the IGX 
platform has been provided by NVIDIA, and these patches have been integrated 
into the new kernel.

  [Other Info]
  The following patches are contained in the NVIDIA-provided list, but need 
backporting to v5.15.

  8681e3663411 drm/simpledrm: Support the XB24/AB24 format
  9abecb1d338c drm/format-helper: Support the XB24 format
  9a10c7e6519b drm/simpledrm: Add support for system memory framebuffers
  fa904b4cbc60 drm/simpledrm: Use struct iosys_map consistently

  Hence, these will be addressed in a separate change.

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


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

[Kernel-packages] [Bug 2023313] Re: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"

2023-06-14 Thread Khaled El Mously

** Description changed:

  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from
- upstream 6.2 to the 5.19 (kinetic) gcp kernel
+ upstream 6.2 to the 5.19 gcp kernel
  
  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback
  
  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
  
  Impact:
   - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.
  
  Testing:
   - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD 
hardware.

** Description changed:

  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from
  upstream 6.2 to the 5.19 gcp kernel
  
  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback
  
  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
  
  Impact:
   - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.
  
  Testing:
-  - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD 
hardware.
+  - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD 
hardware.

** Description changed:

  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from
  upstream 6.2 to the 5.19 gcp kernel
  
  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback
  
  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
  
  Impact:
   - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.
  
  Testing:
   - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD 
hardware.
+ 
+ 
+ Regression potential:
+  - The changes are limited to the AMD iommu driver. Regression potential 
could impact virtualization on AMD hardware. Risk is considered low as the 
changes are limited and apply cleanly from upstream.

** Description changed:

  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from
  upstream 6.2 to the 5.19 gcp kernel
  
  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback
  
  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
  
  Impact:
   - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.
  
  Testing:
   - Boot-tested the changes in SEV, SEV-SNP and non-SEV environments on AMD 
hardware.
  
- 
  Regression potential:
-  - The changes are limited to the AMD iommu driver. Regression potential 
could impact virtualization on AMD hardware. Risk is considered low as the 
changes are limited and apply cleanly from upstream.
+  - The changes are limited to the AMD iommu driver. Regression potential 
could impact virtualization on AMD hardware. Risk is considered low as the 
changes are limited and apply cleanly from upstream. The requested patch is 
from 6.2 and there have been no follow-up fixes since.

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

Title:
  gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops
  callback support"

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Kinetic:
  In Progress

Bug description:
  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
  from upstream 6.2 to the 5.19 gcp kernel

  The following two patches are

[Kernel-packages] [Bug 2020606] Re: net: openvswitch: fix race on port output

2023-06-14 Thread Bartlomiej Zolnierkiewicz

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

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

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

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

Title:
  net: openvswitch: fix race on port output

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  New
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  fix race on port output

  * Explain the bug(s)

  there is a race condition on port output

  * brief explanation of fixes

  We found that upstream linux has the same issue and fix

  commit 066b86787fa3d97b7aefb5ac0a99a22dad2d15f8
  Author: Felix Huettner 
  Date:   Wed Apr 5 07:53:41 2023 +

  net: openvswitch: fix race on port output

  assume the following setup on a single machine:
  1. An openvswitch instance with one bridge and default flows
  2. two network namespaces "server" and "client"
  3. two ovs interfaces "server" and "client" on the bridge
  4. for each ovs interface a veth pair with a matching name and 32 rx and
 tx queues
  5. move the ends of the veth pairs to the respective network namespaces
  6. assign ip addresses to each of the veth ends in the namespaces (needs
 to be the same subnet)
  7. start some http server on the server network namespace
  8. test if a client in the client namespace can reach the http server
  ...
  Fixes: 7f8a436eaa2c ("openvswitch: Add conntrack action")
  Co-developed-by: Luca Czesla 
  Signed-off-by: Luca Czesla 
  Signed-off-by: Felix Huettner 
  Reviewed-by: Eric Dumazet 
  Reviewed-by: Simon Horman 
  Link: https://lore.kernel.org/r/ZC0pBXBAgh7c76CA@kernel-bug-kernel-bug
  Signed-off-by: Jakub Kicinski 

  * How to test
  After configuring QoS on BF-3:
  Disable all priorities
  Set priorities [0, 0, 0, 0, 0, 0, 0, 0]
  Remove all policies
  Remove all traffic classes
  Add policy (policy_name=ND_traffic, traffic_type=RDMA, priority=5, 
port=2, dscp=None)
  Add policy (policy_name=TCP_traffic, traffic_type=TCP, priority=4, 
port=26000, dscp=None)
  Add traffic class two prio TC with prio_list=[5, 4], min_bw=76, algorithm=ETS
  Enable QOS on adapter SLOT 5 Port 1
  Restart driver (detach VFs -> restart with devcon -> attach VFs)

  BF-3 sometimes stops responding. need to run it multiple times!

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


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

[Kernel-packages] [Bug 2022387] Re: mlxbf-gige: Fix intermittent no ip issue

2023-06-14 Thread Bartlomiej Zolnierkiewicz

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

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

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

Title:
  mlxbf-gige: Fix intermittent no ip issue

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  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.

  [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/2022387/+subscriptions


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

[Kernel-packages] [Bug 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors

2023-06-14 Thread Bartlomiej Zolnierkiewicz

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

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

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

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

Title:
  mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx
  descriptors

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  New
Status in linux-bluefield source package in Jammy:
  New

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to avoid potential tmfifo console stuck when network 
interface is down or receiving oversized packets.

  [Fix]
  Drop the Rx packets in the above cases. Since tmfifo is shared resource for 
both console and networking. Dropping such network packets can continue to 
process the fifo and avoid console stuck.

  [Test Case]
  Same functionality and testing as on BlueField-1/2/3. No functionality change.
  Add negative tests:
  1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim 
console doesn't stuck.
  2. Config MTU to 4000 on rshim host and send oversized packet with command 
'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck.

  [Regression Potential]
  Same behavior from user perspective.

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


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

[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part

2023-06-14 Thread Frank Heimes

Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-June/thread.html#140405
changing status to 'In Progress'.

A test kernel was build in PPA and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1853306

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => 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/1853306

Title:
  [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x -
  kernel part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * Currently the PCI passthrough implementation for s390x is based on
 intercepting PCI I/O instructions, which leads to a reduced I/O performance
 compared to the execution of PCI instructions directly in LPAR.

   * Hence users may face I/O bottlenecks when using PCI devices in passthrough
 mode based on the current implementation.

   * For avoiding this and to improve performance, the interpretive execution
 of the PCI store and PCI load instructions get enabled.

   * A further improvement is achieved by enabling the 
Adapter-Event-Notification
 Interpretation (AENI).

   * Since LTS releases are the main focus for stable and long running KVM
 workloads, it is highly desired to get this backported to the jammy kernel
 (and because the next LTS is still some time away).

  [ Test Plan ]

   * Have an Ubuntu Server 22.04 installation on LPAR,
 that is able to access (ideally multiple) PCI devices,
 like RoCE Express (network) or NVMe disks.

   * Setup KVM and pass through (ideally multiple) of these PCI devices
 (that are otherwise unused on the KVM host).

   * Generate IO load on these passed through PCI devices,
 for example with stress-ng, using class network and/or device
 and/or io stressors.

   * This PR also introduces a new kernel config option 'VFIO_PCI_ZDEV_KVM'
 that allows to enable support for the s390x-specific extensions and
 enhancements to KVM passthrough, such as interpretive execution of zPCI
 instructions and is with this PR and got enabled.

   * The qemu autopkgtest (also needed due to LP#1853307) will be a got fit
 to identify any potential regressions, also in the kvm kernel area.

   * zPCI passthrough related test will be done by IBM.

  
  [ Where problems could occur ]

   * The modifications do not change the way users or APIs have to make
 use of PCI passthrough, only the internal implementation got modified.

   * The vast majority of the code changes/or additional code is s390x-specific,
 under arch/s390 and drivers/s390.

   * However there is also common code touched:
 
   * 'kvm: use kvfree() in kvm_arch_free_vm()' touches
 arch/arm64/include/asm/kvm_host.h, arch/arm64/kvm/arm.c,
 arch/x86/include/asm/kvm_host.h, arch/x86/kvm/x86.c,
 include/linux/kvm_host.h switches in kvm_arch_free_vm() from kfree() to
 kvfree() allowing to use the common variant, which is upstream since v5.16
 and with that well established.

   * And 'vfio-pci/zdev: add open/close device hooks' touches
 drivers/vfio/pci/vfio_pci_core.c and drivers/vfio/pci/vfio_pci_zdev.c
 include/linux/vfio_pci_core.h add now code to introduce device hooks.
 It's upstream since kernel 6.0.

   * 'KVM: s390: pci: provide routines for en-/disabling interrupt forwarding'
 expands a single #if statement in include/linux/sched/user.h.

   * 'KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices'
 adds s390x specific KVM_S390_ZPCI_OP and it's definition to
 include/uapi/linux/kvm.h.

   * And 'vfio-pci/zdev: different maxstbl for interpreted devices' and
 'vfio-pci/zdev: add function handle to clp base capability' expand
 s390x-specific (aka z-specific aka zdev) device structs in
 include/uapi/linux/vfio_zdev.h.

   * This shows that the vast majority of modifications are s390x specific,
 even in most of the common code files.

   * The remaining modifications in the (generally) common code files are
 related to the newly introduced kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'
 and documentation.

   * The s390x changes are more significant, and could not only harm
 passthrough itself for zPCI devices, but also KVM virtualization in 
general.

   * In addition to these kernel changes, qemu modifications  are needed
 as well (that are addressed at LP#1853307), this modified kernel
 must be tested in combination with the updated qemu package.
 - The qemu autopkgtest will be a

[Kernel-packages] [Bug 2023313] Re: gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"

2023-06-14 Thread Khaled El Mously

** Description changed:

  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support" from
  upstream 6.2 to the 5.19 (kinetic) gcp kernel
  
  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback
  
  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view
  
  Impact:
-  - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that this also has a security side-effect which they are interested 
in.
+  - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.
  
  Testing:
   - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD 
hardware.

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

Title:
  gcp: backport "iommu/amd: Add map/unmap_pages() iommu_domain_ops
  callback support"

Status in linux-gcp package in Ubuntu:
  In Progress
Status in linux-gcp source package in Kinetic:
  In Progress

Bug description:
  GCP is requesting the backport of the patch "6b080c4e815ceba3c08f
  iommu/amd: Add map/unmap_pages() iommu_domain_ops callback support"
  from upstream 6.2 to the 5.19 (kinetic) gcp kernel

  The following two patches are required for the backport:
   6b080c4e815ceba3c08ffa980c858595c07e7 iommu/amd/io-pgtable: Implement 
map_pages io_pgtable_ops callback
   251c4db699ca7b966db7e59e8663a231c96ba iommu/amd/io-pgtable: Implement 
unmap_pages io_pgtable_ops callback

  More info at
  https://canonical.lightning.force.com/lightning/r/Case/5008e0CjJJCAA3/view

  Impact:
   - This allows the AMD iommu driver to map/unmap multiple pages in one call. 
GCP states that these changes also have a security side-effect which they are 
interested in.

  Testing:
   - Boot-tested the changes in a gcp SEV and non-SEV environment on AMD 
hardware.

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


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

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

2023-06-14 Thread Tim Gardner

** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2021605

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

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

Bug description:
  [Impact]

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

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

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

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

  [Regression potential]

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

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


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

[Kernel-packages] [Bug 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part

2023-06-14 Thread Frank Heimes

** Description changed:

- The PCI Passthrough implementation is based on intercepting PCI I/O 
instructions which leads to a reduced I/O performance compared to execution of 
PCI instructions in LPAR. 
- For improved performance the interpretive execution of the PCI store and PCI 
load instructions get enabled. 
+ [ Impact ]
+ 
+  * Currently the PCI passthrough implementation for s390x is based on
+intercepting PCI I/O instructions, which leads to a reduced I/O performance
+compared to the execution of PCI instructions directly in LPAR.
+ 
+  * Hence users may face I/O bottlenecks when using PCI devices in passthrough
+mode based on the current implementation.
+ 
+  * For avoiding this and to improve performance, the interpretive execution
+of the PCI store and PCI load instructions get enabled.
+ 
+  * A further improvement is achieved by enabling the 
Adapter-Event-Notification
+Interpretation (AENI).
+ 
+  * Since LTS releases are the main focus for stable and long running KVM
+workloads, it is highly desired to get this backported to the jammy kernel
+(and because the next LTS is still some time away).
+ 
+ [ Test Plan ]
+ 
+  * Have an Ubuntu Server 22.04 installation on LPAR,
+that is able to access (ideally multiple) PCI devices,
+like RoCE Express (network) or NVMe disks.
+ 
+  * Setup KVM and pass through (ideally multiple) of these PCI devices
+(that are otherwise unused on the KVM host).
+ 
+  * Generate IO load on these passed through PCI devices,
+for example with stress-ng, using class network and/or device
+and/or io stressors.
+ 
+  * This PR also introduces a new kernel config option 'VFIO_PCI_ZDEV_KVM'
+that allows to enable support for the s390x-specific extensions and
+enhancements to KVM passthrough, such as interpretive execution of zPCI
+instructions and is with this PR and got enabled.
+ 
+  * The qemu autopkgtest (also needed due to LP#1853307) will be a got fit
+to identify any potential regressions, also in the kvm kernel area.
+ 
+  * zPCI passthrough related test will be done by IBM.
+ 
+ 
+ [ Where problems could occur ]
+ 
+  * The modifications do not change the way users or APIs have to make
+use of PCI passthrough, only the internal implementation got modified.
+ 
+  * The vast majority of the code changes/or additional code is s390x-specific,
+under arch/s390 and drivers/s390.
+ 
+  * However there is also common code touched:
+
+  * 'kvm: use kvfree() in kvm_arch_free_vm()' touches
+arch/arm64/include/asm/kvm_host.h, arch/arm64/kvm/arm.c,
+arch/x86/include/asm/kvm_host.h, arch/x86/kvm/x86.c,
+include/linux/kvm_host.h switches in kvm_arch_free_vm() from kfree() to
+kvfree() allowing to use the common variant, which is upstream since v5.16
+and with that well established.
+ 
+  * And 'vfio-pci/zdev: add open/close device hooks' touches
+drivers/vfio/pci/vfio_pci_core.c and drivers/vfio/pci/vfio_pci_zdev.c
+include/linux/vfio_pci_core.h add now code to introduce device hooks.
+It's upstream since kernel 6.0.
+ 
+  * 'KVM: s390: pci: provide routines for en-/disabling interrupt forwarding'
+expands a single #if statement in include/linux/sched/user.h.
+ 
+  * 'KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices'
+adds s390x specific KVM_S390_ZPCI_OP and it's definition to
+include/uapi/linux/kvm.h.
+ 
+  * And 'vfio-pci/zdev: different maxstbl for interpreted devices' and
+'vfio-pci/zdev: add function handle to clp base capability' expand
+s390x-specific (aka z-specific aka zdev) device structs in
+include/uapi/linux/vfio_zdev.h.
+ 
+  * This shows that the vast majority of modifications are s390x specific,
+even in most of the common code files.
+ 
+  * The remaining modifications in the (generally) common code files are
+related to the newly introduced kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM'
+and documentation.
+ 
+  * The s390x changes are more significant, and could not only harm
+passthrough itself for zPCI devices, but also KVM virtualization in 
general.
+ 
+  * In addition to these kernel changes, qemu modifications  are needed
+as well (that are addressed at LP#1853307), this modified kernel
+must be tested in combination with the updated qemu package.
+- The qemu autopkgtest will be a got fit to identify any regressions,
+also in the kernel.
+- In addition some passthrough related test will be done by IBM
+ 
+ __
+ 
+ The PCI Passthrough implementation is based on intercepting PCI I/O 
instructions which leads to a reduced I/O performance compared to execution of 
PCI instructions in LPAR.
+ For improved performance the interpretive execution of the PCI store and PCI 
load instructions get enabled.
  Further improvement is achieved by enabling the Adapter-Event-Notification

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to

[Kernel-packages] [Bug 2015741] Re: efivarfs:efivarfs.sh in ubuntu_kernel_selftests crash L-6.2 ARM64 node dazzle (rcu_preempt detected stalls)

As cypressyew mentioned above, dazzle is dead, so we can close and mark
this bug verified for lunar.

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

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

Title:
  efivarfs:efivarfs.sh in ubuntu_kernel_selftests crash L-6.2 ARM64 node
  dazzle (rcu_preempt detected stalls)

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Issue found on 6.2.0-20.20 ARM64 instances "dazzle" only.

  Looks like the efivarfs:efivarfs.sh will never finish properly and the
  whole test will be interrupted abnormally.

  Test log:
   Running 'make run_tests -C efivarfs TEST_PROGS=efivarfs.sh TEST_GEN_PROGS='' 
TEST_CUSTOM_PROGS='''
   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs'
   TAP version 13
   1..1
   # selftests: efivarfs: efivarfs.sh
   # 
   # running test_create
   # 
   Timer expired (5400 sec.), nuking pid 21170

  This issue can be found since 6.2.0-19.19

  This node was not tested with 6.2.0-18.18

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


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

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

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

Title:
  E810 Ubuntu 20.04 LTS - Crash - Device is in unrecoverable state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  On intensive load, the interface goes in "unrecoverable state". We
  already using the latest firmware from Dell
  https://www.dell.com/support/home/en-
  ca/drivers/driversdetails?driverid=25ffj which is supposed to prevent
  that issue

  "- Resolved an issue with E810 adapters where the queues are not freed up 
properly and causes
  kernel issues under heavy traffic. {208689}"

  
  Here are the syslog when the bug appears:

  
  @timestamptypemessage program
  2023-04-11T23:34:01.406Z  syslog  [6833005.040087] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:34:01.406Z  syslog  [6833005.040086] ice :c4:00.3 
ens3f3: tx_timeout recovery level 911, hung_queue 22  kernel
  2023-04-11T23:34:01.406Z  syslog  [6833005.040085] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924350] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924349] ice :c4:00.3 
ens3f3: tx_timeout recovery level 910, hung_queue 22  kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924347] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936862] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936864] ice :c4:00.3 
ens3f3: tx_timeout recovery level 909, hung_queue 22  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936864] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049162] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049164] ice :c4:00.3 
ens3f3: tx_timeout recovery level 908, hung_queue 22  kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049165] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:35.323Z  syslog  [6832978.929427] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:35.322Z  syslog  [6832978.929426] ice :c4:00.3 
ens3f3: tx_timeout recovery level 907, hung_queue 22  kernel
  2023-04-11T23:33:35.322Z  syslog  [6832978.929424] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:29.487Z  syslog  [6832973.041730] ice :c4:00.3 
ens3f3: tx_timeout recovery level 906, hung_queue 22  kernel
  2023-04-11T23:33:29.487Z  syslog  [6832973.041731] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:29.486Z  syslog  [6832973.041729] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:24.327Z  syslog  [6832967.921995] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:24.326Z  syslog  [6832967.921993] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:24.326Z  syslog  [6832967.921994] ice :c4:00.3 
ens3f3: tx_timeout recovery level 905, hung_queue 22  kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942505] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942502] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel

[Kernel-packages] [Bug 2023674] Re: E810 Ubuntu 20.04 LTS - Crash - Device is in unrecoverable state

2023-06-14 Thread Brian Murray

** Project changed: kernel => linux (Ubuntu)

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

Title:
  E810 Ubuntu 20.04 LTS - Crash - Device is in unrecoverable state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  On intensive load, the interface goes in "unrecoverable state". We
  already using the latest firmware from Dell
  https://www.dell.com/support/home/en-
  ca/drivers/driversdetails?driverid=25ffj which is supposed to prevent
  that issue

  "- Resolved an issue with E810 adapters where the queues are not freed up 
properly and causes
  kernel issues under heavy traffic. {208689}"

  
  Here are the syslog when the bug appears:

  
  @timestamptypemessage program
  2023-04-11T23:34:01.406Z  syslog  [6833005.040087] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:34:01.406Z  syslog  [6833005.040086] ice :c4:00.3 
ens3f3: tx_timeout recovery level 911, hung_queue 22  kernel
  2023-04-11T23:34:01.406Z  syslog  [6833005.040085] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924350] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924349] ice :c4:00.3 
ens3f3: tx_timeout recovery level 910, hung_queue 22  kernel
  2023-04-11T23:33:56.290Z  syslog  [6832999.924347] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936862] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936864] ice :c4:00.3 
ens3f3: tx_timeout recovery level 909, hung_queue 22  kernel
  2023-04-11T23:33:46.365Z  syslog  [6832989.936864] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049162] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049164] ice :c4:00.3 
ens3f3: tx_timeout recovery level 908, hung_queue 22  kernel
  2023-04-11T23:33:40.414Z  syslog  [6832984.049165] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:35.323Z  syslog  [6832978.929427] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:35.322Z  syslog  [6832978.929426] ice :c4:00.3 
ens3f3: tx_timeout recovery level 907, hung_queue 22  kernel
  2023-04-11T23:33:35.322Z  syslog  [6832978.929424] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:29.487Z  syslog  [6832973.041730] ice :c4:00.3 
ens3f3: tx_timeout recovery level 906, hung_queue 22  kernel
  2023-04-11T23:33:29.487Z  syslog  [6832973.041731] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:29.486Z  syslog  [6832973.041729] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:24.327Z  syslog  [6832967.921995] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:24.326Z  syslog  [6832967.921993] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:24.326Z  syslog  [6832967.921994] ice :c4:00.3 
ens3f3: tx_timeout recovery level 905, hung_queue 22  kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942505] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in unrecoverable state.   
kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942502] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:14.306Z  syslog  [6832957.942504] ice :c4:00.3 
ens3f3: tx_timeout recovery level 904, hung_queue 22  kernel
  2023-04-11T23:33:08.414Z  syslog  [6832952.050807] ice :c4:00.3 
ens3f3: tx_timeout: VSI_num: 15, Q 22, NTC: 0x8e, HW_HEAD: 0x8d, NTU: 0x78, 
INT: 0x1  kernel
  2023-04-11T23:33:08.414Z  syslog  [6832952.050809] ice :c4:00.3 
ens3f3: tx_timeout recovery level 903, hung_queue 22  kernel
  2023-04-11T23:33:08.414Z  syslog  [6832952.050810] ice :c4:00.3 
ens3f3: tx_timeout recovery unsuccessful, device is in

[Kernel-packages] [Bug 1690632] Re: SATA card SiL 3112 doesn't work well

2023-06-14 Thread psl

SIL3114 was working OK for some time (5 years?) but it failed today. I
replaced it with that old SIL3112 card and I see DMA errors, so this bug
was not fixed in the newer kernel. I replaced Ubuntu with Debian some
time ago (as Ubuntu do not support 32-bit anymore). This is my current
kernel and SIL3112 is still troublemaker...

Linux server 5.10.0-23-686-pae #1 SMP Debian 5.10.179-1 (2023-05-12)
i686 GNU/Linux

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

Title:
  SATA card SiL 3112 doesn't work well

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04.5 i386
  Ubuntu 16.04.2 i386

  I have a small DIY server for long time and I used PCI card with chip
  "SiL 3112" to connect SATA drives, to have RAID volume; I use SW RAID
  (mdadm). I am sure that when I built this system long time ago, it
  worked fine but it reports many DMA errors now, too many errors and it
  works slowly because there are many retries. I changed all my SATA
  cables, etc but that was not a source of the trouble. Real trouble is
  chip SiL3112. I believe that some change in Linux kernel module
  sata_sil started the trouble. I cannot tell when it happened, 2017,
  2016 or even 2015?

  Anyway, I replaced my SATA card with card based on SiL 3114 and it
  works fine!

  $ lspci | grep 3114
  00:0d.0 Mass storage controller: Silicon Image, Inc. SiI 3114 
[SATALink/SATARaid] Serial ATA Controller (rev 02)

  I see this message in dmesg output (14.04.5, 3.13.0-117-generic
  #164-Ubuntu SMP Fri Apr 7 11:06:36 UTC 2017 i686):

  [3.543370] sata_sil :00:0d.0: version 2.4
  [3.544339] sata_sil :00:0d.0: Applying R_ERR on DMA activate FIS 
errata fix

  Could be the same "workarround" applied to SiL 3112 card? I know that
  when SiL 3112 is in my PC, I cannot find any message "Applying R_ERR
  on DMA activate FIS errata fix" in dmesg output.

  BTW, I have found some comments on the net, that these cards are
  "broken" and should be avoided as plague, etc. Well, I think that my
  SiL 3112 worked fine in the past and SiL 3114 works fine just now, so
  it is driver problem (and some HW design bug, so the performance of
  chips is limited by this SW workaround).

  This report is from Ubuntu 14.04.4 but I already tried 16.04.2 but it
  was not better, DMA errors were there but were more visible
  (annoying).

  I can update this report with details about SiL 3112 card but it is
  out of my PC now...

  SATA card with SiL 3112 is loaded with Non-RAID BIOS v 4.2.84.
  http://www.latticesemi.com/view_document?document_id=51771
  file b4284.bin

  ---
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/hwC0D0', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=468d6e78-760e-4825-9e16-3b8e4110f981
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq Deskpro EN Series SFF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic 
root=UUID=afab7acb-1aa5-4ac8-a8ff-4cb3c57b5eb7 ro quiet splash acpi=force 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-117-generic N/A
   linux-backports-modules-3.13.0-117-generic  N/A
   linux-firmware  1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-117-generic i686
  UpgradeStatus: Upgraded to trusty on 2015-03-08 (797 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 08/21/99
  dmi.bios.vendor: Compaq
  dmi.bios.version: 686T5
  dmi.board.name: 042Ch
  dmi.board.vendor: Compaq
  dmi.chassis.asset.tag: 8031DLCC0314
  dmi.chassis.type: 3
  dmi.chassis.vendor: Compaq
  dmi.modalias: 
dmi:bvnCompaq:bvr686T5:bd08/21/99:svnCompaq:pnDeskproENSeriesSFF:pvr:rvnCompaq:rn042Ch:rvr:cvnCompaq:ct3:cvr:
  dmi.product.name: Deskpro EN Series SFF
  dmi.sys.vendor: Compaq

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


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

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

The linux-aws/6.2.0-1005.5 kernel defines do_lib_rust only for the
master kernel (amd64) - as expected on this kernel.

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

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

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

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

Bug description:
  [Impact]

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

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

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

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

  [Regression potential]

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

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


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

[Kernel-packages] [Bug 2012612] Re: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well

2023-06-14 Thread Simon Chopin

Hi,

This seems reasonable to me, especially since it also seems like it
would be needed to address xnox's review in bug 2012412. Uploaded, and
unsubscribed ubuntu-sponsors.

I also took the liberty to modify a bit the testplan to make it obvious
to bystanders (e.g. me) how to reproduce the issue.

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

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

Title:
  Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well

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

Bug description:
  [SRU Justification]

  Impact:
  Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG 
which prevent it from building if a specific configuration is enabled/disabled.
  This feature was released for kinetic but not for jammy.
  This backports the patch to jammy as well.

  Fix:
  Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic.
  In order to be applied, I had to slightly modify the first junk. Other than 
that, it was a clean backport.

  [Testcase]

  $ sudo apt install linux-image-kvm linux-headers-kvm
  $ sudo apt install evdi-dkms

  Before the fix, it will fail with this error:
  DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64)
  Thu Mar 23 10:10:14 UTC 2023
  make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm'
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
    CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit 
declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
     49 | return i2c_add_adapter(adapter);
    |^~~
    |i2c_verify_adapter
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function 
‘evdi_i2c_remove’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit 
declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
     54 | i2c_del_adapter(adapter);
    | ^~~
    | i2c_verify_adapter
  cc1: some warnings being treated as errors
  make[1]: *** [scripts/Makefile.build:297: 
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1
  make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm'

  This fails because CONFIG_I2C=n for a KVM kernel derivative.
  Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C 
CONFIG_DRM"

  After the fix, it will not build:
  Building initial module for 5.15.0-1029-kvm
  Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf 
for module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch.
  The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for 
module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch/config.
  This indicates that it should not be built.
  Skipped.

  [Regression potential]

  Very low, this is just a simple feature to prevent building a module.

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


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

[Kernel-packages] [Bug 2012612] Re: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well

2023-06-14 Thread Simon Chopin

** Description changed:

  [SRU Justification]
  
  Impact:
  Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG 
which prevent it from building if a specific configuration is enabled/disabled.
  This feature was released for kinetic but not for jammy.
  This backports the patch to jammy as well.
  
  Fix:
  Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic.
  In order to be applied, I had to slightly modify the first junk. Other than 
that, it was a clean backport.
  
- Testcase:
- I used evdi as dkms module with this feature. Before the fix, it will fail 
with this error:
+ [Testcase]
+ 
+ $ sudo apt install linux-image-kvm linux-headers-kvm
+ $ sudo apt install evdi-dkms
+ 
+ Before the fix, it will fail with this error:
  DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64)
  Thu Mar 23 10:10:14 UTC 2023
  make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm'
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
-   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
+   CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit 
declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
-49 | return i2c_add_adapter(adapter);
-   |^~~
-   |i2c_verify_adapter
+    49 | return i2c_add_adapter(adapter);
+   |^~~
+   |i2c_verify_adapter
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function 
‘evdi_i2c_remove’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit 
declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
-54 | i2c_del_adapter(adapter);
-   | ^~~
-   | i2c_verify_adapter
+    54 | i2c_del_adapter(adapter);
+   | ^~~
+   | i2c_verify_adapter
  cc1: some warnings being treated as errors
  make[1]: *** [scripts/Makefile.build:297: 
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1
  make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm'
  
  This fails because CONFIG_I2C=n for a KVM kernel derivative.
  Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C 
CONFIG_DRM"
  
  After the fix, it will not build:
  Building initial module for 5.15.0-1029-kvm
  Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf 
for module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch.
  The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for 
module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch/config.
  This indicates that it should not be built.
  Skipped.
  
+ [Regression potential]
  
- Regression potential:
  Very low, this is just a simple feature to prevent building a module.

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

Title:
  Add new

[Kernel-packages] [Bug 2018303] Re: move sev-guest module from linux-modules-extra to linux-modules

linux-aws/6.2.0-1005.5 provides the sev-guest kernel module in the
linux-modules package (linux-
modules-6.2.0-1005-aws_6.2.0-1005.5_amd64.deb).

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

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

Title:
  move sev-guest module from linux-modules-extra to linux-modules

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

Bug description:
  AWS did recently announce AMD SEV-SNP support (see
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To
  have that working in the ubuntu AWS images, the module needs to be
  available (linux-modules-extra is not installed by default).

  So please move the module to linux-modules.

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


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

[Kernel-packages] [Bug 2010997] Re: Pull-Request to address USB and PWM cooling fan issues with Orin HW

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Pull-Request to address USB and PWM cooling fan issues with Orin HW

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

Bug description:
  [Impact]
  Adding this patch addresses USB and PWM cooling fan issues as described 
in the following bugs:

  https://bugs.launchpad.net/riverside/+bug/2009867
  https://bugs.launchpad.net/riverside/+bug/2002173

   [Fix]
  The PR is made up of a revert of one commit and the application of 4 new 
patches from upstream to address the indicated issues.

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


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

[Kernel-packages] [Bug 2012939] Re: Pull-request to address a number of issues in the nvidia-tegra -1010.10

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Pull-request to address a number of issues in the nvidia-tegra
  -1010.10

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

Bug description:
  [Impact]
  Adding these patches address a number of differences between the Ubuntu 
kernel and the internal NVIDIA kernel.

   [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-tegra/+bug/2012939/+subscriptions


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

[Kernel-packages] [Bug 2015755] Re: Pull-request to address mgbe ethernet driver on AGX Orin

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Pull-request to address mgbe ethernet driver on AGX Orin

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

Bug description:
  [Impact]
  This patch set is intended to address 
https://bugs.launchpad.net/riverside/+bug/2011636

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


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

[Kernel-packages] [Bug 2021535] Re: Request application of upstream patch to address drm/ast ARM compatibility issue

** Package changed: linux-nvidia-tegra (Ubuntu) => linux-nvidia-5.19
(Ubuntu)

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

Title:
  Request application of upstream patch to address drm/ast ARM
  compatibility issue

Status in linux-nvidia-5.19 package in Ubuntu:
  New

Bug description:
  [impact]
  This patch addresses a drm/ast compatibility issue with ARM architecture. The 
patch is in the upstream Linux kernel as sha1 
4327a6137ed43a091d900b1ac833345d60f32228. The issue was found during 
development testing and application of this commit has been confirmed to 
resolve the issue.

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


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

[Kernel-packages] [Bug 2003728] Re: Enable MGBE ethernet on Orin platforms

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Enable MGBE ethernet on Orin platforms

Status in linux-nvidia-tegra 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.

  Specifically these 3 patches (2 cherry-picks and 1 backport) add
  the MGBE driver.

   [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-tegra/+bug/2003728/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-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] Re: Please apply yet another set of Orin, platform enablement patches

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

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

Status in linux-nvidia-tegra 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-tegra/+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 2001557] Re: Integrate Nvidia Orin enablement patches

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Integrate Nvidia Orin enablement patches

Status in linux-nvidia-tegra 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-tegra/+bug/2001557/+subscriptions


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

[Kernel-packages] [Bug 2008503] Re: Please apply another batch of Orin platform enablement patches

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Please apply another batch of Orin platform enablement patches

Status in linux-nvidia-tegra 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-tegra/+bug/2008503/+subscriptions


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

[Kernel-packages] [Bug 2008921] Re: Please apply the indicated patch to address an audio issue with the tegra kernel

** Package changed: linux-nvidia (Ubuntu) => linux-nvidia-tegra (Ubuntu)

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

Title:
  Please apply the indicated patch to address an audio issue with the
  tegra kernel

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

Bug description:
   [Impact]
  Adding this patch addresses a specific audio issue with the tegra kernel.

   [Fix]
  ASoC: simple-card-utils: Increase maximum DAI links limit to 512

  The current limit of 128 is not sufficient when more components are
  added to the audio map on Tegra210 and later platforms. Thus it is
  resulting in probe failure.

  The requirement is of nearly ~200 DAI links. To give sufficient room
  for future additions the maximum limit is increased to 512 DAI links.
  This is a preparatory patch to add more components like resampler,
  mixer, multiplexers, demultiplexers and volume controllers to Tegra210
  and later platforms.

   This is upstream commit 7a226f2eabdc2e839d8f07c5ce087136f9c0f35c

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


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

[Kernel-packages] [Bug 2018303] Re: move sev-guest module from linux-modules-extra to linux-modules

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

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

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


** Tags added: kernel-spammed-lunar-linux-aws verification-needed-lunar

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

Title:
  move sev-guest module from linux-modules-extra to linux-modules

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

Bug description:
  AWS did recently announce AMD SEV-SNP support (see
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To
  have that working in the ubuntu AWS images, the module needs to be
  available (linux-modules-extra is not installed by default).

  So please move the module to linux-modules.

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


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

[Kernel-packages] [Bug 2012612] Re: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well

2023-06-14 Thread Simon Chopin

** Changed in: dkms (Ubuntu)
   Status: New => Fix Released

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

** Changed in: dkms (Ubuntu Kinetic)
   Status: New => Fix Released

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

Title:
  Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Jammy:
  New
Status in dkms source package in Kinetic:
  Fix Released

Bug description:
  [SRU Justification]

  Impact:
  Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG 
which prevent it from building if a specific configuration is enabled/disabled.
  This feature was released for kinetic but not for jammy.
  This backports the patch to jammy as well.

  Fix:
  Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic.
  In order to be applied, I had to slightly modify the first junk. Other than 
that, it was a clean backport.

  Testcase:
  I used evdi as dkms module with this feature. Before the fix, it will fail 
with this error:
  DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64)
  Thu Mar 23 10:10:14 UTC 2023
  make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm'
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
CC [M]  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit 
declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
 49 | return i2c_add_adapter(adapter);
|^~~
|i2c_verify_adapter
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function 
‘evdi_i2c_remove’:
  /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit 
declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? 
[-Werror=implicit-function-declaration]
 54 | i2c_del_adapter(adapter);
| ^~~
| i2c_verify_adapter
  cc1: some warnings being treated as errors
  make[1]: *** [scripts/Makefile.build:297: 
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1
  make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm'

  This fails because CONFIG_I2C=n for a KVM kernel derivative.
  Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C 
CONFIG_DRM"

  After the fix, it will not build:
  Building initial module for 5.15.0-1029-kvm
  Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf 
for module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch.
  The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for 
module evdi includes a BUILD_EXCLUSIVE directive which does not match this 
kernel/arch/config.
  This indicates that it should not be built.
  Skipped.

  
  Regression potential:
  Very low, this is just a simple feature to prevent building a module.

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


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

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

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

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

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


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

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

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

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

Bug description:
  [Impact]

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

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

  [Test case]

  Build the kernel producing all the debs.

  [Fix]

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

  [Regression potential]

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

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1102.107)

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

r8168/8.048.00-1ubuntu0.20.04.2 (amd64)
systemd/245.4-4ubuntu3.21 (arm64)


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

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

[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 1997505] Re: Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

2023-06-14 Thread Andy Whitcroft

** Description changed:

+ [ Impact ]
+ 
+ When the a factory image is installed onto a new system it ends up with
+ very old packages installed as available when that image was frozen.
+ Due to the presence of strict version clamps in some older linux-
+ restricted-modules packages these will not upgrade as removals are
+ required, however the associated kernel can still upgrade.  This leads
+ unattended-upgrades to upgrade one without the other rendering the
+ latest kernel unable to drive the display.  A very poor user experience
+ on second boot.
+ 
+ [ Test Plan ]
+ 
+ Install a factory image into a VM and allow unattended-upgrades to
+ upgrade the system; expect the kernel to upgrade and Nvidia components
+ to be held-back.  Then install this package and expect both to upgrade.
+ 
+ [ Where problems could occur ]
+ 
+ The new source provides updated packages for very old and now abandoned
+ ABI specific packages.  No current install should have the packages we
+ are changing nor should they be installed by normal updates.  Affected
+ installs from frozen media should install a single package out of this
+ set based on their frozen ABI version releasing the strict version
+ clamp, and then immediately upgrade to the latest packages in the
+ archive.  We do not expect these packages to remain installed on any
+ system.
+ 
+ [ Other Info ]
+ 
+ All included packages are pulled directly from the Launchpad Librarian.
+ 
+ ===
+ 
  If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
  would like meet this issue.
  
- 1020-oem is in security channel. In jammy the unattende-upgrade will
+ 1020-oem is in security channel. In jammy the unattended-upgrade will
  install security fixes by default.
  
  For the I+N platforms, the nvidia driver couldn't be installed for
  1020-oem kernel, then user will meet a black screen cause of nvidia
  modules couldn't be loaded.
  
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  "${distro_id}ESMApps:${distro_codename}-apps-security";
  "${distro_id}ESM:${distro_codename}-infra-security";

** Changed in: linux-meta-oem-5.14 (Ubuntu)
   Importance: Undecided => Critical

** Also affects: oem-priority/focal
   Importance: Critical
 Assignee: Bin Li (binli)
   Status: Confirmed

** No longer affects: oem-priority/focal

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

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

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

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

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

Title:
  Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver

Status in OEM Priority Project:
  Confirmed
Status in linux-meta-oem-5.14 package in Ubuntu:
  New
Status in linux-meta-oem-5.17 package in Ubuntu:
  Fix Released
Status in linux-meta-oem-5.14 source package in Focal:
  New
Status in linux-meta-oem-5.17 source package in Focal:
  New
Status in linux-meta-oem-5.14 source package in Jammy:
  New
Status in linux-meta-oem-5.17 source package in Jammy:
  New

Bug description:
  [ Impact ]

  When the a factory image is installed onto a new system it ends up
  with very old packages installed as available when that image was
  frozen.  Due to the presence of strict version clamps in some older
  linux-restricted-modules packages these will not upgrade as removals
  are required, however the associated kernel can still upgrade.  This
  leads unattended-upgrades to upgrade one without the other rendering
  the latest kernel unable to drive the display.  A very poor user
  experience on second boot.

  [ Test Plan ]

  Install a factory image into a VM and allow unattended-upgrades to
  upgrade the system; expect the kernel to upgrade and Nvidia components
  to be held-back.  Then install this package and expect both to
  upgrade.

  [ Where problems could occur ]

  The new source provides updated packages for very old and now
  abandoned ABI specific packages.  No current install should have the
  packages we are changing nor should they be installed by normal
  updates.  Affected installs from frozen media should install a single
  package out of this set based on their frozen ABI version releasing
  the strict version clamp, and then immediately upgrade to the latest

[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')

2023-06-14 Thread Po-Hsu Lin

Hints removed.

** Changed in: ubuntu-kernel-tests
   Status: In Progress => 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/1937133

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  On s390x LPAR instances, this test will fail with:
  #   File "linux/tools/testing/selftests/net/devlink_port_split.py", line 
64, in get_if_names
  # if ports[port]['flavour'] == 'physical':
  # KeyError: 'flavour'
not ok 1 selftests: net: devlink_port_split.py # exit=1

  This is because the mlx4 driver in use on this instance does not set
  attributes, therefore `devlink -j port show` command output does not
  contain this "flavour" key.

  [Fix]
  * 3de66d08d3 selftests: net: devlink_port_split.py: skip test if no
suitable device available

  This patch can be cherry-picked into our J/K/L kernels.

  [Test]
  Run the patched devlink_port_split.py on s390x LPAR, and it won't
  fail with # KeyError: 'flavour' but marked as SKIP instead.

  [Where problems could occur]
  If this change is incorrect, it may affect the test result, however it's
  limited to testing tools, no actual impact to kernel functions.


  [Original Bug Report]
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25

  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

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


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

@ Ben Baker thank you for your suggestion. I did try and here is what
has actually happened:

When I only added `intel_idle.max_cstate=1` kernel boot arg to grub
boot, without `nomodeset` and without `i915.enable_psr=0`, I got a
system freeze just when the login screen showed up. I only tried this
once.

Then, I have added `intel_idle.max_cstate=1` along 'i915.enable_psr=0'
(without `nomodeset`). This time, the system booted fine. When I tried
"sudo systemctl suspend", yes, the system went into sleep and woke up
fine. I did not wait too long after the system went into sleep and me
waking it up again. I have tried this on AC and on battery and it worked
both times. And it does so even if I just close the lid and then open it
back up again. Great!

What still seems to be an issue, however, if the screen fades to black
after being idle. Now, if this happens and one would quickly interact
with the system, all comes back and works fine. IF THERE IS 10-20
SECONDS WAIT AFTER THE SCREEN FADED TO BLACK, it becomes unresponsive (I
repeated the test three times, and once it happened after 2 minutes 39
seconds)! I had ping running to this laptop and I also had an ssh
connection showing 'top' and both were gone (ping stopped and 'top'
stopped updating).

I also tried to issue "sudo systemctl hibernate" and again, the screen
would go black straight away, keyboard back-light would fade, with the
power button led still on, and, the system would become unresponsive
(still, if I press any key on the keyboard, the back-light would come
back on again and fade after a little while). For the record, ping and
'top' via ssh would also stop.

It would be really good for this to get a solution. (I tried running
Ubuntu 23.04 and the problem persists, without me testing too much).

--
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:

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

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

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

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.

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

[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt

2023-06-14 Thread Stefan Bader

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

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

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

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

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

Title:
  cls_flower: off-by-one in fl_set_geneve_opt

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Fix 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]
  An unprivileged user may cause an out-of-bounds write by setting up geneve 
options on the flower classifier.

  [Test case]
  https://seclists.org/oss-sec/2023/q2/219

  [Potential regression]
  Users setting up geneve options on the flower tc classifier can be affected.

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


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

[Kernel-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

2023-06-14 Thread Dirk Su

** Changed in: ubuntu-drivers-common (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-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1988836

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1087.84) 
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

acpi-call/unknown (arm64)
bbswitch/unknown (arm64)
dpdk/unknown (arm64)
fwts/unknown (arm64)
glibc/unknown (arm64)
ktap/unknown (arm64)
langford/unknown (arm64)
linux-raspi-5.4/blacklisted (arm64, armhf)
lxc/3.0.3-0ubuntu1~18.04.3 (arm64)
lxd/unknown (arm64)
nat-rtsp/unknown (arm64)
r8168/unknown (arm64)
rtl8812au/unknown (arm64)
rtl8821ce/unknown (arm64)
spl-linux/unknown (arm64)
west-chamber/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
zfs-linux/unknown (arm64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-meta-raspi-5.4

[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 2023750] [NEW] package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: »dpkg-deb --fsys-tarfile«-Unterprozess gab den Fehlerwert 2 zurück

2023-06-14 Thread Michi Müller

Public bug reported:

Wurde nur als Meldung agezeigt

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckMismatches: ./casper/minimal.squashfs
CasperMD5CheckResult: fail
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Wed Jun 14 10:30:19 2023
Dependencies: firmware-sof-signed 2.2.4-1
ErrorMessage: »dpkg-deb --fsys-tarfile«-Unterprozess gab den Fehlerwert 2 zurück
InstallationDate: Installed on 2023-06-14 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: CSL-Computer GmbH & Co. KG A001
PackageArchitecture: all
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=4f8c3a9f-3215-4cb6-b320-8f24471d2663 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux-firmware
Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to 
install/upgrade: »dpkg-deb --fsys-tarfile«-Unterprozess gab den Fehlerwert 2 
zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/08/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B550M-A (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/08/2022:br5.17:svnCSL-ComputerGmbH:pnA001:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB550M-A(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:sku82071:
dmi.product.family: Sprint
dmi.product.name: A001
dmi.product.sku: 82071
dmi.product.version: System Version
dmi.sys.vendor: CSL-Computer GmbH & Co. KG

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to
  install/upgrade: »dpkg-deb --fsys-tarfile«-Unterprozess gab den
  Fehlerwert 2 zurück

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Wurde nur als Meldung agezeigt

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Jun 14 10:30:19 2023
  Dependencies: firmware-sof-signed 2.2.4-1
  ErrorMessage: »dpkg-deb --fsys-tarfile«-Unterprozess gab den Fehlerwert 2 
zurück
  InstallationDate: Installed on 2023-06-14 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: CSL-Computer GmbH & Co. KG A001
  PackageArchitecture: all
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=4f8c3a9f-3215-4cb6-b320-8f24471d2663 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-firmware
  Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to 
install/upgrade: »dpkg-deb --fsys-tarfile«-Unterprozess gab den Fehlerwert 2 
zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B550M-A (WI-FI)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/08/2022:br5.17:svnCSL-ComputerGmbH:pnA001:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB550M-A(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:sku82071:
  dmi.product.family: Sprint
  dmi.product.name: A001
  dmi.product.sku: 82071
  dmi.product.version: System Version
  dmi.sys.vendor:

[Kernel-packages] [Bug 2015867] Re: Kernel 6.1 bumped the disk consumption on default images by 15%

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

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

Title:
  Kernel 6.1 bumped the disk consumption on default images by 15%

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed
Status in linux source package in Mantic:
  Confirmed

Bug description:
  [Impact]

  After enabling Rust support in the kernel we noticed an increased size
  in linux-headers, because all the Rust libraries required to build
  out-of-tree  kernel modules are now included in linux-headers
  directly.

  The increased size goes from ~30MB to ~100MB.

  This extra size is not worth it, considering the small amount of users
  that are going to experiment Rust in the kernel at the moment.

  [Test case]

  Install linux-headers and check the size of /usr/src/linux-
  headers-`uname -r`.

  [Fix]

  Some work has already done to reduce the size of linux-headers by
  dropping some binary artifacts (*.o and *.cmd) that are not required
  to build out-of-tree kernel modules.

  Ideally it'd be nicer to provide a separate package (called for
  example linux-lib-rust-`uname -r`) to ship the Rust-specific
  dependencies (libraries / headers).

  In this way linux-headers would be restored back to the original size,
  those that want to experiment Rust in the kernel can simply install
  linux-lib-rust and we can prevent wasting space in the cloud images.

  [Regression potential]

  Introducing a new package in the kernel may break something in our
  kernel promotion workflow, so with this change applied we need to pay
  a little more attention when the kernel is going to be promoted to
  release/updates.

  [Original bug report]

  Hi,
  in the regular monitoring of metrics there was a bump in disk size last week.
  The default image once installed consumes now 994 (formerly 859) megabytes.

  Looking at the consumers there was much noise, but the biggest change
  was

  linux-headers-5.19.0-1008-kvm 25197 -> linux-headers-6.2.0-1002-kvm 108072
  linux-modules-5.19.0-1008-kvm 76090 -> linux-modules-6.2.0-1002-kvm 97221

  I haven't looked deeper yet. Is that an accident and will be fixed
  soon, is that a change we can do nothing about, anything in between?

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


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

[Kernel-packages] [Bug 2023307] Re: System hang at reading amdgpu sysfs attribute psp_vbflash

2023-06-14 Thread Timo Aaltonen

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

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

Title:
  System hang at reading amdgpu sysfs attribute psp_vbflash

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

Bug description:
  [Summary]
  1. System hang on starting checkbox test.
  2. Hang on collecting device information during start Auto and Stress test.
  3. This issue exist on GPU with W7500 & W7600.

  [Steps to reproduce]
  1. Boot into OS
  2. Start Auto test or Stress test(checkbox-cli run 
com.canonical.certification::sysfs_attachment)

  AMD proposed fix in 
https://lore.kernel.org/amd-gfx/20230607065259.48516-1-mario.limoncie...@amd.com/T/#mc5c38f31129f23e498d669734cafe96474a8f8ba
 .
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1442 F pulseaudio
   /dev/snd/controlC0:  u  1442 F pulseaudio
  CasperMD5CheckResult: pass
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-tynamo+X81
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2023-05-16 (23 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  IwConfig:
   lono wireless extensions.
   
   enp5s0f0  no wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Dell Inc. Precision 7875 Tower
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem 
root=UUID=e9463c30-0a89-4838-a9fa-3296791ccd2a ro log_buf_len=64M quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.1.0-1014-oem N/A
   linux-backports-modules-6.1.0-1014-oem  N/A
   linux-firmware  20220329.git681281e4-0ubuntu3.13
  RfKill:
   
  Tags:  jammy
  Uname: Linux 6.1.0-1014-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 05/10/2023
  dmi.bios.release: 0.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.28
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 0.18
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.28:bd05/10/2023:br0.4:efr0.18:svnDellInc.:pnPrecision7875Tower:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0C61:
  dmi.product.family: Precision
  dmi.product.name: Precision 7875 Tower
  dmi.product.sku: 0C61
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2022826] Re: Ethernet hangs

2023-06-14 Thread John Rose

Apologies to everyone trying to help. It turns out that the problem is
the computer: a 4 month old Asus mini PN50-1. I suddenly remembered that
the same thing had happened last August and that the supplier had given
me a replacement after I returned the original.

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

Title:
  Ethernet hangs

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I'm now getting my wired (i.e. Ethernet) connection hanging on trying
  to connect. I've tried switching ports (on the router) and using a
  different cable, but still the same.

  ifconfig shows for Ethernet:
  enp2s0: flags=4163 mtu 1500
  ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet)
  RX packets 2779 bytes 250524 (250.5 KB)
  RX errors 0 dropped 1 overruns 0 frame 0
  TX packets 355 bytes 72171 (72.1 KB)
  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  sudo lshw -C enp2s0 shows nothing

  lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]:
  Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
  (rev 05)

  I found a web page: https://tutorialforlinux.com/2021/05...based-systems/
  I followed the instructions and installed realtek-r8125-dkms package OK. On 
rebooting, I followed the instructed procedure (shown when installing the 
package) of creating a password and then entering it when requested on the 
reboot. But still same problem. Any ideas what to do?
  PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is 
a little flaky due to walls) in order to post this question.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  3 07:29:15 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  InstallationDate: Installed on 2022-08-21 (285 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago)
  dmi.bios.date: 03/18/2021
  dmi.bios.release: 4.5
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0405
  dmi.board.asset.tag: Default string
  dmi.board.name: PN50-E1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: MINIPC PN50-E1
  dmi.product.version: 0405
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 2019320] Re: i2c devices missing in lunar

2023-06-14 Thread Juerg Haefliger

** Description changed:

+ [Impact]
+ 
  In the lunar release of linux-raspi, despite the boot configuration
  enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0
  and /dev/i2c-1 devices are missing (they are present in jammy and
  kinetic). These are the I2C interfaces present on the GPIO header (and
  thus rather important on the raspi as without these interfaces being
  present, I2C devices connected to the header cannot be used).
  
  I'm guessing this is a kernel change, but it *might* be something in the
  udev configuration; I haven't dug that far yet.
+ 
+ [Test Case]
+ 
+ Boot raspi and check presence of /dev/i2c-* device entries.
+ 
+ [Where Problems Could Occur]
+ 
+ Previous release had the i2c-dev driver compiled into the kernel. With
+ lunar we turned it into a module which turns out to be not great. So
+ change it back and restore the old behavior.

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

** Changed in: linux-raspi (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  i2c devices missing in lunar

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Lunar:
  Confirmed

Bug description:
  [Impact]

  In the lunar release of linux-raspi, despite the boot configuration
  enabling the i2c_arm parameter of the base overlay, the usual
  /dev/i2c-0 and /dev/i2c-1 devices are missing (they are present in
  jammy and kinetic). These are the I2C interfaces present on the GPIO
  header (and thus rather important on the raspi as without these
  interfaces being present, I2C devices connected to the header cannot
  be used).

  I'm guessing this is a kernel change, but it *might* be something in
  the udev configuration; I haven't dug that far yet.

  [Test Case]

  Boot raspi and check presence of /dev/i2c-* device entries.

  [Where Problems Could Occur]

  Previous release had the i2c-dev driver compiled into the kernel. With
  lunar we turned it into a module which turns out to be not great. So
  change it back and restore the old behavior.

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


-- 
Mailing list: https://launchpad.net/~kernel-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-oracle-5.4/5.4.0.1103.112~18.04.75)