from:"Adam"

[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-10 Thread Adam Smith

Hi Jeffrey, yes that workaround solves the problem.  I should have
probably said that.

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

Status in Linux:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  Confirmed
Status in linux source package in Noble:
  Fix Committed
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-10 Thread Adam Smith

lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation Celeron 
N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller 
[8086:5a84] (rev 0b)
Subsystem: Acer Incorporated [ALI] Celeron N3350/Pentium N4200/Atom 
E3900 Series Integrated Graphics Controller [1025:1190]
Kernel driver in use: i915
Kernel modules: i915

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

Status in Linux:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  Confirmed
Status in linux source package in Noble:
  Fix Committed
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-10 Thread Adam Smith

Installed 24.04 to a usb drive. Still flickering and with linux-
oem-6.11.  Having a quick look at the patch I guess my device id is
missing.  As noted in the comments above, this hits more than just
Skylake processors.  I think mine is an Apollo lake.

** Tags removed: verification-needed-noble-linux-oem-6.11
** Tags added: verification-failed-noble-linux-oem-6.11

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

Status in Linux:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  Confirmed
Status in linux source package in Noble:
  Fix Committed
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-09 Thread Adam Smith

I've corrected my previous message as I'm actually running 22.04.  I've
tried the 6.8.0-44 kernel which still has the fault.  I don't think
there are any higher packages than that in 22.04?  So I manually
downloaded and installed the 6.11.0-1004-oem and 6.11.0-6 kernels from
24.04/24.10, but these also still have the fault.  With these latter
kernels I do get an update-initramfs warning relating to i915 (missing
bmg_dmc.bin and xe2lpd_dmc.bin files), so I'm not sure if that is a fair
test.  Updating linux-firmware turned into a bit of a nightmare of
dependencies so I gave up.

Hopefully a 24.04 user will be able to test 6.11 properly.

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

Status in Linux:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  Confirmed
Status in linux source package in Noble:
  Fix Committed
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2062951] Re: Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on Linux 6.8

2024-09-09 Thread Adam Smith

I believe I have this bug with my N4200 Acer swift laptop.  I was
convinced it was a hardware problem.  Screen flashing (the picture gets
stretched and repeated horizontally while flashing) when the mouse
pointer is at certain positions in the screen.  It is easily repeatable
in Lubuntu 24.04 with the hwe kernel with the mouse just above the task
bar on the right hand side.  I spent the weekend looking for a new
laptop, but before I parted with some money I thought I better double
check there was not a cheaper solution!

Plugging in an external monitor to the hdmi port fixes the problem.  As
does forcing the hdmi port on with the laptop screen mirrored to that
port.  So that's another workaround.

Reverting to a 6.5 kernel also fixes the problem.  This led me to this
bug report.  If you haven't done that though, it is hard to find this
bug.

Surely this should be urgently fixed?  I can't be the only one to be
looking at buying new hardware unnecessarily?

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

Title:
  Random flickering with Intel i915 (Gen9 GPUs in 6th-8th gen CPUs) on
  Linux 6.8

Status in Linux:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-6.8 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-hwe-6.8 source package in Jammy:
  Confirmed
Status in linux source package in Noble:
  Fix Committed
Status in linux-hwe-6.8 source package in Noble:
  Invalid
Status in linux source package in Oracular:
  In Progress
Status in linux-hwe-6.8 source package in Oracular:
  Invalid

Bug description:
  SRU Justification

  [Impact]
  The flickering predominantly occurs when the mouse cursor is in the bottom 
quarter of the screen and stops when the cursor leaves this area.
  Extensive testing across various kernel versions revealed that the issue 
became apparent from kernel version 6.8.0 onward, correlating with the 
mentioned configuration changes, CONFIG_INTEL_IOMMU_DEFAULT_ON and 
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
  The problem persists in the latest drm tip.

  [Fix]
  As an immediate workaround, adding 'intel_iommu=igfx_off' to the kernel 
command line has been found to effectively eliminate the flickering issue. 
  This patch proposes the same behavior as 'intel_iommu=igfx_off' and apply the 
rule to all Intel SKL GPU IDs.

  [Test]
  1. Boot up to desktop with 6.8.0-x kernels
  2. Moving cursor around the desktop
  3. There should be no flicker while cursor is moving

  [Where problems could occur]
  For virtualized environments using hardware-assisted virtualization for 
graphics (such as VFIO or mediated pass-through), disabling IOMMU for graphics 
could either disable these features or reduce their security and efficiency.
  Usually, users pass the 'intel_iommu=on' by themselves when they are using 
related features. So, the impact of this change is minimal.

  ===

  After migrating Mantic 23.10 install to Linux 6.8.0, I am experiencing heavy 
flickering at random.
  It happens after a moderate to heavy on screen activity like window 
switching, scrolling etc.
  It never happens when playing video or when there is no interaction using 
keyboard/pointer.

  It tend to happen when the mouse cursor is in the bottom quarter of the 
screen and stops immediately when the cursor leaves that screen region.
  Around the same time the following appears in kernel log:
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  Happens on both X11 and Wayland on both KDE plasma and Mate (though
  less).

  I first encountered the issue with Linux 6.8.0-11 and it still happens with 
Ubunutu's 6.8.0-28 and Mainline 6.8.7.
  Kernels 6.6, 6.5, 6.1 and older did not have that issue.

  Hardware is: Dell XPS 9350, Vendor Intel, Driver i915, Skylake GT2 [HD 
Graphics 520]
  Software: Ubuntu 23.10, KDE Plasma 5.27.10 / Mate 1.26

  Attaching kernel log for 6.8.0-28

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2062951/+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 2063179] [NEW] package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic package pos

2024-04-22 Thread Dimitris Adam

Public bug reported:

the problem occurred during installation while trying to remove previous
package

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Apr 23 09:40:31 2024
ErrorMessage: installed linux-modules-nvidia-470-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-01-25 (88 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.12
SourcePackage: linux-restricted-modules-hwe-6.5
Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 
failed to install/upgrade: installed linux-modules-nvidia-470-6.5.0-27-generic 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package linux-modules-nvidia-470-6.5.0-27-generic
  6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed linux-
  modules-nvidia-470-6.5.0-27-generic package post-installation script
  subprocess returned error exit status 1

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

Bug description:
  the problem occurred during installation while trying to remove
  previous package

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Apr 23 09:40:31 2024
  ErrorMessage: installed linux-modules-nvidia-470-6.5.0-27-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-01-25 (88 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.3
   apt  2.4.12
  SourcePackage: linux-restricted-modules-hwe-6.5
  Title: package linux-modules-nvidia-470-6.5.0-27-generic 
6.5.0-27.28~22.04.1+2 failed to install/upgrade: installed 
linux-modules-nvidia-470-6.5.0-27-generic package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.5/+bug/2063179/+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 2056140] [NEW] Nvidia crashes very often ( static image)

2024-03-04 Thread Dimitris Adam

Public bug reported:

Ubuntu 22.04.4 LTS

NVIDIA driver metapackage from nvdia-driver-470 (proprietary,tested)

crashes regurarly (static image )

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-515 (not installed)
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  5 09:27:44 2024
InstallationDate: Installed on 2024-01-25 (39 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nvidia-graphics-drivers-525
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-525 (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 nvidia-graphics-drivers-525 in Ubuntu.
https://bugs.launchpad.net/bugs/2056140

Title:
  Nvidia crashes very often ( static image)

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

Bug description:
  Ubuntu 22.04.4 LTS

  NVIDIA driver metapackage from nvdia-driver-470 (proprietary,tested)

  crashes regurarly (static image )

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nvidia-driver-515 (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 09:27:44 2024
  InstallationDate: Installed on 2024-01-25 (39 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: nvidia-graphics-drivers-525
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2056140/+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 2051424] [NEW] libnvidia-common-535: packaging problem

2024-01-27 Thread Adam Vodopjan

Public bug reported:

I'm on jammy, all available upgrades installed. My sources:

deb http://archive.ubuntu.com/ubuntu/ jammy main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted 
universe multiverse
deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted 
universe multiverse

There are two problems with libnvidia-common-535 packaging:

1. Outdated versions are still offered

2. It is phasing all the time, at %0, even though not listed as a phasing one at
https://ubuntu-archive-team.ubuntu.com/phased-updates.html

Compare this

> apt-cache policy libnvidia-cfg1-535
libnvidia-cfg1-535:
  Installed: 535.154.05-0ubuntu0.22.04.1
  Candidate: 535.154.05-0ubuntu0.22.04.1
  Version table:
 *** 535.154.05-0ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
100 /var/lib/dpkg/status

to this

> apt-cache policy libnvidia-common-535
libnvidia-common-535:
  Installed: 535.154.05-0ubuntu0.22.04.1
  Candidate: 535.154.05-0ubuntu0.22.04.1
  Version table:
 *** 535.154.05-0ubuntu0.22.04.1 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
100 /var/lib/dpkg/status
 535.146.02-0ubuntu0.22.04.1 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
 535.129.03-0ubuntu0.22.04.1 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
 535.113.01-0ubuntu0.22.04.3 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
 535.104.05-0ubuntu0.22.04.4 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
 535.86.05-0ubuntu0.22.04.1 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages
 535.54.03-0ubuntu0.22.04.1 500 (phased 0%)
500 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted 
amd64 Packages

Out of the whole set of nvidia-driver-535 packages it is the only one of
the kind. Demo script:

#!/usr/bin/env bash

nv_pkgs=(
libnvidia-cfg1-535
libnvidia-common-535
libnvidia-compute-535
libnvidia-decode-535
libnvidia-encode-535
libnvidia-extra-535
libnvidia-fbc1-535
libnvidia-gl-535
nvidia-compute-utils-535
nvidia-dkms-535
nvidia-driver-535
nvidia-kernel-common-535
nvidia-kernel-source-535
nvidia-utils-535
xserver-xorg-video-nvidia-535
)

print_count () {
printf '== %s ==\n' "$1"

for pkg in "${nv_pkgs[@]}"; do
n=$(apt-cache policy "$pkg" | grep -Ec "$2")
printf '%s %s\n' "$n" "$pkg"
done

echo
}

print_count 'Available versions' '^.535'
print_count 'Phasing' 'phased'

Run result:

== Available versions ==
1 libnvidia-cfg1-535
7 libnvidia-common-535
1 libnvidia-compute-535
1 libnvidia-decode-535
1 libnvidia-encode-535
1 libnvidia-extra-535
1 libnvidia-fbc1-535
1 libnvidia-gl-535
1 nvidia-compute-utils-535
1 nvidia-dkms-535
1 nvidia-driver-535
1 nvidia-kernel-common-535
1 nvidia-kernel-source-535
1 nvidia-utils-535
1 xserver-xorg-video-nvidia-535

== Phasing ==
0 libnvidia-cfg1-535
7 libnvidia-common-535
0 libnvidia-compute-535
0 libnvidia-decode-535
0 libnvidia-encode-535
0 libnvidia-extra-535
0 libnvidia-fbc1-535
0 libnvidia-gl-535
0 nvidia-compute-utils-535
0 nvidia-dkms-535
0 nvidia-driver-535
0 nvidia-kernel-common-535
0 nvidia-kernel-source-535
0 nvidia-utils-535
0 xserver-xorg-video-nvidia-535

Demo script to see all phasing packages:

#!/usr/bin/env bash

cat /var/lib/apt/lists/*_Packages |
grep -E '^(Package|Version|Phased)' |
grep -B2 --no-group-separator ^Phased |
while read -r _ pkg; do
IFS=- read -r pkg1 pkg2 <<< "$pkg"

read -r _ vers

[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2023-07-13 Thread Adam Collard

** Changed in: maas
   Status: Incomplete => Invalid

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

Status in MAAS:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Using latest MAAS master, I'm unable to compose a VM over the UI
  successfully when composed with 2048 MB of RAM. By that I mean that
  the VM is created, but it fails with a kernel panic.

  
  So far this only occurred in MAAS environments and often went away with e.g. 
the next daily images. Therefore to reproduce and finally debug/fix this issue 
we'd need data from anyone being affected. This list will grow as we identify 
more that is needed.

  If you are affected, please attach to the bug
  - the kernel used to boot the guest
  - the initrd used to boot the guest
  - libvirt guest XML used to define the guest
  - PXE config provided to the guest
  - the cloud image used to start the guest (That will likely not fit as bug 
attachment, consider storing it somewhere and contact us)

  TODO: The Maas Team will outline how to get all these artifacts.
  TODO: add reference to the comment outlining this (once added)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1797581/+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 2026625] [NEW] package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess

2023-07-08 Thread Adam ODonnell

Public bug reported:

Occurred during installation

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-24-generic 6.2.0-24.24
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Sat Jul  8 12:13:10 2023
ErrorMessage: installed linux-headers-6.2.0-24-generic package 
post-installation script subprocess returned error exit status 1
MachineType: Alienware Alienware Aurora Ryzen Edition
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b6810121-855e-41ef-a565-e89e88e0b75f ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to 
install/upgrade: installed linux-headers-6.2.0-24-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-05-09 (60 days ago)
dmi.bios.date: 01/13/2023
dmi.bios.release: 2.4
dmi.bios.vendor: Alienware
dmi.bios.version: 2.4.0
dmi.board.name: 0NWN7M
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr2.4.0:bd01/13/2023:br2.4:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.4.0:rvnAlienware:rn0NWN7M:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku098E:
dmi.product.family: Alienware
dmi.product.name: Alienware Aurora Ryzen Edition
dmi.product.sku: 098E
dmi.product.version: 2.4.0
dmi.sys.vendor: Alienware

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


** Tags: amd64 apport-package lunar need-duplicate-check

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

Title:
  package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to
  install/upgrade: installed linux-headers-6.2.0-24-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Occurred during installation

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-24-generic 6.2.0-24.24
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Jul  8 12:13:10 2023
  ErrorMessage: installed linux-headers-6.2.0-24-generic package 
post-installation script subprocess returned error exit status 1
  MachineType: Alienware Alienware Aurora Ryzen Edition
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=b6810121-855e-41ef-a565-e89e88e0b75f ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to 
install/upgrade: installed linux-headers-6.2.0-24-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-05-09 (60 days ago)
  dmi.bios.date: 01/13/2023
  dmi.bios.release: 2.4
  dmi.bios.vendor: Alienware
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NWN7M
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr2.4.0:bd01/13/2023:br2.4:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.4.0:rvnAlienware:rn0NWN7M:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku098E:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora Ryzen Edition
  dmi.product.sku: 098E
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026625/+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 2024943] Re: 5.19.0-45-generic stalls on boot

2023-06-23 Thread Adam Jones

** Attachment added: "Logs when disabling editing GRUB config to disable quiet
splash from boot config"

https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2024943/+attachment/5681706/+files/logs.jpg

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

Title:
5.19.0-45-generic stalls on boot

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

Bug description:
Version: Ubuntu 22.04.2 LTS

After installing the `5.19.0-45-generic kernel`, my system no longer
boots properly. Going via GRUB and starting either `5.19.0-45-generic
kernel (recovery)` (and then choosing 'resume') or `5.19.0-43-generic
kernel` works correctly. I didn't intentionally update this part of my
system, I think it was just part of a regular `sudo apt update` and
`sudo apt upgrade`.

I can't seem to find the logs for any of the failed boots in
journalctl. Happy to take advice on what logs need to be provided (but
please be detailed on how I can retrieve them e.g. by providing links
to documentation I should follow).

Expected behaviour:
- The system shows the BIOS splash screen, then goes black for a second, then
shows the motherboard brand logo (but without any bios keys etc.) for a second,
then shows the encryption dialog. After entering encryption password, the
system boots into the desktop.

Actual behaviour:
- Normal boot: The system shows the BIOS splash screen, then goes black for a
second, then shows the motherboard brand logo (but without any bios keys etc.).
It then seems to just be stuck here (waited 15 minutes and no change).
- Grub boot: The system shows the BIOS splash screen, then goes black for a
second, then opens GRUB. Based on selection here:
- Ubuntu: the system shows the motherbroad brand logo and gets stuck.
- Advanced > 5.19.0-45-generic kernel: the system shows the motherbroad
brand logo and gets stuck.
- Advanced > 5.19.0-45-generic kernel (recovery): the system boots into
recovery just fine, and prompts me for the encryption password along the way.
Using 'resume' here loads the desktop and things appear to work as normal.
- Advanced > 5.19.0-43-generic kernel: the system shows shows the
motherboard brand logo (but without any bios keys etc.) for a second, then
shows the encryption dialog. After entering encryption password, the password
field gets stuck.
- Advanced > 5.19.0-43-generic kernel (recovery): same as 5.19.0-45-generic
kernel (recovery)

Other troubleshooting context:
- I have full-disk encryption enabled
- The system appeared to be working fine before these updates
- I have an Intel CPU and Nvidia GPU

It appears others might be experiencing this bug, with some discussion
on AskUbuntu https://askubuntu.com/questions/1473252/someone-else-
experienced-boot-failures-with-the-5-19-0-45-generic-kernel-version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2024943/+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 2024943] Re: 5.19.0-45-generic stalls on boot

2023-06-23 Thread Adam Jones

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

Title:
5.19.0-45-generic stalls on boot

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

Bug description:
Version: Ubuntu 22.04.2 LTS

Other troubleshooting context:
- I have full-disk encryption enabled
- The system appeared to be working fine before these updates
- I have an Intel CPU and Nvidia GPU

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

[Kernel-packages] [Bug 2024943] Re: 5.19.0-45-generic stalls on boot

2023-06-23 Thread Adam Jones

Following the instructions on debugging kernel boot problems (
https://wiki.ubuntu.com/DebuggingKernelBoot ), I think I've found a
workaround and perhaps a clue as to where the problem lies.

Workaround:
Disable Intel graphics in your BIOS. For me, this was in Peripherals > Intel
Processor Graphics > Set to 'Disabled'

Key log:
i915 :00:02.0: enabling device (0006 -> 0007)

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

Title:
5.19.0-45-generic stalls on boot

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

Bug description:
Version: Ubuntu 22.04.2 LTS

Other troubleshooting context:
- I have full-disk encryption enabled
- The system appeared to be working fine before these updates
- I have an Intel CPU and Nvidia GPU

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

[Kernel-packages] [Bug 2024943] [NEW] 5.19.0-45-generic stalls on boot

2023-06-23 Thread Adam Jones

Public bug reported:

Version: Ubuntu 22.04.2 LTS

After installing the `5.19.0-45-generic kernel`, my system no longer
boots properly. Going via GRUB and starting either `5.19.0-45-generic
kernel (recovery)` (and then choosing 'resume') or `5.19.0-43-generic
kernel` works correctly. I didn't intentionally update this part of my
system, I think it was just part of a regular `sudo apt update` and
`sudo apt upgrade`.

I can't seem to find the logs for any of the failed boots in journalctl.
Happy to take advice on what logs need to be provided (but please be
detailed on how I can retrieve them e.g. by providing links to
documentation I should follow).

Expected behaviour:
- The system shows the BIOS splash screen, then goes black for a second, then 
shows the motherboard brand logo (but without any bios keys etc.) for a second, 
then shows the encryption dialog. After entering encryption password, the 
system boots into the desktop.

Actual behaviour:
- Normal boot: The system shows the BIOS splash screen, then goes black for a 
second, then shows the motherboard brand logo (but without any bios keys etc.). 
It then seems to just be stuck here (waited 15 minutes and no change).
- Grub boot: The system shows the BIOS splash screen, then goes black for a 
second, then opens GRUB. Based on selection here:
  - Ubuntu: the system shows the motherbroad brand logo and gets stuck.
  - Advanced > 5.19.0-45-generic kernel: the system shows the motherbroad brand 
logo and gets stuck.
  - Advanced > 5.19.0-45-generic kernel (recovery): the system boots into 
recovery just fine, and prompts me for the encryption password along the way. 
Using 'resume' here loads the desktop and things appear to work as normal.
  - Advanced > 5.19.0-43-generic kernel: the system shows shows the motherboard 
brand logo (but without any bios keys etc.) for a second, then shows the 
encryption dialog. After entering encryption password, the password field gets 
stuck.
  - Advanced > 5.19.0-43-generic kernel (recovery): same as 5.19.0-45-generic 
kernel (recovery)

Other troubleshooting context:
- I have full-disk encryption enabled
- The system appeared to be working fine before these updates
- I have an Intel CPU and Nvidia GPU

It appears others might be experiencing this bug, with some discussion
on AskUbuntu https://askubuntu.com/questions/1473252/someone-else-
experienced-boot-failures-with-the-5-19-0-45-generic-kernel-version

** Affects: linux-signed-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-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2024943

Title:
  5.19.0-45-generic stalls on boot

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

Bug description:
  Version: Ubuntu 22.04.2 LTS

  After installing the `5.19.0-45-generic kernel`, my system no longer
  boots properly. Going via GRUB and starting either `5.19.0-45-generic
  kernel (recovery)` (and then choosing 'resume') or `5.19.0-43-generic
  kernel` works correctly. I didn't intentionally update this part of my
  system, I think it was just part of a regular `sudo apt update` and
  `sudo apt upgrade`.

  I can't seem to find the logs for any of the failed boots in
  journalctl. Happy to take advice on what logs need to be provided (but
  please be detailed on how I can retrieve them e.g. by providing links
  to documentation I should follow).

  Expected behaviour:
  - The system shows the BIOS splash screen, then goes black for a second, then 
shows the motherboard brand logo (but without any bios keys etc.) for a second, 
then shows the encryption dialog. After entering encryption password, the 
system boots into the desktop.

  Actual behaviour:
  - Normal boot: The system shows the BIOS splash screen, then goes black for a 
second, then shows the motherboard brand logo (but without any bios keys etc.). 
It then seems to just be stuck here (waited 15 minutes and no change).
  - Grub boot: The system shows the BIOS splash screen, then goes black for a 
second, then opens GRUB. Based on selection here:
- Ubuntu: the system shows the motherbroad brand logo and gets stuck.
- Advanced > 5.19.0-45-generic kernel: the system shows the motherbroad 
brand logo and gets stuck.
- Advanced > 5.19.0-45-generic kernel (recovery): the system boots into 
recovery just fine, and prompts me for the encryption password along the way. 
Using 'resume' here loads the desktop and things appear to work as normal.
- Advanced > 5.19.0-43-generic kernel: the system shows shows the 
motherboard brand logo (but without any bios keys etc.) for a second, then 
shows the encryption dialog. After entering encryption password, the password 
field gets stuck.
- Advanced > 5.19.0-43-generic kernel (recovery): same as 5.19.0-45-generic 
kernel (recovery)

  Other troubleshooting context:
  - I have full-disk encryption enabled
  - The sys

[Kernel-packages] [Bug 2022901] Re: dmcrypt+btrfs Out of bounds

2023-06-13 Thread adam furtenbach

System has been running stable for the entire time when not using dmcrypt on 
that disk.
dmcrypt+btrfs has been working perfectly on OS disk since the beginning.

> lsblk
nvme0n1   259:00  2000398934016  0 disk  
├─nvme0n1p1   259:10  805306368  0 part  
│ └─LUKS_BOOT 253:10  803209216  0 crypt /boot
├─nvme0n1p2   259:20  134217728  0 part  /boot/efi
├─nvme0n1p3   259:30  1099511627776  0 part  
│ └─ROOT  253:00  1099494850560  0 crypt /home
│/
...


# CPU model
> cat /proc/cpuinfo  | grep "model name" | head -n 1
model name  : AMD Ryzen 9 7950X3D 16-Core Processor

# System running at stock speed
> dmidecode --type 17 | grep Speed: | head -n 1
Speed: 4800 MT/s

# no issues with scrubbing
> btrfs scrub status /mnt/grid/
UUID: b1dc5510-5ecc-4bdb-b464-0ac09ffad89f
Scrub started:Sat Jun 10 11:13:39 2023
Status:   finished
Duration: 9:03:05
Total to scrub:   6.74TiB
Rate: 209.78MiB/s
Error summary:no errors found

# smart table looks good
> smartctl -A /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.0-20-generic] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000b   100   100   001Pre-fail  Always   
-   0
  2 Throughput_Performance  0x0005   149   149   054Pre-fail  Offline  
-   44
  3 Spin_Up_Time0x0007   084   084   001Pre-fail  Always   
-   337 (Average 310)
  4 Start_Stop_Count0x0012   100   100   000Old_age   Always   
-   21
  5 Reallocated_Sector_Ct   0x0033   100   100   001Pre-fail  Always   
-   0
  7 Seek_Error_Rate 0x000b   100   100   001Pre-fail  Always   
-   0
  8 Seek_Time_Performance   0x0005   140   140   020Pre-fail  Offline  
-   15
  9 Power_On_Hours  0x0012   100   100   000Old_age   Always   
-   267
 10 Spin_Retry_Count0x0013   100   100   001Pre-fail  Always   
-   0
 12 Power_Cycle_Count   0x0032   100   100   000Old_age   Always   
-   15
 22 Helium_Level0x0023   100   100   025Pre-fail  Always   
-   100
192 Power-Off_Retract_Count 0x0032   100   100   000Old_age   Always   
-   33
193 Load_Cycle_Count0x0012   100   100   000Old_age   Always   
-   33
194 Temperature_Celsius 0x0002   059   059   000Old_age   Always   
-   35 (Min/Max 22/37)
196 Reallocated_Event_Count 0x0032   100   100   000Old_age   Always   
-   0
197 Current_Pending_Sector  0x0022   100   100   000Old_age   Always   
-   0
198 Offline_Uncorrectable   0x0008   100   100   000Old_age   Offline  
-   0
199 UDMA_CRC_Error_Count0x000a   100   100   000Old_age   Always   
-   0

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

Title:
  dmcrypt+btrfs Out of bounds

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Getting this IO error when using btrfs + dmcrypt (5 times so far,
  reformat between each try) on a DDR5 system w/ built in ECC.

  
  [82228.951950] Buffer I/O error on dev sda1, logical block 35156653829, async 
page read

  35156653829*512=18000206760448

  This value 18000206760448 is between /dev/sda1 partition size and
  /dev/mapper/ARCHIVE(btrfs volume) size, but is still slightly out of
  bounds of btrfs partition geometry, causing an out of bounds error.


  # lsblk -b

  sda 8:00 18000207937536  0 disk  
  └─sda1  8:10 18000206872064  0 part  
└─ARCHIVE   253:10 18000190094848  0 crypt /mnt/archive

  # btrfs filesystem show --raw
   devid1 size 18000190091264 used 416628604928 path 
/dev/mapper/ARCHIVE



  Linux oblivion 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr
  6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 23.04
  Release:23.04
  Codename:   lunar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2022901/+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 2022901] [NEW] dmcrypt+btrfs Out of bounds

2023-06-05 Thread adam furtenbach

Public bug reported:

Getting this IO error when using btrfs + dmcrypt (5 times so far,
reformat between each try) on a DDR5 system w/ built in ECC.


[82228.951950] Buffer I/O error on dev sda1, logical block 35156653829, async 
page read

35156653829*512=18000206760448

This value 18000206760448 is between /dev/sda1 partition size and
/dev/mapper/ARCHIVE(btrfs volume) size, but is still slightly out of
bounds of btrfs partition geometry, causing an out of bounds error.


# lsblk -b

sda 8:00 18000207937536  0 disk  
└─sda1  8:10 18000206872064  0 part  
  └─ARCHIVE   253:10 18000190094848  0 crypt /mnt/archive

# btrfs filesystem show --raw
 devid1 size 18000190091264 used 416628604928 path 
/dev/mapper/ARCHIVE


Linux oblivion 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr
6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.04
Release:23.04
Codename:   lunar

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


** Tags: btrfs dmcrypt kernel-bug

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

Title:
  dmcrypt+btrfs Out of bounds

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Getting this IO error when using btrfs + dmcrypt (5 times so far,
  reformat between each try) on a DDR5 system w/ built in ECC.

  
  [82228.951950] Buffer I/O error on dev sda1, logical block 35156653829, async 
page read

  35156653829*512=18000206760448

  This value 18000206760448 is between /dev/sda1 partition size and
  /dev/mapper/ARCHIVE(btrfs volume) size, but is still slightly out of
  bounds of btrfs partition geometry, causing an out of bounds error.


  # lsblk -b

  sda 8:00 18000207937536  0 disk  
  └─sda1  8:10 18000206872064  0 part  
└─ARCHIVE   253:10 18000190094848  0 crypt /mnt/archive

  # btrfs filesystem show --raw
   devid1 size 18000190091264 used 416628604928 path 
/dev/mapper/ARCHIVE



  Linux oblivion 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr
  6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 23.04
  Release:23.04
  Codename:   lunar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2022901/+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 2022053] [NEW] docker container cannot reach host with firewall enabled after kernel upgrade

2023-06-01 Thread Adam Juraszek

Public bug reported:

$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04

I have the following kernels installed:

$ apt list --installed | grep linux-image

linux-image-5.19.0-41-generic/jammy-updates,jammy-security,now 
5.19.0-41.42~22.04.1 amd64 [installed,auto-removable]
linux-image-5.19.0-42-generic/jammy-updates,jammy-security,now 
5.19.0-42.43~22.04.1 amd64 [installed,automatic]
linux-image-5.19.0-43-generic/jammy-updates,jammy-security,now 
5.19.0-43.44~22.04.1 amd64 [installed,automatic]
linux-image-generic-hwe-22.04/jammy-updates,jammy-security,now 
5.19.0.43.44~22.04.17 amd64 [installed,automatic]

The following setup worked with 41 (and still works when I just boot
using that kernel) but broke with 42 (and does not work in 43 either).

I have docker installed (tried both version 23 and recently released
24).

I have ufw installed with the following extra setup:

$ sudo cat /etc/ufw/after.rules 
#
# rules.input-after
#
# Rules that should be run after the ufw command line added rules. Custom
# rules should be added to one of these chains:
#   ufw-after-input
#   ufw-after-output
#   ufw-after-forward
#

# Don't delete these required lines, otherwise there will be errors
*filter
:ufw-after-input - [0:0]
:ufw-after-output - [0:0]
:ufw-after-forward - [0:0]
# End required lines


# Allow containers to access host
-A ufw-after-input -p tcp -m physdev --physdev-in veth+ -j ACCEPT -m comment 
--comment 'Allow_docker_tcp'
-A ufw-after-input -p udp -m physdev --physdev-in veth+ -j ACCEPT -m comment 
--comment 'Allow_docker_udp'
-A ufw-after-input -p icmp -m physdev --physdev-in veth+ -j ACCEPT -m comment 
--comment 'Allow_docker_icmp'


# don't log noisy services by default
-A ufw-after-input -p udp --dport 137 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp --dport 138 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp --dport 139 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp --dport 445 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp --dport 67 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp --dport 68 -j ufw-skip-to-policy-input

# don't log noisy broadcast
-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input

# don't delete the 'COMMIT' line or these rules won't be processed
COMMIT

Note those three rules for docker; these work in 41 but stop working
afterwards.

How to reproduce:

$ docker run --rm curlimages/curl http://172.17.0.1

  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:--  0:02:10 --:--:-- 0
curl: (28) Failed to connect to 172.17.0.1 port 80 after 130429 ms: Couldn't 
connect to server

It times out after a long time. dmesg contains the following message:

[  872.069093] [UFW BLOCK] IN=docker0 OUT=
MAC=02:42:55:c9:a5:6e:02:42:ac:11:00:03:08:00 SRC=172.17.0.3
DST=172.17.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=27268 DF PROTO=TCP
SPT=56862 DPT=80 WINDOW=64240 RES=0x00 SYN URGP=0

To explain docker networking:

$ ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state DOWN 
group default qlen 1000
link/ether 34:48:ed:08:e1:f5 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
3: gpd0:  mtu 1500 qdisc noop state DOWN group 
default qlen 500
link/none 
4: wlp59s0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 24:41:8c:c3:1d:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.138/24 brd 192.168.0.255 scope global dynamic noprefixroute 
wlp59s0
   valid_lft 2519sec preferred_lft 2519sec
inet6 fe80::cb8e:fe0e:6131:d3fc/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
6: docker0:  mtu 1500 qdisc noqueue state UP 
group default 
link/ether 02:42:55:c9:a5:6e brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
   valid_lft forever preferred_lft forever
inet6 fe80::42:55ff:fec9:a56e/64 scope link 
   valid_lft forever preferred_lft forever
8: veth17e77be@if7:  mtu 1500 qdisc noqueue 
master docker0 state UP group default 
link/ether 72:cd:15:f8:84:2d brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::70cd:15ff:fef8:842d/64 scope link 
   valid_lft forever preferred_lft forever


$ brctl show
bridge name bridge id   STP enabled interfaces
docker0 8000.024255c9a56e   no  veth17e77be

$ docker network inspect bridge 
[
{
"Name": "bridge",
"Id": 
"f17a627c3397d0aaf496b7cac59a23a902fe66e14f2e820cd097f313680ccb88",
"Created": "2023-06-01T12:33:14.87479534+02:00",
"Scope": "local",
"Driver": "b

Re: [Kernel-packages] [Bug 2018181] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subproce

2023-05-01 Thread Adam Titmus

adam@adam-ThinkPad-P73:~$ dpkg -l 
evdi-dkmsdpkg-query: no packages found matching 
evdi-dkmsadam@adam-ThinkPad-P73:~$ apt-cache policy evdi-dkmsevdi-dkms:  
Installed: (none)  Candidate: 1.12.0+dfsg-0.3ubuntu2  Version table:     
1.12.0+dfsg-0.3ubuntu2 500        500 http://archive.ubuntu.com/ubuntu 
lunar/universe amd64 Packages        500 http://archive.ubuntu.com/ubuntu 
lunar/universe i386 
Packagesadam@adam-ThinkPad-P73:~$
I assume this is nothing to do with running Lubuntu, which I hope has no impact 
on the kernel.
However, note also that I'm running 3 screens (for the last 5-ish releases of 
Ubuntu) - the extra screens are an HP via DisplayPort (I think) and a USB ASUS.
So evdi might have made sense at some point.


Adam Titmus atit...@yahoo.co.uk

On Monday, 1 May 2023 at 11:20:21 BST, Juerg Haefliger 
<2018...@bugs.launchpad.net> wrote:  
 
 1.12.0 is a weird evdi package version. This doesn't look like an Ubuntu DKMS. 
What is the output of:
 $ dpkg -l evdi-dkms
 $ apt-cache policy evdi-dkms


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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/2018181

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  23.04 upgrade failure

  
  Errors were encountered while processing:
  linux-headers-6.2.0-20-generic
  linux-headers-generic
  linux-generic
  linux-image-6.2.0-20-generic
  Log ended: 2023-04-29  23:08:16

  6.2.0 hans

  using 5.19

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Apr 29 23:00:58 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-03-03 (422 days ago)
  InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20QR0026UK
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=6dc0fe26-e31b-440e-bc8e-aeb79fa116f1 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-29 (0 days ago)
  dmi.bios.date: 01/08/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QR0026UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:br1.20:efr1.9:svnLENOVO:pn20QR0026UK:pvrThinkPadP73:rvnLENOVO:rn20QR0026UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QR_BU_Think_FM_ThinkPadP73:
  dmi.product.family: ThinkPad P73
  dmi.product.name: 20QR0026UK
  dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
  dmi.product.version: ThinkPad P73
  dmi.sys.vendor: LENOVO

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

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  23.04 upgrade failure

  
  Errors were encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  Log ended: 2023-04-29  23:08:16

  6.2.0 hans

  using 5.19

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20

[Kernel-packages] [Bug 2018181] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess

2023-04-30 Thread Adam Titmus

Public bug reported:

23.04 upgrade failure


Errors were encountered while processing:
 linux-headers-6.2.0-20-generic
 linux-headers-generic
 linux-generic
 linux-image-6.2.0-20-generic
Log ended: 2023-04-29  23:08:16

6.2.0 hans

using 5.19

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Sat Apr 29 23:00:58 2023
ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-03-03 (422 days ago)
InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20QR0026UK
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=6dc0fe26-e31b-440e-bc8e-aeb79fa116f1 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.06-2ubuntu16
SourcePackage: linux
Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to lunar on 2023-04-29 (0 days ago)
dmi.bios.date: 01/08/2020
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET35W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QR0026UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:br1.20:efr1.9:svnLENOVO:pn20QR0026UK:pvrThinkPadP73:rvnLENOVO:rn20QR0026UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QR_BU_Think_FM_ThinkPadP73:
dmi.product.family: ThinkPad P73
dmi.product.name: 20QR0026UK
dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73
dmi.product.version: ThinkPad P73
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package lunar

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

Title:
  package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to
  install/upgrade: installed linux-headers-6.2.0-20-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  23.04 upgrade failure

  
  Errors were encountered while processing:
   linux-headers-6.2.0-20-generic
   linux-headers-generic
   linux-generic
   linux-image-6.2.0-20-generic
  Log ended: 2023-04-29  23:08:16

  6.2.0 hans

  using 5.19

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: linux-headers-6.2.0-20-generic 6.2.0-20.20
  ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Apr 29 23:00:58 2023
  ErrorMessage: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2022-03-03 (422 days ago)
  InstallationMedia: Lubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20QR0026UK
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic 
root=UUID=6dc0fe26-e31b-440e-bc8e-aeb79fa116f1 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu16
  SourcePackage: linux
  Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to 
install/upgrade: installed linux-headers-6.2.0-20-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-04-29 (0 days ago)
  dmi.bios.date: 01/08/2020
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2NET35W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QR0026UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENO

[Kernel-packages] [Bug 2015588] [NEW] package linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed linux-modules-nvidia-525-5.19.0-38-generic package

2023-04-07 Thread Adam Ehrlich

Public bug reported:

dont know what this is about

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Apr  7 07:46:03 2023
DuplicateSignature:
 package:linux-modules-nvidia-525-5.19.0-38-generic:5.19.0-38.39~22.04.1+1
 Setting up linux-modules-nvidia-525-5.19.0-38-generic (5.19.0-38.39~22.04.1+1) 
...
 /var/lib/dpkg/info/linux-modules-nvidia-525-5.19.0-38-generic.config: 6: 
/etc/default/linux-modules-nvidia: 
linux-modules-nvidia-525-open-generic-hwe-22.04: not found
 dpkg: error processing package linux-modules-nvidia-525-5.19.0-38-generic 
(--configure):
  installed linux-modules-nvidia-525-5.19.0-38-generic package 
post-installation script subprocess returned error exit status 127
ErrorMessage: installed linux-modules-nvidia-525-5.19.0-38-generic package 
post-installation script subprocess returned error exit status 127
InstallationDate: Installed on 2023-04-03 (3 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: linux-restricted-modules-hwe-5.19
Title: package linux-modules-nvidia-525-5.19.0-38-generic 
5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed 
linux-modules-nvidia-525-5.19.0-38-generic package post-installation script 
subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-modules-nvidia-525-5.19.0-38-generic
  5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed linux-
  modules-nvidia-525-5.19.0-38-generic package post-installation script
  subprocess returned error exit status 127

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

Bug description:
  dont know what this is about

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-nvidia-525-5.19.0-38-generic 5.19.0-38.39~22.04.1+1
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr  7 07:46:03 2023
  DuplicateSignature:
   package:linux-modules-nvidia-525-5.19.0-38-generic:5.19.0-38.39~22.04.1+1
   Setting up linux-modules-nvidia-525-5.19.0-38-generic 
(5.19.0-38.39~22.04.1+1) ...
   /var/lib/dpkg/info/linux-modules-nvidia-525-5.19.0-38-generic.config: 6: 
/etc/default/linux-modules-nvidia: 
linux-modules-nvidia-525-open-generic-hwe-22.04: not found
   dpkg: error processing package linux-modules-nvidia-525-5.19.0-38-generic 
(--configure):
installed linux-modules-nvidia-525-5.19.0-38-generic package 
post-installation script subprocess returned error exit status 127
  ErrorMessage: installed linux-modules-nvidia-525-5.19.0-38-generic package 
post-installation script subprocess returned error exit status 127
  InstallationDate: Installed on 2023-04-03 (3 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-restricted-modules-hwe-5.19
  Title: package linux-modules-nvidia-525-5.19.0-38-generic 
5.19.0-38.39~22.04.1+1 failed to install/upgrade: installed 
linux-modules-nvidia-525-5.19.0-38-generic package post-installation script 
subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.19/+bug/2015588/+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 2012561] [NEW] package linux-base 4.5ubuntu9 failed to install/upgrade: installed linux-base package post-installation script subprocess returned error exit status 1

2023-03-22 Thread Adam Frick

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-base 4.5ubuntu9
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Mar 22 16:20:41 2023
DuplicateSignature:
 package:linux-base:4.5ubuntu9
 Setting up linux-base (4.5ubuntu9) ...
 debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another 
process: Resource temporarily unavailable
 dpkg: error processing package linux-base (--configure):
  installed linux-base package post-installation script subprocess returned 
error exit status 1
ErrorMessage: installed linux-base package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2021-11-10 (497 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.8.2-4
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: linux-base
Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed 
linux-base package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2023-03-22 (0 days ago)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-base 4.5ubuntu9 failed to install/upgrade: installed
  linux-base package post-installation script subprocess returned error
  exit status 1

Status in linux-base package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-base 4.5ubuntu9
  ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
  Uname: Linux 5.15.0-67-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Mar 22 16:20:41 2023
  DuplicateSignature:
   package:linux-base:4.5ubuntu9
   Setting up linux-base (4.5ubuntu9) ...
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
   dpkg: error processing package linux-base (--configure):
installed linux-base package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed linux-base package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-11-10 (497 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: linux-base
  Title: package linux-base 4.5ubuntu9 failed to install/upgrade: installed 
linux-base package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to jammy on 2023-03-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/2012561/+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 2002748] Re: Unable to handle page fault under heavy M.2 load

2023-01-18 Thread Adam Petrycki

A backup (rsync) ran again and crashed:

[16096.851781] usb 2-1: reset SuperSpeed USB device number 3 using xhci_hcd
[16096.875912] usb 2-1: LPM exit latency is zeroed, disabling LPM.
[20421.689261] perf: interrupt took too long (6260 > 6216), lowering 
kernel.perf_event_max_sample_rate to 31750
[145901.879732] BUG: unable to handle page fault for address: d824fa40
[145901.879789] #PF: supervisor read access in kernel mode
[145901.879820] #PF: error_code(0x) - not-present page
[145901.879849] PGD 721a15067 P4D 721a15067 PUD 721a17067 PMD 0
[145901.879885] Oops:  [#1] SMP PTI
[145901.879907] CPU: 2 PID: 846408 Comm: rsync Tainted: G   OE 
5.15.0-57-generic #63-Ubuntu
[145901.879957] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 1.23 
04/08/2021
[145901.879996] RIP: 0010:do_dentry_open+0xc8/0x390
[145901.880029] Code: 00 20 0f 85 07 02 00 00 66 2d 00 40 66 a9 00 b0 75 07 81 
4b 44 00 80 00 00 49 8b 84 24 68 01 00 00 48 85 c0 0f 84 54 01 00 00 <48> 8b 38 
e8 30 a3 e0 ff 84 c0 0f 84 44 01 00 00 49 8b 84 24 68 01
[145901.880124] RSP: 0018:a67d8301fc50 EFLAGS: 00010282
[145901.880154] RAX: d824fa40 RBX: 96e32f006100 RCX: 
0002
[145901.880192] RDX: 41ed RSI: 0002 RDI: 
96e318380c8c
[145901.880230] RBP: a67d8301fc80 R08: 96e318623060 R09: 
96e208cd6600
[145901.880268] R10: 0001 R11: 32336372 R12: 
96e2020a0ee0
[145901.880306] R13:  R14: 96e32f006110 R15: 
96e32f006100
[145901.880344] FS:  7f0f8e4ef740() GS:96ea5fd0() 
knlGS:
[145901.880388] CS:  0010 DS:  ES:  CR0: 80050033
[145901.880420] CR2: d824fa40 CR3: 00012f55 CR4: 
00350ee0
[145901.880458] Call Trace:
[145901.880474]  
[145901.880490]  vfs_open+0x2d/0x40
[145901.880513]  do_open+0x20d/0x470
[145901.880535]  path_openat+0x112/0x2b0
[145901.880557]  ? evm_inode_setattr+0x2d/0xf0
[145901.880584]  do_filp_open+0xb2/0x160
[145901.880607]  ? __check_object_size+0x1d/0x30
[145901.880634]  do_sys_openat2+0x9f/0x160
[145901.880659]  __x64_sys_openat+0x55/0x90
[145901.880683]  do_syscall_64+0x59/0xc0
[145901.880706]  ? do_syscall_64+0x69/0xc0
[145901.880729]  ? exit_to_user_mode_prepare+0x37/0xb0
[145901.880758]  ? syscall_exit_to_user_mode+0x27/0x50
[145901.880786]  ? __x64_sys_newfstatat+0x1c/0x30
[145901.880813]  ? do_syscall_64+0x69/0xc0
[145901.880835]  ? do_syscall_64+0x69/0xc0
[145901.880857]  ? do_syscall_64+0x69/0xc0
[145901.880879]  entry_SYSCALL_64_after_hwframe+0x61/0xcb
[145901.880910] RIP: 0033:0x7f0f8e60bbcc
[145901.880932] Code: 24 18 31 c0 41 83 e2 40 75 44 89 f0 25 00 00 41 00 3d 00 
00 41 00 74 36 44 89 c2 4c 89 ce bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 44 48 8b 54 24 18 64 48 2b 14 25 28 00 00 00
[145901.881025] RSP: 002b:7fff5c804d30 EFLAGS: 0287 ORIG_RAX: 
0101
[145901.881066] RAX: ffda RBX:  RCX: 
7f0f8e60bbcc
[145901.881103] RDX: 00090800 RSI: 7fff5c806ff0 RDI: 
ff9c
[145901.881141] RBP: 7fff5c806ff0 R08: 00090800 R09: 
7fff5c806ff0
[145901.881179] R10:  R11: 0287 R12: 
55ac421173f0
[145901.881216] R13: 7fff5c806ff0 R14: 0001 R15: 
55ac421173f0
[145901.881255]  
[145901.881269] Modules linked in: tcp_diag udp_diag inet_diag cpuid xt_nat 
xt_tcpudp veth xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge stp llc rdma_ucm ib_uverbs rdma_cm iw_cm ib_cm ib_core nvme_fabrics 
overlay bonding tls binfmt_misc intel_rapl_msr intel_rapl_common intel_pmc_bxt 
intel_telemetry_pltdrv intel_punit_ipc intel_telemetry_core mei_hdcp 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel nls_iso8859_1 kvm rapl 
intel_cstate input_leds joydev ee1004 mei_me r8125(OE) mei mac_hid sch_fq_codel 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr ramoops pstore_blk 
pstore_zone reed_solomon efi_pstore nfsd auth_rpcgss nfs_acl lockd grace sunrpc 
ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_
 pq
[145901.881363]  libcrc32c raid0 multipath linear i915 i2c_algo_bit ttm 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec raid1 xhci_pci 
crct10dif_pclmul rc_core sdhci_pci nvme i2c_i801 cqhci crc32_pclmul 
ghash_clmulni_intel aesni_intel i2c_smbus crypto_simd sdhci nvme_core drm 
cryptd xhci_pci_renesas intel_lpss_pci intel_lpss ahci idma64 libahci video 
pinctrl_geminilake
[145901.881978] CR2: d824fa40
[145901.882000] ---[ end trace 69c48397b099b00e ]---
[145902.109279] RIP: 0010:do_dentry_open+0xc8/0x390
[145902.109325] Code: 00 20 0f 85 07 02 00 00 66 2d 00 40 66 a9 00 b0 75 07

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or week

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup that

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup that has high

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
bac

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something lik

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup th

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup that has

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup th

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup that has h

[Kernel-packages] [Bug 2002748] Re: Unable to handle page fault under heavy M.2 load

2023-01-13 Thread Adam Petrycki

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  Under heavy disk usage, such as backing up the disk to another drive, I
  get the error:
  
  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---
  
  The process and exact message changes, but it's ext4 related.
  
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup that has high utilization for an extended period of time.
  
  I would expect the computer to run smoothly.
  
  Instead, it throws the message and crawls to a hault as disk access stops 
working.
  r8125 driver is the only non-distro module
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jan 12 1

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

2023-01-13 Thread Adam Petrycki

apport information

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

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup that has high u

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

2023-01-13 Thread Adam Petrycki

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2002748/+attachment/5641189/+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/2002748

Title:
  Unable to handle page fault under heavy M.2 load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under heavy disk usage, such as backing up the disk to another drive,
  I get the error:

  [137133.774493] BUG: unable to handle page fault for address: 4164
  [137133.774507] #PF: supervisor read access in kernel mode
  [137133.774512] #PF: error_code(0x) - not-present page
  [137133.774515] PGD 0 P4D 0
  [137133.774520] Oops:  [#1] SMP PTI
  [137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
  [137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
  [137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
  [137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 
08 8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 
64 83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
  [137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
  [137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
  [137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
  [137133.774564] RBP: b16640487a10 R08: 0002 R09: 

  [137133.774567] R10: 0001 R11:  R12: 
95409700
  [137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
  [137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
  [137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
  [137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
  [137133.774587] Call Trace:
  [137133.774591]  
  [137133.774596]  __dquot_drop+0x91/0xc0
  [137133.774602]  dquot_drop+0x53/0x60
  [137133.774606]  ext4_clear_inode+0x44/0xb0
  [137133.774613]  ext4_evict_inode+0x86/0x670
  [137133.774618]  evict+0xcf/0x190
  [137133.774624]  prune_icache_sb+0x81/0xc0
  [137133.774629]  super_cache_scan+0x169/0x200
  [137133.774635]  do_shrink_slab+0x155/0x2c0
  [137133.774641]  shrink_slab_memcg+0xcf/0x1e0
  [137133.774646]  shrink_slab+0x10a/0x120
  [137133.774651]  ? shrink_slab+0x10a/0x120
  [137133.774655]  shrink_node_memcgs+0x188/0x1d0
  [137133.774660]  shrink_node+0x15d/0x5c0
  [137133.774666]  balance_pgdat+0x36e/0x800
  [137133.774670]  ? try_to_del_timer_sync+0x22/0x90
  [137133.774677]  kswapd+0x10c/0x1c0
  [137133.774682]  ? balance_pgdat+0x800/0x800
  [137133.774686]  kthread+0x127/0x150
  [137133.774691]  ? set_kthread_struct+0x50/0x50
  [137133.774696]  ret_from_fork+0x1f/0x30
  [137133.774703]  
  [137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat 
xt_tcpudp veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 i2c_algo_b
 it ttm
  [137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
  [137133.774849] CR2: 4164
  [137133.774854] ---[ end trace 85a590ce733b1c95 ]---

  The process and exact message changes, but it's ext4 related.

  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  (GNU/Linux 5.15.0-57-generic x86_64)
  ODROID-H2+
  Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
  Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
  Google Coral
  smartctl shows no errors
  It can be days or weeks before I see the issue unless I do something like a 
backup

[Kernel-packages] [Bug 2002748] [NEW] Unable to handle page fault under heavy M.2 load

2023-01-12 Thread Adam Petrycki

Public bug reported:

Under heavy disk usage, such as backing up the disk to another drive, I
get the error:

[137133.774493] BUG: unable to handle page fault for address: 4164
[137133.774507] #PF: supervisor read access in kernel mode
[137133.774512] #PF: error_code(0x) - not-present page
[137133.774515] PGD 0 P4D 0
[137133.774520] Oops:  [#1] SMP PTI
[137133.774525] CPU: 1 PID: 104 Comm: kswapd0 Tainted: G   OE 
5.15.0-46-generic #49-Ubuntu
[137133.774531] Hardware name: HARDKERNEL ODROID-H2/ODROID-H2, BIOS 5.13 
04/27/2020
[137133.774535] RIP: 0010:dqput.part.0+0x47/0x1f0
[137133.774545] Code: 53 48 89 fb 48 c7 c7 68 e4 dd 95 4c 8d 6b 30 48 83 ec 08 
8b 15 1a b1 e0 01 e8 65 b8 23 00 48 c7 c7 00 97 40 95 e8 69 45 97 00 <8b> 43 64 
83 f8 01 0f 8f 90 00 00 00 48 8b 83 80 00 00 00 a8 01 75
[137133.774551] RSP: 0018:b166404879e0 EFLAGS: 00010246
[137133.774556] RAX:  RBX: 4100 RCX: 
00038ee0
[137133.774560] RDX: 0001 RSI: 0001 RDI: 
95409700
[137133.774564] RBP: b16640487a10 R08: 0002 R09: 

[137133.774567] R10: 0001 R11:  R12: 
95409700
[137133.774571] R13: 4130 R14: 98aeb0d14870 R15: 
0010f224
[137133.774575] FS:  () GS:98b5dfc8() 
knlGS:
[137133.774579] CS:  0010 DS:  ES:  CR0: 80050033
[137133.774583] CR2: 4164 CR3: 00074601 CR4: 
00350ee0
[137133.774587] Call Trace:
[137133.774591]  
[137133.774596]  __dquot_drop+0x91/0xc0
[137133.774602]  dquot_drop+0x53/0x60
[137133.774606]  ext4_clear_inode+0x44/0xb0
[137133.774613]  ext4_evict_inode+0x86/0x670
[137133.774618]  evict+0xcf/0x190
[137133.774624]  prune_icache_sb+0x81/0xc0
[137133.774629]  super_cache_scan+0x169/0x200
[137133.774635]  do_shrink_slab+0x155/0x2c0
[137133.774641]  shrink_slab_memcg+0xcf/0x1e0
[137133.774646]  shrink_slab+0x10a/0x120
[137133.774651]  ? shrink_slab+0x10a/0x120
[137133.774655]  shrink_node_memcgs+0x188/0x1d0
[137133.774660]  shrink_node+0x15d/0x5c0
[137133.774666]  balance_pgdat+0x36e/0x800
[137133.774670]  ? try_to_del_timer_sync+0x22/0x90
[137133.774677]  kswapd+0x10c/0x1c0
[137133.774682]  ? balance_pgdat+0x800/0x800
[137133.774686]  kthread+0x127/0x150
[137133.774691]  ? set_kthread_struct+0x50/0x50
[137133.774696]  ret_from_fork+0x1f/0x30
[137133.774703]  
[137133.774706] Modules linked in: tcp_diag udp_diag inet_diag xt_nat xt_tcpudp 
veth tls binfmt_misc xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat 
nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user 
xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter 
bridge cfg80211 8021q garp mrp stp llc overlay intel_rapl_msr intel_rapl_common 
mei_hdcp nls_iso8859_1 intel_pmc_bxt intel_telemetry_pltdrv intel_punit_ipc 
intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm rapl intel_cstate ee1004 ucsi_acpi r8125(OE) mei_me typec_ucsi mei typec 
mac_hid sch_fq_codel dm_multipath ipmi_devintf scsi_dh_rdac ipmi_msghandler 
scsi_dh_emc scsi_dh_alua ramoops mtd msr reed_solomon pstore_blk pstore_zone 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage i915 
i2c_algo_bit
  ttm
[137133.774796]  drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
cec rc_core i2c_i801 xhci_pci crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
intel_lpss_pci aesni_intel drm r8169 nvme ahci i2c_smbus libahci intel_lpss 
crypto_simd idma64 xhci_pci_renesas nvme_core cryptd realtek video 
pinctrl_geminilake
[137133.774849] CR2: 4164
[137133.774854] ---[ end trace 85a590ce733b1c95 ]---

The process and exact message changes, but it's ext4 related.

Description:Ubuntu 22.04.1 LTS
Release:22.04
(GNU/Linux 5.15.0-57-generic x86_64)
ODROID-H2+
Two Team Group CX2 2.5" 2TB SATA III 3D TLC Internal Solid State Drive (SSD) 
T253X6002T0C101 in RAID1 as a storage drive (not root)
Team Group MP33 M.2 2280 1TB PCIe 3.0 x4 with NVMe 1.3 3D NAND Internal Solid 
State Drive (SSD) TM8FP6001T0C101 (which seems to be the problem)
Google Coral
smartctl shows no errors
It can be days or weeks before I see the issue unless I do something like a 
backup that has high utilization for an extended period of time.

I would expect the computer to run smoothly.

Instead, it throws the message and crawls to a hault as disk access stops 
working.
r8125 driver is the only non-distro module

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/2002748

Title:
  Unable to handle page fault under heavy

[Kernel-packages] [Bug 1996981] [NEW] package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1

2022-11-17 Thread Adam Mock

Public bug reported:

package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1
[modified: usr/share/bash-completion/completions/bpftool
usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower-
monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-
annotate.1.gz usr/share/man/man1/perf-archive.1.gz
usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-
cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-ftrace.1.gz
usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-inject.1.gz
usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz
usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz
usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz
usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz
usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz
usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-script-
python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-
stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1/perf-
trace.1.gz usr/share/man/man1/perf-version.1.gz
usr/share/man/man1/perf.1.gz usr/share/man/man1/usbip.8.gz
usr/share/man/man1/usbipd.8.gz usr/share/man/man8/bpftool-btf.8.gz
usr/share/man/man8/bpftool-cgroup.8.gz usr/share/man/man8/bpftool-
feature.8.gz usr/share/man/man8/bpftool-map.8.gz
usr/share/man/man8/bpftool-net.8.gz usr/share/man/man8/bpftool-perf.8.gz
usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz
usr/share/man/man8/turbostat.8.gz] failed to install/upgrade: trying to
overwrite '/usr/bin/acpidbg', which is also in package linux-tools-
common 5.4.0-131.147

ProblemType: Package
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21
Uname: Linux 5.14.0-1054-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Nov 18 15:10:06 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.4.0-131.147
InstallationDate: Installed on 2022-06-08 (162 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: linux-intel-iotg-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-intel-iotg-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check package-conflict

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

Title:
  package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1
  [modified: usr/share/bash-completion/completions/bpftool
  usr/share/man/man1/cpupower-idle-info.1.gz
  usr/share/man/man1/cpupower-monitor.1.gz
  usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz
  usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-
  bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz
  usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz
  usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz
  usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz
  usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz
  usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-
  report.1.gz usr/share/man/man1/perf-sched.1.gz
  usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-
  script-python.1.gz usr/share/man/man1/perf-script.1.gz
  usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz
  usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf-
  top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf-
  version.1.gz usr/share/man/man1/perf.1.gz
  usr/share/man/man1/usbip.8.gz usr/share/man/man1/usbipd.8.gz
  usr/share/man/man8/bpftool-btf.8.gz usr/share/man/man8/bpftool-
  cgroup.8.gz usr/share/man/man8/bpftool-feature.

[Kernel-packages] [Bug 1992383] [NEW] package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1 [modified: usr/share/bash-completion/completions/bpftool usr/share/man/man1/cpupower-idle-info.1

2022-10-10 Thread Adam Mock

Public bug reported:

Automatic update failed.

package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1
[modified: usr/share/bash-completion/completions/bpftool
usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower-
monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-
annotate.1.gz usr/share/man/man1/perf-archive.1.gz
usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-
cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-ftrace.1.gz
usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-inject.1.gz
usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz
usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz
usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz
usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz
usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz
usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf-script-
python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-
stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1/perf-
trace.1.gz usr/share/man/man1/perf-version.1.gz
usr/share/man/man1/perf.1.gz usr/share/man/man1/usbip.8.gz
usr/share/man/man1/usbipd.8.gz usr/share/man/man8/bpftool-btf.8.gz
usr/share/man/man8/bpftool-cgroup.8.gz usr/share/man/man8/bpftool-
feature.8.gz usr/share/man/man8/bpftool-map.8.gz
usr/share/man/man8/bpftool-net.8.gz usr/share/man/man8/bpftool-perf.8.gz
usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz
usr/share/man/man8/turbostat.8.gz] failed to install/upgrade: trying to
overwrite '/usr/bin/acpidbg', which is also in package linux-tools-
common 5.4.0-125.141

ProblemType: Package
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.14.0-1051.58-oem 5.14.21
Uname: Linux 5.14.0-1051-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering:
 linux-intel-iotg-5.15-tools-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Oct 10 20:39:09 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
DpkgTerminalLog:
 Preparing to unpack 
.../linux-intel-iotg-5.15-tools-common_5.15.0-1016.21~20.04.1_all.deb ...
 Unpacking linux-intel-iotg-5.15-tools-common (5.15.0-1016.21~20.04.1) over 
(5.15.0-1010.14~20.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-intel-iotg-5.15-tools-common_5.15.0-1016.21~20.04.1_all.deb
 (--unpack):
  trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.4.0-125.141
ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package 
linux-tools-common 5.4.0-125.141
InstallationDate: Installed on 2022-06-08 (124 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: linux-intel-iotg-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-intel-iotg-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check package-conflict

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

Title:
  package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1
  [modified: usr/share/bash-completion/completions/bpftool
  usr/share/man/man1/cpupower-idle-info.1.gz
  usr/share/man/man1/cpupower-monitor.1.gz
  usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz
  usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-
  bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz
  usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz
  usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz
  usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz
  usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz
  usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-
  report.1.gz usr/share/man/man1/

[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot

2022-09-01 Thread Adam Collard

** Changed in: maas
 Assignee: (unassigned) => Björn Tillenius (bjornt)

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

Title:
  Unable to deploy HWE kernel with sub-arch set to xgene-uboot

Status in MAAS:
  New
Status in linux package in Ubuntu:
  Expired

Bug description:
  When trying to deploy Moonshot nodes, the sub-arch must be set to
  xgene-uboot for it to be deployed with GA kernel.

  However, when trying to deploy it with the HWE kernel it will complain that:
  Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel.

  [ deleted the bit about how generic/hwe fails, because that is
  expected. this machine requires xgene-uboot/hwe ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1922910/+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 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

2022-06-09 Thread Adam-morey

For Debian and Ubuntu, I used "sudo grub-reboot 2", which forces grub
menu 2's kernel on next reboot.  Once rebooted, use "dpkg-l | grep 1028"
and apt remove each package relate to kernel 1028.  Apt will also update
grub for you.

Don't forget to uninstall or "break" unattended-upgrades, which is how
my server got the new kernel in the first place.

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

Title:
  Docker container creation causes kernel oops on linux-aws
  5.13.0.1028.31~20.04.22

Status in linux-aws-5.13 package in Ubuntu:
  Confirmed
Status in linux-azure-5.13 package in Ubuntu:
  Confirmed
Status in linux-gcp-5.13 package in Ubuntu:
  Confirmed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Confirmed
Status in linux-oracle-5.13 package in Ubuntu:
  Confirmed
Status in linux-aws-5.13 source package in Focal:
  Fix Committed
Status in linux-azure-5.13 source package in Focal:
  Fix Committed
Status in linux-gcp-5.13 source package in Focal:
  Fix Committed
Status in linux-intel-iotg-5.15 source package in Focal:
  Won't Fix
Status in linux-oracle-5.13 source package in Focal:
  Fix Committed

Bug description:
  Running the attached script on the latest AWS AMI for Ubuntu 20.04, I
  get a kernel panic and hard reset of the node.

  [   12.314552] VFS: Close: file count is 0
  [   12.351090] [ cut here ]
  [   12.351093] kernel BUG at include/linux/fs.h:3104!
  [   12.355272] invalid opcode:  [#1] SMP PTI
  [   12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws 
#31~20.04.1-Ubuntu
  [   12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
  [   12.371130] RIP: 0010:__fput+0x247/0x250
  [   12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.393425] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.398679] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.419533] FS:  () GS:9153ea90() 
knlGS:
  [   12.426937] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 
007706e0
  [   12.436716] DR0:  DR1:  DR2: 

  [   12.441941] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   12.447170] PKRU: 5554
  [   12.450355] Call Trace:
  [   12.453408]  
  [   12.456296]  fput+0xe/0x10
  [   12.459633]  task_work_run+0x70/0xb0
  [   12.463157]  do_exit+0x37b/0xaf0
  [   12.466570]  do_group_exit+0x43/0xb0
  [   12.470142]  __x64_sys_exit_group+0x18/0x20
  [   12.473989]  do_syscall_64+0x61/0xb0
  [   12.477565]  ? exit_to_user_mode_prepare+0x9b/0x1c0
  [   12.481734]  ? do_user_addr_fault+0x1d0/0x650
  [   12.485665]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   12.489790]  ? irqentry_exit+0x19/0x30
  [   12.493443]  ? exc_page_fault+0x8f/0x170
  [   12.497199]  ? asm_exc_page_fault+0x8/0x30
  [   12.501013]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   12.505289] RIP: 0033:0x7f80d42a1bd6
  [   12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac.
  [   12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 
00e7
  [   12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 
7f80d42a1bd6
  [   12.526115] RDX:  RSI: 003c RDI: 

  [   12.531328] RBP:  R08: 00e7 R09: 
fe98
  [   12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 
7f80d45a4740
  [   12.541687] R13: 0002 R14: 7f80d45ad708 R15: 

  [   12.546916]  
  [   12.549829] Modules linked in: xt_conntrack xt_MASQUERADE 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter 
iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc 
input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr 
drm ip_tables x_tables autofs4
  [   12.583913] ---[ end trace 77367fed4d782aa4 ]---
  [   12.587963] RIP: 0010:__fput+0x247/0x250
  [   12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 0

[Kernel-packages] [Bug 1954692] Re: Reconsider compressed kernels on arm64

2022-03-17 Thread Adam Collard

** Changed in: maas-images
   Status: In Progress => Fix Committed

** Changed in: maas-images
   Importance: Undecided => High

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

Title:
  Reconsider compressed kernels on arm64

Status in maas-images:
  Fix Committed
Status in flash-kernel package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Compressed kernel images were introduced in bug 1384955 to work around
  some limits on old u-boot systems. This in turn broke grub-check-
  signatures, meaning that while cloud images booted in secure boot, you
  could not upgrade grub or install new kernels on secure systems as
  that would trigger a "you have unsigned kernels" message. grub 2.06
  also fails to boot the images, as it verifies before decompressing.

  Work to fix grub to handle such images on arm64 for backward
  compatibility is tracked in bug 1954683. This bug is to reconsider
  whether the change is still necessary or could be removed in 22.04
  such that we can have proper UEFI executables again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1954692/+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 1957154] [NEW] Can't boot after kernel 5.11.0-44 update

2022-01-12 Thread Adam Mateusz Brożyński

Public bug reported:

- With kernel 5.11.0-41 everything is ok. 
- Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch 
lines at top of screen and instant reboot.
- It may be related to nvidia-driver-470?

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-44-generic 5.11.0-44.48
ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  adam   1523 F mate-settings-d
  adam   1928 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jan 12 10:00:59 2022
InstallationDate: Installed on 2021-10-03 (101 days ago)
InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. Precision T3600
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-41-generic N/A
 linux-backports-modules-5.11.0-41-generic  N/A
 linux-firmware 1.197.5
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2018
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 08HPGT
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision T3600
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug hirsute third-party-packages

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

Title:
  Can't boot after kernel 5.11.0-44 update

Status in linux package in Ubuntu:
  New

Bug description:
  - With kernel 5.11.0-41 everything is ok. 
  - Choosing updated kernel 5.11.0-44 or 5.11.0-46 in Grub results in glitch 
lines at top of screen and instant reboot.
  - It may be related to nvidia-driver-470?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-44-generic 5.11.0-44.48
  ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   1523 F mate-settings-d
    adam   1928 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Wed Jan 12 10:00:59 2022
  InstallationDate: Installed on 2021-10-03 (101 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  MachineType: Dell Inc. Precision T3600
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=014ec6ad-d170-40b9-8b77-af7620c76daf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-41-generic N/A
   linux-backports-modules-5.11.0-41-generic  N/A
   linux-firmware 1.197.5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 08HPGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/21/2018:br4.6:svnDellInc.:pnPrecisionT3600:pvr01:sku:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957154/+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 1946055] Re: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop!

2021-12-03 Thread Adam Stylinski

We're seeing this on a laptop at work (TigerLake Oryx Pro from System76)
on 20.04 as well.

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

Title:
  Ubuntu 21.04 drivers/drm/i915 crashes on my laptop!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [2.515353] Missing case (val == 65535)
  [2.515366] WARNING: CPU: 3 PID: 478 at 
drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915]
  [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep 
nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp 
intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel 
snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress 
cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core 
i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me 
thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect 
snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm 
processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei 
intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq 
snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone 
mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad 
acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr
  [2.515472]  parport_pc ppdev lp drm parport ip_tables x_tables autofs4 
crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme 
thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake
  [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P   O 
 5.11.0-37-generic #41-Ubuntu
  [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W 
(1.15 ) 09/01/2021
  [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915]
  [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 
41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 
0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09
  [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282
  [2.515537] RAX:  RBX: be36011b79ec RCX: 
9b27574d8ac8
  [2.515538] RDX: ffd8 RSI: 0027 RDI: 
9b27574d8ac0
  [2.515539] RBP: be36011b79a8 R08:  R09: 
be36011b7760
  [2.515540] R10: be36011b7758 R11: a37535e8 R12: 

  [2.515541] R13: 004c R14: 9b164558 R15: 

  [2.515542] FS:  7fb8218a08c0() GS:9b27574c() 
knlGS:
  [2.515544] CS:  0010 DS:  ES:  CR0: 80050033
  [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 
00770ee0
  [2.515546] PKRU: 5554
  [2.515546] Call Trace:
  [2.515549]  skl_dram_get_channel_info+0x2e/0x150 [i915]
  [2.515592]  skl_dram_get_channels_info+0x6e/0x190 [i915]
  [2.515634]  skl_get_dram_info+0x6e/0x100 [i915]
  [2.515667]  intel_dram_detect+0x3e/0xd0 [i915]
  [2.515711]  i915_driver_hw_probe+0x1cc/0x210 [i915]
  [2.515748]  i915_driver_probe+0xe5/0x2f0 [i915]
  [2.515781]  ? mutex_lock+0x13/0x40
  [2.515785]  ? acpi_dev_found+0x66/0x70
  [2.515788]  i915_pci_probe+0x58/0x140 [i915]
  [2.515822]  local_pci_probe+0x48/0x80
  [2.515824]  pci_call_probe+0x53/0xf0
  [2.515826]  pci_device_probe+0xad/0xf0
  [2.515827]  really_probe+0x23a/0x4a0
  [2.515830]  driver_probe_device+0xe9/0x160
  [2.515832]  device_driver_attach+0xab/0xb0
  [2.515833]  __driver_attach+0x8f/0x150
  [2.515835]  ? device_driver_attach+0xb0/0xb0
  [2.515836]  bus_for_each_dev+0x7e/0xc0
  [2.515837]  driver_attach+0x1e/0x20
  [2.515839]  bus_add_driver+0x135/0x1f0
  [2.515840]  driver_register+0x95/0xf0
  [2.515842]  __pci_register_driver+0x54/0x60
  [2.515843]  i915_init+0x66/0x86 [i915]
  [2.515877]  ? 0xc0c7
  [2.515878]  do_one_initcall+0x48/0x1d0
  [2.515881]  ? kmem_cache_alloc_trace+0xf6/0x200
  [2.515883]  ? do_init_module+0x28/0x290
  [2.515886]  do_init_module+0x62/0x290
  [2.515887]  load_module+0x6fd/0x780
  [2.515888]  __do_sys_finit_module+0xc2/0x120
  [2.515890]  __x64_sys_finit_module+0x1a/0x20
  [2.515891]  do_syscall_64+0x38/0x90
  [2.515893]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [2.515894] RIP: 0033:0x7fb821d58f6d
  [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48
  [2.515897] RSP: 002b:7ffdf53714c8 EFLAGS: 0246 ORIG_RA

[Kernel-packages] [Bug 1908090] Re: ubuntu 20.04 kdump fails

2021-11-30 Thread Adam Dorsey

Same issue here, with the same workaround for me:

Edit /etc/default/grub.d/kdump-tools.cfg

Change the crashkernel part to read
crashkernel=512M-:256M

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

Title:
  ubuntu 20.04 kdump fails

Status in kexec-tools package in Ubuntu:
  Confirmed

Bug description:
  When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS,
  everything appears to be in good working order, according to
  "systemctl status kdump-tools" and "kdump-config status". However,
  upon an actual crash, the system hangs, and no crash files are
  produced. I've investigated and have learned that the capture kernel
  does indeed start, but it is unable to unpack the rootfs/initrd, and
  thus fails and hangs.

  [1.070469] Trying to unpack rootfs image as initramfs...
  [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), 
order=0, oom_score_adj=0
  [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic 
#30-Ubuntu 
  [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [1.336396] Call Trace:
  [1.336396]  dump_stack+0x6d/0x9a
  [1.336396]  dump_header+0x4f/0x1eb
  [1.336396]  out_of_memory.part.0.cold+0x39/0x83
  [1.336396]  out_of_memory+0x6d/0xd0
  ...
  [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on 
memory ]---

  
  On this system with 8G of memory, the crash memory as specified on the kernel 
command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now 
kdump works.

  Not sure how the 192M value is chosen, but it does not work. I think
  this used value used to work for 16.04 and maybe 18.04 (I didn't try),
  but is no longer useful for 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1908090/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

2021-11-18 Thread Adam Niedling

Bumped into this bug after upgrading to 21.10. Laptop with nVidia 2080, 
DisplayPort to external screen.
Adding LIBGL_DRI3_DISABLE=true to /etc/environment fixed my issue.

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

Title:
  Ubuntu 20.04 and Displaylink is extremely slow

Status in Nouveau Xorg driver:
  Unknown
Status in OEM Priority Project:
  New
Status in X.Org X server:
  Unknown
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  In Progress
Status in xserver-xorg-video-nouveau package in Ubuntu:
  In Progress
Status in xorg-server source package in Focal:
  In Progress
Status in xorg-server source package in Hirsute:
  In Progress
Status in xorg-server source package in Impish:
  Fix Released

Bug description:
  Using ubuntu 20.04 on displaylink docking with external monitor is
  totally slow, unusable. The GUI responds very slow, if you click, the
  command of the click goes on after about 3 seconds... if you type, all
  the letters are with the same lag, so it is totally unusable.

  Was using displaylink without any problem on 19.10 until yesterday, when I 
upgraded to 20.04. 
  It is terrific.

  If i plug out the usb for the displaylink docking station, than the
  speed is back, and the system is ok, if I connect it to the docking
  station again, everything extremely slow again.

  Please investigate this asap, as it is unusable on displaylink docking
  stations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1948576] Re: Ubuntu 21.10 latest update making problem

2021-10-25 Thread Adam

Not sure if the above info is good enough to find the bug? thanks

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

Title:
  Ubuntu 21.10 latest update making problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The fans spin at max and the system freezes after I un-suspend the system. 
That start to happen after I update the latest 21.10. I was happy with the 
21.10 at the begging but when I update the latest release, got me upset. Please 
see attached log file.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ahmed  2282 F pulseaudio
   /dev/snd/controlC1:  ahmed  2282 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-14 (224 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash pci=noaer 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-14 (9 days ago)
  UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948576/+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

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 2742 matches

Mail list logo