[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-intel-iotg/5.15.0-1026.31)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-intel-iotg 
(5.15.0-1026.31) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-intel-iotg

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/5.15.0-1030.36)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-oracle 
(5.15.0-1030.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-oracle

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle-5.15/5.15.0-1030.36~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-oracle-5.15 
(5.15.0-1030.36~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-oracle-5.15

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-intel-iotg/5.15.0-1026.31)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-intel-iotg 
(5.15.0-1026.31) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-intel-iotg

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

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

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

   * [nvidia driver]

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

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

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

  [ Where problems could occur ]

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

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-oracle/5.15.0-1030.36)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-oracle 
(5.15.0-1030.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-oracle

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

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

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

   * [nvidia driver]

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

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

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

  [ Where problems could occur ]

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

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-oracle-5.15/5.15.0-1030.36~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-oracle-5.15 
(5.15.0-1030.36~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-oracle-5.15

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

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

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

   * [nvidia driver]

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

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

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

  [ Where problems could occur ]

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

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 2002285] Re: Alder Lake N-Series Enablement

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  Alder Lake N-Series Enablement

Status in linux-intel-iotg package in Ubuntu:
  New
Status in linux-intel-iotg source package in Focal:
  Invalid
Status in linux-intel-iotg source package in Jammy:
  Fix Committed

Bug description:
  [Summary]
  Alder Lake N-Series Enablement

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


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

[Kernel-packages] [Bug 1996609] Re: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel

Status in HWE Next:
  New
Status in linux-intel-iotg package in Ubuntu:
  Invalid
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Invalid
Status in linux-intel-iotg source package in Focal:
  Invalid
Status in linux-intel-iotg-5.15 source package in Focal:
  New
Status in linux-intel-iotg source package in Jammy:
  Fix Committed
Status in linux-intel-iotg-5.15 source package in Jammy:
  Invalid

Bug description:
  [Summary]
  AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel.

  [Steps to reproduce]
  install 5.15 Intel IoTG kernel.

  [Expected result]
  WLAN works with no problem.

  [Actual result]
  Can't detect WLAN.

  [Failure rate]
  100%

  The ucode version 66 would not be loaded successfully on this particular
  model with the folloing error messages:

  [   13.231830] kernel: iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000
  [   13.232964] kernel: iwlwifi :02:00.0: Microcode SW error detected. 
Restarting 0x0.
  [   13.233061] kernel: iwlwifi :02:00.0: Start IWL Error Log Dump:
  [   13.233062] kernel: iwlwifi :02:00.0: Transport status: 0x004A, 
valid: 6
  [   13.233064] kernel: iwlwifi :02:00.0: Loaded firmware version: 
66.f1c864e0.0 ty-a0-gf-a0-66.ucode
  [   13.233065] kernel: iwlwifi :02:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
  [   13.233066] kernel: iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0
  [   13.233067] kernel: iwlwifi :02:00.0: 0x | trm_hw_status1
  [   13.233068] kernel: iwlwifi :02:00.0: 0x004DA722 | branchlink2
  ...
  [   14.094020] kernel: iwlwifi :02:00.0: Failed to run INIT ucode: -5

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


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

[Kernel-packages] [Bug 2006914] Re: Raptor Lake S/P Enablement

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  Raptor Lake S/P Enablement

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

Bug description:
  [Summary]
  Raptor Lake S/P Enablement

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


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

[Kernel-packages] [Bug 2006554] Re: [5G] Enable 5G support with Fibocom FM350

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  [5G] Enable 5G support with Fibocom FM350

Status in linux-intel-iotg package in Ubuntu:
  New
Status in linux-intel-iotg source package in Jammy:
  Fix Committed

Bug description:
  Enable 5G support with Fibocom FM350 module in intel iotg kernel.

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


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

[Kernel-packages] [Bug 2007328] Re: [ADL-N] HDMI port through type-c stops working after reboot

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-intel-iotg verification-needed-jammy

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

Title:
  [ADL-N] HDMI port through type-c stops working after reboot

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

Bug description:
  [Impact]
  HDMI port through type-c stops working after reboot

  [Fix]
  adding the correct ddc pin mapping and eliminate the warn log about ownership.

  [Test Case]
  1.Connected the external monitor to the onboard HDMI port which comes from 
type-c.
  2.Boot OS.
  3.Check the monitor to see if it is working.

  [Where problems could occur]
  Low, the fix limits to adl-n (adl-p) series.

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


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

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-525-server -
525.85.12-0ubuntu1

---
nvidia-graphics-drivers-525-server (525.85.12-0ubuntu1) lunar; urgency=medium

  * New upstream release (LP: #2003995).
  * debian/templates/control.in:
- Add Conflicts, Replaces, Provides up to libcuda-11.7-1.

 -- Alberto Milone   Wed, 01 Feb 2023
11:00:04 +

** Changed in: nvidia-graphics-drivers-525-server (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  Fix Released
Status in fabric-manager-525 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-515 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-525 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  New
Status in linux-restricted-modules-hwe package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Fix Released
Status in fabric-manager-515 source package in Bionic:
  Triaged
Status in fabric-manager-525 source package in Bionic:
  Triaged
Status in libnvidia-nscq-515 source package in Bionic:
  Triaged
Status in libnvidia-nscq-525 source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux-restricted-modules-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  Triaged
Status in fabric-manager-525 source package in Focal:
  Triaged
Status in libnvidia-nscq-515 source package in Focal:
  Triaged
Status in libnvidia-nscq-525 source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  New
Status in linux-restricted-modules-hwe source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  Triaged
Status in fabric-manager-525 source package in Jammy:
  Triaged
Status in libnvidia-nscq-515 source package in Jammy:
  Triaged
Status in libnvidia-nscq-525 source package in Jammy:
  Triaged
Status in linux-restricted-modules source package in Jammy:
  New
Status in linux-restricted-modules-hwe source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Triaged
Status in fabric-manager-515 source package in Kinetic:
  Triaged
Status in fabric-manager-525 source package in Kinetic:
  Triaged
Status in libnvidia-nscq-515 source package in Kinetic:
  Triaged
Status in libnvidia-nscq-525 source package in Kinetic:
  Triaged
Status in linux-restricted-modules source package in Kinetic:
  New
Status in linux-restricted-modules-hwe source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  Triaged
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Triaged

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  525

* New upstream release (LP: #2003995):
  - Improved the reliability of suspend and resume on UEFI systems
when using certain display panels.
  - Fixed a bug that could cause 

[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot

[Gary Brainin]

Correction: It is not the kernel itself I was talking about, above.
It's the initrd.img file associated with the kernel.

Note also that replacing that file with the old version eliminates the
problem (at least until some update changes it 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/1986623

Title:
  cryptsetup fails to decrypt root partion during boot

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

Bug description:
  During boot, cryptsetup fails to decrypt the root partition in a,
  seemingly, non-deterministic fashion. I know that the password is
  correct and that the keymap is not a fault either, because I have
  specifically chosen the very weak password "123456" for testing
  purposes. A hardware defect seems also rather unlikely as this
  behavior does not affect other Linux distributions or FreeBSD. Earlier
  Ubuntu versions do not seem to be affected either, as this bug appears
  to have been introduced during a kernel update in 20.04 and persists
  throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact
  kernel update that introduced this bug. I have appended the output of
  cryptsetup when manually called from the initramfs shell. Here the
  second attempt succeeded in decrypting the root partition, however, it
  usually takes a lot more attempts to do so.

  As for some additional information, I can decrypt the same luks
  partition from a live USB without any problems whatsoever.

  echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 
nvme0n1p3_crypt
  # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug 
/dev/nvme0n1p3 nvme0n1p3_crypt"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device /dev/nvme0n1p3.
  # Trying to open and read device /dev/nvme0n1p3 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device /dev/nvme0n1p3.
  # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in 
cryptsetup library version 2.4.3.
  # Detected kernel Linux 5.15.0-46-generic x86_64.
  # Loading LUKS2 header (repair disabled).
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Trying to read primary LUKS2 header at offset 0x0.
  # Opening locked device /dev/nvme0n1p3
  # Verifying locked device handle (bdev)
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(on-disk)
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(in-memory)
  # Trying to read secondary LUKS2 header at offset 0x4000.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(on-disk)
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(in-memory)
  # Device size 497776852992, offset 16777216.
  # Device /dev/nvme0n1p3 READ lock released.
  # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, 
parallel_threads 4.
  # Activating volume nvme0n1p3_crypt using token (any type) -1.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.45.0.
  # Detected dm-crypt version 1.23.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  No usable token is available.
  # STDIN descriptor passphrase entry requested.
  # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase.
  # dm versions   [ opencount flush ]   [16384] (*1)
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  # Keyslot 0 priority 1 != 2 (required), skipped.
  # Keyslot 1 priority 1 != 2 (required), skipped.
  # Trying to open LUKS2 keyslot 0.
  # Running keyslot key derivation.
  # Reading keyslot area [0x8000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # Device /dev/nvme0n1p3 READ lock released.
  # Verifying key from keyslot 0, digest 0.
  # Digest 0 (pbkdf2) verify failed with -1.
  # Trying to open LUKS2 keyslot 1.
  # Running keyslot key derivation.
  # Reading keyslot area [0x47000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock 

[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key

[Ubuntu Kernel Bot]

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

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

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

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

Title:
  Revoke & rotate to new signing key

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Revoke & rotate to new signing key

   * Update revocations, which match the next Ubuntu shim 15.7
  revocations. Specifically - revoke certs that were previously
  protected with by-hash revocations, revoke lost/unused certificates.

   * Start using advantage2021v1 and ubuntu2022v1 signing keys.

   * This is a routine key rotation.

  [ Test Plan ]

   * Check that old shim/grub boot this kernel
   * Check that the upcomming future shim/grub can boot this kernel
   * Check that these kernels can do signed kexec into itself

  [ Where problems could occur ]

   * Kernels with this patch applied should be signed using ubuntu/4
  pro/3 core/2 signing streams.

  [ Other Info ]
   
   * TPM PCR values and measurements will change when changing the signing key

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


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

[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-focal-linux-raspi

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

Title:
  Revoke & rotate to new signing key

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Revoke & rotate to new signing key

   * Update revocations, which match the next Ubuntu shim 15.7
  revocations. Specifically - revoke certs that were previously
  protected with by-hash revocations, revoke lost/unused certificates.

   * Start using advantage2021v1 and ubuntu2022v1 signing keys.

   * This is a routine key rotation.

  [ Test Plan ]

   * Check that old shim/grub boot this kernel
   * Check that the upcomming future shim/grub can boot this kernel
   * Check that these kernels can do signed kexec into itself

  [ Where problems could occur ]

   * Kernels with this patch applied should be signed using ubuntu/4
  pro/3 core/2 signing streams.

  [ Other Info ]
   
   * TPM PCR values and measurements will change when changing the signing key

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.4.0-1101.110)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-gcp 
(5.4.0-1101.110) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-gcp

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-gcp/5.4.0-1101.110)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules-gcp 
(5.4.0-1101.110) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-gcp

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

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

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

Bug description:
  [ Impact ]

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

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

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

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

  [ Test Plan ]

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

   * [nvidia driver]

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

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

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

  [ Where problems could occur ]

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

  [ Other Info ]
   
  -

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


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

[Kernel-packages] [Bug 1914774] Re: Some derivative kernel tools packages don't depend on linux-tools-common

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-jammy-linux-ibm verification-needed-jammy

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

Title:
  Some derivative kernel tools packages don't depend on linux-tools-
  common

Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux-ibm package in Ubuntu:
  Invalid
Status in linux-ibm-5.4 package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  Fix Committed
Status in linux-ibm-5.4 source package in Bionic:
  Fix Committed
Status in linux-ibm source package in Focal:
  Fix Committed
Status in linux-ibm source package in Jammy:
  Fix Committed
Status in linux-ibm source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Installing the tools package for some kernels, like linux-tools-
  generic-hwe-18.04, does not install linux-tools-common because of a
  missing dependency. This results in missing /usr/bin/* wrapper scripts
  that call the version dependent binaries (like cpupower).

  [Test Case]

  Install like linux-tools-generic-hwe-18.04 on bionic and:
  $ cpupower
  cpupower: command not found

  
  [Fix]

  Add linux-tools-common as a dependency.

  
  [Regression Potential]

  The fix results in an additional package being installed. If something
  goes wrong this would manifest itself as a package installation error.

  
  [Original Description]

  While running kernel 5.4.0-64 today on bionic I noticed that Canonical
  kernel team does not provide a linux-hwe-5.4-tools package.  Is that a
  deliberate choice?  If so, would you please share the reason?

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


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

[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[AceLan Kao]

>From the dmesg logs, the kernel you use on desktop(5.15.0-56) and on
core(5.15.0-58) are not the same, but I've checked the kernel logs,
there is no update on bt driver part between the 2 kernel versions. It'd
be good if you can help me to update the kernel to make sure the kernel
versions are identical and check the issue again.(I feel the result
won't change)

The snap package works on desktop, but not on core, this doesn't look
like a kernel/driver issue. Could you provide more info about which
function call failed? or provide a simple program that we could try on
our side?

BTW, the difference between the dmesg logs is that rfcomm is loaded on
the desktop, but not on the core system, could you also try to load it
on the core system to see if it makes any difference, thanks.

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

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


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

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2007633/+attachment/5648204/+files/acpidump.txt

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

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2007633] PulseList.txt

[Jeff Schmidt]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/2007633/+attachment/5648201/+files/PulseList.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/2007633

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2007633] PaInfo.txt

[Jeff Schmidt]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2007633/+attachment/5648196/+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/2007633

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2007633] Lsusb-t.txt

[Jeff Schmidt]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2007633/+attachment/5648194/+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/2007633

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2007633] Lsusb.txt

[Jeff Schmidt]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2007633/+attachment/5648193/+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/2007633

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2007633] Lspci.txt

[Jeff Schmidt]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2007633/+attachment/5648191/+files/Lspci.txt

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

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

[Jeff Schmidt]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2007633/+attachment/5648190/+files/CurrentDmesg.txt

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

Title:
  amdgpu fails to init with kernel 5.19.0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.

  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280
  GPU fails to init. This results in the computer effectively getting
  'hung' part way through the kernel boot as X or Wayland, whatever
  should start up, doesn't. The kernel keeps running (I can see the hard
  drive light occasionally flash on my case, and the kernel logs
  continue after the point of the apparent hang - although kernel
  messages stop getting output to the console - to see the messages, I
  have to reboot with 5.15 then use journalctl to review the previous
  boot messages).

  It inits fine with the older kernel. Not sure what the root cause of
  the failure is. Found this in kernel boot logs (via "journalctl -b -1"
  to get the logs for the previous boot, that failed), which I think is
  indicative of the problem:

  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090

  --
  version signature info (line 2 from kernel boot log):

  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2
  (Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17)

  -

  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  See attached lspci-vnvn.log
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jeff   1525 F pulseaudio
   /dev/snd/controlC0:  jeff   1525 F pulseaudio
   /dev/snd/controlC1:  jeff   1525 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-27 (355 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/06/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Q77-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Kernel-packages] [Bug 2007633] Re: amdgpu fails to init with kernel 5.19.0

[Jeff Schmidt]

apport information

** Tags added: apport-collected jammy wayland-session

** Description changed:

  I recently installed apt upgrades, and among the upgrades, was the
  5.19.0-32-generic kernel. I also still have installed the
  5.15.0-58-generic kernel.
  
  Every time I try to boot with the 5.19 kernel, my AMD Radeon R9 280 GPU
  fails to init. This results in the computer effectively getting 'hung'
  part way through the kernel boot as X or Wayland, whatever should start
  up, doesn't. The kernel keeps running (I can see the hard drive light
  occasionally flash on my case, and the kernel logs continue after the
  point of the apparent hang - although kernel messages stop getting
  output to the console - to see the messages, I have to reboot with 5.15
  then use journalctl to review the previous boot messages).
  
  It inits fine with the older kernel. Not sure what the root cause of the
  failure is. Found this in kernel boot logs (via "journalctl -b -1" to
  get the logs for the previous boot, that failed), which I think is
  indicative of the problem:
  
  Feb 16 21:37:17 jeff-linux kernel: status:
  Feb 16 21:37:17 jeff-linux kernel: [drm] amdgpu: dpm initialized
  Feb 16 21:37:17 jeff-linux kernel: [drm] Found UVD firmware Version: 64.0 
Family ID: 13
  Feb 16 21:37:17 jeff-linux kernel: amdgpu: Move buffer fallback to memcpy 
unavailable
  Feb 16 21:37:17 jeff-linux kernel: [drm:amdgpu_device_ip_init [amdgpu]] 
*ERROR* sw_init of IP block  failed -19
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: 
amdgpu_device_ip_init failed
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: Fatal error 
during GPU init
  Feb 16 21:37:17 jeff-linux kernel: amdgpu :01:00.0: amdgpu: amdgpu: 
finishing device.
  Feb 16 21:37:17 jeff-linux kernel: BUG: kernel NULL pointer dereference, 
address: 0090
  
  --
  version signature info (line 2 from kernel boot log):
  
  Feb 16 21:37:14 jeff-linux kernel: Linux version 5.19.0-32-generic
  (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu
  11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
  #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 (Ubuntu
  5.19.0-32.33~22.04.1-generic 5.19.17)
  
  -
  
  root@jeff-linux:/home/jeff# lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  
  See attached lspci-vnvn.log
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  jeff   1525 F pulseaudio
+  /dev/snd/controlC0:  jeff   1525 F pulseaudio
+  /dev/snd/controlC1:  jeff   1525 F pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-02-27 (355 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ IwConfig:
+  lono wireless extensions.
+  
+  eno1  no wireless extensions.
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=bd9a6ac0-c013-4645-a8d7-23af9e13d239 ro quiet splash 
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 
amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-58-generic N/A
+  linux-backports-modules-5.15.0-58-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.10
+ RfKill:
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  jammy wayland-session
+ Uname: Linux 5.15.0-58-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/06/2014
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1302
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: P8Q77-M
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev X.0x
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1302:bd08/06/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Q77-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

** Attachment 

[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-kinetic-linux-raspi

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

Title:
  Revoke & rotate to new signing key

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Revoke & rotate to new signing key

   * Update revocations, which match the next Ubuntu shim 15.7
  revocations. Specifically - revoke certs that were previously
  protected with by-hash revocations, revoke lost/unused certificates.

   * Start using advantage2021v1 and ubuntu2022v1 signing keys.

   * This is a routine key rotation.

  [ Test Plan ]

   * Check that old shim/grub boot this kernel
   * Check that the upcomming future shim/grub can boot this kernel
   * Check that these kernels can do signed kexec into itself

  [ Where problems could occur ]

   * Kernels with this patch applied should be signed using ubuntu/4
  pro/3 core/2 signing streams.

  [ Other Info ]
   
   * TPM PCR values and measurements will change when changing the signing key

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


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

[Kernel-packages] [Bug 2003524] Re: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks

[Ubuntu Kernel Bot]

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

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

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


** Tags added: kernel-spammed-kinetic-linux-raspi

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

Title:
  amdgpu: framebuffer is destroyed and the screen freezes with
  unsupported IP blocks

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

Bug description:
  [Impact]
  From "Mario Limonciello mario.limonciello at amd.com"
  https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html.

  There is a problem in amdgpu that if not all of IP blocks are
  supported or not all of the firmware is present then the framebuffer
  is destroyed and the screen freezes.  In more recent kernels the
  amdgpu driver loads for all PCI VGA class AMD devices.

  This effectively means that unless you have all the pieces you need to
  support a GPU then the installer freezes unless you do nomodeset.

  This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that 
is currently in drm-next.  This does two basic things:
  1) If the IP blocks isn't supported, don't destroy the framebuffer.
  2) If firmware for any IP blocks aren't present, don't destroy the 
framebuffer.

  The whole patch series still needs more time to back in drm-next, but
  the most important part of the series is the first patch which
  accomplishes "1".

  This patch went out to stable 6.1.y as well:

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y=dcfeba477b3e3df526e0f543b58fa71c045dff8b

  My reasoning is that it will ensure that if someone picks up a newer
  GPU such as Ryzen 7000 desktop or RDNA3 based they can at least
  install Ubuntu without needing to use "Safe Graphics Mode" at the
  installer.

  Sure; they won't have hardware acceleration without the rest of the
  kernel and framework, but that's a separate problem to a basic
  display.

  [Fix]
  Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a 
"drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 
kernel.

  [Test case]
  Boot kernel in a system with one of the amdgpu affected adapters.

  [Where problems can occur]
  The aforementioned commit could introduce other regressions on the support 
for AMD GPUs.

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


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

[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key

[Ubuntu Kernel Bot]

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

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

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


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

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

Title:
  Revoke & rotate to new signing key

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

   * Revoke & rotate to new signing key

   * Update revocations, which match the next Ubuntu shim 15.7
  revocations. Specifically - revoke certs that were previously
  protected with by-hash revocations, revoke lost/unused certificates.

   * Start using advantage2021v1 and ubuntu2022v1 signing keys.

   * This is a routine key rotation.

  [ Test Plan ]

   * Check that old shim/grub boot this kernel
   * Check that the upcomming future shim/grub can boot this kernel
   * Check that these kernels can do signed kexec into itself

  [ Where problems could occur ]

   * Kernels with this patch applied should be signed using ubuntu/4
  pro/3 core/2 signing streams.

  [ Other Info ]
   
   * TPM PCR values and measurements will change when changing the signing key

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Black screen on boot and tearing on resume on HP Envy x360

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu about 1 week ago on a new machine, after testing
  with a Live USB 22.10 that it was working reasonably well. While the
  live USB was working pretty well, including 3D acceleration, the
  installed system failed to display anything after the first mode
  setting.

  I was able to work around this first issue with:

  echo 'FRAMEBUFFER=y' | sudo tee /etc/initramfs-tools/conf.d/hp-envy-x360-quirk
  sudo update-initramfs -c -k all

  With this, the system starts correctly, with 3D acceleration. I
  noticed that, after enabling this option, the initrd image now
  contained i915 driver and firmware. However, just declaring "i915"
  /etc/initramfs-tools/modules did not appear to fix the issue.

  A second, possibly related issue, is that after resume, the screen was
  displaying random pixels of increasing intensity (tearing ?).

  I was able to work around this other issue with:

  echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 
i915.enable_fbc=1"' | sudo tee /etc/default/grub.d/hp-envy-x360-quirk.cfg
  sudo update-grub

  With this second workaround in place, suspend/resumes has been working
  fine for at least the past couple of days.

  Let me know if this bug should be split into 2 dedicated bugs or if I
  can help with any test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-31-generic 5.19.0-31.32
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jean-tiare  111982 F pipewire
jean-tiare  111986 F wireplumber
   /dev/snd/pcmC0D0p:   jean-tiare  111982 F...m pipewire
   /dev/snd/seq:jean-tiare  111982 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 17 23:35:44 2023
  InstallationDate: Installed on 2023-02-10 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: HP HP ENVY x360 2-in-1 Laptop 15-ew0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash i915.enable_psr=0 
i915.enable_fbc=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-31-generic N/A
   linux-backports-modules-5.19.0-31-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2022
  dmi.bios.release: 15.13
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8A29
  dmi.board.vendor: HP
  dmi.board.version: 22.41
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 22.41
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd12/23/2022:br15.13:efr22.41:svnHP:pnHPENVYx3602-in-1Laptop15-ew0xxx:pvrType1ProductConfigId:rvnHP:rn8A29:rvr22.41:cvnHP:ct31:cvrChassisVersion:sku6R3F4EA#ABF:
  dmi.product.family: 103C_5335M8 HP ENVY
  dmi.product.name: HP ENVY x360 2-in-1 Laptop 15-ew0xxx
  dmi.product.sku: 6R3F4EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2007734] [NEW] Black screen on boot and tearing on resume on HP Envy x360

[jtlb]

Public bug reported:

I installed Ubuntu about 1 week ago on a new machine, after testing with
a Live USB 22.10 that it was working reasonably well. While the live USB
was working pretty well, including 3D acceleration, the installed system
failed to display anything after the first mode setting.

I was able to work around this first issue with:

echo 'FRAMEBUFFER=y' | sudo tee /etc/initramfs-tools/conf.d/hp-envy-x360-quirk
sudo update-initramfs -c -k all

With this, the system starts correctly, with 3D acceleration. I noticed
that, after enabling this option, the initrd image now contained i915
driver and firmware. However, just declaring "i915" /etc/initramfs-
tools/modules did not appear to fix the issue.

A second, possibly related issue, is that after resume, the screen was
displaying random pixels of increasing intensity (tearing ?).

I was able to work around this other issue with:

echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 
i915.enable_fbc=1"' | sudo tee /etc/default/grub.d/hp-envy-x360-quirk.cfg
sudo update-grub

With this second workaround in place, suspend/resumes has been working
fine for at least the past couple of days.

Let me know if this bug should be split into 2 dedicated bugs or if I
can help with any test.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-31-generic 5.19.0-31.32
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jean-tiare  111982 F pipewire
  jean-tiare  111986 F wireplumber
 /dev/snd/pcmC0D0p:   jean-tiare  111982 F...m pipewire
 /dev/snd/seq:jean-tiare  111982 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 17 23:35:44 2023
InstallationDate: Installed on 2023-02-10 (6 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: HP HP ENVY x360 2-in-1 Laptop 15-ew0xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash i915.enable_psr=0 
i915.enable_fbc=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-31-generic N/A
 linux-backports-modules-5.19.0-31-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2022
dmi.bios.release: 15.13
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8A29
dmi.board.vendor: HP
dmi.board.version: 22.41
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 22.41
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd12/23/2022:br15.13:efr22.41:svnHP:pnHPENVYx3602-in-1Laptop15-ew0xxx:pvrType1ProductConfigId:rvnHP:rn8A29:rvr22.41:cvnHP:ct31:cvrChassisVersion:sku6R3F4EA#ABF:
dmi.product.family: 103C_5335M8 HP ENVY
dmi.product.name: HP ENVY x360 2-in-1 Laptop 15-ew0xxx
dmi.product.sku: 6R3F4EA#ABF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


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

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

Title:
  Black screen on boot and tearing on resume on HP Envy x360

Status in linux package in Ubuntu:
  New

Bug description:
  I installed Ubuntu about 1 week ago on a new machine, after testing
  with a Live USB 22.10 that it was working reasonably well. While the
  live USB was working pretty well, including 3D acceleration, the
  installed system failed to display anything after the first mode
  setting.

  I was able to work around this first issue with:

  echo 'FRAMEBUFFER=y' | sudo tee /etc/initramfs-tools/conf.d/hp-envy-x360-quirk
  sudo update-initramfs -c -k all

  With this, the system starts correctly, with 3D acceleration. I
  noticed that, after enabling this option, the initrd image now
  contained i915 driver and firmware. However, just declaring "i915"
  /etc/initramfs-tools/modules did not appear to fix the issue.

  A second, possibly related issue, is that after resume, the screen was
  displaying random pixels of increasing intensity (tearing ?).

  I was able to work around this other issue with:

  echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 
i915.enable_fbc=1"' | sudo tee /etc/default/grub.d/hp-envy-x360-quirk.cfg
  sudo update-grub

  With this second workaround in place, suspend/resumes has been working
  fine for at least the past couple of days.

  Let me know if this bug should be split into 2 dedicated bugs or if I
  can help with any test.

  ProblemType: 

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

[Ubuntu Kernel Bot]

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

apport-collect 2007717

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

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

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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

  To reproduce, I would think that compiling any decent sized software
  package one on 5.15 and then on 5.19 whould yield the same results.

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


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

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

[Brian Murray]

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

** Tags added: regression-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/2007717

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

Status in linux package in Ubuntu:
  New

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

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

  To reproduce, I would think that compiling any decent sized software
  package one on 5.15 and then on 5.19 whould yield the same results.

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


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

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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

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

To reproduce, I would think that compiling any decent sized software
package one on 5.15 and then on 5.19 whould yield the same results.

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


** Tags: bot-comment
-- 
Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
https://bugs.launchpad.net/bugs/2007717
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 2007729] [NEW] HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi driver not working

[Tobiyo Kuujikai]

Public bug reported:

this forum post, https://community.intel.com/t5/Wireless/Linux-Intel-
AC-9560-iwlwifi-fails-on-kernels-above-5-10/m-p/1377826#M41506, appears
to mention that QuZ-a0-jf-b0-64.ucode has this problem but
QuZ-a0-jf-b0-59.ucode does not.

taking a look in /lib/firmware i see the following:
iwlwifi-QuZ-a0-jf-b0-48.ucode  iwlwifi-QuZ-a0-jf-b0-63.ucode
iwlwifi-QuZ-a0-jf-b0-50.ucode  iwlwifi-QuZ-a0-jf-b0-66.ucode
iwlwifi-QuZ-a0-jf-b0-53.ucode  iwlwifi-QuZ-a0-jf-b0-68.ucode
iwlwifi-QuZ-a0-jf-b0-55.ucode  iwlwifi-QuZ-a0-jf-b0-71.ucode
iwlwifi-QuZ-a0-jf-b0-59.ucode  iwlwifi-QuZ-a0-jf-b0-72.ucode
iwlwifi-QuZ-a0-jf-b0-62.ucode

it appears to be loading iwlwifi-QuZ-a0-jf-b0-72.ucode and failing.

i have removed the these entries one by one, followed by modprobe -r
iwlwifi && modprobe iwlwifi untill i have found a working one, which
turns out to be iwlwifi-QuZ-a0-jf-b0-55.ucode

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

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


** Tags: amd64 apport-bug jammy

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

Title:
  HP Probook 450 G8 Intel i5-1135G7 with Intel Wireless-AC 9560 wifi
  driver not working

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

Bug description:
  this forum post, https://community.intel.com/t5/Wireless/Linux-Intel-
  AC-9560-iwlwifi-fails-on-kernels-above-5-10/m-p/1377826#M41506,
  appears to mention that QuZ-a0-jf-b0-64.ucode has this problem but
  QuZ-a0-jf-b0-59.ucode does not.

  taking a look in /lib/firmware i see the following:
  iwlwifi-QuZ-a0-jf-b0-48.ucode  iwlwifi-QuZ-a0-jf-b0-63.ucode
  iwlwifi-QuZ-a0-jf-b0-50.ucode  iwlwifi-QuZ-a0-jf-b0-66.ucode
  iwlwifi-QuZ-a0-jf-b0-53.ucode  iwlwifi-QuZ-a0-jf-b0-68.ucode
  iwlwifi-QuZ-a0-jf-b0-55.ucode  iwlwifi-QuZ-a0-jf-b0-71.ucode
  iwlwifi-QuZ-a0-jf-b0-59.ucode  iwlwifi-QuZ-a0-jf-b0-72.ucode
  iwlwifi-QuZ-a0-jf-b0-62.ucode

  it appears to be loading iwlwifi-QuZ-a0-jf-b0-72.ucode and failing.

  i have removed the these entries one by one, followed by modprobe -r
  iwlwifi && modprobe iwlwifi untill i have found a working one, which
  turns out to be iwlwifi-QuZ-a0-jf-b0-55.ucode

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

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


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

[Kernel-packages] [Bug 1995296] Re: mlx-bootctl: support icm carveout eeprom region read/write

[Meriton Tuli]

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

Title:
  mlx-bootctl: support icm carveout eeprom region read/write

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

Bug description:
  SRU Justification:

  [Impact]

  The BlueField-3 ICM carveout feature will enable NIC FW to bypass the SMMU 
block to access DRAM memory.
  The amount of memory accessible by FW will be controlled by ARM. This patch 
enables setting the size of the large ICM carveout from userspace. The max size 
is 1TB, has a granularity of 128MB and will be passed
  and printed in hex. The size unit is MB.

  [Fix]

  * Support SMC calls to control the large ICM carveout size.

  [Test Case]

  * Only valid testing on BlueField-3 real hardware.
  * set the region size from sysfs and NIC FW will test that it has access to 
the entire region requested.

  [Regression Potential]

  * This code doesn't really have a negative impact on the functionality of the 
mlxbf-bootctl driver itself but could be a risk for the overall boot if not 
used/tested properly.
  * memory region requested is too large, adn linux cannot boot as a result. 
The memory allocated for the ICM carveout cannot be accessed by linux.
  * the icmc size is not passed properly to NIC FW

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


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

[Kernel-packages] [Bug 1994897] Re: Support BlueField-3 GPIO driver

[Meriton Tuli]

# dmesg | grep gpio
[5.166183] gpio_mlxbf3: loading out-of-tree module taints kernel.
[5.195583] mlxbf3_gpio MLNXBF33:01: IRQ index 0 not found
# lsmod | grep gpio
gpio_mlxbf320480  2

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

Title:
  Support BlueField-3 GPIO driver

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

Bug description:
  SRU Justification:

  [Impact]

  * Support GPIO driver for BlueField-3 SoCs.

  [Fix]

  * Support GPIO driver for BlueField-3 SoCs.
  * Allows user to alter GPIO value when direction is set to output
  * Support configuring GPIOs as interrupts for dependent drivers such as 
pwr-mlxbf and mlxbf-gige

  [Test Case]

  * At the moment, this driver can only be tested internally on palladium and 
via the ARM simulator.
  * This driver only loaded on BF3 platforms so has no impact on older 
platforms such as BF2 and BF1.

  [Regression Potential]

  * Code will need to be tested once real HW is ready (bringup)

  [Other]
  * This driver is in the process of being upstreamed. This code is likely to 
change depending on feedback we receive from maintainers. But the upstreaming 
process is long and we need to have this code to be available before 
BlueField-3 bringup.

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  kernel BUG at fs/buffer.c:3326!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to copy large amounts of data at once, I get a fault from
  the kernel that there's a bug in buffer.c. (See attached log from
  dmesg.) I first encountered it while trying to copy hundreds of gigs
  of files from an old Adaptec raid controller to the NVMe drive I'm
  currently using, but it also happens copying those files from the raid
  controller to a different SATA drive or just copying a lot of stuff
  from one directory on the NVMe to another on the NVMe, so it's not
  particular to one drive. Once it happens, the kernel sometimes panics.
  If it doesn't, I can issue a shutdown command to restart but it gets
  stuck trying to unmount the drive. I have kernels 5.15.0-25-generic
  and 5.15.0-60-generic installed and they both do it.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kenshi 1166 F pulseaudio
   /dev/snd/controlC0:  kenshi 1166 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Feb 17 13:49:48 2023
  InstallationDate: Installed on 2023-02-17 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   enp39s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7D53
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-60-generic N/A
   linux-backports-modules-5.15.0-60-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570S EDGE MAX WIFI (MS-7D53)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/27/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570SEDGEMAXWIFI(MS-7D53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D53
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 2007727] [NEW] kernel BUG at fs/buffer.c:3326!

[El Conquistador]

Public bug reported:

When trying to copy large amounts of data at once, I get a fault from
the kernel that there's a bug in buffer.c. (See attached log from
dmesg.) I first encountered it while trying to copy hundreds of gigs of
files from an old Adaptec raid controller to the NVMe drive I'm
currently using, but it also happens copying those files from the raid
controller to a different SATA drive or just copying a lot of stuff from
one directory on the NVMe to another on the NVMe, so it's not particular
to one drive. Once it happens, the kernel sometimes panics. If it
doesn't, I can issue a shutdown command to restart but it gets stuck
trying to unmount the drive. I have kernels 5.15.0-25-generic and
5.15.0-60-generic installed and they both do it.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  kenshi 1166 F pulseaudio
 /dev/snd/controlC0:  kenshi 1166 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Feb 17 13:49:48 2023
InstallationDate: Installed on 2023-02-17 (0 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
IwConfig:
 lono wireless extensions.
 
 enp39s0   no wireless extensions.
MachineType: Micro-Star International Co., Ltd. MS-7D53
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-60-generic N/A
 linux-backports-modules-5.15.0-60-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570S EDGE MAX WIFI (MS-7D53)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/27/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570SEDGEMAXWIFI(MS-7D53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7D53
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug jammy

** Attachment added: "dmesg just after fault"
   
https://bugs.launchpad.net/bugs/2007727/+attachment/5648130/+files/fault_again.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/2007727

Title:
  kernel BUG at fs/buffer.c:3326!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to copy large amounts of data at once, I get a fault from
  the kernel that there's a bug in buffer.c. (See attached log from
  dmesg.) I first encountered it while trying to copy hundreds of gigs
  of files from an old Adaptec raid controller to the NVMe drive I'm
  currently using, but it also happens copying those files from the raid
  controller to a different SATA drive or just copying a lot of stuff
  from one directory on the NVMe to another on the NVMe, so it's not
  particular to one drive. Once it happens, the kernel sometimes panics.
  If it doesn't, I can issue a shutdown command to restart but it gets
  stuck trying to unmount the drive. I have kernels 5.15.0-25-generic
  and 5.15.0-60-generic installed and they both do it.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-60-generic 5.15.0-60.66
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kenshi 1166 F pulseaudio
   /dev/snd/controlC0:  kenshi 1166 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Feb 17 13:49:48 2023
  InstallationDate: Installed on 2023-02-17 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  

[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in
  kmalloc-2k slabs

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

Bug description:
  Since updating to kernel 5.15.0-46-generic (package version
  5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel
  memory; our first server with 8 GB of RAM just fatally OOMed, causing
  us to detect this. Inspection of OOM reports, /proc/meminfo, and
  /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k
  slabs:

  Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab 
info:
  Aug 23 12:51:11 cluster kernel: [361299.864757] Name  
Used  Total
  [...]
  Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k   
6676584KB6676596KB

  Most of our machines appear to be leaking slab memory at a rate of
  around 20 to 40 Mbytes/hour, with some machines leaking much faster;
  the champions are leaking kernel memory at 145 Mbytes/hour and 237
  Mbytes/hour.

  We aren't running any proprietary kernel modules and our only unusual
  kernel configuration is that we've disabled AppArmor with 'apparmor=0'
  on the kernel command line.

  /proc/version_signature:
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Full kernel command line from the Dell R240 system that fatally OOMd:
  BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 
console=tty0 apparmor=0

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


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

[Kernel-packages] [Bug 1991112] Re: mlxbf_gige: compute MDIO period based on i1clk

[Meriton Tuli]

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

Title:
  mlxbf_gige: compute MDIO period based on i1clk

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

Bug description:
  The following upstream patch should be cherry picked to jammy kernel:

  3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  amdgpu updateMST crash 43s after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Amdgpu has tendency of crashing after resume when MST responses of the
  displays waking up aren't what it expects.

  Sadly launchpad does not provide a way to review the logs sent by
  ubuntu-bug before submit button here, apparently can preview only
  locally prior to sending report.

  More details to be added after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  iheino 3038 F pulseaudio
   /dev/snd/controlC0:  iheino 3038 F pulseaudio
   /dev/snd/pcmC0D0c:   iheino 3038 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Feb 17 21:23:03 2023
  InstallationDate: Installed on 2022-04-27 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 2007722] [NEW] amdgpu updateMST crash 43s after resume

[Tuomas Heino]

Public bug reported:

Amdgpu has tendency of crashing after resume when MST responses of the
displays waking up aren't what it expects.

Sadly launchpad does not provide a way to review the logs sent by
ubuntu-bug before submit button here, apparently can preview only
locally prior to sending report.

More details to be added after reboot.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-58-generic 5.15.0-58.64
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  iheino 3038 F pulseaudio
 /dev/snd/controlC0:  iheino 3038 F pulseaudio
 /dev/snd/pcmC0D0c:   iheino 3038 F...m pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Feb 17 21:23:03 2023
InstallationDate: Installed on 2022-04-27 (296 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-58-generic N/A
 linux-backports-modules-5.15.0-58-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug jammy

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

Title:
  amdgpu updateMST crash 43s after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Amdgpu has tendency of crashing after resume when MST responses of the
  displays waking up aren't what it expects.

  Sadly launchpad does not provide a way to review the logs sent by
  ubuntu-bug before submit button here, apparently can preview only
  locally prior to sending report.

  More details to be added after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  iheino 3038 F pulseaudio
   /dev/snd/controlC0:  iheino 3038 F pulseaudio
   /dev/snd/pcmC0D0c:   iheino 3038 F...m pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Feb 17 21:23:03 2023
  InstallationDate: Installed on 2022-04-27 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis 

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

[Roemer Claasen]

** Description changed:

  After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from
  5.15.0.60) suspend/wake up is broken on my laptop.
  
  The system refuses to wake up in about 50% of the cases, seemingly
- random.
+ random. The only "solution" is a forced system power down.
  
  Reverting back to 5.15.0.60 resolves this issue immediately.
  
  I suspect some patch was not re-applied to 5.19, since there are many
  postings on Reddit (for instance) about sleep problems with newer AMD
  CPUs, but 5.15 was running beautifully.
  
  My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU.

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

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

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

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

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

  Reverting back to 5.15.0.60 resolves this issue immediately.

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

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

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


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

[Kernel-packages] [Bug 2007718] [NEW] HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u

[Roemer Claasen]

Public bug reported:

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

The system refuses to wake up in about 50% of the cases, seemingly
random.

Reverting back to 5.15.0.60 resolves this issue immediately.

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

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

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

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

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

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

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

  The system refuses to wake up in about 50% of the cases, seemingly
  random.

  Reverting back to 5.15.0.60 resolves this issue immediately.

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

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

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


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

[Kernel-packages] [Bug 1994974] Re: Azure: hv_netvsc: Fix race between VF offering and VF association message from host

[Tim Gardner]

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

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

Title:
  Azure: hv_netvsc: Fix race between VF offering and VF association
  message from host

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

Bug description:
  SRU Justification

  [Impact]

  During vm boot, there might be possibility that vf registration call
  comes before the vf association from host to vm.

  And this might break netvsc vf path, this is in order to prevent the
  same block vf registration until vf bind message comes from host.

  [Test Plan]

  Microsoft tested

  [Where things could go wrong]

  The 5.4 backport patch could hang waiting for a VF addition to
  complete.

  [Other Info]

  SF: #00347129

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


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

[Kernel-packages] [Bug 2004604] Re: Azure: mana: Fix IRQ name - add PCI and queue number

[Tim Gardner]

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

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

Title:
  Azure: mana: Fix IRQ name - add PCI and queue number

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

Bug description:
  SRU Justification

  [Impact]

  The PCI and queue number info is missing in MANA IRQ names.
  request_irq() will fail if the name is incorrect.

  [Test Case]

  Load the MANA module and ascertain if it detected a device.

  [Where things could go wrong]

  Existing instances could fail to initialize.

  [Other Info]

  SF: #00353708

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


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

[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs

[JianlinLv]

Attach patch to fix this issue

** Patch added: "0001-UBUNTU-audit-fix-memory-leak-of-audit_log_lsm.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+attachment/5648111/+files/0001-UBUNTU-audit-fix-memory-leak-of-audit_log_lsm.patch

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

Title:
  Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in
  kmalloc-2k slabs

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

Bug description:
  Since updating to kernel 5.15.0-46-generic (package version
  5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel
  memory; our first server with 8 GB of RAM just fatally OOMed, causing
  us to detect this. Inspection of OOM reports, /proc/meminfo, and
  /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k
  slabs:

  Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab 
info:
  Aug 23 12:51:11 cluster kernel: [361299.864757] Name  
Used  Total
  [...]
  Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k   
6676584KB6676596KB

  Most of our machines appear to be leaking slab memory at a rate of
  around 20 to 40 Mbytes/hour, with some machines leaking much faster;
  the champions are leaking kernel memory at 145 Mbytes/hour and 237
  Mbytes/hour.

  We aren't running any proprietary kernel modules and our only unusual
  kernel configuration is that we've disabled AppArmor with 'apparmor=0'
  on the kernel command line.

  /proc/version_signature:
  Ubuntu 5.15.0-46.49-generic 5.15.39

  Full kernel command line from the Dell R240 system that fatally OOMd:
  BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 
console=tty0 apparmor=0

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


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

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

[Daniel Allen]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648110/+files/acpidump.txt

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

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] PaInfo.txt

[Daniel Allen]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2007473/+attachment/5648101/+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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] RfKill.txt

[Daniel Allen]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/2007473/+attachment/5648107/+files/RfKill.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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] PulseList.txt

[Daniel Allen]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648106/+files/PulseList.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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] Lsusb-t.txt

[Daniel Allen]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648099/+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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] Lsusb.txt

[Daniel Allen]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2007473/+attachment/5648098/+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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] Lspci.txt

[Daniel Allen]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2007473/+attachment/5648096/+files/Lspci.txt

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] IwConfig.txt

[Daniel Allen]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648095/+files/IwConfig.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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

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

[Daniel Allen]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648094/+files/CurrentDmesg.txt

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

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] AudioDevicesInUse.txt

[Daniel Allen]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648093/+files/AudioDevicesInUse.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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59

  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06

  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.

  Best Regards,

  Daniel

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-12-11 (67 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. XPS 9315
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-32-generic N/A
   linux-backports-modules-5.19.0-32-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.10
  Tags:  jammy wayland-session
  Uname: Linux 5.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2023
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 00KRKP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
  dmi.product.family: XPS
  dmi.product.name: XPS 9315
  dmi.product.sku: 0B14
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2007473] Re: Bug In Intel Mesa Graphics From Latest Linux Headers

[Daniel Allen]

apport information

** Tags added: apport-collected jammy wayland-session

** Description changed:

   affects Ubuntu 22.04.1
  
  Hello,
  
  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.
  
  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04
  
  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: linux-image-generic-hwe-22.04:amd64 (5.15.0.60.58, 5.19.>
  End-Date: 2023-02-15  14:14:59
  
  Start-Date: 2023-02-15  14:16:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Remove: linux-headers-5.15.0-58-generic:amd64 (5.15.0-58.64), lin>
  End-Date: 2023-02-15  14:16:06
  
  These are some of the latest upgrades from my logs. Please note that this
  issue did not exist in the LTS release until this recent update. I have
  been using it since December. It was immediately present on 22.10 and why I
  went back to 22.04. Seems updates finally caught up to what is in 22.10.
  
  Best Regards,
  
  Daniel
+ 
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: amd64
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-12-11 (67 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
+ MachineType: Dell Inc. XPS 9315
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=b87c2954-b95d-486f-832a-27f29ee17fdd ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-32-generic N/A
+  linux-backports-modules-5.19.0-32-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.10
+ Tags:  jammy wayland-session
+ Uname: Linux 5.19.0-32-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/04/2023
+ dmi.bios.release: 1.7
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.7.1
+ dmi.board.name: 00KRKP
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn00KRKP:rvrA00:cvnDellInc.:ct10:cvr:sku0B14:
+ dmi.product.family: XPS
+ dmi.product.name: XPS 9315
+ dmi.product.sku: 0B14
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2007473/+attachment/5648092/+files/AlsaInfo.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/2007473

Title:
  Bug In Intel Mesa Graphics From Latest Linux Headers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   affects Ubuntu 22.04.1

  Hello,

  I have an issue running Intel Mesa graphics (ADL GT2) (VGA compatible
  controller: Intel Corporation Device 46aa (rev 0c)) on a Dell XPS laptop
  after the latest linux headers upgrade. I am using Ubuntu 22.04.1 LTS and I
  stayed away from the latest non LTS release because this issue already
  existed there. The problem I have is that every so often in the display I
  will get rainbow horizontal lines that run from one side of the display to
  the other and it flashes for like a second or 2 and then disappears. It
  seems to be triggered by mouse movements. It will be anywhere from 2 to 6
  lines of pixels.

  Start-Date: 2023-02-15  11:18:03
  Commandline: aptdaemon role='role-commit-packages' sender=':1.125'
  Upgrade: alsa-ucm-conf:amd64 (1.2.6.3-1ubuntu1.3, 1.2.6.3-1ubuntu>
  End-Date: 2023-02-15  11:18:04

  Start-Date: 2023-02-15  14:14:15
  Commandline: aptdaemon role='role-commit-packages' sender=':1.162'
  Install: linux-modules-extra-5.19.0-32-generic:amd64 (5.19.0-32.3>
  Upgrade: 

[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time

[João Pedro Seara]

I spoke to soon. Problem still appears. : - )

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

Title:
  nvme drive fails after some time

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Groovy:
  Fix Released
Status in Debian:
  New

Bug description:
  Sorry for the vague title. I thought this was a hardware issue until
  someone else online mentioned their nvme drive goes "read only" after
  some time. I tend not to reboot my system much, so have a large
  journal. Either way this happens once in a while. The / drive is fine,
  but /home is on nvme which just disappears. I reboot and everything is
  fine. But leave it long enough and it'll fail again.

  Here's the most recent snippet about the nvme drive before I restarted
  the system.

  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting 

   
  Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting 

   
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset 
controller
  Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset 
controller
  Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371
  Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure 
status: -19
  Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more 
than 120 seconds.
  Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0   731  2 0x4000
  Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, 
CSTS=0x1
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123967, lost async page write
  Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): 
__ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading 
directory lblock 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123917, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 240123909, lost async page write
  Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, 
sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
  Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical 
block 0, lost sync page write
  Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing 
superblock

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:56:28 2021
  InstallationDate: Installed on 2020-08-15 (146 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel Corporation NUC8i7HVK
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic 
root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7
  RebootRequiredPkgs:
   linux-image-5.8.0-36-generic
   linux-base
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-34-generic N/A
   

[Kernel-packages] [Bug 1995004] Re: Increase stability with connection tracking offload

[Bodong Wang]

This bug is not presenting on 5.15 kernel.

** Changed in: linux-bluefield (Ubuntu Jammy)
   Status: Fix Committed => Invalid

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

Title:
  Increase stability with connection tracking offload

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

Bug description:
  * Explain the bug(s)

  Currently qdisc ingress handling (sch_handle_ingress()) doesn't
  set a return value and it is left to the old return value of
  the caller (__netif_receive_skb_core()) which is RX drop, so if
  the packet is consumed, caller will stop and return this value
  as if the packet was dropped.

  Also, include set of patches to increase stability with connection
  tracking offload, including reduced cpu load and possible deadlock on
  cleanup.

  * What it could break.

  Packet on egress tc rule forwarding to a ingress tc rule will drop.
  High cpu load. Possible deadlock on cleanup.

  * How to test

  Run connection tracking hw offload scenario with millions of flows,
  check cpu load, test cleanup and readd scenarios.

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


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

[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

[LucidBrot]

I have the same problem. It came up because I upgraded from ubuntu 18.04
LTS to 22.04 LTS (via 20.04 and then immediately upgrading again).
Mainly leaving my comment here to indicate that this is an issue that
affects many users.

The github issue at
https://github.com/openzfs/zfs/issues/13709#issuecomment-1292880434
contains a workaround to make the system boot again after the zfs
version upgrade, but imo this needs to be fixed urgently because:

* Not everyone will find that workaround
* Even after that workaround, old snapshots are still inaccessible
* The fix seems to be easy for the repo maintainers, since the issue has been 
fixed in the latest version of zfs already ( as mentioned in 
https://github.com/openzfs/zfs/issues/13709#issuecomment-1433505102 )

@Walter thank you for the "How to apply the patch" guidance. I will try it once 
I have more time, since I noticed I already have zfs-dkms installed, but also a 
leftover kmod from 2020 and I don't feel confident that I won't break anything 
on accident.
Does it still make sense to apply your patch, or would I rather figure out how 
to install zfs directly from the source from github? As far as I understand, 
dkms builds the kernel modules from source anyway?

Cheers,
lucid

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I have a server that has been running its data volume using ZFS in
  20.04 without any problem. The volume is using ZFS encryption and a
  raidz1-0 configuration. I performed a scrub operations before the
  upgrade and it did not find any problem. After the reboot for the
  upgrade, I was welcomed with the following message:

  status: One or more devices has experienced an error resulting in data
  corruption.  Applications may be affected.
  action: Restore the file in question if possible.  Otherwise restore the
  entire pool from backup.
 see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

  The volumes still do not have any checksum error but there are 5 zvols
  that are not accessible. zpool status displays a line similar to the
  below for each of the five:

  errors: Permanent errors have been detected in the following files:   



  tank/data/data:<0x0>

  I run a scrub and it has not identified any problem but the error
  messages are not there and the data is still not available. There are
  10+ other zvols in the zpool that do not have any kind of problem. I
  have been unable to identify any correlation between the zvols that
  are failing.

  I have seen people reporting similar problems in github after the
  20.04 to the 22.04 upgrade (see
  https://github.com/openzfs/zfs/issues/13763). I wonder how widespread
  the problem will be as more people upgrades to 22.04.

  I will try to downgrade the version of zfs in the system and report
  back

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: zfsutils-linux 2.1.4-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Aug 20 22:24:54 2022
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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


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

[Kernel-packages] [Bug 1991113] Re: "source" PKA driver Kconfig in mellanox/Kconfig

[Meriton Tuli]

# grep MLXBF_PKA  /boot/config-5.15*-bluefield
CONFIG_MLXBF_PKA=m

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

Title:
  "source" PKA driver Kconfig in mellanox/Kconfig

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

Bug description:
  PKA driver Kconfig needs to be "sourced" in mellanox/Kconfig. This
  makes MLXBF_PKA config option visible by the kernel configuration
  system and is needed to actually build PKA driver.

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


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

[Kernel-packages] [Bug 1999309] Re: mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC

[Meriton Tuli]

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

Title:
  mmc: sdhci-of-dwcmshc: Enable host V4 support for BlueField-3 SoC

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

Bug description:
  SRU Justification:

  [Impact]
  This change is needed to for eMMC host setting on BlueField-3 SoC to be 
consistent with UEFI setting and also for stability reason.

  [Fix]
  The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC.

  [Test Case]
  Same functionality as on BlueField-1/2.

  [Regression Potential]
  Can be considered minimum since similar functionality was already included in 
the focal branch for BlueField-1/2. The driver is different, but functionality 
and eMMC device files will be the same.

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


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

[Kernel-packages] [Bug 2003353] Re: Azure: Fix race on per-CQ variable napi_iperf panic fix

[Tim Gardner]

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

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

Title:
  Azure: Fix race on per-CQ variable napi_iperf panic fix

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

Bug description:
  SRU Justification

  [Impact]

  This patch [1]1 is requested by MSFT Linux Systems Group to fix a race
  condition that can cause a panic in napi_iperf().

  [1] -
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=18010ff776fa42340efc428b3ea6d19b3e7c7b21

  A number of prerequisite patches are required. v5.15.83 contains this
  patch, however v5.19 stable does not.

  [Test Case]

  MSFT tested and approved, "Please merge in both the kernels, LSG
  finished the validation".

  [Where things could go wrong]

  Test results are good. Regression potential seems low.

  [Other Info]

  SF: #00350135

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


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

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

[Tim Gardner]

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

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

Title:
  Azure: Performance improvement for TDX

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Kinetic:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

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

  [Fix]

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

  [Where things could go wrong]

  TDX guests may perform worse.

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


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

[Kernel-packages] [Bug 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read

[Tien Do]

** Tags removed: kernel-spammed-jammy-linux-bluefield 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1989495

Title:
  mlxbf_gige: need to clear MDIO gateway lock after read

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  The BlueField-2 GIGE logic accesses the MDIO device via reads/writes
  to a gateway (GW) register. The MDIO GW lock is set after read. Make
  sure to always clear to indicate that the GW register is not being used.
  If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO
  accesses will be blocked and PHY device will be inaccessible.

  [Fix]
  For each MDIO read and write transaction, the last step should
  be to clear the MDIO GW lock.

  [Test Case]
  Boot the BlueField-2 platform
  Bring up the "oob_net0" interface via DHCP or static IP
  Ping and file transfer over "oob_net0" should work properly
  Bounce the "oob_net0" interface a few times and repeat tests

  [Regression Potential]
  * Low risk for causing a regression, tested well in our lab.

  [Other]
  * None

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


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

[Kernel-packages] [Bug 1991551] Re: i2c-mlxbf.c: Sync up driver with upstreaming

[Tien Do]

** Tags removed: kernel-spammed-jammy-linux-bluefield 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1991551

Title:
  i2c-mlxbf.c: Sync up driver with upstreaming

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  Fix Released
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  Several i2c-mlxbf.c patches have been upstreamed recently and are in
  linux-next at the moment. So revert all changes in both Focal (5.4)
  and Jammy (5.15) and cherry-pick all changes from linux-next master.

  IMPORTANT NOTE: The new linux i2c support for BF3 also REQUIRES
  upgrading the UEFI firmware version. For BF1 and BF2 however, this
  driver should be backward compatible with older UEFI versions.

  [Fix]

  * There is a total of 17 commits: 8 reverts, 8 cherry-picks from
  linux-next and one internal "UBUNTU: SAUCE:" to ad the driver version.
  Following is the list of commits cherry-picked.

  * i2c: mlxbf: incorrect base address passed during io write
  From 


  * i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
  From 


  * i2c: mlxbf: remove IRQF_ONESHOT
  From 


  * i2c: mlxbf: Fix frequency calculation
  From 


  * i2c: mlxbf: support lock mechanism
  From 


  * i2c: mlxbf: add multi slave functionality
  From 


  * i2c: mlxbf: support BlueField-3 SoC
  From 


  * i2c: mlxbf: remove device tree support
  From 


  * Also add the i2c driver version to keep track of the changes
  internally.

  [Test Case]

  * Check that the i2c driver loads without errors on BF1 and BF2 (dmesg, and 
check i2c1 sysfs is created)
  * Check that the i2c module can be removed and reloaded without errors.
  * Check that IPMB services work successfully on systems with BMC. This is the 
best way to test the i2c driver. Run ipmitool command from the BF: ipmitool mc 
info
  * Run ipmitool from the BMC as well: ipmitool -I ipmb mc info
  * This driver should be backward compatible
  * Make sure this driver is backward compatible with older UEFI version (only 
applicable for BF1 and BF2)
  * Make sure this driver works for BF1, BF2 and BF3 with the latest UEFI 
version.

  [Regression Potential]

  * The i2c driver could fail to load because the UEFI firmware hasn't been 
upgraded
  * The i2c driver would fail to load due to a bug
  * IPMB code which utilises the i2c driver fails to work (ipmitool commands)

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


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

[Kernel-packages] [Bug 1998863] Re: mlxbf-pmc: Fix event string typo

[Tien Do]

** Tags removed: kernel-spammed-focal-linux-bluefield 
kernel-spammed-jammy-linux-bluefield verification-needed-focal 
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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1998863

Title:
  mlxbf-pmc: Fix event string typo

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

Bug description:
  SRU Justification:

  [Impact]

  Due to a typo, duplicate events are shown

  [Fix]

  * Fix event name typo.

  [Test Case]

  * cd /sys/class/hwmon/hwmon0/tilenetX ("X" may be 0..7)
  root@localhost:/sys/class/hwmon/hwmon0/tilenet3# cat event_list | grep CRED
  15: CDN_DIAG_N_OUT_OF_CRED
  16: CDN_DIAG_S_OUT_OF_CRED
  17: CDN_DIAG_E_OUT_OF_CRED
  18: CDN_DIAG_W_OUT_OF_CRED
  19: CDN_DIAG_C_OUT_OF_CRED
  25: DDN_DIAG_N_OUT_OF_CRED
  26: DDN_DIAG_S_OUT_OF_CRED
  27: DDN_DIAG_E_OUT_OF_CRED
  28: DDN_DIAG_W_OUT_OF_CRED
  29: DDN_DIAG_C_OUT_OF_CRED
  35: NDN_DIAG_N_OUT_OF_CRED  <== Incorrectly was set to NDN_DIAG_S_OUT_OF_CRED
  36: NDN_DIAG_S_OUT_OF_CRED
  37: NDN_DIAG_E_OUT_OF_CRED
  38: NDN_DIAG_W_OUT_OF_CRED
  39: NDN_DIAG_C_OUT_OF_CRED
   

  [Regression Potential]

  * Duplicate events still get shown

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


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

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

[Tim Gardner]

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

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

Title:
  Azure: Fix TDX backport

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

Bug description:
  SRU Justification

  [Impact]

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

  [Fix]

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

  [Test Plan]

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

  [Where things could go wrong]

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

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


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

[Kernel-packages] [Bug 1991151] Re: mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

[Khoa Vo]

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

Title:
  mlxbf_gige: need to revert SAUCE patch for "clear MDIO gateway lock"

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

Bug description:
  SRU Justification:

  [Impact]

  The Jammy repo contains the following SAUCE patch:
  UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read

  This patch is now in mainline Linux kernel, so the SAUCE patch
  can be reverted and replaced with the upstream commit SHA.

  [Fix]

  The fix requires two parts, the first of which is addressed by
  this bug. A second bug will be created to add the upstream
  commit to the repo. The fix to this bug is a revert of the SAUCE patch
  8d2dbbd437a1 UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read

  [Test Case]

  Boot platform and bring up "oob_net0" interface properly
  Test that network traffic works properly

  [Regression Potential]

  Low, as this logic is well tested.

  [Other]

  Will add a note to this bug with the second bug's number,
  after the second bug is created. The second bug is for
  adding the upstream commit to the Jammy repo.

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


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

[Kernel-packages] [Bug 1991403] Re: mlxbf_gige: fix devm_ioremap error handling

[Khoa Vo]

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

Title:
  mlxbf_gige: fix devm_ioremap error handling

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

Bug description:
  SRU Justification:

  [Impact]

  The following upstream commit was recently added to Jammy:
3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk

  This patch added driver logic that includes a "devm_ioremap"
  call, but the error handling logic pertaining to this call
  is incorrect.

  [Fix]

  The "devm_ioremap" function returns NULL on error, it doesn't 
  return error pointers.  The error handling logic has been
  fixed accordingly.

  [Test Case]

  Boot platform and bring up "oob_net0" interface properly
  Test that network traffic works properly

  [Regression Potential]

  Low, as the patch was reviewed upstream

  [Other]

  None

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


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

[Kernel-packages] [Bug 1995148] Re: mlxbf_gige: need to add BlueField-3 support

[Tien Do]

** Tags removed: kernel-spammed-jammy-linux-bluefield 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1995148

Title:
  mlxbf_gige: need to add BlueField-3 support

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

Bug description:
  SRU Justification:

  [Impact]

  The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
  support the BlueField-3 SoC.  The "mlxbf_gige" driver which
  supports BlueField-2 SoC currently will be extended to include
  the BlueField-3 support.

  [Fix]
  The BlueField-3 support will be provided in the form of a set
  of 4 patches, to be sent in as a pull request. 

  [Test Case]
  BlueField-2: Boot platform and bring up "oob_net0" interface properly
   Test that network traffic works properly
  BlueField-3: Tested in simulator platforms and early silicon

  [Regression Potential]
  Since this is initial support there is chance of regression
  on BlueField-2 platforms, but it's been tested there.

  [Other]
  n/a

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


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

[Kernel-packages] [Bug 1998857] Re: tick/rcu: Stop allowing RCU_SOFTIRQ in idle

[Tien Do]

** Tags removed: kernel-spammed-jammy-linux-bluefield 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1998857

Title:
  tick/rcu: Stop allowing RCU_SOFTIRQ in idle

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

Bug description:
  * Explain the bug
  RCU_SOFTIRQ used to be special in that it could be raised on purpose
  within the idle path to prevent from stopping the tick. Some code still
  prevents from unnecessary warnings related to this specific behaviour
  while entering in dynticks-idle mode.

  However the nohz layout has changed quite a bit in ten years, and the
  removal of CONFIG_RCU_FAST_NO_HZ has been the final straw to this
  safe-conduct. Now the RCU_SOFTIRQ vector is expected to be raised from
  sane places.

  * Brief explanation of fixes
   
  Stop allowing RCU_SOFTIRQ in idle
   
  * How to test
   
  In boot dmesg, the warning should be gone.
   
  * What it could break.
   
  N/A

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


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

[Kernel-packages] [Bug 2002501] Re: mlxbf-pmc support for BlueField-3

[Khoa Vo]

** Tags added: verification-done-jammy

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

Title:
  mlxbf-pmc support for BlueField-3

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

Bug description:
  SRU Justification:

  [Impact]
  Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 
devices. BlueField-3 is not supported.

  [Fix]
  Add support for BlueField-3 devices by adding new access mechanism for 
programming and reading counter values as in the new design, along with the 
list of supported events in each HW block in BlueField-3.

  [Test Case]
  Previously, the driver would not be loaded when the OS is loaded on a 
BlueField-3 card. With the fix, the driver should get loaded and create sysfs 
entries as a hwmon device under /sys/class/hwmon/hwmon0.

  [Regression Potential]
  The ACPI table needs to be in sync with this change since it depends on newly 
introduces parameters such as mss_enable and llt_enable, which were not present 
earlier.

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


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

[Kernel-packages] [Bug 2001564] Re: Kernel crash due to Bluefield pka TRNG ioctl call

[Khoa Vo]

** Tags added: verification-done-jammy

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

Title:
  Kernel crash due to Bluefield pka TRNG ioctl call

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

Bug description:
  SRU Justification

  [Impact]
  Bluefield 3 on Ubuntu 22.04 and OpenSSL 3.0.2, encounters kernel crash/oops 
when HTTPS client uses OpenSSL with PKA engine during TLS handshake. The issue 
is with TRNG ioctl call. The kernel logs show the following errors.

  Unable to handle kernel access to user memory outside uaccess routines
  at virtual address ce65d328

  BF3 on Ubuntu 22.04, OpenSSl 3.0.2

  [Fix]
  * Change RNG ioctl kernel handler code to copy data from user to kernel space.

  [Test Case]
  openssl rand -engine pka 512

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


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

[Kernel-packages] [Bug 2002852] Re: mlxbf-ptm: power and thermal management debugfs driver

[Khoa Vo]

** Tags added: verification-done-focal

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

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

Title:
  mlxbf-ptm: power and thermal management debugfs driver

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  mlxbf-ptm is a kernel driver that provides debufgs interface for
  system software to monitor Bluefield devices' power and thermal
  management parameters.

  [Fix]

  * New driver added

  [Test Case]

  * After installing the kernel module, debugfs entry at 
/sys/kernel/debug/mlxbf-ptm will be created
  * monitors/status folder contains read-only parameters reported from the 
Bluefield device

  [Regression Potential]

  * Minimal - as these are read-only parameters that report Bluefield
  device information.

  [Other]
  * This code is likely to change depending on feedback we received from 
maintainers.

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


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

[Kernel-packages] [Bug 2002689] Re: mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3 SoC

[Khoa Vo]

** Tags added: verification-done-jammy

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

Title:
  mlxbf-tmfifo: Add ctrl message and MAC configuration For BlueField-3
  SoC

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

Bug description:
  
  SRU Justification:

  [Impact]

  
  This is a porting commit from 
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1927253.

  
  [Fix]
  * N/A

  [Test Case]
  * Set DISPLAY_LEVEL to 1 in /dev/rshim0/misc and do 'cat /dev/rshim0/misc' 
from external rshim driver.
The rshim MAC address will show up.

  # cat /dev/rshim0/misc
  DISPLAY_LEVEL 1 (0:basic, 1:advanced, 2:log)
  BOOT_MODE 1 (0:rshim, 1:emmc, 2:emmc-boot-swap)
  BOOT_TIMEOUT 100 (seconds)
  DROP_MODE 0 (0:normal, 1:drop)
  SW_RESET 0 (1: reset)
  DEV_NAME usb-1-1.1
  DEV_INFO BlueField-2(Rev 0)
  OPN_STR MBF2M516A-EEEO
  BOOT_RESET_SKIP 0 (1: skip)
  PEER_MAC 00:1a:ca:ff:ff:01 (rw)
  PXE_ID 0x (rw)
  VLAN_ID 0 0 (rw)
  * echo "PEER_MAC xx:xx:xx:xx:xx:xx" > /dev/rshim0/misc to modify the MAC 
address, which will take effect in next boot.

  [Regression Potential]
  * This is a new enhancement and is backward-compatible with previous behavior.

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


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

[Kernel-packages] [Bug 1986964] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module failed to build

[Launchpad Bug Tracker]

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

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

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: sdhci_pci cqhci sdhci r8169 i2c_piix4 realtek wmi 
i2c_scmi
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DKMSKernelVersion: 5.17.0-1015-oem
  Date: Thu Aug 18 16:08:37 2022
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:3307:26:
 error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2022-01-30 (200 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu8
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: Upgraded to jammy on 2022-08-18 (0 days ago)

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


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

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

[Andrei Gherzan]

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Andrei Gherzan (agherzan)

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

** No longer affects: linux (Ubuntu Bionic)

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

Title:
  Fix selftests/ftracetests/Meta-selftests in Focal

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

Bug description:
  [SRU Justification]

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

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

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

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

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


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

[Kernel-packages] [Bug 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi

[Bartlomiej Zolnierkiewicz]

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

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

Title:
  mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  This change is needed so the sdhci-of-dwcmshc driver can be loaded 
automatically when built ad kernel module.

  [Fix]
  add the missing device table IDs for acpi

  [Test Case]
  Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the 
output contains 'acpi*:MLNXBF30:*'.

  [Regression Potential]
  No changes to driver funtionality.

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


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

[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

[Stefan Bader]

Committed via stable v5.15.86.

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

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

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  Included in v6.2-rc1
  d899aa668498 PCI: vmd: Disable MSI remapping after suspend

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

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


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

[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)

[Stefan Bader]

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

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

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

Title:
  Screen freeze after resuming from suspend (nvme0: I/O timeout)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-6.0 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  The system hangs after S3 with VMD mode is on.

  [Fix]
  Intel provides a fix and still under discussion
  
https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/

  Included in v6.2-rc1
  d899aa668498 PCI: vmd: Disable MSI remapping after suspend

  [Test]
  Verified by us and ODM.

  [Where problems could occur]
  The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any 
regression.

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


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