from:"Michael"

All of these patches are in the latest master-next noble kernel.

git describe --tags
Ubuntu-6.8.0-11.11-1-g04cdb2da2df3

** Changed in: linux (Ubuntu Noble)
   Status: Confirmed => 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/2044589

Title:
  [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and
  include critical  fixes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Noble:
  Fix Committed

Bug description:
  This request is to add support for SAS5116 controller and few critical 
bug-fixes in Ubuntu 24.04 LTS.
  Below is the list of upstream commits that adds support for SAS5116:

  b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50
  1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor
  cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32
  c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116
  6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs

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


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

[Kernel-packages] [Bug 2046875] Re: [22.04.04]: mpt3sas: Critical Bug Fixes

This is a public version of the following bug:

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

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

Title:
  [22.04.04]: mpt3sas: Critical Bug Fixes

Status in linux package in Ubuntu:
  New

Bug description:
  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  3c978492c333  : scsi: mpt3sas: Fix loop logic
  0854065092a7  : scsi: mpt3sas: Remove volatile qualifier
  4ca10f3e3174 :  scsi: mpt3sas: Perform additional retries if doorbell read 
returns 0

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


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

[Kernel-packages] [Bug 2046722] Re: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

This is a public version of the following bug:

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

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

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

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

I have created tests kernels for both Jammy and Mantic.  Please test and
provide feedback.


Jammy
https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/jammy/

Mantic
https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/mantic/

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

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

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

These patches are already in 6.8

** Summary changed:

- [22.04.04]: megaraid_sas: Critical Bug Fixes
+ [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

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

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Michael Reed (mreed8855)
   Status: New

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

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

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

Hi Chandrakanth,

Can you also fill in these fields for the SRU process in addition to
testing the test kernels

[Test Plan]

[ Where problems could occur ]

[ Other Info ]

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

Title:
  [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes

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

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

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

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes

** Description changed:

+ [Impact]
+ 
  This update has been initiated to include a few critical bug fixes from
  upstream into the upcoming 22.04.04 point kernel. Below are the upstream
  commit IDs:
  
+ 
+ [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()
  
+ The change log for the above commit IDs is small and doesn't require
+ rigorous validation. So please include these patches.
  
- The change log for the above commit IDs is small and doesn't require rigorous 
validation. So please include these patches.
+ [Test Plan]
+ 
+ [ Where problems could occur ]
+ 
+ [ Other Info ]
+ 
+ Jammy
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update
+ 
+ 
+ Mantic
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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

Title:
  [22.04.04]: megaraid_sas: Critical Bug Fixes

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  This update has been initiated to include a few critical bug fixes
  from upstream into the upcoming 22.04.04 point kernel. Below are the
  upstream commit IDs:

  
  [Fix]
  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()

  The change log for the above commit IDs is small and doesn't require
  rigorous validation. So please include these patches.

  [Test Plan]

  [ Where problems could occur ]

  [ Other Info ]

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

  
  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update

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


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

[Kernel-packages] [Bug 2046726] Re: [24.04 LTS]: megaraid_sas driver update

2024-02-20 Thread Michael Reed

I have verified that all of the patches listed in the description are
indeed in the currently 6.8 proposed kernel and should be in 24.04.

$ git describe --tags
Ubuntu-6.8.0-11.11-1-g04cdb2da2df3

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

Title:
  [24.04 LTS]: megaraid_sas driver update

Status in linux package in Ubuntu:
  New

Bug description:
  This update has been initiated to incorporate the megaraid_sas driver
  from upstream into the upcoming Ubuntu 24.04 LTS release.

  Assuming the 24.04 already included the patches up to driver version
  07.725.01.00-rc1. So, below are the commit IDs after it.

  0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
  2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is 
requested but not issued
  8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 
30 for selected registers
  0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump
  bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code
  a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code
  d67790ddf021 overflow: Add struct_size_t() helper
  aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays
  2309df27111a scsi: megaraid_sas: Fix crash after a double completion
  0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show()
  264e222b004c scsi: megaraid: Declare SCSI host template const

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


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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-02-18 Thread Michael Hudson-Doyle

** Description changed:

- In mantic, we migrated livecd-rootfs to use losetup -P instead of
- kpartx, with the expectation that this would give us a reliable, race-
- free way of loop-mounting partitions from a disk image during image
- build.
+ [impact]
+ In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, 
with the expectation that this would give us a reliable, race-free way of 
loop-mounting partitions from a disk image during image build.
  
  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.
  
  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is
  
-   https://launchpad.net/~ubuntu-
+   https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790
  
  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.
  
-   https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el
+   https://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/noble/ppc64el
  
  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.
+ 
+ The losetup usage has been backported to Jammy, and sees frequent
+ failures there.
+ 
+ [test case]
+ The autopkgtests will provide enough confidence that the changes are not 
completely broken. Whether the change helps with the races on riscv can be 
"tested in prod" just as well as any other way.
+ 
+ [regression potential]
+ If the backport has been done incorrectly, image builds can fail (and the 
autopkgtests will fail if it has been completely bungled). This can be quickly 
handled. There is no foreseeable way for this to result in successful builds 
but broken images, which would be a much more difficult failure mode to unpick.

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in livecd-rootfs source package in Jammy:
  New
Status in util-linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in livecd-rootfs source package in Mantic:
  New
Status in util-linux source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in util-linux source package in Noble:
  New

Bug description:
  [impact]
  In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, 
with the expectation that this would give us a reliable, race-free way of 
loop-mounting partitions from a disk image during image build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

    https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

    https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

  The losetup usage has been backported to Jammy, and sees frequent
  failures there.

  [test case]
  The autopkgtests will provide enough confidence that the changes are not 
completely broken. Whether the change helps with the races on riscv can be 
"tested in prod" just as well as any other way.

  [regression potential]
  If the backport has been done incorrectly, image builds can fail (and the 
autopkgtests will fail if it has been completely bungled). This can be quickly 
handled. There is no foreseeable way for this to result in successful builds 
but broken images, which would be a much more difficult failure mode to unpick.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-02-18 Thread Michael Hudson-Doyle

Here is a backport of the partial fix to jammy
https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-
rootfs/+merge/460729

I'm not sure I am best placed to update this bug description to match
the SRU template though -- I'm not sure which builds are being affected
in practice and so should be incorporated into the test plan.

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in livecd-rootfs source package in Jammy:
  New
Status in util-linux source package in Jammy:
  New
Status in linux source package in Mantic:
  New
Status in livecd-rootfs source package in Mantic:
  New
Status in util-linux source package in Mantic:
  New
Status in linux source package in Noble:
  New
Status in livecd-rootfs source package in Noble:
  Fix Released
Status in util-linux source package in Noble:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2051457] Re: Jammy 22.04.3 gcc compiler no longer builds modules for 6.5.0 kernel series

2024-01-30 Thread Michael Rakijas

I have this problem as well.  I've made multiple approaches trying to
install the stock package for CUDA:

cuda-repo-ubuntu2204-12-1-local_12.1.1-530.30.02-1_amd64.deb

but had problems with the 530 Nvidia driver.  Got suggestions to try to
install the 535 Nvidia driver first so that the 530 driver install would
be bypassed as deprecated.  The 535 package would not install with the
following packages being held back:

gjs libgjs0g

These attempts were both on a fresh install.  I may try the suggestion
in

https://ubuntuforums.org/showthread.php?t=2494273=2=14175164#post14175164

but this might be excessive for me and I've got work to do.

-Rocky714

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

Title:
  Jammy 22.04.3 gcc compiler no longer builds modules for  6.5.0 kernel
  series

Status in dkms package in Ubuntu:
  New
Status in gcc-defaults package in Ubuntu:
  Won't Fix

Bug description:
  Since Jammy went to the 6.5.0 kernel series, that kernel series was
  compiled with gcc-12. The previous 6.2.0 series kernels were compiled
  with gcc-11.

  The current version of gcc in jammy is 11.4.

  Many NVidia drivers, wifi drivers, VirtualBox (from our Repo), etc
  fail to build the modules, because of a gcc compiler version mismatch
  between what the current running kernel was built by, and the module
  being built.

  I recognized this while helping Users with NVidia driver compile errors on 
the forum, and came up with this work-around for them:
  https://ubuntuforums.org/showthread.php?t=2494273=14175164#post14175164

  Summary:
  Install gcc-12 & g++-12 on 22.04.3 and use it as the compiler.

  Since then, this work-around has helped to resolve problems with
  running the 6.5.0 series kernels and building modules for other
  applications and hardware drivers: VirtualBox, WiFi Drivers, etc. for
  use with the 6.5.0 series.

  I have run this for over a month as my default with no ill affects. I
  have continued to recommend this work-around to many user to solve
  their problems...

  *** I think it is time to look at pushing through gcc-12 as the
  default compiler for 22.04.3 through the normal updates channel.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gcc 4:11.2.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: GNOME
  Date: Sun Jan 28 08:23:37 2024
  InstallationDate: Installed on 2022-09-19 (496 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-01-30 Thread Michael Hudson-Doyle

Oh wait, we've been through something very like this before
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1834875. I suspect
a judicious application of flock may be the most correct solution
available.

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress

2024-01-25 Thread Michael Lin

Heard from Dell DM, there is a regression issue on Jammy which is caused
by this WCN6856 firmware. Therefore, remove verification-done-jammy tag
and suggest dropping this version of linux-firmware and repack another
version. Thanks for your understanding and great support.

** Tags removed: 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/2048977

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Won't Fix
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Due to a known silicon limitation, the following sequence is needed while
  initialing the PCIE device on a certain devices with ASMedia chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes from
  suspend.

  [Fix]

  Upstream commits:
  * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
  * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")

  And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
  update board-2.bin") to forfill git history dependency.

  And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
  bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
  has not yet accept the PR for bug 2042534, it has no such problem at this
  moment.

  [Test Case]

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
  Jammy for oem-6.5 included.

  == original bug report ==

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
    - This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
    - The FW is to support new China regulatory support.

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


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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-01-24 Thread Michael Hudson-Doyle

Here's my workaround then https://code.launchpad.net/~mwhudson/livecd-
rootfs/+git/livecd-rootfs/+merge/459380

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress

2024-01-24 Thread Michael Lin

According to Dell DM's comment, ODM has done the validation with this proposed 
linux-firmware package. Please kindly refer to the attachment and below, thanks.
-
Hi Michael,


ODM has done the validation with this proposed linux-firmware package.
Top on the x88 manifest, and via online update to only install the
linux-firmware.


Running 2000 cycles and issue is VNP. Please moving this proposed linux-
firmware package forward to the updates.


Thanks

** Attachment added: "Canonical Mail - [Tramore] Please Support Verifying 
Qualcomm WCN6856 New Firmware.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048977/+attachment/5741896/+files/Canonical%20Mail%20-%20%5BTramore%5D%20Please%20Support%20Verifying%20Qualcomm%20WCN6856%20New%20Firmware.pdf

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

Title:
  WCN6856 Wi-FI Unavailable and no function during suspend stress

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Lunar:
  Fix Committed
Status in linux-firmware source package in Mantic:
  Fix Committed
Status in linux-firmware source package in Noble:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  Due to a known silicon limitation, the following sequence is needed while
  initialing the PCIE device on a certain devices with ASMedia chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes from
  suspend.

  [Fix]

  Upstream commits:
  * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
  * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")

  And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
  update board-2.bin") to forfill git history dependency.

  And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
  bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
  has not yet accept the PR for bug 2042534, it has no such problem at this
  moment.

  [Test Case]

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  [Where problems could occur]

  Opaque firmware update. No known issue found yet after the update.

  [Other Info]

  This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
  Jammy for oem-6.5 included.

  == original bug report ==

  Due to a known silicon limitation, the following sequence is needed
  while initialing the PCIE device on a certain devices with ASMedia
  chipset involved:

  1. 'hot reset' assert
  2. 2nd PCIe reset' assert
  3. Asmedia 'hot reset' deassert
  4. PT21 GPIO13 2nd PCIe reset' deassert.

  In certain caes, the WIFI link training failed while system resumes
  from suspend.

  This can be reproduced with suspend/resume stress test.

  $ checkbox-cli run com.canonical.certification::stress-
  suspend-30-cycles-with-reboots-automated

  The proposed fixes are:

  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
    - This FW include this LP ticket issue fix
  * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
    - The FW is to support new China regulatory support.

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


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

[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

2024-01-23 Thread Michael Hudson-Doyle

Amazing debugging Dann. Until we can get a kernel fix, what's the way
forward here? Run losetup without -P, run udevadm settle, run partprobe
on the device (then maybe run udevadm settle again??)

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2049711] [NEW] Kernels 6.2 and 6.5: cannot adjust screen brightness

2024-01-17 Thread Michael Labhard

Public bug reported:

After upgrading to LM 21.3 I could no longer adjust screen brightness.
Reverted to kernel 6.2 but the problem remained. Reverted to kernel
5.15.0-91 generic and that solved the problem.

mel@Schmetterling:~$ inxi -Fxxxrz
System:
  Kernel: 6.5.0-14-generic x86_64 bits: 64 compiler: N/A
Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: HP product: HP Laptop 14-dq2xxx v: N/A
serial:  Chassis: type: 10 serial: 
  Mobo: HP model: 87FD v: 57.20 serial:  UEFI: AMI
v: F.21 date: 03/21/2022
Battery:
  ID-1: BAT0 charge: 40.5 Wh (100.0%) condition: 40.5/41.0 Wh (98.7%)
volts: 12.9 min: 11.4 model: HP Primary type: Li-ion serial: 
status: Full cycles: 28
CPU:
  Info: quad core model: 11th Gen Intel Core i3-1125G4 bits: 64 type: MT MCP
smt: enabled arch: Tiger Lake rev: 1 cache: L1: 320 KiB L2: 5 MiB L3: 8 MiB
  Speed (MHz): avg: 838 high: 1255 min/max: 400/3700 cores: 1: 963 2: 400
3: 400 4: 1137 5: 1255 6: 1021 7: 733 8: 802 bogomips: 31948
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel vendor: Hewlett-Packard driver: i915 v: kernel ports:
active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: :00:02.0
chip-ID: 8086:9a78 class-ID: 0300
  Device-2: Chicony HP TrueVision HD Camera type: USB driver: uvcvideo
bus-ID: 1-3:3 chip-ID: 04f2:b6f1 class-ID: 0e02 serial: 
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
  Monitor-1: eDP-1 model: BOE Display res: 1920x1080 hz: 60 dpi: 158
size: 309x174mm (12.2x6.9") diag: 355mm (14") modes: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics (TGL GT2)
v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Hewlett-Packard
driver: sof-audio-pci-intel-tgl bus-ID: :00:1f.3 chip-ID: 8086:a0c8
class-ID: 0401
  Sound Server-1: ALSA v: k6.5.0-14-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rtw_8822ce v: N/A port: 3000
bus-ID: :01:00.0 chip-ID: 10ec:c822 class-ID: 0280
  IF: wlo1 state: up mac: 
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 1-10:5 chip-ID: 0bda:b00c class-ID: e001 serial: 
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: 
bt-v: 3.0 lmp-v: 5.1 sub-v: 6d7d hci-v: 5.1 rev: 19b7
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 port: N/A bus-ID: :00:0e.0 chip-ID: 8086:9a0b rev:
class-ID: 0104
Drives:
  Local Storage: total: 238.47 GiB used: 100.77 GiB (42.3%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: BC711 HFM256GD3JX013N
size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: 
rev: HPS1 temp: 28.9 C scheme: GPT
Partition:
  ID-1: / size: 232.47 GiB used: 100.77 GiB (43.3%) fs: ext4
dev: /dev/nvme0n1p3
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0 fan-2: 0
Repos:
  Packages: 2736 apt: 2701 flatpak: 35
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/1password.list
1: deb [arch=amd64 
signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] 
https://downloads.1password.com/linux/debian/amd64 stable main
  Active apt repos in: 
/etc/apt/sources.list.d/apandada1-brightness-controller-jammy.list
1: deb 
[signed-by=/etc/apt/keyrings/apandada1-brightness-controller-jammy.gpg] 
https://ppa.launchpadcontent.net/apandada1/brightness-controller/ubuntu jammy 
main
  Active apt repos in: /etc/apt/sources.list.d/chrome-remote-desktop.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome-remote-desktop/deb/ 
stable main
  Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com virginia main upstream import backport
2: deb http://archive.ubuntu.com/ubuntu jammy main restricted universe 
multiverse
3: deb http://archive.ubuntu.com/ubuntu jammy-updates main restricted 
universe multiverse
4: deb http://archive.ubuntu.com/ubuntu jammy-backports main restricted 
universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted 
universe multiverse
  No active apt repos in: /etc/apt/sources.list.d/surfshark.list
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
1:

[Kernel-packages] [Bug 2049107] Re: Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

2024-01-11 Thread Michael Hankins

In case my hardware config is useful:

mhankins@mediabox:~$ inxi -F
System:
  Host: mediabox Kernel: 6.2.0-39-generic x86_64 bits: 64 Console: pty pts/0
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
  Type: Desktop System: Intel product: KBL-R MRD v: 0.1
serial: 
  Mobo: Intel model: MIR1 v: RVP7 serial: 
UEFI: American Megatrends v: 5.12 date: 08/27/2018
CPU:
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache:
L2: 1024 KiB
  Speed (MHz): avg: 1850 min/max: 400/4000 cores: 1: 2000 2: 2000 3: 2000
4: 2000 5: 2000 6: 2000 7: 2000 8: 800
Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
  Display: server: No display server data found. Headless machine?
tty: 80x24 resolution: 2560x1440
  Message: GL data unavailable in console. Try -G --display
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
  Sound Server-1: ALSA v: k6.2.0-39-generic running: yes
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e
  IF: wlp1s0 state: up mac: 14:13:33:8c:7d:85
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:e0:4c:e0:01:2f
  IF-ID-1: br-54cbdf234280 state: up speed: 1 Mbps duplex: unknown
mac: 02:42:38:64:12:9e
  IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown
mac: 02:42:3c:ad:bd:5b
  IF-ID-3: veth103090f state: up speed: 1 Mbps duplex: full
mac: 42:16:28:32:fc:93
  IF-ID-4: veth87768e9 state: up speed: 1 Mbps duplex: full
mac: 0e:41:45:ea:c8:32
  IF-ID-5: vethc256878 state: up speed: 1 Mbps duplex: full
mac: 4e:b7:f2:ba:cb:96
Bluetooth:
  Device-1: IMC Networks Wireless_Device type: USB driver: btusb
  Report: hciconfig ID: hci0 state: up address: 14:13:33:8C:7D:84 bt-v: 3.0
Drives:
  Local Storage: total: 5.55 TiB used: 2.65 TiB (47.8%)
  ID-1: /dev/nvme0n1 vendor: Silicon Power model: SPCC M.2 PCIe SSD
size: 3.73 TiB
  ID-2: /dev/sda vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB
Partition:
  ID-1: / size: 97.87 GiB used: 21.31 GiB (21.8%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot size: 1.9 GiB used: 410.1 MiB (21.1%) fs: ext4
dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 1.05 GiB used: 6.1 MiB (0.6%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) file: /swap.img
Sensors:
  System Temperatures: cpu: 55.0 C pch: 49.5 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 231 Uptime: 1h 8m Memory: 15.4 GiB used: 1.32 GiB (8.6%)
  Init: systemd runlevel: 5 Shell: Bash inxi: 3.3.13

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

Title:
  Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

Status in linux-meta-hwe-6.5 package in Ubuntu:
  New

Bug description:
  After server boots up, outbound network connectivity over wifi
  interface is okay but inbound is not.  Jellyfin app clients are unable
  to connect to Jellyfin server running on this server.  From my desktop
  PC I cannot ping the ip for the wifi interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Jan 11 22:13:46 2024
  InstallationDate: Installed on 2023-10-29 (74 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049107] [NEW] Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

2024-01-11 Thread Michael Hankins

Public bug reported:

After server boots up, outbound network connectivity over wifi interface
is okay but inbound is not.  Jellyfin app clients are unable to connect
to Jellyfin server running on this server.  From my desktop PC I cannot
ping the ip for the wifi interface.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Jan 11 22:13:46 2024
InstallationDate: Installed on 2023-10-29 (74 days ago)
InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230810)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-meta-hwe-6.5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy uec-images

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

Title:
  Trouble with wifi interface after upgrade from 6.2 to 6.5 hwe kernel

Status in linux-meta-hwe-6.5 package in Ubuntu:
  New

Bug description:
  After server boots up, outbound network connectivity over wifi
  interface is okay but inbound is not.  Jellyfin app clients are unable
  to connect to Jellyfin server running on this server.  From my desktop
  PC I cannot ping the ip for the wifi interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Jan 11 22:13:46 2024
  InstallationDate: Installed on 2023-10-29 (74 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS

2024-01-08 Thread Michael Reed

CONFIG_SCSI_MPI3MR in Makefile
  d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API
  7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints
  65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS
  c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast
  f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0
  2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug
  f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time
  130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload
  bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code
  f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA
  7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels
  47cd930ee6ae scsi: mpi3mr: Support new power management framework
  ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files
  5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler()
  a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture()
  7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects
  2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset
  176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks
  2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds
  7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL
  626665e9c38d scsi: mpi3mr: Get target object based on rphy
  e22bae30667a scsi: mpi3mr: Add expander devices to STL
  c4723e68a0d8 scsi: mpi3mr: Enable STL on HBAs where multipath is disabled
  42fc9fee116f scsi: mpi3mr: Add helper functions to manage device's port
  125ad1e6b445 scsi: mpi3mr: Add helper functions to retrieve device objects
  fc7212fd3100 scsi: mpi3mr: Add framework to add phys to STL
  7188c03ff884 scsi: mpi3mr: Enable Enclosure device add event
  64a8d9315b85 scsi: mpi3mr: Add helper functions to retrieve config pages
  32d457d5a2af scsi: mpi3mr: Add framework to issue config requests
  3b73c45e6fd2 scsi: mpi3mr: Add config and transport related debug flags
  502f4c18704d scsi: mpi3mr: Delete a stray tab
  2a8a0147cb52 scsi: mpi3mr: Unlock on error path
  cf1ce8b71524 scsi: mpi3mr: Reduce VD queue depth on detecting throttling
  f10af057325c scsi: mpi3mr: Resource Based Metering
  d29ea7b71621 scsi: mpi3mr: Increase cmd_per_lun to 128
  465191d6526a scsi: mpi3mr: Enable shared host tagset
  1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc
  4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings
  9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes
  e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes
  bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails
  a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init()
  256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR
  2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset
  1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s
  
  [ Where problems could occur ]
  
  [ Other Info ]
  
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_update3

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

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

Title:
  [SRU][Ubuntu] mpi3mr: Include the latest patchset from upstream into
  22.04.4/later LTS

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  [Impact]
  This BUG is created to integrate the latest mpi3mr driver available upstream 
into the upcoming Ubuntu LTS OS inbox driver.
  - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 
8.0.0.69.0. which is
    considerably the base driver + management app support.
  - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has 
various important features and
    critical bugs.

  [Fix]
  Please include below the latest mpi3mr upstream patset:

  git online commit id and description:

  f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O
  144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap
  2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add()
  2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain 
frame allocation
  a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002)
  b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const
  1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0
  e74f2fbd8b06 scsi: mpi3mr: Update copyright year
  80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation w

[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs

2023-12-30 Thread Michael Baehr

It looks like there is one person charged with maintaining this package,
and we're still in the holidays. I agree this has taken too long and it
sounds like there should be more resources assigned but I will wait for
Dimitri to finish his work. The Ubuntu ZFS package has quite a few
customizations, mostly to work with things like zsys and full disk
encryption. I am sure he is working to get it just right.

For the time being, I've been running Satadru's "zfs-experimental"
package for Mantic, but the missing zsys/fde support does mean I have to
manually unlock my drive from the initramfs rescue shell. You can find
it here: https://launchpad.net/~satadru-umich/+archive/ubuntu/zfs-
experimental

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  Incomplete
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

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


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

[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

2023-12-12 Thread Michael Reed

In the latest branch CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is no longer
disabled

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

** Description changed:

  [Impact]
  Description of problem:
  
  Observed device_dax related probe errors in dmesg when HBM CPU is set to
  flat mode.  Duplicate device_dax ids were created and hence probing is
  failing.
  
  How reproducible:
  Frequently
  
  Version-Release
  Release:22.04.2, 22.10
  
  [Test Case]
  
  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
  
  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.
  
  Expected results:
  Dummy/duplicate devices should not create.
  
  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
  
  By default this is enabled, but it is causing an issue reconfiguring device 
dax memory, thus
  it is being disabled.
  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
  Set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=N
  
  [Where problems could occur]
  
  [Other Info]
+ 
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
+ 
  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].
  
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"devdax" ---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    }
  ]
  root@ubuntu:/home/ubuntu# dmesg | grep -i error
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748902] device_dax: probe of dax3.0 failed with error -16
  
  After reconfig-device devdax to system-ram below are the results:
  ---
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
  {
    "chardev":"dax0.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":2,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
  {
    "chardev":"dax1.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":3,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax4.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"system-ram",---> Converted from devdax - system-ram
  "online_memblocks":32,
  "total_memblocks":32,
  "movable":true
    },
    {
  "chardev":"dax5.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",

[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup

2023-12-12 Thread Michael Reed

** Description changed:

  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:
  
  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...
  
  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
  
  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.
  
  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.
  
  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?
  
  [Test Plan]
  
  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled
  
  2.Install OS
  
  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled
  
  4.Rebooting will reproduce this issue
  
  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
- * The regression leads to the boot failure (cannot boot info OS 
successfully). 
+ * The regression leads to the boot failure (cannot boot info OS successfully).
  
  [ Other Info ]
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
+ 
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022

** Description changed:

  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:
  
  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...
  
  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
  
  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.
  
  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.
  
  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?
  
  [Test Plan]
  
  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled
  
  2.Install OS
  
  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled
  
  4.Rebooting will reproduce this issue
  
  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
  * The regression leads to the boot failure (cannot boot info OS successfully).
  
  [ Other Info ]
- 
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
+ 
  
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022

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

Title:
  [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
  in UEFI setup

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:

  [  166.605518] DMAR: VT-d detected Invalidation Queue

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

2023-12-12 Thread Michael Reed

Here is the test kernel for Mantic

https://people.canonical.com/~mreed/cisco/lp_2036777/mantic/

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  924cb24df4fcscsi: fnic: Stop using the SCSI pointer
  b559b99a5c081   scsi: fnic: Replace DMA mask of 64 bits with 47 bits
  5a43b07a87835   scsi: fnic: Replace return codes in 
fnic_clean_pending_aborts()
  15924b0503630   scsi: fnic: Replace sgreset tag with max_tag_id
  514f0c400bde6   scsi: fnic: Fix sg_reset success path

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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

  Mantic
  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777

  Links to first 3 patches
  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

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


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

Re: [Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble

2023-12-11 Thread Michael Hudson-Doyle

> Is only asking kernel to scan the device; to then generate "kernel udev"
> events; for then udev to wakeup and process/emit "udev udev" events; and
> create the required device nodes.
>

It's not udev that creates nodes like /dev/loop1p1 though is it? That's
devtmpfs surely.

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable in noble

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

2023-12-08 Thread Michael Gödderz

Update. 
After last "apt upgrade" and kernel 6.2.0-37-generic everything is working fine 
on my notebook.

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

These patches were also needed.

924cb24df4fcscsi: fnic: Stop using the SCSI pointer
b559b99a5c081 scsi: fnic: Replace DMA mask of 64 bits with 47 bits

** Description changed:

[Impact]

fnic_clean_pending_aborts() was returning a non-zero value
irrespective of failure or success.
This caused the caller of this function to assume that the
device reset had failed, even though it would succeed in
most cases. As a consequence, a successful device reset
would escalate to host reset.

sgreset is issued with a scsi command pointer.
The device reset code assumes that it was issued
on a hardware queue, and calls block multiqueue
layer. However, the assumption is broken, and
there is no hardware queue associated with the
sgreset, and this leads to a crash due to a
null pointer exception.

[Fix]
Fix the code to use the max_tag_id as a tag
which does not overlap with the other tags
issued by mid layer.

Below are the kernel patches which picked for the newer version of fins
driver.

https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

[Test Plan]
Tested by running FC traffic for a few minutes,
and by issuing sgreset on the device in parallel.
Without the fix, the crash is observed right away.
With this fix, no crash is observed.

sg_reset performs a device reset/lun reset on a lun.
Since it is issued by the user, it does not come into the
driver with a tag or a queue id.
Fix the fnic driver to create an io_req and use a scsi command tag.
Fix the ITMF path to special case the sg_reset response.

[ Where problems could occur ]

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

** Description changed:

[Impact]

[Fix]
Fix the code to use the max_tag_id as a tag
which does not overlap with the other tags
issued by mid layer.

Below are the kernel patches which picked for the newer version of fins
driver.

- https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
+ 924cb24df4fcscsi: fnic: Stop using the SCSI pointer
+ b559b99a5c081 scsi: fnic: Replace DMA mask of 64 bits with 47 bits
+ 5a43b07a87835 scsi: fnic: Replace return codes in
fnic_clean_pending_aborts()
+ 15924b0503630 scsi: fnic: Replace sgreset tag with max_tag_id
+ 514f0c400bde6 scsi: fnic: Fix sg_reset success path

- https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
-
- https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

[Test Plan]
Tested by running FC traffic for a few minutes,
and by issuing sgreset on the device in parallel.
Without the fix, the crash is observed right away.
With this fix, no crash is observed.

[ Where problems could occur ]

[ Other Info ]

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

- Mantic
-
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777
+
+ Links to first 3 patches
+ https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
+ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
+ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

** Description changed:

[Impact]

sgreset is issued with a scsi command pointer.
The device reset code assumes that it was issued
on a hardware queue, and calls block multiqueue

[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup

I created a 6.2 test kernel for Lunar.Please test

https://people.canonical.com/~mreed/lenovo/lp_2020022_vmd/lunar/12062023/

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

Title:
  [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
  in UEFI setup

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:

  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...

  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.

  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.

  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.

  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?

  [Test Plan]

  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled

  2.Install OS

  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled

  4.Rebooting will reproduce this issue

  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
  * The regression leads to the boot failure (cannot boot info OS 
successfully). 

  [ Other Info ]
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022

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


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

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

** Changed in: linux (Ubuntu Noble)
   Status: Incomplete => Fix Released

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

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  In Progress
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Jeff Lane  (bladernr)
   Status: 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/2020022

Title:
  [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
  in UEFI setup

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic 
leads to the system reboot. The following log is shown:

  [  166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
  [  166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID 
  [  166.612445] DMAR: VT-d detected Invalidation Completion Error: SID 
  [  166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
  [  166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
  ...

  Additional info:
    * The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.

  Debugging info and fix commit info:
    * `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd: 
Clean up domain before enumeration"). The root cause is that VMD driver tries 
to clear a PCI configuration space range when resetting a VMD domain 
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
 which leads to the failure.

  [Fix]
    * Another `git bisect` indicates the fix commit is 20f3337d350c ("x86: 
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this 
commit can fix the issue.

  Would it be possible to include the commit 20f3337d350c in Ubuntu
  22.04.2/23.10 kernel?

  [Test Plan]

  Reproduce Step
  1.Disable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Disabled

  2.Install OS

  3.Enable Intel VMD in BIOS settings
     System Settings --> Devices and I/O Ports --> Intel VMD technology --> 
Enable/Disable Intel VMD : Enabled

  4.Rebooting will reproduce this issue

  [ Where problems could occur ]
  * Lenovo SE350 server and Lenovo SR850 v2 server
  * The regression leads to the boot failure (cannot boot info OS 
successfully). 

  [ Other Info ]
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022

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


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

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

2023-12-05 Thread Michael Reed

Here is a test kernel for Jammy.

https://people.canonical.com/~mreed/cisco/lp_2036777/

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
 Assignee: Michael Reed (mreed8855)
   Status: Incomplete

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

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

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

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

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Incomplete
Status in linux source package in Noble:
  Incomplete

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS

2023-12-01 Thread Michael Reed

This patch is also needed for a clean build.

3d8fa78ebd61   scsi: scsi_transport_sas: Add 22.5 Gbps link rate
definitions

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

Title:
  [Ubuntu] mpi3mr: Include the latest patchset from upstream into
  22.04.1/later LTS

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  This BUG is created to integrate the latest mpi3mr driver available upstream 
into the upcoming Ubuntu LTS OS inbox driver.
  - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 
8.0.0.69.0. which is 
considerably the base driver + management app support.  
  - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has 
various important features and 
critical bugs.

  
  Please include below the latest mpi3mr upstream patset: 

  
  git online commit id and description:

  f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O
  f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O
  144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap
  2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add()
  2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain 
frame allocation
  a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002)
  b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const
  1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0
  e74f2fbd8b06 scsi: mpi3mr: Update copyright year
  80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings
  e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27
  f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target 
is removed
  22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds
  23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset
  3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault
  ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove()
  c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc()
  d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove()
  d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove()
  7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak
  f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak
  8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash
  4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails
  ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init 
path
  0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init
  5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging 
is enabled
  02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt
  66b381d874fa scsi: mpi3mr: Remove unneeded version.h include
  e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization
  339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes
  eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi
  fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()
  ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN
  f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile
  d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API
  7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints
  65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS
  c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast
  f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0
  2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug
  f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time
  130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload
  bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code
  f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA
  7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels
  47cd930ee6ae scsi: mpi3mr: Support new power management framework
  ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files
  5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler()
  a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture()
  7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects
  2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset
  176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks
  2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds
  7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL
  626665e9c38d scsi: mpi3mr: Get target object based on rphy

[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS

2023-12-01 Thread Michael Reed

Here is the test kernel.
https://people.canonical.com/~mreed/dell/lp_2029905_mpi3mr/

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

Title:
  [Ubuntu] mpi3mr: Include the latest patchset from upstream into
  22.04.1/later LTS

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Lunar:
  Won't Fix
Status in linux source package in Mantic:
  Fix Committed

Bug description:
  This BUG is created to integrate the latest mpi3mr driver available upstream 
into the upcoming Ubuntu LTS OS inbox driver.
  - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 
8.0.0.69.0. which is 
considerably the base driver + management app support.  
  - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has 
various important features and 
critical bugs.

  
  Please include below the latest mpi3mr upstream patset: 

  
  git online commit id and description:

  f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O
  f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O
  144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap
  2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add()
  2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain 
frame allocation
  a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002)
  b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const
  1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0
  e74f2fbd8b06 scsi: mpi3mr: Update copyright year
  80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings
  e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27
  f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target 
is removed
  22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds
  23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset
  3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault
  ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove()
  c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc()
  d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove()
  d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove()
  7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak
  f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak
  8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash
  4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails
  ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init 
path
  0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init
  5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging 
is enabled
  02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt
  66b381d874fa scsi: mpi3mr: Remove unneeded version.h include
  e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization
  339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes
  eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi
  fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info()
  ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN
  f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile
  d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API
  7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints
  65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS
  c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast
  f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0
  2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug
  f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time
  130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload
  bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code
  f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA
  7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels
  47cd930ee6ae scsi: mpi3mr: Support new power management framework
  ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files
  5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler()
  a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture()
  7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects
  2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset
  176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks
  2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds
  7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL
  626665e9c38d scsi: mpi3mr: Get target object based on rphy
  e22bae30667a scsi: mpi3mr: Add expander

[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

2023-11-10 Thread james michael

In the ever-evolving world of social media, Instagram remains a
powerhouse for creativity and self-expression. With millions of users
sharing their stories to the https://insta-fonts.com/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-41.61 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions


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

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

2023-11-08 Thread Michael Reed

The first patch is already in Jammy

commit 06adda263bd3776b019f282318efe18dd5bfa173
Author: Karan Tilak Kumar 
Date:   Thu Jul 27 12:39:19 2023 -0700

scsi: fnic: Replace return codes in fnic_clean_pending_aborts()

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

commit 5a43b07a87835660f91d88a4db11abfea8c523b7 upstream.

fnic_clean_pending_aborts() was returning a non-zero value irrespective of
failure or success.  This caused the caller of this function to assume that
the device reset had failed, even though it would succeed in most cases. As
a consequence, a successful device reset would escalate to host reset.

Reviewed-by: Sesidhar Baddela 
Tested-by: Karan Tilak Kumar 
Signed-off-by: Karan Tilak Kumar 
Link: https://lore.kernel.org/r/20230727193919.2519-1-karti...@cisco.com
Signed-off-by: Martin K. Petersen 
Signed-off-by: Greg Kroah-Hartman 
Signed-off-by: Kamal Mostafa 
Signed-off-by: Stefan Bader 

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

2023-11-08 Thread Michael Reed

** Summary changed:

- [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal
+ [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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


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

[Kernel-packages] [Bug 1310402] Re: Userland depends on ionice idle but default scheduler is "deadline".

2023-10-26 Thread Michael Mess

Finally I have sent the processes stealing I/O throughput a STOP signal (kill 
-19), 
and voila: The I/O througput of the mv command increased from ~2 Mb/s to ~75 
Mb/s.

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

Title:
  Userland depends on ionice idle but default scheduler is "deadline".

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Userland depends upon the idle feature of the CFQ scheduler, this can
  lead to extreme desktop sluggishness with the default deadline
  scheduler due to IO blocking.

  In my case, the KDE baloo indexer was indexing all of my files, and
  making other desktop processes block.  The baloo processes are set to
  idle IO priority to avoid this problem but this was not being honored.

  From the information I have found online and in the ionice man page,
  the idle priority only is useful with the CFQ scheduler.

  KDE Baloo indexer sets it's processes to use "idle" priority

  the man-db cronjobs also use idle priority
  root@sirius:/etc# grep idle cron.daily/man-db 
  iosched_idle=
  iosched_idle='--iosched idle'
  --oknodo --chuid man $iosched_idle -- -c \
$iosched_idle \

  The compiled in default scheduler is "deadline"
  root@sirius:/boot# grep DEFAULT_IOSCHED config-3.13.0-24-generic 
  CONFIG_DEFAULT_IOSCHED="deadline"

  from the ionice man page:
  Linux supports I/O scheduling priorities and classes since 2.6.13 with the 
CFQ I/O scheduler.

  root@sirius:/boot# uname -a
  Linux sirius 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.24.28
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zmc2658 F pulseaudio
zmc3010 F pulseaudio
   /dev/snd/controlC0:  zmc2658 F pulseaudio
zmc3010 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Apr 20 17:23:28 2014
  HibernationDevice: RESUME=UUID=dea47071-fda3-4725-a9c5-1f4fc531e6ef
  InstallationDate: Installed on 2014-04-18 (2 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  MachineType: Acer Aspire 7551
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire 7551
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd10/26/2010:svnAcer:pnAspire7551:pvrV1.15:rvnAcer:rnAspire7551:rvrV1.15:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 7551
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1310402] Re: Userland depends on ionice idle but default scheduler is "deadline".

2023-10-26 Thread Michael Mess

I have experienced this also on Ubuntu 16.04.7 LTS when I wanted to move
1,5 TB data to an external USB3 disk.

When I started the mv command it performed well until I have noticed that 
BackupPC and updatedb.mlocate woke up to do plenty of disk activity, slowing 
down the source disk of the mv command.
Then I used ionice to set the priority of those processes to "idle" and the mv 
to "rt/4" priority in the hope that the mv will be able to read at maximum 
speed while the idle processes will have to wait most of the time until the mv 
process has finished.

But the performance of the mv process didn't increase as expected.

Both, source and target disks are spinning disks, not SSDs.

I would expect that it should be possible to force the linux kernel to process 
the mv command to be done in maximum speed while other processes should not be 
able to steal I/O throughput until the mv is done.
I could have killed the other processes, but this is not what I wanted to do 
for that.

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

Title:
  Userland depends on ionice idle but default scheduler is "deadline".

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Userland depends upon the idle feature of the CFQ scheduler, this can
  lead to extreme desktop sluggishness with the default deadline
  scheduler due to IO blocking.

  In my case, the KDE baloo indexer was indexing all of my files, and
  making other desktop processes block.  The baloo processes are set to
  idle IO priority to avoid this problem but this was not being honored.

  From the information I have found online and in the ionice man page,
  the idle priority only is useful with the CFQ scheduler.

  KDE Baloo indexer sets it's processes to use "idle" priority

  the man-db cronjobs also use idle priority
  root@sirius:/etc# grep idle cron.daily/man-db 
  iosched_idle=
  iosched_idle='--iosched idle'
  --oknodo --chuid man $iosched_idle -- -c \
$iosched_idle \

  The compiled in default scheduler is "deadline"
  root@sirius:/boot# grep DEFAULT_IOSCHED config-3.13.0-24-generic 
  CONFIG_DEFAULT_IOSCHED="deadline"

  from the ionice man page:
  Linux supports I/O scheduling priorities and classes since 2.6.13 with the 
CFQ I/O scheduler.

  root@sirius:/boot# uname -a
  Linux sirius 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.24.28
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zmc2658 F pulseaudio
zmc3010 F pulseaudio
   /dev/snd/controlC0:  zmc2658 F pulseaudio
zmc3010 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Apr 20 17:23:28 2014
  HibernationDevice: RESUME=UUID=dea47071-fda3-4725-a9c5-1f4fc531e6ef
  InstallationDate: Installed on 2014-04-18 (2 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  MachineType: Acer Aspire 7551
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire 7551
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd10/26/2010:svnAcer:pnAspire7551:pvrV1.15:rvnAcer:rnAspire7551:rvrV1.15:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 7551
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 2039894] [NEW] USB-C 3.2 port registering as USB 2.0

2023-10-19 Thread Michael Black

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

Public bug reported:

When I plug in USB 3.0/3.1/3.2 devices into system, it is always
registering at USB 2.0 speeds.

mblack@pro:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 7: Dev 4, If 0, Class=Mass Storage, Driver=uas, 480M
|__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

Port 7: Dev 4 is a SanDisk Extreme Pro Portable SSD which is a USB 3.2
2x2 drive.  This is connected via USB-C port.   When same drive is
connected via USB-A cable, device connect at 1M speed. This is
consistent with all USB 3.x devices.

mblack@pro:~$ lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
|__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=uas, 1M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M


mblack@pro:~$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-35-generic 6.2.0-35.35~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:17:22 2023
InstallationDate: Installed on 2023-08-13 (67 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** This bug has been marked a duplicate of bug 1991028
   USB-C 3.x port running at 2.0 speeds

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

Title:
  USB-C 3.2 port registering as USB 2.0

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

Bug description:
  When I plug in USB 3.0/3.1/3.2 devices into system, it is always
  registering at USB 2.0 speeds.

  mblack@pro:~$ lsusb -t
  /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
  /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 7: Dev 4, If 0, Class=Mass Storage, Driver=uas, 480M
  |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

  Port 7: Dev 4 is a SanDisk Extreme Pro Portable SSD which is a USB 3.2
  2x2 drive.  This is connected via USB-C port.   When same drive is
  connected via USB-A cable, device connect at 1M speed. This is
  consistent with all USB 3.x devices.

  mblack@pro:~$ lsusb -t
  /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
  /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 2M/x2
  |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=uas, 1M
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

  
  mblack@pro:~$ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-35-generic 6.2.0-35.35~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:17:22 2023
  InstallationDate: Installed on 2023-08-13 (67 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2

[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

Ah no it's a bit simpler than that https://github.com/util-linux/util-
linux/issues/2528.

--disable-libmount-mountfd-support looking better tbh.

** Bug watch added: github.com/util-linux/util-linux/issues #2528
   https://github.com/util-linux/util-linux/issues/2528

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions


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

[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

So the cause of this, I am fairly sure, is the new "libmount-mountfd"
support in util-linux which seems to have the consequence that "mount -o
remount $mountpoint" fails for an overlay that references paths no
longer available in the current mount namespace.

You can see the discussion of a similar-but-not-the-same issue here
https://github.com/util-linux/util-linux/issues/1992

I'm trying to come up with a reproducer but I have to head afk now. I'll
file a bug upstream when I get that done.

Maybe we should build util-linux with --disable-libmount-mountfd-support
for now (bit late in the release cycle to be uploading util-linux
though...)


** Bug watch added: github.com/util-linux/util-linux/issues #1992
   https://github.com/util-linux/util-linux/issues/1992

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions


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

[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

** Also affects: util-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/2037417

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  New
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed
Status in util-linux source package in Mantic:
  New

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions


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

[Kernel-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems

** Tags added: foundaitions-todo

** Tags removed: foundaitions-todo
** Tags added: foundations-todo

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

Title:
  mantic images after 20230917 are failing to deploy with failure to
  mount root and kernel filesystems

Status in maas-images:
  New
Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Mantic:
  Incomplete
Status in systemd source package in Mantic:
  Confirmed

Bug description:
  Mantic arm64 deploys started failing on Sept 18th with:

  [   41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root 
and Kernel File Systems...
   Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File 
Systems...
  [   41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug 
All udev Devices...
   Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev 
Devices...
  [   41.964758] systemd[1]: Started systemd-journald.service - Journal Service.
  [[0;32m  OK  [0m] Started [0;1;39msystemd-journald.service[0m - Journal 
Service.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message 
Queue File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug 
File System.
  [[0;32m  OK  [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace 
File System.
  [[0;32m  OK  [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console 
keyboard layout.
  [[0;32m  OK  [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static 
Device Nodes.
  [[0;32m  OK  [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or 
progress polling.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel 
Module configfs.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel 
Module dm_mod.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel 
Module drm.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel 
Module efi_pstore.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel 
Module fuse.
  [[0;32m  OK  [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel 
Module loop.
  [[0;32m  OK  [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load 
Kernel Modules.
  [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and 
Kernel File Systems.
  See 'systemctl status systemd-remount-fs.service' for details.

  After this many other services and cloud-init fails. See the full
  kopter-0918.log. For comparison, a log from the prior day's test is
  also attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2037417/+subscriptions


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

[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

2023-10-04 Thread james michael

The information you provided appears to be related to a specific version
of the Linux kernel in the Ubuntu operating system's "proposed"
repository. The "proposed" repository in Ubuntu is where packages are
initially placed for testing before they are moved to the stable release
you can visit to the https://downloadertwitter.com/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-41.61 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions


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

[Kernel-packages] [Bug 2036777] Re: fnic driver on needs to be updated to 1.6.0.57 on Focal

2023-10-03 Thread Michael Reed

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
 Assignee: Michael Reed (mreed8855)
   Status: Incomplete

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

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

** Summary changed:

- fnic driver on needs to be updated to 1.6.0.57 on Focal
+ [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal

** Description changed:

+ [Impact]
+ 
  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.
- 
  
  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.
  
+ [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.
  
+ Below are the kernel patches which picked for the newer version of fins
+ driver.
+ 
+ https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
+ 
+ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
+ 
+ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/
+ 
+ [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.
  
  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.
  
- below are the kernel patches which picked for the newer version of fins
- driver.
+ [ Where problems could occur ]
  
- 
- https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/
- 
- https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/
- 
- https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/
+ [ Other Info ]

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Michael Reed (mreed8855)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

Title:
  [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  New
Status in linux source package in Lunar:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  [Impact]

  fnic_clean_pending_aborts() was returning a non-zero value
  irrespective of failure or success.
  This caused the caller of this function to assume that the
  device reset had failed, even though it would succeed in
  most cases. As a consequence, a successful device reset
  would escalate to host reset.

  sgreset is issued with a scsi command pointer.
  The device reset code assumes that it was issued
  on a hardware queue, and calls block multiqueue
  layer. However, the assumption is broken, and
  there is no hardware queue associated with the
  sgreset, and this leads to a crash due to a
  null pointer exception.

  [Fix]
  Fix the code to use the max_tag_id as a tag
  which does not overlap with the other tags
  issued by mid layer.

  Below are the kernel patches which picked for the newer version of
  fins driver.

  https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/

  https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/

  [Test Plan]
  Tested by running FC traffic for a few minutes,
  and by issuing sgreset on the device in parallel.
  Without the fix, the crash is observed right away.
  With this fix, no crash is observed.

  sg_reset performs a device reset/lun reset on a lun.
  Since it is issued by the user, it does not come into the
  driver with a tag or a queue id.
  Fix the fnic driver to create an io_req and use a scsi command tag.
  Fix the ITMF path to special case the sg_reset response.

  [ Where problems could occur ]

  [ Other Info ]

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705363/+files/version.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

** Attachment added: "lspcivvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705361/+files/lspcivvnn.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705362/+files/uname-a.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

As the kernel version that has the issue does not boot, the commands as per 
https://wiki.ubuntu.com/Kernel/Bugs
were collected with an older kernel!


** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036271/+attachment/5705360/+files/dmesg.log

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

An update to this bug.
In the meantime a newer kernel version 6.2.0-33-generic is available, so i've
installed it via "apt update / apt upgrade". Unfortunately it shows the same
behaviour as the 6.2.0.32 version. So it's not possible to boot this notebook
with the newer kernel versions.

Additional info:
For some testings i've added 2 partitions on the notebook and installed kubuntu
22.04.02 and as well from latest image kubuntu 22.04.3. (Only minimal system
and with and without third-party drivers) All installations work fine after
installation, but when i do an apt upgrade the 6.2.0-33-generic kernel will not
boot.

Not sure if this is maybe interesting:
As in my initial installation the 6.2.0-31-generic kernel is working fine, i've
tried to install this kernel on the test installations as well. Normal boot
with the kernel 6.2.0.31 does NOT work! But in recovery mode it reaches the
screen were you can select "resume" to proceed with boot. The last one works
then, only e.g. network is missing.

Btw. I have another but old notebook ( from 2016 ), here everything works fine
with this kernels.

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

Title:
Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
on a Lenovo Ideapad Flex 5 14ALC05

The Ubuntu splash screen appear with the loader but the boot process
is stuck there (with the loader still animating)

No problem when booting with the kernel 6.2.0-26-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 19:22:42 2023
InstallationDate: Installed on 2021-08-26 (750 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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

[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

2023-09-22 Thread Michael Reed

** Description changed:

  [Impact]
  Description of problem:
  
  Observed device_dax related probe errors in dmesg when HBM CPU is set to
  flat mode.  Duplicate device_dax ids were created and hence probing is
  failing.
  
  How reproducible:
  Frequently
  
  Version-Release
  Release:22.04.2, 22.10
  
  [Test Case]
  
  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
  
  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.
  
  Expected results:
  Dummy/duplicate devices should not create.
  
  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
  
  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
  Set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=N
  
  [Where problems could occur]
+ 
  [Other Info]
  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].
  
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"devdax" ---> HBM CPU 1, This we can change the devdax 
to
  system-ram
    }
  ]
  root@ubuntu:/home/ubuntu# dmesg | grep -i error
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748902] device_dax: probe of dax3.0 failed with error -16
  
  After reconfig-device devdax to system-ram below are the results:
  ---
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
  {
    "chardev":"dax0.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":2,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
  {
    "chardev":"dax1.0",
    "size":"64.00 GiB (68.72 GB)",
    "target_node":3,
    "align":2097152,
    "mode":"system-ram",
    "online_memblocks":32,
    "total_memblocks":32,
    "movable":true
  }
  reconfigured 1 device
  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax4.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"system-ram",---> Converted from devdax - system-ram
  "online_memblocks":32,
  "total_memblocks":32,
  "movable":true
    },
    {
  "chardev":"dax5.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"system-ram", ---> Converted from devdax - system-ram
  "online_memblocks":32,
  "total_memblocks":32,
  "movable":true
    }
  ]
  
  root@ubuntu:/home/ubuntu# dmesg | grep -i dax
  [   12.748880] device_dax dax2.0: mapping0:

[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate device_dax ids created and hence probing is failing.

2023-09-22 Thread Michael Reed

bled"
    },
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"system-ram",---> Converted from devdax - system-ram
  "online_memblocks":32,
  "total_memblocks":32,
  "movable":true
    },
    {
  "chardev":"dax5.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax2.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax3.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3, > Duplicate device
  "align":2097152,
  "mode":"devdax",
  "state":"disabled"
    },
    {
  "chardev":"dax0.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":2,
  "align":2097152,
  "mode":"system-ram", ---> Converted from devdax - system-ram
  "online_memblocks":32,
  "total_memblocks":32,
  "movable":true
    }
  ]
  
  root@ubuntu:/home/ubuntu# dmesg | grep -i dax
  [   12.748880] device_dax dax2.0: mapping0: 0x208000-0x307fff could 
not reserve range
  [   12.748884] device_dax: probe of dax2.0 failed with error -16
  [   12.748901] device_dax dax3.0: mapping0: 0x508000-0x607fff could 
not reserve range
  [   12.748902] device_dax: probe of dax3.0 failed with error -16
  [  812.677056] device_dax dax4.0: mapping0: 0x208000-0x307fff could 
not reserve range
  [  812.677070] device_dax: probe of dax4.0 failed with error -16
  [  821.092762] device_dax dax5.0: mapping0: 0x508000-0x607fff could 
not reserve range
  [  821.092774] device_dax: probe of dax5.0 failed with error -16

** Information type changed from Private to Public

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Michael Reed (mreed8855)

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

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

Title:
  [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.

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

Bug description:
  [Impact]
  Description of problem:

  Observed device_dax related probe errors in dmesg when HBM CPU is set
  to flat mode.  Duplicate device_dax ids were created and hence probing
  is failing.

  How reproducible:
  Frequently

  Version-Release
  Release:22.04.2, 22.10

  [Test Case]

  Steps to Reproduce:
  1. Set HBM cpu to flat mode in memory settings in BIOS.
  2. Boot to the OS.
  3. Perform OS warm boot cycle test.
  4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.

  Actual results:
  Observed device_dax related errors in dmesg, device Dax is creating 
dummy/duplicate devices and probe failing.

  Expected results:
  Dummy/duplicate devices should not create.

  [Fix]
  Upstream Fix
  
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/

  Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
  Set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=N

  [Where problems could occur]
  [Other Info]
  Additional info:
  SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should 
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4 
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is 
"mode":"devdax" which are actuall devadax to system-ram convertible devices. 
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of 
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0, 
5.0 etc..].

  root@ubuntu:/home/ubuntu# daxctl list -u
  [
    {
  "chardev":"dax1.0",
  "size":"64.00 GiB (68.72 GB)",
  "target_node":3,
  "align":2097152,
  "mode":"devdax"---> HBM CPU 1, This we can cha

[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen

** Project changed: snappy => snapd

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

Title:
  Raspberry Pi 3: a small rainbow square on the top right of screen

Status in snapd:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm working on the WD/nextcloud project, and found this issue

  Download the UC16 for Raspberry Pi 3 from 
http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz
  unxz , dd the image to sd card and boot up the system.
  There is a small rainbow square on top right of HDMI monitor.

  From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373
  If the voltage is under 4.65V, firmware displays a rainbow square on top 
right of screen and power LED goes off.
  But for UC16 the rainbow square is always there even the voltage is 
sufficient, but the power LED works properly.

  So I also check 
  1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi
  This RPI3 image works properly (if the voltage is not sufficient, rainbow 
square shows on the top right of screen, if it's sufficient,  
  no rainbow square shows up)
   2. Rasbian (jessie lite): 
https://downloads.raspberrypi.org/raspbian_lite_latest
  This works properly too, and the official Rasbian was released with the 
latest firmware, so the rainbow square changes to a 
  lighting icon

  It looks the firmware might be old in UC16? so the under-voltage
  warning doesn't display correctly.

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


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

[Kernel-packages] [Bug 1674509] Re: Unable to find bluetooth device on RPi3 running Ubuntu Core 16

** Project changed: snappy => snapd

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

Title:
  Unable to find bluetooth device on RPi3 running Ubuntu Core 16

Status in snapd:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  Invalid

Bug description:
  When tried to find/init bluetooth device from rp3 ubuntu core image by
  using bluetoothctl and bluez snaps, it returned "No default controller
  available" all the time.

  I'd tested it both from stable and daily images, but just got same
  failure.

  
http://cdimage.ubuntu.com/ubuntu-core/16/stable/current/ubuntu-core-16-pi3.img.xz
  http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/

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


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

[Kernel-packages] [Bug 1837209] Re: Splash screen fails to display on recent pi core18 images

** Project changed: snappy => snapd

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

Title:
  Splash screen fails to display on recent pi core18 images

Status in snapd:
  In Progress
Status in linux-raspi2 package in Ubuntu:
  In Progress

Bug description:
  The current core18 image [1] for the raspberry pi fails to display the
  "Core" splash screen on boot. This is because psplash fails to open
  the /dev/fb0 framebuffer device, because it doesn't exist. This
  appears to be due to a lack of supporting kernel modules in the
  initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present
  but are missing from the version I'm testing (pi-kernel
  4.15.0-1041.44, snap rev 42).

  Steps to reproduce:

  * Flash the image to a uSD card and boot the pi with it (preferably with a 
serial console attached).
  * Note screen remains black instead of displaying the familiar "Core" text 
under an Ubuntu logo.
  * If serial console is attached, note "Error opening /dev/fb0" in the output 
shortly after u-boot starts the kernel; this is output from psplash failing

  [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu-
  core-18-armhf+raspi3.img.xz

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


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

[Kernel-packages] [Bug 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU

** Project changed: snappy => snapd

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

Title:
  Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU

Status in snapd:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  The snapd/desktop/advocacy team are investigating the startup
  performance of running snaps.

  While doing this and comparing various distros (fedora, opensuse,
  ubuntu) on Igors reference hardware we noticed that fedora is
  substantially faster at starting snaps.

  After some research it turns out that they use the
  CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use
  CONFIG_SQUASHFS_DECOMP_SINGLE.

  I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes
  this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that
  the first run firefox startup went from 15s to 6s (!) on Igors
  reference hardware. Given the dramatic performance improvements we
  would like to get this option switched.

  However we need to be careful and double check that the results from
  https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue
  - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just
  mounting a snap would use up 131Mb or memory(!).

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


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

[Kernel-packages] [Bug 1653988] Re: no sound device in raspberry pi2 and 3

** Project changed: snappy => snapd

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

Title:
  no sound device in raspberry pi2 and 3

Status in Gadget snap for Raspberry Pi 2:
  Fix Committed
Status in Gadget snap for Raspberry Pi 3:
  Fix Committed
Status in snapd:
  Fix Committed
Status in linux-raspi2 package in Ubuntu:
  Invalid

Bug description:
  while snd-bcm2835.ko exists in the package snd.ko itself seems to be
  compiled in, only the oss sound modules seem to be there.

  wild guess: if snd-bcm2835 is a module, snd should be one as well to
  make alsa functional ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-pi2/+bug/1653988/+subscriptions


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

[Kernel-packages] [Bug 2029332] Re: Reboot command powers off the system

2023-09-19 Thread Michael Reed

sudo apt-cache search linux-generic-hwe
linux-generic-hwe-20.04 - Complete Generic Linux kernel and headers (dummy 
transitional package)
linux-generic-hwe-20.04-edge - Complete Generic Linux kernel and headers (dummy 
transitional package)
linux-generic-hwe-22.04 - Complete Generic Linux kernel and headers
linux-generic-hwe-22.04-edge - Complete Generic Linux kernel and headers


Try installing the latest 6.2  
sudo apt install linux-generic-hwe-22.04-edge


uname -a
Linux  6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep  7 
13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Reboot command powers off the system

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in linux-hwe-6.2 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  Issue: When a reboot (or init 6) command is issued the server shuts
  down instead.

  Expected behaviour: To reboot and NOT shutdown

  Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core
  count greater than 16 (like 24,28 or 32)

  Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15

  When the CPU count is 1, issue is not observed. When core count is
  less than 24 (like 16) issue not observed.

  [Fix]

  Problem introduced in v5.18 with commit:
  08f253ec3767 x86/cpu: Clear SME feature flag when not in use

  Fixes for the above:0
  9b040453d444 x86/smp: Dont access non-existing CPUID leaf
  1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust

  [Test Case]

  $ sudo reboot
  Server should reboot and not power off.

  [Where Problems Could Occur]

  The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines
  could be affected.

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


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

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

2023-09-17 Thread Michael Gödderz

Have the same issue with this kernel version 6.2.0-31-generic. Yesterday
tried to boot in recovery mode, then i could see some messages that the
kernel tried to connect to partitions e.g. /home that should be mounted
but failed to connect to. Today the boot process already stuck after USB
devices were detected.


Last kernel works fine!
uname -a
Linux michael-nb 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed 
Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

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

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2034033] Re: Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5

2023-09-05 Thread Michael Lueck

Ubuntu has release kernel version "6.2.0-32-generic #32~22.04.1-Ubuntu
SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64
GNU/Linux" which has successfully resolved this defect case.

One of the Samba maintainers told me I should check if SMB 1.0 protocol
was purposely removed from the Ubuntu 6.2.0-31 kernel version. This
evening I received that changelog, and could not see a hint of it being
removed by Ubuntu on purpose.

Then my system notified me of a yet newer kernel package. I pulled it
down, and was happy to see it has successfully resolved this defect.

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

Title:
  Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to
  vers=1.0 server cifs_mount failed w/return code = -5

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

Bug description:
  My Xubuntu system this weekend alerted me to a new kernel update being
  available. The following versions are the existing/working version:

  linux-image-6.2.0-26-generic  6.2.0-26.26~22.04.1

  And the updated/not working version:

  linux-image-6.2.0-31-generic  6.2.0-31.31~22.04.1

  And yes I run my system with:

  linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8

  
  Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs 
operation to our Samba NT4 PDC, results in the following output into syslog:

  Sep  4 08:03:24 jaakob kernel: [  107.703886] FS-Cache: Loaded
  Sep  4 08:03:24 jaakob kernel: [  107.824160] Key type cifs.spnego registered
  Sep  4 08:03:24 jaakob kernel: [  107.824169] Key type cifs.idmap registered
  Sep  4 08:03:24 jaakob kernel: [  107.824454] Use of the less secure dialect 
vers=1.0 is not recommended unless required for access to very old servers
  Sep  4 08:03:24 jaakob kernel: [  107.824454]
  Sep  4 08:03:24 jaakob kernel: [  107.824457] CIFS: VFS: Use of the less 
secure dialect vers=1.0 is not recommended unless required for access to very 
old servers
  Sep  4 08:03:24 jaakob kernel: [  107.824460] CIFS: Attempting to mount 
\\ldslnx01\data
  Sep  4 08:03:24 jaakob kernel: [  107.859554] CIFS: VFS: cifs_mount failed 
w/return code = -5

  And none of the Samba mounts will establish.

  Booting back to the prior 6.2.0-26 kernel version, Samba mounts work
  just fine.

  I use the following switches to the mount.cifs command in order to
  establish connections to our Samba NT4 PDC:

  "-o
  
credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0"

  
  That last vers= option was the last that needed to be added to continue 
making use of our Samba NT4 style PDC.

  Since it is a version upgrade of only the kernel, not Samba package, I
  would not think that yet another switch to mount.cifs was needed in
  order to continue connecting successfully. So did the latest Kernel
  update suddenly break Samba's mount.cifs vers=1.0 support?

  Nothing gets logged to our Samba server for the failed mount attempt.

  Booting for not back to the working 6.2.0-26 kernel version. Please
  kindly advise.

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


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

[Kernel-packages] [Bug 2034033] [NEW] Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to vers=1.0 server cifs_mount failed w/return code = -5

2023-09-04 Thread Michael Lueck

Public bug reported:

My Xubuntu system this weekend alerted me to a new kernel update being
available. The following versions are the existing/working version:

linux-image-6.2.0-26-generic  6.2.0-26.26~22.04.1

And the updated/not working version:

linux-image-6.2.0-31-generic  6.2.0-31.31~22.04.1

And yes I run my system with:

linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8


Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs operation 
to our Samba NT4 PDC, results in the following output into syslog:

Sep  4 08:03:24 jaakob kernel: [  107.703886] FS-Cache: Loaded
Sep  4 08:03:24 jaakob kernel: [  107.824160] Key type cifs.spnego registered
Sep  4 08:03:24 jaakob kernel: [  107.824169] Key type cifs.idmap registered
Sep  4 08:03:24 jaakob kernel: [  107.824454] Use of the less secure dialect 
vers=1.0 is not recommended unless required for access to very old servers
Sep  4 08:03:24 jaakob kernel: [  107.824454]
Sep  4 08:03:24 jaakob kernel: [  107.824457] CIFS: VFS: Use of the less secure 
dialect vers=1.0 is not recommended unless required for access to very old 
servers
Sep  4 08:03:24 jaakob kernel: [  107.824460] CIFS: Attempting to mount 
\\ldslnx01\data
Sep  4 08:03:24 jaakob kernel: [  107.859554] CIFS: VFS: cifs_mount failed 
w/return code = -5

And none of the Samba mounts will establish.

Booting back to the prior 6.2.0-26 kernel version, Samba mounts work
just fine.

I use the following switches to the mount.cifs command in order to
establish connections to our Samba NT4 PDC:

"-o
credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0"


That last vers= option was the last that needed to be added to continue making 
use of our Samba NT4 style PDC.

Since it is a version upgrade of only the kernel, not Samba package, I
would not think that yet another switch to mount.cifs was needed in
order to continue connecting successfully. So did the latest Kernel
update suddenly break Samba's mount.cifs vers=1.0 support?

Nothing gets logged to our Samba server for the failed mount attempt.

Booting for not back to the working 6.2.0-26 kernel version. Please
kindly advise.

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

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

Title:
  Ubuntu 22.04 update to 6.2.0-31 kernel version breaks mount.cifs to
  vers=1.0 server cifs_mount failed w/return code = -5

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

Bug description:
  My Xubuntu system this weekend alerted me to a new kernel update being
  available. The following versions are the existing/working version:

  linux-image-6.2.0-26-generic  6.2.0-26.26~22.04.1

  And the updated/not working version:

  linux-image-6.2.0-31-generic  6.2.0-31.31~22.04.1

  And yes I run my system with:

  linux-image-generic-hwe-22.04 6.2.0.31.31~22.04.8

  
  Booted to the 6.2.0-31 kernel version, attempting to do a mount.cifs 
operation to our Samba NT4 PDC, results in the following output into syslog:

  Sep  4 08:03:24 jaakob kernel: [  107.703886] FS-Cache: Loaded
  Sep  4 08:03:24 jaakob kernel: [  107.824160] Key type cifs.spnego registered
  Sep  4 08:03:24 jaakob kernel: [  107.824169] Key type cifs.idmap registered
  Sep  4 08:03:24 jaakob kernel: [  107.824454] Use of the less secure dialect 
vers=1.0 is not recommended unless required for access to very old servers
  Sep  4 08:03:24 jaakob kernel: [  107.824454]
  Sep  4 08:03:24 jaakob kernel: [  107.824457] CIFS: VFS: Use of the less 
secure dialect vers=1.0 is not recommended unless required for access to very 
old servers
  Sep  4 08:03:24 jaakob kernel: [  107.824460] CIFS: Attempting to mount 
\\ldslnx01\data
  Sep  4 08:03:24 jaakob kernel: [  107.859554] CIFS: VFS: cifs_mount failed 
w/return code = -5

  And none of the Samba mounts will establish.

  Booting back to the prior 6.2.0-26 kernel version, Samba mounts work
  just fine.

  I use the following switches to the mount.cifs command in order to
  establish connections to our Samba NT4 PDC:

  "-o
  
credentials=/home/mdlueck/.smbcredentials,uid=mdlueck,gid=mdlueck,dir_mode=0777,file_mode=0666,nobrl,vers=1.0"

  
  That last vers= option was the last that needed to be added to continue 
making use of our Samba NT4 style PDC.

  Since it is a version upgrade of only the kernel, not Samba package, I
  would not think that yet another switch to mount.cifs was needed in
  order to continue connecting successfully. So did the latest Kernel
  update suddenly break Samba's mount.cifs vers=1.0 support?

  Nothing gets logged to our Samba server for the failed mount attempt.

  Booting for not back to the working 6.2.0-26 kernel version. Please
  kindly

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

2023-07-19 Thread Michael Reed

I have created a test kernel can anyone provide feedback?

https://people.canonical.com/~mreed/misc/lp_1988711_lpfc_14_2_0_5/

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

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5

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

Bug description:
  [IMPACT/Justification]
  There are numerous bug fixes included in the more recent version of lpfc That 
Broadcom has asked to pull into Jammy and Kinetic to better support customers 
in the field who are using the GA kernel and cant or wont move to the HWE 
kernels.  These all are limited to the lpfc driver itself, no patches to core 
code are requested.

  [FIX]
  A few of these were already landed in Jammy, and all but 6 (ones landed in 
6.0 upstream) were already in Kinetic.

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

[Kernel-packages] [Bug 2025500] Re: package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11

2023-06-30 Thread Michael Pelley

Will cause kernel panic if used. Cannot find root fs.

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

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

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12
  Uname: Linux 6.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jun 30 10:07:42 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-04-28 (63 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: dkms
  Title: package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

2023-06-16 Thread Michael Autry

Public bug reported:

running Handbrake overnight. In more found "System program problem
detected" window.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-23-generic 6.2.0-23.23
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mautry 2553 F wireplumber
 /dev/snd/controlC1:  mautry 2553 F wireplumber
 /dev/snd/seq:mautry 2550 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Jun 16 06:40:05 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
InstallationDate: Installed on 2023-05-07 (40 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: System76 Thelio Mira
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=750bb3c8-bb38-4ef7-9e8f-fe3aa87ee148 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: dkms
Title: package linux-image-6.2.0-23-generic 6.2.0-23.23 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2023
dmi.bios.release: 5.27
dmi.bios.vendor: System76
dmi.bios.version: F24b Z5
dmi.board.asset.tag: Default string
dmi.board.name: Thelio Mira
dmi.board.vendor: System76
dmi.board.version: thelio-mira-b3
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: System76
dmi.chassis.version: thelio-mira-b3
dmi.modalias: 
dmi:bvnSystem76:bvrF24bZ5:bd06/02/2023:br5.27:svnSystem76:pnThelioMira:pvrthelio-mira-b3:rvnSystem76:rnThelioMira:rvrthelio-mira-b3:cvnSystem76:ct3:cvrthelio-mira-b3:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Thelio Mira
dmi.product.sku: Default string
dmi.product.version: thelio-mira-b3
dmi.sys.vendor: System76

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


** Tags: amd64 apport-package lunar

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

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

Status in dkms package in Ubuntu:
  New

Bug description:
  running Handbrake overnight. In more found "System program problem
  detected" window.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-23-generic 6.2.0-23.23
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mautry 2553 F wireplumber
   /dev/snd/controlC1:  mautry 2553 F wireplumber
   /dev/snd/seq:mautry 2550 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jun 16 06:40:05 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  InstallationDate: Installed on 2023-05-07 (40 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: System76 Thelio Mira
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=750bb3c8-bb38-4ef7-9e8f-fe3aa87ee148 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: dkms
  Title: package linux-image-6.2.0-23-generic 6.2.0-23.23 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: System76
  dmi.bios.version: F24b Z5
  dmi.board.asset.tag: Default string
  dmi.board.name: Thelio Mira
  dmi.board.vendor: System76
  dmi.board.version: thelio-mira-b3
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76
  dmi.chassis.version: thelio-mira-b3
  dmi.modalias: 
dmi:bvnSystem76:bvrF24bZ5:bd06/02/2023:br5.27:svnSystem76:pnThelioMira:pvrthelio-mira-b3:rvnSystem76:rnThelioMira:rvrthelio-mira-b3:cvnSystem76:ct3:cvrthelio-mira-b3:skuDefaultstring:
  dmi.product.family: Z690 MB
  dmi.product.name: Thelio Mira
  dmi.product.sku: Default string
  dmi.product.version: thelio-mira-b3
  dmi.sys.vendor: System76

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


-- 
Mailing list:

[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 931353] Re: package linux-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.3

2023-06-05 Thread Michael Solonevich

I'm getting the same error with the higher version of linux-base. E:
/var/cache/apt/archives/linux-base_4.6_all.deb: trying to overwrite
'/usr/bin/perf', which is also in package linux-tools-common
5.15.0-73.80

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

Title:
  package linux-tools-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/perf', which is also in package linux-
  base 3.3

Status in linux package in Ubuntu:
  Won't Fix
Status in linux-base package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Won't Fix
Status in linux-base source package in Precise:
  Fix Released
Status in linux-meta source package in Precise:
  Invalid
Status in linux source package in Quantal:
  Won't Fix
Status in linux-base source package in Quantal:
  Fix Released
Status in linux-meta source package in Quantal:
  Invalid

Bug description:
  Dear Ones,

  Seems like straightforward same file existing in two different
  packages conflict. But I haven't read the APT policy.

  Thanks and Blessings,
  Shahar

  ProblemType: Package
  DistroRelease: Ubuntu 11.10
  Package: linux-tools-common (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
  Uname: Linux 3.0.0-15-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  AptOrdering:
   linux-tools-common: Install
   linux-tools-common: Configure
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  shahar 2366 F pulseaudio
   /dev/snd/controlC0:  shahar 2366 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,1458a102,0014'
 Controls  : 38
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdefc000 irq 19'
 Mixer name : 'ATI RS690/780 HDMI'
 Components : 'HDA:1002791a,00791a00,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card2.Amixer.info:
   Card hw:2 'Camera'/'Vimicro Corp. Venus USB2.0 Camera at usb-:00:12.2-5, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0ac8:3420'
 Controls  : 2
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 48
 Mono: Capture 47 [98%] [20.00dB] [on]
  Date: Mon Feb 13 12:15:18 2012
  DpkgTerminalLog:
   Unpacking linux-tools-common (from 
.../linux-tools-common_3.0.0-16.28_all.deb) ...
   dpkg: error processing 
/var/cache/apt/archives/linux-tools-common_3.0.0-16.28_all.deb (--unpack):
trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.3
  DuplicateSignature:
   Unpacking linux-tools-common (from 
.../linux-tools-common_3.0.0-16.28_all.deb) ...
   dpkg: error processing 
/var/cache/apt/archives/linux-tools-common_3.0.0-16.28_all.deb (--unpack):
trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.3
  ErrorMessage: trying to overwrite '/usr/bin/perf', which is also in package 
linux-base 3.3
  HibernationDevice: RESUME=UUID=f2bd5594-8447-422c-a345-492ede4de1d9
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth4  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-15-generic 
root=UUID=57641e34-8b71-4e2e-9324-ff40ca1bc82a ro quiet splash vt.handoff=7
  PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: 
No PulseAudio daemon running, or not running as session daemon.
  PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 
1: No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 1.99-12ubuntu5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-tools-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/perf', which is also in package linux-base 3.3
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (120 days ago)
  WifiSyslog:
   
  dmi.bios.date: 10/20/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-880GMA-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias:

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

2023-05-26 Thread Michael Reed

Hi Keng-Yu,

Here is a test kernel for lunar.  I had only included the source before
and not the debs. Can you please test and verify the config_numa_emu
option works and provides the performance boost.


https://people.canonical.com/~mreed/hpe/lp_2008745_config_numa_emu/lunar/


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

** 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).
+  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
  
  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
+ 
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_2_lunar

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

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

2023-05-23 Thread Michael Reed

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

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

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

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

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

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

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

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

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

  All patches applied without any conflicts.

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

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

  [Other Info]

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

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


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

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

2023-05-17 Thread Michael Reed

Hi Gerry,

This is in our currently SRU cycle.  https://kernel.ubuntu.com/If
everything goes smoothly then the target release date is June 5.
However, that is not guaranteed.  I would not notify any of your
customers about the driver until it actually gets 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/1998643

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

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

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

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

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

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

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

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

  All patches applied without any conflicts.

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

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

  [Other Info]

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

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


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

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

2023-05-17 Thread Michael Reed

Hi Don,

These patches are currently in the proposed kernel (linux:
5.15.0-74.81).  Can you test them in the proposed kernel and verify they
are working properly.

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

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

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

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

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

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

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

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

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

  All patches applied without any conflicts.

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

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

  [Other Info]

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

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


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

[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker

2023-05-10 Thread Michael

thanks for sharing https://7dstierlister.com/7ds-tier-list-jp/

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

Title:
  linux: 4.4.0-41.61 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  This bug is for tracking the 4.4.0-41.61 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions


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

[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install

2023-05-09 Thread Michael Harden

issue resolved, please complete this

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
     ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
    Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
    Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
    
No apport report written because the error message 
indicates its a followup error from a previous failure.
    
Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
     ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
    Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ---
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.

   virbr0no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKer

[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install

2023-05-09 Thread Michael Harden

ipt 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
-   Errors were 
encountered while processing:
-  linux-headers-6.2.0-20-generic
-  linux-headers-generic
-  linux-generic
-  linux-image-6.2.0-20-generic
+   Errors were 
encountered while processing:
+  linux-headers-6.2.0-20-generic
+  linux-headers-generic
+  linux-generic
+  linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  michael1934 F wireplumber
-  /dev/snd/seq:    michael1932 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  michael1934 F wireplumber
+  /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
-  lono wireless extensions.
-  
-  eno1  no wireless extensions.
-  
-  virbr0no wireless extensions.
+  lono wireless extensions.
+ 
+  eno1  no wireless extensions.
+ 
+  virbr0no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=fb795829-c3ca-41fc-8f58-5448a75c1398 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.19.0-40-generic N/A
-  linux-backports-modules-5.19.0-40-generic  N/A
-  linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
+  linux-restricted-modules-5.19.0-40-generic N/A
+  linux-backports-modules-5.19.0-40-generic  N/A
+  linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
-  
+ 
  Tags:  lunar
  Uname: Linux 5.19.0-40-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (11 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/16/2013
  dmi.bios.release: 2.90
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: AUD4100JVJ
  dmi.board.name: 3397
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD4100JVJ
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuC4K06PA#ABG:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Elite 8300 SFF
  dmi.product.sku: C4K06PA#ABG
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
     ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
    Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however

[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install

2023-05-09 Thread Michael Harden

.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=fb795829-c3ca-41fc-8f58-5448a75c1398 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-40-generic N/A
   linux-backports-modules-5.19.0-40-generic  N/A
   linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
  RfKill:
   
  Tags:  lunar
  Uname: Linux 5.19.0-40-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-23 (11 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/16/2013
  dmi.bios.release: 2.90
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: AUD4100JVJ
  dmi.board.name: 3397
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD4100JVJ
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:skuC4K06PA#ABG:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Elite 8300 SFF
  dmi.product.sku: C4K06PA#ABG
  dmi.sys.vendor: Hewlett-Packard

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


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

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

2023-05-09 Thread Michael Reed

This has been ack'ed by the kernel team and will need to be tested once
it hits the proposed kernel.

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

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

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

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

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

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

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

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

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

  All patches applied without any conflicts.

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

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

  [Other Info]

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

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


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

[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install

2023-05-08 Thread Michael Harden

michael@michael-HP-Compaq-Elite-8300-SFF:~$ dkms status
vhba/20200106, 5.11.0-16-generic, x86_64: installed
vhba/20200106, 5.11.0-17-generic, x86_64: installed
vhba/20200106, 5.11.0-18-generic, x86_64: installed
vhba/20200106, 5.11.0-22-generic, x86_64: installed
vhba/20200106, 5.11.0-31-generic, x86_64: installed
vhba/20200106, 5.4.0-52-generic, x86_64: installed
vhba/20200106, 5.8.0-26-generic, x86_64: installed
vhba/20200106, 5.8.0-29-generic, x86_64: installed
vhba/20200106, 5.8.0-31-generic, x86_64: installed
vhba/20200106, 5.8.0-40-generic, x86_64: installed
virtualbox/7.0.6, 5.19.0-40-generic, x86_64: installed
virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed

I tried to uninstall but it needs to know the module and the version, should I 
just remove all of these?
I attempted to remove virtualbox since I already have boxes installed, and it 
does not seem to remove it, because its trying to install 6.0.2-20, appears it 
removed all but one package.

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already

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

2023-05-05 Thread Michael Reed

Hi Ketan,

Currently the reverted patches have already been pulled into our master-
next kernel because they are apart of the upstream kernel.  Cherry
picking the affected patches on top of those causes all types of issues.
We need a solution with those reverted patches in place.  Can you
provide a revised list of commits that takes the reverted patches into
account?

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

Title:
  Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5

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

Bug description:
  [IMPACT/Justification]
  There are numerous bug fixes included in the more recent version of lpfc That 
Broadcom has asked to pull into Jammy and Kinetic to better support customers 
in the field who are using the GA kernel and cant or wont move to the HWE 
kernels.  These all are limited to the lpfc driver itself, no patches to core 
code are requested.

  [FIX]
  A few of these were already landed in Jammy, and all but 6 (ones landed in 
6.0 upstream) were already in Kinetic.

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

[Kernel-packages] [Bug 2018420] Re: linux kerkel 6.2.0.20-generic failed to install

It generated the logs and I clicked on send, it did not report any
errors so I assume it sent everything.

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq Elit

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

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670932/+files/acpidump.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670931/+files/WifiSyslog.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless exten

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670928/+files/ProcInterrupts.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2018420/+attachment/5670930/+files/UdevDb.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670929/+files/ProcModules.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless exten

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670925/+files/ProcCpuinfo.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless exten

[Kernel-packages] [Bug 2018420] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670922/+files/Lsusb-t.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670927/+files/ProcEnviron.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless exten

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670926/+files/ProcCpuinfoMinimal.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no

[Kernel-packages] [Bug 2018420] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2018420/+attachment/5670924/+files/PaInfo.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.

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

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670923/+files/Lsusb-v.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.

[Kernel-packages] [Bug 2018420] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2018420/+attachment/5670921/+files/Lsusb.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.
  MachineT

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

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2018420/+attachment/5670920/+files/Lspci-vt.txt

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

Title:
  linux kerkel 6.2.0.20-generic failed to install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting up linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  Setting up linux-headers-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/header_postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
   installed linux-headers-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-headers-generic:
   linux-headers-generic depends on linux-headers-6.2.0-20-generic; however:
Package linux-headers-6.2.0-20-generic is not configured yet.

  dpkg: error processing package linux-headers-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-headers-generic (= 6.2.0.20.20); however:
Package linux-headers-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for libc-bin (2.37-0ubuntu2) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.

Processing triggers for man-db (2.11.2-1) ...
  Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu5) ...
  Processing triggers for gnome-menus (3.36.0-1.1ubuntu1) ...
  Processing triggers for linux-image-6.2.0-20-generic (6.2.0-20.20) ...
  /etc/kernel/postinst.d/dkms:
   * dkms: running auto installation service for kernel 6.2.0-20-generic
  Sign command: /usr/bin/kmodsign
  Signing key: /var/lib/shim-signed/mok/MOK.priv
  Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

  Building module:
  Cleaning build area...
  make -j4 KERNELRELEASE=6.2.0-20-generic...(bad exit status: 2)
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/vhba-dkms.0.crash'
  Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64)
  Consult /var/lib/dkms/vhba/20200106/build/make.log for more information.
  Error! One or more modules failed to install during autoinstall.
  Refer to previous errors for more information.
 ...fail!
  run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
  dpkg: error processing package linux-image-6.2.0-20-generic (--configure):
   installed linux-image-6.2.0-20-generic package post-installation script 
subprocess returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1934 F wireplumber
   /dev/snd/seq:    michael1932 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2019-01-13 (1572 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   virbr0no wireless extensions.

[Kernel-packages] [Bug 2018420] Lspci.txt